| Storage |
Storage Area Network, VPN and SAN management servers |
| Console |
Remote Console Access to servers |
| Network |
Services in support of the network and Server Farm such as DNS, DHCP, SSO |
| Auth |
Authentication and Authorization servers (e.g. Kerberos and permit) |
| NOC |
NOC Infrastructure to support communications among NOC, Server Farm, and Systems Support Staff |
| Monitoring |
Server Farm and Network monitoring |
| Email |
CU messaging infrastructure |
| Email - after |
Those email servers that need to wait for the infrastructure to be in place (e.g. mail routers) |
| CU/CIT -before |
Servers that need to be functional before the CU/CIT web servers are restarted (e.g. database back end) |
| CU/CIT web |
Informational infrastructure including cornell.edu, uportal, and HelpDesk systems like Vantive or Remedy |
| CU Mission |
High-impact servers that directly support Cornell instruction |
| Library |
In support of Cornell instruction |
| Data Rec |
Data Recovery Infrastructure to recover servers that lose a disk or data (e.g. EZ-Backup) |
| CU Business |
Maintaining Cornell administration - the business of Cornell (e.g. Payroll) |
| Services |
Other services that have smaller impact and/or do not require high availability |
| Test/Dev |
Systems that are for testing, development, and backup |
