Connectivity diagram call out
Description
D
Gigabit Ethernet ports (built-in)
E (optional)
SAS to SAS cable (0.5 meters) — customer provided
F
Customer supplied CAT 5 Ethernet cable (minimum
10 feet, 3 meters)
K (optional)
Tape drive and AC power cord — customer provided
Support for KVM and headless CMS systems
CMS servers are shipped without a keyboard, video monitor, or mouse (KVM). Customers are
expected to have a lab set of these (commonly known as a crash cart) available for technical
support.
Linux-based CMS servers do
not
have a GUI console. The console is text-based only. KVM systems
typically seem to work fine with the Linux-based systems. However, use of a KVM or crash cart is a
customer responsibility.
Connecting to external interfaces
This section describes the external interfaces that connect to the CMS server.
Connecting the switch link
The CMS server uses TCP/IP over a LAN to connect to the Communication Manager switch. One
CMS server can collect data from eight Communication Manager switches. To the CMS server,
each Communication Manager switch represents one Automatic Call Distribution (ACD) switch.
Important:
You must use Ethernet port 1 for the switch connection.
For more information about how to connect and administer the Communication Manager switch link,
see
Avaya Call Management System Switch Connections, Administration, and Troubleshooting
.
Connecting to the customer network
The CMS server has built-in Ethernet ports that support network speeds of 10/100/1000 Mbps.
However, for CMS installations, you must use only speeds of 10/100 Mbps. The customer network
Ethernet connection is used for CMS Supervisor, network printers, and LAN backup.
Support for KVM and headless CMS systems
July 2016
Avaya CMS HPE DL20 G9 and DL380 G9 HIMT
25
