1. Sun SNMP Management Agent Version 1.6.2 Release Notes
Oracle Solaris Operating System
Obtaining Oracle Solaris OS Packages
Obtaining Installation Packages
Restart PICL Before Running SNMP
Do Not Run SNMP MASF and Sun Management Center at the Same Time
Bugs Affecting SNMP Management Agent 1.6.2 Software
Fan Module 5 is not Hot-Swappable in Netra SPARC T3-1 and Netra SPARC T4-1 Servers (CR 7043996)
Setting MASF SNMP Agent as Subagent of SMA Causes Harmless Messages (CR 6850760)
You must install the installation packages in SNMP Management Agent Software Installation Packages to enable support of the SNMP management agent. For information about obtaining these packages, see Obtaining Installation Packages.
The following table lists all packages contained in the tar archive bundle.
Table 1-2 SNMP Management Agent Software Installation Packages
|
To upgrade the software, you must remove the existing software before reinstalling the new version. For more information, see Uninstalling the Software.
When you install the packages, a new startup file is created in /etc/init.d, as shown in the following table, with links to /etc/rcn.d.
Table 1-3 Startup Script
|
After installation, the following MIBs, supported by the agent, are located in the directory /opt/SUNWmasf/lib/mibs. All other MIBs in that directory are included for reference purposes.
Table 1-4 MIB Files
|
This section includes the procedures for installing the monitoring software.
Before installing the software, ensure that:
You have the requisite level of the Oracle Solaris OS installed on both the domain or target, and on the platform agent server (see Oracle Solaris Operating System).
You have installed all the necessary patches (see Oracle Solaris OS Patches).
If you are installing on a domain in a logical domains environment, you must install the software on the control domain.
When you are certain that your system meets all these requirements, you can proceed with installing the SNMP software.
$ zcat unzip SNMP-zip | tar xvf -
You can start installation from a different directory. In that case, when using the pkgadd(1M) command (as shown in Step 4), you must specify the path of the root of the directory hierarchy where the files were extracted using the -d option (rather than -d . as shown in Step 4).
![]() | Caution - If you have installed Sun Management Center, you cannot run both Sun Management Center and this agent at the same time on any chip multithreaded (CMT) platform. Otherwise, you can skip to Step 5. |
Install the Sun Fire V125/V210/V215/V240/V245 and Netra 210/240 instrumentation:
# pkgadd -d . SUNWescdl SUNWescpl
Install the Sun Fire V250 instrumentation.
# pkgadd -d . SUNWescdl SUNWescfl
Install the Sun Fire V440 and V445 instrumentation.
# pkgadd -d . SUNWescdl SUNWeschl
Install the Netra 440 instrumentation.
# pkgadd -d . SUNWescdl SUNWescnl
Install the Sun Fire T1000 instrumentation.
# pkgadd -d . SUNWeserl SUNWespdl SUNWescdl
Install the instrumentation for: Sun Fire T2000, Netra T2000, T5220, T5440, Sun Blade T6300, T6320, T6340, SE T5220, T5120, T5140, T5240, T5440, SPARC T3-1, T3-1B, T3-2, T3-4, Netra SPARC T3-1, Netra SPARC T4-1.
# pkgadd -d . SUNWesonl SUNWespdl
# pkgadd -d . SUNWmasf SUNWmasfr
# pkginfo SUNWmasfr system SUNWmasfr Sun SNMP Management Agent for Sun Fire and Netra Systems
/etc/init.d/masfd /etc/rc{0..2,S}.d/K40masfd /etc/rc3.d/S80masfd /opt/SUNWmasf/lib/mibs
You are now ready to configure the SNMP agent.
After installation, you must configure the agent before you attempt to start it. A full description of the configuration options for the SNMP agent is provided in the Sun SNMP Management Agent Administration Guide for Sun Supported Servers. Refer to the “Configuration Files” chapter.
Before You Begin
Before using the agent, you must assign it a network port to use. In deciding which network port to use, consider:
Whether other SNMP agents might be installed on the system
Where management applications might attempt to discover SNMP agents
Note - Use a port other than 161 for SNMP access to the agent provided by this product to ensure that this port is available for use by other agents, such as snmpdx(1M) and Sun Management Center. The conventional port for SNMP access is port 161 for data. By default, the Oracle Solaris snmpdx daemon uses this port.
agentaddress 9161
This setting enables the agent to communicate on port 9161. Ensure that the port you select is not currently in use by another application. If you are using SNMPv1 or SNMPv2c, no further configuration is required unless you want to use traps. In that case, you must specify the trap destinations. Refer to the “Configuration Files” chapter in the Sun SNMP Management Agent Administration Guide for Sun Supported Servers for more information.
# svcadm restart picl
# /etc/init.d/masfd start
# ps -ef | fgrep snmpd
You should see a line of the form:
root 29394 1 0 Feb 18 ? 4:11 /opt/SUNWmasf/sbin/snmpd
If you do not see this output, review the /var/adm/messages log file to locate any error messages from the agent. For more information on troubleshooting, see the “Troubleshooting” chapter in the Sun SNMP Management Agent Administration Guide for Sun Supported Servers.
On subsequent reboots, the agent starts automatically without any user intervention.
Ensure that the agent is running, by typing:
# netstat -anv | grep agent_port
For example, where agent_port is 9161:
# netstat -anv | grep 9161 *.9161 Idle
You might experience a delay of up to 15 minutes before seeing the response to this netstat command.
Once the agent is fully operational, look in the syslog log file for a string similar to this:
NET-SNMP version 5.4.2.1
You might experience a delay of up to 15 minutes before the string appears in the file.