Co-location details and requirements

The hosting environment

Servers are placed within a research dedicated VRF with a default deny off-campus/default allow on-campus Firewall zone (Zone8)
IST recommends researcher install host based firewalls
Area8 can access IST production servers only for DNS/DHCP/NTP/Kerberos/LDAP services
All equipment and software are subject to all campus policies related to computing/networking
All change requests must come from a single Point of Contact (POC); or the POC must be CC'd and approve the requested change
Firewall rules are host specific
All physical access is ESCORTED access (expected to be less than 2 instances/year) - 24x7 coverage
Special cases (PCI/DSS, Government of Canada protected/classified) are on a case-by-case basis

A common out of band (OOB) management subnet
OOB subnet accessible via a common Windows JumpBox
JumpBox is accessible from On-campus or via restricted [Nexus AD group] VPN
Common public data subnet available with ipv6 – static addressing ipv4 and ipv6
Common private data subnet available with ipv6 – static addressing ipv4 and ipv6

The server must:

Be 19" rack mountable ideally with square hole rack kit
Have dual power supplies accepting C13/C15/C19 with 208V+ (Note: we do not have 120V capacity)
Have a remote access ability ‘enterprise remote access’ (Dell:iDRAC, Oracle:iLOM, HP:iLO, IBM: IMM)
1G RJ45, 10G RJ45 or 10G SFP+ network adapters
To utilize redundancy built within the datacentre, servers should have 2x network adapters and support Link Aggregation Control Protocol (LACP)

Faculty supported researchers can install physical hardware into IST Datacentre (East Campus 2, EC2)
IST is only able to support the physical and logical infrastructure
While every effort will be made to host researcher equipment, not all systems can be hosted within this environment
IST cannot host High Performance Computing clusters or other like systems
IST will not host servers for commercial purposes or hosting sites or applications offering commercial products or services
Systems hosting regulated data must be identified (eg: PCI/DSS, HIPAA, Protected) and will be approved on a case-by-case basis