HP Cluster Platform Interconnects v2010 Quadrics QsNetII Interconnect - Page 128

Using the qsctrl Command

Page 128 highlights

connectivity table. Database content is based upon the current interconnect module description or from command line arguments. You can also use this command to create a report on the network state compared to the database. The system impact is very low because the processes only manipulate database entries on one of the management nodes. The qsdiagadm command usage is as follows: # qsdiagadm -h Usage: qsdiagadm [-fhv][-c type][-d database][-m name][-n ns] [-r rails][-t ts] Flags: -c type create a diags database for a given network type -d name specify an alternate diags database (defaults to qsdiagshost:qsnet) -f force database drop/delete -m name specify the machine name -n ns number of node-level interconnects (defaults to max) -r rails number of rails (defaults to 1) -t ts number of top-level interconnects (defaults to max) -v verbose The default diags database is named qsdiagshost:qsnet, a database named qsnet on the server qsdiagshost. If the RMS database is in use, you must specify it the first time you use any database access tools. You can determine the cluster name by using the rmsquery command on the management node as follows: # rmsquery -v sql> select * from attributes where name='name' name val name atlas sql> quit The cluster name is shown in the val column of the output. For a cluster called cp6000 the specified database should be qsdiagshost:rms_cp6000. Supported network types are: QMS64, QMF256 and QMF1024 or you can use the -n and -t options to specify the number of interconnects in your system. System names are assumed to be a short character string and node names are constructed from the system name and the Elan id of the node. Specify sets of nodes by using a range string. For example m, m0 and m[0-1023]. The qsdiagadm command builds a description of the system, creating tables in the database and populating them according to the type of network specified. Other diagnostic commands can use this information to check or change the state of the network. When you have built the database, you can use the qsdiagadm command with no arguments to display a diagnostic history of the system. 12.15 Using the qsctrl Command Use the qsctrl command to perform the following tasks: • Verify the switch card population of an interconnect, its network attributes, and the status of installed modules such as the fan tray. • In a federated network, verify the consistency of the interconnect controller firmware. • Modify the network state to temporarily configure a link out of the network. 12-26 Maintenance and Diagnostic Procedures

  • 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

connectivity table. Database content is based upon the current interconnect module
description or from command line arguments. You can also use this command to
create a report on the network state compared to the database.
The system impact is very low because the processes only manipulate database
entries on one of the management nodes.
The
qsdiagadm
command usage is as follows:
#
qsdiagadm -h
Usage: qsdiagadm [-fhv][-c type][-d database][-m name][-n ns]
[-r rails][-t ts]
Flags:
-c type create a diags database for a given network type
-d name specify an alternate diags database
(defaults to qsdiagshost:qsnet)
-f force database drop/delete
-m name specify the machine name
-n ns number of node-level interconnects (defaults to max)
-r rails number of rails (defaults to 1)
-t ts number of top-level interconnects (defaults to max)
-v verbose
The default
diags
database is named
qsdiagshost:qsnet
, a database named
qsnet
on the server
qsdiagshost
. If the RMS database is in use, you must specify
it the first time you use any database access tools. You can determine the cluster
name by using the
rmsquery
command on the management node as follows:
#
rmsquery -v
sql> select * from attributes where name=’name’
name val
--------------
name atlas
sql> quit
The cluster name is shown in the
val
column of the output. For a cluster called
cp6000 the specified database should be
qsdiagshost:rms_cp6000
.
Supported network types are: QMS64, QMF256 and QMF1024 or you can use the
-n
and
-t
options to specify the number of interconnects in your system. System
names are assumed to be a short character string and node names are constructed
from the system name and the Elan id of the node. Specify sets of nodes by using
a range string. For example
m
,
m0
and
m[0-1023]
.
The
qsdiagadm
command builds a description of the system, creating tables in the
database and populating them according to the type of network specified. Other
diagnostic commands can use this information to check or change the state of the
network. When you have built the database, you can use the
qsdiagadm
command
with no arguments to display a diagnostic history of the system.
12.15 Using the qsctrl Command
Use the
qsctrl
command to perform the following tasks:
Verify the switch card population of an interconnect, its network attributes,
and the status of installed modules such as the fan tray.
In a federated network, verify the consistency of the interconnect controller
firmware.
Modify the network state to temporarily configure a link out of the network.
12-26
Maintenance and Diagnostic Procedures