Fujitsu ServerView Event Manager User Manual
  1. Manuals
  2. Brands
  3. Fujitsu Manuals
  4. Software
  5. ServerView Event Manager
  6. User manual
Fujitsu ServerView Event Manager User Manual

Fujitsu ServerView Event Manager User Manual

Serverview operations manager v6.12
Hide thumbs
Table of Contents

Quick Links

User Guide - English
ServerView Suite
ServerView Event Manager
ServerView Operations Manager V6.12
Edition February 2013
Table of Contents
loading

Related Manuals for Fujitsu ServerView Event Manager

Summary of Contents for Fujitsu ServerView Event Manager

  • Page 1 User Guide - English ServerView Suite ServerView Event Manager ServerView Operations Manager V6.12 Edition February 2013...

  • Page 2: Copyright And Trademarks

    Gesellschaft für Technik-Dokumentation mbH www.cognitas.de Copyright and Trademarks Copyright © 2013 Fujitsu Technology Solutions GmbH. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers.

  • Page 3: Table Of Contents

    Contents Introduction ......7 Changes from the previous version ....8 ServerView Suite link collection .
  • Page 4 Contents Alarm configuration ..... . . 35 Alarm rules ......37 4.1.1 Managing alarm rules .
  • Page 5 Tape drive traps (tapealrt.mib) ....145 5.3.22 Team Server traps (Fujitsu) ....158 5.3.23 Threshold traps (Trap.mib) .
  • Page 6 Contents ServerView Event Manager...

  • Page 7: Introduction

    Introduction The ServerView Event Manager (called simply Event Manager below) is a component of the Event Management of the ServerView Suite. After installation, this component is available both via the Windows Start Menu and via ServerView Operations Manager (called simply Operations Manager below). The Event Manager function has a user-friendly Web-based graphical user interface (GUI) where you can obtain reliable, secure information about system faults quickly.

  • Page 8: Changes From The Previous Version

    Changes from the previous version Changes from the previous version This edition is valid for the Event Manager of ServerView V6.12 and replaces the online manual: “Event Manager“ as of ServerView V6.00 Edition July 2012. The manual has been updated to reflect the latest software status. ServerView Event Manager...

  • Page 9: Serverview Suite Link Collection

    ServerView Suite link collection ServerView Suite link collection Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. For ServerView Suite, links are offered on the following topics:...

  • Page 10: Documentation For Serverview Suite

    This opens the start page of the ServerView link collection. 2. Via the ServerView Suite DVD 2 or via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server. You access the start page of the online documentation via the following link: http://manuals.ts.fujitsu.com...

  • Page 11: Notational Conventions

    Notational conventions Notational conventions The following notational conventions are used in this manual: Caution This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment. This symbol highlights important information and tips. This symbol refers to a step that you must carry out in Ê...
  • Page 12 Notational conventions ServerView Event Manager...

  • Page 13: Event Manager

    Event Manager The Event Manager allows you to filter and forward alarm messages and specify the display. For monitoring, ServerView agents must be installed on the managed servers and for servers with VMware vSphere ESXi 5 ServerView ESXi 5 CIM Provider must be installed.

  • Page 14: First-Time Startup

    First-time startup CIM-Indications for VMware vSphere ESXi 5 Events of servers with VMware vSphere ESXi 5 are provided as CIM indications. The CIM indications are analyzed by the ServerView Event Manager, which can manage and forward them as usual. Via Test Connectivity you can test the connection to the VMware vSphere ESXi 5 server (see User Guide „ServerView Operations Manager“...

  • Page 15: Starting The Event Manager

    Starting the Event Manager Starting the Event Manager You start the Event Manager either via the ServerView Operations Manager start screen or via the ServerList main window. 1. Start ServerView Operations Manager. How to do this is described in the documentation for ServerView Operations Manager.

  • Page 16: Icons

    Icons Icons You will find a list of the icons in the Alarm Monitor and Alarm Configuration windows and their meanings in the following. Red alarm: critical Orange alarm: major Yellow alarm: minor Blue alarm: informational Gray alarm: unknown Alarm is ignored The alarm was confirmed by a user entry.
  • Page 17 Icons Yellow: Forwarding completed Red: Forwarding present (still active) Table columns can be filtered according to different criteria. Table 2: Icons in the Alarm Monitor and Alarm Configuration ServerView Event Manager...
  • Page 18 Icons ServerView Event Manager...

  • Page 19: Alarm Monitor

    Alarm Monitor The Alarm Monitor component displays all received alarms relating to the selected servers and server groups in the Operations Manager main window. Viewing alarms You start the Alarm Monitor via the Operations Manager start window by clicking the Alarm Monitor link under Event Management (see section "Starting the Event Manager"...
  • Page 20 Viewing alarms The window is divided into four sections: The menu bar below the title bar allows you to navigate between the Operations Manager functions: – Serverlist – Administration – Asset Management – Event Management – Monitoring – Update Management –...
  • Page 21 Viewing alarms Below the status bar the alarm entries are displayed with the following information: Receive Time Time when the alarm was received. Alarm Type Brief description of the alarm. Alarm icon (see table below) Indicates the severity of the alarm. Server Server name.
  • Page 22 Viewing alarms An executable program was triggered by this alarm. This alarm was forwarded to the management station. Table 3: Icons in the Alarm Monitor In the bottom right section of the window you can find out information on the selected alarm entry in the alarm list via the two or three tabs provided: –...

  • Page 23: Viewing Alarms For A Server

    Viewing alarms for a server Viewing alarms for a server If several alarm messages have been received for a server, the one with the highest severity level is displayed in the server list. In the bottom display area you will only see information on the last alarm message received with this severity.

  • Page 24: Processing Alarm Entries

    Processing alarm entries Processing alarm entries The following functions are available for processing the alarm entries: – Acknowledge alarms – Suppress alarms – Reset alarm suppression – Delete alarms 3.4.1 Acknowledging alarms You can acknowledge alarms that have been received. Proceed as follows: Ê...

  • Page 25: Resetting Alarm Suppression

    Processing alarm entries When the server starts up, a RAID manager or Ethernet card, etc. may issue an alarm (SNMP trap) as a startup notification (e.g. RFC1157LinkUP). To suppress this kind of alarm, you can configure alarm suppression. This function must be specified for each server. If multiple servers are monitored, configure this setting for each server using the alarm function.

  • Page 26: Testing The Connection

    Testing the connection Testing the connection To test the connection to a specific server, you can send a trap. Proceed as follows: Ê Select Test Trap from the context menu. The Test Trap window opens: Ê Either select the server from the list under Serverlist, Ê...

  • Page 27: Other Settings

    Other settings Other settings 3.6.1 Editing an alarm note You can edit the note displayed for an alarm entry: Ê Click the relevant alarm entry. Ê Select Edit Note from the context menu. The Edit Note window opens: Ê Enter your text. Ê...

  • Page 28: Irmc S2/S3 Sel Entries Relayed As Sc2 Mib Traps

    iRMC S2/S3 SEL Entries and SC2 MIB Traps iRMC S2/S3 SEL entries relayed as SC2 MIB traps The following table applies to PRIMERGY systems manufactured in 2009 or later. If the iRMC S2/S3 writes an event to the System Event Log (SEL), in some cases an SNMP trap is triggered.
  • Page 29 iRMC S2/S3 SEL Entries and SC2 MIB Traps Error iRMC S2/S3 SEL Trap text Trap Trap name code entry 040003 ’FAN XY’: Redundant The redundant fan 2015 sc2Trap fan failed ’FAN XY’ failed in RedundantFan cabinet XY of server Failed XY.
  • Page 30 iRMC S2/S3 SEL Entries and SC2 MIB Traps Error iRMC S2/S3 SEL Trap text Trap Trap name code entry 070001 ’PSU XY’: Power Power supply ’PSU 2030 sc2TrapPower supply OK XY’ in cabinet XY at SupplyAdded server XY was added. Power supply ’PSU 2032 sc2TrapPower XY’...
  • Page 31 iRMC S2/S3 SEL Entries and SC2 MIB Traps Error iRMC S2/S3 SEL Trap text Trap Trap name code entry 07000A ’PSU XY’: Power Temperature at 2037 sc2TrapPower supply critical power supply ’PSU SupplyCritical temperature XY’ in cabinet XY of Temperature server XY has reached the critical level.
  • Page 32 iRMC S2/S3 SEL Entries and SC2 MIB Traps Error iRMC S2/S3 SEL Trap text Trap Trap name code entry 120030 PCI system error The system wa 2006 sc2TrapSevere (SERR): Slot 0x%1 restarted after a SystemError severe problem at 120031 PCI parity error cabinet XY of server (PERR): Slot 0%1 XY.
  • Page 33 iRMC S2/S3 SEL Entries and SC2 MIB Traps Error iRMC S2/S3 SEL Trap text Trap Trap name code entry 150031 Battery voltage ’BATT Battery voltage 2054 sc2TrapBattery XY’ low warning: % ’BATT XY’ in cabinet VoltagePrefail Volt XY at server XY: Battery is predicted to fail in near future.
  • Page 34 iRMC S2/S3 SEL Entries and SC2 MIB Traps Error iRMC S2/S3 SEL Trap text Trap Trap name code entry 190017 ’DIMM XY’: Memory Memory module 2070 sc2TrapMem replaced by spare ’DIMM XY’ in cabinet ErrorModule memory XY of server XY had Replaced failed and was replaced by a hot-...

  • Page 35: Alarm Configuration

    Alarm configuration The Alarm Configuration component in the Event Manager is used to define settings for alarm handling. You can define alarm rules, filter rules and general settings. The alarm rules define which alarms are forwarded from which servers to which destinations (see section "Alarm rules"...
  • Page 36 Alarm configuration The first time the window opens, the right-hand section shows the Alarm Rules – Manage Alarm Rules dialog window. The Previous and Next buttons take you step by step through the individual screens for setting the alarm parameters. You can also call up the individual screens directly by clicking the entries in the menu tree.

  • Page 37: Alarm Rules

    Alarm rules Alarm rules An alarm rule forwards alarms from various servers to one or more destinations. A complete definition of a new alarm rule consists of the following four steps: – Defining the name of the new alarm rule (see section "Managing alarm rules"...

  • Page 38: Managing Alarm Rules

    Alarm rules 4.1.1 Managing alarm rules The Alarm Rules – Manage Alarm Rules screen provides an overview of all defined alarm rules. The tabs Alarm Rules, Alarms, Servers and Destinations allow different views of the defined alarm rules, depending on which tab is selected. The Add button allows you to add new alarm rules.
  • Page 39 Alarm rules Alarm Rules tab The Alarm Rules tab is used to assign alarm rules to alarms, servers and alarm destinations. The first column lists all known alarm rules. The enabled column indicates which alarm rules are activated (checkmark) and which are deactivated. By clicking in the enabled column you can set or remove a checkmark.
  • Page 40 Alarm rules Servers tab The Servers tab shows you which servers are covered by which alarm rules. Here you can check whether alarms from a server are at least being forwarded to one destination. The first column lists all known and unfiltered servers in alphabetical order (see section "Server filters"...

  • Page 41: Assigning Servers

    Alarm rules 4.1.2 Assigning servers In the Alarm Rules – Assign Server screen, you define the servers and/or server groups to be assigned to an alarm rule. Figure 4: Alarm Rules - Assign Servers Via the drop-down list, you can select the alarm rule that you want to edit. The file tree in the Serverlist box contains all known and unfiltered servers.
  • Page 42 Alarm rules Because different server groups can have the same name, they are displayed in the Alarm Configuration component with their group hierarchy. Figure 5: Alarm Rules - Assign Servers group hierarchy You can use the following buttons to specify which servers are to belong to this alarm rule: >...

  • Page 43: Displaying Server Information

    Alarm rules 4.1.2.1 Displaying server information If you select Show Information about Server from the context menu,the Server information window opens, showing additional information about the selected server. Figure 6: Server information The header gives the server name accompanied by a status icon which indicates the current server status.
  • Page 44 Alarm rules You can start Operations Manager for the selected server in this window. To do this, click the status icon in the top right-hand corner. The status display, the server picture and the start command for Operations Manager are only enabled if Operations Manager is already installed.

  • Page 45: Assigning Alarms

    Alarm rules 4.1.3 Assigning alarms In the Alarm Rules – Assign Alarms dialog box you can define in the Individual Alarms dialog box the alarms for the alarm rule and display all details of the assigned alarms. In the Type of Alarms dialog box you can define for selected alarm rules what kind of alarms are to be forwarded.
  • Page 46 Alarm rules The alarm list in the bottom section of the window shows via checkboxes which alarms are assigned to the alarm rule. It also shows the names of the alarms (Alarm Name), their severity (Severity), their MIB file (MIB), in which the alarm is defined, and their trap name (Identifier).
  • Page 47 Alarm rules The alarm list offers a context menu, in which you can select the following items: Show information about selected Alarm To see additional information on the selected alarm Check all alarms To add all currently known alarms to the alarm rule Check selected alarm(s) To add the selected alarms to the alarm rule Uncheck all alarms...
  • Page 48 Alarm rules The top drop-down list contains the names of all known alarm rules. Here you can select the alarm rule that you want to edit. You can activate or deactivate the following filter settings: All alarms of severity critical All alarms of severity critical are handled according to the alarm rule.

  • Page 49: Forwarding Alarms

    Alarm rules 4.1.4 Forwarding alarms In the Alarm Rules – Assign Destinations screen you can make settings relating to alarm destinations. Select an alarm rule and then define the actions to be triggered for the servers of this alarm rule in response to certain alarm messages.
  • Page 50 Alarm rules You can use the following buttons to activate or deactivate the forwarding of an alarm: > Activates the selected destinations. < Deactivates the selected destinations. >> Activates all known destinations. << Deactivates all known destinations. Clicking the Apply button saves the new settings. Clicking the Reset button restores the settings from the last save.
  • Page 51 Alarm rules By clicking the Add button you can define a new destination. The following window opens showing the available destinations. Figure 10: Type of New Destination Clicking OK opens additional windows, depending on your selection, in which you must make further settings. There, via different tabs, you can define all the parameters necessary for forwarding.
  • Page 52 Alarm rules Note for SMTP AUTH For sending mails, SMTP AUTH is supported. The supported authentication method is: CRAM MD5 / LOGIN / PLAIN. The authentication method used when you send a mail automatically switches to the safest method compatible with the authentication method supported by the destination SMTP server.

  • Page 53: Filter Rules

    Filter rules Filter rules The filter rules define the servers or server groups from which you want to filter out alarms (see section "Server filters" on page 53) and/or which alarms are to be filtered out (see section "Filtering alarms" on page 54).

  • Page 54: Filtering Alarms

    Filter rules 4.2.2 Filtering alarms In the Filter Rules – Alarm Filtering dialog box you can activate or deactivate filter settings for an alarm type. Figure 11: Filter settings for an alarm type You can activate or deactivate the following filter settings: All unknown alarms Filter out unknown alarms.
  • Page 55 Filter rules In the input field Set time for repetition in seconds you can specify the interval after which the same alarm is allowed through from the same server again. This is useful to prevent the management station from being bombarded with identical alarms from a server that is not running correctly.

  • Page 56: Making Settings

    Making settings Making settings In the General Settings screen you can define general settings for alarm handling. You can define the actions to be executed by default and regardless of the alarm groups whenever an alarm arrives. You can define the following actions: –...

  • Page 57: Mail Forwarding In General

    ServerView. The Readme files are located – on Windows in: /ServerView/common/readme.txt – on Linux in: /usr/share/doc/fujitsu/ServerViewSuite/en/README /usr/share/doc/fujitsuServerViewSuite/jp//README Making mail settings If you have selected Mail for the forwarding, the following New Mail Configuration window opens. ServerView Event Manager...
  • Page 58 Mail forwarding in general Figure 12: New Mail Configuration In this window you can define all the necessary parameters for forwarding on the Mail Settings, Mail Properties and Time Model Settings tabs. Fields marked with * are mandatory, while the other fields are optional. ServerView Event Manager...
  • Page 59 Mail forwarding in general Mail Settings tab The Mail Settings tab provides fields for the mail settings, some of which already contain predefined settings. The input fields in the Mail Settings window have the following meanings: Name Meaning Description Name of the mail settings If you want to change the mail settings for an existing mail forwarding (see Edit button, section "Forwarding...
  • Page 60 Mail forwarding in general Mail Properties tab The Mail Properties tab provides fields for the mail server. Depending on the mail service, MAPI (Windows only) or SMTP (Windows, Linux) must be selected. Depending on the selected mail service, different input fields are enabled in the Mail Properties window.
  • Page 61 Mail forwarding in general Time Model Settings tab The Time Model Settings tab allows you to select, add or modify a time model. You can define hour by hour for the whole week when an alarm is to be forwarded. If you click the Test Address button, a test mail is sent to check your settings.

  • Page 62: Mail Forwarding To The Service Provider

    Mail forwarding to the service provider Mail forwarding to the service provider The Event Manager allows you to automatically forward alarms to the service provider by e-mail. If mail forwarding to the service provider is activated, the service provider is notified by e-mail whenever certain traps occur.
  • Page 63 Mail forwarding to the service provider You can enable or disable this configuration with the Enabled option. If you click the Mail Properties tab, you can specify additional information on the mail service in this window. Depending on the mail service, you must select MAPI (Windows only) or SMTP (Windows, Linux).
  • Page 64 Mail forwarding to the service provider A minimum period of 600 seconds has been specified for the sending of identical mails. This ensures that redundant messages are not sent. In the Alarm Monitor, traps that have triggered a service mail are identified as follows: This icon identifies a trap that has been forwarded using the service mail function.

  • Page 65: Making Pop-Up Settings

    Making pop-up settings Making pop-up settings If you have selected Popup for the forwarding, the New Popup Configuration window opens. In this window you can use the Popup Settings and Time Model Settings tabs to make all necessary settings for pop-up forwarding. Pop-up notifications are only displayed on the local host.
  • Page 66 Making pop-up settings Notes for Linux 1. To receive the forwarded alarm messages, a user must be logged onto the Linux system console. If no user is logged on, the forwarded alarm messages are not saved. This means that they will not be output the next time a user logs onto the system console.

  • Page 67: Making Pager Settings (Com Port And Modem)

    Making pager settings (COM port and modem) Making pager settings (COM port and modem) If you have selected Pager for the forwarding, the New Pager Configuration window opens. In this window you can use the Pager Settings and Modem Settings tabs to make the different settings for the serial interfaces and the modems connected to them (pager types).
  • Page 68 Making pager settings (COM port and modem) Name Meaning Time Model Time model indicating when an alarm is to be forwarded. Select a predefined time model from the drop-down list. You can set your own time model via the Time Model Settings tab. Retry Delay Delay in minutes between two pager attempts.
  • Page 69 Making pager settings (COM port and modem) You specify the pager service via the Pager, SMS-1 or SMS-2 tabs. The Server Num tab tells you which server numbers are assigned to which server name. The server number is sent to the pager type numeric. You can test your settings by clicking the Test button.

  • Page 70: Making Execute Settings

    Making execute settings Making execute settings If you have selected Execute for the forwarding, the New Execute Configuration window opens. In this window you can use the Exec Settings and Time Model Settings tabs to make all necessary settings for the Execute forwarding. Exec Settings tab The Exec Settings tab offers fields for the Execute settings, some of which already contain predefined settings.

  • Page 71: Making Broadcast Settings

    Making broadcast settings Time Model Settings tab The Time Model Settings tab allows you to select, add or modify a time model. You can define hour by hour for the whole week when an alarm is to be forwarded. For Windows Server 2008, the CUI command is the only command that can be used for the program execution.
  • Page 72 Making broadcast settings Name Meaning Mode Mode for the broadcast forwarding Special user Only one user is notified, whose name must be entered here. All users of All users belonging to the same domain for the domain forwarding are notified. (Valid only with Windows, default.) As of Windows Server 2008, domain is no longer supported.
  • Page 73 Making broadcast settings Notes for Linux The forwarding service uses the database under /var/run/utmp (utmp(5)) to obtain information on the connected users and the type of the session (GUI or CLI). All sessions (local or remote) should therefore be correctly registered in the utmp database.

  • Page 74: Making Trap Settings

    Making trap settings 4.10 Making trap settings If you have selected Station for the forwarding, the New Station Configuration window opens. In this window you can use the Station Settings and Time Model Settings tabs to make all necessary settings for trap forwarding. Station Settings tab The Station Settings tab offers fields for the trap settings, some of which already contain predefined settings.
  • Page 75 Making trap settings Name Meaning Forwarding The mode for the forwarding. Mode Normal This mode evaluates the alarm and forwards it to the management station. Pass This mode is available in an original variant and in the Through variant Transparent. The original variant passes the alarm directly through to the management station.

  • Page 76: Macros

    ID number of the server $_OMS Name of management station $_MIB MIB file name of the received alarm $_SPC Specific number of the received alarm $_MDL Fujitsu REMCS ID of a hardware which is reporting the alarm Table 16: Macros ServerView Event Manager...

  • Page 77: Alarm Configuration Example

    Alarm configuration example 4.12 Alarm configuration example This section explains a typical example of alarm configuration. Purpose When an event whose severity is critical occurs on the ALARMTEST server, a mail is sent to the administrator ([email protected]). Requirements – ServerView agent is running on the server, and the server is registered as a management target in ServerView Operations Manager on the same network.
  • Page 78 Alarm configuration example Ê Click Apply, then click Next. The Assign Alarms - Individual Alarms window opens. Ê Click Next again. The Assign Alarms - Type of Alarms window opens. Ê Check All alarms of severity critical. Ê Click Apply, then click Next. The Assign Destinations window opens.
  • Page 79 Alarm configuration example Ê Click Apply, then click Test Address. Ê Once the test mail is sent successfully, click OK. This returns you to the Assign Destinations window. Ê Select the created MailSet, then click the > button. Ê Click Apply. ServerView Event Manager...
  • Page 80 Alarm configuration example ServerView Event Manager...

  • Page 81: Traps

    Traps If a special event occurs in a network component, then the SNMP agent can send a message to one or more managers to inform them of the event. Such messages are called traps in SNMP. The manager can react to events in the network based on the incoming trap.
  • Page 82 Displaying trap information Ê Under Alarms, select the Agent Alarm Information option. The trap information can also be called up in the same way via the start window of ServerView Operations Manager. The Alarm Mibs window is displayed: Figure 13: MIB overview in the Event Manager - example ServerView Event Manager...
  • Page 83 Displaying trap information When you select a MIB, a window with detailed trap information will open; the window will look like this: Figure 14: Detailed information about the traps from a MIB (example) If you want to print out this information, select the Print button in the window. ServerView Event Manager...

  • Page 84: Displaying Traps In The Windows Event Log

    When you install the Windows agents, you can specify whether the traps from the Fujitsu MIB (e.g. HD.MIB, Mylex.MIB) are also to be written to the Windows event log. The trap ID in the event log is shown increased by 10000 and not as in the subsequent trap descriptions (e.g.
  • Page 85 Trap overview Traps from Comments baspTrap.mib Broadcom Advanced Server traps BIOS.mib BUS.mib clariion1.mib FibreCat clariion_fsc_2.mib FibreCat Cmc32.mib Rittal rack monitor CMS-TC.mib Ddm.mib DuplexDataManager traps page 103 dec.mib Compaq StorageWorks Enterprise Array page 123 Manager desktrap.mib DeskView traps dhtraps.mib domagt.mib dptscsi.mib DPT SCSI traps page 101 Duralink.mib...
  • Page 86 Trap overview Traps from Comments Ldcm.mib LAN Desk Client Manager from Intel traps page 160 Ldsm.MIB LAN Desk Server Manager from Intel traps page 160 log3v1.mib PRIMEPOWER log entries page 118 Lsi1030.mib LSIRAID-IDE.mib Megaraid.mib RAID adapter from American Mega Trends page 127 Inc.
  • Page 87 Trap overview Traps from Comments PSA- PRIMEQUEST traps LinBcm5700Trap- MIB.mib PSA-LinEmulexTrap- PRIMEQUEST traps MIB.mib PSA-LinGdsTrap- PRIMEQUEST traps MIB.mib PSA-LinGlsTrap- PRIMEQUEST traps MIB.mib PSA-LinGrmpdTrap- PRIMEQUEST traps MIB.mib PSA- PRIMEQUEST traps LinIntelE1000Trap- MIB.mib PSA- PRIMEQUEST traps LinIntelE100Trap- MIB.mib PSA- PRIMEQUEST traps LinLanComTrap- MIB.mib PSA- PRIMEQUEST traps...
  • Page 88 RMS- C_SNMPv1_humid2. RMS- C_SNMPv1_main.mi RMS- C_SNMPv1_output. RMS- C_SNMPv1_temp2. Rompilot.mib RomPilot traps page 130 S31.mib Blade server traps SANMgrV1.mib Pathlight SAN Data Gateway SC.mib ServerControl traps page 131 SC2.mib SECURITY.mib Servervi.mib FUJITSU ServerVisor traps Table 17: MIB overview ServerView Event Manager...
  • Page 89 Trap overview Traps from Comments ServerView.mib ServerView traps page 143 Status.mib ServerView status traps page 144 tapealrt.mib Tape driver traps page 145 Threshold.mib TOK.mib Trap.mib ServerView traps page 161 trap1493.mib Switch traps trap1757.mib Switch traps unicorn-trap.mib uniserv.mib PRIMEPOWER Enterprise Server page 119 UNIX.mib Upsman.mib...

  • Page 90: Adaptec Traps (Duralink.mib)

    Trap overview 5.3.1 Adaptec traps (Duralink.mib) MIB-OID: 1.3.6.1.4.1.795.3.1.2.3 This section lists Adaptec traps in alphabetical order. Trap name Meaning Error class duralinkStatusTrap The link status has informational changed. failoverStatusTrap The failover status has informational changed. Table 18: Adaptec traps 5.3.2 APC traps (Powernet.mib) MIB-OID: 1.3.6.1.4.1.318 This section lists the APC traps in alphabetical order.
  • Page 91 Trap overview Trap name Meaning Error class communication Communication is established informational Established between the agent and power supply. communicationLost Communication between the major agent and power supply was interrupted. contactFault One of the contacts on the major Measure UPS has changed from its default position.
  • Page 92 Trap overview Trap name Meaning Error class softwareBypass The UPS has been set to minor bypass by a user via software or via the UPS front panel. switchedBypass The UPS has been set to minor bypass by a user via the switch on the back.

  • Page 93: Blade System Traps (S31.Mib)

    Trap overview 5.3.3 Blade System traps (s31.mib) MIB-OID: 1.3.6.1.4.1.7244.1.1.1 This section lists the blade system traps in alphabetical order. Trap name Meaning Error class s31LivetimeError 1644 The lifetime of the blade informational system has exceeded the limited count. s31MgmtBladeAdded 1601 A management blade was informational added to the blade system.
  • Page 94 Trap overview Trap name Meaning Error class s31ServerBladeError 1609 The server blade status at critical the blade system is error. s31ServerBladeHot 1640 A server blade was added informational Replace by hot replace. s31ServerBladeNewAdd 1639 A server blade was added informational on an empty slot of the blade system.
  • Page 95 Trap overview Trap name Meaning Error class s31SwitchBladeAdded 1611 A switch blade was added informational to the blade system. s31SwitchBladeCritical 1615 The switch blade status at critical Error the blade system is critical. s31SwitchBladeError 1614 The switch blade status at major the blade system is error.
  • Page 96 Trap overview Trap name Meaning Error class s31SysPowerSupplyRemo 1627 A power supply unit was informational removed from the blade system. s31SysTempCriticalError 1623 The temperature at the critical system temperature sensor of the blade server has reached the critical level. s31SysTempError 1622 The temperature at the major system temperature...
  • Page 97 Trap overview Trap name Meaning Error class s31TrapEventLog 1638 An error was recorded on major the blade system. See the server management event error log (Recovery) for detailed information. s31UserAuthentication 1637 An user authentication major Failure failure was detected at the blade system.

  • Page 98: Cluster Traps (Ntcluster.mib)

    Trap overview 5.3.4 Cluster traps (NTCluster.mib) MIB-OID: 1.3.6.1.4.1.231 This section lists cluster traps in alphabetical order.^ Trap name Meaning Error class sniWpChange The SNMP agent has informational ClusterActiveAgain established the connection with the cluster service. sniWpChange The SNMP agent has lost the critical ClusterNoLonger connection with the cluster...
  • Page 99 Trap overview Trap name Meaning Error class sniWpChange A network was deleted from critical NetworkDeleted the cluster. sniWpChange The settings for a network major NetworkProperty have been changed. sniWpChange A network has changed its major NetworkState status. sniWpChange A new node was added to the informational NodeAdded cluster.
  • Page 100 Trap overview Trap name Meaning Error class sniWpChange The cluster API has returned critical Unknown a note type that does not have an associated trap definition. Table 21: Cluster traps ServerView Event Manager...

  • Page 101: Dpt Traps (Dptscsi.mib)

    Trap overview 5.3.5 DPT traps (dptscsi.mib) MIB-OID: 1.3.6.1.4.1.1597 This section lists DPT traps in alphabetical order. Trap name Meaning Error class dptArrayCfgChangeTrap Configuration of a RAID informational array changed due to one of the following events: – creating a new array –...
  • Page 102 Trap overview Trap name Meaning Error class dptDevStatus Status of the SCSI device informational ChangedTrap changed. dptHbaCorrected The HBA encountered an informational HardRAMErrorTrap ECC RAM error and corrected it. dptScsiHbaBadMemoryAddre ss contains the RAM address. dptHbaSoftRAM The HBA encountered an informational ErrorTrap ECC RAM error, but the...

  • Page 103: Duplexdatamanager Traps (Ddm.mib)

    Trap overview 5.3.6 DuplexDataManager traps (Ddm.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists DuplexDataManager traps in alphabetical order. Trap name Meaning Error class FscDdmNewConfig 1400 After the driver has created informational a new DuplexWrite group or has added a new disk to an existing DuplexWrite group as requested by the user.
  • Page 104 Trap overview Trap name Meaning Error class FscDdmReservationConf 1407 A reservation conflict has major lict been detected. From now on an entire DuplexWrite group is no longer available. This leads to an error if a conflict of operation (not initialization) occurs in the group.
  • Page 105 Trap overview Trap name Meaning Error class FscDdmNameChanged 1414 After the driver has informational changed the name of a DuplexWrite group. FscDdmPathFailed 1415 After the driver has critical detected an error on one path of a MultiPath group. FscDdmRetry 1416 After the driver has major detected an error on one path of a MultiPath group...
  • Page 106 Trap overview Trap name Meaning Error class FscDdmDdmCluster 1424 After the informational DuplexDataManager service has detected a cluster configuration change. Table 23: DDM-Traps ServerView Event Manager...

  • Page 107: Duplexwrite Traps (Dw.mib)

    Trap overview 5.3.7 DuplexWrite traps (DW.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists DuplexWrite traps in alphabetical order. Trap name Meaning Error class sieDWActiveLunChan 1310 A user has changed the informational read path for a DuplexWrite group to a certain disk. sieDWConfig 1308 The driver has reread the informational...
  • Page 108 Trap overview Trap name Meaning Error class sieDWPieceFailed 1311 The driver has detected an critical error on one of the disks of a DuplexWrite group. sieDWPieceRecovere 1305 A DuplexWrite group was informational successfully recovered. Both elements of the DuplexWrite group have the status ONLINE.

  • Page 109: Hard Disk (S.m.a.r.t.) Traps (Hd.mib)

    Trap overview 5.3.8 Hard disk (S.M.A.R.T.) traps (Hd.mib) This section lists hard disk traps in alphabetical order. MIB-OID: 1.3.6.1.4.1.231.2.10.2 Trap name Meaning Error class sniSMARTFailure S.M.A.R.T. is warning that a critical Predicted hard disk may fail. sniSMARTMonitoring The S.M.A.R.T. configuration informational Disabled has been changed.

  • Page 110: Generic Traps

    Trap overview 5.3.9 Generic traps This section lists generic traps in alphabetical order. Trap name Meaning Error class coldStart An agent was restarted. minor MIB view objects may have changed. egpNeighborLoss An EGP neighbor of the major managed node changed from the UP to the DOWN state.

  • Page 111: Multipath Traps (Mp.mib)

    Trap overview 5.3.10 MultiPath traps (mp.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists MultiPath traps in alphabetical order. Trap name Meaning Error class sieMP 1202 The user has enabled or informational ActivePortChanged disabled a path of a MultiPath group. sieMPAutoRecovered 1205 A path of a MultiPath group, informational which was in error status, is accessible again due to...

  • Page 112: Mylex Traps (Mylex.mib)

    Trap overview 5.3.11 Mylex traps (Mylex.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists Mylex traps in alphabetical order. Trap name Meaning Error class mylexAdapterDied 221 Connection to a disk array critical controller interrupted. mylexAutoRebuild 200 Automatic rebuild of a unit critical Started has been started.
  • Page 113 Trap overview Trap name Meaning Error class mylexLogicalDriveOffline 214 Logical drive is offline. critical mylexLogicalDriveOnline 216 Logical drive is online. critical mylexManualRebuild 201 Manual rebuild started. informational Started mylexManualRebuild 223 Manual rebuild started. informational Started2 After the rebuild has finished successfully, mylexRebuildDone2 will be sent.
  • Page 114 Trap overview Trap name Meaning Error class mylexPhysicalDevice 255 Prefailure alert from major Prefailure physical device. mylexPhysicalDevice 258 Physical device has been major Removed removed. mylexPhysicalDevice 252 A normal (soft) error has minor SoftError occurred in physical device. mylexPhysicalDevice 256 Physical device is minor Unconfigured unconfigured.
  • Page 115 Trap overview Trap name Meaning Error class mylexRebuildNew 206 Rebuild finished; new major DeviceFailed device failed. mylexRebuildNewDevice 227 Rebuild of system drive; major Failed2 new device has failed. mylexRebuildStatus 204 Rebuild status. informational mylexSMART 271 S.M.A.R.T. configuration informational ConfigurationChanged has been changed. mylexSMART 270 Sent if a failure (S.M.A.R.T.) critical...

  • Page 116: Pci Hotplug Traps (Pcihotplug.mib)

    Trap overview 5.3.12 PCI HotPlug traps (pcihotplug.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists PCI HotPlug traps in alphabetical order. Trap name Meaning Error class sieDeviceHotPlug 1022 A SCSI device was added. informational TrapHotAdd sieDeviceHotPlug 1020 A SCSI device was informational TrapHotRemoval removed.

  • Page 117: 5.3.13 Primepower Traps

    Trap overview 5.3.13 PRIMEPOWER traps This section describes the traps supplied with PRIMEPOWER. ADICLIBMIB-V2 traps (ADICLIBMIB-v2.mib) MIB-OID: 1.3.6.1.4.1.3764.3 Trap name Meaning Error class doorStateChange The door state has changed. informational error The device has an error. Error informational code and error data is displayed.
  • Page 118 Trap overview Trap name Meaning Error class domNoManagementS An agent was stopped. informational erver domStartTrap An agent was started. informational Table 31: DOMAIN-MIB traps FSC-LOG3-MIB traps (log3v1.mib) MIB-OID: 1.3.6.1.4.1.231.2.46.2 Trap name Meaning Error class log3AlertNotice A log3Event has occurred. critical System, module, error and text is displayed.
  • Page 119 Trap overview Trap name Meaning Error class log3WarningNotice A log3Event has occurred. minor System, module, error and text is displayed. Table 32: FSC-LOG3-MIB traps UNISERV-MIB traps (uniserv.mib) MIB-OID: 1.3.6.1.4.1.231.2.41 Trap name Meaning Error class kaiPartitionOffline A partition was powered off. minor kaiPartitionOnline A partition was powered on.
  • Page 120 Trap overview FSC-HACL-MIB traps (v1_fscHaCl.mib) MIB-OID: 1.3.6.1.4.1.231.2.42.2.0 Trap name Meaning Error class fscHaClApplicationSt Application state has major ateChanged changed. fscHaClClusterInfAvai Cluster information is informational lable available. InfoOperScope is displayed. fscHaClClusterInfNot Cluster information is no major Available longer available. InfoOperScope is displayed. fscHaClMonitorState Cluster monitoring state has major...
  • Page 121 Trap overview Trap name Meaning Error class wsaDROperationFinishe 313 DR operation was informational terminated. wsaEnvironmentHardwar 301 Defect on environment critical eDefectSet hardware has occurred. wsaEnvironmentHardwar 302 Error on environment critical eErrorSet hardware has occurred. wsaEnvironmentRepair 303 Environment component minor was repaired. wsaErrorRepair An error was repaired.
  • Page 122 Trap overview Trap name Meaning Error class wsaLarHardwareErrorUn A hardware error was informational repaired. wsaLUNStateChanged 101 State of LUN has changed. critical wsaMonitoringRuleInitiali 311 EEM rule was initialized. minor wsaMonitoringRuleMatch 310 EEM rule was matched. informational wsaNodeStatusIntegrate A node was integrated. informational wsaNodeStatusNotavail A node is not available.

  • Page 123: Pxre Traps (Dec.mib)

    Trap overview 5.3.14 PXRE traps (dec.mib) MIB-OID: 1.3.6.1.4.1.36.2.15.21 This section lists PXRE traps in alphabetical order. Trap name Meaning Error class cacheBatteryFailureTrap A controller cache battery major has failed. Replace cache battery or replenish charge. cacheBattery A controller cache battery informational InformationTrap has GOOD state.
  • Page 124 Trap overview Trap name Meaning Error class diskFailureTrap A disk drive has failed. The major location of the disk is indicated by the disk name. Replace the disk device. The numbers in the name indicate Port, Target, Lun behind the controller pair. Examples: –...
  • Page 125 Trap overview Trap name Meaning Error class fanFailureTrap The fan in the specified major location has failed. Replace fan. fanInformationTrap The fan in the specified informational location was recovered. lunFailureTrap The LUN has failed and is critical off-line. Possible cause is too many failed disk drives that make up the LUN, the OS can no longer...
  • Page 126 Trap overview Trap name Meaning Error class powerSupplyFailureTrap The power supply in the major specified location has failed. Replace power supply. powerSupply Power supply was informational InformationTrap recovered. temperature A temperature sensor informational InformationTrap indicates temperature below WARNING threshold limit. temperatureOver A temperature sensor has major...

  • Page 127: Raid Adapter Traps (Megaraid.mib)

    Trap overview 5.3.15 RAID Adapter traps (Megaraid.mib) MIB-OID: 1.3.6.1.4.1.16.1.1.200 This section lists RAID Adapter traps in alphabetical order. Trap name Meaning Error class rtBatteryMissing 9020 Adapter-%d: Battery informational Module is missing. rtBattery 9022 Adapter-%d: Battery informational TemperatureHigh Module temperature exceeded Danger Threshold.
  • Page 128 Trap overview Trap name Meaning Error class rtConsistency 9011 Adapter-%d, Logical Drive- informational Corrected %d: Check consistency operation completed. Inconsistencies have been cured. rtInitializeAborted 9006 Adapter-%d, Logical Drive- informational %d: Initialization aborted by user. rtInitializeCompleted 9005 Adapter-%d, Logical Drive- informational %d: Initialization completed successfully.
  • Page 129 Trap overview Trap name Meaning Error class rtPredictiveFailures 9017 Adapter-%d, Channel-%d, informational False Target-%d: Reported failure prediction threshold exceeded [FALSE]. Drive identification string = %s Sense Key = 0x%x, ASC = 0x%x, ASCQ = 0x%x. rtReconstruction 9014 Adapter-%d, Logical Drive- informational Completed %d: Reconstruction...

  • Page 130: Rompilot Traps (Rompilot.mib)

    Trap overview 5.3.16 RomPilot traps (Rompilot.mib) MIB-OID: 1.3.6.1.4.1.2487 This section lists RomPilot traps in alphabetical order. Trap name Meaning Error class RomPilotColdReset Phoenix RomPilot was informational loaded after a cold system reset. RomPilot Phoenix RomPilot was informational DiagnosticReset loaded after a diagnostic system reset.

  • Page 131: Servercontrol Traps (Sc.mib)

    Trap overview 5.3.17 ServerControl traps (SC.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists ServerControl traps in alphabetical order. Trap name Meaning Error class cabinetNotConfigured 623 Cabinet is not configured. informational cabinetSwitchedOff 617 Cabinet was switched off. informational cabinetSwitchedOn 618 Cabinet was switched on. informational correctableMemError 643 Correctable memory error.
  • Page 132 Trap overview Trap name Meaning Error class notEnoughCabinets 615 The actual number of major storage extensions is lower than number stored in the configuration. powerOffTimeReached 645 Power off time has been informational reached. powerSupplyAdded 625 A power supply was added. informational powerSupplyFailed 626 A power supply has failed.
  • Page 133 Trap overview Trap name Meaning Error class sieScBootError 661 No bootable operating informational system can be found. sieScBootWatchdogExpir 662 Boot watchdog expires. informational sieScCpuPrefailure 673 A CPU is predicted to fail major (prefailure). sieScDiagnosticBoot 665 Server is reset and informational diagnostic boot is enabled.
  • Page 134 Trap overview Trap name Meaning Error class sieScUserAuthentication 664 User authentication failure major Failure is detected via PPP, FTP, HTTP or telnet. sniScCpuSpeedChanged 656 CPU speed has changed informational because of temperature problems. sniScFanAdded 653 The indicated hot-plug fan informational was inserted.
  • Page 135 Trap overview Trap name Meaning Error class tempSensorBroken 630 The temperature sensor is major defective or not connected. tempSensorOk 635 The temperature sensor is informational working again. tempWarn 603 The temperature has major reached the warning level. testTrap 600 Test trap sent to verify trap informational connection.
  • Page 136 Trap overview Trap name Meaning Error class trapOnBattery 606 AC power failure. Cabinet is critical running on battery power. The UPS is operating on battery power or the power supply is drawing current from the backup battery unit (BBU). This trap is persistent and is resent at one minute intervals until the mains returns or the...

  • Page 137: Servercontrol Traps (Sc2.Mib)

    Trap overview 5.3.18 ServerControl traps (SC2.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2.2.10.20 This section lists ServerControl traps in alphabetical order. Trap name Meaning Error class sc2TrapAcFail 2040 Mains failed in the specified critical cabinet. This trap occurs only in storage extension cabinets without UPS or BBU.
  • Page 138 Trap overview Trap name Meaning Error class sc2TrapCabinetSwitche 2090 This trap will be sent when a informational dOff cabinet is switched off. For obvious reasons it cannot be sent when the main cabinet is switched off. sc2TrapCabinetSwitche 2091 This trap will be sent when a informational cabinet is switched on.
  • Page 139 Trap overview Trap name Meaning Error class sc2TrapDcFail 2041 DC power failed in the critical specified cabinet. This is the result of the systems power-good sensor monitoring. The system stops if this error occurs. sc2TrapFanAdded 2010 The indicated hot-plug fan informational was inserted.
  • Page 140 Trap overview Trap name Meaning Error class sc2TrapMessageLogFul 2100 The System Event Log minor (message log) is full. No more messages can be logged. This trap will not occur on wrap-around log types. sc2TrapMessageLogWa 2101 The warning threshold for minor rning the number of System Event Log entries has been...
  • Page 141 Trap overview Trap name Meaning Error class sc2TrapRedundantFanF 2015 The indicated redundant major ailed fan failed. sc2TrapRedundantPow 2035 One redundant hot-replace major erSupplyFailed power supply failed. sc2TrapServerShutdow 2093 This trap will be sent before informational a server will switch off. sc2TrapSevereSystemE 2006 The system was restarted critical...
  • Page 142 Trap overview Trap name Meaning Error class sc2TrapUncorrectableM 2067 A uncorrectable memory critical emError error at unknown location was detected. sc2TrapUncorrectableM 2061 An uncorrectable memory critical emErrorAddr error at specified address was detected. sc2TrapUncorrectableM 2063 An uncorrectable memory critical emErrorBank error at specified bank was detected.

  • Page 143: Serverview Traps (Serverview.mib)

    Trap overview 5.3.19 ServerView traps (ServerView.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists ServerView traps in alphabetical order. Trap name Meaning Error class sniSvGenericTrap 700 A ServerView alarm signal informational Forward has been received. sniSvPagerOff 701 The pager should be informational switched off. sniSvPassThrough 703 Forwarded if the Event informational...

  • Page 144: Serverview Status Traps (Status.mib)

    Trap overview 5.3.20 ServerView status traps (Status.mib) MIB-OID: 1.3.6.1.4.1.231.2.10.2 This section lists ServerView status traps in alphabetical order. Trap name Meaning Error class sieStTrapStatusChanged 1100 System status has changed informational at server. Table 43: ServerView status trap ServerView Event Manager...

  • Page 145: Tape Drive Traps (Tapealrt.mib)

    Trap overview 5.3.21 Tape drive traps (tapealrt.mib) MIB-OID: 1.3.6.1.4.1.11.2.3.9.7.1 This section lists tape drive traps in alphabetical order. Trap name Meaning Error class tapeAlertTrap1 The tape drive is having minor problems reading data. No data has been lost, but there has been a reduction in the performance of the tape.
  • Page 146 Trap overview Trap name Meaning Error class tapeAlertTrap6 The tape is from a faulty critical batch or the tape drive is faulty: 1. Use a good tape to test the drive. 2. If the problem persists, call the tape drive supplier helpline.
  • Page 147 Trap overview Trap name Meaning Error class tapeAlertTrap12 You have tried to load a informational cartridge of a type which is not supported by this drive. tapeAlertTrap13 The operation has failed critical because the tape in the drive has snapped: 1.
  • Page 148 Trap overview Trap name Meaning Error class tapeAlertTrap19 The tape cartridge is informational nearing the end of its useful life. It is recommended that you: 1. Use another tape cartridge for your next backup. 2. Store this tape cartridge in a safe place in case you need to restore data from it.
  • Page 149 Trap overview Trap name Meaning Error class tapeAlertTrap23 The last cleaning cartridge critical used in the tape drive was an invalid type: 1. Do not use this cleaning cartridge in this drive. 2. Wait for the current operation to finish. 3.
  • Page 150 Trap overview Trap name Meaning Error class tapeAlertTrap32 The tape drive has a minor problem with the host interface: 1. Check the cables and cable connections. 2. Restart the operation. tapeAlertTrap33 The operation has failed: critical 1. Eject the tape or magazine.
  • Page 151 Trap overview Trap name Meaning Error class tapeAlertTrap39 The tape drive may have a minor hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the tape drive users manual for device specific instructions on running extended diagnostic tests. tapeAlertTrap40 The changer mechanism is critical...
  • Page 152 Trap overview Trap name Meaning Error class tapeAlertTrap43 The operation has failed critical because the autoloader door is open: 1. Clear any obstructions from the autoloader door. 2. Eject the magazine and then insert it again. 3. If the fault does not clear, turn the autoloader off and then on again.
  • Page 153 Trap overview Trap name Meaning Error class tapeAlertTrap256 256 The library mechanism is critical having difficulty communicating with the drive: 1. Turn the library off then 2. Restart the operation. 3. If problem persists, call the library supplier helpline. tapeAlertTrap257 257 There is a problem with the minor library mechanism.
  • Page 154 Trap overview Trap name Meaning Error class tapeAlertTrap260 260 The library mechanism may minor have a hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the library users manual for device specific instructions on running extended diagnostic tests. tapeAlertTrap261 261 The library has a problem critical...
  • Page 155 Trap overview Trap name Meaning Error class tapeAlertTrap266 266 The voltage supply to the critical library exceeds specifications. There is a potential problem with the power supply or failure of a redundant power supply. tapeAlertTrap267 267 A cartridge has been left in critical a drive inside the library by a previous hardware fault:...
  • Page 156 Trap overview Trap name Meaning Error class tapeAlertTrap271 271 The operation has failed critical because the library door is open: 1. Clear any obstructions from the library door. 2. Close the library door. 3. If the problem persists, call the library supplier helpline.
  • Page 157 Trap overview Trap name Meaning Error class tapeAlertTrap278 278 There is a potential problem minor with the barcode label or the scanner hardware in the library mechanism. If the problem persists, call the library supplier helpline. tapeAlertTrap279 279 The library has detected a critical inconsistency in its inventory.

  • Page 158: Team Server Traps (Fujitsu)

    Trap overview 5.3.22 Team Server traps (Fujitsu) This section describes the traps supplied with the Fujitsu Team Server. ASM PRIVATE COMMIB traps (Asmpro.mib) MIB-OID: 1.3.6.1.4.1.3764.3 Trap name Meaning Error class trapACFail AC Power failed. major trapAssetChange Asset is changed. major trapBatteryFail UPS battery fails.
  • Page 159 Trap overview Trap name Meaning Error class trapPowerFanFail Any power subsystem fan major fails. trapPSFail Any power supply fails. major trapRPSFail Redundant power supply is major failed. trapRPSFanFail Redundant power supply major fan is failed. trapTemperatureCritical Temperatures exceed the critical second level threshold value.
  • Page 160 Trap overview LDCM MIB traps (Ldcm.mib) MIB-OID: 1.3.6.1.4.1.343.2.5.1.2 Trap name Meaning Error class ldcmCriticalTrap Manager has reported a critical severity Critical event. ldcmFatalTrap Manager has reported a critical severity Fatal event. ldcmInfoTrap Manager has reported an informational Informational event. ldcmOkTrap Manager has reported a informational severity OK event.

  • Page 161: Threshold Traps (Trap.mib)

    Trap overview 5.3.23 Threshold traps (Trap.mib) MIB-OID: 1.3.6.1.4.1.231 This section lists threshold traps in alphabetical order. Trap name Meaning Error class sniInvDeltaTrap 131 DELTA threshold underflow. informational Underflow This trap indicates, that one of the polled variables has left the interval specified by the user.
  • Page 162 Trap overview Trap name Meaning Error class sniInvTrapValid 133 Threshold has become informational valid. sniNTAlert 304 NT alert message was informational written to the event log. sniNTChangeSecurity 302 Security change has informational occurred. sniNTChangeTime 305 Time has changed or a informational nonuniform time adjustment has occurred.
  • Page 163 Trap overview Trap name Meaning Error class sniNTLoginUser 301 User logged into server. informational sniNTRegChangeAttr 311 Attributes for a key or its informational subtree in registry has been changed. sniNTRegChangeLast 312 Last write time for a key or informational Write its subtree in registry has been changed.
  • Page 164 Trap overview Trap name Meaning Error class sniNWDataMigration 041 A files data has been informational migrated. sniNWDataDeMigration 042 Migration of file has been informational withdrawn. sniNWDeactivateScreen 018 Screen is deactivated on informational server. sniNWDeleteBinderyObj 012 Bindery object was deleted informational (NetWare).
  • Page 165 Trap overview Trap name Meaning Error class sniNWNoRelinquish 023 NLM-Module has not critical Control relinquished control. sniNWOpenScreen 020 Screen was opened on informational server. sniNWProtocolBind 033 A Protocol is bound to a informational MLID. sniNWProtocolUnbind 034 A Protocol is unbound from warning a MLID.

  • Page 166: Ups Traps (Upsman.mib)

    Trap overview 5.3.24 UPS traps (Upsman.mib) MIB-OID: 1.3.6.1.4.1.1356 This section lists UPS traps in alphabetical order. UPS traps 1 Trap name Meaning Error class communication The connection with the informational Established UPS was established. communicationLost The connection with the critical UPS was lost.
  • Page 167 Trap overview UPS traps 2 Trap name Meaning Error class boostOn The UPS has turned on the major booster. communication The connection with the informational Established UPS was established. communicationLost The connection with the critical UPS was lost. lowBattery The batteries are low and critical will soon be empty.
  • Page 168 Trap overview ServerView Event Manager...

  • Page 169: Mib Integration

    MIB integration The Web-based MIB Manager tool is installed automatically when you install the Event Manager under Windows and Linux. This tool is used to integrate private MIBs into the Event Manager, so that ServerView can detect the traps for this type of MIB. Then if an event occurs, ServerView can take the necessary action.
  • Page 170 MIB integration The tool starts up and the following window is displayed: Figure 15: “MIB Manager” tool To integrate private MIBs, proceed as follows: Ê Select the relevant directory using the Browse... button. Ê Select the MIB and then click the Upload button. The tool then checks the MIB for correct syntax.
  • Page 171 MIB integration Updating integrated MIB files You can update integrated MIB files. The name of the updated integrated MIB file must be the same as that of the integrated MIB file. Please note that the MIB Integrator distinguishes between upper and lower case.
  • Page 172 MIB integration ServerView Event Manager...

This manual is also suitable for:

Serverview operations manager v6.12

Table of Contents