This readme file contains updated information for your "HP OpenView
Network Node Manager Special Edition 1.5.2 User's Guide" and "Dell
OpenManage HIP 3.5.2 User's Guide" and any other technical
documentation included with these products.
Always refer to the Dell World Wide Web site (http://www.dell.com)
for the most current information.
The following sections contain updated requirements, features,
resolved issues, and open issues for the Dell OpenManage(TM)
Hardware Instrumentation Package (HIP) 3.5.2.
######################################################################
HP OPENVIEW NETWORK NODE MANAGER SPECIAL EDITION (NNM SE) 1.5.2 WITH
DELL OPENMANAGE HIP 3.5.2
######################################################################
------------
REQUIREMENTS
------------
Supported systems: Dell(TM) PowerEdge(TM) 1300, 2200, 2300,
2400, 2450, 4200, 4300, 4350, 4400, 6100,
6300, 6350, 8450
Version: 3.5.2
Release date: January 2000
Operating systems: Microsoft® Windows NT® 4.0 with SP3
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
Microsoft Windows 2000 - Tested with RC3.
Managed Node Only.
DMI to SNMP Mapping
is not supported for
any components.
Your Dell PowerEdge system requires the following basic input/output
system (BIOS) version and, where noted, embedded server management
(ESM) firmware version to run the Dell OpenManage HIP version 3.5.2:
PowerEdge 1300 - BIOS A01 or later
PowerEdge 2200 - BIOS A04 or later
PowerEdge 2300 - BIOS A05 or later and ESM 3.14 or later
PowerEdge 2400 - BIOS A01 or later
PowerEdge 2450 - BIOS A01 or later
PowerEdge 4200 - BIOS A01 or later
PowerEdge 4300 - BIOS A02 and ESM 3.18 or later
PowerEdge 4350 - BIOS A01 or later
PowerEdge 4400 - BIOS A00 or later
PowerEdge 6100 - BIOS A04 or later
PowerEdge 6300 - BIOS A03 and ESM 3.17 or later
PowerEdge 6350 - BIOS A05 or later
PowerEdge 8450 - BIOS A00 or later
Dell OpenManage Remote Assistant Card (DRAC) 2 - firmware version 2.x
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 versions and update instructions are available
for all Dell PowerEdge systems on the Dell World Wide Web site at
http://support.dell.com.
Your Dell PowerEdge Expandable RAID Controller (PERC) 2/SC requires
the following versions of the PowerEdge device drivers (available
from Dell) to manage the PowerVault(TM) 2xxS storage system:
NOTE: The reference to PowerVault 2xxS storage systems includes
the following PowerVault systems: 200S, 201S, 210S, and 211S.
Windows NT: pedge.sys Version 2.19
NetWare: pedge4xx.ham Version 1.47
--------
Features
--------
New Hardware Support
* Dell PowerEdge 2450
New Software Support
* Drac 2.2.1
---------------
RESOLVED ISSUES
---------------
Duplicate storage system entries displayed in Server Console
In situations involving multiple storage systems daisy chained
together via an SMB cable, a duplicate storage system entry may result
in the Server Console if one of the cables is disconnected before
opening a Server Console session and is reconnected while the Server
Console session is open.
This problem can be resolved by closing and reopening the Server
Console.
-----------
OPEN ISSUES
-----------
HP OpenView Y2K Guideline
HP OpenView's processes are time sensitive and were not designed
to handle time gaps of one year. You can advance the system clock
by months, but not by one year.
This issue is not a year 2000 problem. For example, if you advance
the date from 1998 to 1999, an error occurs. Stop HP OpenView's
processes before advancing the clock ahead by one year. If you are
going to advance the system clock by one year during your year 2000
testing, perform the following steps:
1. Close HP OpenView.
2. Run "ovstop" from the command line.
3. Advance your system clock one year.
4. Run "ovstart" from the command line.
5. Continue your year 2000 testing.
Descriptions of test scenarios that HP has performed on HP OpenView
to certify it as year 2000-compliant are available on their Web site
at http://www.hp.com/year2000.
=====================================================================
Version number in Netware system:
In NetWare systems, the version number is shown as 3.51 even though
the version number in Windows NT is displayed as 3.5.1
=====================================================================
Conflicting host and computer names cause a failure of management
station installation.
During the installation of Management Station, the following error
may occur:
Setup determined that your machine and the domain name server may
not agree on your IP hostname. Please check your settings in the
Control Panel -- Network applet. Setup will now exit.
This issue may be resolved by editing the local machine's host file
to match the hostname found in the network database.
======================================================================
Error message ISSET_SE during management station installation
After executing the management station setup program, you may see
an error message box (titled ISSET_SE) with the following message:
--------------------------------------------------------------
An error has occurred in your application.
If you choose Ignore, you should save your work in a new file.
If you choose close, your application will terminate.
--------------------------------------------------------------
This is an InstallShield issue. There seems to
be no effect as a result of this error message. Choose "ignore"
and continue with the install.
======================================================================
FAST support/compatibility:
This version of HP OpenView Network Node Manager Special Edition
provides for PERC 2 and PERC 2/Si management using FAST version 2.1
along with version 2.1 agents. Not all implementations of PERC 2
are supported with this package. Specifically, this package can
only manage remotely installed PERC 2 version 1.1 controllers.
A local PERC 2 version 1.1 controller will not work properly with this
version of FAST and its agents. Refer to the following table:
FAST Version Controller Compatibility
2.1 PERC 2 version 1.1 - remote only
PERC 2/Si version 2.1 - local and remote
1.1 PERC 2 version 1.1 - local and remote
FAST and its agents at version 2.1 must not be installed on a machine
running PERC 2 firmware and driver version 1.1. A 2.1 version of the
PERC 2 firmware and associated driver are not available at this time.
======================================================================
Intel NIC DMI to SNMP mapping on Windows 2000 not supported
After the Intel Client Instrumentation for the NIC is installed on a
Windows 2000 operating system, and the system is rebooted, the following
error message will be displayed:
"The Intel Client Instrumentation for DMI and SNMP service hung on
starting."
The DMI to SNMP mapping for the Intel NIC instrumentation will not be
supported and will display the above error message on each reboot.
This issue is due to a limitation of the DMI to SNMP mapper when running on
a Windows 2000 system.
======================================================================
Dell Baseboard agent fails to start after install on a PowerEdge 8450
runnning Windows 2000
If the Dell Baseboard agent fails to start after installing the managed
node a PowerEdge 8450 running Windows 2000, reboot the system and the
Dell Baseboard agent will start normally. The Baseboard agent will
start normally on subsequent reboots.
======================================================================
Incorrect Memory Display (problem seen from Dell OpenManage IT
Assistant)
Because of a software limitation, systems with over 2 GB of memory may
incorrectly report the size of the system memory. Individual memory
devices continue to function properly. This problem does not degrade
error checking and correcting memory (ECC) protection or performance.
======================================================================
Dell OpenManage Client Incompatibilities
This product (NNM SE Components) allows for the installation of the
Dell OpenManage Client (DOMC) application version 4.2. When the
Management Station is installed, the DOMC is installed automatically.
If the DOMC is used to manage clients with client instrumentation
newer than version 4.2, there may be incompatibility problems. If
problems occur, Dell recommends that you use Dell OpenManage
IT Assistant as the management application for the client systems.
======================================================================
PERC Console Applications prior to NNM SE 1.5. Will Not Recognize
PERC Instrumentation Included with NNM SE 1.5.2
Attempting to view NNM SE 1.5.2 PERC instrumentation from a PERC
console application prior to 1.5 will generate the following error
message:
Cannot connect server
One Instance of PERC console
or Remote Client may be Running.
======================================================================
Object Identification Change Prevents Management Stations Prior to
NNM SE 1.5 from Discovering PERC Agents included with NNM SE 1.5.2
Due to a PERC Object Identification Definition (OID) change,
management stations prior to NNM SE 1.5 cannot discover PERC agents
included with NNM SE 1.5.2. NNM SE 1.5.2 management stations can still
recognize PERC traps from NNM SE 1.4 or later.
Management stations prior to NNM SE 1.5.1 are unable to display
Dell PowerEdge Expandable RAID Controller icons for any servers that
are using PERC instrumentation included with the NNM SE 1.5.1 release.
======================================================================
Managing Managed Nodes With PERC Instrumentation Prior to Dell HIP
1.5 From a 1.5.2 Management Station
When managing managed nodes with PERC instrumentation prior to Dell
HIP 1.5 from an HIP 1.5.2 management station, you can no longer:
* Configure RAIDs on managed nodes with Dell HIP 1.4. (You can
only view configurations.)
* Walk through the "perc.mib" file from the management station.
(This is because of an SNMP object ID (OID) change to avoid
conflicts with other software.)
To regain the ability to walk through the "perc.mib" file from the
management station, you can unload the NNM SE 1.5.2 "perc.mib" file
and load the NNM SE 1.4 "perc.mib" file in its place. Perform the
following steps:
1. Run the xnmloadmib program on the management station.
2. Unload the "perc.mib" file.
3. Load the earlier "perc.mib" file from the directory where you
put it.
NOTE: When the NNM SE 1.4 "perc.mib" file is loaded, you will not be
able to browse the "perc.mib" file on HIP 1.5.2 managed nodes.
======================================================================
PERC Security Page GUI Password
To view and/or configure a server's RAID controller, you
must first select the access mode that will be used for the current
session. To configure a RAID controller, you must choose the full
access mode and supply a password. The default password is PERCRAID
(case sensitive). You can change the full access password by
running the SetPass.exe utility located under program files\dell\perc
\inst\rserver.
======================================================================
Adaptec CI/O Install Cannot Accept a Directory Pathname Longer Than
57 Characters
If you plan to install Adaptec CI/O Management Software during
installation of HP OpenView NNM SE with Dell OpenManage HIP, ensure
that the install directory pathname does not exceed 57 characters.
======================================================================
Adaptec CI/O I/O Manager Module for NetWare Fails to Unload
The Adaptec CI/O I/O manager module for NetWare may fail to unload,
causing the following symptoms:
* The system hangs during the NetWare boot. (This happens
intermittently.)
* The system boots, but the Adaptec CI/O Management Software cannot
manage this node for the SCSI controller and the devices connected
to the controller.
* The system responds very slowly. For example, if you type
something on the console, the text appears after a significant
delay.
There is no resolution at this time.
======================================================================
Adaptec CI/O NLMs Cause Higher CPU Use
Adaptec CI/O NetWare Loadable Modules (NLMs) cause higher CPU use,
which results in degraded system performance. The Adaptec CI/O
periodically polls all devices on the SCSI bus, which can take a few
seconds to a few minutes. For example, if the data file says that a
device had existed at an ID but had failed or was removed, Adaptec
CI/O waits for the SCSI request to time out before going to the next
ID. During this poll process, the CPU use is higher than in a wait
state.
There is no resolution at this time.
======================================================================
APC PowerChute Plus Error Message: Attempt to Modify NDS Object
When you are running American Power Conversion (APC) PowerChute plus
version 4.3 for NetWare with either NetWare version 5.0 or NetWare
version 4.11 with Support Pack 6, PowerChute plus generates the
following message when it loads the "pwrchute.nlm" file:
Attempt to Modify NDS Object
The PowerChute plus "pwrchute.nlm" file is not linking to the
uninterruptible power supply (UPS) object.
To solve this problem, download and install PowerChute plus version
4.33 for NetWare from the APC Web site.
If the problem is not resolved, perform the following steps:
1. Verify that you loaded the correct "pwrchute.nlm." (You may have
installed PowerChute plus version 4.33 but did not delete the
4.30 version of "pwrchute.nlm," which still loads when you boot
the system.)
a. At the server console, type "modules pwrchute" to determine
which version of "pwrchute.nlm" is loaded.
b. If version 4.30 is loaded, unload and delete it; then load the
4.33 version of "pwrchute.nlm."
2. If "pwrchute.nlm" version 4.33 is loaded and you continue to get
the error message, you have a synchronization error.
For the two types of synchronization errors, perform the following
steps:
* Time Synchronization Errors
1. At the server console, type "load time" to echo back any time
synchronization errors.
2. If a time synchronization error exists, APC recommends that you
call Novell Technical Support for assistance.
* NetWare Directory Service (NDS) Synchronization Errors
1. Open "NDS Manager," which should be located in the "Public"
directory.
2. Right-click the partition on which the affected server resides.
Perform the following steps for each of the three areas where
errors may occur:
* From the pull-down menu, click "Check Synchronization." If all
entries are "processed = Yes," click "Continuity." When the
"Partition Continuity" screen appears, right-click the
affected server and click "Information." If the "Current
Sync Errors" check box has errors, an NDS error has occurred.
* From the pull-down menu, choose "Check Synchronization." If
all entries are "processed = No," an NDS error has occurred.
* If the affected server has an exclamation point next to it,
an NDS error has occurred.
3. If any of these NDS errors appear, run "DSRepair." For assistance
running "DSRepair," APC recommends that you call Novell Technical
Support.
======================================================================
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 PERC running firmware Uc77 or later,
PERC 2/SC adapters running firmware ED4D or later, and drives that
support Mode 6.
For a PERC firmware update, see http://support.dell.com.
======================================================================
Intel® LDSM 2.52 With Dell OpenManage HIP 2.2
During 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 HP OpenView map
after the HIP 2.2 installation is completed. HP OpenView will then
rediscover the node as an 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 management information base (MIB) is 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 NETWORK NODE MANAGER SPECIAL EDITION (NNM SE) 1.4 WITH
DELL OPENMANAGE HIP 3.4.1
######################################################################
--------
Features
--------
* Updates to Microsoft Windows NT and Novell NetWare Simple
Network Management Protocol (SNMP) Agents for the Dell PowerEdge
Expandable RAID Controller (PERC). These updated SNMP agents
support enhanced RAID Controller security.
* An update to the PERC console application for enhanced security.
* An update that allows installation of the HP OpenView remote
console on non-Dell systems.
* An update that allows installation of Dell console plug-ins on
non-Dell systems.
* An update that allows installation of a managed node without
checking video resolution.
* An update that displays proper HP OpenView trap information for
power-supply failure conditions.
######################################################################
HP OPENVIEW NETWORK NODE MANAGER SPECIAL EDITION (NNM SE) 1.4 WITH
DELL OPENMANAGE HIP 3.4
######################################################################
--------
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 PERC 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 2xxS Monitoring
If you are connected to a PowerVault 2xxS storage system, you must
install Adaptec CI/O Management instrumentation on the managed node.
The PowerVault 2xxS 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 2xxS.
######################################################################
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 2xxS storage
system
New Software Features
* Support for monitoring up to eight PowerVault 2xxS 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) 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 1999
Download 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.