User Guide - English Fujitsu Software ServerView Suite ServerView Event Manager ServerView Operations Manager V6.
Comments… Suggestions… Corrections… The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by e-mail to manuals@ts.fujitsu.com.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1 Changes from the previous version . . . . . . . . . . . . . . . 8 1.2 ServerView Suite link collection . . . . . . . . . . . . . . . . . 9 1.3 Documentation for ServerView Suite . . . . . . . . . . . . . 10 1.4 Notational conventions 2 Event Manager . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 First-time startup . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2 Starting the Event Manager . .
Contents 4 Alarm configuration . . . . . . . . . . . . . . . . . . . . . . . 37 4.1 4.1.1 4.1.2 4.1.2.1 4.1.3 4.1.4 Alarm rules . . . . . . . . . . . Managing alarm rules . . . . . . Assigning servers . . . . . . . . Displaying server information Assigning alarms . . . . . . . . Forwarding alarms . . . . . . . 4.2 4.2.1 4.2.2 Filter rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Server filters . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Filtering alarms . . . . . . . . .
Contents 5.3.7 5.3.8 5.3.9 5.3.10 5.3.11 5.3.12 5.3.13 5.3.14 5.3.15 5.3.16 5.3.17 5.3.18 5.3.19 5.3.20 5.3.21 5.3.22 5.3.23 5.3.24 DuplexWrite traps (DW.mib) . . . . . Hard disk (S.M.A.R.T.) traps (Hd.mib) Generic traps . . . . . . . . . . . . MultiPath traps (mp.mib) . . . . . . . Mylex traps (Mylex.mib) . . . . . . . PCI HotPlug traps (pcihotplug.mib) . PRIMEPOWER traps . . . . . . . . PXRE traps (dec.mib) . . . . . . . . RAID Adapter traps (Megaraid.mib) . RomPilot traps (Rompilot.mib) . . . .
Contents ServerView Event Manager
1 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.
Changes from the previous version 1.1 Changes from the previous version This edition is valid for the Event Manager of ServerView V6.20 and replaces the online manual: “Event Manager“ as of ServerView V6.12 Edition February 2013. The manual has been updated to reflect the latest software status and includes the following additions:. – The Edit Automatic Service Mail Configuration window now also includes the Exec Settings tab. – The MAPI is no longer supported.
ServerView Suite link collection 1.2 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.
Documentation for ServerView Suite Access to the link collection You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager. Ê Select Help – Links on the start page or on the menu bar. This opens the start page of the ServerView link collection. 2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server.
Notational conventions 1.4 Notational conventions The following notational conventions are used in this manual: V Caution I 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 order to continue with the procedure.
Notational conventions 12 ServerView Event Manager
2 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. If an unusual operating status occurs, the ServerView agents automatically send an alarm (trap) to a management station.
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“ manual).
Starting the Event Manager 2.2 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. 2. Click the menu item Event Manager either in the ServerView Operations Manager start screen or in the ServerList main window. 3.
Icons 2.3 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. Some other executable program was triggered by this alarm. A broadcast message was sent for this alarm. A mail was sent for this alarm. This alarm triggered a pager call.
Icons Yellow: Forwarding completed Red: Forwarding present (still active) Table columns can be filtered according to different criteria.
Icons 18 ServerView Event Manager
3 Alarm Monitor The Alarm Monitor component displays all received alarms relating to the selected servers and server groups in the Operations Manager main window. 3.1 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" on page 15). How to start Operations Manager is described in the ServerView Operations Manager documentation.
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 Security (only if OpenDS is used as directory service) In the line below the menu bar, the individual menu items are listed, depending on which menu is selected.
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. If you click the server name, the ServerView [servername] window opens, in which you can request detailed information about the selected server. For more information see the ServerView Operations Manager manual.
Viewing alarms The icons have the following meanings: Indicates the alarm level. The alarm was written to the local event log. This alarm triggered a pager call. A mail was sent for this alarm. A broadcast message was sent for this alarm. An executable program was triggered by this alarm. This alarm was forwarded to the management station.
Viewing alarms If the server is in the server list, you can use the Edit Server Settings link to open the Server Properties window for this server, via which you can change the configured values for the server. If the server is not in the ServerView server list, you can use the Add Server link to start the Server Browser and add the server to the list. For more information on the Server Properties and the Server Browser, see the ServerView Operations Manager User Guide.
Viewing alarms for a server 3.2 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. To get an overview of all alarm messages for this server, you can switch to the Alarm Monitor function for this server only.
Processing alarm entries 3.4 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: Ê Select the alarm entries in the list. Ê Select Ack Alarm from the context menu. The acknowledgment is indicated in the Ack column with the following icon: 3.4.
Processing alarm entries I 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. 3.4.3 Resetting alarm suppression You can reset an alarm suppression that has already been set.
Testing the connection 3.5 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, or Ê Enter the IP address of the server. If you wish you can specify the server name. Ê Either accept the default values for Community and Timeout or enter the relevant values in these fields.
Other settings 3.6 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. Ê Confirm your input with OK.
iRMC S2/S3 SEL Entries and SC2 MIB Traps 3.7 iRMC S2/S3 SEL entries relayed as SC2 MIB traps I 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. The following table shows the correlation between the iRMC S2/S3 entries in the SEL and the traps they trigger. I Not all iRMC S2/S3 entries made in the SEL trigger an SNMP trap. Some trigger the same trap.
iRMC S2/S3 SEL Entries and SC2 MIB Traps Error code iRMC S2/S3 SEL entry Trap text Trap no. Trap name 040003 ’FAN XY’: Redundant The redundant fan 2015 sc2Trap RedundantFan fan failed ’FAN XY’ failed in cabinet XY of server Failed XY. System can become critical if another fan in this group fails. 040004 ’FAN XY’: Fan removed Fan ’FAN XY’ was 2011 sc2TrapFan removed from Removed cabinet XY of server XY.
iRMC S2/S3 SEL Entries and SC2 MIB Traps Error code iRMC S2/S3 SEL entry 070001 ’PSU XY’: Power supply OK Trap text Trap no. Trap name Power supply ’PSU 2030 sc2TrapPower XY’ in cabinet XY at SupplyAdded server XY was added. Power supply ’PSU 2032 sc2TrapPower XY’ in cabinet XY at SupplyOk server XY is working again. 070002 ’PSU XY’: Power supply failed Power supply ’PSU 2034 sc2TrapPower XY’ in cabinet XY at SupplyFailed server failed.
iRMC S2/S3 SEL Entries and SC2 MIB Traps Error code iRMC S2/S3 SEL entry Trap text Trap no. Trap name 07000A ’PSU XY’: Power supply critical temperature Temperature at 2037 sc2TrapPower SupplyCritical power supply ’PSU XY’ in cabinet XY of Temperature server XY has reached the critical level. 07000F ’PSU XY’: Power supply fan prefailure Fan failure is 2038 sc2TrapPower predicted at power SupplyFan supply ’PSU XY’ in Failure cabinet XY of server Prediction XY.
iRMC S2/S3 SEL Entries and SC2 MIB Traps Error code iRMC S2/S3 SEL entry Trap text Trap no. Trap name 2006 sc2TrapSevere The system wa restarted after a SystemError severe problem at 120031 PCI parity error cabinet XY of server (PERR): Slot 0%1 XY. See server 120034 PCI bus parity error management indicated by onboard message log device (PERR): Bus: (recovery log) for %1 Device: 0x%2 detailed information.
iRMC S2/S3 SEL Entries and SC2 MIB Traps Error code iRMC S2/S3 SEL entry Trap text Trap no. Trap name 150031 Battery voltage ’BATT Battery voltage 2054 sc2TrapBattery VoltagePrefail XY’ low warning: % ’BATT XY’ in cabinet Volt XY at server XY: Battery is predicted to fail in near future. 190003 ’DIMM XY’ Memory: Uncorrectable error (ECC) 190040 ’DIMM XY’: Uncorrectable Parity memory error Uncorrectable memory error at module ’DIMM XY’ in cabinet XY of server XY.
iRMC S2/S3 SEL Entries and SC2 MIB Traps Error code iRMC S2/S3 SEL entry Trap text Trap no. Trap name 190017 ’DIMM XY’: Memory replaced by spare memory Memory module 2070 sc2TrapMem ’DIMM XY’ in cabinet ErrorModule XY of server XY had Replaced failed and was replaced by a hotspare module. 19001A ’DIMM XY’: Memory module failed predicted Memory module 2068 sc2TrapMem failure is predicted ErrorModule for module ’DIMM Prefail XY’ in cabinet XY of server XY.
iRMC S2/S3 SEL Entries and SC2 MIB Traps 36 ServerView Event Manager
4 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" on page 39). The filter rules define which types of alarm are filtered out (see section "Filter rules" on page 55).
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. Buttons The various screens contain the following buttons: Add Define a new setting. Edit Edit an existing setting. Delete Delete an existing setting.
Alarm rules 4.1 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" on page 40). – Assigning one or more servers to the alarm rule (see section "Assigning servers" on page 43). The alarm rule then only applies to alarms from these servers.
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. It opens a window in which you can enter the name of the new alarm rule. You can also copy settings of an existing alarm rule over to the new one.
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. You save the new setting by clicking the Apply button. The second column lists the alarms that are assigned to the selected alarm rule.
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" on page 55). You can find out more about a particular server by clicking its entry in the list. The second column lists all the alarm rules to which the selected server is assigned.
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. The Assigned Servers window shows the list of servers and server groups which are assigned to the alarm rule.
Alarm rules I 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: > Adds the selected servers to the alarm rule. < Removes the selected servers from the alarm rule. >> Adds all known servers to the alarm rule. << Removes all servers from the alarm rule.
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. Underneath the status icon there is another icon which indicates whether or not the server is entered in the server list: The server is known, i.e.
Alarm rules I 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. To close the Server information window, click the Close button.
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. Figure 7: Alarm Rules - Assign Alarms - Individual Alarms The Individual Alarms dialog box contains in the top drop-down list the names of all known alarm rules.
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). Alarms which are assigned to the selected alarm rule are indicated by selected checkboxes. You can select or deselect a checkbox by clicking it. Clicking the Apply button saves the changed settings for the alarm rule.
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 To remove all currently known alarms from the alarm rule Uncheck selected alarm(s) To remove the selected alarms from the alarm rule Clicking the Apply button saves the n
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. All alarms of severity major All alarms of severity major are handled according to the alarm rule. All alarms of severity minor All alarms of severity minor are handled according to the alarm rule.
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. Figure 9: Alarm Rules - Assign Destinations 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.
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.
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. A detailed description of the various windows is available via the respective Help buttons.
Alarm rules I ● 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. If User and Password are left blank, mails will be sent by SMTP without authentication.
Filter rules 4.2 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 55) and/or which alarms are to be filtered out (see section "Filtering alarms" on page 56). I Filter rules take priority over alarm rules. If a alarm is ignored because of the filter rules, the alarm rule assigned to the alarm is not activated. 4.2.
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. These are alarms which are not defined in any of the integrated MIBs. Alarms from unknown server Filter out alarms from unknown servers.
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.
Making settings 4.3 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: – Alarms relating to failed authentication are suppressed. – Alarms from server blades are issued with the relevant name of the blade server. For different error severities you can specify the following actions.
Mail forwarding in general 4.4 Mail forwarding in general Making mail settings If you have selected Mail for the forwarding, the following New Mail Configuration window opens. 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.
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 alarms" on page 51), this field contains the already assigned name and is disabled.
Mail forwarding in general Mail Properties tab The Mail Properties tab provides fields for the mail server. The mail server is an SMTP server. I With alarm forwarding in ServerView V6.20 or later, MAPI is no longer supported. Only SMTP servers are still used. If during an upgrade the mail service is addressed via MAPI, a warning is issued. During the setup, all MAPI destinations are changed to SMTP. The settings for the SMTP server must then be configured in the Alarm Configuration component.
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. If you click OK, your settings will be saved and you will be returned to the previous window. Further buttons are offered depending on the type of forwarding and the selected tab (see "Buttons" on page 38).
Mail and Execute forwarding to the service provider 4.5 Mail and Execute 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. The group of traps that trigger a mail is defined by the service provider and can only be changed by them.
Mail and Execute forwarding to the service provider You can enable or disable this configuration with the Enabled option. The Mail Properties tab provides fields for the mail server. The mail server is an SMTP server. I With alarm forwarding in ServerView V6.20 or later, MAPI is no longer supported. Only SMTP servers are still used. If during an upgrade the mail service is addressed via MAPI, a warning is issued. During the setup, all MAPI destinations are changed to SMTP.
Mail and Execute forwarding to the service provider The Exec Settings tab offers fields for execute settings, some of which already contain predefined settings. The input fields in the Exec Settings window have the following meanings: Name Meaning Description (optional) Name of the execute settings Command Name of the command to be executed.
Mail and Execute forwarding to the service provider If you click the Test Address button in the Service Mail Settings window, a test mail is sent to the service provider. The Service Center sends an automatic e-mail response to all test mails it receives. In doing so it uses the address specified in the E-mail input field. A minimum period of 600 seconds has been specified for the sending of identical mails. This ensures that redundant messages are not sent.
Making pop-up settings 4.6 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. I Pop-up notifications are only displayed on the local host. They cannot be displayed on any other host. Popup Settings tab The Popup Settings tab offers fields for the pop-up settings, some of which already contain predefined settings.
Making pop-up settings I 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. 2. Because with Linux systems the user is logged onto a virtual system console, they can either use graphical interfaces (GUI session, e.g. Gnome or KDE) or the command line interface (CLI session).
Making pager settings (COM port and modem) 4.7 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). You can define the following values: – – – – The name of the available interfaces (e.g.
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. Do not select too short a time, as calls to a pager can be delayed by a few minutes by the service provider. Also bear in mind the time required to reach the server management station.
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. For each service number, you make settings for data bits, parity and stop bits and you define the prompt used by the pager service for messages.
Making execute settings 4.8 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.
Making execute 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. I For Windows Server 2008, the CUI command is the only command that can be used for the program execution.
4.9 Making broadcast settings Broadcast is a type of transmission whereby a pop-up window or a message is displayed on multiple servers or server groups simultaneously. If you have selected for the forwarding, the New Broadcast Configuration window opens. In this window you can use the Broadcast Settings and Time Model Settings tabs to make all necessary settings for broadcast forwarding.
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 domain All users belonging to the same domain for the forwarding are notified. (Valid only with Windows, default.) As of Windows Server 2008, domain is no longer supported. All users with session All users who are associated with the forwarding through any session are notified (default with Linux).
Making broadcast settings I 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. With SuSE Linux and RedHat Linux, the KDE session does not make any utmp entries via the console or the emulation that is started with it. Forwarded alarm messages are therefore not output in these windows.
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.
Making trap settings Name Meaning Forwarding Mode The mode for the forwarding. Normal This mode evaluates the alarm and forwards it to the management station. Pass Through This mode is available in an original variant and in the variant Transparent. The original variant passes the alarm directly through to the management station. The alarm appears there as if it is coming directly from the server. In this mode the trap is only forwarded once.
Macros 4.11 Macros Below is a list of macros that can be used for the forwarding of alarms (e.g. Mail, Pager). These macros are replaced by the corresponding information about the servers which are reporting the alarm. Name Meaning $_SRV Name of the server $_TRP Text of the alarm message $_TYP Brief description of the alarm $_IPA IP address of the server $_CTY Community $_SEV Severity of the alarm (critical, major, minor, informational, unknown) $_TIM Time model (format: yyyy-mm-dd-hh.mm.
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 (admin@test.co.jp). 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.
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. Ê Click Add. The Type of new Destination dialog box opens. Ê Select Mail and click OK. The New Mail Configuration window opens. Ê Enter the required item in each field on the Mail Settings tab.
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.
5 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. A trap can be uniquely identified with the trap ID and MIB OID. I In WBEM (Web-Based Enterprise Management) environments CIM providers send events as CIM indications. CIM indications largely correspond to the traps defined in the SC2.MIB.
Displaying trap information Ê Under Alarms, select the Agent Alarm Information option. I The trap information can also be called up in the same way via the start window of ServerView Operations Manager.
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.
Displaying traps in the Windows event log 5.2 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. the trap mylexBBUFound with the trap number 275 is shown in the event log with the trap number 10275).
Trap overview MIB Traps from baspTrap.mib Broadcom Advanced Server traps Comments BIOS.mib BUS.mib clariion1.mib FibreCat clariion_fsc_2.mib FibreCat Cmc32.mib Rittal rack monitor CMS-TC.mib Ddm.mib DuplexDataManager traps see page 105 dec.mib Compaq StorageWorks Enterprise Array Manager see page 125 desktrap.mib DeskView traps dhtraps.mib domagt.mib dptscsi.mib DPT SCSI traps see page 103 Duralink.mib ADAPTEC Duralink traps see page 92 DW.
Trap overview MIB Traps from Comments Ldcm.mib LAN Desk Client Manager from Intel traps see page 162 Ldsm.MIB LAN Desk Server Manager from Intel traps see page 162 log3v1.mib PRIMEPOWER log entries see page 120 Megaraid.mib RAID adapter from American Mega Trends Inc. see page 129 MIxraid.mib MylexDiskArrayController traps Lsi1030.mib LSIRAID-IDE.mib MMB-COM-MIB.mib MMB-ComTrapMIB.mib mp.mib MultiPath traps see page 113 Mylex.mib RAID controller (Mylex DAC 960) see page 114 net-snmp.
Trap overview MIB Traps from PSALinBcm5700TrapMIB.mib PRIMEQUEST traps PSA-LinEmulexTrapMIB.mib PRIMEQUEST traps PSA-LinGdsTrapMIB.mib PRIMEQUEST traps PSA-LinGlsTrapMIB.mib PRIMEQUEST traps PSA-LinGrmpdTrapMIB.mib PRIMEQUEST traps PSALinIntelE1000TrapMIB.mib PRIMEQUEST traps PSALinIntelE100TrapMIB.mib PRIMEQUEST traps PSALinLanComTrapMIB.mib PRIMEQUEST traps PSALinLsiLogicTrapMIB.mib PRIMEQUEST traps PSALinScsiComTrapMIB.mib PRIMEQUEST traps PSA-LinTg3TrapMIB.
Trap overview MIB Traps from PSAWinIntelE100TrapMIB.mib PRIMEQUEST traps PSAWinLsiLogicTrapMIB.mib PRIMEQUEST traps Comments RAID.mib RFC1157.mib RFC1213.mib RFC1285.mib RFC1628.mib RMSC_SNMPv1_contact. mib RMSC_SNMPv1_humid1. mib RMSC_SNMPv1_humid2. mib RMSC_SNMPv1_main.mi b RMSC_SNMPv1_output. mib RMSC_SNMPv1_temp2. mib Rompilot.mib RomPilot traps S31.mib Blade server traps SANMgrV1.mib Pathlight SAN Data Gateway SC.mib ServerControl traps see page 132 see page 133 SC2.mib SECURITY.
Trap overview MIB Traps from Comments ServerView.mib ServerView traps see page 145 Status.mib ServerView status traps see page 146 tapealrt.mib Tape driver traps see page 147 Trap.mib ServerView traps see page 163 trap1493.mib Switch traps trap1757.mib Switch traps Threshold.mib TOK.mib unicorn-trap.mib uniserv.mib PRIMEPOWER Enterprise Server see page 121 Upsman.mib Enterprise Specific Top Level MIB by Quazar GmbH, UPS traps 1 see page 168 v1_fscHaCI.
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 ID Meaning Error class duralinkStatusTrap 1 The link status has changed. informational failoverStatusTrap 1 The failover status has changed. informational Table 19: 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.
Trap overview Trap name ID Meaning Error class communication Established 8 Communication is established between the agent and power supply. informational communicationLost 1 Communication between the agent and power supply was interrupted. major contactFault 18 One of the contacts on the Measure UPS has changed from its default position. major contactFaultResolved 19 An error on one of the Measure UPS contacts has been resolved.
Trap overview Trap name ID Meaning Error class softwareBypass 21 The UPS has been set to bypass by a user via software or via the UPS front panel. minor switchedBypass 22 The UPS has been set to minor bypass by a user via the switch on the back. upsBatteryNeeds Replacement 17 The UPS batteries require immediate replacement. major upsDiagnosticsFailed 3 Internal UPS self-test failed. major upsDiagnosticsPassed 10 Internal UPS self-test passed.
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 ID 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. critical s31MgmtBladeCriticalError 1605 The management blade status at the blade system is critical.
Trap overview Trap name ID Meaning Error class s31ServerBladeError 1609 The server blade status at critical the blade system is error. s31ServerBladeHot Replace 1640 A server blade was added informational by hot replace. s31ServerBladeNewAdd 1639 A server blade was added informational on an empty slot of the blade system. s31ServerBladeOk 1608 The server blade status at informational the blade system is ok. s31ServerBladeRemoved 1607 A server blade was removed from the blade system.
Trap overview Trap name ID Meaning Error class s31SwitchBladeAdded 1611 A switch blade was added informational to the blade system. s31SwitchBladeCritical Error 1615 The switch blade status at critical the blade system is critical. s31SwitchBladeError 1614 The switch blade status at major the blade system is error. s31SwitchBladeOk 1613 The switch blade status at informational the blade system is ok. s31SwitchBladeRemoved 1612 A switch blade was removed from the blade system.
Trap overview Trap name ID Meaning Error class s31SysPowerSupplyRemo ved 1627 A power supply unit was 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 sensor of the blade server is out of normal range.
Trap overview Trap name ID 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 Failure 1637 An user authentication major failure was detected at the blade system. Performing the protocol.
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 ID Meaning Error class sniWpChange ClusterActiveAgain 811 The SNMP agent has established the connection with the cluster service. informational sniWpChange ClusterNoLonger Active 812 The SNMP agent has lost the critical connection with the cluster service.
Trap overview Trap name ID Meaning Error class sniWpChange NetworkDeleted 910 A network was deleted from the cluster. critical sniWpChange NetworkProperty 913 The settings for a network have been changed. major sniWpChange NetworkState 912 A network has changed its status. major sniWpChange NodeAdded 831 A new node was added to the informational cluster. sniWpChange NodeDeleted 830 A node has been permanently deleted from the cluster.
Trap overview Trap name ID Meaning Error class sniWpChange Unknown 801 The cluster API has returned critical a note type that does not have an associated trap definition.
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 ID Meaning Error class dptArrayCfgChangeTrap 12 Configuration of a RAID informational array changed due to one of the following events: – creating a new array – deleting an existing array – modifying an array (changing stripe size, etc.) dptDevBlock ReassignedTrap 6 The HBA reassigned a block. dptScsiDevBadBlockNumber contains the reassigned block number.
Trap overview Trap name ID Meaning Error class dptDevStatus ChangedTrap 9 Status of the SCSI device changed. informational dptHbaCorrected HardRAMErrorTrap 4 The HBA encountered an informational ECC RAM error and corrected it. dptScsiHbaBadMemoryAddre ss contains the RAM address. dptHbaSoftRAM ErrorTrap 3 informational The HBA encountered an ECC RAM error, but the error is not found on the physical disk block. dptScsiHbaBadMemoryAddre ss contains the RAM address.
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 ID 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. FscDdmPieceRemoved 1401 After the driver has removed a disk from a DuplexWrite group as requested by the user.
Trap overview Trap name ID 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. FscDdmConfigChanged 1408 Repeated reading of the configuration by the driver detects a modified configuration.
Trap overview Trap name ID Meaning Error class FscDdmNameChanged 1414 After the driver has changed the name of a DuplexWrite group. informational FscDdmPathFailed 1415 After the driver has detected an error on one path of a MultiPath group. critical FscDdmRetry 1416 After the driver has detected an error on one path of a MultiPath group and the retry of the command was successful on another path.
Trap overview Trap name ID Meaning Error class FscDdmDdmCluster 1424 After the DuplexDataManager service has detected a cluster configuration change.
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 ID Meaning Error class sieDWActiveLunChan 1310 ged A user has changed the informational read path for a DuplexWrite group to a certain disk. sieDWConfig Changed The driver has reread the configuration and found a modified configuration.
Trap overview Trap name ID Meaning Error class sieDWPieceFailed 1311 The driver has detected an critical error on one of the disks of a DuplexWrite group. sieDWPieceRecovere 1305 d A DuplexWrite group was informational successfully recovered. Both elements of the DuplexWrite group have the status ONLINE. sieDWPieceRemoved 1301 A user has removed a disk from a DuplexWrite group. The action was requested by the configuration utility.
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 ID Meaning Error class sniSMARTFailure Predicted 750 S.M.A.R.T. is warning that a hard disk may fail. critical sniSMARTMonitoring 751 Disabled The S.M.A.R.T. configuration informational has been changed.
Trap overview 5.3.9 Generic traps This section lists generic traps in alphabetical order. Trap name ID Meaning Error class coldStart 0 An agent was restarted. minor MIB view objects may have changed. egpNeighborLoss 5 An EGP neighbor of the managed node changed from the UP to the DOWN state. major linkDown 2 An interface of the managed node changed from the UP to the DOWN state. critical linkUp 3 One interface of the managed node changed from the DOWN to the UP state.
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 ID Meaning Error class sieMP ActivePortChanged 1202 The user has enabled or 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 automatic recovery.
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 ID Meaning Error class mylexAdapterDied 221 Connection to a disk array controller interrupted. critical mylexAutoRebuild Started 200 Automatic rebuild of a unit has been started. critical mylexAutoRebuild Started2 222 Automatic rebuild of a system drive has been started. informational mylexBBUFound 275 Battery Backup Unit found.
Trap overview Trap name ID Meaning Error class mylexLogicalDriveOffline 214 Logical drive is offline. critical mylexLogicalDriveOnline 216 Logical drive is online. critical mylexManualRebuild Started 201 Manual rebuild started. informational mylexManualRebuild Started2 223 Manual rebuild started. After the rebuild has finished successfully, mylexRebuildDone2 will be sent. informational mylexParityCheck Cancelled 210 Parity check canceled.
Trap overview Trap name ID Meaning Error class mylexPhysicalDevice Prefailure 255 Prefailure alert from physical device. major mylexPhysicalDevice Removed 258 Physical device has been removed. major mylexPhysicalDevice SoftError minor 252 A normal (soft) error has occurred in physical device. mylexPhysicalDevice Unconfigured 256 Physical device is unconfigured. minor mylexRaidExpansion Done 236 RAID capacity expansion completed successfully.
Trap overview Trap name ID Meaning Error class mylexRebuildNew DeviceFailed 206 Rebuild finished; new device failed. major mylexRebuildNewDevice Failed2 227 Rebuild of system drive; new device has failed. major mylexRebuildStatus 204 Rebuild status. informational mylexSMART ConfigurationChanged 271 S.M.A.R.T. configuration has been changed. informational mylexSMART FailurePredicted 270 Sent if a failure (S.M.A.R.T.) critical has been predicted on a physical disk.
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 ID Meaning Error class sieDeviceHotPlug TrapHotAdd 1022 A SCSI device was added. informational sieDeviceHotPlug TrapHotRemoval 1020 A SCSI device was removed. informational sieDeviceHotPlug TrapHotReplace 1021 A SCSI device was replaced.
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 ID Meaning Error class doorStateChange 2 The door state has changed. informational error 6 The device has an error. Error informational code and error data is displayed. mailboxStateChange 3 The mailbox state has changed. informational sac 7 The device has generated a SAC code.
Trap overview Trap name ID Meaning Error class domNoManagementS 55 erver An agent was stopped. informational domStartTrap An agent was started. informational 54 Table 32: DOMAIN-MIB traps FSC-LOG3-MIB traps (log3v1.mib) MIB-OID: 1.3.6.1.4.1.231.2.46.2 Trap name ID Meaning Error class log3AlertNotice 2 A log3Event has occurred. System, module, error and text is displayed. critical log3CriticalNotice 3 A log3Event has occurred. System, module, error and text is displayed.
Trap overview Trap name ID Meaning Error class log3WarningNotice 5 A log3Event has occurred. System, module, error and text is displayed. minor Table 33: FSC-LOG3-MIB traps UNISERV-MIB traps (uniserv.mib) MIB-OID: 1.3.6.1.4.1.231.2.41 Trap name ID Meaning Error class kaiPartitionOffline 700 A partition was powered off. minor kaiPartitionOnline 701 A partition was powered on. informational Table 34: UNISERV-MIB traps PRIMEPOWER-XSCF-MIB traps (primepower_xscf.mib) MIB-OID: 1.3.6.1.4.1.
Trap overview FSC-HACL-MIB traps (v1_fscHaCl.mib) MIB-OID: 1.3.6.1.4.1.231.2.42.2.0 Trap name ID Meaning Error class fscHaClApplicationSt ateChanged 5 Application state has changed. major fscHaClClusterInfAvai 1 lable Cluster information is available. InfoOperScope is displayed. informational fscHaClClusterInfNot Available 2 Cluster information is no longer available. InfoOperScope is displayed. major fscHaClMonitorState Changed 3 Cluster monitoring state has changed.
Trap overview Trap name ID Meaning wsaDROperationFinishe d 313 DR operation was terminated. Error class informational wsaEnvironmentHardwar 301 Defect on environment eDefectSet hardware has occurred. critical wsaEnvironmentHardwar 302 Error on environment eErrorSet hardware has occurred. critical wsaEnvironmentRepair 303 Environment component was repaired. minor wsaErrorRepair 6 minor wsaGenLogMessage 900 Error in one module on server has occurred.
Trap overview Trap name ID wsaLarHardwareErrorUn 4 set wsaLUNStateChanged Meaning Error class A hardware error was repaired. informational 101 State of LUN has changed. critical wsaMonitoringRuleInitiali 311 EEM rule was initialized. zed minor wsaMonitoringRuleMatch 310 EEM rule was matched. ed informational wsaNodeStatusIntegrate d A node was integrated. informational 24 wsaNodeStatusNotavail 25 A node is not available. critical wsaNodeStatusNotrunni ng 26 A node is not running.
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 ID Meaning Error class cacheBatteryFailureTrap 7 A controller cache battery major has failed. Replace cache battery or replenish charge. cacheBattery InformationTrap 9 A controller cache battery has GOOD state. informational cacheBatteryLowTrap 8 A controller cache battery has LOW state. Replace cache battery or replenish charge.
Trap overview Trap name ID Meaning Error class diskFailureTrap 1 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: – DISK10100 is disk location Port 1, Target 01, Lun 00. – DISK30300 is disk location Port 3, Target 03, Lun 00. diskInformationTrap 2 A disk drive has recovered. informational The location of the disk is indicated by the disk name.
Trap overview Trap name ID Meaning Error class fanFailureTrap 5 The fan in the specified major location has failed. Replace fan. fanInformationTrap 6 The fan in the specified location was recovered. lunFailureTrap 16 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 communicate with the LUN for other reasons.
Trap overview Trap name ID Meaning Error class powerSupplyFailureTrap 3 The power supply in the specified location has failed. Replace power supply. major powerSupply InformationTrap 4 Power supply was recovered. informational temperature InformationTrap 11 A temperature sensor indicates temperature below WARNING threshold limit. informational temperatureOver ThresholdTrap 10 A temperature sensor has major exceeded WARNING threshold limit.
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 ID Meaning Error class rtBatteryMissing 9020 Adapter-%d: Battery Module is missing. informational rtBattery TemperatureHigh 9022 Adapter-%d: Battery Module temperature exceeded Danger Threshold. informational rtBatteryVolatageLow 9021 Adapter-%d: Battery Module voltage is low.
Trap overview Trap name ID Meaning Error class rtConsistency Corrected 9011 Adapter-%d, Logical Drive%d: Check consistency operation completed. Inconsistencies have been cured. informational rtInitializeAborted 9006 Adapter-%d, Logical Drive- informational %d: Initialization aborted by user. rtInitializeCompleted 9005 Adapter-%d, Logical Drive- informational %d: Initialization completed successfully. rtInitializeFailed 9007 Adapter-%d, Logical Drive%d: Initialization failed.
Trap overview Trap name ID Meaning Error class rtPredictiveFailures False 9017 Adapter-%d, Channel-%d, informational Target-%d: Reported failure prediction threshold exceeded [FALSE]. Drive identification string = %s Sense Key = 0x%x, ASC = 0x%x, ASCQ = 0x%x. rtReconstruction Completed 9014 Adapter-%d, Logical Drive%d: Reconstruction completed successfully. informational rtReconstructionFailed 9015 Adapter-%d, Logical Drive%d: Reconstruction failed.
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 ID Meaning Error class RomPilotColdReset 258 Phoenix RomPilot was loaded after a cold system reset. informational RomPilot DiagnosticReset 259 Phoenix RomPilot was loaded after a diagnostic system reset. informational RomPilotFatalError 769 Phoenix RomPilot detected informational a fatal error.
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 ID Meaning 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. minor correctableMemError Addr 637 Correctable memory error at address.
Trap overview Trap name ID 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 reached. powerSupplyAdded 625 A power supply was added. informational powerSupplyFailed 626 A power supply has failed. major powerSupplyOk 627 The power supply is working again. informational powerSupplyRemoved 624 The power supply has been informational removed.
Trap overview Trap name ID Meaning sieScBootError 661 No bootable operating system can be found. Error class informational sieScBootWatchdogExpir 662 Boot watchdog expires. ed informational sieScCpuPrefailure 673 A CPU is predicted to fail (prefailure). major sieScDiagnosticBoot 665 Server is reset and diagnostic boot is enabled. informational sieScMessageLogFull 667 System Event Log is full. No minor more message can be logged. Trap will not occur on wrap-around log types.
Trap overview Trap name ID Meaning Error class sieScUserAuthentication Failure 664 User authentication failure is detected via PPP, FTP, HTTP or telnet. major sniScCpuSpeedChanged 656 CPU speed has changed because of temperature problems. informational sniScFanAdded 653 The indicated hot-plug fan was inserted. informational sniScFanRemoved 654 The indicated hot-plug fan was removed. informational sniScPowerSupply RedundancyLost 671 Power supply redundancy no longer available.
Trap overview Trap name ID Meaning Error class tempSensorBroken 630 The temperature sensor is major defective or not connected. tempSensorOk 635 The temperature sensor is working again. informational tempWarn 603 The temperature has reached the warning level. major testTrap 600 Test trap sent to verify trap connection. informational tooManyCabinets 616 The actual number of storage subsystems is higher than the number stored in the configuration. minor trapAcFail 632 AC power has failed.
Trap overview Trap name ID 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 system is switched off. trapOnMains 607 AC power OK. informational uncorrectableMemError 644 Uncorrectable memory error.
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 ID Meaning Error class sc2TrapAcFail 2040 Mains failed in the specified critical cabinet. This trap occurs only in storage extension cabinets without UPS or BBU. A server has no time to send this trap. sc2TrapBatteryVoltage Prefail 2054 Battery is predicted to fail.
Trap overview Trap name ID 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 dOn cabinet is switched on. sc2TrapCommunication 2002 The communication with informational Established the management controller was reestablished.
Trap overview Trap name ID Meaning Error class sc2TrapDcFail 2041 DC power failed in the specified cabinet. This is the result of the systems power-good sensor monitoring. The system stops if this error occurs. critical sc2TrapFanAdded 2010 The indicated hot-plug fan was inserted. informational sc2TrapFanCritical 2013 The indicated fan became critical. major sc2TrapFanFailed 2014 The indicated fan failed. critical sc2TrapFanOk 2012 The indicated fan is OK again.
Trap overview Trap name ID Meaning Error class sc2TrapMessageLogFul 2100 The System Event Log l (message log) is full. No more messages can be logged. This trap will not occur on wrap-around log types. minor sc2TrapMessageLogWa 2101 The warning threshold for minor rning the number of System Event Log entries has been exceeded. sc2TrapOnBattery 2042 The UPS is operating on critical battery power or the power supply is drawing current from the backup battery unit (BBU).
Trap overview Trap name ID Meaning sc2TrapRedundantFanF 2015 The indicated redundant ailed fan failed. Error class major sc2TrapRedundantPow erSupplyFailed 2035 One redundant hot-replace major power supply failed. sc2TrapServerShutdow n 2093 This trap will be sent before informational a server will switch off. sc2TrapSevereSystemE 2006 The system was restarted critical rror after a severe problem. See server management message log (recovery log) for detailed information.
Trap overview Trap name ID Meaning Error class sc2TrapUncorrectableM 2067 A uncorrectable memory emError error at unknown location was detected. critical sc2TrapUncorrectableM 2061 An uncorrectable memory emErrorAddr error at specified address was detected. critical sc2TrapUncorrectableM 2063 An uncorrectable memory critical emErrorBank error at specified bank was detected. sc2TrapUncorrectableM 2065 A correctable memory error critical emErrorModule at specified module was detected.
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 ID Meaning Error class sniSvGenericTrap Forward 700 A ServerView alarm signal has been received. informational sniSvPagerOff 701 The pager should be switched off. informational sniSvPassThrough TrapForward 703 Forwarded if the Event informational Manager receives a trap to be forwarded. The original server name and severity is retained.
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 ID sieStTrapStatusChanged 1100 Meaning Error class System status has changed informational at server.
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 ID Meaning Error class tapeAlertTrap1 1 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. tapeAlertTrap2 2 The tape drive is having minor problems writing data. No data has been lost, but there has been a reduction in the capacity of the tape.
Trap overview Trap name ID Meaning Error class tapeAlertTrap6 6 The tape is from a faulty batch or the tape drive is faulty: critical 1. Use a good tape to test the drive. 2. If the problem persists, call the tape drive supplier helpline. tapeAlertTrap7 7 The tape cartridge has reached the end of its calculated useful life: minor 1. Copy any data you need to another tape 2. Discard the old tape. tapeAlertTrap8 8 The tape cartridge is not data-grade.
Trap overview Trap name ID Meaning Error class tapeAlertTrap12 12 You have tried to load a informational cartridge of a type which is not supported by this drive. tapeAlertTrap13 13 The operation has failed because the tape in the drive has snapped: critical 1. Discard the old tape. 2. Restart the operation with a different tape. tapeAlertTrap14 14 The operation has failed because the tape in the drive has snapped: critical 1. Do not attempt to extract the tape cartridge. 2.
Trap overview Trap name ID Meaning Error class tapeAlertTrap19 19 informational The tape cartridge is 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. tapeAlertTrap20 20 critical The tape drive needs cleaning: 1. If the operation has stopped, eject the tape and clean the drive. 2.
Trap overview Trap name ID Meaning Error class tapeAlertTrap23 23 The last cleaning cartridge used in the tape drive was an invalid type: critical 1. Do not use this cleaning cartridge in this drive. 2. Wait for the current operation to finish. 3. Then use a valid cleaning cartridge. tapeAlertTrap29 29 Preventive maintenance of minor the tape drive is required. Check the tape drive users manual for device specific preventive maintenance tasks or call the tape drive supplier helpline.
Trap overview Trap name ID Meaning Error class tapeAlertTrap32 32 The tape drive has a problem with the host interface: minor 1. Check the cables and cable connections. 2. Restart the operation. tapeAlertTrap33 33 The operation has failed: critical 1. Eject the tape or magazine. 2. Insert the tape or magazine again. 3. Restart the operation. tapeAlertTrap34 34 The firmware download has minor failed because you have tried to use the incorrect firmware for this tape drive.
Trap overview Trap name ID Meaning Error class tapeAlertTrap39 39 The tape drive may have a 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. minor tapeAlertTrap40 40 The changer mechanism is critical having difficulty communicating with the tape drive: 1. Turn the autoloader off then on. 2. Restart the operation. 3.
Trap overview Trap name ID Meaning Error class tapeAlertTrap43 43 The operation has failed because the autoloader door is open: critical 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. 4. If the problem persists, call the tape drive supplier helpline. tapeAlertTrap44 44 The autoloader has a hardware fault: critical 1. Turn the autoloader off and then on again. 2.
Trap overview Trap name ID Meaning tapeAlertTrap256 256 The library mechanism is having difficulty communicating with the drive: Error class critical 1. Turn the library off then on. 2. Restart the operation. 3. If problem persists, call the library supplier helpline. tapeAlertTrap257 257 There is a problem with the minor library mechanism. If problem persists, call the library supplier helpline. tapeAlertTrap258 258 The library has a hardware critical fault: 1. Reset the library. 2.
Trap overview Trap name ID 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 with the host interface: critical 1. Check the cables and cable connections. 2. Restart the operation.
Trap overview Trap name ID Meaning Error class tapeAlertTrap266 critical 266 The voltage supply to the 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: 1. Insert an empty magazine to clear the fault. 2. If the fault does not clear, turn the library off and then on again. 3.
Trap overview Trap name ID Meaning Error class tapeAlertTrap271 271 The operation has failed because the library door is open: critical 1. Clear any obstructions from the library door. 2. Close the library door. 3. If the problem persists, call the library supplier helpline. tapeAlertTrap272 272 There is a mechanical problem with the library media import/export mailslot. critical tapeAlertTrap273 273 The library cannot operate without the magazine. critical 1.
Trap overview Trap name ID 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 inconsistency in its inventory. critical 1. Redo the library inventory to correct inconsistency. 2.
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 ID Meaning Error class trapACFail 13 AC Power failed. major trapAssetChange 23 Asset is changed. major trapBatteryFail 15 UPS battery fails. major trapBusUtilization 8 Percent bus utilization exceeds the threshold value. major trapBiosEventLog 20 BIOS has new event log.
Trap overview Trap name ID Meaning Error class trapPowerFanFail 14 Any power subsystem fan fails. major trapPSFail 12 Any power supply fails. major trapRPSFail 18 Redundant power supply is major failed. trapRPSFanFail 19 Redundant power supply fan is failed. major trapTemperatureCritical 2 Temperatures exceed the second level threshold value. critical trapVoltage 6 Any voltage reading major exceeds the save operating range.
Trap overview LDCM MIB traps (Ldcm.mib) MIB-OID: 1.3.6.1.4.1.343.2.5.1.2 Trap name ID Meaning Error class ldcmCriticalTrap 5 Manager has reported a severity Critical event. critical ldcmFatalTrap 6 Manager has reported a severity Fatal event. critical ldcmInfoTrap 2 Manager has reported an Informational event. informational ldcmOkTrap 3 Manager has reported a severity OK event. informational ldcmUnknownTrap 1 Manager has reported an Unknown event.
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 ID Meaning Error class sniInvDeltaTrap Underflow 131 DELTA threshold underflow. informational This trap indicates, that one of the polled variables has left the interval specified by the user. The variable will be given in the sniInvPollAlarm field. sniInvPollDeltaExceed 130 DELTA threshold exceeded.
Trap overview Trap name ID Meaning Error class sniInvTrapValid 133 Threshold has become valid. informational sniNTAlert 304 NT alert message was written to the event log. informational sniNTChangeSecurity 302 Security change has occurred. informational sniNTChangeTime 305 Time has changed or a informational nonuniform time adjustment has occurred. sniNTDownServer 300 Server is going down. informational sniNTEventLogError 330 Error entry was written to event log.
Trap overview Trap name ID Meaning Error class sniNTLoginUser 301 User logged into server. sniNTRegChangeAttr 311 Attributes for a key or its informational subtree in registry has been changed. sniNTRegChangeLast Write 312 Last write time for a key or its subtree in registry has been changed. informational sniNTRegChangeName 310 Keyname in registry has been changed. informational sniNTRegChange Security 313 Security for a key or its informational subtree in registry has been changed.
Trap overview Trap name ID Meaning Error class sniNWDataMigration 041 A files data has been migrated. informational sniNWDataDeMigration 042 Migration of file has been withdrawn. informational sniNWDeactivateScreen 018 Screen is deactivated on server. informational sniNWDeleteBinderyObj 012 Bindery object was deleted informational (NetWare). sniNWDeleteObject 047 Directory Service (NetWare) object was deleted. informational sniNWDestroyProcess 029 Process was destroyed.
Trap overview Trap name ID Meaning Error class sniNWNoRelinquish Control 023 NLM-Module has not relinquished control. critical sniNWOpenScreen 020 Screen was opened on server. informational sniNWProtocolBind 033 A Protocol is bound to a MLID. informational sniNWProtocolUnbind 034 A Protocol is unbound from warning a MLID. sniNWQueueAction 043 A queue was activated, deactivated, created or deleted. informational sniNWRenameObject 048 Directory Service (NetWare) object was renamed.
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 ID Meaning Error class communication Established 4 The connection with the UPS was established. informational communicationLost 1 The connection with the UPS was lost. critical powerRestored 5 Normal power has been restored to the UPS. informational testCompleted 8 The UPS test was completed.
Trap overview UPS traps 2 Trap name ID Meaning Error class boostOn 6 The UPS has turned on the major booster. communication Established 8 The connection with the UPS was established. informational communicationLost 1 The connection with the UPS was lost. critical lowBattery 7 The batteries are low and will soon be empty. critical powerRestored 9 Normal power has been restored to the UPS.
Trap overview 170 ServerView Event Manager
6 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. I The following example shows the format for a description of TRAP-Type, where TRAP-Type must have the format SMIv1.
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. In the next window a message shows the status. Ê Click the Save parsed MIB button to integrate the MIB. Ê In the next window, select Close to close the tool.
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. I Please note that the MIB Integrator distinguishes between upper and lower case.
MIB integration 174 ServerView Event Manager
