6 Oracle Collaboration Suite On Demand Infrastructure

Oracle Collaboration Suite Certified Configuration

The Oracle Collaboration Suite Certified Configuration is installed with the latest Oracle Collaboration Suite software and is pre-configured to comply with On Demand rules and policies. Oracle provides a production and non-production environment for Oracle Collaboration Suite On Demand Customers.The Production environment is designed to run the Customer's production Oracle Collaboration Suite system. A Test environment is used for problem diagnostics and resolution and patch verification. Additional non-production environments may be purchased.

The Oracle Collaboration Suite Certified Configuration consists of the following components:

• Oracle Collaboration Suite Certified Configuration Utility Pack Release 2.3.1

• Oracle9iAS Infrastructure 9.0.2.3

  • Oracle9iAS Metadata Repository with Oracle9i Release 1 (9.0.1.4) database

  • Oracle Internet Directory (OID) with patch 9.0.2.3

  • Oracle9iAS Single Sign-On (SSO) with patch 9.0.2.3

  • Oracle9iAS Containers for J2EE with patch 9.0.2.3

  • Web Cache with patch 9.0.2.3

• Oracle® Server - Enterprise Edition 9.2.0.3

• Oracle® Collaboration Suite 9.0.4.1.0

  • Oracle® Email

  • Oracle® Files

  • Oracle® Real-Time Collaboration

  • Oracle® Calendar

  • Oracle® Wireless

  • Oracle® Ultra Search

• Oracle® Workflow 2.6.2

Language

The Oracle Collaboration Suite On Demand Certified Configuration contains only U.S. English as the base language. All other Customer required languages are installed during the Initialization phase of the On Demand Life Cycle.

Database Server

Each customer utilizes a dedicated database server that provides the information required to offer Oracle Collaboration Suite services. The Email, Voicemail, and Fax message store, the Conferencing store, the Files store, the Directory store, and the Calendar store are each separate databases with their own Oracle homes. This allows Oracle On Demand to service databases individually and facilitates Customers addition of databases and servers. Customers can also grow from small to large without requiring any software reconfiguration. And for even more extensive growth, the message store, files store, and directory store databases can be expanded to multiple servers each using Oracle Real Application Clusters.

The database server contains the following minimum preconfigured elements:

• Linux/Intel machine with 2 CPUs, 6 GB RAM,

• 2 Intel Pro 1000MT NICs

• Red Hat Linux Advanced Server 2.1 e.35

• Oracle Collaboration Suite 9.0.4.1 Certified Configuration

Protocol Server

Each customer utilizes a dedicated protocol server as the direct interface with most of Oracle Collaboration Suite services. Each protocol server is configured identically, providing most of the e-mail and all of the web, directory, files, calendar, and conferencing interfaces. If the requested information is not already cached on the protocol server, this server turns service requests into SQL commands to the databases that supply or update the actual data for the service.

The Protocol server contains the following minimum preconfigured elements:

• Linux/Intel machine with 2 CPUs, 6 GB RAM

• 2 Intel Pro 1000MT NICs

• Red Hat Linux Advanced Server 2.1 e.35

• Oracle Collaboration Suite 9.0.4.1 Certified Configuration

SMTP Relay Server

The shared SMTP Relay server acts as the SMTP gateway between the open Internet and all Oracle Collaboration Suite On Demand customer environments. Each incoming and outgoing message is scanned for virus or spam content at this point. This is required for all environments although multiple environments may share a single or set of SMTP Relay Servers.

The shared SMTP Relay server contains the following preconfigured elements:

• Linux/Intel machine with 2 CPUs, 6 GB RAM

• Red Hat Linux Advanced Server 2.1 e.35

• Sendmail, Inc. Sendmail Switch 3.1.4

• Sendmail, Inc. Mailstream Attachment Filter Plugin for Sendmail Switch 2.6.0

• TrendMicro InterScan Messaging Security Suite 5.5

• Brightmail Anti-Spam Enterprise Edition 5.5.2

Voicemail/Fax Computer Telephony (CT) Server

Customers that wish to use the voicemail/fax functionality must purchase and physically locate a Voicemail/Fax Computer Telephony (CT) server at the Customer's premise close to each PBX phone switch. The PBX switch routes incoming phone and fax calls to the Voicemail/Fax CT server, which looks up the user, retrieves the appropriate greeting, and then stores or retrieves the incoming message or fax. In most cases, the PBX switch also enables or disables end user telephone Òmessage waitingÓ lights. If a customer has PBX switches in multiple locations, the Voicemail/Fax CT servers must be installed at each PBX switch location. Multiple Voicemail/Fax CT servers can be used for each PBX switch, depending on workload requirements and requirements for fault tolerance. Ongoing maintenance of the Voicemail/Fax CT server is the customer's responsibility.

The Customer-provided Voicemail/Fax CT Server contains the following preconfigured elements:

• Intel machine with 2 CPUs, 6 GB RAM

• 2 Intel Dialogic D41/D82/T1 (dependent on Switch Type)

• 2 36 GB hard drives (RAID 1)

• Intel Dialogic

• System release 5.1.1 SP1 for Windows for Intel

• 1 Intel VFXJCT Fax Card

• Microsoft Windows 2000 SP4

• Microsoft Windows 2000 Resource Kit

• Intel NetMerge CCS 3.0 SP1

• Intel NetMerge Patches PTR29924, PTR30122, BZ955877, ANLOGSPP.exe

• Intel NetMerge NISList Utility

• Java Runtime Environment 1.3.1_03

• Oracle Voicemail & Fax 9.0.4

• Oracle9iAS Edition 9.0.2.0.0

Web Conferencing Conversion Server

A dedicated Web Conferencing Conversion Server is required by those Customers wishing to use the document conversion and voice streaming capabilities within Oracle Collaboration Suite's Web conferencing feature. At the protocol server's request, it also converts Microsoft documents to an efficient Web-streamable format.

The Web Conferencing Conversion server contains the following preconfigured elements:

• Intel machine with 2 CPUs, 6 GB RAM

• Intel Dialogic D24OJCT-T1 Telephony Card

• Microsoft Windows 2000 SP4

• Oracle Collaboration Suite 9.0.4.1

Voice Access Server

The Voice Access server is shared by multiple On Demand Customers and connects to a phone switch that provides voice access to text within Oracle Collaboration Suite, converting voice requests to HTML, and then reading the requested HTML page back to the user. This service can be shared by multiple environments and scaled independently.

The shared Voice Access Server contains the following preconfigured elements:

• Linux/Intel machine with 2 CPUs, 6 GB RAM

• 24-port Intel Dialogic Telephony Card

• Red Hat Linux Advanced Server 2.1 e.35

• VoiceGenie VoiceXML Gateway Server

• SpeechWorks OpenSpeech Recognizer

• SpeechWorks OpenSpeech DialogModules

• SpeechWorks Speechify TTS

• Intel Dialogic Voice Portal Reference System

Server Location

The following table summarizes the location for which the servers should be deployed and who is responsible for the acquisition and installation of hardware and any relevant third party software.

^Footnote 1 Server dedicated to each Customer
^Footnote 2 Server dedicated to each Customer
^Footnote 3 Common infrastructure servers processing multiple Customers
^Footnote 4 Server dedicated to each Customer
^Footnote 5 Common infrastructure servers processing multiple Customers

@Oracle

For @Oracle Customers, Oracle performs full online backups of the database, code tree, and archive logs. With the exception of Oracle Express Server, Oracle does not require that the system be unavailable in order to perform the backup. Oracle does not encrypt the backups on tape.

Table 6-1 details the Oracle standard online backup policy frequency and retention period and Table 6-2 specifies the online backup windows for specific regions.

^Footnote 1 Performed on production systems during the Production phase of the LifeCycle only.
^Footnote 2 Performed on non-production systems during the Implementation phase of the LifeCycle only. Performed on non-production systems during the Production phase of LifeCycle by request only.

For backups that are not specific to the Oracle On Demand LifeCycle, Table 6-3 details the Oracle backup policy frequency and retention periods for special backups.

@Oracle Customers may not purge any production data from their environment.

@Customer Recovery

Oracle will work with customer to facilitate data recovery from backup media in the event of a system failure or urgent data restoration request. Data restoration times will vary depending on the severity of the problem and backup tape location. It is the Customer's responsibility to provide the tape media from which oracle will restore the database.

@Oracle Recovery

Oracle will work with Customer to facilitate data recovery from disk or backup media in the event of a system failure or urgent data restoration request. The ability to recover to a point in time is limited by the retention times in Table 6-1. Data restoration times will vary depending on the severity of the problem and the location of the backup tape.

@Customer Backup

Oracle will provide a nightly, online backup of the Oracle database files to a standard location on a disk. These Oracle Database backups include the Oracle data files,control files, redo logs, and any necessary archive logs. These files are necessary for recovery of the Oracle database. Oracle backups do not include Oracle code tree,operating system, and any other code or files. Backups of these files are a Customer responsibility.

Customer is solely responsible for copying the Oracle database backups, Oracle code tree, operating system, customer-specific application files, and any other relevant files daily to a backup tape. Customer is solely responsible for all aspects of backup media management, offsite storage, archival, and retrieval.

Shared Link

A shared link is a connection between the Customer and Oracle that utilizes the Customer's existing ISP connection. The connection is used for Oracle traffic and the Customer's normal Internet activity.

Dedicated Link

A dedicated link is a connection between the Customer and Oracle that utilizes a dedicated ISP connection. The connection is used only for Oracle traffic. The Customer's other Internet activity uses a separate connection. A dedicated link can use an Authorized Network Provider (ANP) or another dedicated ISP circuit.

@Oracle Model

In the @Oracle model, Oracle provides data center hosting facilities and manages the server(s) housing the Customer's Oracle database and applications. A network link between Oracle's data center and the Customer site supports the transmission of application transaction traffic from the end user to the hosted servers. The basic offering contains one link (VPN) from a Customer location to the Oracle Data Center. Additional VPNs can be purchased.

The network link supports transaction traffic between end users and servers hosted at Oracle. An end user's experience will be affected by three network metrics: bandwidth, latency, and packet loss. Oracle's experience has shown that the following performance metrics can be used as a starting point for the Customer's network designs.

• Throughput equivalent to 2-12 kbps per user (see below for more details)

• Roundtrip latency less than 300 ms between Oracle and the Customer premise

• Packet Loss less than .1%

Oracle's ANPs can provide circuits with guaranteed latency to Oracle's Austin Data Center of < 100ms in the US and < 250ms from Europe.

Bandwidth requirements for the Oracle Collaboration Suite On Demand service will vary depending on which applications are used. Oracle's experience shows that the following metrics are a good starting point for network design. Actual network usage will vary depending on the Customers business and workflows.

• Oracle Email - 1-2 kbps per user

• Oracle Files Online - 10-12 kbps per user

• Oracle voicemail/fax - 10-12 kbps per user

• Oracle Web Conferencing - 18kbps per host, 6 kbps per user

The standard network connection is an Internet connection, which can be provided by an Oracle Authorized Network Provider (ANP) or an Internet Services Provider (ISP). Regardless of which connection option is chosen, Oracle requires the use of IPSec compliant VPN hardware to secure the data transmission over the network link.

The standard configurations for the VPN hardware are shown below. Although other configurations are technically feasible, Oracle has chosen these configurations to enhance security, performance and manageability.

Figure 6-4 illustrates an ANP link between Oracle and the Customer's premise. The ANP link uses a dedicated Internet connection for the VPN tunnel. The Oracle provided VPN device's remote interface is connected to the ANP provided router, and the local interface is connected to the Customer's external or DMZ firewall interface. The Customer configures their network to route application traffic for Oracle to the Oracle provided VPN device, which in turn sends the traffic through the VPN tunnel to Oracle. The Customer's normal Internet traffic uses the Customers existing Internet circuit.

Figure 6-5 illustrates a shared link connection using both interfaces on the Oracle provided VPN device. The remote interface is connected to the subnet between the Customers border router and firewall external interface. The local interface is connected to the Customers DMZ subnet. The Customer configures their network to route application traffic for Oracle to the Oracle provided VPN device local interface, which in turn sends the traffic through the VPN tunnel to Oracle. The Customer's normal Internet traffic bypasses the VPN device and is routed over the same Internet circuit.

Figure 6-6 illustrates a shared link connection using only the remote interface on the Oracle provided VPN device. The remote interface is connected to the subnet between the Customers border router and firewall external interface. The local interface is not used. The Customer configures their network to route application traffic for Oracle to the Oracle provided VPN device remote interface, which in turn sends the traffic through the VPN tunnel to Oracle. The Customer's normal Internet traffic bypasses the VPN device and is routed over the same Internet circuit.

To eliminate the risks associated with IP addressing conflicts, Oracle requires the use of globally unique public IP addresses registered through one of the following regional Internet registry organizations:

• Asia Pacific Network Information Center (APNIC)

• Réseaux IP Européens (RIPE)

• American Registry for Internet Numbers (ARIN)

Oracle will not support the use of private IP addresses in the following ranges:

• Class A: 10.0.0.0 - 10.255.255.255

• Class B: 172.16.0.0 - 172.31.255.255

• Class C: 192.168.0.0 - 192.168.255.255

@Customer Model

In the @Customer model, the server(s) housing the Customer's Oracle database and applications reside in the Customer's data center or a third party hosting site. A management link between the Customer's server and Oracle provides the connection for Oracle On Demand services. Oracle uses the management link to deliver remote monitoring and diagnostic services of Oracle systems by way of the Oracle Continuous Connection Network (OCCN).

The Oracle Continuous Connection Network (OCCN) is the foundation for the delivery of Oracle online support services. The OCCN comprises of access, tools, and connectivity solutions in a management framework that enables Oracle online support, consulting, and development organizations to provide remote support services and diagnostic capabilities to Customers for their Oracle databases and applications.

The standard network connection is an Internet connection, which an Oracle Authorized Network Provider (ANP) or an Internet Services Provider (ISP) can provide. Regardless of which connection option is chosen, Oracle requires the use of IPSec compliant VPN hardware to secure the data transmission over the network link.

The following figures illustrate the standard configurations for the VPN hardware. Although other configurations are technically feasible, Oracle chose these configurations to enhance security, performance, and manageability.

Figure 6-7 illustrates an ANP link between Oracle and the Customer's premise. The ANP link uses a dedicated Internet connection for the VPN tunnel. The Oracle provided VPN device's remote interface is connected to the ANP provided router, and the local interface is connected to the Customer's external or DMZ firewall interface. The Customer configures their network to route Oracle management traffic to the Oracle provided VPN device, which in turn sends the traffic through the VPN tunnel to Oracle. The Customer's normal Internet traffic uses the Customers existing Internet circuit.

Figure 6-8 illustrates a shared link connection using both interfaces on the Oracle provided VPN device. The remote interface is connected to the subnet between the Customers border router and firewall external interface. The local interface is connected to the Customers DMZ subnet. The Customer configures their network to route Oracle management traffic to the Oracle provided VPN device local interface, which in turn sends the traffic through the VPN tunnel to Oracle. The Customer's normal Internet traffic bypasses the VPN device and is routed over the same Internet circuit.

Figure 6-9 illustrates a shared link connection using only the remote interface on the Oracle provided VPN device. The remote interface is connected to the subnet between the Customers border router and firewall external interface. The local interface is not used. The Customer configures their network to route Oracle management traffic to the Oracle provided VPN device remote interface, which in turn sends the traffic through the VPN tunnel to Oracle. The Customer's normal Internet traffic bypasses the VPN device and is routed over the same Internet circuit.

To eliminate the risks associated with IP addressing conflicts, Oracle requires the use of globally unique public IP addresses registered through one of the following regional Internet registry organizations:

• Asia Pacific Network Information Center (APNIC)

• Réseaux IP Européens (RIPE)

• American Registry for Internet Numbers (ARIN)

Oracle will not support the use of private IP addresses in the following ranges:

• Class A: 10.0.0.0 - 10.255.255.255

• Class B: 172.16.0.0 - 172.31.255.255

• Class C: 192.168.0.0 - 192.168.255.255

Infrastructure Security Architecture Rules Sets

The default deny rules sets are enforced by Firewall Security Policy. Any potential violations of the predefined rules are monitored by a production quality Intrusion Detection System (IDS). In addition, periodic assessments of the environment are performed by an external assessment vendor. The results and recommendations provided are implemented where appropriate.

Intrusion Detection Systems (IDS) and Practice

The IDS system in use is designed to recognize intrusions in a number of ways such as identifying attack signatures as well as recognition of anomalous ports and protocols being accessed within the environment. Alerts, when generated, are routed to a 24x7 response desk that performs appropriate levels of triage and response, escalating to senior security engineers when necessary.

Firewall and VPN Requirements

All accesses into the environments must traverse a firewall that validates the appropriateness of the communications being attempted. It performs this validation through recognition of protocols being used as well as verifying the acceptability of ranges of source and destination IP addresses. Oracle utilizes Virtual Private Network (VPN) devices in a site-to-site, or more accurately stated network-to-network topology leveraging the most ubiquitous transport technology available today, the public Internet. Oracle requires the implementation of IPSec as part of an overall VPN strategy for securing data between endpoints on the management link, employing tunneling and encryption to facilitate data privacy.IPSec is a framework of open standards developed by the Internet Engineering Task Force (IETF) to, as the name implies, provide security for IP datagrams. It is a robust standard that withstood extensive peer review and emerged as the clear industry standard for Internet VPNs.Oracle pre-configures VPN devices to provide the following levels of encryption and authentication per the IPSec standard:

• Data is encrypted using 168-bit Triple Des

• The VPN is configured using Hashed Message Authentication Codes (HMAC) with a SHA-1 algorithm

The standard connection from the Customer to the Oracle data center is through an Oracle provided hardware VPN.

Access Controls

The Power Broker product from Symark Technologies is used to control, log, and audit all access to production systems by all Oracle personnel so that any changes or modifications to the Customer environment are strictly controlled. Power Broker is based on its policy configurations that allows or disallows the processing of programs on the system. The policy configuration file controls accesses via defined variables such as time of day, user id and system being accessed.

Local, National, and International Rules

• Local Carriers, Inter-Exchange Carriers, and the Telecommunications Industry

• At the Federal Level in the United States, the Federal Communications Commission's (FCC) Part 68 Rule provides regulations for connecting telecommunications wiring and Customer-provided equipment to the regulated networks

• Building codes and standards encompass most, if not all, aspects of the construction industry. Installation methods and electrical products must conform to local code requirements in the construction of telecommunication facilities.

Sample of Codes affecting the Telecommunication Facilities

• ASHRAE – American Society of Heat, Refrigeration, and Air Conditioning Engineers

• BICSI – Building Industry Consulting Service International

• CEC – Canadian Electrical Code

• CSA – Canadian Standards Association

• ISO/IEC 11801 International Standard – Information Technology – Generic cabling for Customer location

• NEC – National Electrical Code

• NFPA – National Fire Protection Association

• TIA/EIA – Telecommunications Building Wiring Standards

• UL – Underwriters Limited

Additional Code Provisions and Good Practices

• Air Plenums – Prohibit open wiring (except with listed low-smoke, flame retardant insulation) in spaces used for transport of environmental air in buildings

• Fire Stops – Properly seal all penetrations through fire-rated walls and floors with approved materials to reduce the chance of fire and smoke spread.

• Separation of Systems – Stipulate separation of system components and wiring between different classes of voltages. Adherence is important to help reduce the risk of accidental shock due to contact with dangerous voltage levels.

• Voltage Hazards – Provide outside protection from voltage hazards caused by contact between communications circuit elements and electrical system elements such as lighting strikes and induced voltage from close proximity to power circuits.

• Working Clearances – Provide clear space to safely service wiring and equipment throughout a building.

Equipment Room

A Telecommunications Equipment Room is a special-purpose room that provides space and maintains a suitable operating environment for telecommunications and/or computer equipment. Equipment Rooms may be connected to cable backbone pathways that run both within and between buildings. The equipment room must be dedicated solely to telecommunications and related equipment. Do not allow equipment that does not support the equipment room (for example, pipes, duct work, and distribution of building power) to be located in or pass through the equipment room.

• Equipment rooms typically have the following (Recommended):

  • Demarcation for Telecommunication Service Providers

  • Termination point for telephone/data station wiring

  • PBX Switch Equipment

  • Voice Mail Equipment

  • Inter-Building backbone cross-connects

  • Horizontal and Vertical cross-connects

  • Communications station racks and cabinets

  • Network LAN/WAN

  • Workstation(s) for telecommunications personnel

• Equipment rooms typically do not have the following:

  • White Noise generating systems

  • Paging Systems

  • Security Equipment

  • General Office Storage

• Equipment rooms should not have the following (not recommended):

  • Boiler Room Equipment

  • Drains and Clean Outs

  • Electrical Transformers and switch gear

  • Food and Drinks

  • Hydraulic equipment and other heavy machinery that causes vibration

  • Janitor's Closets

  • Loading Docks

  • Sources of excessive EMI and RFI

  • Steam Pipes

  • Storage Rooms

  • Washrooms

• Physical Characteristics

  The square footage allocated for this room shall be in proportion to the square feet of usable office space and the telecommunications/computer equipment required.

  • In general, telecommunications racks are preferred over equipment cabinets in dedicated telecommunications rooms. Designs should consider the types of equipment planned for the room, and future equipment requirements. Space should be allocated to accommodate (24Ó width by 30" depth) equipment cabinets installed in rows. It is recommended that equipment racks meet ANSI/EIA 310-D-1992: racks, panels and associated equipment.

  • It is recommended, that in a slab floor environment, Anti-Static Vinyl Coated Tile (VCT) flooring be installed.

  • Entry into telecommunications rooms should be secure, and auditable via a means as a card reader, or electronic key system

• Heating, Ventilation, and Air Conditioning (HVAC)

  • Telecommunications Racks will generate from 2500 to 5000 BTU each.

  • The HVAC shall maintain an ambient temperature between 65 & 75 degrees Fahrenheit, 24 hours per day 365 per year, and a relative humidity of 20% to 80%.

  • It is recommended that each telecommunications room have its own HVAC unit with alarm monitoring and reporting capability.

• Wall Fields/ Cable Termination

  A cable system is a part of the telecommunication distribution system that provides connection between telecommunications service entrance facilities, equipment rooms, telecommunication, server and storage equipment. Typical and recommended distribution cable shall be Category 5, 4 pair, 24 AWG, unshielded, solid conductor twisted pair and above.

  • It is recommended that all telecommunication wiring be installed by a Registered Communications Distribution Designer (RCDD), or BiCSi qualified cable installer.

  • It is recommended that all Category 5 distribution cables use 110 termination type blocks, and that all jumper cables use RJ-45 type terminating connectors.

  • Horizontal and Jumper Cable - The cable shall meet or exceed all requirements for Category 5 cable specified in ANSI/TIA/EIA-568-A of the CSA T529.

  • T1 Cable – It is recommended that each T1 circuit use conventional, 2 pair 22 to 24 AWG twisted shielded pairs, encapsulated in one dielectric sheath, to minimize the risk of electromagnetic interference (EMI) and radio frequency interference (RFI).

  • Wallfield/Rack Field/Distribution Frame – It is recommended that all building type telecommunications cable use a centralized point of termination. The centralized point of termination allows for cable to be terminated according to services and application. The point of cable termination may be attached to: a fire retardant piece of plywood attached to the wall, a cable distribution field located in an equipment rack, or free standing cable distribution frame.

• Electrical

  Telecommunications equipment is sensitive to power fluctuations. Because of this sensitivity, provisions should be made for: dedicated power feeds, individual branch circuits, back up power, grounding and bonding.

  • It is recommended that the equipment room have its own dedicated electrical sub-panel, but not required.

  • Power installed under raised floors should have e minimum of 6 ft. flexible conduit to allow for movement.

  • It is recommended that power be mounted on the cable trays/racks when installed above equipment. Typically each equipment rack requires a dedicated 20 amp duplex receptacle.

  • It is recommended that four convenience outlets be installed around the room (one on each wall).

  • Grounding and bonding provides safeguards for personnel, property, and equipment from foreign electrical voltages and currents. It is important for construction, electrical and cable contractors to provide proper grounding and bonding throughout the entire construction of a facility. At a minimum, all equipment racks, and telecommunication equipment must be grounded to prevent risk of electrocution to personnel.

• @Customer data center - "Must Have Requirements"

  • Equipment room

    • A special-purpose room or location that provides adequate space, and maintains a suitable operating environment for telecommunications racks and/or computer equipment.

    • A suitable equipment rack or equipment cabinet, with a writing shelf provided for VPN equipment placement.

    • An HVAC system that maintains an ambient temperature between 65 & 75 degrees Fahrenheit, 24 hours per day 365 per year, and a relative humidity of 20% to 80%.

    • Enforceable process by which entry into the telecommunications room shall be secure, and restricted to authorized personnel.

  • Cable, Termination/Electrical

    • A centralized point, and ease of access to cable termination for Service Provider Products (T1)

    • All equipment racks, and telecommunication equipment grounded to prevent risk of electrocution to personnel.

    • Two dedicated 20 amp duplex receptacles.