Installing Sun SNMP Management Agent on the N1 Provisioning Server

If you are going to use an SNMP-based monitoring and management tool such as Sun Management Center, to manage and control your blade system chassis and blades, you must install the Sun SNMP Management Agent on the control plane server. Refer to Sun SNMP Management Agent Guide for the Sun Fire B1600 for installation and configuration details.

Depending on the platform type, you can employ the following agents:

• A domain agent, running on Sun Fire B10n, B100s, B100x, and B200x server blades for domain hardware monitoring.

  The software is installed locally on the server being monitored and only that server can be monitored. In the case of the Sun Fire B1600, each server blade is monitored separately.

  The scope of domain hardware monitoring for the Sun Fire B100s blade is limited to the hardware of the blade only. The scope does not include other Sun Fire B1600 components such as the service indicators, power supply units (PSUs), SSCs and the identity of the Blade System Chassis itself.

• A platform agent, proxied through a system controller (platform hardware monitoring).

  The software is installed on the control plane server, which functions as the platform agent server to access chassis instrumentation through the system controller. This setup enables you to monitor all the hardware managed by the system controller.

  The scope of platform hardware monitoring for a Sun Fire B1600 includes the Blade System Chassis, its identity, service indicators, and all its field replaceable units (FRUs). In addition, some hardware information, specifically voltage monitoring, about the Sun Fire B100s blades is available that is not available using domain hardware monitoring.

For N1 provisioning, install the platform agent on the control plane server. After you install the platform agent packages, you need to configure both the control plane server and the B1600 chassis to use the platform agent. See Sun SNMP Management Agent Guide for the Sun Fire^TM B1600 for details.

When you install and configure the Sun SNMP Management Agent according to the instructions in Sun SNMP Management Agent Guide for the Sun Fire^TM B1600, be sure to perform the following tasks:

• Where installation instructions say to make sure that you have installed Java 1.4. Note that for N1 Provisioning, JRE 1.4.1_01 has already been installed on the N1 Provisioning Server and the server blades. Consequently, you need to modify the Sun SNMP Management Agent startup scripts. Follow the instructions in Appendix A, Editing the Startup Scripts of Sun SNMP Management Agent Guide for the Sun Fire^TM B1600.

• Step 5 in Installing Software for Domain Hardware Monitoring, Chapter 10 of Sun SNMP Management Agent Guide for the Sun Fire B1600 says to see Chapter 11 to configure the software. To accommodate N1 Provisioning while editing the General, Mediator, and Master Agent Configuration files, use cp for the manager variable name.

• Step 5 in Installing Software for Platform Hardware Monitoring, Chapter 10 of Sun SNMP Management Agent Guide for the Sun Fire B1600 says to see Chapter 11 to configure the software. If you have not done so already, you need to install the following Solaris packages on the N1 Provisioning Server before you install any Sun SNMP Management Agent packages:

  • SUNWmibii

  • SUNWsacom

  • SUNWsadmi

  • SUNWsasnm

• The N1 SNMP Trap Listener and Receiver by default listens for traps on port 162, which is also the port used by the Solstice Enterprise Agents^TM master agent, snmpdx. If you install the Sun SNMP Management Agent, the N1 Provisioning SNMP Trap Listener and Receiver ports need to be changed by allocating two free open ports, one for listening and one for sending traps by adding the following lines in the /etc/opt/terraspring/tspr.properties file:

  com.terraspring.mlg.SnmpConf.SnmpTrapReceivePort=Port for Receiving Traps
  com.terraspring.mlg.SnmpConf.SnmpTrapSendPort=Port for Sending Traps
  

  After you add these lines, restart the SNMP Trap Receiver on the N1 Provisioning Server by executing the following commands:

  /opt/terraspring/sbin/snmpd stop /opt/terraspring/sbin/snmpd start

• The communication between the server blades and the N1 Provisioning Server is blocked by IP Filter. Consequently, ports 161 and 162 need to be opened on the N1 Provisioning Server to allow the Sun SNMP Management Agent software to communicate. To open these ports on the N1 Provisioning Server for Sun SNMP Management Agent, you need to add the following lines to the /etc/opt/ipf/ipf.conf file:

  pass in quick proto udp from any to any port = 162 # allow SNMP Trap pass in quick proto udp from any to any port = 161 # allow SNMP commands

  Also, because you must change the N1 Provisioning SNMP Trap Listener and Receiver ports, addressed in the previous item, you need to add the following lines to the /etc/opt/ipf/ipf.conf file as well:

  pass in quick proto udp from any to any port=Port Number for Receiving Traps pass in quick proto udp from any to any port=Port Number for Sending Traps

  After you have added these lines, restart the ipf daemon by using the following command:

  /etc/rc2.d/S65ipfboot reload