Purpose
hc.vsd - Queries and controls the hc daemon of the Recoverable Virtual Shared Disk subsystem.
Syntax
Flags
None.
Operands
The hc subsystem must be restarted for this operand to take effect
Once debugging is turned on and the hc subsystem has been restarted, hc.vsd trace should be issued to turn on tracing
Use this operand under the direction of your IBM service representative.
Note: the default when the node is booted is to have standard output and standard error routed to the console. If debugging is turned off, standard output and standard error will be routed to /dev/null and all further trace messages will be lost. You can determine if debug has been turned on by issuing hc.vsd qsrc. If debug has been turned on, the return value will be:
action = "2"
This operand is only meaningful after the debug operand has been used to send standard output and standard error to the console and the hc subsystem has been restarted.
Description
Use this command to display information about the hc subsystem and to change the status of the subsystem.
You can restart the hc subsystem with the IBM Virtual Shared Disk Perspective. Type spvsd and select actions for virtual shared disk nodes.
Exit Values
Security
You must have root privilege to issue the debug, mksrc, reset, start, and stop subcommands.
Implementation Specifics
This command is part of the IBM Recoverable Virtual Shared Disk option of PSSP.
Prerequisite Information
See PSSP: Managing Shared Disks
Location
/usr/lpp/csd/bin/hc.vsd
Related Information
Commands: ha_vsd, ha.vsd
Examples
To stop the hc subsystem and restart it, enter:
hc.vsd reset
The system returns the messages:
Waiting for the hc subsystem to exit. hc subsystem exited successfully. Starting hc subsystem. hc subsystem started PID=xxx.
Purpose
hmadm - Administers the Hardware Monitor daemon.
Syntax
hmadm [ {-d debug_flag} ... ] operation
Flags
Operands
The operation must be one of the following:
This operation must by invoked by the administrator after the administrator modifies the ACL configuration file.
Description
The hmadm command is used to administer the Hardware Monitor daemon. The Hardware Monitor daemon executes on the control workstation and is used to monitor and control the SP hardware. Five administrative actions are supported, as specified by the operation operand.
Normally when the daemon exits, it is automatically restarted by the system. If frame configuration information is changed, the quit operation can be used to update the system.
The daemon writes debug information and certain error information to its log file. The log file is located in /var/adm/SPlogs/spmon and its name is of the form hmlogfile.nnn, where nnn is the Julian date of the day the log file was opened by the daemon. The clog operation causes the daemon to close its current log file and create a new one using the name hmlogfilennn, where nnn is the current Julian date. If this name already exists, a name of the form hmlogfile.nnn_m is used, where m is a number picked to create a unique file name.
The s70 daemon writes debug information and certain error information to its log file. The log file is located in /var/adm/SPlogs/spmon/s70d and is of the form s70d.f.log.ddd, where f is the frame number, and ddd is the Julian date of the day the log was opened by the s70 daemon.
The hmadm clog operation causes the s70 daemon, as well as hardmon, to close its current log file and open a new one. For the s70 daemon the form of the new log file name is the same as the original log file unless that name already exists, in which case the form becomes s70d. f.log.ddd_n, where n is an incremental number picked to create a unique file name.
|The hmadm clog operation causes hardmon to close |its current log file and open a new one.
The following debug flags are supported by the daemon:
|
| debug_flag | hardmon | s70 | hmcd |
|---|---|---|---|
| all | Set/unsets all of hardmon's debug options | Sets/unsets all of s70d's debug options | Sets/unsets all of hmcd's debug options |
| acls | Logs the Access Control Lists | N/A | N/A |
| cmdq | Logs the contents of the internal queue of commands sent to the frames | N/A | N/A |
| cntrs | Logs the daemon (hardmon) internal counters | Logs the daemon (s70d) internal counters | Logs the daemon (hmc) internal counters |
| dcmds | Logs commands sent to the daemon (hardmon) | Logs commands sent to the daemon (s70d) | Logs commands sent to the daemon (hmc) |
| fcmds | Logs commands sent to the frame supervisors | Logs commands sent to the S70 hardware | Logs commands sent to the HMC |
| ipl | Logs interested party lists | N/A | N/A |
| memchk | Logs memory allocation data in hm_memory_dump | N/A | N/A |
| pckts | Logs packets received from the frame supervisors in hm_frame_packet_dump | Logs packets sent to hardmon in s70d.f.packet.dump where f is the frame number | Logs packets sent to hardmon in hmcd.[f].packet.dump |
| polla | Logs poll list array | N/A | N/A |
| rsps | Logs responses sent to clients in hm_response_dump | N/A | N/A |
| sami | N/A | Logs data sent to and received from the S70 Control Panel in s70d.f.sami_dump where f is the frame number | N/A |
| socb | Logs client socket session information. | N/A | N/A |
| s1data | Logs data sent to the S1 serial ports in hm_s1data_dump | Logs data sent to and received from the S70 serial port in s70d.f.s1data_dump where f is the frame number | Logs data sent to and received from the serial port in hmcd.f.n.s1data_dump |
| s1refs | Logs S1 serial port reference counts and connections | N/A | N/A |
| ttycb | Logs ttycb control blocks | N/A | N/A |
| tvars | Logs boundary values used in checking temperatures, amperages, and volts | N/A | N/A |
| java | N/A | N/A | HMCD.class logs specific status and exception information in hmcd[ipaddress].java_trace |
Security
This command uses the SP Hardware Monitor. To execute this command, users must be authorized to access the Hardware Monitor subsystem with administrative permission.
Location
/usr/lpp/ssp/bin/hmadm
Related Information
Commands: hmdceobj, hmckacls, hmgetacls
Files: /spdata/sys1/spmon/hmdceacls, /spdata/sys1/spmon/hmacls
Examples
hmadm -d socb setd
hmadm -d fcmds setd
To clear this debug flag, enter:
hmadm -d fcmds cleard
hmadm cleard
hmadm clog
hmadm quit
Purpose
hmckacls - Checks the existence of Hardware Monitor permissions.
Syntax
hmckacls [-f file_name] permission_string [slot_spec]
Flags
Operands
Description
The hmckacls command checks the existence of Hardware Monitor permissions that are associated with the specified hardware. The command returns 0 if the ACL(s) in the specified permission string exist for all of the slots contained in the target slot specification. It returns 1 if any of the ACLs do not exist in any one of the targets in the slot specification.
Exit Values
Location
/usr/lpp/ssp/bin/hmckacls
Related Information
Commands: lsauthts, chauthts, hmgetacls, hmdceobj
Files: /spdata/sys1/spmon/hmacls, /spdata/sys1/spmon/hmdceacls
Examples
In the following examples the same command (hmckacls 1:1) is issued four times; once for each of the possible authorization method configurations. The commands target is slot 1 in frame 1.
[/]> hmckacls vsmu 1:1 [/]> echo $? 0
[/]> hmckacls vsmu 1:1 [/]> echo $? 1
[/]> hmckacls vsmu 1:1 [/]> echo $? 0
If the user is root and on the control workstation, the return shows that the user can perform all of the actions:
[/]> hmckacls vsmu 1:1 [/]> echo $? 0
If the user is not root or not on the control workstation, the return shows that at least one of the permissions is not valid:
[/]> hmckacls vsmu 1:1 [/]> echo $? 1
Purpose
hmcmds - Controls the state of the SP hardware.
Syntax
Flags
Operands
Description
Use this command to control the state of the SP hardware. Control is provided via the Virtual Front Operator Panel (VFOP). VFOP is a set of commands that can be sent to the hardware components contained in one or more SP frames. Each frame consists of 18 slots, numbered 0 through 17, where slot 0 represents the frame itself, slot 17 can contain a switch and slots 1 through 16 can contain thin or wide processing nodes. Wide nodes occupy two slots and are addressed by the odd slot number. In a switch only frame, slots 1 through 16 can contain switches; the switches occupy two slots and are addressed by the even slot number.
Normally, commands are only sent to the hardware components in the current system partition. A system partition only contains processing nodes. The switches and the frames themselves are not contained in any system partition. To send VFOP commands to hardware components not in the current system partition or to any frame or switch, use the -G flag.
The following list describes the VFOP command set. Commands that require the -G flag are marked by an asterisk (*). Commands marked by a double asterisk (**) are primarily used by the Eclock command and are not intended for general use since an in-depth knowledge of switch clock topology is required to execute these commands in the proper sequence.
Before issuing these commands, refer to the "Using a switch" chapter in the PSSP: Administration Guide for detailed descriptions.
SP Switch
Any Frame, Node, or Switch that Supports Microcode Download
Any Node, with the exception of Node Expansion Nodes such as S70 and S80, which do not support normal, secure, or service.
Any Frame, with the exception of Node Expansion Nodes such as S70 and S80, which do not support setid.
Any Frame, Node, or Switch, with the exception of Node Expansion Frames such as S70 and S80, which do not support off, or on.
Any Node, or Switch, with the exception of Node Expansion Nodes such as S70 and S80, which do not support flash.
One of these commands must be specified using the command operand. The command is sent to the hardware specified by the slot_spec operands. However, the command is not sent to any hardware that is not in the current system partition unless the -G flag is specified. If the -G flag is not specified and the slot_spec operands specify no hardware in the current system partition, an error message is displayed.
The slot_spec operands are interpreted as slot ID specifications. A slot ID specification names one or more slots in one or more SP frames and it has either of two forms:
fidlist:sidlist or nodlist
where:
The first form specifies frame numbers and slot numbers. The second form specifies node numbers. A fval is a frame number or a range of frame numbers of the form a-b. A sval is a slot number from the set 0 through 17 or a range of slot numbers of the form a-b. A nval is a node number or a range of node numbers of the form a-b.
The relationship of node numbers to frame and slot numbers is shown in the following formula:
node_number = ((frame_number - 1) x 16) + slot_number
The following are some examples of slot ID specifications.
To specify slot 1 in frames 1 through 10, enter:
1-10:1
To specify frames 2, 4, 5, 6, and 7, enter:
2,4-7:0
To specify slots 9 through 16 in frame 5, enter:
5:9-16
If frame 5 contained wide nodes, the even slot numbers are ignored.
To specify specifies slots 1, 12, 13, 14, 15, and 16 in each of frames 3 and 4, enter:
3,4:1,12-16
To specify slot 17 in frame 4, enter:
4:17
To specify the nodes in slots 1 through 16 of frame 2, enter:
17-32
To specify the nodes in slot 1 of frame 1, slot 1 of frame 2 and slot 1 of frame 3, enter:
1,17,33
To specify the node in slot 6 of frame 1, enter:
6
Optionally, slot ID specifications can be provided in a file rather than as command operands. The file must contain one specification per line. The command requires that slot ID specifications be provided. If the command is to be sent to all SP hardware, the keyword all must be provided in lieu of the slot_spec operands. However, the all keyword can only be specified if the -G flag is specified and if the VFOP command is on or off, since on or off are the only commands common to all hardware components.
Commands sent to hardware for which they are not appropriate, or sent to hardware which does not exist, are silently ignored by the Hardware Monitor subsystem.
By default, and except for the reset, flash, and run_post commands, the hmcmds command does not terminate until the state of the hardware to which the command was sent matches the command or until 15 seconds have elapsed. If 15 seconds have elapsed, the hmcmds command terminates with a message stating the number of nodes whose state was expected to match the VFOP command sent and the number of nodes which actually are in that state. The state of hardware for which the VFOP command is inappropriate, or where the hardware does not exist, is ignored.
The hmcmds command fails if any of the hardware targeted is not supported by the version of PSSP on the machine where the command was issued.
Security
To execute the hmcmds command, the user must be authorized to access the Hardware Monitor subsystem and must be granted "VFOP" permission for the hardware objects (frames, slots) specified in the command. Commands sent to hardware objects for which the user does not have "VFOP" permission are ignored.
Location
/usr/lpp/ssp/bin/hmcmds
Related Information
Commands: hmdceobj, hmmon, spsvrmgr
Files: /spdata/sys1/spmon/hmdceacls, /spdata/sys1/spmon/hmacls
Examples
hmcmds -G off all
hmcmds secure 1-5:1-16
hmcmds -G extclk3 1-8:17
hmcmds normal 6 2,3:2
Purpose
hmdceobj - Adds, deletes and lists hardware monitor DCE objects.
Syntax
Flags
The permission list is a string of one or more of the following characters:
Operands
Description
Use the hmdceobj command to add and delete hardmon DCE objects. The DCE objects represent hardware that the hardware monitor is responsible for on an SP system. Access Control Lists (ACLs) can be associated with the objects to control access. The spacl command or RS6000/SP Security SMIT interface is used to change the ACLs associated with an existing object. Hardware monitor protected objects that may be added or deleted are:
The hardware objects are hierarchical. There is a system object (that cannot be added or deleted) that contains frame objects which contain slot objects (which represent nodes and switches). In checking for authorization, if a slot object exists the ACLs associated with it are used to determine access. If no slot object exists, ACLs for the frame object containing that slot will be checked if they exist. If the frame object doesn't exist, the system object is checked. The system object is the initial object in the system and must have a default ACL associated with it. If only one group of administrators will be responsible for the whole SP system, only the system object is required.
When an object is created the object will inherit the initial object or initial container ACLs of its container object (depending upon whether the object being created is a container itself). A slot is contained by its frame. If there is no existing object for its frame when a slot object is created, it will inherit the ACLs from the system object. If a group is specified on the hmdceobj command with the -n flag, that group is added to the default ACLs when the object is created.
Frame and slot objects are represented the same for the hmdceobj command as for the other hardmon commands (hmmon and hmcmds). Each frame consists of 18 slots, numbered 0 through 17, where slot 0 represents the frame itself, slot 17 can contain a switch, and slots 1 through 16 can contain thin or wide processing nodes. Wide nodes occupy two slots and are addressed by the odd slot number. In a switch only frame, slots 1 through 16 can contain switches; the switches occupy two slots and are addressed by the even slot number.
The hardware identifier operands are interpreted as slot ID specifications or node lists. A slot ID specification names one or more slots in one or more SP frames and it has the following form:
fidlist:sidlist
where:
fidlist = fval[,fval,...] sidlist = sval[,sval,...]
An fval is a frame number or a range of frame numbers of the form a-b. An sval is a slot number from the set 0 through 17 or a range of slot numbers of the form a-b.
The form for a node list is:
nodlist = nval[,nval,...]
An nval is a node number or a range of node numbers of the form a-b.
The following are some examples of slot ID specifications.
1-10:1
2,4-7:0
5:9-16
If frame 5 contained wide nodes, the even slot numbers are ignored.
3,4:1,12-16
4:17
17-32
1,17,33
6
Optionally, hardware identifiers can be provided in a file rather than as command operands. The file must contain one specification per line.
After creating objects, ACLs can be modified using the dcecp command or the RS6000/SP Security SMIT interface. A hardmon object will be represented by a string such as:
/.:/subsys/ssp/hardmon/{hostname}/{residual-part}
where /.:/subsys/ssp/{hostname}/hardmon is the CDS pathname for the hardmon daemon running on the SP system whose control workstation is identified by the specified DCE hostname. The hostname needs to be part of the database string since more than one SP system can be within the same DCE cell. The {residual-part} of the object string will be one of the following:
Files
/spdata/sys1/spmon/hmdceacls
Standard Error
This command writes all error messages to standard error.
Exit Values
Security
This command uses the SP Hardware Monitor. To execute this command, users must be authorized to access the Hardware Monitor subsystem with administrative permission.
Restrictions
This command is only used if DCE is used as an authentication method.
Implementation Specifics
This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP) ssp.clients file set.
Prerequisite Information
Refer to PSSP: Administration Guide for more information on DCE implementation on the SP.
Location
/usr/lpp/ssp/bin/hmdceobj
Related Information
Commands: spacl
Examples
hmdceobj 1:17
hmdceobj -d 1:17
hmdceobj -a -g monitor_only -p m 1,2:0
hmdceobj -q 0-3
Sample output:
system hardmon frame1 frame1/slot0 frame1/slot1 frame1/slot2 frame1/slot3
hmdceobj -r 0-3
Sample output:
- - 0xa17d - - 0xa17e 1 0 0xa175 1 1 0 0xa176 1 1 1 0xa176 1 1 2 0xa176 1 1 3 0xa176 1
hmdceobj -s 0-3
Sample output:
- - SystemHasObject TRUE 0xa17d System Object Exists - - HaclmonHasObject TRUE 0xa17e Hardmon Object Exists 1 0 FrameHasObject TRUE 0xa175 Frame Has Object 1 0 SlotHasObject TRUE 0xa176 Slot Has Object 1 1 SlotHasObject TRUE 0xa176 Slot Has Object 1 2 SlotHasObject TRUE 0xa176 Slot Has Object 1 3 SlotHasObject TRUE 0xa176 Slot Has Object