Visara Master Console Center Installation - Manual (Page 33)

Chapter 5 Connectivity Interfaces
Installation Preparation Guide 33
Cabling Requirements
Each console or session to be interfaced to the MCC must have TCP/IP
link installed from the point of origin to the MCC server. The point of
origin may be, for example, a 3174, an HP-9000 server, or some other
TCP/IP controlled device. Examples of consoles include:
ƒ A hardware management console, to select an LPAR to IPL, for
SAD display, etc.
ƒ A system console, to monitor a system’s activity and messages.
ƒ A VTAM console, for access to TSO, IMS, IDMS, CICS, etc.
ƒ A UNIX console, to BOOT and/or monitor a system’s activity and
messages.
ƒ A managed network switch or remote power device, for monitoring
and control of other functions.
Examples of acceptable console interface cables are:
ƒ Coax cable run from 3174/3274 ports.
ƒ Coax cable run from a mainframe hardware, and/or system console
port.
ƒ TCP/IP cable run from a UNIX server.
ƒ A network cable for TELNET and/or Browser access.
All cables should have at least four (4) feet of slack at the MCC rack
location (measured vertically up from the floor). For correct installation
and proper management, all cables MUST be identified and labeled with
a unique identification scheme. The scheme can be as simple as a unique
number for each cable. Many customers utilize a combination of system
name, console id, and/or system port.
Note: Failure to install and test the Interface Cabling prior to
arrival of the MCC equipment will delay the MCC
installation. Coax should be tested using “live” 327x
consoles/printers. TELNET connections should be tested
with TELNET or PING commands.