Owner's Manual

Issue 45: For agent based updates it is possible to have a successful update download task, but then to
have the actual update fail to install on the client. In this case the inventory report will correctly show
the older version of the update and the update will need to be re-applied.
Issue 46: When using online mode (ftp.dell.com), on few occasions the digital signature check for
downloaded updates could fail due to corrupted download. Re-run the stage and distribute task to
download the update again.
Event Console
Issue 47: Alert Initiated Discovery will not work for the PowerVault MD storage devices.
MD Array Traps are forwarded from the server where Dell PowerVault Modular Disk Storage Manager
application is installed and the Host IP address in the trap is the server's IP address instead of the MD
Storage Device. Alert Initiated discovery is run on the Host IP which in this case is the device that is
managing the MD Storage device.
Issue 48: Traps from some Dell printers such as model number 2330dn and 2145cn may not be categorized
properly in the Event Console. These models may not support the standard printer MIB (RFC 3805) for trap
classification. Such traps will be received by the Event Console but displayed as Unknown Event Name,
Unknown Event Category and Undetermined severity.
Resolution: You can perform all actions, such as Resolve, Acknowledge, and View Details that can be
performed on other recognized alerts. The difference between recognized and unrecognized traps is that
Name, Category, and Severity do not display the proper values.
Issue 49: Traps may not be received when both IT Assistant and Dell Management Console are installed on
the same management station. To correct this behavior, restart the Altiris Event Engine and Altiris Event
Receiver services.
Issue 50: Traps received from a managed node server having Red Hat Enterprise Linux 4 (Update:7) (x86 or
64) installed on it, will show 0 as Trap Description in Event Console. This issue is caused by a net-snmp
bug introduced in Red Hat Enterprise Linux 4 (Update:7) operating system and not specific to Dell
Management Console. Install the below mentioned rpms on the managed node to fix this issue:
net-snmp-utils-5.1.2-13.el4_7.3.x86_64.rpm
net-snmp-libs-5.1.2-13.el4_7.3.x86_64.rpm and
net-snmp-5.1.2-13.el4_7.3.x86_64.rpm
Issue 51: Purge policy will not purge events required for maintaining the device state. If you have large
number of alerts it could cause latency in the Console.
Resolution: You can clear out the alerts manually in SQL Management Studio by deleting the alert entries
in EC_Alerts table and delete the rulestate file located under [DMC_INSTALL_DIR]\Altiris Agent\Monitor
Agent. However this will clear all device health until the next device health poll (default: every 1 hour).
Monitoring
Issue 52: Alerts sent from some versions of the PowerVault MD Storage Management Software for the
MD3000 family of devices will not be associated with the MD device in Dell Management Console.
As a result, OnDemand polling for the MD Array will not be triggered. An alert will be generated on the
next scheduled health polling cycle if the device state has changed. Reduce the polling interval for the
primary health metric if you require more timely updates. Changing the interval will also affect other
devices.
Issue 53: To create Customer filter for the Monitoring policies & metrics, it is required that you create the
filter from the Dell Management Console Portal -> "Group View - Aggregate Health by Dell Resource" web
part by launching the "Configure" dialog box. Save this newly defined custom filter and select the same in