Sun SNMP Management Agent
Release Notes, Version 1.6.1 | 
   |
| C H A P T E R 1 |
This document contains release- and platform-specific information for the Sun™ Simple Network Management Protocol (SNMP) Management Agent software, Version 1.6.1, including procedures for installing and uninstalling the software. Use this document with the Sun SNMP Management Agent Administration Guide for Sun Supported Servers, Version 1.6.1 at a Minimum.
The following summarizes the operational changes from the Version 1.6 software to the Version 1.6.1 software:
Sun SNMP Management Agent, Version 1.6.1, requires Solaris OS 10 at a minimum. Earlier versions of Solaris OS are not supported.
Check the documentation for your platform for information about any other Solaris OS requirements.
Required Solaris OS packages are available from the Solaris™ 10 Operating System DVD, under:
/cdrom/cdrom0/s0/Solaris_10/Product
These additional packages must be installed to enable support of the SNMP Management Agent. For a list of these packages refer to “Installation and Additional Required Packages” in the Sun SNMP Management Agent Administration Guide for Sun Supported Servers.
The following table lists all platforms supported in this release with reference to documentation specific to that platform.
Sun SNMP Version 1.6 software installation packages are supplied in the zip archive bundle SNMP-1_6_1-GA.tar.Z, at the following location:
Always use the latest version of this file for installation. For information about installation, refer to Installing the Software.
The installation packages in TABLE 1-2 and the additional required packages listed in TABLE 1-3 must be installed to enable support of the SNMP Management Agent. For information about obtaining these packages, refer to Obtaining Installation Packages.
The following table lists all packages contained in the tar archive bundle.
The packages listed in the following table must be installed to enable support of the SNMP Management Agent.
To upgrade the software, you must remove the existing software before reinstalling the new version. For more information, refer to Uninstalling the Software.
A new startup file is created in /etc/init.d, as shown in the following table, with links to /etc/rcn.d.
| Component | Startup Script | Package Name | Package Description |
|---|---|---|---|
| Agent | masfd | SUNWmasfr | Configuration and startup script for SNMP agent |
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.
This section describes the procedures for installing the monitoring software.
Before installing the software, ensure that:
You have the requisite level of the Solaris OS installed on both the domain or target and the platform agent server. (See Solaris Operating System.)
You have installed all the necessary patches (refer to Solaris OS Patches) and any additional essential packages (TABLE 1-3) not supplied as part of the SNMP software.
If you are installing on a domain in an LDoms environment, you must install the software on the control domain.
When you are certain that your system meets all these requirements, you can proceed to install the SNMP software.
$ zcat unzip SNMP-zip | tar xvf - |
Ensure you are the superuser before proceeding with installation.
Change to the directory where the zip file was extracted (at the root of the packages provided by the zip file).
If you want to start installation from a different directory, when using the pkgadd(1M) command 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 |
Install the support for platform instrumentation by doing one of the following depending on your platform:
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 Sun Fire T2000, Netra T2000, Sun Blade T6300, T6320, T6340 and Sun SPARC Enterprise T5120/T5220, T5140, T5240, T5440 instrumentation.
# pkgadd -d . SUNWesonl SUNWespdl SUNWescdl |
# pkgadd -d . SUNWmasf SUNWmasfr |
Ensure that the packages have been installed properly.
Display information for the installed packages using pkginfo. For example:
# pkginfo SUNWmasfr system SUNWmasfr Sun SNMP Management Agent for Sun Fire and Netra Systems |
Ensure that the following files now exist:
/etc/init.d/masfd
/etc/rc{0..2,S}.d/K40masfd
/etc/rc3.d/S80masfd
/opt/SUNWmasf/lib/mibs
|
Ensure that the agent is running, by using:
# netstat -anv | grep agent_port |
# netstat -anv | grep 9000
*.9000 Idle
|
You might experience a delay of up to 15 minutes before seeing the response to this netstat command.
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 using the agent, you must assign it a network port to use. In deciding which network port to use, consider:
Configure the SNMP agent using the /etc/opt/SUNWmasf/conf/snmpd.conf file.
Set the port number by adding a line to the file in the form:
agentaddress 9161 |
This enables the agent to communicate on the port 9161. Make sure 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 which case you must specify the trap destinations. Refer to the “Configuratin Files” chapter in the administration guide for more information.
Restart the Platform Information and Control Library (PICL) daemon:
# svcadm restart picl |
# /etc/init.d/masfd start |
Confirm that the agent is correctly running:
# 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.
Verify that the agent is running.
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.
Generally, all that is required to uninstall SNMP is to use the pkgrm(1M) command to remove the packages you installed. This section specifies all the relevant files and links to remove for various platforms.
| Caution - If you have also installed Sun Management Center, remove only the SNMP-specific packages SUNWmasfr and SUNWmasf. |
Do one of the following depending on your platform:
Remove the Sun Fire V125/V210, V215, V240, V245, and Netra 210/240 platform agent packages from the platform agent server.
# pkgrm SUNWmasfr SUNWmasf SUNWescpl SUNWescdl |
Remove the Sun Fire V250 platform agent packages from the platform agent server.
# pkgrm SUNWmasfr SUNWmasf SUNWescfl SUNWescdl |
Remove the Sun Fire V440/V445 platform agent packages from the platform agent server.
# pkgrm SUNWmasfr SUNWmasf SUNWeschl SUNWescdl |
Remove the Netra 440 platform agent packages from the platform agent server.
# pkgrm SUNWmasfr SUNWmasf SUNWescnl SUNWescdl |
Remove the Sun Fire T1000 platform agent packages from the platform agent server.
# pkgrm SUNWmasfr SUNWmasf SUNWescdl SUNWespdl SUNWeserl |
Remove the Sun Fire T2000, Netra T2000, Sun Blade T6300, T6320, T6340 and Sun SPARC Enterprise T5120/T5220, T5140, T5240, T5440 platform agent packages from the platform agent server.
# pkgrm SUNWmasfr SUNWmasf SUNWescdl SUNWespdl SUNWesonl |
This section contains general issues and specific bugs concerning the Sun SNMP Management Agent, Version 1.6 software.
This section describes general known issues about this release of Sun SNMP Management Agent software that are broader than a specific bug number. Workarounds are provided where available.
Before you run the SNMP daemon, restart the Platform Information and Control Library (PICL) daemon by typing:
# svcadm restart picl |
This section summarizes the bugs that you might encounter when using this version of the software. The bug descriptions are in numerical order by bug ID. If a workaround is available, it is specified.
Bug ID 6628809: On Sun Blade T6320 systems, the SNMP tree does not have entities for the Network Express Module (NEM) components.
Workaround: Use the showfru command to view these FRUs.
sc> showfru |
Bug ID 6641519: When a PCI Express Module (PCI-EM) is unconfigured, it is deleted from the SNMP tree, and the slot is reported empty, even though module is still there physically. Conversely, when a PCI-EM is connected to the system, the SNMP tree does not show it, and the slot is reported empty, until the module is configured.
Workaround: Use the following Solaris OS cfgadm(1M) command to check the occupancy status of PCI-EMs.
# cfgadm -al | grep PCI-EM |
Bug ID 6850760: When the MASF SNMP agent is configured as a sub-agent of SMA and started, you will see an error message on the console similar to this:
# Jun 10 12:46:07 dt88-192 snmpd[3258]: registering pdu failed: 263! Jun 10 12:46:07 dt88-192 last message repeated 64 times |
|
Sun SNMP Management Agent
Release Notes, Version 1.6.1 | 821-0654-10 |
|
Copyright © 2009, Sun Microsystems, Inc. All rights reserved.
for
the latest set of patches for your product:
Install the SNMP Agent