This readme file contains updated information for your "HP OpenView Network Node Manager Special Edition 1.4 With Dell OpenManage(TM) HIP 3.4 User's Guide" and any other technical documentation included with this product. Always refer to the Dell World Wide Web site (http://www.dell.com) for the most current information. The following sections contain update requirements, features, technical updates, and open issues for the Dell OpenManage Hardware Instrumentation Package (HIP) 3.4. ###################################################################### HP OPENVIEW NETWORK NODE MANAGER SPECIAL EDITION (NNM SE) 1.4 WITH DELL OPENMANAGE HIP 3.4 ###################################################################### ------------ REQUIREMENTS ------------ Supported systems: Dell(TM) PowerEdge(TM) 1300, 2200, 2300, 4200, 4300, 4350, 6100, 6300, 6350 Version: 3.4 Release date: December 1998 Operating systems: Microsoft® Windows NT® 4.0 with Service Pack 3 or later (for clusters, the management station and the managed node must have the same Service Pack) Novell® NetWare® 4.11 with Support Pack 5 or later Novell NetWare 5.0 Your Dell PowerEdge system requires the following basic input/output system (BIOS) revision and, where noted, embedded server management (ESM) firmware revision to run the Dell OpenManage HIP version 3.4: PowerEdge 1300 - BIOS A01 PowerEdge 2200 - BIOS A04 PowerEdge 2300 - BIOS A05 or later and ESM 3.14 or later PowerEdge 4200 - BIOS A01 PowerEdge 4300 - BIOS A02 and ESM 3.18 or later PowerEdge 4350 - BIOS A01 PowerEdge 6100 - BIOS A04 PowerEdge 6300 - BIOS A03 and ESM 3.17 or later PowerEdge 6350 - BIOS A05 Dell Remote Assistant Card (DRAC) 2 - firmware version 2.0 Check your system's BIOS or system management firmware version during the boot routine. If the version is not at the required level, you must update it to the correct version. Flash BIOS and system management firmware revisions and update instructions are available for all Dell PowerEdge systems on the Dell World Wide Web site at http://www.dell.com/support. Your Dell PowerEdge Expandable RAID Controller 2/SC requires the following versions of the PowerEdge device drivers (available from Dell) to manage the PowerVault(TM) 20xS storage system: Windows NT: PEDGE.SYS Version 2.19 NetWare: PEDGE4xx.HAM Version 1.47 -------- Features -------- New Hardware Support * Dell PowerEdge 1300 * Dell PowerEdge 4350 New Software Support * Support for DRAC 2 on Dell PowerEdge 1300, 4350 systems * Support for Adaptec Comprehensive Input/Output (CI/O) Management Software 4.0 * Support of the Flexible Array Storage Tool (FAST) Console for Dell PowerEdge Expandable RAID Controller 2 ----------------- TECHNICAL UPDATES ----------------- Replacing Faulty Memory After replacing a memory module, the memory icon remains yellow. To clear the prefailure condition, log into the Dell OpenManage Server Console and select the memory in question. Under "Actions" select "Clear Memory Error" and select "Yes." The icon turns green. PowerVault 20xS Monitoring If you are connected to a PowerVault 20xS storage system, you must install Adaptec CI/O Management instrumentation on the managed node. The PowerVault 20xS is monitored by the PowerEdge server that has a SCSI connection to the PowerVault's primary SCSI connector. A PowerEdge server that is connected to the PowerVault's secondary SCSI connector will not monitor the PowerVault 20xS. ----------- OPEN ISSUES ----------- SMART Reporting in Dell PowerEdge Expandable RAID Console Application Program The Dell PowerEdge Expandable RAID console application program supports Self-Monitoring Analysis and Reporting Technology (SMART) predictive failures only on the PowerEdge Expandable RAID Controller running firmware Uc77 or later, PowerEdge Expandable RAID Controller 2/SC adapters running firmware ED4D or later, and drives that support Mode 6. For a PowerEdge Expandable RAID Controller firmware update, see http://www.dell.com. ====================================================================== Intel® LDSM 2.52 With Dell OpenManage HIP 2.2 During the installation of the Intel LANDesk® Server Manager (LDSM) console on a server with the NNM SE console previously installed, the following error message appears: Setup was unable to shut down the SNMP service because there are other services running that depend on the SNMP service. Setup cannot guarantee your installation will complete successfully if the SNMP service is running. LDSM is installed correctly despite this warning. ====================================================================== Intel LDSM Conflicts Installation of the LDSM managed node is not supported on a system with HP OpenView NNM SE installed. When using the Server Console for a managed node with LDSM installed, you cannot log in and modify settings. ====================================================================== Installing Dell OpenManage HIP 2.2 Agents on a System With Previously Installed HIP 3.x Agents If a managed node is downgraded from the HIP 3.x agents to HIP 2.2 agents, the node must be manually deleted from the OpenView map after the HIP 2.2 installation is completed. OpenView will then rediscover the node as a HIP 2.2 agent. Failure to manually delete the node may prevent the Server Console from correctly recognizing the managed node as a Dell server. ====================================================================== Transferring MIF Data to SMS Some management information format (MIF) data may be transferred incorrectly to the Systems Management Server (SMS) from the Dell Baseboard MIF (BASEBRDD.MIF) file. This problem occurs only for data with multiple keys. For the BASEBRDD.MIF, this problem affects all data in the fan, temperature, voltage, current, power supply, and chassis extension groups. ====================================================================== Node Labeled Incorrectly in Topology Map With HP OpenView NNM, a node may be labeled with an incorrect name in the topology map when Microsoft Cluster Server (MSCS) clusters on the networks are being discovered by the NNM. The nodes that may be incorrectly labeled are part of the cluster itself. The incorrect label will be the name associated with an Internet Protocol (IP) address that is a resource in the cluster. For example, if you have a two-node MSCS cluster named "CLUSTER" with member nodes "MEMBER1" and "MEMBER2," the node icons associated with "MEMBER1" and "MEMBER2" may be labeled with the name "CLUSTER." ====================================================================== Loading MIBs Into SNMP Management Console The Dell MIB is Simple Network Management Protocol (SNMP) version 2-compliant. Some SNMP management consoles only support SNMP version 1 and may not load the Dell MIB properly. ====================================================================== Coexistence of NNM SE and Dell OpenManage Administrator HP OpenView NNM SE will not coexist with Dell OpenManage Client Administrator. The Dell OpenManage Client Administrator should not be installed on the same system as the HP OpenView NNM SE management station or remote console. ====================================================================== Using the HP OpenView MIB Browser With Dell OpenManage HIP 3.3 or Later Dell HIP 3.3 or later provides instrumentation for a new MIB that occupies a different part of the MIB tree than previous versions of HIP. When using the MIB browser on HIP 3.2 and earlier, use the ".iso.org.dod.internet.private.enterprises.dell.server" branch under the Dell enterprise. When using the MIB browser on HIP 3.3 or later, use the ".iso.org.dod.internet.private.enterprises.dell.server2" branch. If you browse the Dell MIBs using the wrong branch of the MIB against a given version of the Dell HIP, you may see errors such as: Error: SNMP: A general failure occurred on the agent. Also, in general, alert tables, event generation tables, and trap tables cannot be browsed. ====================================================================== Duplicate Traps Posted in the HP OpenView Event Browser A single event could appear multiple times in the HP OpenView Event Browser. This results from a timing issue between the "NNM DMI Discovery" and the "DMI2SNMP" mapper on a managed node. The timing issue is resolved when "NNM DMI Discovery" updates its information as a result of configuration polls. The following entries provide historical information about previous versions. ###################################################################### HP OPENVIEW NNM SE 1.3 WITH DELL OPENMANAGE HIP 3.3.1 ###################################################################### -------- FEATURES -------- New Hardware Support * Updated SNMP Agents for Microsoft Windows NT and Novell NetWare operating systems for the Dell PowerEdge Expandable RAID Controller 2/SC to support the Dell PowerVault 20xS storage system New Software Features * Support for monitoring up to eight PowerVault 20xS chassis, including temperature, fan speed, and power-supply status through either a Dell PowerEdge Expandable RAID Controller 2/SC or an Adaptec 2940U2W controller --------------- RESOLVED ISSUES --------------- Fan Enclosure Removal Status When the fan enclosure is removed from a PowerEdge 6350 or a PowerEdge 4350, the removal status is reflected in the top-level fan icon within the Dell OpenManage Server Console. Memory Prefailure Detection With memory prefailure detection, the memory icon turns yellow when the memory is about to fail. When the memory fails, the icon turns red, indicating a more serious or immediate problem. Rebooting the machine turns the icon yellow again, unless more errors are detected by the hardware. The "memory prefailure detected" configurable action only occurs when the memory switches from a non-prefailure condition (green) to a prefailure (yellow) or failure (red) condition. ###################################################################### HP OPENVIEW NNM SE 1.3 WITH DELL OPENMANAGE HIP 3.3 ###################################################################### -------- FEATURES -------- New Hardware Support * Dell PowerEdge 4300 * Dell PowerEdge 6350 * Dell PowerEdge Expandable RAID Controller 2 with FAST console New Software Features * Thermal shutdown for temperature and fan removal events * Novell NetWare Desktop Management Interface (DMI) 2.0 support * Logging of events within NetWare * Configurable timer for hung server detection and reboot * Standard Desktop Management Task Force (DMTF) DMI-to-SNMP mapping * Enhanced discovery of DRAC 2 network connections * Ability to install management application programs without installing HP OpenView NNM SE * Discovery of clustered systems * Support for more than a single read-only remote console for NNM SE * Ability to install NNM SE management station on any Dell system * Support for simultaneous remote and local consoles for NNM SE --------------- RESOLVED ISSUES --------------- * Installation of Microsoft Windows NT Server Terminal Server Edition (TSE) * Support for a fully qualified network host name longer than 25 characters for the PowerEdge Expandable RAID console application program * Support for management of Adaptec Duralink network interface controllers (NICs) on systems that contain the NNM SE management station ====================================================================== Information in this document is subject to change without notice. (C) 1998-1999 Dell Computer Corporation. All rights reserved. Trademarks used in this text: "Dell," "PowerEdge," "Dell OpenManage," and "PowerVault" are trademarks of Dell Computer Corporation; "Microsoft" and "Windows NT" are registered trademarks of Microsoft Corporation; "Novell" and "NetWare" are registered trademarks of Novell, Inc.; "Intel" and "LANDesk" are registered trademarks of Intel Corporation. This software and documentation are based in part on OpenView under license from Hewlett-Packard Company. 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 Computer Corporation disclaims any proprietary interest in trademarks and trade names other than its own. December 1998Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.