Central Data/Digi Dialog Controls
The EtherLite Terminal Servers from Central Data Corporation require some initial setup to work on the network. The following discussion explains the setup possibilities for Central Data connectivity.
Click Central Data Dialogto skip the network setup and go directly to the definition dialog.
The EtherLite TCP/IP terminal servers can work with Vantage in two ways depending on the needs of the installation. The servers can be set up either on the local/wide area network or on a second Network Interface Card (NIC) with hubs/repeaters attached to the secondary network.
The first method will accommodate an installation in which the resources to be managed are a great distance from the Vantage workstation. Console traffic of the resources connected to the terminal server is broadcast on the local/wide area network.
The second method can be used if it is desirable to keep console traffic off the local/wide area network and if the resources to be connected are within 500 meters of the Vantage workstation. This method has the advantages of reducing vulnerability to network outages and of reducing wide/local area network traffic.
Ports on the EtherLite terminal servers are accessed via device files on the Vantage workstation. The workstation acts as the bootp server and runs a demon to control each EtherLite server.
EtherLite Installation Pre-requisites
· The following are pre-requisites for installation of EtherLite Terminal Servers:
· The workstation's operating system must be running a version of HP-UX 9.05 through 10.20.
· A kernel with the current Central Data/Digi Drivers must be built. (Currently 4.015)
· If a secondary NIC will be installed the Vantage workstation must have an available ESIA slot.
· The following questions will be asked during the installation.
· Will the Vantage workstation run the driver code for the terminal server?
· Will the Vantage workstation act as the bootp server?
· What is the model of the terminal server being added?
· What is the IP address for the terminal server?
· What is the subnet mask for the terminal server? (Default subnet mask is 255.255.255.0)
· What is the hardware address of the terminal server? (This information can be located on the rear or the bottom of the server)
· What is the IP address of any gateway (if any) between the Vantage workstation and the terminal server?
Installing EtherLite on Local/Wide Area Network
The following steps will install an EtherLite terminal server on the local/wide area network. Included are steps to build the appropriate kernel:
1. su to root and execute the program /etc/dmesg to determine if the Central Data/Digi objects are in the kernel. If a line similar to the following appears it indicates that the driver objects are in the kernel: Central Data scsiTerminal/EtherLite(R) Driver R4.015 for HP-UX 10.20, major=75 If this line is in the dmesg output it is not necessary to build a kernel and you can skip the kernel build step.
2. To build a kernel mount the Vantage cdrom and execute /drivers/Central_Data/cdupdate The code will ask if an EtherLite unit is to be added. If the server to be added now respond yes and answer the questions as outlined previously. A reboot may be necessary in order to load the new kernel.
3. If an EtherLite unit is to be added and the appropriate kernel is already in place, su to root and execute /Central_Data/ver4.015/sts/Install.ether
4. Next, use the Resource Definition dialog to configure an EtherLite resource. The device file must be built in order for the daemon to start.
5. The daemon that runs the EtherLite units will be started automatically on reboot. The daemon can be started manually by executing /usr/lbin/cdetherd [EtherLite unit #, i.e els0, els1, etc.] [EtherLite unit ip address] &
6. The terminal server can now be put on the network and powered up. Attempt to ping the server before starting resources connected to the EtherLite server.
Installing EtherLite on Secondary NIC
The previous steps should be performed as appropriate to ensure that the Central Data software drivers are in the kernel and that the EtherLite units to be added have a bootp server from which to receive their ip address.
1. Install the Interphase card in an available EISA slot according to the manufacturers instructions.
2. Connect the Interphase card to the network.
3. To install the software driver login as root, mount the Vantage cdrom, execute /usr/sbin/swinstall and enter /drivers/InterPhase/ss00306-a01_tar as the Source Depot Path.
4. Highlight the Interphase EISA 10/100BaseT Driver fileset and select Install.
5. Respond Yes to begin the installation and again to build a new kernel.
6. Reboot the system.
7. Run lanscan. If the MAC address for the ife device shows 0x000000000 reboot the system.
8. Start SAM. Select Networking and Communications then select Network Interface Cards.
9. Click to select the Interphase card, click the Actions control, select configure and assign the IP address and subnet mask to the card.
10. Reboot the system
11. Run ifconfig to verify the IP address and subnet mask (i.e. ifconfig ife1).
12. Ping the IP address of the card.
13. Connect an appropriate length of straight through network cable to the RJ-45 jack from the Interphase card to an available port on the hub. To cascade hubs connect the network cable from the first hub to port "x" on the next hub in the chain. The distance between primary and secondary hub must not exceed 100 meters. The total number of hubs must not exceed 4 and the total number of segments must not exceed 5. See your hub's documentation for more information.
14. Once the hubs are in place an appropriate length of straight through cable can be connected from an available port on the hub to an available port on the EtherLite unit.
15. Once connected to the net the EtherLite unit can be powered up and should receive its ip address from the bootp server. Remember that the resource must be defined in Vantage before an attempt is made to start the daemon. (See instructions for adding EtherLite unit to wide/local area network)
The figure below is the Central Data connectivity Definition dialog.
Central Data/Digi Definition Dialog
Refer to Using Vantage Dialogs to learn about Vantage dialogs. Each control on the dialog is explained in the text that follows.
Central Data/Digi Dialog Controls
Server:
Required. This control is used to tell Vantage the model of Central Data scsiTerminal Server that will connect the resource to Vantage. Click to select a value other than the default.
· 1002+ Server, 2 Port(Default)
· 1008+ Server, 8 Port
· 1016 Server, 16 Port
· 2001/2008+ Server, 8 Port
· 1400 Server, 4 Port
· 1800+ Server, 8 Port
· EL8P TCP/IP Server, 8 Port
· EL16 TCP/IP Server, 16 Port
· EL32 TCP/IP Server, 32 Port
Serial Port:
Required. The Serial Port control is used to configure the physical port to which the managed resource will be connected. The control will allow selection of a specific range of ports depending on which server is clicked in the Server control. Click to select the serial port to which the resource will be connected.
SCSI Address:
Required. This group of controls is used to tell Vantage the SCSI address that was assigned to the scsiTerminal Server to which the resource will be connected. Click to select a value other than the default.
0(Default) -1 -2 -3 -4 -5 -6
FASlink:
Required. (2001/2008+ server only) This control configures the FASlink address for ST-2008+(s). Each St-2008 on the daisy chain must have its own unique FASlink address (0 for the first ST-2008, 1 for the second etc.) This control is enabled only if the 2001/2008+ server selection is clicked in the Server control. Click to select a value other than the default.
n/a(Default) -0 -1 -2 -3 -4 -5 -6
· 1002+ Serial Port - 1/2
· 1008+ Serial Port - 1/8
· 1016 Serial Port - 1/16
· 2001/2008+ Serial Port - 1/8
· 1400 Serial Port - 1/4
· 1800+ Serial Port - 1/8
· EL8P TCP/IP Port - 1/8
· EL16 TCP/IP Port - 1/16
· EL32 TCP/IP Port - 1/32
EtherLite Unit:
Required. (EtherLite servers only) Use this control to select the EtherLite unit number. The first unit added is unit 0. Subsequent units should be numbered 1 through f. Click to select a value other than the default.
Baud Rate:
Required. Use this control to configure the baud rate of the port being configured. The baud rate on the Central Data/Digi port must match the baud rate of the resource's console port. Click to select a value other than the default.
38400 19200 9600(Default) 4800 2400 1200 300
Parity/Data/Stop:
Required. This control is used to configure the parity and number of data and stop bits to be used on the serial port. The values must match the values of the console port on the resource to be connected. Click to select a value other than the default.
None,8,1(Default) Even,7,0 Odd,7,0
Serial Protocol:
Default is vsld. The default setting is recommended. Click to choose a value other than the default.
Enq-Ack:
Default is Disabled. Click Enabled if the resource requires Enq-Ack protocol.
Tilde Character:
Default is Disabled. Click Enabled if the resource requires the tilde character to be sent through. Typically Solaris resources required the tilde to be enabled to send a break to the resource.
Catwalk Initial State:
This control enables setting the initial state of the Catwalk 3.0 hardware-the state that the Catwalk hardware should be in when the resource is started. Initial state should be set only if Catwalk 3.0 hardware is connected. Click to select a value other than the default.
Click OK when all selections are complete. Click the Add button on the Resource Definition dialog to add the resource.
