Home

Sun SNMP Management Agent Administration Guide for Sun Fire

Contents

1. Physical Model on page 55 Logical Model on page 58 Logical and Physical Hierarchy Mapping on page 59 Event and Alarm Model on page 59 SUN PLATFORM MIB on page 59 SNMP Representation of the Model The SNMP agent supports both management agent system and also a logical representation of the administrative domains within it are provided by the ENTITY MIB as defined by RFC 2737 extended by the SUN PLATFORM MIB Note Many of the objects defined in the MIBs have a MAX ACCESS of read write but these objects are only writable where such an operation is appropriate to the component being modeled The ENTITY MIB contains the following groups which describe the physical and logical elements of the managed system 53 entityPhysical Group The entityPhysical group describes the physical entities identifiable physical resources managed by the agent for example chassis power supplies sensors and so forth These entities are represented by rows in the entPhysicalTable entityLogical Group The entityLogical group describes the logical entities managed by the agent These are representations of logical entities providing abstractions of service that can be managed by higher levels of management These are primarily concerned with platform hardware management and include functions such as OS reboot hardware reset and power control Typically they correspond to administrative domains such
2. Class Attribute Mapping entPhysicalClass sunPlat Class chassis 3 sunPlatChassis backplane 4 Not implemented container 5 sunPlatEquipmentHolder powerSupply 6 sunPlatPowerSupply fan 7 sunPlatFan sensor 8 sunPlatSensor plus subclasses module 9 sunPlatCircuitPack port 10 Not implemented 68 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 TABLE 10 1 Physical Entity Superclass Class Attribute Mapping Continued entPhysicalClass sunPlat Class stack 11 Not implemented other 1 sunPlatEquipment plus subclasses unknown 2 Not implemented m Index This integer uniquely identifies the entry in the Physical Entity Table that identifies the managed object Values are not pre allocated and might vary on each invocation of the agent m Containedin This integer represents the Index attribute of the managed object containing this managed object The attribute therefore models the relationship between the managed objects Note The object at the root of the physical containment hierarchy typically a chassis is not physically contained within another entity represented in the table To indicate this its entPhysicalContainedIn value is set to 0 m FirmwareRev This is a text string containing the manufacturer s firmware revision information for the resource Not all hardware resources have associated firmware revision information m SoftwareRev This is a text
3. Copyright 2006 Sun Microsystems Inc 4150 Network Circle Santa Clara Californie 95054 Etats Unis Tous droits r serv s Sun Microsystems Inc a les droits de propriete intellectuels relatants la technologie qui est d crit dans ce document En particulier et sans la limitation ces droits de propri t intellectuels peuvent inclure un ou plus des brevets am ricains num r s a http www sun com patents et un ou les brevets plus suppl mentaires ou les applications de brevet en attente dans les Etats Unis et dans les autres pays Ce produit ou document est prot g par un copyright et distribu avec des licences qui en restreignent l utilisation la copie la distribution et la d compilation Aucune partie de ce produit ou document ne peut tre reproduite sous aucune forme par quelque moyen que ce soit sans l autorisation pr alable et crite de Sun et de ses bailleurs de licence s il y en a Le logiciel d tenu par des tiers et qui comprend la technologie relative aux polices de caract res est prot g par un copyright et licenci par des fournisseurs de Sun Des parties de ce produit pourront tre d riv es des syst mes Berkeley BSD licenci s par l Universit de Californie UNIX est une marque d pos e aux Etats Unis et dans d autres pays et licenci e exclusivement par X Open Company Ltd Sun Sun Microsystems le logo Sun Sun Fire Netra et Solaris sont des marques de fabrique ou des marques d pos es de Sun
4. setting number 12 Power Supply Table extension 61 R rack 71 relationships 49 replaceable hardware resource 71 resource hierarchy 49 rocommunity 15 rouser 15 routing tables 44 rwcommunity 15 rwuser 15 S Sensor Table extension 60 sensors binary 36 80 discrete 83 numeric 37 80 setting port number 12 trap destinations 13 shelf 71 Simple Network Management Protocol 1 SNMP traps 44 SNMP agent installing 7 updating 23 SNMPv3 access 12 configuration 20 software installing 7 packages 5 uninstalling 31 software alarms 77 state 67 subclasses 51 sunPlat classes 65 sunPlatAlarm class 77 sunPlatBattery class 75 sunPlatBinarySensor class 80 sunPlatChassis class 83 sunPlatCircuitPack class 71 sunPlatDiscreteSensor class 83 sunPlatEquipment class 69 sunPlatEquipmentHolder class 72 sunPlatFan class 78 94 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 SUN PLATFORM MIB 46 53 58 59 63 sunPlatNumericSensor class 80 sunPlatPowerSupply class 74 sunPlatSensor superclass 79 sunPlatWatchdog class 75 superclass 51 syscontact 21 syslocation 21 sysname 21 sysservices 21 system information settings 21 T table definition 46 Physical Entity 56 Physical Mapping 56 Table Extensions 60 tables 44 thresholds 86 timeout 76 trap destinations setting 13 trap2sink 13 trapcommunity 13 traps 8 11 alarm status 91
5. CPU module All power supply indicators and sensors are contained by the power supply module All SCSI disks and tape drives attached to the SCSI port on the chassis are contained by that SCSI port Netra 210 240 System All memory banks are contained by the motherboard The CPU temperature and voltage sensors are contained by the processor All power supply indicators and sensors are contained by the power supply module All SCSI disks and tape drives attached to the SCSI port on the chassis are contained by that SCSI port Drives external to the chassis connected to a PCI card are contained within the object representing the PCI slot in which the card is inserted Netra 440 System The CPU memory module slots PCI slots and system controller slot are contained in the system board The CPU and memory banks are contained in the CPU Memory module All power supply indicators and sensors are contained by the power supply module All SCSI disks and tape drives attached to the SCSI port on the chassis are contained by that SCSI port 34 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 m Drives external to the chassis connected to a PCI card are contained within the object representing the PCI slot in which the card is inserted Sun Fire V1280 E2900 and Netra 1280 1290 Systems The current agent version provides fault monitoring for the power supplies and fans When faults are detected one or more sunP
6. Overview 85 Standard Trap Properties 87 Trap Types 88 Object Creation and Deletion Traps 89 Property Change Traps 89 Environmental and Status Alarm Traps 91 Contents vii viii Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 FIGURE 8 1 FIGURE 8 2 FIGURE 9 1 FIGURE 10 1 Figures Hardware Resource Hierarchy Example 50 SunPSM Managed Object Class Inheritance Diagram 51 Physical Containment Hierarchy Example 55 The sunPlat Physical Resource Inheritance Class Diagram 66 x Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Tables TABLE 2 1 TABLE 2 2 TABLE 2 3 TABLE 2 4 TABLE 3 1 TABLE 6 1 TABLE 9 1 TABLE 9 2 TABLE 9 3 TABLE 9 4 TABLE 10 1 TABLE 10 2 TABLE 10 3 TABLE 10 4 TABLE 10 5 TABLE 10 6 TABLE 10 7 TABLE 10 8 TABLE 10 9 SNMP Management Agent Software Installation Package Descriptions 5 SNMP Management Agent Additional Required Software Packages 5 Startup Script 6 MIB Files 6 Internet Protocol Layer Functionality 22 Numeric Sensor Mapping 37 Physical Entity Table 56 Physical Mapping Table 57 Physical Entity Table Extensions 62 Key to Physical Entity Table Extensions 63 Physical Entity Superclass Class Attribute Mapping 68 Operational State Attribute Values 70 Availability Status Attribute Values 72 Equipment Holder Type Attribute Values 73 Equipment Holder Status Attribute Values 74 Watc
7. Sensor Table Extension This extends the Sensor Table Extension It provides additional information relevant for managed objects of the entPhysicalClass sensor 8 and sunPlatSensorClass numeric 2 a Discrete Sensor Table Extension 60 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 This extends the Sensor Table Extension It provides additional information relevant for managed objects of the entPhysicalClass sensor 8 and sunPlatSensorClass discrete 3 m Fan Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the entPhysicalClass fan 7 a Alarm Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the entPhysicalClass other 1 and sunPlatPhysicalClass alarm 8 m Watchdog Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the entPhysicalClass other 1 and sunPlatPhysicalClass watchdog 3 typically representing service indicator LEDs m Power Supply Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the ent PhysicalClass powerSupply 6 TABLE 9 3 shows an example of the Table Extensions to the Physical Entity Table The entPhysicalIndex column 1 in this table is based on the exam
8. as Solaris domains or service controllers entityMapping Group The entityMapping group identifies the relationship between the entityPhysical group and the entityLogical group entityGeneral Group The entityGeneral group provides the last change time stamp for the time when any entity in the Physical Entity Table or Physical Mapping Table is changed entityMIBTraps Group The entityMIBTraps group defines the entConfigChange notifications used to signal a change to the last change time stamp Chapter 7 provides an overview of how the generic elements of SNMP represent the Sun platform SNMP model 1 These groups are not currently populated but might be so in the future 54 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Physical Model The SunPSM physical model uses the ENTITY MIB to provide a containment hierarchy of hardware entities Each entity is modeled as a separate row of the ENTITY MIB s entPhysicalTable FIGURE 9 1 shows an example of a physical containment hierarchy The number in the bottom right corner gives the index to the corresponding row in the entPhysicalTable TABLE 9 1 3 6 Alarm Device g Sensor Numeric 7 Battery 12 Watchdog 10 Sensor Discrete 44 FIGURE 9 1 Physical Containment Hierarchy Example Chapter 9 Sun SNMP Management Agent MIBs 55 This information is presented using SNMP tables m Physical entity tabl
9. beyond the scope of this document For reference the structure of the MIBs for SNMPv2c is defined by its Structure of Management Information SMI defined in RFC2578 This defines the syntax and basic data types available to MIBs The textual conventions type definitions defined in RFC2579 define additional data types and enumerations MIB Tables Much of the data content defined by MIBs is in tabular form and organized as entries consisting of a sequence of objects each with its own OIDs For example a table of fan characteristics could consist of a number of rows one per fan with each row containing columns corresponding to the current speed the expected speed and the minimum acceptable speed Chapter 7 Introduction to SNMP 45 46 The addressing of the rows within the table can be as follows a Simple single dimensional index a row number within the table for example 6 a More complex multidimensional instance specifier such as an IP address and port number for instance 127 0 0 1 1234 Each table definition within the MIB has an INDEX clause that defines which instance specifiers to use to select a given entry In either case the objects used to define the index to the required row must themselves be defined within the MIB Thus a table with a simple single dimensional index typically has an index column that is referenced by the table s INDEX clause A specific data item within a table is then addressed by s
10. changes This trap is used for all OID property value changes Depending on the object type causing the trap different attributes in the trap body are used to supply both before and after values of the changed attribute Note The sunPlatNotification prefix has been omitted from the following attribute names for clarity m OldInteger This attribute is used for sunPlatStateChange and sunPlatAttributeChangeInteger traps The attribute provides the original value of the object identified by sunPlatNotificationChangedOID mw NewlInteger This attribute is used for sunPlatStateChange and sunPlatAttributeChangeInteger traps The attribute provides the new value of the object identified by sunPlatNotificationChangedOID m OldString This attribute is used by the sunPlatAttributeChangeString trap This is the original value of the object identified by sunPlatNotificationChangedoOID m NewString This attribute is used by the sunPlatAttributeChangeString trap This is the new value of the object identified by sunPlatNotificationChangedOID m OldOID This attribute is used by the sunPlatAttributeChangeOID trap This is the original value of the object identified by sunPlatNotificationChangedoII J m NewOID This attribute is used by the sunPlatAttributeChangeOID trap This is the new value of the object identified by sunPlatNotificationChangedOID 90 Sun SNMP Management Agent for Sun Fire and Netra Systems
11. environment configure access control as described below If there are systems that are to receive traps provide a list of such hosts to the agent as described in Setting Up Trap and or Inform Destinations on page 13 If SNMPv3 access is required further configure SNMPv3 and SNMPv3 users and views as described in SNMPv3 Configuration on page 20 If the management applications using the agent are likely to require information in the MIB II system branch refer to Setting System Information on page 21 You can add comments to the configuration file by making the first character on the comment line Setting Up the Port Number Configure the port number using the agentaddress keyword agentaddress lt transport specifier gt lt transport address gt This makes the agent listen on the specified comma separated list of listening addresses At least one port must be specified for the agent to function The transport specifier should always be set to udp The transport address is of the form hostname lt port gt or lt IPv4 address gt lt port gt For example specifying agent address as agentaddress 8161 localaddress 9161 makes the agent listen on UDP port 8161 on all IPv4 interfaces and UDP port 9161 only on the interface associated with the localhost address The agent MUST have a port number configured before it will start No default value is provided f
12. environmental 91 object creation 89 object deletion 89 property change 89 standard properties 87 types 88 trapsink 13 troubleshooting access permissions 27 agent access 27 network ports 26 traps 27 V VACM 14 default model 19 view 18 view based access control See VACM WwW Watchdog Table extension 61 95 96 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006
13. hardware revision information for the resource Not all hardware resources have associated hardware revision information Chapter 10 Physical Model 67 mg Name This is a text string containing the logical name by which the resource is known to the operating system and associated utilities This name can be a device node or a defined name used by system utilities where applicable Not all resources have a device name m ModelName This is a text string containing the manufacturer s customer visible part number or part definition Not all hardware resources have associated part numbers or definitions m SerialNum This is a text string containing the manufacturer s serial number for the resource Not all hardware resources have associated serial numbers m MfgName This is a text string containing the manufacturer s name for the resource Not all hardware resources have an associated manufacturer s name The Physical Entity superclass also contains attributes that are used for describing the hierarchy of hardware resources m Class This enumerated type contains an indication of the general hardware type of a particular physical resource The supported values of this class are defined by the ENTITY MIB This attribute can be used as an indication of the relevant Table Extensions for the managed object The mapping between the ENTITY MIB classes and the sunPlat classes are as shown in TABLE 10 1 TABLE 10 1 Physical Entity Superclass
14. not responsible or liable for any content advertising products or other materials that are available on or through such sites or resources Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content goods or services that are available on or through such sites or resources Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions You can submit your comments by going to http www sun com hwdocs feedback Please include the title and part number of your document with your feedback Sun SNMP Management Agent for Sun Fire and Netra Systems part number 817 2559 16 Preface xvii xviii Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 raat 1 Installation and Configuration CHAPTER 1 Sun SNMP Management Agent The Sun SNMP Management Agent enables access to system inventory and monitoring and provides support for alarms using the industry standard management protocol Simple Network Management Protocol SNMP The agent supports SNMPv1 SNMPv2c and SNMPv3 to enable interoperability with all common management applications The provision of SNMPv3 enables management accesses to be fully authenticated and secured The agent provides a management model based on the standard ENTITY MIB and is augmented by extensions that provide further informa
15. of a How applicable the operation is to the object being addressed for example where an object defined by the MIB represents a state machine for which only certain transactions are legal m Security restrictions that limit certain operations to restricted sets of managers The mechanism used to communicate security access rights in SMMPv1 is that of community strings These are simply text strings such as private and public that are passed with each SNMP data request As SNMPv1 and SNMPv2 requests are not encrypted this should not be considered secure The mechanism used to define which community strings the agent should respond to and from which manager depends on the implementation of the agent but is typically based on access control lists ACLs which are files describing applicable access permissions For a description of how to configure ACLs refer to Chapter 3 Chapter 7 Introduction to SNMP 47 48 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 8 Platform Management Model This chapter provides an overview of how SNMP models the hardware platform using the Sun platform SNMP model SunPSM The chapter contains the following sections a Modeling the Platform on page 49 a Managed Objects on page 50 a Derivation of sunPlat Classes on page 52 Modeling the Platform The server is represented as a collection of nested hardware resources within a chassis Som
16. other countries exclusively licensed through X Open Company Ltd Sun Sun Microsystems the Sun logo Sun Fire Netra and Solaris are trademarks or registered trademarks of Sun Microsystems Inc in the U S and in other countries All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc in the U S and in other countries Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems Inc The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems Inc for its users and licensees Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the Sop anes industry Sun holds a non exclusive license from Xerox to the Xerox Graphical User Interface which license also covers Sun s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun s written license agreements U S Government Rights Commercial use Government users are subject to the Sun Microsystems Inc standard license agreement and applicable provisions of the FAR and its supplements DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID
17. provides platform specific information for the supported platforms Part II Chapter 7 provides a brief introduction to the essential features of the Simple Network Management Protocol SNMP Chapter 8 provides an overview of how SNMP models the hardware platform Chapter 9 describes how the managed objects and their relationships are presented by the SNMP interface Chapter 10 describes the sunPlat physical class hierarchy and how the managed physical object classes defined in the sunPlat model are represented by the SUN PLATFORM MIB Chapter 11 describes the notifications classes and attributes as defined in the SUN PLATFORM MIB Using UNIX Commands This document might not contain information about basic UNIX commands and procedures such as shutting down the system booting the system and configuring devices Refer to the following for this information a Software documentation that you received with your system a Solaris Operating System documentation which is at http docs sun com xiv Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Shell Prompts Shell Prompt C shell C shell superuser Bourne shell and Korn shell Bourne shell and Korn shell superuser machine name amp machine name Typographic Conventions Typeface Meaning Examples AaBbCc123 The names of commands files Edit your Login file and directories on screen Use 1s a
18. string containing the manufacturer s software revision information for the resource Not all hardware resources have associated software revision information sunPlat Equipment Class The sunPlat Equipment class is used to represent the characteristics that are generic to all hardware resources This class contains attributes representing configuration and generic health status information This class is further subclassed to provide more detail configuration information and monitoring data for particular types of resources The entPhysicalClass is dependent on the subclass being represented The sunPlat Equipment class has the following attributes Chapter 10 Physical Model 69 Note The sunPlatEquipment prefix has been omitted from the following attribute names for clarity m AdministrativeState This read write attribute takes one of the following enumerated values representing the current administrative state of the resource a locked 1 a unlocked 2 a shuttingDown 3 m OperationalState This read only attribute is an enumerated type indicating whether the resource is physically installed and capable of providing service The attribute contributes to the state of the managed object and can take the values shown in TABLE 10 2 TABLE 10 2 Operational State Attribute Values Attribute Values Description disabled 1 The resource is totally inoperable and unable to provide service to the user enabled 2 The res
19. the agent as shipped is functionally equivalent to the following entries CODE EXAMPLE 3 3 Default VACM Model com2sec public default public group public v1 public group public v2c public group public usm public view all included 1 access public any noauth exact all none none Chapter 3 Configuration Files 19 SNMPv3 Configuration This section describes the command that enables the agent to respond to SNM_v3 messages Syntax engineID lt string gt You must configure the snmpd agent with an engineID so that it can respond to SNMPv3 messages If you do not configure an engineID the agent uses a default value of the engineID based on the first IP address found for the hostname of the machine If this is inappropriate for example if another agent is also using the same engineID you must configure an engineID explicitly This line configures the enginelID to the value of lt string gt createUser lt username gt MD5 lt authpassphrase gt MD5 enables the authentication of SNMP users When you create an SNMPv3 user you must also update the VACM access control tables to provide an explicit declaration of what the user can access Note This entry is made in var opt SUNWmasf snmpd dat rather than etc opt SUNWmasf conf snmpd conf The minimum pass phrase length is eight characters Note When the specified user has been created the createUser
20. the following sections m Problems Starting or Accessing the Agent on page 25 m Failure to Receive Traps on page 27 Problems Starting or Accessing the Agent If the agent does not appear to start ensure that you are the root user before proceeding v To Check Whether the Agent is Running 1 Type ps ef grep snmpd 2 Look for a line of the form root 29394 1 O0Feb 18 4 11 opt SUNWsmasf sbin snmpd 25 If no such line appears the agent is not running 3 Attempt to start the agent with the command etc init d masfd start 4 Again confirm whether the agent is now running If the agent continues not to run refer to the file var adm messages Use your preferred editor to review the messages at the end of the file Messages from the SNMP agent have the form date time hostname snmpd pid ID id daemon type Text where m date is the date when the message was created m time is the time of the message a hostname shows the host where the message was created m pid is the process id of the process that resulted in the message a idis an identifier m type indicates the type of message which can be error info or warning depending on the nature of the problem being reported When reviewing the entries in the log file make sure you confirm that the messages you are reviewing did result from the attempt to start the agent If you are in any doubt review th
21. to use the pkgrm command to remove the packages you installed This procedure removes all the relevant files and links v To Uninstall the Software Caution If you have also installed Sun Management Center remove only the SNMP specific packages SUNWmasfr and SUNWmasf a To remove the Sun Fire V210 V215 V240 V245 and Netra 210 240platform agent packages from the platform agent server type pkgrm SUNWmasfr SUNWmasf SUNWescpl SUNWescdl m To remove the Sun Fire V250 platform agent packages from the platform agent server type pkgrm SUNWmasfr SUNWmasf SUNWescfl SUNWescdl m To remove the Sun Fire V440 V445 platform agent packages from the platform agent server type pkgrm SUNWmasfr SUNWmasf SUNWeschl SUNWescdl 31 m To remove the Netra 440 platform agent packages from the platform agent server type pkgrm SUNWmasfr SUNWmasf SUNWescnl SUNWescdl m To remove the Sun Fire V1280 E2900 or Netra 1280 1290 platform agent packages from the platform agent server type pkgrm SUNWmasfr SUNWmasf 32 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 6 Platform Specific Information The chapter contains the following sections Containment Hierarchy on page 33 sunPlat Class Definitions on page 35 Logical and Log Table Population on page 38 For other related documentation see Related Documentation on page xv C
22. you to control access to one row in a table in a relatively simple way 2 1 1 1 ff a0 2 1 1 2 f f a0 view cust1 included 1 3 76 Jb 2n D2 view cust2 included 1 3 6 1 2 1 2 In the example above the hex value a0 has a binary equivalent of 11111111 10100000 The bit position of the first 0 is position 10 which means that the view cust1 provides access to all the objects with OIDs that match 1 3 6 1 2 1 2 2 1 x 1 where x is an integer value Similarly the view cust2 provides access to all the objects with OIDs that match 43 56 0212 52 2K 2 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 VACM Examples CODE EXAMPLE 3 2 VACM Example sec name source community com2sec local localhost private com2sec mynet 10 10 10 0 24 public com2sec public default public group name sec model sec name group mygroup v1 mynet group mygroup v2c mynet group mygroup usm mynet group local v1 local group local v2c local group local usm local group public v1 public group public v2c public group public usm public view name incl excl subtree mask view all included 1 80 view system included system fe group name context sec model sec level prefix read write notify access mygroup any noauth exact mib2 none none access public any noauth exact system none none access local any noauth exact all all all Default VACM Model The default configuration of
23. 3 Disk Space Requirements 3 Patches 4 Installation and Additional Required Packages 4 Installation Packages 5 Additional Required Packages 5 Effects on System Files 6 Installing the SNMP Software 7 v To Install the SNMP Agent 7 v Starting the SNMP Agent 9 Configuration Files 11 Overview 11 Setting Up the Port Number 12 Setting Up Trap and or Inform Destinations 13 Syntax 13 Configuring Access Control 14 Syntax 15 rocommunity and rwcommmunity 15 rouser and rwuser 15 com2sec 16 group 16 access 17 view 18 VACM Examples 19 Default VACM Model 19 SNMPv3 Configuration 20 Syntax 20 Setting System Information 21 Syntax 21 General Configuration 22 Syntax 22 Updating the SNMP Agent When It Is Running 23 v To Force the SNMP Agent to Update 23 Co Existence With Other Agents 23 4 Troubleshooting 25 Problems Starting or Accessing the Agent 25 v To Check Whether the Agent is Running 25 v To Confirm the Agent has Started 27 Failure to Receive Traps 27 5 Uninstalling the Software 31 v To Uninstall the Software 31 iv Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 6 Platform Specific Information 33 Containment Hierarchy 33 Sun FireV210 V215 V240 V245 and V250 Systems 33 Sun Fire V440 V445 Systems 34 Netra 210 240 System 34 Netra 440 System 34 Sun Fire V1280 E2900 and Netra 1280 1290 Systems 35 sunPlat Class Definitions 35 Equipment 35 sunPlatEquipmentAdministrativeState 35 sunPlatEquipmentUnknow
24. 45 Server Administration Guide 819 3741 Sun Fire V445 Server Service Manual 819 3742 Sun Fire V1280 Sun Fire V1280 Netra 1280 Systems Installation Guide 817 3334 PDF Online and Netra 1280 Sun Fire V1280 Netra 1280 Systems Administration 817 0509 Platforms Guide Sun Fire V1280 Netra 1280 Systems Service Manual 817 0510 Netra 210 Platform Netra 210 Server System Administration Guide 819 2749 IPDF Online Netra 210 Server Service Manual 819 2750 Netra 240 Platform Netra 240 Server Installation Guide 817 2698 PDF HTML Online Netra 240 Server System Administration Guide 817 2700 PDF HTML Sun SNMP Management Agent Addendum for the 817 6238 HTML Netra 240 Server Netra 440 Platform Netra 440 Server Installation Guide 817 3882 PDF HTML Online Netra 440 Server System Administration Guide 817 3884 PDF HTML Sun SNMP Management Agent Addendum for the 817 6832 HTML Netra 440 Server INetra 1290 Netra 1290 Server Installation Guide 819 4372 PDF Platform Netra 1290 Server System Administration Guide 819 4374 IPDF xvi Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Documentation Support and Training Sun Function URL Documentation http www sun com documentation Support http www sun com support Training http www sun com training Third Party Web Sites Sun is not responsible for the availability of third party web sites mentioned in this document Sun does not endorse and is
25. Critical 1 warning 5 warning 5 lowerThresholdCritical 2 major 3 major 2 upperThresholdCritical 3 major 3 major 2 lowerThresholdFatal 4 critical 2 critical 1 upperThresholdFatal 5 critical 2 critical 1 For numeric sensors the following objects are not instrumented sunPlatNumericSensorNormalMin sunPlatNumericSensorNormalMax sunPlatNumericSensorAccuracy sunPlatNumericSensorHysteresis sunPlatNumericSensorThresholdResetAction Note sunPlatNumericSensorEnabledThresholds is read only Fan Tachometer Thresholds The only threshold for fan tachometers configured is the lowerThresholdNonCritical 0 When the detected speed of the fan falls below the configured non critical threshold an alarm is raised and the sunPlatEquipmentAlarmStatus is assigned a severity of warning 5 As no further thresholds are set no additional alarms are raised even if the speed of the fan drops further or stops Chapter 6 Platform Specific Information 37 Update Intervals The agent initiates an update of its internal representation of the managed environment every 15 seconds Note For the Sun Fire V1280 E2900 and Netra 1280 1290 systems this interval is set for 10 seconds Logical and Log Table Population In the current version of the agent the following tables are not completely populated sunPlatWatchdogTable sunPlatLogTable For consistency this table has entries where a sunPlatLogAdminist
26. IGURE 10 1 The sunPlat Physical Resource Inheritance Class Diagram 66 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Interpret False sunPlat Class Definitions The attributes of the sunPlat classes are used to represent the characteristics of hardware resources The availability and operability of the resource to the manager are represented by the state of the managed object Different sunPlat classes have a variety of attributes that express aspects of the managed object s state Physical Entity The Physical Entity superclass is used to represent the characteristics that are generic to all resources Note The entPhysical prefix has been omitted from the following attribute names for clarity m Descr This is a text string containing the known name for the resource This name is typically the name used to describe the resource in product documentation on product legends or possibly the name stored in firmware m IsFRU This is a boolean representing whether the resource is a field replaceable unit Only hardware resources of the class sunPlatCircuitPack are considered to be FRUs Note The SNMP agent mistakenly reports the following items as having an incorrect ent PhysicalIsFRU property e Motherboard e CPUs e CPU fans This error can be ignored The Sun Fire V440 V445 and Netra 440 systems are excluded m HardwareRev This is a text string containing the manufacturer s
27. Microsystems Inc aux Etats Unis et dans d autres pays Toutes les marques SPARC sont utilis es sous licence et sont des marques de fabrique ou des marques d pos es de SPARC International Inc aux Etats Unis et dans d autres pays Les produits portant les marques SPARC sont bas s sur une architecture d velopp e par Sun Microsystems Inc L interface d utilisation graphique OPEN LOOK et Sun a t d velopp e par Sun Microsystems Inc pour ses utilisateurs et licenci s Sun reconna t les efforts de pionniers de Xerox pour la recherche et le d veloppement du concept des interfaces d utilisation visuelle ou graphique pour l industrie de Vinformatique Sun d tient une license non exclusive de Xerox sur l interface d utilisation grephique Xerox cette licence couvrant galement les licenci es de Sun qui mettent en place l interface d utilisation graphique OPEN LOOK et qui en outre se conforment aux licences crites de Sun LA DOCUMENTATION EST FOURNIE EN L TAT ET TOUTES AUTRES CONDITIONS DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFA ON SA Ca Adobe PostScript Contents Preface xiii Sun SNMP Management Agent 1 Installation 3 System Requirements 3 Operating System Solaris OS Requirements
28. September 2006 Environmental and Status Alarm Traps The agent sends traps to report potential environmental problems and other warning or error conditions The definition of environmental or other condition depends on the component but examples include the speed of a fan dropping below a pre determined threshold and the temperature of a component rising above a threshold Sensors such as numeric sensors have multiple thresholds defined to reflect warning critical and failure conditions If a sensor value crosses multiple thresholds when sampled traps are sent for all thresholds that have been crossed Similarly when the reading provided by the sensor returns to a value within an acceptable range trap s are sent to indicate that the warning or error condition has cleared The traps used by the agent are sunPlatCommunicationsAlarm sunPlatEnvironmentalAlarm sunPlatEquipmentAlarm sunPlatProcessingErrorAlarm The trap used depends on the nature of the problem as defined by the generic network information model ITU T Recommendation M 3100 The attributes supplied by the traps are Note The sunPlatNotification prefix has been omitted from the following attribute names for clarity mw Eventid This attribute is set as described in Standard Trap Properties on page 87 m Time This attribute is set as described in Standard Trap Properties on page 87 m Object This attribute is set as described in Standard Tra
29. These physical entities are identified by their entLPPhysicalIndex which is equivalent to the ent PhysicalIndex Although this table can potentially represent all the physical entities associated with a given logical entity by convention only the enclosing physical entity is referenced For example for a logical entity realized by a physical module the mapping references only the module not all the physical entities contained within it Event and Alarm Model The ENTITY MIB provides a single SNMP notification entConfigChange which is used to signal a change to any of the tables in the MIB It is set to provide a maximum of one trap every five seconds The SUN PLATFORM MIB defines more specific notifications and these are described in Chapter 11 SUN PLATFORM MIB The SUN PLATFORM MIB does the following m Extends the Physical Entity Table to represent new classes of component m Extends the Logical Entity Table to represent high value platform and server objects Note All objects in the SUN PLATFORM MIB have the prefix sunPlat to make them globally unique Chapter 9 Sun SNMP Management Agent MIBs 59 Physical Model Table Extensions The SUN PLATFORM MIB provides additional attributes from classes that are not represented in the Physical Entity Table It extends the Physical Entity Table by adding the following sparsely populated table extensions m Equipment Table Extension This augments the Physical Entit
30. a hardware module whose purpose is to package internal hardware components into a recognized form factor Typically a FRU will have a defined form factor and physical appearance It can be a pluggable removable unit which is plugged into a connector it can be more permanently sited within a bay or it can fit into a drawer rack or shelf This class has the entPhysicalClass module 9 The sunPlat Circuit Pack class has the following attributes Note The sunPlatCircuitPack prefix has been omitted from the following attribute names for clarity mg Type This read only attribute is a text string used for assessing the resource s compatibility with its container This attribute can identify functionality and form factor characteristics of the resource m AvailabilityStatus This read only attribute further qualifies the Operational State of the managed object It is an object using BITS syntax and can take zero or more of the set of values shown in TABLE 10 3 Not all of these are applicable to every class of managed object This attribute contributes to the state of the managed object Chapter 10 Physical Model 71 TABLE 10 3 Availability Status Attribute Values Attribute Values inTest 0 failed 1 powerOff 2 offLine 3 offDuty 4 dependency 5 degraded 6 notInstalled 7 Bit No 0 1 Hex 80 40 20 10 08 04 02 01 Description The resource is undergoing a test proce
31. attribute names for clarity m Current This read only attribute takes a boolean value indicating the most recent value of the sensor mw Expected This read only attribute takes a boolean value indicating the anticipated value of the sensor m InterpretTrue This read only attribute is a text string indicating the interpretation of a true value from the sensor m InterpretFalse This read only attribute is a text string indicating the interpretation of a false value from the sensor sunPlat Numeric Sensor A sunPlat Numeric Sensor class is used to represent the characteristics of sensors which can return numeric readings The numeric sensor values are qualified by a Unit of Measurement as defined below Unit of Measurement Base Unit 10Exponent This qualification allows for units of measurement such as milliamps and microvolts If a Rate Unit is defined the Unit of Measurement is further refined as below Unit of Measurement Base Unit 10 amp ponent per Rate Unit This qualification allows for units of measurement such as rpm and km hr 80 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 This class has the ent PhysicalClass sensor 8 and the sunPlatSensorClass numeric 2 The sunPlat Numeric Sensor class has the following attributes Note The sunPlatNumericSensor prefix has been omitted from the following attribute names for clarity m BaseUnits This read only at
32. ber 2006 Note The sunPlatEquipmentHolder prefix has been omitted from the following attribute names for clarity mg Type This read only attribute is an enumerated type representing the holder type of the resource as shown in TABLE 10 4 TABLE 10 4 Equipment Holder Type Attribute Values Attribute Values Description bay 1 shelf 2 drawer 3 slot 4 rack 5 A bay is typically a unit of vertical space within a rack that contains shelves or drawers for holding telecommunications equipment sunPlat interprets its use within a chassis as a physical receptacle requiring cables for signal connections A horizontal support or subrack for holding telecommunications equipment within a rack A horizontal enclosure for holding telecommunications equipment within a rack A physical receptacle with an integral connector for signal connections for removable equipment A rack is the support infrastructure for holding telecommunications equipment holders and cable management systems within a self contained enclosure m AcceptableTypes This read only attribute is a list of text strings representing the types of removable resource circuit pack that are supported by the holder These types are tested for compatibility with the removable resource s Type attribute m Status This read only attribute is an enumerated type indicating the status of the holder with regards to any replaceable hardware resource
33. dure The resource has an internal fault that prevents it from operating Operational State is disabled 1 The resource requires power to be applied and is not powered on The resource requires a routine operation to be performed to place it online and make it available for use Operational State is disabled 1 The resource has been made inactive by an internal control process The resource cannot operate because some other resource on which it depends is unavailable Operational State is disabled 1 The service available from the resource is degraded in some respect such as in speed or operating capability However the resource remains available for service Operational State is enabled 2 The resource represented by the managed object is not present or is incomplete Operational State is disabled 1 m Replaceable This read only attribute takes a boolean value indicating whether the resource is a replaceable unit m HotSwappable This read only attribute takes a boolean value indicating whether the replaceable resource is hot swappable sunPlat Equipment Holder The sunPlat Equipment Holder class is used to represent the characteristics of hardware resources that are capable of holding removable hardware resources This class has the entPhysicalClass container 5 The sunPlat Equipment Holder class has the following attributes 72 Sun SNMP Management Agent for Sun Fire and Netra Systems Septem
34. e entPhysicalTable This table provides a row per hardware entity These rows are called Entries and a particular row is referred to as an instance Each entry contains Physical Mapping Table ent PhysicalContainsTable Physical class ent PhysicalClass Common characteristics of the hardware entity Unique index ent Physical Index Reference ent PhysicalContainedIin that points to the row of the hardware entity that acts as the container for this resource This is zero for components such as a chassis that are not physically contained within another This table provides a virtual copy of the hierarchy of the hardware resources represented in the Physical Entity Table This table is two dimensional indexed first by the ent Physical Index of the containing entry and then by the entPhysicaliIndex of each contained entry TABLE 9 1 shows the ent PhysicalTable on which the above figure is based and TABLE 9 2 shows the physical mapping TABLE 9 1 Physical Entity Table entPhysicallndex entPhysicalClass entPhysicalContainedin 1 So oo N DBD oO F amp F WO N Se m e Nu e Chassis Fan Container for example a slot containing a FRU Other Sensor binary Module for example a pluggable FRU Sensor numeric Power supply Alarm device Watchdog Sensor discrete Power supply battery 0 1 1 m Ae DOH KH DBF W N 56 Sun SNMP Management Agent for Sun Fire and Netra Systems Septembe
35. e file before starting the agent and identify the date and time of the last message After attempting to start the agent locate this same message and review messages following it The most likely reason for the agent being unable to start is that it cannot access the network ports that it requires The ports used by the agent are specified in the configuration file Such a problem can be recognized by a message of the form date time hostname snmpd pid ID id daemon type Error opening specified endpoint udp portno where portno is the port specified in the configuration file 26 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 If this message appears identify why the port is not available Use netstat a to show all ports being accessed If the port is not available modify the configuration file to select a different port using an entry of the form agentaddress newport If the error appears again for a port that is available confirm you are running the agent as root and that you have permission to access the specified port If the management applications clients cannot access agent onfirm the agent has started see To Check Whether the Agent is Running on page 25 To Confirm the Agent has Started From a client that is unable to access the agent using SNMP use ping to make sure that the host running the SNMP agent is accessible over the network If the ping fails
36. e following attribute names for clarity m Timeout This read only attribute is an integer indicating the interval in milliseconds after which the watchdog will timeout if not reset m Action This read only attribute is an enumerated type representing the action taken by the watchdog if it is not reset within the period specified by the Timeout The possible values are shown in TABLE 10 6 TABLE 10 6 Watchdog Action Attribute Values Action Description statusOnly 1 The watchdog is readable by software but performs no action systemInterrupt 2 The watchdog generates a hardware interrupt to the system being monitored systemReset 3 The watchdog resets the system being monitored systemPowerOff 4 The watchdog powers off the system being monitored systemPowerCycle 5 The watchdog powers off and then on the system being monitored m LastExpired This read only attribute indicates the date and time at which the watchdog last expired m MonitoredEntity This read only attribute is an enumerated type representing the entities that can be monitored by the watchdog The possible values are unknown 1 other 2 operatingSystem 3 operatingSystemBootProcess 4 operatingSystemShutdownProcess 5 firmwareBoot Process 6 biosBootProcess 7 application 8 76 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 a serviceProcessors 9 sunPlat Alarm The sunPlat Alarm class is
37. e resources can be nested directly within the chassis such as a motherboard Others are nested within other resources for example a motherboard can include a processor These relationships extending from within the chassis form a hierarchy of hardware resources each physically contained within its enclosing parent This hierarchy is modeled using relationships between managed objects that represent the hardware resources FIGURE 8 1 49 Container Sensor Module Sensor Battery Binary Numeric Alarm Sensor Discrete FIGURE 8 1 Hardware Resource Hierarchy Example Managed Objects The SunPSM model provides a useful set of common platform building blocks representing fundamental hardware resources Instances of these platform building blocks are called managed objects A hardware resource is represented by a managed object if it can be monitored or if it provides useful configuration information Additional managed objects are used to represent other features of the management interface For example hardware resources can issue asynchronous status reports notifications in response to problems alarms or changes in configuration events 50 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Managed objects are defined in terms of managed object classes Characteristics of the resource are represented by properties of the managed object New classes called subclasses are de
38. ecifies the SNMPv3 security name to which these permissions apply a The minimum level of authentication and privacy for lt username gt is specified by the first token which defaults to auth m The lt OID gt token restricts access for that user to everything below the given OID Chapter 3 Configuration Files 15 These directives have no effect unless the corresponding user has been created see SNMPvVv3 Configuration on page 20 You can apply only one rwuser or rouser directive for each user com2sec com2sec lt username gt lt source gt lt community gt This directive specifies the mapping from a source community pair to a security name m lt username gt specifies the security name to which this source and community string are to be mapped a lt source gt can be a hostname a subnet or the word default A subnet is specified as IP mask for example 129 156 203 56 255 255 255 0 or IP bits for example 129 156 203 56 24 m default specifies that access is to be provided to all hosts with the specified community The first source community combination that matches the incoming packet is selected group group lt groupname gt lt model gt lt username gt This directive defines the mapping from a given security model and security name to a particular group m lt groupname gt defines the name of the group to which this combination of model and security name belongs m l
39. ed to indicate a replaceable or hot swappable component m sunPlatCircuitPackReplaceable m sunPlatCircuitPackHotSwappable a isFRU A component is replaceable if it can be removed and replaced with a physically different component A component is hotswappable if the power can be on when the component is removed or inserted All hotswappable components are replaceable A component is a Field Replaceable Unit FRU if it is an identifiable part that can be obtained and replaced in the field Binary Sensors Changes in binary sensors that result in sunPlatBinarySensorCurrent not taking the same value as that specified by sunPlatBinarySensorExpected generate an alarm with a sunPlatAlarmPerceivedSeverity of major 3 For example when unplugging a cable from a power supply on the Sun Fire V240 an alarm is sent with a sunPlatAlarmPerceivedSeverity of major 3 and the value of sunPlatEquipmentAlarmStatus is set to major 2 36 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Numeric Sensors TABLE 6 1 shows the mappings that exist between the configured threshold the severity reported in the alarm sunPlatAlarmPerceivedSeverity and the severity sunPlatEquipmentAlarmStatus recorded against the related object for all numeric sensors TABLE 6 1 Numeric Sensor Mapping Threshold sunPlatAlarmPerceivedSeverity sunPlatEquipmentAlarmStatus lowerThresholdNonCritical 0 warning 5 warning 5 upperThresholdNon
40. enting the resource with which the event is associated m CorrelatedNotifications This attribute is comma separated list of ID values that identify the other events to which this event is associated m AdditionalInfo This attribute provides an additional OID that further qualifies the purpose of the trap Not all traps populate this value and a value of 0 0 identifies that no trap specific value is relevant to the trap m AdditionalText This attribute provides a further textual description for the trap The exact content of the string varies depending on the cause of the trap However the format used for this string is always of the form lt serial number gt lt hostname gt lt entPhysicalName gt lt trap specific text gt where ent PhysicalName identifies the physical name of the object raising the trap Examples of the lt trap specific text gt include Voltage threshold crossed Current threshold crossed Tachometer threshold crossed Temperature threshold Chapter 11 Traps 87 m PerceivedSeverity This attribute describes the severity of the cause of the trap The attribute can take the following values indeterminate 1 critical 2 major 3 minor 4 warning cleared 5 6 m ProbableCause This attribute provides a textual description of the probable cause Example of the permitted values include as lowTemperature a coolingSystemFailure externalEquipmentFailure m SpecificProblem This attr
41. enumerated type indicating the relative frequency at which the Alarm flashes vibrates and or emits audible tones The possible values are other 1 unknown 2 notSupported 3 informational 4 nonCritical 5 critical 6 unrecoverable 7 sunPlat Fan The sunPlat Fan class is used to represent the characteristics of active cooling devices A fan typically contains a sensor representing the speed of rotation This is modeled using a physical containment relationship between the sunPlat Fan managed object and a tachometer managed object of class sunPlatSensor This class has the entPhysicalClass fan 7 The sunPlat Fan class has the following attribute Note The sunPlatFan prefix has been omitted from the following attribute name for clarity m Class This read only attribute is an enumerated type indicating the class of cooling device and takes the following values a other 1 a fan 2 a refrigeration 3 78 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 a heatPipe 4 sunPlat Sensor The sunPlat Sensor superclass is used to represent the generic characteristics of hardware resources that measure properties of other hardware resources This class has the entPhysicalClass sensor 8 The sunPlat Sensor class has the following attributes Note The sunPlatSensor prefix has been omitted from the following attribute names for clarity m Class This read only attribute i
42. fined in terms of existing classes A subclass inherits all the characteristics of its superclass but represents its own characteristics by adding new properties FIGURE 8 2 shows the class inheritance hierarchy of the hardware building blocks defined by the SunPSM model Circuit Pack Equipment Holder Power Alarm Batter Binary Discrete Numeric Y Sensor Sensor Sensor FIGURE 8 2 SunPSM Managed Object Class Inheritance Diagram Chapter 8 Platform Management Model 51 Derivation of sunPlat Classes The SunPSM classes are based on industry standard management concepts The Sun SNMP management agent system uses a subset of the ITU T generic network information model chosen for its representation of hardware infrastructure This provides a powerful and extendible framework that supports uniform fault and configuration management in a Telecommunications Management Network TMN The Distributed Management Task Force DMTF common information model CIM schema models the physical environment and event definition and handling and provides system specific extensions to the common model 52 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 9 Sun SNMP Management Agent MIBs This chapter describes how the managed objects and their relationships are presented by the SNMP interface The chapter contains the following sections SNMP Representation of the Model on page 53
43. for Sun Fire and Netra Systems September 2006 Syntax rocommunity and rwcommmunity rocommunity lt community gt lt source gt lt OID gt rwcommunity lt community gt lt source gt lt OID gt These create read only and read write communities that can be used to access the agent They are a simple wrapper around the more complex and powerful com2sec group access and view directive lines They are also not as efficient because groups are not created and the tables can be larger as a consequence It is therefore better not to use these if you have complex situations to set up and to reserve their use to where your setup is simple m The lt community gt token specifies the community string for which access is to be granted m The format of the lt source gt is token and is described in the com2sec directive section m The lt OID gt token restricts access for that community to everything below the given OID You can apply only one rwcommunity or rocommunity directive for each source community combination rouser and rwuser rouser lt username gt noauth auth priv lt OID gt rwuser lt username gt noauth auth priv lt OID gt These configure access permissions for the specified user in the VACM configuration tables It is more efficient and powerful to use the combined group access and view directives instead but these wrapper directives are much simpler m lt username gt sp
44. gement application has been used to receive traps confirm that it is correctly listening for SNMP traps on port 162 or other appropriate port As this is a low port number the application that is to receive traps must run with root privileges If the application is running use netstat to confirm that it is listening UDP IPv3 Local Address Remote Address State 162 Idle Remember traps are not sent continuously and are sent only in the following circumstances m SNMP agent is starting or stopping a Potential problem has been detected by the SNMP agent or the problem has been cleared a SNMP agent has detected a change to the hardware objects being added or removed from the management model m Property value has changed The agent sends traps for all value changes except those that change rapidly such as voltage readings fan tachometers and temperature For these kinds of environmental sensors traps are sent only when thresholds are crossed If you are not sure if a trap has been sent stop and restart the agent to generate cold start traps using etc init d masfd stop followed by etc init d masfd start 28 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Chapter 4 Troubleshooting 29 30 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 5 Uninstalling the Software Generally all that is required to uninstall SNMP is
45. has been omitted from the following attribute name for clarity 74 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 m Class This read only attribute is an enumerated type indicating the class of the power supply and takes the following values m other 1 m powerSupply 2 ms battery 3 sunPlat Battery The sunPlat Battery class is used to represent a power supply that supplies power from a battery This class has the entPhysicalClass powerSupply 6 and the sunPlatPowerSupplyClass battery 3 The sunPlat Battery class has the following attribute Note The sunPlatBattery prefix has been omitted from the following attribute name for clarity m Status This read only attribute is an enumerated type that indicates the status of the battery and takes the following values other 1 unknown 2 fullyCharged 3 low 4 critical 5 charging 6 chargingAndHigh 7 chargingAndLow 8 chargingAndCritical 9 undefined 10 partiallyCharged 11 sunPlat Watchdog The sunPlat Watchdog class is used to represent the characteristics of timer hardware resources that allow the hardware to monitor the state of the operating system or applications Chapter 10 Physical Model 75 This class has the entPhysicalClass other 1 and the sunPlatPhysicalClass watchdog 3 The sunPlat Watchdog class has the following attributes Note The sunPlatWatchdog prefix has been omitted from th
46. hdog Action Attribute Values 76 Alarm Type Attribute Values 77 Alarm State Attribute Values 78 Sensor Type Attribute Values 79 xi xii Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Preface This guide describes the Sun SNMP Management Agent which supports management of hardware using the Simple Network Management Protocol The Management Agent provides monitoring of inventory configuration service indicators and environmental and fault reporting It is intended to be read by experienced enterprise administrators and professional developers The Guide is divided into two parts m Part I Chapter 1 through Chapter 6 explains how to install and configure the software m Part Il Chapter 7 through Chapter 11 introduces the SNMP Management Agent and describes its functionality Note This document describes features and functionality found in version 1 4 of the software Refer to the Sun SNMP Management Agent for Sun Fire and Netra Systems Release Notes part number 817 2667 for the latest information How This Document Is Organized The Guide contains the following chapters Part I Chapter 1 provides an overview of the software Chapter 2 describes how to install the management software Chapter 3 provides information about the user configurable files xiii Chapter 5 explains how to uninstall the software Chapter 4 provides help in troubleshooting your software Chapter 6
47. his attribute is set as described in Standard Trap Properties on page 87 m Time This attribute is set as described in Standard Trap Properties on page 87 m Object The attribute is OID of the parent of the object being created or deleted The OID is that of the entPhysicalDescr object for the row in ent PhysicalTable that represents the parent object m CorrelatedNotifications This is currently assigned to an empty string m AdditionaliInfo This attribute is the OID of object being created The OID is that of the entPhysicalDescr object for the row in entPhysicalTable being created m AdditionalText For details see Standard Trap Properties on page 87 Property Change Traps The agent can deliver traps whenever a value in an object changes The type of trap depends on the type of the object m The sunPlatStateChange trap is sent when a state attribute changes value Chapter 11 Traps 89 a The sunPlatAttributeChangeInteger trap is sent when the value of an integer property changes This trap is used for all integer property value changes with the exception of current values with respect to numeric sensors as such values can change rapidly and can result in a large number of traps a The sunPlatAttributeChangeString trap is sent when the value of a string property changes This trap is used for all string property value changes a The sunPlatAttributeChangeOID trap is sent when the value of an OID property
48. ibute provides an additional textual description that supplies further information about the cause of the trap m RepairAction This attribute provides a textual description of the potential repair actions Multiple repair actions may be described in which case lt CR gt lt LF gt sequences are used to delimit individual descriptions of the actions m ChangedOID This attribute provides the OID of an object whose value changing caused the trap to be sent Trap Types This section describes the function and properties of the following trap types m Object creation and deletion traps m Property change traps a Environmental and status alarm traps 88 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Object Creation and Deletion Traps The sunPlatObjectCreation trap is sent when an object is created within the agent to represent a new component For example a new component has been hotplugged into the system The agent sends object creation traps only for objects added once it has started so traps are not generated during the initial phase of discovery when the agent first starts The sunPlatObjectDeletion trap is sent when an object is deleted as a result of a component being removed or unconfigured from the system Object creation and deletion traps have the following properties Note The sunPlatNotification prefix has been omitted from the following attribute names for clarity m Eventid T
49. ich is modeled within another physical entity such as a chassis or another module The entity is always modeled within a container Logical Model Note The logical model is not populated by this agent The sunPlat logical model uses the ENTITY MIB to provide a list of logical entities Each entity is represented as a separate row in the ENTITY MIB s entLogicalTable Note Unlike the physical model the logical model is flat rather than hierarchical The ENTITY MIB does not distinguish between different classes of logical object unlike the case for physical objects The SUN PLATFORM MIB provides a class hierarchy for logical objects and this is described in Chapter 8 The information in the entLogicalTable can be used to support multi scoping using different naming context However this capability is not employed in this product The information of particular value is the entLogicalDescription and entLogicalTAddress the latter giving the IP address at which the logical entity can be accessed 58 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Logical and Physical Hierarchy Mapping The ENTITY MIB provides a mapping between logical objects and the physical objects of which they are composed This is achieved by the entLPMappingTable which is a two dimensional table similar to the ent PhysicalContainsTable and which identifies the physical entities that realize a given logical entity
50. ile by typing zcat SUNWmasf lt ver gt tar Z tar xf Ensure you are the root user before proceeding with installation Change to the directory where the tar file was extracted at the root of the packages provided by the tar file If you wish to start installation from a different directory when using pkgadd you must specify the path of the root of the directory hierarchy where the files where extracted using the d option rather than d as shown in step 4 Caution If you have installed Sun Management Center on your monitored platform skip to Step 5 Install the support for platform instrumentation For the Sun Fire V1280 E2900 and Netra 1280 and 1290 servers skip to Step 5 a To install the Sun Fire V210 V215 V240 V245 and Netra 210 240 instrumentation type pkgadd d SUNWescdl SUNWescpl1 Chapter 2 Installation 7 a To install the Sun Fire V250 instrumentation type pkgadd d SUNWescdl SUNWescfl1 a To install the Sun Fire V440 instrumentation type pkgadd d SUNWescdl SUNWeschl1 m To install the Netra 440 instrumentation type pkgadd d SUNWescdl SUNWescnl1 5 Install the SNMP agent by typing pkgadd d SUNWmasf SUNWmasfr After installation the agent must be configured before you attempt to start it A full description of the configuration options for the SNMP agent is provided in Chapter 3 Before using the agent yo
51. information sUNWescp1 Common Config Reader Sun Fire V210 V240 Configuration reader platform support for and Netra 210 platform support the Sun Fire V210 V215 V240 V245 and Netra 210 SUNWescf1 Common Config Reader Sun Fire V250 Configuration reader platform support for platform support the Sun Fire V250 SUNWesch1 Common Config Reader Sun Fire V440 Configuration reader platform support for platform support the Sun Fire V440 V445 SUNWescn1 Common Config Reader Netra 440 platform Configuration reader platform support for support the Netra 440 V445 SUNWmas f Sun SNMP Management Agent for Sun Fire SNMP Agent common components and Netra systems SUNWmasfr Sun SNMP Management agent for Sun Fire Startup and configuration scripts for the and Netra systems root SNMP agent Additional Required Packages Note The packages listed in TABLE 2 2 must be installedto enable support of the SNMP Mangement Agent TABLE 2 2 SNMP Management Agent Additional Required Software Packages Package Package Name SUNWfruid FRU ID Utility and Library Usr SUNWfruip FRU ID Platform Modules Usr SUNWmfrun Motif RunTime Kit SUNWpiclh PICL Header Files Usr SUNWpiclr PICL Framework Root SUNWpiclu PICL Libraries and Plugin Modules Usr Chapter 2 Installation 5 To upgrade the software you must remove the existing software before reinstalling the new version see Chapter 5 Effects on System Files A new startup file is created i
52. is raised against the fan rather than the tachometer At this point the CPU may be still be completely functional If the CPU has a related 85 temperature sensor and the fan continues to fail to function the temperature could rise If at some point the temperature exceeds a threshold value a fault is issued against the CPU Multiple thresholds can be set for all numeric sensors upperFatal upperCritical upperNonCritical lowerFatal lowerCritical lowerNonCritical The precise semantics of these thresholds depends on the underlying component and not all components use all the thresholds Where a component uses a threshold the agent always creates a trap when the threshold is crossed This means that if the current value reported by the sensor changes dramatically and crosses multiple thresholds at the same time multiple traps are delivered Note Even if multiple thresholds are crossed in one sample when the problem is cleared the resultant traps can occur over a period of time You can determine the threshold values assigned to a numeric sensor by reading the following properties sunPlatNumericSensorLowerThresholdNonCritical sunPlatNumericSensorUpperThresholdNonCritical sunPlatNumericSensorLowerThresholdCritical sunPlatNumericSensorUpperThresholdCritical sunPlatNumericSensorLowerThresholdFatal sunPlatNumericSensorUpperThresholdFatal These are all 32 bit integer values the actual numeric threshold being determined b
53. latEquipmentAlarm or sunPlatEnvironmentalAlarm traps are issued a Main system fans are contained in the fan tray module a PCI card fans are contained within the I O Assembly module m Power supplies fan tray and I O assembly are contained within the chassis sunPlat Class Definitions This section contains platform specific information relating to class definitions and attributes For further information see Technical Description and Functionality on page 41 Equipment sunPlatEquipmentAdministrativeState The sunPlatEquipmentAdministrativeState is read only and reports unlocked 2 except in the case of network interfaces for which it reports locked 1 until the interface has been appropriately configured sunPlatEquipmentUnknownStatus For all slots bays and PCI cards the precise operation state cannot be determined from available sensors or be derived from other components Therefore these all report sunPlatEquipmentUnknownStatus as true 1 Chapter 6 Platform Specific Information 35 sunPlatEquipmentLocationName For all objects this provides a string of the form lt serial number gt lt hostname gt lt NAC Name gt where lt serial number gt is the serial number of the chassis The lt NAC Name gt provides a unique name for each hardware component sunPlatEquipmentHolderPowered Only read accesses are supported for this object Replaceable and Hotswappable Components The following attributes are us
54. must have an SNMP agent associated with it The purpose of the agent is to m Receive requests for data representing the state of the device from the manager and provide an appropriate response m Accept data from the manager to enable control of the device state m Generate SNMP traps which are unsolicited messages sent to one or more selected mangers to signal significant events relating to the device SNMP Management Information Base To manage and monitor a device its characteristics must be represented using a format known to both the agent and the manager These characteristics can represent physical properties such as fan speeds or services such as routing tables The data structure defining these characteristics is known as a management information base MIB This data model is typically organized into tables but can also include simple values An example of the former is a routing table and an example of the latter is a timestamp indicating the time at which the agent was started The MIB is a definition for a virtual data store accessible via SNMP The content is accessible from the manager using get and set operations as follows m In response to a get operation the agent provides data either maintained locally or directly from the managed device m In response to a set operation the agent typically performs some action affecting the state of either itself or the managed device 44 Sun SNMP Management Agent for Sun Fi
55. n m Logical Class Table Extension This extends the entLogicalTable to define the class of the logical entity sunPlatLogicalClass and its status sunPlatLogicalStatus The sunPlatLogicalTable is valid for all entries in the entLogicalTable The Computer System subclass of the Logical class is represented by a further table extension Computer System Table Extension This table extends the entLogicalTable to provide attributes common to instances of a computer system The sunPlatUnitaryComputerSystemTable is valid for those rows of the entLogicalTable with a sunPlatLogicalClass of computerSystem 2 Chapter 9 Sun SNMP Management Agent MIBs 63 64 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 10 Physical Model This chapter describes the sunPlat physical class hierarchy and how the managed physical object classes defined in the sunPlat model are represented by the SUN PLATFORM MIB The chapter contains the following sections a sunPlat Physical Class Hierarchy on page 65 a sunPlat Class Definitions on page 67 sunPlat Physical Class Hierarchy FIGURE 10 1 shows the inheritance hierarchy of the sunPlat classes used to model hardware resources within the Sun SNMP Management Agent The Physical Entity superclass provides an attribute for defining the relationship between managed objects It also provides standard SNMP attributes that correspond to attributes in the Eq
56. n etc init d as shown in TABLE 2 3 with links to etc re lt n gt d TABLE 2 3 Startup Script Component Startup Script Package Name Package Description Agent masfd suUNWmasfr Configuration and startup script for SNMP agent After installation the following MIBs supported by the agent are located in the directory opt SUNWmasf 1lib mibs TABLE 2 4 MIB Files MIB Function ENTITY MIB txt Describes physical and logical entities RFC1155 SMI txt Defines additional object types used by other MIBS RFC1213 MIB txt Models network interfaces note this agent only supports system part SUN PLATFORM MIB txt Extends the Entity MIB to provide additional information about hardware components 6 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Installing the SNMP Software This section describes the procedure for installing the monitoring software Before installing the software ensure that m You have the requisite level of Solaris installed on both the domain or target and the platform agent server see Operating System Solaris OS Requirements on page 3 a You have installed all the necessary patches see Patches on page 4 and any additional essential packages TABLE 2 2 not supplied as part of the SNMP software When you are certain that your system meets all these requirements you can proceed to install the SNMP software To Install the SNMP Agent Unpack the tar f
57. nStatus 35 sunPlatEquipmentLocationName 36 sunPlatEquipmentHolderPowered 36 Replaceable and Hotswappable Components 36 Binary Sensors 36 Numeric Sensors 37 Fan Tachometer Thresholds 37 Update Intervals 38 Logical and Log Table Population 38 Related Documentation 38 7 Introduction to SNMP 43 SNMP Versions 43 SNMP Managers and Agents 44 SNMP Management Information Base 44 MIB Tables 45 Access Control 47 8 Platform Management Model 49 Contents v Modeling the Platform 49 Managed Objects 50 Derivation of sunPlat Classes 52 9 Sun SNMP Management Agent MIBs 53 SNMP Representation of the Model 53 entityPhysical Group 54 entityLogical Group 54 entityMapping Group 54 entityGeneral Group 54 entityMIBTraps Group 54 Physical Model 55 Classes 57 Logical Model 58 Logical and Physical Hierarchy Mapping 59 Event and Alarm Model 59 SUN PLATFORM MIB 59 Physical Model Table Extensions 60 Logical Model Table Extension 63 10 Physical Model 65 sunPlat Physical Class Hierarchy 65 sunPlat Class Definitions 67 Physical Entity 67 sunPlat Equipment Class 69 sunPlat Circuit Pack Class 71 sunPlat Equipment Holder 72 sunPlat Power Supply 74 sunPlat Battery 75 vi Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 11 sunPlat Watchdog 75 sunPlat Alarm 77 sunPlat Fan 78 sunPlat Sensor 79 sunPlat Binary Sensor 80 sunPlat Numeric Sensor 80 sunPlat Discrete Sensor 83 sunPlat Chassis 83 Traps 85
58. ng networked devices systems It is defined in common with other internet standards by a number of Requests for Comments RFCs published by the Internet Engineering Task Force IETF There are three versions of SNMP that define approved standards a SNMPv1 a SNMPv2 also known and referred to in this document as SNMPv2c a SNMPv3 SNMPv1 was first defined in 1988 SNMPv2 was introduced in 1993 and attempted to address some of the shortcomings of SNMPv1 by adding further protocol operations and data types and providing security Limitations in the security model led to what is now accepted as the SNMPv2c standard which dropped the new security based features Experimental versions known as SNMPv2usec and SNMPv2 also appeared at this time but these have not been widely adopted and remain experimental SNMPv3 introduced in 1999 defines the SNMP management framework supporting pluggable components including security 43 For further information about these standards refer to the following RFCs at the IETF website http www ietf org rfc html SNMPv1 RFC1155 RFC1157 RFC1212 RFC1215 SNMPv2 RFC2578 RFC2579 RFC2580 RFC3416 SNMPv3 RFC3410 RFC3411 RFC3412 RFC3413 RFC3414 RFC3415 Coexistence between standards RFC2576 SNMP Managers and Agents SNMP is a network protocol that allows devices to be managed remotely by a network management station NMS also commonly called a manager To be managed a device
59. ns of the trapsink trap2sink and informsink directives see Setting Up Trap and or Inform Destinations on page 13 When lt model gt is v1 or v2c set lt level gt to noauth and lt context gt to the empty string wu When access for a particular group with a given security model is requested the agent determines access in the following order 1 Entries with an matching security model as opposed to those matching against any 2 If there is still more than one match the most exact lt context gt match 3 If there is still more than one match the entry with the highest security level Chapter 3 Configuration Files 17 18 view view lt viewname gt lt type gt lt subtree gt lt mask gt This defines the named view a lt viewname gt defines the name of the view which you can then use to reference the view in an access directive m lt type gt takes the values included or excluded It specifies whether the OID subtree specified in lt subtree gt should be included or excluded from the corresponding view m lt mask gt is a list of hex octets separated by or The mask defaults to all 1s matching is performed against all digits in the subtree if it is not specified A bit value of 0 in the mask acts as a wildcard for the corresponding value in the OID A bit value of 1 in the mask indicates that the corresponding value in the subtree OID is fixed The mask enables
60. nsion 63 configuration access control 14 general 21 22 inform destinations 13 port number 12 SNMPv3 20 system information 21 trap destinations 13 connector 71 containment hierarchy 33 createuser 20 D Discrete Sensor Table extension 60 drawer 71 E enginelID 20 entConfigChange 59 ENTITY MIB 1 46 53 58 entLPMappingTable 59 entLPPhysicalIndex 59 entPhysicalClass 56 57 entPhysicalContainedIn 56 entPhysicalContainsTable 56 entPhysicalIndex 56 59 entPhysicalTable 56 Equipment Holder Table extension 60 Equipment Table extension 60 events 50 F fan speeds 44 Fan Table extension 61 G group 16 H hardware resource hierarchy 68 hardware resources 49 hardware type 68 l INDFX clause 46 informsink 13 93 inheritance hierarchy 66 installation prerequisites 7 installing agent software 7 instance specifier 46 internet standards 43 L LEDs 77 Logical Class Table extension 63 M managed objects 49 50 management interface 49 MIB 44 tables 45 monitoring data 69 N network management station See NMS network protocol 44 NMS 44 notifications 50 numeric sensor reading 80 Numeric Sensor Table extension 60 O object identifier See OID OID 45 P physical and logical groups 53 Physical Entity superclass 67 Physical Entity Table 54 56 60 Physical Mapping Table 54 Physical Table extension 60 pluggable removable unit 71 ports 8 11
61. ontainment Hierarchy The agent constructs a containment hierarchy for the discovered managed objects based both on the entPhysicalName of the component discovered and knowledge of how the components are related For most objects the location can be identified from entPhysicalName which is typically of the form x y z where x y and z identify other components within the system that form a hierarchy In such a case sunPlatEquipmentLocationName would be x y To provide a complete representation of the physical relationships the agent applies the following rules to override the behavior described above Sun FireV210 V215 V240 V245 and V250 Systems m All memory banks are contained by the motherboard a The CPU temperature and voltage sensors are contained by the processor m The CPU fans are contained by the processor m All power supply indicators and sensors are contained by the power supply module 33 All SCSI disks and tape drives attached to the SCSI port on the chassis are contained by that SCSI port Drives external to the chassis connected to a PCI card are contained within the object representing the PCI slot in which the card is inserted The Sun Fire V250 system configuration card slot is contained within the system configuration card reader Sun Fire V440 V445 Systems The CPU and memory module slots PCI slots and system controller are contained in the system board The CPU and memory banks are contained in the
62. or this port number and its value must be determined by the administrator on the basis of other agents that may be in use and the configuration of the management clients 12 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Note By using ports other than 161 and 162 for SNMP agent access you can ensure that these ports are available for use by other agents such as snmpdx or Sun Management Center which use them by default Setting Up Trap and or Inform Destinations Syntax trapcommunity lt string gt This defines the default community string to be used when sending traps Note You must use the trapcommunity command before any of the following three commands which use this community string If you do not set a community string the default value public is used trapsink lt host gt lt community gt lt port gt trap2sink lt host gt lt community gt lt port gt informsink lt host gt lt community gt lt port gt These commands define the hosts to receive traps and or inform notifications m Use trapsink to specify a host to be sent SNMPv1 traps m Use trap2sink to send SNMPv2 traps m Use informsink to send inform notifications You can use multiple trapsink trap2sink and informsink lines to specify multiple destinations You can also specify a host multiple times in which case a trap is sent for each of the commands listed Chapter 3 Configura
63. ource is partially or fully operable and available for use m AlarmStatus This read only attribute takes an enumerated value representing the current alarm state of the resource It indicates the highest severity of any alarm outstanding on the managed object The attribute can take the following values critical 1 major 2 minor 3 indeterminate 4 warning 5 pending 6 cleared 7 m UnknownStatus This read only attribute indicates if the other state attributes might not reflect the true state of the resource The attribute takes a boolean value representing whether the managed object is able to report accurately faults against the resource If the resource is unable truthfully to reflect its state this attribute is set to true 70 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 m LocationName This read only attribute contains a locator for the resource For resources contained directly within the chassis this attribute correlates with legends on slots and product documentation or provides a geographical indication of the position of the resource within the chassis Other hardware resources typically have a location corresponding to the Name of the managed object for the resource in which it is contained sunPlat Circuit Pack Class The sunPlat Circuit Pack class is used to represent the characteristics that are generic to a replaceable resource or FRU A replaceable resource is defined as
64. p Properties on page 87 m CorrelatedNotifications This attribute is assigned an empty string when an alarm is first raised When the alarm condition is cleared the value is the string representation of the sunPlatNotificationEventId value that was sent in the trap when the alarm condition was first raised m AdditionalInfo This attribute is set as described in Standard Trap Properties on page 87 m AdditionalText This attribute is set as described in Standard Trap Properties on page 87 Chapter11 Traps 91 92 m PerceivedSeverity This attribute is set as described in Standard Trap Properties m ProbableCause This attribute is set as described in Standard Trap Properties m SpecificProblem This attribute is set as described in Standard Trap Properties m RepairAction This attribute is set as described in Standard Trap Properties Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 on page 87 on page 87 on page 87 on page 87 A access 17 Access Control List See ACL access rights 47 ACL 47 addressable objects 47 agentaddress 12 agentgroup 22 agentuser 22 Alarm Table extension 61 alarms 50 authtrapenable 23 B bay 71 Binary Sensor Table extension 60 C Circuit Pack Table extension 60 class definitions 67 classes 51 com2sec 16 comment line 12 Common Information Model 1 community strings 47 Computer System Table exte
65. pecifying the OID giving its columnar prefix For example myFanTable myFanEntry myCurrentFanSpeed with a suffix instance specifier for instance 127 0 0 1 1234 from the previous example gives myFanTable myFanEntry myCurrentFanSpeed 127 0 0 1 1234 The SMI defining the MIB syntax provides an important capability for extending tables to add additional entries effectively by adding extra columns to the table This is achieved by defining a table with an INDEX clause that is a duplicate of the INDEX clause of the table being extended It is also possible to define MIB tables that are indexed not by objects contained within them but by objects imported from other tables potentially defined in other MIBs This construct effectively enables columns to be added to an existing table Note The SUN PLATFORM MIB makes extensive use of this mechanism to extend tables defined in the ENTITY MIB see Chapter 9 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Access Control All addressable objects defined in the MIB have associated maximum access rights for instance read only or read write These determine the maximum access the agent can support and can be used by the manager to restrict the operations it will permit the operator to attempt The agent is able to apply lower access rights as required that is it is able to refuse writes to objects that are considered read write This refusal can be on the basis
66. ple hardware resource hierarchy shown in FIGURE 9 1 Chapter 9 Sun SNMP Management Agent MIBs 61 Physical Entity Table Extensions TABLE 9 3 SUN PLATFORM MIB ssejgAjddnsgiamod e quns ajqe_Ajddnsiamog e quns 31GB SN E SIOSUSS9 919S1q e quns a1qeLsosuaseajesosiqjze quns aiqe_sosuagouawnnie quns ssejjJ10suasj e quns ajqeLiosuasAseuigye quns a1qeLsosuasj ejquns aiqeLwueyyie quns ssejguesjye quns aiqeLuesjzejquns aiqe Bopysjemie quns ssejojeoisAygye quns watchdog aiqeiesisAygie quns aiqeyoequnosgie quns 3 qeJepjoH UeWdiInbyye quns ENTITY MIB jqepu wd nbgeiduns B H Q Q al ajl a amp 2 ssej9leos yd ua alel 2 F elele 2 8 S Bl a 3 5 s ajal s s S El g 8 s 8 oo S oO oO 2 s E4 O O e U o z E v e Q Q xepujeaisAyg ua a om o Nian o r do oflals aiqeLjesisAyqque Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 62 TABLE 9 4 Key to Physical Entity Table Extensions Reference Description Fan Refrigeration Heat sink Binary Numeric Discrete Power supply zoa7mmM UA SY Battery Logical Model Table Extension The SUN PLATFORM MIB provides additional attributes from classes that are not supported in the Logical Entity Table It extends the Logical Entity Table by adding the following sparsely populated table extensio
67. protocols values should be calculated accordingly Chapter 3 Configuration Files 21 TABLE 3 1 provides these layer values TABLE 3 1 Internet Protocol Layer Functionality layer functionality 1 Physical for example repeaters 2 Datalink subnetwork for example bridges 3 Internet for example IP gateways 4 End to end for example IP hosts 7 Applications for example mail relays For systems including OSI protocols layers 5 and 6 can also be counted General Configuration This section describes the commands that enable general configuration of the agent Syntax agentgroup lt groupid gt Change to this groupid after opening the port The groupid can refer to a group by name or a number if the group number starts with For example specifying agentgroup snmp causes the agent to run as the snmp group and specifying agentgroup 10 causes the agent to run as the group with groupid 10 agentuser lt uid gt Change to this uid after opening the port The wid can refer to a user by name or a number if the user number starts with For example specifying agentuser snmp causes the agent to run as the snmp user and specifying agentuser 10 causes the agent to run as the user with uid 10 authtrapenable lt number gt 22 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Setting authtrapenable to 1 enables generation of authentication failure traps The defa
68. r 2006 TABLE 9 2 Physical Mapping Table entPhysicalindex entPhysicalChildIndex 1 2 1 3 1 4 2 5 3 6 4 7 4 12 6 8 6 9 6 10 8 11 Classes The ent PhysicalClass in an enumerated value that provides an indication of the general hardware type of a particular physical entity each of which is represented by a row in the entPhysicalTable The following list describes the set of ent PhysicalClass elements other 1 The enumeration other 1 applies if the physical entity cannot be classified by one of the following chassis 3 The chassis class represents an overall container for equipment Any class of physical entity can be contained within a chassis container 5 The container class applies to a physical entity that can contain one or more removable physical entities of the same or different type For example each empty or full slot in a chassis is modeled as a container Field replaceable units FRUs such as a power supply or fan are modeled as modules within a container entity Chapter 9 Sun SNMP Management Agent MIBs 57 m powerSupply 6 The power supply class applies to a component that can supply power such as a battery m fan 7 The fan class applies if the physical entity is a fan or other cooling device m sensor 8 The sensor class applies to a physical entity that is capable of measuring some physical property m module 9 The module class applies to a self contained sub system and wh
69. r Solaris operating system requirements See Related Documentation on page xvi of the Preface Disk Space Requirements At least 10 Mbytes must be available on the server Patches The following patches must be installed in addition to the standard Solaris Operating System software Writers note Bryan are there any required patches Installation and Additional Required Packages Installation packages TABLE 2 1 are supplied in the tar archive bundle SsUNWmasf lt ver gt tar Z where lt ver gt is the version number At the time of publication of this document the version is 1 4 Update 2 Always use the latest version of this file for installation Additional required packages TABLE 2 2 are available from the Solaris 10 Operating System DVD under cdrom cdrom0 s0 Solaris_10 Product These additional packages as well as the packages listed in the following note must be installed to enable support of the SNMP Management Agent Note TABLE 2 1 lists all packages contained in the tar archive bundle However the Sun Fire V1280 E2900 and Netra 1280 and 1290 servers require only the SUNWmasf and SUNWmasfr packages 4 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Installation Packages TABLE 2 1 SNMP Management Agent Software Installation Package Descriptions Package Package Name Function sUNWescdl Common Config Reader DAQ Library Framework for providing configuration
70. r messages from the agent For more information on troubleshooting see Chapter 4 On subsequent reboots the agent starts automatically without any user intervention Chapter 2 Installation 9 10 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 3 Configuration Files This chapter describes how to configure the SNMP agent The chapter contains the following sections Overview on page 11 Setting Up the Port Number on page 12 Setting Up Trap and or Inform Destinations on page 13 Configuring Access Control on page 14 SNMPv3 Configuration on page 20 Setting System Information on page 21 General Configuration on page 22 Updating the SNMP Agent When It Is Running on page 23 Co Existence With Other Agents on page 23 Overview You can configure the SNMP agent with the etc opt SUNWmasf conf snmpd conf file This file defines the ports where the agent can be accessed the access controls that it is to apply to management information and destinations for traps By default only the port number requires configuring after installation if m The agent is only to be used for SNMPv1 and or SNMPv2c accesses a The default community is acceptable No trap destinations are required The default configuration used by the agent enables read only access for the community public If this is not required or it is inappropriate for a particular
71. rativeState is locked 1 sunPlatLogOperationalState is disabled 1 a RowStatus is notInService 2 to indicate it is not in use sunPlatl sunPlatl sunPlatl sunPlatl sunPlatl Log Log Log Log RecordTable RecordAdditionalTable RecordAlarmTable RecordChange LogicalTable Table sunPlatUnitaryComputerSystemTable sunPlatInitialLoadInfol Table Additionally for the Sun Fire V1280 E2900 and Netra 1280 1290 servers the following tables are not completely populated m sunPlatEquipmentHolderTable m sunPlatCircuitPackTable Related Documentation For additional information about Sun Fire servers see Related Documentation on page xvit of the Preface 38 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Chapter 6 Platform Specific Information 39 40 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 pant I Technical Description and Functionality CHAPTER 7 Introduction to SNMP This chapter provides a brief introduction to the essential features of the Simple Network Management Protocol SNMP This chapter addresses the issues that are of particular relevance to the Sun Fire and Netra systems The chapter contains the following sections m SNMP Versions on page 43 m SNMP Managers and Agents on page 44 a SNMP Management Information Base on page 44 SNMP Versions SNMP is an open internet standard for managi
72. re and Netra Systems September 2006 To enable an NMS to manage a device via its agent the MIB corresponding to the data presented by the agent must be loaded into the manager The mechanism for doing this varies depending on the implementation of the network management software This gives the manager the information required to address and interpret correctly the data model presented by the agent Note MIBs can reference definitions in other MIBs so to use a given MIB it mightbe necessary to load others To address the content of this virtual data store the MIB is defined in terms of object identifiers OIDs An OID consists of an hierarchically arranged sequence of integers that defines a unique name space Each assigned integer has an associated text name For example the OID 1 3 6 1 corresponds to the OID name iso org dod internet and 1 3 6 1 4 corresponds to the OID name iso org dod internet private The numeric form is used within SNMP protocol transactions whereas the text form is used in user interfaces to aid readability Objects represented by such OIDs are commonly referred to by the last component of their name as a shorthand form To avoid confusion arising from this convention it is normal to apply a MIB specific prefix such as sunPlat to all object names defined therein thereby making all such identifiers globally unique Note The MIB is defined using a language known as ASN 1 the discussion of which is
73. s circuit packs that it may contain as shown in TABLE 10 5 Chapter 10 Physical Model 73 TABLE 10 5 Equipment Holder Status Attribute Values Attribute Values Description holderEmpty 1 There is no removable resource in the holder inTheAcceptableList 2 The holder contains a removable resource that is one of the types in the AcceptableTypes list notInTheAcceptableList 3 The holder contains a removable resource recognizable by the network element but not one of the types in the AcceptableTypes list unknownType 4 The holder contains an unrecognizable removable resource Powered This read write attribute is an enumerated type indicating the power state of the resource The possible values are other 1 unknown 2 powerOff 3 powerOn 4 sunPlat Power Supply The sunPlat Power Supply class is used to represent a power supply It does not extend the characteristics of the sunPlat Equipment class A power supply typically contains sensors representing monitored properties for example voltages current and temperature It can also contain other hardware resources such as fans This is modeled using relationships between the managed objects If a power supply is a removable resource it is modeled within a managed object of sunPlat Circuit Pack class This class has the entPhysicalClass powerSupply 6 The sunPlat Power Supply class has the following attribute Note The sunPlatPowerSupply prefix
74. s an enumerated type indicating the class of the sensor and takes the following values a binary 1 a numeric 2 m discrete 3 mg Type This read only attribute is an enumerated type identifying the property that the sensor measures Some of the possible values of Type are shown in TABLE 10 9 TABLE 10 9 Sensor Type Attribute Values Type Description temperature 3 A sensor for measuring the environmental temperature voltage 4 A sensor for measuring the electrical voltage current 5 A sensor for measuring the electrical current tachometer 6 A sensor for measuring the speed revolutions of a device counter 7 A general purpose sensor which counts defined events m Latency This read only attribute indicates the following a Where the sensor is polled this integer represents the update interval measured in milliseconds a Where the sensor is event driven this value represents the maximum expected latency in processing that event Chapter 10 Physical Model 79 sunPlat Binary Sensor A sunPlat Binary Sensor class is used to represent the characteristics of sensors that return binary output It augments the sunPlatSensor table to provide the attributes that are specific to binary sensors This class has the entPhysicalClass sensor 8 and the sunPlatSensorClass binary 1 The sunPlat Binary Sensor class has the following attributes Note The sunPlatBinarySensor prefix has been omitted from the following
75. s an integer indicating the defined threshold above which the sensor reading is not expected to rise This value is expressed in terms of the units of measurement as defined above The attribute may not be applicable to some sensors m Accuracy This read only attribute is an integer indicating the degree of error of the sensor for the measured property as a percentage to two decimal places The value can vary depending on whether the sensor reading is linear over its dynamic range m LowerNonCriticalThreshold This read only attribute is an integer indicating the lower threshold at which a nonCritical condition occurs m UpperNonCriticalThreshold This read only attribute is an integer indicating the upper threshold at which a nonCritical condition occurs m LowerCriticalThreshold This read only attribute is an integer indicating the lower threshold at which a critical condition occurs m UpperCriticalThreshold This read only attribute is an integer indicating the upper threshold at which a critical condition occurs m LowerFatalThreshold This read only attribute is an integer indicating the lower threshold at which a fatal condition occurs m UpperFatalThreshold This read only attribute is an integer indicating the upper threshold at which a fatal condition occurs m Hysteresis This read only attribute describes the hysteresis around the threshold values m EnabledThresholds This is read only attribute that when wri
76. sS amp o SUN microsystems Sun SNMP Management Agent Administration Guide for Sun Fire and Netra Systems Version 1 4 Update 2 For Sun Fire V210 V215 V240 V245 V250 V440 V445 V 1280 E2900 and Netra 210 240 440 1280 1290 Systems Sun Microsystems Inc www sun com Part No 817 2559 16 September 2006 Revision A Submit comments about this document at http www sun com hwdocs feedback Copyright 2006 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 U S A All rights reserved Sun Microsystems Inc has intellectual property rights relating to technology fiat is described in this document In particular and without limitation these intellectual property rights may include one or more of the U S patents listed at http www sun com patents and one or more additional patents or pending patent applications in the U S and in other countries This document and the product to which it pertains are distributed under licenses restricting their use copying distribution and decompilation No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors if any Third party software including font technology is copyrighted and licensed from Sun suppliers Parts of the s produet may be derived from Berkeley BSD systems licensed from the University of California UNIX is a registered trademark in the U S and in
77. statement provided in the file is removed 20 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Setting System Information This section describes the commands that you use to configure the system information in MIB II Syntax syslocation lt string gt syscontact lt string gt sysname lt string gt These parameters set the system location system contact or system name for the agent This information is reported in the system group the MIB II tree Normally these objects sysLocation 0 sysContact 0 and sysName 0 are read write However if you specify the value for one of these objects by giving the appropriate token the corresponding object becomes read only and subsequent attempts to set the value of the object result in a notWritable error response sysservices lt number gt This parameter sets the value of the system sysServices 0 object For a host an acceptable value is 72 The value of sysservices is a sum based on the network layers for which the node performs transactions For each layer L in the range 1 through 7 for which this node performs transactions 2 raised to L 1 is added to the sum For example a node that performs primarily routing functions would have a value of 4 2 3 1 In contrast a node which is a host offering application services would have a value of 72 2A 4 1 24 7 1 Note In the context of the Internet suite of
78. t model gt is the security model and can be any one of v1 v2c or usm m lt username gt specifies the security name which is defined elsewhere either in a com2sec or createUser directive 16 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 access access lt groupname gt lt context gt lt model gt lt level gt lt match gt lt read gt lt write gt lt notify gt The access directive specifies the access permissions to be given to a particular group security model combination m lt groupname gt specifies the name of the group to which the directive applies a lt model gt is the SNMP security model to which the access directive applies It can take the values of any v1 v2c or usm m lt level gt specifies the minimum level of authentication and encryption of the incoming requests for which this directive applies It can take the values noauth auth or priv m lt match gt specifies how lt context gt should be matched m against the context of the incoming pdu and takes the values exact or prefix exact specifies that lt context gt must be matched exactly a prefix specifies that the context must begin with lt context gt m lt read gt lt write gt and lt notify gt specify the view to be used for the corresponding access Note The lt notify gt field is ignored for the purposes of access control All access control for traps and informs is configured by mea
79. the modeled hardware resources and is not contained within any other resource This class has the entPhysicalClass chassis 3 Chapter 10 Physical Model 83 84 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 1 1 Traps This chapter describes the properties and function of traps The chapter contains the following sections m Overview on page 85 m Standard Trap Properties on page 87 Trap Types on page 88 Overview The SNMP agent provides traps to provide asynchronous updates to management applications The agent provides notifications for the following m Change of value within an object m Removal of an object from the management model a Addition of an object to the management model m Raising of an error or warning condition against a component within the model m Clearance of an error or warning condition The SNMP agent determines whether an error or warning condition exists against an object based on any sensors related to that object and or any sub components of that object For example a CPU can have an associated fan and the fan can have an associated tachometer All three components have an ability to report their operational status If the tachometer reports that it has a failed operational status this relates only to the health of the tachometer However if the tachometer reports that the speed of the fan has fallen below a particular threshold a trap
80. tion Files 13 The daemon sends a cold start trap when it starts up If enabled it also sends traps on authentication failures If lt community gt is not specified the string from a preceding trap community directive is used If no community has been specified the value public is used If lt port gt is not specified the well known SNMP trap port 162 is used CODE EXAMPLE 3 1 Using the trapsink and trap2sink Commands agentaddress 8161 localhost 9161 FE FE HE HE HE HE HE HE HE HE HE FE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HE HH HH HHHH SECTION Trap Destinations Here we defined who the agent will send traps to trapsink A SNMPv1 trap receiver arguments host community portnum trapsink merlin public 32768 trap2sink A SNMPv2 trap receiver arguments host community portnum trap2sink arthur This results in SNMPv1 traps being sent to the system merlin on port 32768 and SNMPv2 traps being sent to arthur using the default port for traps of 162 Configuring Access Control The agent supports the view based access control model VACM as defined in RFC 2575 It therefore recognizes the following keywords in the configuration file com2sec group access view t also recognizes some easier to use wrapper directives rocommunity rwcommunity rouser a a a Em rwuser 14 Sun SNMP Management Agent
81. tion dependent on the component being represented These extensions are based on the generic network information model NIM presented in ITU T M 3100 with further extensions taken from attributes defined by the common information model CIM v2 5 schema These MIBs are supported on other platforms enabling common management solutions to be developed The agent provided is intended to augment the management information such as MIB II already presented by the standard Solaris SNMP agent snmpdx Both agents run independently of each other Systems currently supported are Netra 210 Netra 240 Netra 440 Netra 1280 Netra 1290 Sun Fire V210 Sun Fire V215 Sun Fire V240 Sun Fire V245 Sun Fire V250 Sun Fire V440 Sun Fire V245 Sun Fire V1280 Sun Fire E2900 2 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 2 Installation This chapter describes how to install the management software The chapter contains the following sections System Requirements on page 3 Installation Packages on page 5 Effects on System Files on page 6 Installing the SNMP Software on page 7 Starting the SNMP Agent on page 9 System Requirements Before installing SNMP Management Agent ensure that your system complies with the prerequisites and dependencies discussed in this section Operating System Solaris OS Requirements Refer to the system manuals for your platform fo
82. to list all files computer output You have mail AaBbCc123 What you type when contrasted su with on screen computer output password AaBbCc123 Book titles new words or terms Read Chapter 6 in the User s Guide words to be emphasized Replace command line variables with real names or values These are called class options You must be superuser to do this To delete a file type rm filename The settings on your browser might differ from these settings Preface XV Related Documentation The documents listed as online are available at http www sun com products n solutions hardware docs Part Application Title Number Format Location Sun FireV210 and Sun Fire V210 and V240 Servers Installation Guide 816 4825 PDF HTML Online V240 Platforms Sun Fire V210 and V240 Servers Administration Guide 816 4826 PDF HTML Sun Fire V215 and Sun Fire V215 and V245 Servers Installation Guide 819 3037 PDF Online V245 Platforms Sun Fire V215 and V245 Servers Administration Guide 819 3036 Sun Fire V215 and V245 Servers Service Guide 819 3039 Sun Fire V250 Sun Fire V250 Server Installation Guide 817 0899 PDF Online Platform Sun Fire V250 Server Administration Guide 817 0900 Sun Fire V440 Sun Fire V440 Server Installation Guide 816 7727 PDF Online Platform Sun Fire V440 Server Administration Guide 816 7728 Sun Fire V445 Sun Fire V445 Server Installation Guide 819 3743 PDF Online Platform Sun Fire V4
83. tribute is an enumerated type indicating the unit of measurement prior to qualification as defined above Examples of values of this type are m degC 3 m volts 6 amps 7 mg Exponent This read only attribute is an integer that used to scale the Base Unit by some power of 10 For example if sunPlatNumericSensorBaseUnits is set to volts and sunPlatNumericSensorExponent is set to 6 the units of the values returned are microVolts m RateUnits This read only attribute is an enumerated type that indicates whether the sensor is measuring an absolute value when the value is none or a rate In the latter case the unit specified in sunPlatNumericSensorBaseUnits is expressed as per unit of time For example if sunPlatNumericSensorBaseUnits is set to degC and sunPlatNumericSensorRateUnits is set to perSecond the value represented has the units degC second Examples of values of this type are perMicrosecond 2 perMillisecond 3 perSecond 4 perMinute 5 perHour 6 none 1 m Current This read only attribute is an integer indicating the most recent value of the sensor m NormalMin This read only attribute is an integer indicating the defined threshold below which the sensor reading is not expected to fall This value is expressed in terms of the units of measurement as defined above The attribute may not be applicable to some sensors Chapter 10 Physical Model 81 m NormalMax This read only attribute i
84. tten to resets the sensors to their default values 82 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 sunPlat Discrete Sensor The sunPlat Discrete Sensor class is used for sensors that cannot be represented by the sunPlat Numeric Sensor or sunPlat Binary Sensor classes This class has the ent PhysicalClass sensor 8 and the sunPlatSensorClass discrete 3 The class comprises two tables The sunPlatDiscreteSensorTable has one attribute sunPlatDiscreteSensorCurrent which indicates the current state of the sensor expressed as an index in the sunPlatDiscreteSensorStatesTable The sunPlat Discrete Sensor class has the following attributes Note The sunPlatDiscreteSensorState prefix has been omitted from the following attribute names for clarity m Index This read only attribute takes a number that represents the index of a row in the sunPlatDiscreteSensorStatesTable which identifies this sensor state m Interpretation This read only attribute is a string describing the state represented by the corresponding row of the sunPlatDiscreteSensorStatesTable m Acceptable This read only attribute takes a boolean value that indicates whether the state represented by this row of the table is considered acceptable sunPlat Chassis The sunPlat Chassis class is used to represent the primary enclosure It does not extend the characteristics of the sunPlat Equipment class The chassis contains all
85. u must assign it a network port to use In deciding which network port to use consider a Whether other SNMP agents may be installed on the system m Where management application s may attempt to discover SNMP agents The conventional port for SNMP access is port 161 for data By default the Solaris snmpdx daemon uses this port You must make sure that this port is available for use by other agents such as snmpdx and Sun Management Center by using a port other than 161 for SNMP access to the agent provided by this product Configure the SNMP agent using the etc opt SUNWmasf conf snmpd conf file To set the port number add 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 wish to use traps in which case you must specify the trap destinations See Chapter 3 for more information 8 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 v Starting the SNMP Agent m Type etc init d masfd start You can confirm that the agent is correctly running by typing ps ef fgrep snmpd You should see a line of the form root 29394 10 Feb 18 4 11 opt SUNWmasf sbin snmpd If you do not see this output review the var adm messages logfile to locate any erro
86. uipment class The sunPlat Equipment class is derived from the Physical Entity superclass to provide the additional attributes defined in the corresponding classes that are applicable for fault monitoring The sunPlat Equipment Holder and sunPlat Circuit Pack classes are derived from the sunPlat Equipment superclass to represent receptacles and the components that plug into them respectively The sunPlat Equipment class is then further specialized to provide the DMTF derived classes 65 Physical Entity Serial Number IsFRU Hardware Revision Name Model Name Mfg Name Descr Index Contained In Firmware Rev Software Rev Location Operational Equipment Unknown Status state Administrative State Alarm Status Circuit Pack Availability Status Type Replaceable Hot Swappable Equipment Holder Type Status Acceptable Circuit Pack Types Watchdog Last Expired Monitored Entity Discrete Sensor Current Interpretation Acceptable Variable Speed Type State Urgency Accuracy Normal Min Normal Max Exponent Base Units Rate Units Current Hysteresis Numeric Sensor Lower Threshold Non Critical Upper Threshold Non Critical Lower Threshold Critical Upper Threshold Critical Lower Threshold Fatal Upper Threshold Fatal Enabled Thresholds Sensor Sensor Type Latency Powered Interpret True Expected Current F
87. ult value is disabled 2 Normally the corresponding object snmpEnableAuthenTraps 0 is read write but setting its value with this token makes the object read only and subsequent attempts to set the value of the object result in a notWritable error response Updating the SNMP Agent When It Is Running You can update the configuration file at any time either before starting the agent or once the agent has started If the agent is running it does not update its running configuration unless explicitly requested to do so To Force the SNMP Agent to Update m Type kill HUP lt pid gt Co Existence With Other Agents The SNMP agent must be configured to use a specific network port and this cannot be shared with any other component on the system However master agent technologies can enable multiple SNMP agents on a system to appear as a single entity to management applications To use such solutions configure this agent to use a port that is known to the master agent which then presents an aggregated OID space Chapter 3 Configuration Files 23 24 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 CHAPTER 4 Troubleshooting The Sun SNMP Management Agent has been designed so that it can provide full SNMP capabilities without further need for complex configuration This chapter provides additional information should you experience problems using the agent The chapter contains
88. used to represent the characteristics of hardware resources that emit indications relating to problem situations for instance buzzers LEDs relays vibrators and software alarms This class has the entPhsicalClass other 1 and the sunPlatPhysicalClass alarm 2 The sunPlat Alarm class has the following attributes Note The sunPlatAlarm prefix has been omitted from the following attribute names for clarity mg Type This read only attribute is an enumerated type representing the means by which the alarm condition is communicated The possible values are shown in TABLE 10 7 TABLE 10 7 Alarm Type Attribute Values Attribute Values Description other 1 The alarm device type is not one of the following audible 2 The alarm device is audible change on the device visible 3 The alarm causes a visible change on the device motion 4 The alarm causes motion of the device switch 5 The alarm causes an electrical signal change m State This read write attribute is an enumerated type representing the state of the alarm The possible values are shown in TABLE 10 8 Chapter 10 Physical Model 77 TABLE 10 8 Alarm State Attribute Values Attribute Values Description unknown 1 The state of the alarm is undefined or unobservable off 2 The alarm is inactive steady 3 The alarm is active alternating 4 The alarm is cycling between its inactive and active states mw Urgency This read write attribute is an
89. y applying the exponent value provided by sunPlatNumericSensorExponent For binary sensors a trap is sent when the value reported by sunPlatBinarySensorCurrent is not the same as that specified by sunPlatBinarySensorExpected A trap indicating the problem has cleared is sent when sunPlatBinarySensorCurrent returns to the same value as sunPlatBinarySensorExpected For any binary sensor you can determine the precise semantics of the reported values from the descriptions supplied by sunPlatBinarySensorInterpretTrue and sunPlatBinarySensorInterpretFalse To configure the agent to send traps to a particular management application please see Chapter 3 86 Sun SNMP Management Agent for Sun Fire and Netra Systems September 2006 Standard Trap Properties The information communicated in traps generated by the agent is based on a common set of attributes For clarity the sunPlatNotification prefix has been omitted from the following attribute names mg Eventid This is an integer uniquely identifying the notification and an indication of the order in which the notifications were generated by the agent Note The agent does not guarantee that its sequencing reflects the order of the underlying events from which the notifications were generated m Time This is a timestamp indicating the time at which the notification was generated m Object This attribute is an OID that provides a direct reference to an entry in the MIB repres
90. y Table to provide further information for managed objects of the Equipment class This class is applicable for all Sun SNMP Management Agent hardware resources Subclasses of the Equipment class are represented by further Table Extensions a Equipment Holder Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the container 5 entPhysicalClass a Circuit Pack Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the module 9 entPhysicalClass a Physical Table Extension This extends the Physical Entity Table It is used to supplement the entPhysicalClass column in the Physical Entity Table If a resource has an entPhysicalClass of other 1 but is of a class modeled by sunPlat that is the Watchdog or AlarmDevice class this table identifies its sunPlatPhysicalClass Sensor Table Extension This extends the Equipment Table Extension It provides the additional information relevant for managed objects of the entPhysicalClass sensor 8 Subclasses of Sensor class are represented by further Table Extensions and identified by this table using sunPlatSensorClass a Binary Sensor Table Extension This extends the Sensor Table Extension It provides additional information relevant for managed objects of the entPhysicalClass sensor 8 and sunPlatSensorClass binary 1 a Numeric
91. you need to address the underlying network connectivity issues Make sure that the client has the necessary access permissions for the SNMP agent If you are using SNMPv1 or SNMPv2c make sure that the community string specified by the client is the string expected by the agent If you are using SNMPv3 make sure that passwords for authentication have been correctly specified Failure to Receive Traps The most likely reason for not receiving traps is failure to specify the trap destination for the SNMP agent Confirm which version of trap the management application is expecting then look at the file etc opt SUNWmasf conf snmpd conf For an SNMPv1 trap there must be a line of the form trapsink lt hostname gt where lt hostname gt is either the name of the host or the IP address of the destination For an SNMPv2 trap the entry should read trap2sink lt hostname gt Chapter 4 Troubleshooting 27 From the system running the SNMP agent use ping to confirm that the chosen destination can be accessed over the network ping lt hostname gt If the ping fails it is necessary to confirm network connectivity before taking any further steps If traps are still not received confirm whether the management application is able to receive traps If the management application has received traps from other hosts no further action is necessary to confirm this However if this is the first time the mana

Download Pdf Manuals

Related Search

Related Contents

HI 9033 • HI 9034 - Hanna Instruments Canada  TDSHーBA セミオ=ダ離ライ卜取扱説明書 屋内用 保存用  Homelite HG5700 Portable Generator User Manual  SMD METER  Infokit Les aspirateurs    Manuale utente ruote Bora Ultra copertoncino  PowerPoint プレゼンテーション  OPフッ化バリウム - ステラ ケミファ  Panasonic CS-RE12PKE air conditioner  

Copyright © All rights reserved.

• https://telegra.ph/DC-Voltage-Drop-Calculator-c112894c-11-16
• https://telegra.ph/DC-Voltage-Drop-Calculator-6f0055ed-11-16
• https://telegra.ph/Concrete-Volume-Calculator-for-Curbs-Gutters-25b9380e-11-16
• https://telegra.ph/Round-Column-Concrete-Volume-Calculator-1f5850ed-11-16
• https://telegra.ph/Square-Column-Concrete-Volume-Calculator-8a7816f6-11-16
• https://telegra.ph/Concrete-Mix-Calculator-c5af6567-11-16
• https://telegra.ph/Round-Column-Concrete-Volume-Calculator-14fe396e-11-16
• https://telegra.ph/Round-Column-Concrete-Volume-Calculator-d5523230-11-17
• https://telegra.ph/Square-Column-Concrete-Volume-Calculator-9e2ae18b-11-13
• https://telegra.ph/rebar-weight-calculator-cee468c4-11-07