Activating Compute Nodes as ASR Assets

1. Using SSH, log into the compute node ILOM as root.

2. Go to the alert rules directory and display rule set 1.

   -> cd /SP/alertmgmt/rules
   /SP/alertmgmt/rules
   
   -> show 1
     /SP/alertmgmt/rules/1
         Targets:
         Properties:
             type = snmptrap
             level = disable
             destination = 0.0.0.0
             destination_port = 0
             community_or_username = public
             snmp_version = 1
             testrule = (Cannot show property)
   ->

   If the rule set is available (destination = 0.0.0.0), configure it for ASR. Otherwise, look for the next available rule set.

3. Define a new rule set with the following properties:

   -> cd 1
   -> set level=minor destination=192.168.4.216 destination_port=162 snmp_version=2c
   -> show
     /SP/alertmgmt/rules/1
         Targets:
         Properties:
             type = snmptrap
             level = minor
             destination = 192.168.4.216
             destination_port = 162
             community_or_username = public
             snmp_version = 2c
             testrule = (Cannot show property)
         Commands:
             cd
             set
             show
   ->

   The destination property is a virtual IP in the appliance management network, shared by both management nodes, but active only on the master.

   Rule set properties are space-separated.

4. Activate the compute node as an ASR asset in ASR Manager.

   1. Using SSH, log into the master management node.

   2. Activate the asset by adding its ILOM IP to the ASR configuration with the following command:

      # /opt/SUNWswasr/bin/asr activate_asset –i <asset_ilom_ip>

      Caution

      Verify that you are activating the asset with the IP address of its ILOM, and not the IP assigned to another network interface.

5. Repeat this procedure for each compute node you wish to activate as an ASR asset.

Activating InfiniBand Switches as ASR Assets

1. Using SSH, log into the NM2-36P Sun Datacenter InfiniBand Expansion Switch ILOM as root.

2. Launch the Service Processor shell.

   [root@ilom-ovcasw19r1 ~]# spsh
   ->

3. Go to the alert rules directory and display rule set 1.

   -> cd /SP/alertmgmt/rules
   /SP/alertmgmt/rules
   
   -> show 1
     /SP/alertmgmt/rules/1
         Targets:
         Properties:
             type = snmptrap
             level = disable
             destination = 0.0.0.0
             destination_port = 0
             community_or_username = public
             snmp_version = 1
             testrule = (Cannot show property)
         Commands:
             cd
             set
             show
   ->

4. Define a new rule set with the following properties:

   -> cd 1
   -> set level=minor destination=192.168.4.216 destination_port=162 snmp_version=2c
   Set 'level' to 'minor'
   Set 'destination' to '192.168.4.216'
   Set 'destination_port' to '162'
   Set 'snmp_version' to '2c'
   
   -> show
     /SP/alertmgmt/rules/1
         Targets:
         Properties:
             type = snmptrap
             level = minor
             destination = 192.168.4.216
             destination_port = 162
             community_or_username = public
             snmp_version = 2c
             testrule = (Cannot show property)
         Commands:
             cd
             set
             show
   ->

   The destination property is a virtual IP in the appliance management network, shared by both management nodes, but active only on the master.

   Rule set properties are space-separated.

5. Make sure that SNMP version 2c is enabled on the switch.

   -> cd /SP/services/snmp
   /SP/services/snmp
   -> show
     /SP/services/snmp
         Targets:
             communities
             mibs
             users
         Properties:
             engineid = (none)
             port = 161
             servicestate = enabled
             sets = disabled
             v1 = disabled
             v2c = disabled
             v3 = enabled
         Commands:
             cd
             set
             show
   -> set v2c=enabled

6. Activate the NM2-36P Sun Datacenter InfiniBand Expansion Switch as an ASR asset in ASR Manager.

   1. Using SSH, log into the master management node.

   2. Activate the asset by adding its ILOM IP to the ASR configuration with the following command:

      # /opt/SUNWswasr/bin/asr activate_asset –i <asset_ilom_ip>

7. Repeat this procedure for the second InfiniBand switch in order to activate it as an ASR asset.

1. Using SSH and an account with superuser privileges, log into the master management node.

   Note

   The data center IP address used in this procedure is an example.

   # ssh root@10.100.1.101
   root@10.100.1.101's password:
   [root@ovcamn05r1 ~]#

2. Stop the tinyproxy service and verify the version installed on the system.

   # service tinyproxy stop
   Stopping tinyproxy: [ OK ]
   # rpm -q tinyproxy
   tinyproxy-1.8.2-1.el6.x86_64

3. If the installed tinyproxy is older than version 1.8.3, upgrade it to the version referenced in the support note with Doc ID 1645856.1.

   Download the tinyproxy rpm to a temporary directory on the management node and run the upgrade command.

   # cd /tmp
   # ls -al tinyproxy*
   -rw-r--r-- 1 root root 61224 Apr 4 13:44 tinyproxy-1.8.3-1.el6.x86_64.rpm
   # rpm -Uvh tinyproxy-1.8.3-1.el6.x86_64.rpm
   warning: tinyproxy-1.8.3-1.el6.x86_64.rpm: Header V3 RSA/SHA256 Signature,
   key ID ec551f03: NOKEY
   Preparing...                ########################################### [100%]
      1:tinyproxy              ########################################### [100%]

4. Make the necessary changes to the tinyproxy configuration to enable ASR traffic through the management node.

   1. Open the file /etc/tinyproxy/tinyproxy.conf for editing.

   2. Look for the section that defines on which interfaces tinyproxy listens. It starts with “# Listen:”.

      Comment out the line that binds tinyproxy to the interface in the Oracle VM management network by adding a "#" character in front of it.

      # Listen: If you have multiple interfaces this allows you to bind to
      # only one. If this is commented out, tinyproxy will bind to all
      # interfaces present.
      #
      #Listen 192.168.140.4

   3. Scroll down to the section Customization of authorization controls. It starts with “# Allow:”.

      Add two lines to allow traffic from the internal appliance management network and Oracle VM management network.

      # Allow: Customization of authorization controls. If there are any
      # access control keywords then the default action is to DENY. Otherwise,
      # the default action is ALLOW.
      #
      # The order of the controls are important. All incoming connections are
      # tested against the controls based on order.
      #
      #Allow 127.0.0.1
      Allow 192.168.4.0/24
      Allow 192.168.140.0/24

   4. Save and close the file /etc/tinyproxy/tinyproxy.conf.

5. Restart the tinyproxy service and verify the installed version.

   # service tinyproxy start
   Starting tinyproxy: [ OK ]
   # tinyproxy -version
   tinyproxy 1.8.3

6. Repeat this procedure on the other management node.