This section is a quick and dirty guide to configuring modules for basic
operation. It is potentially useful during VACM installation. Please
refer to the real module documentation for further information on configuring
and testing these mdoules.
To configure node www for management via EMP, you must know the address of the
device
to which the EMP port for this node is physically connected. This can be
a serial port, like /dev/ttyS0, or a network address
and port of the form 192.168.1.1-911. The following example assumes a serial
port at ttyS1. In a typical setup,
such as this example, the password should be set to NONE.
The password must correspond with the EMP access password in the Bios.
A proper configuration command such as the following will
result in this output.
vash$ ipc localhost emp:configuration:www:/dev/ttyS1:NONE
EMP:18:JOB_STARTED
EMP:18:STATUS:ENGAGING
EMP:18:STATUS:PROTOCOL_DETECTED
EMP:18:STATUS:CONNECTION_ACCEPTED
EMP:18:STATUS:DOWNLOADING_FRU
EMP:18:STATUS:DOWNLOADING_SDR
EMP:18:STATUS:DOWNLOADING_SEL
EMP:18:JOB_COMPLETED |
The following IPC responses indicate an authentication failure. Make sure that
the password entered is consistent with the EMP password settings in the
Bios. A new configuration command can be sent to update an incorrect setting.
EMP:19:JOB_STARTED
EMP:19:STATUS:ENGAGING
EMP:19:STATUS:PROTOCOL_DETECTED
EMP:19:STATUS:CONNECTION_DENIED
EMP:19:JOB_COMPLETED |
Output such as the following indicates that Nexxus is trying to configure a
port which is not speaking the EMP protocol. Check the cabling and ensure
you are attempting to engage on the correct port and that the port is set up
for EMP in the Bios.
EMP:20:JOB_STARTED
EMP:20:STATUS:ENGAGING
EMP:20:STATUS:PROTOCOL_UNAVAILABLE
EMP:20:JOB_COMPLETED |
VA 1000 nodes are clustered by joining the nodes with a dedicated
management bus. The nodes determine their addresses dynamically, so a
special start-up procedure is required the first time you power up the
cluster. Appendix C explains the procedure required to configure and
power up a cluster for the first time.
To configure VA 1000 nodes under VACM, you must know the address of
each node on the cluster management bus (CMBus). These addresses are
determined automatically when power is applied to each node for the
first time. To determine the address of a node, use the following procedure:
Press and hold the Power switch down for at least 5 seconds.
Release the Power switch.
The two rightmost LED's will flash once, indicating the start
of the CMBus address transmission.
The three rightmost LED's will flash individually to indicate the CMBus
address. From left to right, the LED's represent 100's, 10's, and 1's
of the address.
Finally, the two rightmost LED's blink together once more
to indicate the end of the address transmission.
A proper configuration command results in the following output:
vash$ ipc localhost va1000:configuration:www:26
VA1000:3:JOB_STARTED
VA1000:3:JOB_COMPLETED |
Please be advised that the RSH protocol is not very secure. Using this module
on a publicly accessible network such as the internet is not recommended.
That being said, RSH can be very useful. Configuring a node for rsh is a two
step process. To configure the RSH module for node www send the following
command.
vash$ ipc localhost rsh:configuration:www:rsh:root
RSH:21:JOB_STARTED
RSH:21:JOB_COMPLETED |
On the node itself, edit the file /root/.rhosts and add this line.
Set the permissions on the file to 600.
To configure a nexxus for serial console access to www, send the following
ipc message. This example assumes the console of node www is attached
to /dev/ttyS0 and a baud rate of 19200bps.
vash$ ipc localhost sercon:configuration:www:/dev/ttyS0:19200
SERCON:22:JOB_STARTED
SERCON:22:JOB_COMPLETED |
By default, console access will only be available during the post boot sequence.
Further configuration is required to support full serial console access.
To redirect OS console messages on the remote node through a serial console:
[root@www]# cd /dev
[root@www]# rm -f console tty0
[root@www]# mknod -m 622 console c 5 1
[root@www]# mknod -m 622 tty0 c 4 0 |
In the globals section of /etc/lilo.conf add the following:
In the kernel section of /etc/lilo.conf add the following:
append="console=ttyS0,19200" |
Run lilo to activate the new settings.
To enable a getty for the serial port add the following to /etc/inittab:
s0:12345:respawn:/sbin/mingetty ttyS0 DT19200 vt100 |
Remove /etc/ioctl.save:
bash# rm -f /etc/ioctl.save |
Add the following line to /etc/securetty to permit root logins over the
serial port:
vacm_sys_statd must be installed and started on each node
to be monitored. Upon starting vacm_sys_statd for the first time, you will be
prompted to set a password. Remember this password as you will need to supply
it when you configure the nexxus portion of sysstat.
vash$ ipc localhost sysstat:configuration:www1:p4ssw0rd
SYSSTAT:7:JOB_STARTED
SYSSTAT:7:JOB_COMPLETED |
Test the sysstat module:
vash$ ipc localhost sysstat:WHO:www1
SYSSTAT:8:JOB_STARTED
SYSSTAT:8:WHO:zsprackett:tty1
SYSSTAT:8:WHO:zsprackett:pts/2
SYSSTAT:8:JOB_COMPLETED |
To configure a baytech power strip, first add a node:
vash$ ipc localhost nexxus:node_add:bt:webservers
NEXXUS:16:JOB_STARTED
NEXXUS:16:JOB_COMPLETED |
Next, configure the BAYTECH module for the new node:
vash$ ipc localhost baytech:configuration:bt:/dev/ttyS3
NEXXUS:17:JOB_STARTED
NEXXUS:17:JOB_COMPLETED |
To configure a VA100, first add a node:
vash$ ipc localhost nexxus:node_add:va100:webservers
NEXXUS:16:JOB_STARTED
NEXXUS:16:JOB_COMPLETED |
Configure the nodes IP address:
vash$ ipc localhost nexxus:set_var:va100:ip_address:192.168.1.2
NEXXUS:16:JOB_STARTED
NEXXUS:16:JOB_COMPLETED |
Next, configure the VASENET module for the new node:
vash$ ipc localhost vasenet:configuration:va100:master:abcdefgh
NEXXUS:17:JOB_STARTED
NEXXUS:17:JOB_COMPLETED |
Nodes must now be created for each nanoprobe based system:
vash$ ipc localhost nexxus:node_add:nano1:webservers
NEXXUS:16:JOB_STARTED
NEXXUS:16:JOB_COMPLETED |
To configure the nanoprobe based systems, you need to know the name of the
VA100 controller as well as the nodes vasenet address:
vash$ ipc localhost vasenet:configuration:nano1:va100:010203
NEXXUS:17:JOB_STARTED
NEXXUS:17:JOB_COMPLETED |
To configure an sbt2 based system, first add a node:
vash$ ipc localhost nexxus:node_add:tupelo:webservers
NEXXUS:16:JOB_STARTED
NEXXUS:16:JOB_COMPLETED |
Next, configure the SBT2 module for the new node:
vash$ ipc localhost sbt2:configuration:tupelo:/dev/ttyS4
NEXXUS:17:JOB_STARTED
NEXXUS:17:JOB_COMPLETED |
To configure a quanta based system, first add a node:
vash$ ipc localhost nexxus:node_add:quantabox:webservers
NEXXUS:16:JOB_STARTED
NEXXUS:16:JOB_COMPLETED |
Next, configure the Quanta module for the new node:
vash$ ipc localhost quanta:configuration:quantabox:/dev/ttyS5
NEXXUS:17:JOB_STARTED
NEXXUS:17:JOB_COMPLETED |