integrating dell servers into an insight manager environment€¦ · web viewthe registration...

Integrating Dell PowerEdge Servers into

an Environment Managed by Insight

Manager

Dell™ OpenManage™Systems Management

Dell White PaperBy Roger Foreman

[email protected]

March 2003

mailto:[email protected]

ContentsIntroduction........................................................................................4Test Configuration...............................................................................5Loading and Configuring Server Administrator..................................6

What SNMP configuration should I use?........................................6Using Dell Server Assistant to load the OS and SNMP..................6SNMP Configuration after OS installation.....................................7Loading Server Administrator........................................................8Testing..........................................................................................11

Selecting and Loading the Dell MIBs................................................12Typographical Conventions..........................................................12Upload the MIBs...........................................................................13Register the MIBs.........................................................................13

Device Type Manager........................................................................15Tailoring and Final Testing for Events.............................................18

Final Testing.................................................................................19Results...............................................................................................20Limitations and Caveats:...................................................................20Appendix A – Dell MIBS.....................................................................21

Essential Server MIBS..................................................................21Network Interface Adapters.........................................................21Other Adapters, Devices, and Software........................................22Legacy MIBS.................................................................................22

FiguresFigure 1: Architecture of the Tested Environment......................................................5Figure 2: Setting Security and Trap Destinations.......................................................8Figure 3: Customizing the Server Administrator Installation.....................................9Figure 4: Server Administrator Options....................................................................10Figure 5: Testing the PowerEdge Server with SNMPWALK.....................................11Figure 6: go-dell.asp..................................................................................................16

March 2003 Dell Enterprise Product Group

Section 1Introduction

In response to the pressure for increased productivity of system administrators, server vendors have responded with management tools. Dell’s offering is the Dell™ OpenManage™ suite of products. While these products cover software deployment, hardware configuration, asset management, remote support, and system health monitoring, this paper is focused on monitoring system health on a collection of servers. To do this, OpenManage Server Administrator is loaded on every Dell PowerEdge™ server to be managed, and one instance of OpenManage IT Assistant is installed and configured for monitoring all the PowerEdge servers. Errors detected by Server Administrator are then forwarded via Simple Network Management Protocol (SNMP) to IT Assistant, where they are logged and can generate email and paging notifications.Since a Hewlett-Packard Insight Manager™ 7 environment has the same architecture, it is possible to integrate Dell PowerEdge servers by taking advantage of the industry standard interfaces of SNMP and Hypertext Transport Protocol – Secure (HTTPS) in Server Administrator. The advantage would be for administrators to continue to use their existing notification processes while fully benefiting from the use of Server Administrator on Dell servers.This paper details the specific steps needed to add a Dell PowerEdge 1650 server running Microsoft® Windows® 2000 server to an environment currently being managed by Insight Manager 7. To add a server running NetWare® or Linux®, the Insight Manager 7 and OpenManage Server Administrator configuration would be the same, with the primary difference being how SNMP is configured at each managed PowerEdge server. At a high level, and ordered for ease of troubleshooting, the steps are:

Load and configure the OpenManage Server Administrator on the Dell server so it can communicate with Insight Manager 7

Load Dell MIBS into Insight Manager 7 so it can properly communicate with Server Administrator

Configure Insight Manager 7 to recognize Dell servers Map the Dell Traps into alert actions and perform an end-to-

end test.


Section 2Test Configuration

The scenario that was tested was a Hewlett-Packard DL580 running Microsoft Windows 2000 Server with Microsoft Data Engine (MSDE) database and Insight Manager 7 SP1 installed and configured as the management console. To this was added a Dell PowerEdge 1650 Server running Microsoft Windows 2000 Server with the latest OpenManage Server Administrator (version 1.3) as the managed system.

Figure 1: Architecture of the Tested Environment


Section 3Loading and Configuring Server Administrator

The first step is to properly load and configure the Dell server as the managed system to talk to Insight Manager 7. If the operating system (OS) has not yet been loaded, then the easiest process is to use the Dell Server Assistant CD to load both Microsoft Windows and SNMP. If the OS was already loaded, then only SNMP needs to be loaded and configured. Once SNMP is configured, the OpenManage Server Administrator can be installed.

What SNMP configuration should I use?The default SNMP community name is public, but using that could allow a rogue management station to access your servers. The SNMP community name is like a password both Insight Manager 7 and Server Administrator need to communicate. To enhance security, access can be Read Only. This prohibits using SNMP to make changes to the server, such as changing threshold settings or shutting it down, but allows Server Administrator to send alerts to a console when status changes. With a Dell PowerEdge Server, users will not lose functionality during this process. It is possible that other systems need SNMP set to Read Write, so be sure the total environment is well understood.

If the intent were for Insight Manager 7 and IT Assistant to coexist in the network to provide the full OpenManage capabilities, then it would be necessary to configure the Dell PowerEdge server with Read Write SNMP permissions. Note that Dell secures Read Write operations using SNMP only to come from Dell OpenManage IT Assistant.

SNMP trap destinations also need to be specified. These are the hostnames or IP addresses of one or more systems that are to receive notification of events.

For this paper, the community name of showcase with Read Only rights was used with a single trap destination to compaq2 running Insight Manager 7. These settings need to be made on each Dell server added to the environment.


Using Dell Server Assistant to load the OS and SNMPThere are three CDs that ship with every Dell PowerEdge server – the Dell OpenManage Server Assistant CD, the Dell OpenManage Systems Management CD, and the Product Documentation CD. The Server Assistant CD is bootable and is used to perform a complete installation from local media. It can also be used with a running system and brings up a menu for access to drivers and BIOS/FW update diskettes.

The PowerEdge 1650 in the configuration tested for this paper was booted from the Server Assistant CD and the menus were followed until the screen titled “Enter Microsoft Windows 2000 Server Configuration Information” was reached. On that screen, it was necessary to scroll down past “Select Optional Components” to enter the SNMP information. The default is Enable SNMP, but it is also necessary to enter a Community Name and Trap Destination and change the Accepted Community Names from “public:Read_Only” to “showcase:Read_Only”. The rest of the defaults should be left unchanged.

At the very bottom of the screen, past the NIC configuration, the Install Dell OpenManage Server Administrator box is checked by default. Uncheck it to allow explicit setting of the appropriate options instead of taking the Express Options. These are described later in the Loading Server Administrator section. If missed, just select Cancel when prompted for the System Management CD after the system reboots and continue with the section below: Loading Server Administrator.

SNMP Configuration after OS installationIf the Server Assistant CD has not been used to load the OS and configure SNMP, then the following steps should be performed. The first is to ensure that the SNMP component is installed. After selecting the “Add/Remove Windows Components” in the left hand of the Add/Remove Programs dialog box of the Control Panel, the Windows Components are displayed. Highlighting “Management and Monitoring Tools” and then selecting “Details” brings up the option to check Simple Network Management Protocol (SNMP).

After the SNMP service is installed, its parameters can be set by right clicking on the SNMP service in Service Manager to open the Properties panel. Here the community name of showcase and trap


destination of compaq2 can be set in the security and traps tabs.

These are shown in Figure 2.

Figure 2: Setting Security and Trap Destinations

Loading Server AdministratorServer Administrator is distributed on the Dell OpenManage Systems Management CD. Documentation is available online at http://docs.us.dell.com/docs/Software/svradmin/ or on the Product Documentation CD. Note that the CD is Version 3.3, denoting the release of all of the OpenManage software, and the version of Server Administrator is 1.3 on that CD.

Although manually loading Server Administrator on a single server is covered in this paper, it is possible to completely script and automate the install. For more information see http://www.dell.com/downloads/global/topics/openmanage/Unattended_Installation_Enhancements_of_Server_Administrator_for_Windows_Platforms.doc.

After inserting the Systems Management CD it will AUTORUN. The user input is as follows:

“Install… Systems Management Software”

“Acknowledge” the Dell Software License Agreement

“Install Managed System” after which there is a wait while “Preparing the wizard”


http://www.dell.com/downloads/global/topics/openmanage/Unattended_Installation_Enhancements_of_Server_Administrator_for_Windows_Platforms.doc



http://docs.us.dell.com/docs/Software/svradmin/

“Custom Setup”

The default destination is OK so select “Next”

This leads to the Managed System Software page, which can be followed for the actual configuration.

Figure 3: Customizing the Server Administrator Installation

Select “Settings” on Other Management Agents, uncheck Adaptec CIO, then select “OK” as this function is now handled by the Storage Management code.

Remote Access and Diagnostic Service should be checked – if not, look at “More Info” for suggestions. Diagnostic Service can be left off for a smaller footprint, but might need to be re-loaded later for problem determination.

Storage Management – If the box is not checked, then select “More Info,” which will tell why. A common message here is “FW out of date.” The FW level needed is on the Server Assistant CD at the same level. Once Server Administrator is installed, it can be used to update firmware, but at this point a boot diskette is needed. For this test, version 1.72 or later of the RAID controller firmware was necessary.


Select Settings on OpenManage Server Administrator. This is where the user’s root password is set to something other than the default. Selspassword was used for this paper.

Figure 4: Server Administrator Options

Since Insight Manager 7 does not use the Common Information Model (CIM), the option to Install CIM can be unchecked to close a potential security opening. The final step is to allow the installation process to restart the server. During this, the process also saves InstallSummary.htm, unattend.txt and DOMSA_SETUP.txt files in C:\ for reference.

Volume Capacity Monitoring was also enabled on the PowerEdge 1650 so that free disk space warning and error events would be sent to Insight Manager 7 when 90% and 98% thresholds were reached on the C: drive. It was deemed that the notification was worth the additional overhead of having this service running. This was done by:

Start -> Programs -> Dell OpenManage Applications -> Array Manager -> Array Manager Utilities

Check Volume Capacity Monitoring then Apply and Close


TestingAfter the reboot, Server Administrator was checked to see that it was operating correctly. This was done in the following steps:

Login to the server as Administrator or other account with administrator membership

Launch Server Administrator from the desktop icon or https://sm1650:1311

Login as Administrator or other account with administrator membership

Select Main System Chassis in the left hand navigation The status icons should all be green checks to indicate an error

free statusThen to check and clear storage errors:

Start -> programs -> Dell OpenManage Applications -> Array Manager -> Array Manager Console

Select the Error tab Right click to clear errors

At this point, everything should be working correctly on the Dell system. A further check would be to use snmpwalk, which is part of Win32tools available at http://www.wtcs.org/snmp4tpc/redirect.htm. As shown in Error: Reference source not found, the command saves all available SNMP information available via community string showcase on system 192.168.30.4 to the file dellserver.txt. Providing that DNS or WINS is properly configured for the new Dell Server system, its name can be used instead of the IP address.

Figure 5: Testing the PowerEdge Server with SNMPWALK

When opening dellserver.txt with Notepad, there should be entries with 10892 in the OID that were returned from Server Administrator. Specifically, 1.3.6.1.4.1.674.10892.1.300.10.1.9.1 will contain the model of the server. Running this from the Insight Manager 7 system tests the following: network connectivity, that the community string is correct, and that Server Administrator is providing the expected information.


Snmpwalk 192.168.30.4 –cshowcase >dellserver.txt

http://www.wtcs.org/snmp4tpc/redirect.htm

Section 4Selecting and Loading the Dell MIBs

The MIB files are located in the directory \support\dcpemibs on the Systems Management CD and are well documented in the included README. The two essential MIBS are:

10892, which provides 36 traps from the server motherboard such as: system type, voltages, temps, etc. It is the primary MIB for PowerEdge systems. Detailed information can be found at http://docs.us.dell.com/docs/software/svradmin/1.2/en/SNMP/index.htm

Arymgr, which provides 80 server related traps from the RAID and SCSI subsystem. Detailed information can be found at http://docs.us.dell.com/docs/software/smarrman/marb33/html/ch15_eve.htm#1031694

The remaining MIBS were not loaded for this paper, as they either did not provide any event traps, or their event traps were from adapters not present in the test environment. A description of all the MIBS and their use is documented in Appendix A.

The 10892 MIB registered without error, but the arymgr MIB encountered the “WARNING” severity type that was not recognized by Insight Manager 7. Editing arymgr.mib with Notepad, these TRAP-TYPEs were mapped to supported types as follows:

Perc2SmartFPTExceeded = MAJOR

EnclosureGenericDegraded = MAJOR

AlertPausedCheckConsistency = MINOR

AlertResumedCheckConsistency = INFORMATIONAL

.

Typographical ConventionsFor clarity of navigation, the following conventions are used:Underscore will be used to indicate an HTML hot link, hot spot, or button within an applet

Large Font will indicate the title of a dialog box or applet

Upload the MIBsUploading the MIB makes a copy of the file in


http://docs.us.dell.com/docs/software/smarrman/marb33/html/ch15_eve.htm#1031694

http://docs.us.dell.com/docs/software/smarrman/marb33/html/ch15_eve.htm#1031694

http://docs.us.dell.com/docs/software/svradmin/1.2/en/SNMP/index.htm

http://docs.us.dell.com/docs/software/svradmin/1.2/en/SNMP/index.htm

c:\Program Files\Compaq\Compaq Insight Manager 7\Compaq\Protocol\SNMP\MIBS

which is subsequently used by Insight Manager 7. Both the Essential MIBs and any applicable optional MIBS need to be uploaded with the following procedure: Select the Tools Icon in upper left Expand SNMP Extensions in the left hand navigation panel Select SNMP MIB Upload

On the Upload MIB panel, select Browse

To load from the Dell System Management CDo Look in Compact Disc, Support then dcpemibs folders

Double click the MIB file, such as 10892.mib In Rename To: enter a new name with the .mib extension, or leave

blank for the same name Click on the Upload button Wait for “successfully uploaded” message Repeat for each MIB needed. For this paper, arymgr.mib was also

uploaded

Register the MIBsRegistering MIBs to Insight Manager 7 is the process that maps the SNMP information received from the Dell server to numbers and character strings that can then be used for identification and notification messages. Both the Essential MIBs were registered as follows: Select Tools Icon in upper left In the left hand navigation pane, expand SNMP Extensions then

select MIB Registration

Scroll down and select 10892.mib in the Unregistered MIBS

Check Create Logfile, Use Edit file, and Create Select <<RegisterThis took over two minutes and only returns a message if there is an error. Errors are logged in:

\Program Files\Compaq\Compaq Insight Manager 7\log\10892.txt. A typical error might be missing a pre-requisite file such as DMTF-DMI or failing to register intel.mib prior to intelnic.mib. Although the version of arymgr.mib from OpenManage 3.2 registered without error, the one included with version 3.3 required editing via Notepad to change the WARNING severity to one that is recognized by Insight Manager 7. The resulting SEVERITY levels were:





AlertResumedCheckConsistency = INFORMATIONAL Finally, by selecting create editfile for each MIB registered, a .REV file is created that is customized later in Section 6.


Section 5Device Type Manager

Devices are discovered and added to the Insight Manager 7 database by its Device Type Manager when a new system is detected via a ping sweep or when receiving a SNMP Trap. The Device Type Manager then does a sequence of queries to the new device to determine its identity. The default configuration includes definitions for all the HP devices and even the Dell devices that use the older Desktop Management Interface (DMI), such as an OptiPlex™ desktop running the OpenManage Client Instrumentation (OMCI) version 6.1. Because Server Administrator only supports SNMP, the steps below configure it to look for specific information in the Dell MIBS to tell that the device found is a PowerEdge server. This only needs to be done once, as all Dell servers running Server Administrator appear the same way within Insight Manager 7.The steps used to configure the Device Type Manager to recognize a Dell Server are: Login to Insight Manager 7 with an account having Administrator

Access Select the Tools icon on the upper left of the Home page

From the Device Type pull down in Device Category Information locate and choose Server

Ignore Product Name and select New (SNMP) Fill in “Dell Server” or another name of your choice for Product

Name Select Get to the right of System Object Identifier

On the subsequent Get Device Response to this OID screen, enter the correct community name and IP address of the server previously configured in the Target IP. In this case it was showcase and 192.168.30.12. If this fails, refer to the Testing heading in Section 3.

Select Get Value, then Apply to return to Add New SNMP Category

In the URL Launch box enter “YourIm7Host/go-dell.asp?dst=$ipaddress”. YourIm7Host is the name or IP address of the server running Insight Manager 7. This will be explained in the next step.

On the “MIB Variable OID:” line select Get

On the subsequent Get SNMP Object Id panel, in the MIB Definition File pull down, locate and choose 10892.mib


In MIB Variable Name, pull down, locate, and select “systemManagementSoftwareName”

Select Get Object ID, then Apply which returns to the Add New SNMP panel

On the Object Value: box select Get

On the subsequent Get Device Response to this OID panel the target IP address and community string should still be filled in as showcase and 192.168.30.12

Select Get Value which should return “Server Administrator” in the Response box

Select Apply to return to Add New SNMP Category panel

The Data Type of String and Compare Rule of StartsWith should be fine so select Add

The result should be a popup saying “Rule created successfully”Before beginning the actual configuration of Insight Manager 7, it is necessary to add a page to the default IIS website. This is detailed in Figure 6 below, and is used to redirect the DTM Launch URL for this Device found on the device page to Server Administrator on the PowerEdge server.

Figure 6: go-dell.asp


<%@ LANGUAGE="VBSCRIPT" %><%' 4/19/2002 R. Foreman, Redirect Dell devices on Insight Manager 7 URL to Server Administrator ' Place go-dell.asp in Inetpub\wwwroot' invoke http://cimhostname/go-dell.asp?dst=$ipaddressIf Request.querystring("dst") = "" Then%> <HTML> <HEAD> <TITLE>Missing Dell Server Address</TITLE>

</HEAD><BODY> There was no Dell Server address specified when opening the go-dell.asp

page <P> Format should be go-dell.asp?dst=xx.xx.xx.xx or go-dell.asp?

dst=dellhostname </BODY></HTML><%Else dest = "https://" & Request.querystring("dst") & ":1311" Session("GoBack")=Request.ServerVariables("SCRIPT_NAME") Response.Redirectdest Response.endEnd if %>

There are two more things to check before Insight Manager 7 is ready to discover the Dell server: On the upper left select the Settings icon In the left hand navigation, select Discovery then Automatic

Discovery to display the Automatic Discovery panel

Make sure the Dell server is in the ping inclusion range of IP Address Ranges

Make sure the community name “showcase” that we used is listed in the SNMP Community String for Discovery.

Finally make sure that non-HP devices can be discovered

In the Status panel, select Enable

In the subsequent Discovery Filters panel, ensure the server box is checked and the HP & Compaq Manageable Devices Only box is Unchecked then Apply

If a new discovery is not initiated, then Execute Discovery NowWhen 100% complete in the Status panel, the Dell server should be recognized by Insight Manager 7. To verify, Select the Devices icon in the upper left In the left hand navigation, select Queries then Device

Select All Servers in Devices by TypeThere should now be entries called “Dell PowerEdge Server” under Product Name for the 1650. Clicking on the Device Name, such as SM1650B, brings up the Device page where the “DTM Launch URL for this Device” hyperlink should take you to the OpenManage Server Administrator login at https://192.168.30.18:1311 for managing the server.


https://192.168.30.18:1311/

Section 6Tailoring and Final Testing for Events

Of the information in the MIB files, the traps or error indications sent by Server Administrator are of primary interest to an administrator. These are the events that can be used to cause a notification such as an email or page. They have names like alertCoolingDeviceNormal with a text description, a severity, and a category. For the 10892 server MIB, there are only 36 traps and for arymgr there are only 80 server-related events. The default notification tasks within Insight Manager 7 are based on Severity with Informational Events being traps of Informational severity and Important events being those with critical, major, or minor. If those were the only notification tasks, then the next step would be a test as covered in the “Final Testing” section.It is possible to create a Personal Query that looks at the category as well as the severity. If specific queries have been created, then it is necessary to edit the 10892.rev and arymgr.rev files to map them into existing Insight Manager 7 categories. Previously, when the essential MIBS were uploaded and registered, they created new Categories of “Status Events”, “Error Events”, and “UNKNOWN”. These can be changed dynamically in the database with the Category tool. But given the number of traps, editing the REV file is faster and more reliable. The 10892.REV and arymgr.REV files were created when the respective MIBs were originally registered. They are located in the directory

\Program Files\Compaq\Compaq Insight Manager 7\Compaq\protocol\snmp\MIBS

and can be edited with Notepad or another editor, as they contain only text. Both of the Essential MIBs were modified and re-registered with the following steps: Use Notepad to edit arymgr.rev, changing “Status Events” and

Error Events” to “Storage” Use Notepad to edit 10892.rev changing UNKNOWN to

“Environmental” Save a copy of arymgr.rev and 10892.rev in a backup directory Select the Tools Icon in upper left Expand SNMP Extensions in left hand navigation pane Select MIB Registration in the left hand navigation pane Scroll down and select arymgr.mib in the “Registered MIBS” Select >>Unregister Check Create Logfile, Use Edit file, and Create


Select <<Register Repeat the steps for the 10892.mib entryThis procedure takes over two minutes, and only returns a message if there is an error. If so, then see the file:

\Program Files\Compaq\Compaq Insight Manager 7\log\10892.txt or arymgr.txt

Final TestingA complete end-to-end test can be performed by using OpenManage Server Administrator to change a threshold setting. Pulling a power cord or power supply can also generate an error event. Here are the steps used for this paper: Browse to Server Administrator at https://sm1650:1311 and login

with an account having administrator privileges Expand Main System Chassis in left hand navigation Select Voltages Select BP 3.3V in the action pane Select “Set to Values” then enter a Minimum Warning Threshold

value that is greater than the current “Reading” and Apply Changes. For example, a value of 3.26 can be entered for a reading of 3.249.

The status for the probe should then change from green check to a yellow warning symbol. An SNMP trap to the Insight Manager 7 server also will be generated

In Insight Manager 7, select Uncleared Minor Events in the icon bar

Select Server Voltage Warning to see the details of the trap

On Event: Severity select associated device, in this case sm1650 to go to the device page

Selecting DTM Launch URL for this Device should then be redirected by go-dell.asp to Server Administrator at https://sm1650:1311.

.


Section 6Results

This paper has shown how a Dell PowerEdge server can be integrated into an Insight Manager 7 environment following these basic steps:

Loading and configuring the Dell PowerEdge Server Recognizing the Dell PowerEdge Server in Insight Manager 7 Mapping the Dell Traps into alert actions in Insight Manager 7

The result was that an error such as a voltage warning or power failure could be received as a Minor Event that triggers an email or page action. Adding an in-context launch to Server Administrator from the device page further solidified the integration.Notifications of specific drive and memory module pre-failure alerts are also recognized as an indication of impending device failure. The full terms of when this can be used for service parts dispatch can be found at http://www.dell.com/us/en/gen/services/service_prefail_svc.htm

Limitations and Caveats:Finally, it is worth mentioning that the Hardware status in the device query will continue to show green until Insight Manager 7 loses communication (no ping response), when it will go red or critical. Also, as the PowerEdge server does not have the necessary software version agent, the SW status will always be blue for unknown. Similarly, the Management processor column will always be empty.Dell’s IT Assistant console provides the best manageability for Dell servers, including detailed status, inventory information, and Remote Access (out of band remote) launch. But the method of integration to Insight Manager 7 shown here does provide an adequate solution by extending the notification and alerting to Dell servers and allowing the in-context launch of Server Administrator for full server management.


http://www.dell.com/us/en/gen/services/service_prefail_svc.htm

Appendix AAppendix A – Dell MIBSEssential Server MIBS

MIB file Registration

Results

Comments

10892.mib OK Information including 36 traps from the server motherboard such as system type, voltages, temps, etc. It is the primary MIB for PowerEdge systems.

Arymgr.mib

OK with 3.2, edit

needed for 3.3

Provides detailed information about storage hardware components and RAID configurations monitored by the array Manager Agent. It provides 80 server related traps. For the OpenManage 3.3 version, the WARNING severity was changed for the following TRAP-TYPE:




AlertResumedCheckConsistency = INFORMATIONAL

Network Interface AdaptersMIB file Registrati

on Results

Comments

Adaptinof, BaspConfig, BaspStat, BaspTrap

OK Collectively provides detailed information about Broadcom Gigabit adapters such as embedded in PowerEdge 2650 models. It only provides one trap indicating teamed adapter fail-over.

Intel.mib OK Registering this MIB is a pre-requisite to both Intelnic.mib and Intel-LAN-Adapters-


MIB.mib

Intelnic.mib cannot find DMTF-DMI

Provides detailed information about the PRO 100+ Intel NIC adapter.

Intel-LAN-Adapters-MIB.mib

Cannot find SNMPV2-SMI-rfc2578

Provides detailed information but no traps for Intel PRO 100s, PRO 1000xt, PRO 100+ Dual Port, and PRO 1000F adapters.

Cnstattrap.mib

OK This provides one trap from the Broadcom CryptoNetX SSL accelerator adapter if present.

Other Adapters, Devices, and SoftwareMIB file Registrati

on Results

Comments

ClusterX.mib trap-type invalid severity

This is used when Cluster X software is installed to manage Microsoft clusters. The registration failure was an unrecognized severity which could be changed to one recognized by Insight Manager 7 as was done for arymgr.mib

DRAC2.mib Unexpected word in

macro

Provides detailed information about the components monitored by the DRAC II software agent available in some older PowerEdge Servers.

Sanappl OK This is used when monitoring a PowerVault 530F SAN Appliance. Four traps were registered.

Symmib.mib cannot find dmtf-dmi

Provides detailed information about the components monitored by LSI's Symbios agent. The Symbios agent monitors LSI/Symbios controllers and the devices connected to them on PowerEdge 8450 systems.

Legacy MIBSThe following MIBS are from earlier versions of OpenManage and would not be needed if the current version of Server Administrator is used throughout the environment.


MIB file Registration

Results

Comments

CIO400.mib OK Adaptec Comprehensive Input/Output. With OpenManage 3.3, arymgr.mib now has this information

AAC.mib OK Provides detailed information about the devices and configurations monitored by the now obsolete PERC 2 software agent.

Dellserv.mib cannot find dmtf-

dmi

Provides detailed information about the various hardware components monitored by the now obsolete HIP3.5.2 software agent.

PERC.mib trap-type invalid severity

Provides detailed information about SCSI storage hardware components and RAID configurations monitored by the PERC Console Package software agent. The PERC Console Package monitors the hard-disk drive subsystem(s) of servers installed with PERC, PERC 2/SC, and PERC 2/DC.

PowerNet.mib

trap-type invalid severity

Provides detailed information about the uninterrupted power supply (UPS) devices monitored by the Powerchute plus software agent.

THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND.

Dell, PowerEdge and OptiPlex are trademarks of Dell Computer Corporation. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. NetWare is a registered trademark of Novell. Linux is a registered trademark of Linus Torvalds. Insight Manager is a trademark of Hewlett- Packard. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others.

©Copyright 2003 Dell Computer Corporation. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Computer Corporation is strictly forbidden. For more information, contact Dell.

Information in this document is subject to change without notice.


integrating dell servers into an insight manager environment€¦ · web viewthe registration...

Documents