Sun SNMP Management Agent
Release Notes, Version 1.5.5 | 
   |
| 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, Version 1.5.5. Use this document with the Sun SNMP Management Agent Administration Guide for Sun Supported Servers, Version 1.5.3, 819-7978-13.
The Sun Netra™ 5440 Server is 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:
Sun SNMP Version 1.5.5 software installation packages are supplied in the zip archive bundle SNMP-1_5_5-GA.tar.Z, at the following location:
http://wwws.sun.com/software/download/index.html
If you do not see the listing for Sun SNMP 1.5.5 under New Downloads, use the A-Z Index of All Products to find the software. 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.5.3.
For some configurations, the /etc/opt/SUNWmasf/conf/snmpd.conf file must be edited before the SNMP agent is started. The line to be edited is currently commented out, and it specifies which alternate configuration file to use.
# SUNW_masfForceConfigFile sun-blade-t6300-c48.conf |
The following table lists the system configurations for which an alternate configuration file has to be specified.
No patches must be installed in addition to the standard Solaris
Operating System software at this time. To ensure the latest patch
information, always go to SunSolve
for
the latest set of patches for your product:
This section describes known issues in SNMP 1.5.5 software.
Before you run the SNMP daemon, restart the Platform Information and Control Library (PICL) daemon by typing:
# svcadm restart picl |
An accurately plumbed and configured network interface is required for the SNMP Management Agent for Sun Fire (MASF) operation. When one or more XAUI 10-gigabit PCI-Express (PCI-E) network cards are installed in a T5x40 system, the cards disable the corresponding network ports 0 and 1. If one of these cards is installed in PCI-E card slot 1, and the card is not going to be used as the default system network interface, select and configure either network port 2 or port 3 to use as the system default interface.
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.
The SNMP agent incorrectly identifies Sun Fire V210, V240, and V250 field replaceable units (FRUs).
Note - This bug does not apply to the Sun Fire V440 and Netra 440 platforms. |
The SNMP agent reports the following items as having an incorrect entPhysicalIsFRU property:
The serial number and host name are not provided in the sunPlatNotificatAdditionalText property of the sunPlatEquipmentAlarm and sunPlatEnvironmentalAlarm traps for the Netra 1280 and Sun Fire 1280 servers.
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.
Currently, the value of the entPhysicalSerialNum provided by the chassis (:ch) node is set to the serial number associated with the chassis containing the Sun Blade T6300 Server Module. The serial number used in entPhysicalSerialNum for the :ch node should be changed to the product serial number of the blade. The product serial number is the number assigned to the blade at manufacturing. If this number is not available, the serial number for the :ch node should be set to the serial number of the motherboard FRU.
On Sun Blade T6320 systems, the SNMP tree does not have entities for the Redundant Array of Inexpensive Disks (RAID) Expansion Module (REM), Fabric Expansion Module (FEM), and Network Express Module (NEM) components.
Workaround: Use the showfru command to view these FRUs.
sc> showfru |
When a PCI Express module (PCI-EM) is unconfigured, it is deleted from the SNMP tree (and the slot is reported empty) even though it is physically still there. Conversely, when a PCI-EM is plugged into the system, the SNMP tree does not show it (and the slot is reported empty) until it is configured.
Workaround: Use the Solaris OS cfgadm(1M) command to check the occupancy status of PCI-EMs.
# cfgadm -al | grep PCI-EM |
When a fan module with multiple fan units per module is unplugged, no fan unit deletion traps are generated, although the fan units are deleted from the SNMP tree correctly. When the fan module is plugged in, no fan creation traps are generated, although the fan units are created correctly. Traps are generated correctly for fan tachometers and the fan module.
|
Sun SNMP Management Agent
Release Notes, Version 1.5.5 | 820-0174-15 |
|
Copyright © 2008, Sun Microsystems, Inc. All rights reserved.