Sun SNMP Management Agent
Release Notes, Version 1.6 | 
   |
| C H A P T E R 1 |
These release notes contain known issues and bugs that affect the Sun™ Simple Network Management Protocol (SNMP) Management Agent, Version 1.6 software. This document also includes changes for this release, supported platforms, required patches, locations of software and documentation, and other pertinent information about this release. Use this document with the Sun SNMP Management Agent Administration Guide for Sun Supported Servers, Version 1.6 at a Minimum, 820-5965-10.
Version 1.6 of the Management Agent for Sun Fire (MASF) represents a major architectural and design change from the Version 1.5 MASF. There have been no functional Management Information Base (MIB) changes between the two releases. The ENTITY-MIB and SUN-PLATFORM-MIB are implemented the same as before.
The following summarizes the operational changes from the Version 1.5 software to the Version 1.6 software:
Significant performance improvement in processing SNMP requests.
Reduction in the number of traps generated on object removal and insertion:
Some changes to text strings in the entPhysicalTable. Some minor differences to other entities, including entPhysicalDescr and entPhysicalName.
Only disk and removable media drives that are internal to the chassis are shown.
Reduction in the number of components provided in the entPhysicalTable. All the important internal components of the system still exist.
In Version 1.5 software when a numeric sensor reading crossed a threshold, the trap generated had sunPlatNotificationObject set to the parent of the sensor and sunPlatNotificationAdditionalText set to the entPhysicalName of the sensor. In some instances this could be confusing, so now in Version 1.6 software, sunPlatNotificationObject is set to the sensor causing the fault. The value of sunPlatNotificationAdditionalText remains unchanged. Network management applications can use the value of entPhysicalContainedIn to find the parent of the sensor.
In Version 1.5 software for object creation and deletion traps, the sunPlatNotificationObject had the value of the parent of the object that was created or deleted. This has changed in the Version 1.6 software, and the sunPlatNotificationObject now reflects the object that is created or deleted rather than the parent.
Also in Version 1.5 software, the sunPlatNotificationAdditionalText could be included optionally. This value is no longer needed in Version 1.6 software and has been removed.
The following changes are to configuration options in the /etc/opt/SUNWmasf/conf/snmpd.conf file:
With Version 1.5 software, you could define a trapsink or trap2sink with just the host name. Now in Version 1.6 software, you must specify the trapsink or trap2sink by including the host name, community string, and port number. For more information, refer to Chapter 3, Configuration Files, “Setting Up Trap Destinations” in the Sun SNMP Management Agent Administration Guide for Sun Supported Servers Version 1.6 at a Minimum.
As of Version 1.6 software, the agent listens for SNMP requests over all configured IP interfaces using the specified port. If you want a different configuration, refer to Chapter 3, Configuration Files, “Setting Up the Port Number” in the Sun SNMP Management Agent Administration Guide for Sun Supported Servers Version 1.6 at a Minimum.
The snmpd.conf parameter SUNW_masfForceConfigFile is no longer required and is considered an error if present.
The snmpd.conf parameter SUNW_alwaysIncludeEntPhysName is no longer used. The sunPlatNotificationAdditionalText is included in all traps.
This section contains system requirements for running the Sun SNMP Management Agent, Version 1.6 software.
The following platforms are supported as of this release:
The following table lists all platforms supported in this release with reference to documentation specific to that platform. Platform documentation can be found at:
At a minimum, the Sun SNMP Management Agent 1.6 software requires one of these versions of Solaris Operating System (OS):
Refer to 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.
Sun SNMP Version 1.6 software installation packages are supplied in the zip archive bundle SNMP-1_6-GA.tar.Z, at the following location:
http://wwws.sun.com/software/download/index.html
Always use the latest version of this file for installation.
Additional required 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 Administration Guide for Sun Supported Servers, Version 1.6.
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.
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 6458182: You cannot run the SNMP MASF and the Sun Management Center at the same time on sun4v servers because of a resource conflict.
Workaround: Run either the SNMP MASF or the Sun Management Center alone.
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 |
|
Sun SNMP Management Agent
Release Notes, Version 1.6 | 820-5966-12 |
|
Copyright © 2009, Sun Microsystems, Inc. All rights reserved.
for
the latest set of patches for your product: