Setup guide

6-38
EPC Connecting Guide
CBLG179–1900
Cable, RJ45 Ethernet for HUB connection 10m 1
VCW3630 Cable, Ethernet ”Thin” (15M, 15F) to
Transceiver
5m 1
Examples of Use
The PowerConsole with the Cluster Assistant GUI is a cluster administration graphics
workstation which is available to setup, install, manage, and service the EPC nodes and the
EPC cluster.
The PowerConsole hardware is an S100 workstation running AIX 4.3.2. Escala S100
running AIX 4.3.1 was the previous AIX stations used as PowerConsole hardware.
CAUTION:
The AIX release of the PowerConsole must be higher or identical to the AIX release of
any Escala EPC node.
The PowerConsole needs a Cluster Administration Hub (10 mbps)for setting up a
dedicated–administration network. A Console Concentrator is used by default in any
configuration. RS232 cables can also be used on the one hand to connect a modem for
remote maintenance purpose, and on the other hand to establish a remote asynchronous
connection via RTC.
Cabling to Console Concentrator and Cluster Administration Hub will be set in
manufacturing. An Ethernet board (LSA board on an EPC800 node, integrated card on an
EPC400 node) is used to connect a node to the Cluster hub. It is mandatory to connect the
integrated Ethernet 10M/Bsec port of an EPC400 CPU drawer to the Cluster Hub (do not
connect a PCI Ethernet adapter 10/100 mbps to the hub). This is required for enabling
network boot of an EPC400 node from the PowerConsole (NIM tool).
There is an optional extra communication board (FDDI, Ethernet or Token-ring adapter) that
can be ordered to allow the PowerConsole to be connected to the customer’s LAN network.
This option is mandatory with NetBackup software, if there is a dedicated administration
network. With that option, an X–Terminal attached to the customer’s network can remotely
access to the PowerConsole, provided that it is configured to run with the CDE windows
manager of the PowerConsole.
If there is no Cluster Administration Hub, that is to say no dedicated administration network,
the Console Concentrator and the PowerConsole will be connected to the customer’s LAN
network (it must be an Ethernet network @ 10Mbps) in customer’s premises. An Ethernet
cable (VCW3630) is provided for doing this.
If the customer’s network is COAXIAL THICK or COAXIAL THIN then the Customer is in
charge of connecting the Console Concentrator and the PowerConsole to his network with
his own cables (As usual for all the Escala platforms).
As an alternative, the PowerConsole can be connected to the Console Concentrator. To do
this, you must order an additional CBLG161-1900 (Ethernet cross-over cable RJ45/RJ45)
and use the TCP10 transceiver on the Console Concentrator end. In that case, the
PowerConsole must also be connected to the customer’s network which requires an
appropriate extra communication board in the PowerConsole configuration. A shortcoming
of such a configuration is that the distributed version of Navisphere (full version with a key)
for managing the DAS full fibre disk subsystem cannot operate from the PowerConsole.
Figures 25 & 26 illustrate the two possible implementations – with or without Cluster
administration hub. In the former case, the nodes, the PowerConsole and the Console
concentrator are linked to the Cluster Administration Hub to make an independent Ethernet
network, said the dedicated–administration network. In the second case, the PowerConsole
and the Console Concentrator are directly connected to the customer’s Ethernet network.
Remind that in both case, the Escala EPC nodes are connected to the customer’s LAN
network.