Setting up remote command processing

Use this procedure to set up remote command processing (dsh) commands from Cluster Systems Management (CSM) to the switches and to the fabric management server.

Remote command processing to the fabric management server setup is a standard Linux® node setup, except that the fabric management server is treated as a device.

Remote command processing to the switches is standard hardware device set up.

Figure 1 illustrate tasks R1, R2, and R3 for setting up remote command processing. It also illustrates how the setup tasks for the remote command processing relate to the key tasks that are illustrated in Figure 1.

Figure 1. Remote command processing setup

Do not proceed with this procedure until all the following tasks have been completed:

1. The Cluster Systems Management/Management Server (CSM/MS) has been installed and cabled to the service and cluster virtual local area networks (VLANs) (CM4).
2. The fabric management server has been installed and cabled to the cluster VLAN (F8).
3. The switches have been installed and cabled to the cluster VLAN (W3).
4. The Ethernet devices on the service and cluster VLAN have been installed and cabled (E2).

To set up remote command processing, complete the following steps:

1. R1 (M4): Set up remote command processing with the fabric management server as follows:
   Note: The following method is just one of several methods by which you can set up remote command processing to a fabric management server. You can use any method that meets your requirements. For example, you can set up the fabric management server as a node. By setting it up as a device rather than a node, you might find it easier to group it differently from the IBM® servers.
   1. If you are only defining a single fabric management server as a device for CSM, use the following command. Otherwise, go to step 1b.

      definehwdev -d [Fabric/MS] DeviceType=FabricMS
             RemoteShellUser=[USERID] RemoteShell=/usr/bin/ssh
             RemoteCopyCmd=/usr/bin/scp

   2. To define multiple fabric management servers, use the -f flag to identify a device definition file. For details, see the CSM Command Reference Guide.

      The following are the key attributes of the device definition file:

      • Name: The host name of the network adapter for the Linux host.
      • DeviceType: A unique name for the type of device, for example, QLogicMS for QLogic Management Server.
      • The following attributes are for Secure Shell (SSH) and dsh:
        • RemoteShellUser equals [USERID]. The USERID has permissions to Fast Fabric or the Fabric Manager.
        • RemoteShell equals /usr/bin/ssh.
        • RemoteCopyCmd equals /usr/bin/scp.
      Note: See the CSM man pages about deviceattributes for a list of available attributes for defining a device.
   3. Define at least one hardware group to address all fabric management servers at once:

      hwdevgrp -w "DeviceType=='FabricMS'”  AllFabricMS

   4. Exchange SSH keys by using the updatehwdev -k -D AllFabricMS command.
      Note: Because a mixture of devices is being defined, the –a option cannot be used.
   5. Use dsh -d or dsh -D to remotely access the fabric management server from the CSM/MS.
2. R2 (M4): Set up remote command processing with the switches as follows.
   Note: The following method is just one of several methods by which you can set up remote command processing to a QLogic switch. You can use any method that meets your requirements. The QLogic switch does not use a standard shell for its command-line interface (CLI). Therefore, it should be set up as a device and not a node. For the dsh and updatehwdev commands to work, you need the command definition file.
   1. Create a definition file for the device type command for the switch device. This is important for the dsh and updatehwdev commands to work on the proprietary command line switch.
      1. If the /var/opt/csm/IBSwitch/Qlogic/config file exists, you can skip the creation of this file, and go to step 2b.
      2. Create the path by using the /var/opt/csm/IBSwitch/Qlogic command.
      3. Edit the /var/opt/csm/IBSwitch/Qlogic/config file.
      4. Add the following lines to the file:

         # QLogic switch device configuration
         # Follow the section format to add entry/value pair similar to below
         # [main]
         # EntryName=Value
         [main]
         # SSH key add command on device (must be uppercase K)
         ssh-setup-command=sshKey add
         [dsh]
         # Special command before remote command: for example, export environment variable
         pre-command=NULL
         # The command used to show the return code of last command processed. 
         # Note: The command output must be a numeric value on the last line.
         # For example:  # hello world!
         #       # 0
         post-command=showLastRetcode -brief

   2. For each switch, define the switch as a device for CSM by using the following command:

      definehwdev -d [switch address] DeviceType=IBSwitch::Qlogic
             RemoteShellUser=admin RemoteShell=/usr/bin/ssh
             RemoteCopyCmd=/usr/bin/scp

   3. To define multiple switches, use the -f flag to identify a device definition file. For details, see the CSM Command Reference Guide.

      The following are the key attributes for the definition file:

      • Name: The host name of the switch.
      • DeviceType: A unique name for the type of device.
      • The following attributes are for SSH and dsh:
        • RemoteShellUser equals admin
        • RemoteShell equals /usr/bin/ssh
        • RemoteCopyCmd equals /usr/bin/scp
      Note: See the CSM man pages about deviceattributes for a list of available attributes for defining a device.
   4. Define a device group for the switches by using the following command:

      hwdevgrp -w "DeviceType like 'IBSwitch%Qlogic'”  AllIBSwitches

      Note: Because the DeviceType is IBSwitch::Qlogic, it conflicts with the mkrsrc use of the :: as a delimiter. Therefore, the % is used as a wildcard to avoid this problem.
   5. Exchange ssh keys with the IBSwitches group by using the following command:

      updatehwdev -k –D AllIBSwitches --devicetype IBSwitch::Qlogic

      Note: Because a mixture of devices is being defined, the –a option cannot be used.
   6. Verify remote access to the switches by using the following command:
      Note: You do not have to enter a password, and each switch replies with its firmware level.

      /opt/csm/bin/dsh –D AllIBSwitches --devicetype IBSwitch::Qlogic fwVersion |
      more

   7. You can now use the dsh -d or dsh -D command to remotely access the switches from the CSM/MS. Do not forget to use the –-devicetype option so that the dsh command uses the appropriate command sequence to the switches.
3. Optional: R3 (M4): Create device groups to send commands to groups of switches and fabric management servers. In the previous steps, you set up a group for all fabric management servers, and you set up a group for all switches. For details on setting up device groups, see the CSM Administration Guide. Some possible groupings include the following examples:
   • All the fabric management servers (AllFabricMS)
   • All primary fabric management servers
   • All the switches (AllIBSwitches)
   • A separate subnet group for all the switches on a subnet