The Enterprise Standard Operating Environment is proposed as a set of minimum standards to be supported or applied for any Commonwealth of Massachusetts Operating Environment within the Executive Department. The goal of articulating the Standard Operating Environment is to increase the interoperability and supportability across the Commonwealth’s technical infrastructure.
In addition to the standards noted in the table below; please find the overview of ITD’s implementation of these standards as part of the standard Data Center Service Offerings. It is important to note that when organizations utilize ITD’s standard Service Offerings that the minimum standards will be implemented and applied as part of that offering. It is also important to recognize that organizations that need to connect to ITD hosted solutions will need to be aware of the SOE and ITD’s implemented services.
As with all architectural documentation; these standards are part of a living document. As knowledge and technology grows and evolves; our standards will need to as well.
NETWORK STANDARDS
1. Connection to MAGNet may be done using any of the following standard methods:
| 1.1. MPLS 1.2. Campus Backbone 1.3. Data Center 1.4. Internet |
| 2. Connection to MAGNet requires use of either Fiber Channel or Ethernet | 2.1. Fiber Channel is required for any connection into ITD’s Enterprise Data Center, e.g. storage, back-up and recovery, etc. 2.2. Ethernet connection is required to access any MAGNet services. |
3. Supported WAN/LAN Hardware
| 3.1. Data Center and Campus Backbone 3.2. WAN and LAN
|
| 4. Standard Ports and Protocols The following standard ports and protocols are specific to network technology alone, and do not include the required security ports and protocols as referenced in the Enterprise Access Control Standards . | 4.1. ITD Network Services uses the following standard protocols to implement the ITD Data Network: 4.2. ITD Network Services uses the following standard protocols to implement the ITD Backup Network: 4.3. ITD Network Services uses the following standard protocols to implement the ITD ILO Network: 4.4. ITD Network Services uses the following standard protocols to implement the ITD Fiber Channel Network: FCOE is emerging as an alternative to transport over fiber optic cabling |
WINDOWS STANDARDS
| 1. All Windows deployments must include the following minimum standard software requirements including one of the following versions of the Windows operating system: | 1.1. Operating Systems 1.2. Anti-Virus |
| 2. All Windows physical deployment platforms must meet the following minimum standard requirements: | 2.1. Chipset 2.2. Memory 2.3. Storage
|
LINUX STANDARDS
| 1. All Linux deployments must include the following minimum standard software requirements: | 1.1. Operating Systems 1.2. Software Updates
|
| 2. All Linux physical deployment platforms must meet the following minimum standard requirements: | 2.1. Chipset 2.2. Memory 2.3. Storage |
MASSCLOUD VIRTUALIZATION STANDARDS
| 1. The following server platform is supported by ITD for virtualized Guest Operating Platforms | 1.1 Intel x86 architecture computing platform |
| 2. All MASSCLOUD Virtualized Guest deployments must utilize one of the following standard Operating System requirements: | 2.1. Linux Operating Systems 2.2. Windows Operating Systems |
STORAGE STANDARDS
| 1. The following server platforms are supported as standard by ITD for Storage Services: | 1.1. Intel x86 architecture computing platform with Windows and Linux 1.2. Intel x86 architecture computing platform with EMC ESXi virtualization services with Windows and Linux 1.3. IBM Power architecture computing platform with AIX 1.4 Assessment of connectivity to other platforms is available on request |
| 2. The following is required by ITD for interconnecting to Storage Services: | 2.1 Fiber Channel connectivity |
BACKUP AND RECOVERY STANDARDS
| 1. The following server platforms are supported by ITD for Backup/Recovery Services: | 1.1. Intel x86 architecture computing platform 1.2. Intel x86 architecture computing platform with EMC ESXi virtualization services 1.3 IBM Power architecture computing platform |
| 2. The following operating systems are supported with agents for Backup/Recovery Services: | 2.1. Windows 2008 (Standard 32-bit, Enterprise 64-bit, and Enterprise R2 64-bit) 2.2. Red Hat Enterprise Linux 5 64-bit 2.3 AIX 6 |
| 3. The following is required by ITD for interconnecting to Backup/Recovery Services: | 3.1. Fiber Channel connectivity for backup/recovery of SAN-based storage 3.2 Ethernet connectivity for backup/recovery of direct attached (DAS) or network attached storage (NAS) |
AIX STANDARDS
| 1. All AIX deployments must include the following minimum standard software requirements: | 1.1. Operating Systems 1.1.1 AIX 6 |
| 2. All AIX virtual partition deployments must meet the following minimum standard requirements: | 2.1. Virtual CPU 2.2. Virtual Memory 2.3. Virtual Storage |
DATABASE STANDARDS
| 1. The following server platforms are supported by ITD for Database Services: | 1.1. Intel x86 architecture computing platform 1.2. Intel x86 architecture computing platform with EMC ESXi virtualization services 1.3 IBM Power architecture computing platform |
| 2. The following operating systems are supported with agents for Database Services: | 2.1. Windows 2008 (Standard 32-bit, Enterprise 64-bit, and Enterprise R2 64-bit) 2.2. Red Hat Enterprise Linux 5 64-bit 2.3 AIX 6 |
| 3. The following are the standard supported Database Versions: | 3.1. Oracle – 10g and above 3.2 SQL Server – 2005 and above |
SCHEDULING STANDARDS
| 1. The following server platforms are supported by ITD for Scheduling Services: | 1.1. Intel x86 architecture computing platform 1.2. Intel x86 architecture computing platform with EMC ESXi virtualization services 1.3 IBM ‘P’ Series |
| 2. The following Operating Systems are supported by ITD for Scheduling Services: | 2.1. Linux Operating Systems 2.2. Windows Operating Systems 2.3. AIX Operating Systems |
MIDDLEWARE STANDARDS
| 1. The following server platforms are supported by ITD for Middleware Services: | 1.1. Intel x86 architecture computing platform 1.2. Intel x86 architecture computing platform with EMC ESXi virtualization services with Windows and Linux 1.3 IBM Power architecture computing platform with AIX |
| 2. The following Operating Systems are supported by ITD for Scheduling Services: | 2.1. Linux Operating Systems 2.2. Windows Operating Systems 2.3. AIX Operating Systems |
SERVER STANDARDS
| 1. Intel Processor Architecture Systems must contain at least 2 processor sockets and capability for supporting the current generation of processors. Processors must be rated as LV (Low Voltage). System BIOS should provide capability for supporting Intel Virtualization Extensions directly. | 1.1. Processor: 1.2. Processor Cache: |
| 2. Memory Architecture and System Chipset Systems must be supported on current chipset. Chipset must be Intel based. At least 2-way interleaved memory compliant with current generation of processor architecture. Memory should be ECC, registered DIMMS with capability for memory mirroring and/or online spare. Integrated heat Sinks should be provided on all DIMMS. | 2.1. Memory RDIMM Support
|
| 3. Network Controller Systems must contain, built onto system board in such a manner as to not occupy available expansion slots, a number of NIC ports supporting 802.3ab 1000BaseT Ethernet. Network cards should support jumbo Ethernet frames, TCP/IP offloading (TOE,TSO), 802.1Q VLAN Trunking and Tagging, QoS, and capability for driver enabled transition to iSCSI | 3.1. Network Interface Cards:
|
| 4. Storage Controller Built-in support for SAS/SATA should be provided on system board. Direct-Attached-Storage RAID support should be available as an option using an integrated solution or PCI-Add-On card with internal support in hardware for RAID 0, 0+1, and 5. On-Board cache memory must range from an optional 0 or 256MB. | 4.1. Storage Controllers: 4.1.1. SAS/SATA 256MB Battery Backed Controller (RAID 0/1/10/5/50/6) w/support for drive hot-swap |
| 5. Storage Backplane – Internal Direct Attached Storage System must have at least support for a number of hot-swap hard drives, supporting either SATA (1.5Gb) or SAS (3.0Gb) interfaces in a hot-swappable backplane. Hot-swap backplane must be capable of support a two-channel optional configuration for duplexing. | 5.1. Internal Drive Support 5.2. Hard disk drives support: |
| 6. PCI Expansion System Capable of supporting at least one full length x16-lane (backward compatible to x8-lane and x4-lane) PCI Express slot with option riser replacement to support single full length 64-bit, 133MhZ PCI-X card. Additionally, system must support up to 2 other slots that are x4-lane. | 6.1. PCI Expansion Slots: 6.1.1. 2 PCI-Express of which 1 must be x8 lane and 1 must be either x4 or x8 lane |
| 7. Remote Management Interface All systems must have the capability to remotely manage the server system via a dedicated Network Interface adapter, supporting 10/100Mb speeds using a TCP/IP addressing for offline and online system management. Remote management card must be operational both in offline (powered down) and online states of the server. | 7.1. Required Remote Management Features 7.1.1. Integrated on System Board 7.1.2. HTTPS Support 7.1.3. Authentication Support 7.1.3.1. Challenge/Response, 2-Factor via Certificate/Logon 7.1.4. SSH Support 7.1.5. System Status Summary 7.1.5.1. Should minimally show fault status, temp, system logs, power I/O, and redundancy status 7.1.6. Changeable TCP Port Ranges 7.1.7. Virtual Console 7.1.7.1. Must support remote KVM with SVGA and USB Virtual Media 7.1.8. Virtual Media 7.1.8.1. Must be capable of reading ISO files and emulating a local directory as a media device to the remote host 7.1.9. Remote Power Up/Down |
| 8. USB Support All systems must have support for USB 2.0 connectivity both internal and externally. | 8.1. USB Ports: 8.1.1. At least 2 Front, 2 Rear, 1 Internal |
| 9. Operating System Support Compatibility must include necessary OEM and manufacturer drivers, monitoring agents, and integration with supplied management software through SNMP or CIM agents. | 9.1. O/S and Virtualization:
|
