IG Node Command List

1 Overview

This module describes how to verify communication between the IG Node and the DARC Node..After verifying that communication exists between the IG Node and the DARC Node, RAC diagnostics for each IG Node may be performed. Memory size is important and may be checked; however, exact memory values expected are not discussed as this memory size value may change over time and with different types of IG Nodes offered. It is currently (July, 2006) around 2 GBytes for Main memory. Application software can be started to verify that Image Generation is running, which assists in determining if the IG Node(s) is up (as we determine up and ready for recon). Refer to the System Diagrams (block diagrams) to understand connections between Nodes. Refer to the Command List to determine which commands can be performed. Additional information has been supplied for specific command outputs.

All IG Nodes must be power cycled with the DARC Node running and booted up (rsh is successful on DARC). This is performed with Apps down. The IG Node should be successfully able to perform the rsh command. If this fails, reinitialize (power cycle) the specific IG Node. To determine issues with IG Nodes, refer to the Command List and at the DARC Node perform cd /var/log and then more messages. Before replacing any IG Node, copy the DARC Node var log (relevant date and time) and include this log with the defective part.

note:

For All-In-One Console, There is no DARC node presence. CDIP card and scan data disks are mounted in Host computer. All the commands ran on DARC node will be ran on Host computer.

For AIO console, maximum one IG is supported.

For AIO console, we can telnet to IG from Host Computer with the same command.

2 Command List

`{ctuser@darc} or [root@darc]` `ifconfig`	This command allows the user to determine what the DARC Node understands in relation to the Ethernet Address / port for a specific IG Node (IG Node1, 2 and 3). When a IG Node is configured /acitive in the system, look for Running.
`[root@darc]` `ipmitool -I lan -H ig# -A NONE chassis power status`	The ipmitool may be available. This command allows the user to determine what the DARC Node understands in relation to the power state for a specific IG Node (for ig# insert 1, 2 or 3 as applicable). The telnet command or the service igpower# start command will allow the user to apply power to the IG Node from a Unix Shell. Refer to Usage Examples, for help.
`[root@darc]` `service igpower# start`	This command allows the user to turn on power to a specific IG Node (for ig# insert 1, 2 or 3 as applicable). The power cord must be inserted and AC Power must be good. The Ethernet cable must be routed between the DARC Node and IG Node correctly and must be in good (working) condition.
`[root@darc]` `service igpower# stop`	This command allows the user to turn off power to a specific IG Node (for ig# insert 1, 2 or 3 as applicable). The power cord must be inserted and AC Power must be good. The Ethernet cable must be routed between the DARC Node and IG Node correctly and must be in good (working) condition.
`[root@darc]` `service cliservice start`	Restarts or verifies the cliservice dpcproxy server is running on the DARC Node to allow for Serial Over LAN (SOL). Returning message will be either: “The dpcproxy is running” or “dpcproxy cliservice has been restarted”
`{ctuser@darc} or [root@darc]` `telnet localhost 623` `Server: ig1 (or ig2 or ig3)` `Username:` Enter `Password:` Enter `Login successful` `dpccli> exit`	After rsh to darc this verifies dpcproxy server running / SOL jconnection for a specific IG Node
`{ctuser@darc} or [root@darc]` `ping ig#`	Performed from the DARC Node for ig1, ig2, or ig3 Select Ctrl+C to stop the ping process OS and Apps software must be loaded on the DARC Node for ping to be successful.
`{ctuser@darc} or [root@darc]` `rsh ig#`	Performed from the DARC Node for ig1, ig2, or ig3 OS and Apps software must be loaded on the DARC Node for rsh to be successful.
`{ctuser@darc} or [root@darc]` `cd /var/log` `more messages`	This IG Node status log can assist in determining issues (used in conjunction with the log on the DARC Node).
`{ctuser@darc} or [root@darc]` `telnet localhost 623` `Server: ig1 (or ig2 or ig3)` `Username:` <Enter> `Password:` <Enter> `Login successful` `dpccli> help`	After rsh to darc this verifies dpcproxy server running / SOL connection. Show the help menu for commands / options.
`{ctuser@darc} or [root@darc]` `telnet localhost 623` `Server: ig1 (or ig2 or ig3)` `Username:` <Enter> `Password:` <Enter> `Login successful` `dpccli> reset` `dpccli> console`	After rsh to darc this verifies dpcproxy server running / SOL connection. The SOL CD may need to be loaded into the DARC if SOL issues exist. Resets the IG Node. This command depends on the software release. Try `reset -c` for older versions of software (pre 06MW03.x).
`{ctuser@darc} or [root@darc]` `telnet localhost 623` `Server: ig1 (or ig2 or ig3)` `Username:` <Enter> `Password:` <Enter> `Login successful` `dpccli> console`	After rsh to darc this verifies dpcproxy server running / SOL connection. Lists the IG Node information and current OS and kernel information.
`{ctuser@darc} or [root@darc]` `telnet localhost 623` `Server: ig1 (or ig2 or ig3)` `Username:` <Enter> `Password:` <Enter> `Login successful` `dpccli> sensors -v`	After rsh to darc this verifies dpcproxy server running / SOL connection. Lists if power is on or off and last or current voltage/temperature/fan information for the IG Node. This command depends on the software release. Try `sens -v` for older versions of software (pre 06MW03.x).
`{ctuser@ig#} or [root@ig#]` `lhinv`	Lists devices and memory.
`{ctuser@ig#} or [root@ig#]` `lhinv \| grep Main`	Lists memory size (2048).
`{ctuser@ig#} or [root@ig#]` `cat /proc/driver/gemsrac`	Shows status and existence of a specific IG Node rac.
`[root@darc]` `rsh ig#` `[root@ig#]` `lsmod \| grep rac`	Checking the existence of a RAC (recon accelerator card) in a specific IG Node. The output of this command will display “rac” (ignore any numbers in the output string), if the RAC is seen.
`{ctuser@hostname}` `racdiags`	Performs rac (recon accelerator card) diagnostics on up to 3 IG Nodes from ctuser on the Host computer with Application Software Down (preferably when performed remotely). Alternate command is `racdiags 1` for a single IG Node Operator Console. It has been reported that racdiags may hang when running. Try the racbist command.
`{ctuser@ig#} or [root@ig#]` `uname -a`	Displays kernel name, hostname, kernel release and version, machine hardware name, hardware platform.
`{ctuser@ig#} or [root@ig#]` `free -m`	Does not adequately display IG Node total memory information but does display used memory.
`{ctuser@ig#} or [root@ig#]` `cat /proc/meminfo`	Displays detailed memory information.
`df -h`	Displays partition information.
`{ctuser@ig#} or [root@ig#]` `cat /proc/devices`	Lists all devices detected by the system's Node.
`[root@ig#]` `dmidecode \| less`	Shows the IG Node version of Motherboard.
`[root@ig#]` `dmidecode \| grep -i version`	Shows IG Node BIOS version as loaded by the vendor.
`[root@ig#]` `ps -leaf \| grep -v grep \| grep image_generation`	With APPS Up ONLY - provides a clue that recon is up and running on the specific IG Node (do not perform this command on the DARC Node - the DARC Node information is not properly updated). Refer to Usage Examples, for help..
`[root@darc]` `ethtool -p eth#` (Ctrl-C to stop)	For an Ethernet cabling connection issue or a bad DARC NIC issue, use the command 'ethtool -p eth#' (where # represents the Ethernet address) as root. If the Ethernet cable is good and correctly connected from the Host Computer to the DARC Node, and the DARC NIC port is good, then the port will blink or flash when activated. Ctrl-C will stop the test. To find the associated IG Node Ethernet address, perform the ifconfig command on the Host Computer
{ctuser@darc} ipmitool -I lan -H ig1 -P “” sel	Basic comm. over SOL, and log status.
{ctuser@darc} ipmitool -H ig1 -P '' chassis power status	Check chassis power behavior at boot.
{ctuser@darc} ipmitool -H ig1 -P '' fru	Lists board components.
{ctuser@darc} ipmitool -H ig1 -P '' sdr type temp	Component temperature checks.
{ctuser@darc} ipmitool -H ig1 -P '' sel list last 15	Lists all board sensors. Many details. Look for OKs.
{ctuser@darc} ipmitool -H ig1 -P '' sdr	Simplified board sensors. Look for OKs.
[root@ig#] dmidecode\|grep -i vers	Returns a Version string which contains WV for Westville, JR for Jarrell.

3 Usage Examples

3.1 ipmitool

{ctuser@ hostname } su -

Password: #bigguy

[root@ hostname ]# rsh darc

Last login: Mon Aug 6 19:35:00 from oc

You have new mail.

[root@darc ~]# ipmitool -I lan -H ig1 -A NONE chassis power status

Chassis Power is on

[root@darc ~]# ipmitool -I lan -H ig1 -A NONE chassis power status

Chassis Power is off

[root@darc ~]# service igpower1 start

Starting ig1: [ OK ]

To remove power to the chassis, perform the following command:

[root@darc ~]# service igpower1 stop

Stopping ig1: [ OK ]

3.2 image_generation (Apps Up)

ctuser@ig1: ps –leaf | grep –v grep | grep image_generation

4 S ctuser     767   766  0  81   0 -  1143 rt_sig 14:52 ?        00:00:00 csh -c
image_generation -bp 0 -host darc -node 1 -vrac 0

0 S ctuser     785   767  0  75   0 - 48692 -      14:52 ?        00:00:00
image_generation -bp 0 -ho st darc -node 1 -vrac 0

4 IG Node dpcproxy cliservice Verification

          {ctuser@hostname} su -
Password: <password>
[root@hostname]# telnet localhost 623
Trying 127.0.0.1...
Failed to connect to localhost.
[root@hostname]# rsh darc
Last login: Mon Aug  6 19:35:00 from oc
You have new mail.
[root@darc ~]# ps -aef |grep dpcproxy
root      3836  3817  0 15:07 pts/10   00:00:00 grep dpcproxy

note:

If the /usr/local/cli/dpcproxy information is not displayed then restart the cliservice. .

Alternate command: ps -aef | grep –v grep | grep dpcproxy

When this command is performed (ignore grep) then there will not be any output at all if the dpcproxy server is not running

          [root@darc ~]# /etc/rc.d/init.d/cliservice
[root@darc ~]# service cliservice start
The dpcproxy is running
dpcproxy cliservice has been restarted
[root@darc ~]# ps -aef |grep dpcproxy
root      2891     1  0 14:51 ?        00:00:00 /usr/local/cli/dpcproxy
root      3836  3817  0 15:07 pts/10   00:00:00 grep dpcproxy

5 IG Node Ping and Remote Shell

This subsection will verify the IG Node can be communicated too or pinged via the DARC Node. After verifying the ping communication line exists between the specific IG Node and the DARC Node a remote shell will be invoked to determine if the specific IG Node is up. This can be performed as ctuser or as root (not insight).

Open a Unix Shell and type the following:

          {ctuser@hostname} su -
Password: <password>
[root@hostname]# rsh darc
Last login: Mon Aug  6 19:35:00 from oc
You have new mail.
[root@darc ~]# ping ig1 (or ig2 or ig3 as applicable)
PING ig1 (10.0.1.2) from (10.0.1.1): 56(84) bytes of data.
64 bytes from ig1 (10.0.1.2) icmp_seq=1 ttl=64 time=0.157 ms
64 bytes from ig1 (10.0.1.2) icmp_seq=2 ttl=64 time=0.209 ms
64 bytes from ig1 (10.0.1.2) icmp_seq=3 ttl=64 time=0.175 ms
64 bytes from ig1 (10.0.1.2) icmp_seq=4 ttl=64 time=0.134 ms

Select: Control-C to stop the ping

--- ig1 ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 3000ms
rtt min/avg/max/mdev = 0.134/0.168/0.209/0.031 ms

[root@darc ~]$ rsh ig1

(ignore the following messages)

          connect to address 10.0.1.2: Connection refused
Trying krb4 rlogin...
connect to address 10.0.1.2: Connection refused
trying normal rlogin (/usr/bin/rlogin)
Last login: Mon Aug  6 19:35:00 from darc
[root@ig1 ~] exit
logout
rlogin: connection closed.
[root@darc ~] exit
logout
rlogin: connection closed.
[root@hostname]#

6 DARC Node ifconfig Verification

This subsection will confirm the DARC Node address and the DARC Node Subnet address. Specific sites may require changing the DARC Subnet to a 169 base address due to a Hospital Backbone conflict with the 172.16.0.x base address. This 172 base address is the default. It is loaded onto the Host and DARC Node during the Load From Cold software installation process unless the DARC Subnet box is selected and the alternate address supplied is inserted.

note:

Remember to resave the System State Reconfig Info File whenever the DARC Subnet address is modified.

DEFAULT DARC Subnet address: inet addr: 172 16.0.2 Bcast: 172.16.0.255 Mast: 255.255.255.0

ALTERNATE DARC Subnet address:

inet addr: 169.254.0.2 Bcast: 169.254.0.255 Mast: 255.255.255.0

7 DARC Node ifconfig Running and Address Verification

          {ctuser@hostname} su -
Password: <password>
[root@hostname]# rsh darc
Last login: Mon Aug  6 19:35:00 from oc
You have new mail.
[root@darc ~]# ifconfig

note:

The eth2 inet addr and Bcast may be different for specific sites that have experienced a 172.16.0.x HOSPITAL Backbone conflict. These specific sites will have a specific 169.254.0.2 address.

          eth0      Link encap:Ethernet  HWaddr 00:04:23:CA:7E:B8
eth0      inet addr:10.0.2.1  Bcast:10.0.2.255  Mask:255.255.255.0
IG2       inet6 addr: fe80::204:23ff:feca:7eb8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:166057 errors:0 dropped:0 overruns:0 frame:0
          TX packets:146124 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:32397595 (30.8 Mb)  TX bytes:91184965 (86.9 Mb)
          Base address:0xc400 Memory:cfe80000-cfea0000

eth1      Link encap:Ethernet  HWaddr 00:04:23:CA:7E:B9
IG1       inet addr:10.0.1.1  Bcast:10.0.1.255  Mask:255.255.255.0
          inet6 addr: fe80::204:23ff:feca:7eb9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:164105 errors:0 dropped:0 overruns:0 frame:0
          TX packets:141147 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:31762737 (30.2 Mb)  TX bytes:84167297 (80.2 Mb)
          Base address:0xc480 Memory:cfea0000-cfec0000

          eth2      Link encap:Ethernet  HWaddr 00:04:23:BB:DB:EC
eth2      inet addr:172.16.0.2  Bcast:172.16.0.255  Mask:255.255.255.0
DARC      inet6 addr: fe80::204:23ff:febb:dbec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:89484 errors:0 dropped:0 overruns:0 frame:0
          TX packets:121201 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15385255 (14.6 Mb)  TX bytes:13943296 (13.2 Mb)
          Base address:0xdc00 Memory:cffa0000-cffc0000

eth3      Link encap:Ethernet  HWaddr 00:04:23:BB:DB:ED
IG3       inet addr:10.0.3.1  Bcast:10.0.3.255  Mask:255.255.255.0
          inet6 addr: fe80::204:23ff:febb:dbed/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:152621 errors:0 dropped:0 overruns:0 frame:0
          TX packets:118265 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28314323 (27.0 Mb)  TX bytes:55007399 (52.4 Mb)
          Base address:0xdc80 Memory:cffe0000-d0000000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:101274 errors:0 dropped:0 overruns:0 frame:0
          TX packets:101274 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5267464 (5.0 Mb)  TX bytes:5267464 (5.0 Mb)

Following is an example output of ifconfig ran on Host computer of All-in-one Console. For AIO console, IG node is connected to Host Computer.

{ctuser@hostname}ifconfig

          eth0      Link encap:Ethernet  HWaddr 00:1B:21:02:18:E4
(IG Node) inet addr:10.0.1.1  Bcast:10.0.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:21ff:fe02:18e4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:425 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:27200 (26.5 KiB)  TX bytes:492 (492.0 b)
          Base address:0x2400 Memory:f2180000-f21a0000

eth1      Link encap:Ethernet  HWaddr 00:1B:21:02:18:E5
          inet addr:192.9.220.1  Bcast:192.9.220.255  Mask:255.255.255.0
          inet6 addr: fe80::21b:21ff:fe02:18e5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3788 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3758 errors:0 dropped:0 overruns:0 carrier:0
          collisions:36 txqueuelen:10
          RX bytes:646931 (631.7 KiB)  TX bytes:492127 (480.5 KiB)
          Base address:0x2440 Memory:f21a0000-f21c0000

          eth2      Link encap:Ethernet  HWaddr 00:0E:0C:AA:52:4E
          inet addr:3.36.231.122  Bcast:3.36.231.255  Mask:255.255.252.0
          inet6 addr: fe80::20e:cff:feaa:524e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11874 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2090 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:3014106 (2.8 MiB)  TX bytes:234499 (229.0 KiB)
          Base address:0x2480 Memory:f21c0000-f21e0000

eth3      Link encap:Ethernet  HWaddr 00:0E:0C:AA:52:4F
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0x24c0 Memory:f21e0000-f2200000

eth4      Link encap:Ethernet  HWaddr 00:1A:4B:54:94:9D
          inet addr:10.44.22.20  Bcast:10.44.22.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:177

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:103607 errors:0 dropped:0 overruns:0 frame:0
          TX packets:103607 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:101229370 (96.5 MiB)  TX bytes:101229370 (96.5 MiB)

8 dpccli Help Menu

          dpccli> help
    alarm -q { -g <id> [ -o <id> ] [-a <id> ] } | { -l <severity> } | -p
    alarm -s -a <id> -l <severity>
    alarm -c { -g <id> [ -o <id> ] [-a <id> ] } | { -l <severity> } | all
    boot -s normal | service [-f] [-console]
    clear
    clearlog
    commit
    console
    displaylog [-F csv|hex|dsv] [-O filename] [-n <num>]
    exit
    quit
    get -T <target> <options>
    help [-C <command>]
    id
    identify [-on [<seconds>]] [-off]

    identify -s
    interrupt -i nonmask [-console]
    power { -on [-console] } | -off
    power -state
    reset [-console]
    sensors [-v] [-F csv|dsv] [-f ok|nc|cr|nr|us] [-T volt|temp|power|fan]
    service { console | exit | ftp { start | stop } }
    set -T <target> <options>
    shutdown [-f] [-r]
    version