Command and Technical Reference, Volume 1

Eannotator

Purpose

Eannotator - Annotates the connection labels in the topology file.

Syntax

|Eannotator: |[-h] [-p |{0|1|all}] {-F |input_file | -d} -f |output_file |
|: |-O [yes | no]

Flags

-h: Displays usage information.
-d: Specifies that the topology filename is to be determined from the contents of the SDR, based on the number and type of switches in the system. On an SP Switch system, this flag is only valid on a system which has not been partitioned.
-F: Specifies the topology input file.
-f: Specifies the topology output file.
-O: Specifies whether to save the output file to the System Data Repository (SDR) or to the current directory. yes saves the output file to the SDR via the Etopology command. no saves the output file to the current directory. |
|-p {0|1|all}: |Specifies for which switch plane the operation is to be performed. |If not specified, the default is to perform the operation for all valid switch |planes. This flag is valid only on systems with SP Switch2 |switches.

Operands

None.

Description

This command supports all of the following:

The SP Switch
The SP Switch-8
The SP Switch2

This command must be executed whenever a new topology file is selected.

The topology file contains node-to-switch or switch-to-switch cable information. A node-to-switch connection looks like following:

s 25 2 tb0 17 0     E2-S00-BH-J16 to E2-N2

The predefined node-to-switch connections start with an "s" which indicates a switch connection. The next two digits, in this case "25" indicate the switch (2) and switch chip (5) being connected. The next digit, in this case "2", indicates the switch chip port in the connection. The next field, in this case "tb0", specifies the type of adapter present in the SP node. The following field, in this case "17", is the switch node number for the SP node, and the last digit, in this case "0", indicates the adapter port within the connection.

For switch-to-switch connections, the first four fields (switch indicator, switch, switch chip, and switch chip port) are repeated to identify the other end of the connection.

The connection label "E2-S00-BH-J16 to E2-N2" provides physical connection information for a customer's use to identify the problem connection.

Depending on the customer's physical switch frame configuration defined in the SDR, the Eannotator command retrieves switch node and dependent node objects from the SDR and applies proper connection information to the topology file.

If the input topology file contains existing connection information, the Eannotator command replaces the existing connection label with the new connection labels. If the input topology file does not contain connection labels, the Eannotator command appends the proper connection label to each line on the topology file.

The precoded connection labels on the topology file start with an "L" which indicate logical frames. The Eannotator command replaces the "L" character with an "E" which indicates physical frames. The "S" character indicates which slot the switch occupies in the frame, the "BH" characters indicate a Bulk Head connection, the "J" character indicates which jack provides the connection from the switch board, the "N" character indicates the node being connected to the switch, and the "SC" characters indicate the Switch Chip connection.

If you have a partitioned system and need to do a reannotate, you will need to make sure that you are reannotating the correct topology file.

Make sure you are in the correct partition first by exporting the correct partition name. For example:
```
export SP_NAME=partition_name
```
Run Etopology to get the correct topology file. For example:
```
Etopology -read /tmp/temporary.top
```
Run Eannotator with option -O yes to save output file to the SDR via the Etopology command. For example:
```
Eannotator -F /tmp/temporary.top -f /tmp/expected.top.annotate -O yes
```

If you have a multiplane system, make sure that you reannotate the correct plane's topology file.

Files

/etc/SP/expected.top.1nsb_8.0isb.0: The standard topology file for systems with a maximum of eight nodes.
/etc/SP/expected.top.1nsb.0isb.0: The standard topology file for one NSB system or a maximum of 16 nodes.
/etc/SP/expected.top.2nsb.0isb.0: The standard topology file for two NSB systems or a maximum of 32 nodes.
/etc/SP/expected.top.3nsb.0isb.0: The standard topology file for three NSB systems or a maximum of 48 nodes.
/etc/SP/expected.top.4nsb.0isb.0: The standard topology file for four NSB systems or a maximum of 64 nodes.
/etc/SP/expected.top.5nsb.0isb.0: The standard topology file for five NSB systems or a maximum of 80 nodes.
/etc/SP/expected.top.5nsb.4isb.0: The standard topology file for five NSB and four ISB systems or a maximum of 80 nodes. This is an advantage-type network with a higher bisectional bandwidth.
/etc/SP/expected.top.6nsb.4isb.0: The standard topology file for six NSB and four ISB systems or a maximum of 96 nodes.
/etc/SP/expected.top.7nsb.4isb.0: The standard topology file for seven NSB and four ISB systems or a maximum of 112 nodes.
/etc/SP/expected.top.8nsb.4isb.0: The standard topology file for eight NSB and four ISB systems or a maximum of 128 nodes.
/etc/SP/expected.top.1nsb_8.0isb.1: The standard topology file for systems with an SP Switch-8 and a maximum of eight nodes.

|Environment Variables

|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.

|To determine whether you are using either AIX rsh or rcp |or the secure remote command and copy method, the following environment |variables are used. |If no environment variables are set, the defaults are |/bin/rsh and /bin/rcp.

|You must be careful to keep these environment variables consistent. |If setting the variables, all three should be set. The DSH_REMOTE_CMD |and REMOTE_COPY_CMD executables should be kept consistent with the choice of |the remote command method in RCMD_PGM: |

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run Eannotator using a secure remote |method, enter:

|export RCMD_PGM=secrshell
|export DSH_REMOTE_CMD=/bin/ssh
|export REMOTE_COPY_CMD=/bin/scp

Security

You must have root privilege to run this command.

Location

/usr/lpp/ssp/bin/Eannotator

Related Information

Commands: Eclock, Efence, Eprimary, Equiesce, Estart, Etopology, Eunfence, Eupartition

Refer to IBM RS/6000 SP: Planning, Volume 2, Control Workstation and Software Environment for details about system partition topology files.

Examples

The following are the topology file entries before and after the Eannotator command executes:

For the SP Switch:
 
Before:
 
s 15 3 tb3 0 0 L01-S00-BH-J18 to L01-N1
 
After:
 
s 15 3 tb3 0 0 E01-S17-BH-J18 to E01-N1
 
For the SP Switch2:
 
Before:
 
s 15 3 tb3 0 0 L01-S00-BH-J18 to L01-N1
 
After:
 
s 15 3 xxx x x E01-S17-BH-J18 to E01-N1

Note:: Logical frame L01 is defined as physical frame 1 in the SDR Switch object.

|For both the SP Switch and the SP Switch2:
| 
|Before:
| 
|s 10016 0 s 51 3 L09-S1-BH-J20 to L05-S00-BH-J19
| 
|After:
| 
|s 10016 0 s 51 3 E10-S1-BH-J20 to E05-S17-BH-J19

Note:: Logical frame L09 is defined as physical frame 10 in the SDR Switch object.

|For the SP Switch:
| 
|Before:
| 
|s 15 3 tb0 0 0 L03-S00-BH-J18 to L03-N3
| 
|After:
| 
|s 15 3 tb3 0 0 E03-S17-BH-J18 to E03-N3 # Dependent Node

Note:: Logical frame L03 is defined as physical frame 3 in the SDR Switch object and the node was determined to be a dependent node.

|To annotate a topology file for a 128-way SP system with eight Node |Switch Boards (NSBs) and four Intermediate Switch Boards (ISBs) and to save |the output file in the current directory, enter:
```
|Eannotator -F /etc/SP/expected.top.8nsb.4isb.0 -f expected.top -O no
```
|To annotate an SP Switch2 system with a system-determined topology |file, enter:
```
|Eannotator -d -f /etc/SP/expected.top -O yes
```
|To annotate a topology file for a 16-way SP system with one NSB and |no ISBs and to save the output file in the SDR via the Etopology |command, enter:
```
|Eannotator -F /etc/SP/expected.top.1nsb.0isb.0 -f expected.top -O yes
```
To reannotate a partitioned system, you will need to get the correct topology file from the Etopology command.
1. Make sure you are in the correct partition first by exporting the correct partition name:
```
export SP_NAME=partition_name
```
2. Run Etopology to get the correct topology file:
```
Etopology -read /tmp/temporary.top
```
3. Run Eannotator with the -O yes option to save the output file to the SDR via the Etopology command:
```
Eannotator -F /tmp/temporary.top -f /tmp/expected.top.annotate -O yes
```
|To annotate only the second switch plane on an SP Switch2 system for |a 16-way plane with one NSB and no ISBs and to save the output file in the SDR |via the Etopology command, enter:
```
|Eannotator -F /etc/SP/expected.top.1nsb.0isb.0 \
|           -f expected.top -O yes -p 1
```

Eclock

Purpose

Eclock - Controls the clock source for each switch board within an SP cluster.

Syntax

Eclock: [-f Eclock_topology_file] | [-a Eclock_topology_file] | [-r] | [ -d] |
: [-s switch_number -m mux_value] | [-c Eclock_topology_file]

Flags

-f Eclock_topology_file

Specifies the file name of the clock topology file containing the initial switch clock input values for all switches in the system.

-a Eclock_topology_file

Uses the alternate Eclock topology specified in the given clock topology file.

-r

Extracts the clock topology file information from the System Data Repository (SDR) and initializes the switch clock inputs for all switches in the system.

-d

Detects the switch configuration, automatically selects the clock topology file, and initializes the switch clock inputs for all switches in the system.

-s switch_number -m mux_value

Sets an individual switch (switch_number) clock multiplexor (mux) value (mux_value)

where:

switch_number

Specifies the switch number.

mux_value

Specifies a flag with one of the following values:

0: Use the internal oscillator (make this frame the master frame).
1: Use input 1 (clock input from jack 3) (NSBs or ISBs).
2: Use input 2 (clock input from jack 4) (NSBs or ISBs).
3: Use clock input from jack 5 (NSBs or ISBs).
4: Use clock input from jack 4 (NSBs or ISBs).
5: Use clock input from jack 5 (NSBs or ISBs).
6: Use clock input from jack 6 (NSBs or ISBs).
7: Use clock input from jack 7 (ISBs only).
8: Use clock input from jack 8 (ISBs only).
9: Use clock input from jack 9 (ISBs only).
10: Use clock input from jack 10 (ISBs only).
27: Use clock input from jack 27 (NSBs or ISBs).
28: Use clock input from jack 28 (NSBs or ISBs).
29: Use clock input from jack 29 (NSBs or ISBs).
30: Use clock input from jack 30 (NSBs or ISBs).
31: Use clock input from jack 31 (ISBs only).
32: Use clock input from jack 32 (ISBs only).
33: Use clock input from jack 33 (ISBs only).
34: Use clock input from jack 34 (ISBs only).

-c Eclock_topology_file

Creates a new clock topology file from the data in the SDR.

If a flag is not specified, the clock input values stored in the SDR are displayed.

Operands

None.

Description

Note:: This command is not valid on a system with an SP Switch2 switch.

Use this command to set the multiplexors that control the clocking at each switch board within the configuration. One switch board within the configuration is designated as the "Master" switch that provides the clocking signal for all other switch boards within the configuration. The Eclock command reads clock topology information from either the file specified on the command line or the clock topology data within the SDR. If a clock topology file was specified, the Eclock command places the clock topology information into the SDR, so that it can be accessed again during a subsequent Eclock invocation. After processing the clock topology file, Eclock causes the new clock topology to take effect for the switches specified. A clock topology file contains the following information for each switch board within the cluster:

A switch board number.
A flag indicating the clock source for the switch within the frame. The flag can have any of the following settings:

0
Use the internal oscillator (make this frame the master frame).
1
Use input 1 (clock input from jack 3) (NSBs or ISBs).
2
Use input 2 (clock input from jack 4) (NSBs or ISBs).
3
Use clock input from jack 5 (NSBs or ISBs).
4
Use clock input from jack 4 (NSBs or ISBs).
5
Use clock input from jack 5 (NSBs or ISBs).
6
Use clock input from jack 6 (NSBs or ISBs).
7
Use clock input from jack 7 (ISBs only).
8
Use clock input from jack 8 (ISBs only).
9
Use clock input from jack 9 (ISBs only).
10
Use clock input from jack 10 (ISBs only).
27
Use clock input from jack 27 (NSBs or ISBs).
28
Use clock input from jack 28 (NSBs or ISBs).
29
Use clock input from jack 29 (NSBs or ISBs).
30
Use clock input from jack 30 (NSBs or ISBs).
31
Use clock input from jack 31 (ISBs only).
32
Use clock input from jack 32 (ISBs only).
33
Use clock input from jack 33 (ISBs only).
34
Use clock input from jack 34 (ISBs only).
The receiving jack number (xx if this switch board is the master).
The switch board number providing the clocking signal (zero if this switch board is the master).
The clock source jack number.
An alternate clock source (mux) value.
The alternate clock receiver jack number.
The switch board number providing the alternate clock source (mux) value.
The alternate sending jack number (xx if this switch board is the master).

SP Switch Warning

If Eclock is run to change the clock multiplexor settings while the switch is operational, you will experience css outages until a subsequent Estart is completed. If you run Eclock and specify the -f, -a, -r or -d flag, you do not need to run Estart if the swtadmd subsystem is active. In this case the subsystem runs Estart for you.

SP Switch Warning
If Eclock is run to change the clock multiplexor settings while the switch is operational, you will experience css outages until a subsequent Estart is completed. If you run Eclock and specify the -f, -a, -r or -d flag, you do not need to run Estart if the swtadmd subsystem is active. In this case the subsystem runs Estart for you.

SP Switch Considerations

Eclock on the SP switch recycles the fault_service_Worm_RTG_SP (Worm) daemon on the nodes. If the switch was operational when the Eclock command was issued, you must run the Estart command following the switch adjustment.
Since Eclock operates across system partitions, if you specified the -f, -a, -r or -d flag, you must run the Estart command in ALL system partitions unless the swtadmd subsystem is active. In this case the subsystem runs Estart for you. Since the -s flag operates just on the specified switch, you need to run Estart only in the partitions which share that switch. However, if you used the -s command to reset the master switch, the effect is the same as having issued a global Eclock command and you must run Estart in all partitions. The -s option will recycle the Worm daemons only on the nodes connected to the target switches.
The -s option will recycle the Worm daemons only on the nodes connected to the target switches. There are certain considerations which must be taken into account when running Eclock -s. Assuming the master switch is not one of the target switches:

If the primary node is not on a targeted switch, its Worm daemon will not be recycled. However, the primary's link to other nodes over the switch will be disrupted. Attempts to Eunfence nodes may timeout or cause the Worm daemon to die on other nodes. To avoid this, run Equiesce prior to running the Eclock -s command. After the Eclock, run the Estart command to get a functional primary node. If necessary, run the Eunfence command to bring isolated nodes on the switch.
If the primary node is on a targeted switch but the primary backup is not, you can wait for primary node takeover to complete. A new primary backup node will be chosen. If necessary, run the Eunfence command to bring isolated nodes on the switch.
If both the primary and primary backup nodes are on a targeted switch, the Worm daemon on both these nodes will be recycled, and you must run Estart to get a functional primary node. If necessary, run the Eunfence command to bring isolated nodes on the switch.

SP Switch Considerations
Eclock on the SP switch recycles the fault_service_Worm_RTG_SP (Worm) daemon on the nodes. If the switch was operational when the Eclock command was issued, you must run the Estart command following the switch adjustment. Since Eclock operates across system partitions, if you specified the -f, -a, -r or -d flag, you must run the Estart command in ALL system partitions unless the swtadmd subsystem is active. In this case the subsystem runs Estart for you. Since the -s flag operates just on the specified switch, you need to run Estart only in the partitions which share that switch. However, if you used the -s command to reset the master switch, the effect is the same as having issued a global Eclock command and you must run Estart in all partitions. The -s option will recycle the Worm daemons only on the nodes connected to the target switches. The -s option will recycle the Worm daemons only on the nodes connected to the target switches. There are certain considerations which must be taken into account when running Eclock -s. Assuming the master switch is not one of the target switches: If the primary node is not on a targeted switch, its Worm daemon will not be recycled. However, the primary's link to other nodes over the switch will be disrupted. Attempts to Eunfence nodes may timeout or cause the Worm daemon to die on other nodes. To avoid this, run Equiesce prior to running the Eclock -s command. After the Eclock, run the Estart command to get a functional primary node. If necessary, run the Eunfence command to bring isolated nodes on the switch. If the primary node is on a targeted switch but the primary backup is not, you can wait for primary node takeover to complete. A new primary backup node will be chosen. If necessary, run the Eunfence command to bring isolated nodes on the switch. If both the primary and primary backup nodes are on a targeted switch, the Worm daemon on both these nodes will be recycled, and you must run Estart to get a functional primary node. If necessary, run the Eunfence command to bring isolated nodes on the switch.

Files

/etc/SP/Eclock.top.1nsb.0isb.0: The standard clock topology file for systems with one NSB or a maximum of 16 nodes.
/etc/SP/Eclock.top.1nsb_8.0isb.0: The standard clock topology file for systems with an SP Switch-8 or a maximum of eight nodes.
/etc/SP/Eclock.top.2nsb.0isb.0: The standard clock topology file for systems with two NSBs or a maximum of 32 nodes.
/etc/SP/Eclock.top.3nsb.0isb.0: The standard clock topology file for systems with three NSBs or a maximum of 48 nodes.
/etc/SP/Eclock.top.4nsb.0isb.0: The standard clock topology file for systems with four NSBs or a maximum of 64 nodes.
/etc/SP/Eclock.top.5nsb.0isb.0: The standard clock topology file for systems with five NSBs or a maximum of 80 nodes.
/etc/SP/Eclock.top.5nsb.4isb.0: The standard clock topology file for systems with five NSBs and four ISBs or a maximum of 80 nodes. This is an advantage-type network with a higher bisectional bandwidth.
/etc/SP/Eclock.top.6nsb.4isb.0: The standard clock topology file for systems with six NSBs and four ISBs or a maximum of 96 nodes.
/etc/SP/Eclock.top.7nsb.4isb.0: The standard clock topology file for systems with seven NSBs and four ISBs or a maximum of 112 nodes.
/etc/SP/Eclock.top.8nsb.4isb.0: The standard clock topology file for systems with eight NSBs and four ISBs or a maximum of 128 nodes.

|Environment Variables

|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run Eclock using a secure remote |method, enter:

|export RCMD_PGM=secrshell
|export DSH_REMOTE_CMD=/bin/ssh
|export REMOTE_COPY_CMD=/bin/scp

Security

You must have root privilege to run this command.

|When restricted root access (RRA) is enabled, this command can only |be run from the control workstation.

Restrictions

This command is not valid on a system with an SP Switch2 switch.

Location

/usr/lpp/ssp/bin/Eclock

Related Information

Commands: Eannotator, Efence , Eprimary, Equiesce , Estart, Etopology , Eunfence, Eunpartition

Examples

To set the clock multiplexors for a 128-way SP system with eight Node Switch Boards (NSBs) and four Intermediate Switch Boards (ISBs), enter:
```
Eclock -f /etc/SP/Eclock.top.8nsb.4isb.0
```
To display the clock multiplexor settings for all switches within the SP system, enter:
```
Eclock
```
To set the switch on frame 1 (switch 1) to be the master switch (use internal oscillator), enter:
```
Eclock -s 1 -m 0
```
To create an Eclock topology file from the current data in the SDR, enter:
```
Eclock -c /tmp/Eclock.top
```
To use an alternate clock topology (with a new switch clock source) for a 64-way SP system with two ISBs, enter:
```
Eclock -a /etc/SP/Eclock.top.4nsb.2isb.0
```
To have Eclock automatically select a topology file for you based on data in the SDR, enter:
```
Eclock -d
```

Efence

Purpose

Efence - Removes an SP node from the current active switch network.

Syntax

|Efence [-h] | |[-G] [-p |{0|1|all}] |[-autojoin] [-f] |[node_specifier] ...

Flags

-h

Displays usage information.

-G

Fences all valid nodes in the list of nodes regardless of system partition boundaries. If the -G flag is not used, the Efence command will only fence the nodes in the current system partition. All other specified nodes will not be fenced and a nonzero return code is returned.

-autojoin

|This flag is not valid on systems where the automatic unfence |feature is enabled.

|With PSSP 3.1 or later releases, you can choose to have nodes |automatically unfenced. With the automatic unfence feature enabled, |whenever a node reboots the default behavior is that it will automatically |join the switch.

|If the automatic unfence feature is disabled, or in a coexistence |environment with the primary node at PSSP 2.4, the autojoin |option enables the nodes in the argument list to be fenced and to |automatically rejoin the current switch network if the node is rebooted or the |Fault Service daemon is restarted.

|If you have an SP Switch installed on your system, such nodes are also |rejoined when an Estart command is issued.

|The default for PSSP 3.1 or later releases, is to have the automatic |unfence feature enabled. See the Estart command for how to |change the default. |

|-p {0|1|all}

|Specifies for which switch plane the operation is to be performed. |If not specified, the default is to perform the operation for all valid switch |planes. This flag is valid only on systems with SP Switch2 |switches.

-f

Allows the current primary and/or primary backup to be fenced. If not specified, the current primary and primary backup may not be fenced. If a current primary node is specified to be fenced, the Efence command will run Eprimary to make the current primary backup node the new oncoming primary node, turn on the isolated bit for the old primary node, and then run Estart. If a current backup node is specified to be fenced, Efence will turn on the isolated bit for the old primary backup node and run Estart. If both the current primary and the current primary backup node are specified to be fenced, a new oncoming primary node is selected, Eprimary is run, the isolated bit for the old primary and primary backup node is turned on, and Estart is run.

Operands

node_specifier

Specifies a node or a list of nodes that are to be taken out of the current switch network. It can be a list of host names, IP addresses, node numbers, frame,slot pairs, or a node group.

|Notes:

|You cannot fence either the primary or primary backup nodes on the SP |Switch, unless you specify the -f flag.
|You cannot fence a node that does not have a switch adapter.

Description

Use the Efence command to remove a node from being part of the current switch network. Once a node is fenced, it cannot communicate with other nodes on the switch network, nor cause errors on the network. This command should be used (without the -autojoin flag) if you want to isolate the node for a period of time, for example, for service or maintenance. To bring the node back on the switch network, use the Eunfence command.

Note:: If a host name or IP address is used as the node_specifier for a dependent node, it must be a host name or IP address assigned to the adapter that connects the dependent node to the SP Switch. Neither the administrative host name nor the Simple Network Management Protocol (SNMP) agent's host name for a dependent node is guaranteed to be the same as the host name of its switch network interface.

|Environment Variables

|PSSP 3.4 provides the ability to run commands using secure remote |command and secure remote copy methods.

|RCMD_PGM - remote command method, either rsh or |secrshell
|DSH_REMOTE_CMD - remote command executable
|REMOTE_COPY_CMD - remote copy executable |

|For example, if you want to run Efence using a secure remote |method, enter:

|export RCMD_PGM=secrshell
|export DSH_REMOTE_CMD=/bin/ssh
|export REMOTE_COPY_CMD=/bin/scp

Security

You must have root privilege to run this command.

|When restricted root access (RRA) is enabled, this command can only |be run from the control workstation.

Location

|/usr/lpp/ssp/bin/Efence

Related Information

Commands: Eannotator, Eclock , Eprimary, Equiesce , Estart, Etopology , Eunfence, Eunpartition

Examples

To display all the nodes that were fenced from the switch network in the current system partition, enter:
```
Efence
```
To display all the nodes that were fenced from the switch network in all system partitions, enter:
```
Efence -G
```
To fence two nodes by IP address, enter:
```
Efence 129.33.34.1 129.33.34.6
```
To fence a node by host name, enter:
```
Efence r11n01
```
To fence node 14 of frame 2 by frame,slot pair, enter:
```
Efence 2,14
```
If the current partition has nodes with node numbers 1, 2, 5, and 6 and another partition has nodes with node numbers 3, 4, 7, and 8, issuing the command:
```
Efence 5 6 7 8
```
fences nodes 5 and 6, but not nodes 7 and 8. As a result, the command returns a nonzero return code.
To successfully fence the nodes in example 6 with the same partitions, use the -G flag as follows:
```
Efence -G 5 6 7 8
```
|On an SP Switch2 system, to fence node number 5 on just the second |switch plane, enter:
```
|Efence -p 1 5
```

Emaster

Purpose

Emaster - Displays the master switch sequencing (MSS) node.

Syntax

Emaster [-h]

Flags

-h: Displays usage information.

Operands

None.

Description

The MSS node is the node which periodically re-synchronizes time-of-day (TOD) signals on the SP Switch2. Use the Emaster command to display the node number of the MSS node.

Standard Output

Output consists of informational messages indicating the current MSS node.

Standard Error

Output consists of error messages, when the command cannot complete successfully.

Exit Values

0: Indicates successful completion of the command.
1: Indicates that an error occurred.

Security

You must have root privilege to run this command.

Restrictions

The Emaster command may be used only on systems with SP Switch2 switches.

Location

/usr/lpp/ssp/bin/Emaster

Related Information

The emasterd daemon (SRC subsystem name emaster) monitors the health and connectivity of the MSS node. If it goes down or loses connectivity to the switch, the emasterd daemon changes the MSS node.

Examples

To display the node number of the current MSS node, enter:

Emaster

emconditionctrl

Purpose

emconditionctrl - Loads the System Data Repository (SDR) with predefined Event Management conditions.

Syntax

emconditionctrl [-a] [-s] [ -k] [-d] [-c] [-t] [-o] [-r] [-h]

Flags

-a: Loads the SDR with predefined Event Management conditions for the current system partition.
-s: Starts the subsystem. (Currently has no effect.)
-k: Stops the subsystem. (Currently has no effect.)
-d: Deletes the subsystem. (Currently has no effect.)
-c: Cleans the subsystem. (Currently has no effect.)
-t: Turns tracing on. (Currently has no effect.)
-o: Turns tracing off. (Currently has no effect.)
-r: Refreshes the subsystem. (Currently has no effect.)
-h: Displays usage information.

Operands

None.

Description

The emconditionctrl script loads the SDR with some useful conditions that can be used for registering for Event Management events. Currently the SP Perspectives application can make use of conditions.

The emconditionctrl script is not normally executed on the command line. It is normally called by the syspar_ctrl command after the control workstation has been installed or when the system is partitioned. It implements all of the flags that syspar_ctrl can pass to its subsystems, although only the -a flag causes any change to the system. The -a flag causes predefined conditions to be loaded only if run on the control workstation. It has no effect if run elsewhere.

Exit Values

0: Indicates the successful completion of the command.
nonzero: Indicates an exit code from the SDRCreateObjects command.

Security

You must have root privilege and write access to the SDR to run this command.

Implementation Specifics

This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).

Location

/usr/lpp/ssp/bin/emconditionctrl

Related Information

Commands: syspar_ctrl

emonctrl

Purpose

emonctrl - A control script that manages the Emonitor subsystem.

Syntax

emonctrl { -a | -s | -k | -d | -c | -t | -o | -r | -h }

Flags

-a: Adds the subsystem.
-s: Starts the subsystem. Not implemented. The subsystem should be started using Estart -m
-k: Stops the subsystem.
-d: Deletes the subsystem.
-c: Cleans the subsystems, that is, delete them from all system partitions.
-t: Turns tracing on for the subsystem. Not used.
-o: Turns tracing off for the subsystem. Not used.
-r: Refreshes the subsystem. Not implemented.
-h: Displays usage information.

Operands

None.

Description

Note:: In PSSP 3.1 or later releases, the Emonitor subsystem is no longer needed, since the new Switch Administration daemon and automatic unfence options provide the same functions as the Emonitor subsystem. However, if you turn off the Switch Administration daemon functions you may still want to use the Emonitor subsystem. And if you are using a primary node with a code_version of PSSP 2.4 or earlier in a coexistence environment, the new functions are not supported. You may want to use the Emonitor subsystem in such an environment.

Note:: The Emonitor subsystem is not supported on a system with an SP Switch2 switch.

The Emonitor subsystem monitors designated nodes in an attempt to maximize their availability on the switch network.

The emonctrl control script controls the operation of the Emonitor subsystem. The subsystem is under the control of the System Resource Controller (SRC) and belongs to a subsystem group called emon.

An instance of the Emonitor subsystem can execute on the control workstation for each system partition. Because Emonitor provides its services within the scope of a system partition, it is said to be system partition-sensitive. This control script operates in a manner similar to the control scripts of other system partition-sensitive subsystems. It should be issued from the control workstation and is not functional on the nodes.

From an operational point of view, the Emonitor subsystem group is organized as follows:

Subsystem

Emonitor

Subsystem Group

emon

SRC Group

emon

The emon group is associated with the Emonitor daemon.

On the control workstation, there are multiple instances of Emonitor, one for each system partition. Accordingly, the subsystem names on the control workstation have the system partition name appended to them. For example, for system partitions named sp_prod and sp_test, the subsystems on the control workstation are named Emonitor.sp_prod and Emonitor.sp_test.

Daemons

Emonitor

The Emonitor daemon provides switch node monitoring.

The emonctrl script is not normally executed from the command line. It is normally called by the syspar_ctrl command during installation of the system, and partitioning or repartitioning of the system.

The emonctrl script provides a variety of controls for operating the Emonitor daemon:

Adding, stopping, and deleting the subsystem
Cleaning up the subsystems, that is, deleting them from all system partitions

Before performing any of these functions, the script obtains the current system partition name and IP address (using the spget_syspar command) and the node number (using the node_number ) command. If the node number is zero, the control script is running on the control workstation. Since the Emonitor daemon runs only on the control workstation, the script performs no function when run on a node.

Except for the clean function, all functions are performed within the scope of the current system partition.

Adding the Subsystem

When the -a flag is specified, the control script uses the mkssys command to add the Emonitor daemon to the SRC. The control script operates as follows:

It checks whether the Emonitor subsystem already exists in this system partition. If the Emonitor subsystem does exist, it exits.
It adds the Emonitor subsystem to the SRC with the system partition name appended.

Starting the Subsystem

This option is unused since the Emonitor daemon must be started via Estart -m.

Stopping the Subsystem

When the -k flag is specified, the control script uses the stopsrc command to stop the Emonitor daemon in the current system partition.

Deleting the Subsystem

When the -d flag is specified, the control script uses the rmssys command to remove the Emonitor subsystem from the SRC. The control script operates as follows:

It makes sure that the Emonitor subsystem is stopped.
It removes the Emonitor subsystem from the SRC using the rmssys command.

Cleaning Up the Subsystems

When the -c flag is specified, the control script stops and removes the Emonitor subsystems for all system partitions from the SRC. The control script operates as follows:

It stops all instances of subsystems in the subsystem group in all system partitions, using the stopsrc -g emon command.
It removes all instances of subsystems in the subsystem group in all system partitions from the SRC using the rmssys command.

Turning Tracing On

Not currently used.

Turning Tracing Off

Not currently used.

Refreshing the Subsystem

Not currently used.

Logging

While it is running, the Emonitor daemon provides information about its operation and errors by writing entries in a log file. The Emonitor daemon uses log files called /var/adm/SPlogs/css/Emonitor.log and /var/adm/SPlogs/css/Emonitor.Estart.log .

Files

/var/adm/SPlogs/css/Emonitor.log: Contains the log of all Emonitor daemons on the system.
/var/adm/SPlogs/css/Emonitor.Estart.log: Contains the log of all Estart and Eunfence commands issued by all Emonitor daemons.

Standard Error

This command writes error messages (as necessary) to standard error.

Exit Values

0: Indicates the successful completion of the command.
1: Indicates that an error occurred.

Security

You must have root privilege to run this command.

Implementation Specifics

This command is part of the IBM Parallel System Support Programs (PSSP) Licensed Program (LP).

Prerequisite Information

AIX Commands Reference

Information about the System Resource Controller (SRC) in AIX General Programming Concepts: Writing and Debugging Programs

Location

/usr/lpp/ssp/bin/emonctrl

Related Information

Commands: Emonitor, Estart , lssrc, startsrc, stopsrc , syspar_ctrl

Examples

To add the Emonitor subsystem to the SRC in the current system partition, set the SP_NAME environment variable to the appropriate system partition name and enter:
```
emonctrl -a
```
To stop the Emonitor subsystem in the current system partition, set the SP_NAME environment variable to the appropriate system partition name and enter:
```
emonctrl -k
```
To delete the Emonitor subsystem from the SRC in the current system partition, set the SP_NAME environment variable to the appropriate system partition name and enter:
```
emonctrl -d
```
To clean up the Emonitor subsystem on all system partitions, enter:
```
emonctrl -c
```
To display the status of all of the subsystems in the Emonitor SRC group, enter:
```
lssrc -g emon
```
To display the status of an individual Emonitor subsystem, enter:
```
lssrc -s subsystem_name
```
To display the status of all of the daemons under SRC control, enter:
```
lssrc -a
```

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]