HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 107

Running qsnetstat

Get HP Cluster Platform Interconnects v2010 PDF manuals and user guides View all HP Cluster Platform Interconnects v2010 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 107 highlights

You can also select interconnects to test by specifying their name, as follows: cp6000sms# /usr/bin/qsnetstat QR0N00 QR0N01 The qsnetstat script checks the environment data on each interconnect. In federated interconnects, the qsnetstat script also verifies for each rail the consistency of the clock source and the software revision of the interconnects. The command parser reads the interconnect module names from the /etc/hosts file and communicates directly with the swmserver daemons for each interconnect to determine the state of the interconnect. The system impact from running this script is not significant, enabling you to run the qsnetstat script without impact on a production system. The following component status is tested: • Controller card. • Fans • Power supply units • Clock source • Firmware • Error registers Typical problems found include the following: • Incorrect IP or hostnames in the /etc/hosts file or in the supplied argument list. • Incorrect firmware version on the controller card. • Problems with the IP address of the controller card. • Problems with the Ethernet cable connected to the controller card. • Problems with environment conditions (such as temperature and fan speeds) on the interconnects themselves. The following sections describe how to run the script and interpret its output. 12.2.1.1 Running qsnetstat Run the qsnetstat script with the -h option to display help information, as follows: # qsnetstat -h Usage: qsnetstat -hvlwtsfdm:R: switch_module -h prints this info -v verbose mode -l loop and resample errors -f sample frequency in seconds (default 10) -m machine_name machine database to use -d use database to get module descriptions -w use weighted list - most serious error first -t 'top' style display (implies weighted list order) -s use error summary -R rail id= network rail to use Typical command output, truncated for ease of reference, is as follows: # qsnetstat -ltws -Switch Module State Name IPAddr Type Build Clock PSU FanSpd Temp QR1N00 192.168.180.1 QS2_64U64D 42-4022508 A/656 O/O OOOOOO 25'C QR1N01 192.168.180.2 QS2_64U64D 42-4022508 A/656 O/O OOOOOO 24'C . . . Maintenance and Diagnostic Procedures 12-5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
You can also select interconnects to test by specifying their name, as follows:
cp6000sms#
/usr/bin/qsnetstat QR0N00 QR0N01
The
qsnetstat
script checks the environment data on each interconnect. In
federated interconnects, the
qsnetstat
script also verifies for each rail the
consistency of the clock source and the software revision of the interconnects. The
command parser reads the interconnect module names from the
/etc/hosts
file
and communicates directly with the
swmserver
daemons for each interconnect to
determine the state of the interconnect.
The system impact from running this script is not significant, enabling you to
run the
qsnetstat
script without impact on a production system. The following
component status is tested:
•
Controller card.
•
Fans
•
Power supply units
•
Clock source
•
Firmware
•
Error registers
Typical problems found include the following:
•
Incorrect IP or hostnames in the
/etc/hosts
file or in the supplied argument
list.
•
Incorrect firmware version on the controller card.
•
Problems with the IP address of the controller card.
•
Problems with the Ethernet cable connected to the controller card.
•
Problems with environment conditions (such as temperature and fan speeds)
on the interconnects themselves.
The following sections describe how to run the script and interpret its output.
12.2.1.1
Running qsnetstat
Run the qsnetstat script with the -h option to display help information, as follows:
#
qsnetstat -h
Usage: qsnetstat -hvlwtsfdm:R:
switch_module
-h prints this info
-v verbose mode
-l loop and resample errors
-f sample frequency in seconds (default 10)
-m
machine_name
machine database to use
-d use database to get module descriptions
-w use weighted list - most serious error first
-t ’top’ style display (implies weighted list order)
-s use error summary
-R
rail id=
network rail to use
Typical command output, truncated for ease of reference, is as follows:
#
qsnetstat -ltws
-Switch Module State--------------------------------------------
Name
IPAddr
Type
Build
Clock PSU FanSpd Temp
QR1N00 192.168.180.1 QS2_64U64D 42-4022508 A/656 O/O OOOOOO 25’C
QR1N01 192.168.180.2 QS2_64U64D 42-4022508 A/656 O/O OOOOOO 24’C
.
. <display truncated>
.
Maintenance and Diagnostic Procedures
12-5