Chapter 5 Administering Cluster Interconnects and Public Networks
This chapter provides the software procedures for administering the Sun Cluster interconnects and public networks.
Administering the cluster interconnects and public networks consists of both hardware and software procedures. Typically, you configure the cluster interconnects and public networks, including NAFO groups, when you initially install and configure the cluster. If you later need to alter a cluster interconnect or public network configuration, you can use the software procedures in this chapter.
This is a list of the procedures in this chapter.
-
"5.1.2 How to Add Cluster Transport Cables and Transport Adapters"
-
"5.1.3 How to Remove Cluster Transport Cables and Transport Adapters"
-
"5.2.7 How to Change Public Network Management Tunable Parameters"
For a high-level description of the related procedures in this chapter, see Table 5-1 and Table 5-2.
Refer to the Sun Cluster 3.0 Concepts document for background and overview information on the cluster interconnects and public networks.
5.1 Administering the Cluster Interconnects
This section provides the procedures for reconfiguring cluster interconnects, such as cluster transport adapters and cluster transport cables. These procedures require that you install Sun Cluster software.
Most of the time, you can use the scsetup utility to administer the cluster transport for the cluster interconnects. See the scsetup(1M) man page for more information.
For cluster software installation procedures, see the Sun Cluster 3.0 Installation Guide. For procedures about servicing cluster hardware components, see the Sun Cluster 3.0 Hardware Guide.
Table 5-1 Task Map: Administering the Cluster Interconnect|
Task |
For Instructions, Go To... |
|---|---|
|
Administer the cluster transport - Use scsetup | |
|
Check the status of the cluster interconnect - Use scstat | |
|
Add a cluster transport cable or transport adapter - Use scsetup |
"5.1.2 How to Add Cluster Transport Cables and Transport Adapters" |
|
Remove a cluster transport cable or transport adapter - Use scsetup |
"5.1.3 How to Remove Cluster Transport Cables and Transport Adapters" |
|
Enable a cluster transport cable - Use scsetup | |
|
Disable a cluster transport cable - Use scsetup |
5.1.1 How to Check the Status of the Cluster Interconnect
You do not need to be logged in as superuser to perform this procedure.
-
Check the status of the cluster interconnect.
# scstat -W
-
Refer to the following for common status messages.
Status Message
Description and Possible Action
Path online
The path is currently functioning correctly. No action is necessary.
Path waiting
The path is currently being initialized. No action is necessary.
Path faulted
The path is not functioning. Take corrective action.
5.1.1.1 Example--Checking the Status of the Cluster Interconnect
The following example shows the status of a functioning cluster interconnect.
# scstat -W -- Cluster Transport Paths -- Endpoint Endpoint Status -------- -------- ------ Transport path: phys-schost-1:qfe1 phys-schost-2:qfe1 Path online Transport path: phys-schost-1:qfe0 phys-schost-2:qfe0 Path online Transport path: phys-schost-1:qfe1 phys-schost-3:qfe1 Path online Transport path: phys-schost-1:qfe0 phys-schost-3:qfe0 Path online Transport path: phys-schost-2:qfe1 phys-schost-3:qfe1 Path online Transport path: phys-schost-2:qfe0 phys-schost-3:qfe0 Path online |
5.1.2 How to Add Cluster Transport Cables and Transport Adapters
-
Ensure that the physical cluster transport cables are installed.
For the procedure on installing a cluster transport cable, see the Sun Cluster 3.0 Hardware Guide.
-
Become superuser on any node in the cluster.
-
Execute the scsetup utility.
# scsetup
The Main Menu appears.
-
Access the Cluster Interconnect Menu by entering 2 (Cluster interconnect).
-
Add the cable by entering 1 (Add a transport cable).
Follow the instructions and enter the requested information. A junction is not needed for direct connections in a cluster with two nodes. However, you need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
>>> Add a Cluster Transport Cable <<< ... Is it okay to continue (yes/no) [yes]? <Return> ... To which node do you want to add the cable? nodename Name of the adapter to use on "node"? adaptername Name of the junction at the other end of the cable? junctionname Okay to use the default for this cable connection [yes]? <Return> Is it okay to proceed with the update (yes/no) [yes]? <Return>
-
Add the adapter by entering 2 (Add a transport adapter to a node).
Follow the instructions and enter the requested information. A junction is not needed for direct connections in a cluster with two nodes. However, you need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
>>> Add a Cluster Transport Adapter <<< ... Is it okay to continue (yes/no) [yes]? <Return> ... To which node do you want to add the cable? nodename Name of the adapter to use on "node"? adaptername Name of the junction at the other end of the cable? junctionname Okay to use the default for this cable connection [yes]? <Return> Is it okay to proceed with the update (yes/no) [yes]? <Return>
-
Verify that the cluster transport cable or transport adapter is added.
# scconf -p | grep cable # scconf -p | grep adapter
5.1.2.1 Example--Adding a Cluster Transport Cable and a Transport Adapter
The following example shows how to add a transport cable or transport adapter to a node using the scsetup command.
[Ensure the physical cable is installed.] [Become superuser on a node in the cluster.] [Execute the scsetup utility:] # scsetup [Enter option 2:] *** Main Menu *** Please select from one of the following options: ... 2) Cluster interconnect ... Option: 2 [Enter option 1 to add a cable:] *** Cluster Interconnect Menu *** Please select from one of the following options: ... 1) Add a transport cable ... Option: 1 [Enter the requested information:] >>> Add a Cluster Transport Cable <<< ... Is it okay to continue (yes/no) [yes]? <Return> . ... To which node is the cable attached? phys-schhost-2 Name of the adapter on "phys-schost-2"? qfe-0 Is it okay to proceed with the update (yes/no) [yes]? <Return> . scconf -a -m endpoint=phys-schost-2:hme1,endpoint=hub0 Command completed successfully. Hit ENTER to continue: <Return> [Enter option 2 to add an adapter:] *** Cluster Interconnect Menu *** Please select from one of the following options: ... 2) Add a transport adapter to a node ... Option: 2 [Enter the requested information:] >>> Add a Cluster Transport Adapter <<< ... Is it okay to continue (yes/no) [yes]? <Return> . ... To which node is the cable attached? phys-schhost-2 Name of the adapter on "phys-schost-2"? qfe-0 Is it okay to proceed with the update (yes/no) [yes]? <Return> . scconf -a -m endpoint=phys-schost-2:hme1,endpoint=hub0 Command completed successfully. Hit ENTER to continue: <Return> [Verify that the cable and adapter are added:] # scconf -p | grep cable Transport cable: phys-schost-2:qfe0@1 ethernet-1@2 Enabled Transport cable: phys-schost-3:qfe0@1 ethernet-1@3 Enabled Transport cable: phys-schost-1:qfe0@0 ethernet-1@1 Enabled # scconf -p | grep adapter Node transport adapters: qfe2 hme1 qfe0 Node transport adapter: qfe0 Node transport adapters: qfe0 qfe2 hme1 Node transport adapter: qfe0 Node transport adapters: qfe0 qfe2 hme1 Node transport adapter: qfe0 |
5.1.3 How to Remove Cluster Transport Cables and Transport Adapters
Use the following procedure to remove cluster transport cables and cluster transport adapters from a node. When a cable is disabled, the two endpoints of the cable remain configured. An adapter cannot be removed if it is still in use as an endpoint in a transport cable.
Caution - A cluster node needs at least one functioning cable attached to the cluster interconnect to be a member of the cluster. Always verify the status of a node's cluster interconnect before disabling a cable. Only disable a cable connection after you have verified that it is redundant; that is, that another connection is available. Disabling a node's last remaining working cable takes the node out of cluster membership.
-
Become superuser on any node in the cluster.
-
Check the status of the remaining cluster transport path.
# scstat -W
Caution - If you receive an error such as "path faulted" while attempting to remove one node of a two-node cluster, investigate the problem before continuing with this procedure. Such a problem could indicate that a node path is unavailable. Removing the remaining good path takes the node out of cluster membership and could result in a cluster reconfiguration.
-
Execute the scsetup utility.
# scsetup
The Main Menu appears.
-
Access the Cluster Interconnect Menu by entering 2 (Cluster interconnect).
-
Remove the cable by entering 4 (Remove a transport cable).
Follow the instructions and enter the requested information. You need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
*** Cluster Interconnect Menu *** Please select from one of the following options: ... 4) Remove a transport cable ... Option: 4 ... >>> Remove a Cluster Transport Cable <<< ... Is it okay to continue (yes/no) [yes]? <Return> ... To which node is the cable attached? nodename Name of the adapter on "node"? adaptername Is it okay to proceed with the update (yes/no) [yes]? <Return> ... Command completed successfully. Hit ENTER to continue: <Return>
Note -If you are removing a physical cable, disconnect the cable between the port and the destination device.
-
To remove an adapter, enter 5 (Remove a transport adapter from a node).
Follow the instructions and enter the requested information. You need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
*** Cluster Interconnect Menu ** Please select from one of the following options: ... 5) Remove a transport adapter ... Option: 5 ... >>> Remove a Cluster Transport Adapter <<< ... Is it okay to continue (yes/no) [yes]? <Return> ... To which node is the cable attached? nodename Name of the adapter on "node"? adaptername Is it okay to proceed with the update (yes/no) [yes]? <Return> ... Command completed successfully. Hit ENTER to continue: <Return>
Note -If you are removing a physical adapter from a node, see the Sun Cluster 3.0 Hardware Guide for hardware service procedures.
-
Verify that the cable or the adapter has been removed.
# scconf -p | grep cable # scconf -p | grep adapter
The transport cable or adapter removed from the given node should not appear in the output from this command.
5.1.3.1 Example--Removing a Transport Cable or Transport Adapter
The following example shows how to remove a transport cable or transport adapter using the scsetup command.
[Become superuser on a node in the cluster.] [Execute the scsetup utility:] # scsetup [Enter option 2:] *** Main Menu *** Please select from one of the following options: ... 2) Cluster interconnect ... Option: 2 [Enter option 4 to remove a cable:] *** Cluster Interconnect Menu *** Please select from one of the following options: ... 4) Remove a transport cable ... Option: 4 [Enter the requested information:] >>> Remove a Cluster Transport Cable <<< ... Is it okay to continue (yes/no) [yes]? <Return> . ... To which node is the cable attached? phys-schhost-2 Name of the adapter on "phys-schost-2"? qfe-0 Is it okay to proceed with the update (yes/no) [yes]? <Return> . scconf -a -m endpoint=phys-schost-2:hme1,endpoint=hub0 Command completed successfully. Hit ENTER to continue: <Return> [Enter option 5 to remove an adapter:] *** Cluster Interconnect Menu *** Please select from one of the following options: ... 5) Remove a transport adapter from a node ... Option: 5 [Enter the requested information:] >>> Remove a Cluster Transport Adapter <<< ... Is it okay to continue (yes/no) [yes]? <Return> . ... To which node is the cable attached? phys-schhost-2 Name of the adapter on "phys-schost-2"? qfe-0 Is it okay to proceed with the update (yes/no) [yes]? <Return> . scconf -r -m endpoint=phys-schost-2:hme1 Command completed successfully. Hit ENTER to continue: <Return> [Verify that the cable or adapter is removed:] # scconf -p | grep cable Transport cable: phys-schost-2:qfe0@1 ethernet-1@2 Enabled Transport cable: phys-schost-3:qfe0@1 ethernet-1@3 Enabled Transport cable: phys-schost-1:qfe0@0 ethernet-1@1 Enabled # scconf -p | grep adapter Node transport adapters: qfe2 hme1 qfe0 Node transport adapter: qfe0 Node transport adapters: qfe0 qfe2 hme1 Node transport adapter: qfe0 Node transport adapters: qfe0 qfe2 hme1 Node transport adapter: qfe0 |
5.1.4 How to Enable a Cluster Transport Cable
This option is used to enable an already existing cluster transport cable.
-
Become superuser on any node in the cluster.
-
Enter the scsetup utility.
# scsetup
The Main Menu appears.
-
Access the Cluster Interconnect Menu by entering 2 (Cluster interconnect).
-
Enable the transport cable by entering 7 (Enable a transport cable).
Follow the instructions when prompted. You need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
-
Verify that the cable is enabled.
# scconf -p | grep cable
5.1.4.1 Example--Enabling a Cluster Transport Cable
This example shows how to enable a cluster transport cable on adapter qfe-1 located on the node phys-schost-2.
[Become superuser on any node.] [Enter the scsetup utility:] # scsetup [Enter option 7:] *** Cluster Interconnect Menu *** Please select from one of the following options: ... 7) Enable a transport cable ... Option: 7 [Enter the requested information:] >>> Enable a Cluster Transport Cable <<< ... Is it okay to continue (yes/no) [yes]? <Return> ... To which node is the cable attached? phys-schhost-2 Name of the adapter on "phys-schost-2"? qfe-1 Is it okay to proceed with the update (yes/no) [yes]? <Return> scconf -c -m endpoint=phys-schost-2:qfe1,state=enabled Command completed successfully. Hit ENTER to continue: <Return> [Verify that the cable is enabled:] # scconf -p | grep cable Transport cable: phys-schost-2:qfe1@0 ethernet-1@2 Enabled Transport cable: phys-schost-3:qfe0@1 ethernet-1@3 Enabled Transport cable: phys-schost-1:qfe0@0 ethernet-1@1 Enabled |
5.1.5 How to Disable a Cluster Transport Cable
You might need to disable a cluster transport cable to temporarily shut down a cluster interconnect path. This is useful when troubleshooting a cluster interconnect problem or when replacing cluster interconnect hardware.
When a cable is disabled, the two endpoints of the cable remain configured. An adapter cannot be removed if it is still in use as an endpoint in a transport cable.
Caution - A cluster node needs at least one functioning cable attached to the cluster interconnect to be a member of the cluster. Always verify the status of a node's cluster interconnect before disabling a cable. Only disable a cable connection after you have verified that it is redundant; that is, that another connection is available. Disabling a node's last remaining working cable takes the node out of cluster membership.
-
Become superuser on any node in the cluster.
-
Check the status of the cluster interconnect before disabling a cable.
# scstat -W
Caution - If you receive an error such as "path faulted" while attempting to remove one node of a two-node cluster, investigate the problem before continuing with this procedure. Such a problem could indicate that a node path is unavailable. Removing the remaining good path takes the node out of cluster membership and could result in a cluster reconfiguration.
-
Enter the scsetup utility.
# scsetup
The Main Menu appears.
-
Access the Cluster Interconnect Menu by entering 2 (Cluster interconnect).
-
Disable the cable by entering 8 (Disable a transport cable).
Follow the instructions and enter the requested information. All of the components on this cluster interconnect will be disabled. You need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
-
Verify that the cable is disabled.
# scconf -p | grep cable
5.1.5.1 Example--Disabling a Cluster Transport Cable
This example shows how to disable a cluster transport cable on adapter qfe-1 located on the node phys-schost-2.
[Become superuser on any node.] [Enter the scsetup utility:] # scsetup [Enter option 8:] *** Cluster Interconnect Menu *** Please select from one of the following options: ... 8) Disable a transport cable ... Option: 8 [Enter the requested information:] >>> Disable a Cluster Transport Cable <<< ... Is it okay to continue (yes/no) [yes]? <Return> ... To which node is the cable attached? phys-schhost-2 Name of the adapter on "phys-schost-2"? qfe-1 Is it okay to proceed with the update (yes/no) [yes]? <Return> scconf -c -m endpoint=phys-schost-2:qfe1,state=disabled Command completed successfully. Hit ENTER to continue: <Return> [Verify that the cable is disabled:] # scconf -p | grep cable Transport cable: phys-schost-2:qfe1@0 ethernet-1@2 Disabled Transport cable: phys-schost-3:qfe0@1 ethernet-1@3 Enabled Transport cable: phys-schost-1:qfe0@0 ethernet-1@1 Enabled |
5.2 Administering the Public Network
If you need to alter a public network configuration, you can use the software procedures in this section.
When administering public network adapters pay attention to the following:
-
Avoid unconfiguring (unplumbing) or bringing down the active adapter of a NAFO group without first switching over the active adapter to a backup adapter in the group. See "5.2.5 How to Switch a NAFO Group's Active Adapter".
-
Avoid rewiring backup adapters to different subnets without first removing them from their respective NAFO groups.
-
Logical adapter operations can be done on the active adapter even if monitoring is on for the group.
-
You must maintain at least one public network connection for each node in the cluster. The cluster is inaccessible without a public network connection.
For cluster software installation procedures, see the Sun Cluster 3.0 Installation Guide. For procedures about servicing public networking hardware components, see the Sun Cluster 3.0 Hardware Guide.
Table 5-2 Task Map: Administering the Public Network|
Task |
For Instructions, Go To... |
|---|---|
|
Create a NAFO group on a node. | |
|
Add more public network adapters to a node for increased availability of the public network. | |
|
Delete a NAFO group to not have any monitoring or failover for any adapter in the group. | |
|
Remove backup adapters from an existing NAFO group to enable the adapter to be removed from the system, to be replaced, or to be reconnected to a different subnet and used as backup for another NAFO group. | |
|
Switch the active adapter to a backup adapter so that the current active adapter can be removed from the NAFO group. | |
|
Check the status of NAFO groups. | |
|
Change parameters to tune the PNM fault detection and failover process. |
"5.2.7 How to Change Public Network Management Tunable Parameters" |
5.2.1 How to Create a NAFO Group
-
Note the following requirements for creating a NAFO group:
-
All public network adapters must be configured to belong to a NAFO group.
-
For any given node, there can be at most one NAFO group on a given subnet.
-
All adapters in a given NAFO group must be connected to the same subnet.
-
Only one adapter in a given NAFO group can have a hostname association, that is, an /etc/hostname.adapter file.
-
A public network adapter can belong to only one NAFO group.
-
-
Become superuser on the node being configured for a NAFO group.
-
For this node, find out the public network adapters that are physically connected to the same subnet.
These adapters form the backup adapters for the NAFO group.
-
Determine if you need to create an /etc/hostname.adapter file for one of the public network adapters.
-
If no (the file already exists), proceed to Step 5.
-
If yes (the file does not exist), create the file and add the hostname of the public network adapter's IP address to the file. For example:
# vi /etc/hostname.hme0 phys-schost-1
-
-
Edit the /etc/inet/hosts file to add the IP address and corresponding hostname assigned to the public network adapter.
For example, the following shows the IP address 192.29.75.101 and hostname phys-schost-1 added to the /etc/inet/hosts file.
# vi /etc/inet/hosts 192.29.75.101 phys-schost-1
Note -If a naming service is used, this information should also exist in the naming service database.
-
Create the NAFO group.
# pnmset -c nafo-group -o create adapter [adapter ...]
- -c nafo-group
-
Performs a configuration subcommand for the specified NAFO group. NAFO groups must be named nafoN, where N is a nonnegative integer identifier for the group. Group names are local to each node. Thus, the same NAFO group name can be used on multiple nodes.
- -o create
-
Creates the new NAFO group.
- adapter [ adapter ... ]
-
Specifies the public network adapter(s) that serves as the backup adapter. See Step 3 above.
Note -If an adapter is already configured, it will be chosen as the active adapter and the pnmset command does not alter its state. Otherwise, one of the backup adapters will be configured and assigned the IP address found in the /etc/hostname.adapter file for the NAFO group.
-
Verify the status of the NAFO group.
# pnmstat -l
5.2.1.1 Example--Creating a NAFO Group
The following example shows the creation of a NAFO group (nafo0) configured with two network adapters (qfe0 and qfe1).
# pnmstat -l # pnmset -c nafo0 -o create qfe0 qfe1 # pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK NEVER qfe0 |
5.2.2 How to Delete a NAFO Group
Delete a NAFO group when you do not want monitoring and failover for any adapter in the group. To be deleted, a NAFO group cannot be in use by logical host resource groups or shared address resource groups.
-
Become superuser on the node that contains the NAFO group that is being deleted.
-
Identify whether the NAFO group is being used by any logical host or shared address resources.
# scrgadm -pv
You can also use scrgadm -pvv (with two v flags) to locate the resources that are using the NAFO group you are going to delete.
-
Switch logical host resource groups and shared address resource groups using this NAFO group to another node.
# scswitch -z -g resource-group -h node
- -z -g resource-group
-
Switches the specified resource group.
- -h node
-
Specifies the name of the node to switch the resource group to.
-
Delete the NAFO group.
# pnmset -c nafo-group -o delete
- -c nafo-group
-
Specifies the NAFO group to be deleted.
- -o delete
-
Deletes the NAFO group.
-
Verify the status of the NAFO group.
The deleted NAFO group should not appear in the listing.
# pnmstat -l
5.2.2.1 Example--Deleting a NAFO Group
The following example shows the NAFO group named nafo1 deleted from the system. Logical host resource group lh-rg-1, which uses this NAFO group, is first switched to a different node.
# scswitch -z -g lh-rg-1 -h phys-schost-2 # pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK NEVER qfe0 nafo1 qfe2 OK NEVER qfe2 # pnmset -c nafo1 -o delete # pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK NEVER qfe0 |
5.2.3 How to Add an Adapter to a NAFO Group
You can add adapters to an existing NAFO group to provide additional backup adapters for the NAFO group and thereby increase the availability of public network connectivity for the cluster node.
-
Do you need to install the new public network adapter card(s) in the node(s)?
-
If yes, see the Sun Cluster 3.0 Hardware Guide for instructions.
-
If no, proceed to Step 2.
-
-
Make sure the adapter to be added to the NAFO group is connected to the same subnet as the active adapter for the NAFO group.
-
Make sure the adapter is not plumbed, and that it does not have an associated /etc/hostname.adapter file.
-
Become superuser on the node that contains the NAFO group to which the new adapter is being added.
-
Add the adapter to the NAFO group.
# pnmset -c nafo-group -o add adapter
- -c nafo-group
-
Specifies the NAFO group to which the new adapter is being added.
- -o add adapter
-
Specifies the public network adapter being added to the named NAFO group.
-
Verify the status of the NAFO group.
# pnmstat -l
5.2.3.1 Example--Adding an Additional Public Network Adapter to a NAFO Group
The following example shows the addition of adapter qfe2 to NAFO group nafo0 which already contained two adapters (qfe0, qfe1).
# pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK NEVER qfe0 # pnmset -c nafo0 -o add qfe2 # pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1:qfe2 OK NEVER qfe0 |
5.2.4 How to Remove an Adapter From a NAFO Group
Remove backup adapters from an existing NAFO group to enable the adapter to be removed from the system, to be replaced, or to be reconnected to a different subnet and used as backup for another NAFO group.
Caution - Removing the last backup adapter from a NAFO group results in no protection against faults detected on the active adapter, reducing public network availability for the cluster node.
-
If you want to remove the active adapter, first switch to another adapter in the group.
-
As superuser, remove the adapter from the NAFO group.
# pnmset -c nafo-group -o remove adapter
- -c nafo-group
-
Specifies the NAFO group from which to remove the adapter.
- -o remove adapter
-
Removes the adapter from the NAFO group.
-
Verify the status of the NAFO group.
The deleted adapter should not appear in the listing for the NAFO group.
# pnmstat -l
5.2.4.1 Example--Removing an Adapter From a NAFO Group
The following example removes adapter qfe2 from NAFO group nafo0.
# pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1:qfe2 OK NEVER qfe0 # pnmset -c nafo0 -o remove qfe2 # pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK NEVER qfe0 |
5.2.5 How to Switch a NAFO Group's Active Adapter
Switch the active adapter to a backup adapter so that the current active adapter can be removed from the NAFO group. The pnmd(1M) daemon moves all IP addresses hosted by the current active adapter to the new active adapter in a similar fashion as a fault-triggered adapter failover.
Note -
Connections can experience a brief delay while the switchover is taking place. Otherwise, the operation is transparent to higher-level applications.
-
Ensure the physical connectivity of the new active adapter is identical to that of the current active adapter.
If the new active adapter fails to host some of the IP addresses as the current active adapter, network and data services that depend on those IP addresses are interrupted until the physical connectivity is fixed or a subsequent successful failover occurs.
-
Become superuser on the node that contains the NAFO group whose active adapter you want to switch.
-
Switch the active adapter.
# pnmset -c nafo-group -o switch adapter
- -c nafo-group
-
Specifies the NAFO group containing the adapter to switch.
- -o switch adapter
-
Makes the specified adapter the active adapter in the NAFO group.
-
Verify the status of the NAFO group.
The "switched-to" adapter should now appear as the active adapter.
# pnmstat -l
5.2.5.1 Example--Switching a NAFO Group's Active Adapter
The following example switches the active adapter to qfe1 from qfe0.
# pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK NEVER qfe0 # pnmset -c nafo0 -o switch qfe1 # pnmstat -l group adapters status fo_time act_adp nafo0 qfe0:qfe1 OK 11 qfe1 |
5.2.6 How to Check the Status of NAFO Groups
Run the pnmstat(1M) command to list information about the current setup and status of all NAFO groups on a node.
# pnmstat -l |
You can also use the pnmptor(1M) and pnmrtop(1M) commands to get information on adapters.
5.2.6.1 Examples--Checking the Status of NAFO Groups
The following example shows the status of a node's three NAFO groups.
# pnmstat -l Group adapters status fo_time act_adp nafo0 qfe5 OK NEVER qfe5 nafo1 qfe6 OK NEVER qfe6 nafo2 qfe7 OK NEVER qfe7 |
5.2.6.2 Examples--Finding the Active Adapter For a NAFO Group
The following example shows that the active adapter in NAFO group nafo0 is adapter qfe5.
# pnmptor nafo0 qfe5 |
5.2.6.3 Examples--Finding an Adapter's NAFO Group
The following example shows that adapter qfe5 belongs to NAFO group nafo0.
# pnmrtop qfe5 nafo0 |
5.2.7 How to Change Public Network Management Tunable Parameters
There are four tunable parameters in this algorithm: inactive_time, ping_timeout, repeat_test, and slow_network. These parameters provide an adjustable trade-off between speed and correctness of fault detection. See Table 5-3 for more information.
Use this procedure to change the default Public Network Management (PNM) values for the pnmd(1M) daemon.
-
Become superuser on a node in the cluster.
-
If it doesn't already exist, create the pnmparams file.
# vi /etc/cluster/pnmparams
-
Use the following table to set PNM parameters.
Note -Settings in the /etc/cluster/pnmparams file apply to all NAFO groups on the node. Lines started with a pound sign (#) are ignored. Other lines in the file must be of the format: variable=value.
Table 5-3 Public Network Management Tunable ParametersParameter
Description
inactive_time
Number of seconds between successive probes of the packet counters of the current active adapter. Default is 5.
ping_timeout
Time-out value in seconds for the ALL_HOST_MULTICAST and subnet broadcast pings. Default is 4.
repeat_test
Number of times to do the ping sequence before declaring that the active adapter is faulty and failover is triggered. Default is 3.
slow_network
Number of seconds waited after each ping sequence before checking packet counters for any change. Default is 2.
warmup_time
Number of seconds waited after failover to a backupadapter before resuming fault monitoring. This allows extra time for any slow driver or port initialization. Default is 0.
Note -The changes don't take affect until the next time the pnmd daemon starts up.
5.2.7.1 Example--Changing Public Network Management Tunable Parameters
The following shows a sample/etc/cluster/pnmparams file, with two parameters changed from their default values.
inactive_time=3 repeat_test=5 |
- © 2010, Oracle Corporation and/or its affiliates