Table Of Contents
Release Notes for Device Fault Manager 2.0.3 on Solaris
Known Problems Inherited from DFM 2.0
Problems Resolved in DFM 2.0.3
Problem Resolutions Inherited from DFM 2.0 Service Pack 2
Problem Resolutions Inherited from DFM 2.0 Service Pack 1
Problem Resolutions Inherited from DFM 2.0
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Device Fault Manager 2.0.3 on Solaris
Revised: 3 October 2006
These release notes are for use with Device Fault Manager (DFM) 2.0.3 running on a Solaris platform. Supported Solaris versions are Solaris 8 (Solaris 2.8) or Solaris 9 (Solaris 2.9).
Refer to the installation guides for software and hardware installation details.
These release notes provide the following information:
•
Additional Information Online
•
•
•
New Features
DFM 2.0.3 contains the following features.
New Features
DFM 2.0.3 contains all of the features that were introduced in DFM 2.0, which are described in the User Guide for Device Fault Manager (see Product Documentation).
Resolved Problems
In addition to all bug fixes provided through DFM 2.0 Service Pack 2, DFM 2.0.3 contains many new bug resolutions. A complete list of resolved problems is provided in Resolved Problems.
Device Support
DFM 2.0.3 contains all device support provided through DFM 2.0 Service Pack 2. In addition, it contains support for the following devices:
•
•
For a complete list of supported devices, see Supported Devices for Device Fault Manager 2.0.3 (refer to Product Documentation).
Product Documentation
Note
Table 1 describes the product documentation that is available.
Table 1 Product Documentation
Release Notes for Device Fault Manager 2.0.3 on Solaris
•
•
Installation and Setup Guide for Device Fault Manager 2.0.3 on Solaris
•
•
•
User Guide for Device Fault Manager, Software Release 2.0.3
•
•
•
Supported Devices for Device Fault Manager 2.0.3
On Cisco.com at http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_device_support_tables_list.html
Status of DFM Device Agent Bugs (DFM 1.x and DFM 2.x)
On Cisco.com at http://www.cisco.com/en/US/products/sw/cscowork/ps2421/prod_release_notes_list.html
Context-sensitive online help
•
•
Related Documentation
Note
Table 2 describes the additional documentation that is available.
Table 2 Related Documentation
Quick Start Guide for LAN Management Solution 2.5.1
•
•
Data Migration Guide for LAN Management Solution 2.5.1
•
•
Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView) on Solaris
•
•
Installation and Setup Guide for Common Services 3.0.3 (Includes CiscoView) on Solaris
•
•
•
User Guide for CiscoWorks Common Services 3.0.3
•
•
•
1 See Obtaining Documentation.
Additional Information Online
Service packs (formerly called incremental device updates or IDUs) contain the updated files necessary for the latest device support and fixes to known problems that are not available in DFM 2.0. If you are a registered user, you can download service packs for DFM from:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-dfm
To determine which packages are installed on your CiscoWorks Server, from the Common Services home page, select Software Center > Software Updates.
You can also obtain any published patches from the download site.
Known Problems
Refer to these sections for information on known and resolved problems in this release:
•
For information on DFM bugs that result from device bugs, see Status of DFM Device Agent Bugs at http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dev_sup/index.htm.
Note
Known Problems in DFM 2.0.3
Table 8 lists all problems that are specific to DFM 2.0.3. Note that known bugs from DFM 2.x service packs have been rolled in to this release.
Table 3 Known Problems in DFM 2.0.3
CSCsc68174
Local upgrade from LMS 2.5 LMS 2.5.1 should remove jar files from old image
After performing a local upgrade to LMS 2.5.1 from LMS 2.5 (in other words, an upgrade from DFM 2.0), the DFM 2.0.3 image contains some jar files that should be removed. If not removed, these files may cause random problems when DFM Group Administration is used.
The workaround is as follows:
1.
2.
cogs1.3.jar
ogs-client1.3.jar
ogs-server1.3.jar
ogs-sharedasa1.3.jar
ogs-sharedgroup1.3.jar
ogs-sqlasa1.3.jar
ogs-testasa1.3.jar
ogs-util1.3.jar3.
CSCsa31846
Cannot resize Detailed Device View columns
Several columns in the DFM 2.x Detailed Device View are difficult to read because they are narrow and cannot be resized. There is currently no workaround.
CSCsa49471
Cannot configure user messages for the ciscoEpmNotificationAlarm
DFM CISCO-EPM-NOTIFICATION-MIB traps contain three user message fields: cenUserMessage1, cenUserMessage2, cenUserMessage3. However, the varbinds values are set to um1, um2, and um3, respectively, and cannot be reconfigured. There is no workaround.
CSCsb04678
DFM 2.0 displays bogus device info for selected alerts
When a user clicks an Alert ID for a given device, sometimes DFM occasionally displays alerts that are for different devices. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb04914
DFM helpdesk user should not be able to manage/unmanage devices and interfaces
A user with the helpdesk role can manage and unmanage devices and interfaces (from either the Detailed Device View or by editing polling parameters from Configuration > Polling Parameters). A helpdesk user should not have this privilege. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb05350
Cannot customize e-mail notification subject
Users cannot customize the subject of e-mail notifications. There is currently no workaround.
CSCsb82140
DFM does not handle ifOperStatus values correctly
DFM is capable of handling ifOperStatus values up(1) and down(2), but it does not recognize the dormant state. There is currently no workaround.
CSCsa48916
AA Detail page only refreshes events when they clear or recur
The Alerts and Activities Detail page only refreshes an event's status when the event is cleared, or when the event surpasses a threshold. However, even if the event repeatedly surpasses the threshold, DFM does not refresh the value. There is currently no workaround.
CSCsb38137
DFM 2.x discovery may hang (in Learning state) indefinitely
DFM 2.x discovery may hang (in Learning state). The conditions are unknown. This bug is under investigation. There is currently no workaround.
CSCsb82889
DFM does not generate alerts when another application subsequently takes port 162
If DFM is listening for traps at port 162, and another application subsequently takes that port, DFM will not receive any traps nor will it generate alerts.
The workaround is as follows:
1.
2.
3.
CSCsb87408
If an interface goes down, DFM generates two interface Unresponsive events
When a device interface goes down, DFM generates two interface Unresponsive events for the same interface. This happens because DFM generates one event for the interface and another event for the underlying SNMP object. No workaround is currently available. Ignore the duplicate event.
CSCsc38566
DFM should not create virtual interface objects
DFM creates objects for virtual interfaces, but it should not. This is problematic for networks containing routers that have large numbers of virtual interfaces (because the objects, which contain little information, use system resources and discovery time). This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb96943
In device name, dot is missing between name and domain
After importing devices from the DCR to DFM, a device may occasionally go to the Questioned state because the dot in the device name (between the name and domain) disappears. The name may be displayed correctly in the DCR. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc13884
Device Selector page gives JSP error after upgrade from DFM 2.0 to DFM 2.0.3
After upgrading DFM 2.0 to DFM 2.0.3 (using the CD), if the user selects Device Management > Device Selector, the page occasionally displays a JSP error. This was observed on one machine. There is currently no workaround.
CSCsc41746
Intermittent problems when editing DFM user-defined groups
Occasionally, a user will not be able to edit user-defined groups. This happens intermittently. The workaround is to restart the daemon manager.
CSCsc44902
DFM devices are deleted when restricted license number exceeded
When more than 300 devices are added to a DFM server running with a restricted license, all devices are deleted from DFM. After some time, some of the devices may be automatically re-added. There is no workaround.
CSCsc46279
Solaris: Local upgrade hangs because sm_server is not registered with broker
When upgrading LMS 2.2 to LMS 2.5.1 on Solaris, a local upgrade may intermittently fail during the migration phase. This is because the sm_server does not register with the DFM broker. The workaround is to stop the sm_server and brstart processes using kill -9.
CSCsc60557
Local upgrade to DFM 2.0.3 proceeds without running required migration script
When performing a local upgrade from DFM 1.2.x to DFM 2.0.3, the upgrade sometimes proceeds without running the required migration script. The workaround is as follows:
1.
2.
CSCsc61715
Device Selector page gives DCRAdapter.log error after upgrade from DFM 1.2.x to DFM 2.0.3
After upgrading DFM 1.2.x to DFM 2.0.3, if the user selects Device Management > Device Selector, the page intermittently displays the following message:
An exception has occurred. Please check the DCRAdapter.log file.The workaround is as follows:
1.
2.
3.
CSCsa79086
Cannot create MSFC user-defined or customizable groups
DFM users cannot create user-defined or customizable groups for MSFCs. This is because the Group Administration user interface does not list the MSFCs in the Objects Matching Membership Criteria list, even though the MSFCs match the rule. As a result, the user cannot adjust polling and threshold settings or priorities for MSFCs. There is no workaround.
CSCsb36438
LMS 2.5 may not work properly with HP NIC-Teaming environment
If DFM is running on a server with multihomed HP NIC-Teaming (fail-on-fault) environment, devices in the DFM inventory are listed as Unresponsive. This was observed on a Windows server. The workaround is to disable NIC-Teaming, and then reinstall Common Services, DFM, and any other required LAN Management Solution applications.
CSCsa58553
Fault History search screens are nonintuitive and may not work properly
Fault History screens have the following limitations:
•
•
To find a device with an unknown name, use the Search by Group page, which provides a device object selector.
To find relevant event or alert IDs, start the Alerts and Activities display, and locate the event or alert ID for which you want to search. Use that ID in the Fault History search field.
CSCsb48643
Cannot disable ICMP polling in DFM
DFM 2.x does not allow users to disable ICMP polling so software can function across a firewall. (Users could disable polling in earlier DFM versions.) There is currently no workaround.
CSCsb16311
Alerts and Activities display alarm not updated when most severe event is cleared
When the most severe event associated with an alert is cleared, DFM does not update the Alerts and Activities display to show the current status of all the events. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb16307
Fault not attached when user selects Notify in Alerts and Activities Detail display
When a user clicks Notify from the Alerts and Activities Detail page, an e-mail is sent, but with no alert information. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb14294
DFM polls MSFC 15.1/16.1 internal interfaces
Device Fault Manager 2.0 polls the 6506 MSFC internal interfaces 15/1 and 16/1. It should not. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb73377
Bogus ExcessiveFragmentation alerts for 6503 CatOS LargestFreeBuffer
DFM generates bogus ExcessiveFragmentation events for the Catalyst 6503 catOS LargestFreeBuffer. This problem has been fixed in DFM 2.0.4 (see Additional Information Online). Delete and re-add the device to remove any previously-existing bogus events.
CSCsb83127
Cannot edit customizable group by ifType
DFM does not allow the user to edit customizable groups so that ifType has a unique value. There is currently no workaround
CSCsc02403
Alerts and Activities Detail page information not propagated
When a user clicks an Alert ID in the Alerts and Activities display, the Alerts and Activities Detail page will open, but occasionally no event details are displayed (or it may take up to 30 minutes to display the information). The problem maybe due to DBexceptions caused by attempts access a large dfmepm.db database. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc21691
Cannot clear UnidentifiedTrap alert
When an unmanaged device sends a pass-through trap, the event is added to the UnidentifiedTrap bucket. If that device is then added as a managed device before the event is cleared from UnidentifiedTraps, there is no way to clear that event manually. There is currently no workaround.
CSCsa97721
120dpi font resolution renders Alerts and Activities display unreadable
Setting font resolution to 120 dpi on a high resolution monitor renders the Alerts and Activities display unreadable. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsa67346
3560-48PS, Metro 3750: Collision Rate event info shows null value
When a user opens an event details page to check collision rate information, the value of SingleCollisionFramesP is displayed as null, as follows:
OutputPacketRate 3333333.2 PPS CollisionPct 12.0 % SingleCollisionFramesP nullThis was observed on the 3560-48PS switch and the Metro 3750 series switches. There is no workaround.
CSCsa86901
MDS-9216A: DDV does not display FibreChannel interfaces
The MDS-9216A Detailed Device View does not display the device's FibreChannel interfaces. The MDS-9216A has 18 interfaces (17 are ifType fibreChannel(56) and one is ifType fastEther(62)). Only the FastEthernet port is shown in the DDV; no interface components are listed.
This is due to a problem with the DFM engine. There is no workaround.
CSCsa85670
MDS-9216A: DDV does not display memory information
The Detailed Device View does not display memory components for the MDS-9216A, even though the device supports memory components.
This is due to a problem with the DFM engine. There is no workaround.
CSCsa81033
GSR-12010: DFM generates discovery error messages
When attempting to discover the GSR-12010 (OID 1.3.6.1.4.1.9.1.348), DFM generates error messages and device fans are not discovered.
This is due to a problem in the DFM engine. There is no workaround.
CSCsa66807
DDV has meaningless redundancy-related information
The following redundancy-related information was displayed on the Detailed Device View for the CE-2636, CDM-4650, CE-511, and WLSE 2.8:
RedundancyState
LastSwitchOverTime
LastSwitchOverReasonThis information should not be listed, since it is meaningless for these devices. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCin86757
DFM does not generate fault when SNMP agent gives null response
DFM does not report SNMPAgent Unresponsive symptoms when it receives a NULL response from an SNMP agent. This is misleading to users, since the agent is actually responding to SNMP queries with an invalid value, but DFM never detects this. DFM neither polls the device nor reports there is a device polling problem.
CSCin86753
Issue regarding duplicate IP address in ITM 2.0
When different IP addresses belonging to the same device are added as separate devices, due to a timing issue, they are discovered and listed as separate devices. This is incorrect and causes invalid DuplicateIP alarms.
CSCsb64944
DFM 2.0.3: DDV displays blank page
When a DFM 2.0.3 user opens a Detailed Device View using Device Management > Select Devices, DFM occasionally displays a blank page in addition to the normal page. This has only been observed on one client machine. The workaround is to close the blank window. This bug is under investigation.
CSCsb21975
Ca t2924CXLv: DDV shows LargestFreeBuffer value as not available
When a user launches a Detailed Device View for the Catalyst 2924CXLv, DFM occasionally fails to collect the value of LargestFreeBuffer. The following was displayed:
LargestFreeBuffer = ciscoMemoryPoolLargestFree / 1024 Unable to generate the alarm for Excessive fragmentationThere is no workaround.
CSCsd33287
Device rediscovery hangs at 10%
DFM 2.x discovery may hang at 10% due to a communication problem between the inventory service and collector. This problem is under investigation. There is currently no workaround.
CSCsd38823
INVDbEngine process hogs CPU, rendering the system unusable
The DFM INVDbEngine process can hog the CPU. This was observed when DFM was installed with other contents of the LAN Management Solution, the DCR was managing 9,000 devices, and DFM attempted to import all of the devices.
The workaround is to use.manual DFM/DCR synchronization to selectively add devices to the DFM inventory. (In the Device Selector page, make sure the synchronization checkbox is not checked.)
CSCsd42055
Devices not getting managed when imported in bulk
When 1,500 devices were added to DFM in a bulk import, most of the devices are put in the Questioned state and finally time out. The behavior differed between Solaris and Windows as follows:
•
•
CSCsd46213
Backup succeeds, but incorrect DFM version listed in restorebackup.log
DFM 2.0.4 can be successfully backed up and restored, However, the restorebackup.log lists the following message:
Version of DFM available in the backup is 2.0Ignore the log message.
CSCsd46224
Device management states not preserved after data is restored
After a user backs up and restores DFM data, DFM does not preserve the original management state of the devices. For example, a device that was suspended is moved to managed.
The workaround is to manually change the managed state of the device from the Detailed Device View.
CSCsd46279
Notification group management states not preserved after the groups are edited
After a user edits a notification group, DFM does not preserve the original management state. For example, a suspended notification group is moved to running. The workaround is to manually change the management state using Notification Services.
CSCsd64086
New user defined groups not reflected in Fault History unless users logs out and in
After creating a new user defined group in DFM, the group is not displayed in Fault History. The user must log out and back in to CiscoWorks to see the new group in Fault History. The workaround is to log out and back in to CiscoWorks.
CSCsd65361
Trap recipient entries deleted when they follow a duplicate
If a user lists the same trap recipient twice, any recipients listed after the duplicate are deleted. For example, dfmpc3 and dfmpc4 would be deleted from the following list of hostnames:
dfmpc1,dfmpc2,dfmpc1,dfmpc3,dfmpc4There is no workaround.
CSCsd70989
Empty Alerts and Activities page exits when saved to PDF
If the user displays an Alerts and Activities page that has no alerts, and exports the window to PDF, the Alerts and Activities page exits. There is no workaround.
CSCsd72607
Solaris: Deleted devices not removed from notification groups
After deleting devices from the DFM inventory, the devices still appear in existing notification groups. (The devices do not appear when creating a new notification group.) There is no workaround.
CSCsd78100
WLSE: Switchover events not generated when added through VIP in NAT
When a WLSE device is added to DFM using VIP, and the device is configured with a NAT address, DFM does not generate any switchover events or traps after services are started or stopped. There is no workaround.
CSCsd79639
User cannot search Fault History for devices deleted in last 31 days
If a device is deleted from DFM, users cannot search for historical device information from Fault History, even if the Fault History database contains information on the device. There is no workaround.
CSCsd81235
Alerts and Activities Details page displays two Tools drop-down lists
The Alerts and Activities Detail page occasionally displays two Tools drop-down lists for one event. This was observed when two events occurred on the same device, and one of the events is cleared. There is no workaround.
CSCsd73739
DFM 2.0.3 stops sending notifications for very large networks
When the number of managed instances approaches or exceeds the DFM maximum, DFM stops sending notifications for new events. There is no workaround.
CSCin86752
DFM does not discover 4604 Access Gateway card in Catalyst 4506
DFM 1.2.x did not discover 4604 Access Gateway cards in Catalyst 4506 switches. This problem has been fixed. However, although DFM 2.0 discovers the parent switch and card successfully, it does not display any card details in the Detailed Device View. There is currently no workaround.
CSCsa63869
WLSE: VIP not being rediscovered after switchover
When the virtual interface (VIP) of a WLSE device is added and a switchover occurs, the VIP is not rediscovered by DFM. This is because after a switchover, the VIPs become unreachable for a short period of time, and if this coincides with when the polling is performed, no rediscovery is performed. The workaround is to manually rediscover the VIP.
CSCsa58587
ONS-15454 not moved to Known unless group selected
While being discovered, the ONS-15454 may get stuck in the Learning state if a group is not selected. The workaround is to select a group.
CSCsc63868
CSS devices: Device is listed as Unknown device type
When a CSS 11501, 11503 or 11506 device running WebNS 7.4 or later is added to DFM, it is listed as an Unknown device type. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb78524
CSS devices: DDV does not list all interfaces/ports
The Detailed Device View does not list all of the ports and interfaces on the CSS 11501, 11503 or 11506 devices running WebNS 7.4 or later. There is currently no workaround.
CSCsc41119
CSS devices: DFM does not report processor and memory events
DFM does not report processor and memory HighUtilization events on CSS 11501, 11503 or 11506 devices running WebNS 7.4 or later. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsg03702
SIP 200 card: DDV lists card status as Not Available
When the Detailed Device View is launched on a Cisco 7609 router that has a SIP 200 card, the card is listed as Not Available. There is no workaround.
CSCsg13511
6504-E: Temperature OutOfRange event not generated
DFM does not generate a temperature OutOfRange event for the 6504-E. There is no workaround.
Known Problems Inherited from DFM 2.0
Table 4 lists all known problems that were inherited from the DFM 2.0 release.
Resolved Problems
These sections contain tables that list the problems resolved in this release:
•
•
•
•
Problems Resolved in DFM 2.0.3
Table 5 lists all problems that are resolved in DFM 2.0.3.
Table 5 Problems Resolved in DFM 2.0.3
CSCsa70833
dfmValidateUpgrade fails to validate a DFM 1.2 CD-ROM
The dfmValidateUpgrade script failed to validate a DFM 1.2 CD-ROM. It now validates the CD correctly.
CS Csa72836
DFM12x-DFM20-upgrade.pl should be integrated with restorebackup.pl
When upgrading to DFM 2.0, the user had to run a separate DFM12x-DFM20-upgrade.pl script to perform an upgrade (unlike other applications in the LAN Management Solution). The script is now integrated with restorebackup.pl, a script which is used by LMS 2.5.1 applications.
CSCsa97915
Solaris: Installation on Solaris sometimes fails
Sometimes, while installing DFM on Solaris, the installation script displayed dependency handling errors and stopped. This was because there were special characters in the CD mount path. This has been fixed and the installation now proceeds correctly.
CSCsa80715
Notification Services hangs after 2 weeks
Trap recipients did not receive traps from Notification Services; also, there was no response when a user clicked a link on the Notification Services tab. This happened after the NOSServer process had been running continuously for about two weeks. This problem no longer occurs.
CSCsb40243
sm_server and brstart are not terminated when daemon manager stops
The sm_server and brstart processes are not terminated when the CiscoWorks daemon manager stops. If the daemon manager is restarted, two instances of both sm_server and brstart will be running, and the CPU will hang around 100%. The workaround is as follows:
1.
2.
3.
CSCsa91950
restorebackup.pl displays incorrect instructions
If a user performed a remote upgrade to DFM 2.0 and ran the restorebackup.pl command, the command displayed upgrade instructions that were not up-to-date and not correct. The messages have been updated and corrected.
CSCsa97047
Remote upgrade completion message unclear
When performing a remote upgrade using the DFMRestore.pl command from the DFM 2.0 Upgrade Kit, the upgrade script generated an error message and the upgrade appeared to fail due to a problem with the DFM Broker. This problem no longer occurs.
CSCsa97839
Fatal errors when migrating polling/threshold data
Fatal errors were sometimes displayed while running the DFM12x-DFM20-upgrade.pl command and migrating polling and threshold data. This seemed to happen after migrating Resource Manager Essentials data. This problem no longer occurs.
CSCsa97928
E-Mail and Trap Notifier data is migrated but not displayed
Although Mail and Trap Notifier data was migrated from DFM 1.2.x to DFM 2.0, the data was not displayed by DFM 2.0. This was because TRAP_DEFAULT_FILE and EMAIL_DEFAULT_FILE were not defined in the NMSROOT/object/nos/config/nos.properties file. These are now defined and the data is displayed.
CSCsa98010
sm_ov_fwd does not run after remote HPOV-NV adapters installed
After installing the HPOV-NetView adapters on a remote host, sm_ov_fwd would not run. The process now runs correctly after the adapters are installed.
CSCsb04458
Changing homepage server name breaks DFM groups
If a user changed the homepage name to a value other than the hostname, DFM groups would break. This problem no longer occurs.
CSCsb06357
TCP port 8888 is not listed as used port in the documentation
DFM uses port 8888 for the DFMLogServer, but the port was not listed in the table of ports in the user guide and online help. This information has been added.
CSCsb14204
Solaris: DFM polling and threshold settings cannot be saved in Mozilla
Polling and Threshold values could not be saved when using a Mozilla-based browser (such as Mozilla or Netscape) on Solaris. The values are now saved.
CSCsb71371
Print and Export to PDF links in DDV do not work
If the user tried to Print or Export to PDF from the Detailed Device View, the links did not work. The links now work.
CSCsb75934
Solaris: Uninstall of HPOV-NetView Adapter alone is not possible
On Solaris, the user was not offered the option of uninstalling only the HPOV-NetView Adapter (which is useful on remote machines). This option is now displayed.
CSCsb76225
sm_nv_fwd does not run after remote HPOV-NV adapters installed
After installing the HPOV-NetView adapters on a remote host, sm_nv_fwd would not run. The process now runs correctly.
CSCsb77987
DFM prompts for license even if license was already provided
DFM prompted the user for a valid license even after a license had already been provided. This problem no longer occurs.
CSCsb89994
Trap recipients information is skipped after five entries
If a user tried to migrate more than five trap recipients (IP/hostnames) during an upgrade, after the upgrade, DFM displayed only the first five entries. The other information was lost. All recipient information is now migrated and displayed.
CSCsc12761
Remote upgrade license validation from 1.2.x fails
When validating an upgrade license on a remote server, the validation failed. This problem has been fixed.
CSCsc24189
E-Mail and Trap Notification data not displayed after remote upgrade
When upgrading from DFM 1.2.x to DFM 2.0.3, E-Mail and Trap Notification data was not migrated. The data is now migrated.
CSCsc28680
Local upgrade should not ask for proof of purchase
After a local (inline) upgrade to DFM 2.0.3, even if the user supplied the upgrade license information, DFM would nag the user for proof of purchase. This problem no longer occurs.
CSCsc53405
After migration, DFM times out waiting for DFM server process
After migrating data, DFM would time out when waiting for the DfmServer process to register with the DfmBroker process. This problem no longer occurs.
CSCsb86237
Cannot customize thresholds for Interfaces and Modules group
When a user selected Polling and Thresholds > Managing Thresholds and tried to customize thresholds for Cisco Interfaces and Modules, the Customize Settings page opened but did not display any settings that could be changed. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsa79675
Cannot read Detailed Device View screen
Detailed Device View columns in DFM 2.x were not readable because they were too small. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb59510
DDV displays error page
DFM occasionally displayed an error page when a user opened a Detailed Device View, clicked the device IP address radio button, and then clicked either the Device Attribute or Information link (on the right side of the page). This error was displayed:
Problem with File /WEB-INF/screens/ddv.jsp!!!Cannot find bean ddvhtmltable in scope nullThis problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc18405
Trap and Syslog Notification recipients are cleared
Existing trap and syslog recipients were sometimes cleared when a user tried to edit them. This happened when the user edited an existing subscription, and did the following:
1.
2.
This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc92186
DFM does not support SHA-1 SNMPv3 authentication algorithm
DFM 2.0.3 could not discover devices using SNMPv3 with SHA-1 as its hashing algorithm, because DFM considered SHA-1 an invalid SNMP protocol. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsd31511
Rediscovery Schedule displays 500 Server Error
When a user selected Configuration > Other Configuration > Rediscovery Schedule, the system sometimes displayed a 500 Internal Server error. Investigation showed that this occurred predominantly when DFM was installed with Resource Manager Essentials (RME), and RME was running several periodic system jobs (collection, polling, purging, and so forth). This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc49794
DFM does not add device using correct IP address
When a switch with multiple IP addresses was added to DFM, DFM did not use the specified IP address when creating the object instance in the DFM engine. This caused the device to go to the Unknown discovery state. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc05115
DFM does not discover MeetingPlace Express as Host
DFM did not discover the Cisco MeetingPlace Express (1.3.6.1.4.1.9.1.710) as a host. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb21876
Cat 3750: Standalone switches (without stack) not supported
DFM reported all Catalyst 3750 switches with the same OID, because DFM assumed they would be used in a stack: 3750-24FS, 3750-24PS, 3750-24TS, 3750-48PS, 3750G-16TD, 3750G-24PS, 3750G-24TS1U, 3750G-48PS, and 3750G-48TS. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsb57090
CSS device no longer supported because sysObjectID changed
For CSS 11503 and 11506 devices running WebNS 7.4 or higher, DFM did not correctly discover the devices. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc76777
Sup720 and NAM cards: Correct names not displayed
The Detailed Device View did not display the correct names for the Sup720 and NAM cards. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc76732
3750: Support stack MIB
DFM did not generate any alerts if a 3750 switch was removed from the stack because it did not support the following CISCO-STACKWISE-MIB pass-through traps:
cswStackPortChange
cswStackNewMaster
cswStackMismatch
cswStackRingRedundant
cswStackMemberRemovedThis problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc53019
ASL ERROR in DFM.log file
The DFM.log file sometimes contained ASL-ERROR messages. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsd31319
Running notifications not sent when DFM is restarted
If a user restarted DFM, previously existing notifications stopped running. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsd00991
DFM should not create async interfaces on Access Servers
DFM was creating and managing all Access Server async interfaces (SLIP itType=28), even though they are logical interfaces. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
CSCsc91394
Notification subscriptions do not work after upgrade to DFM 2.0.3
Notification subscriptions stopped working after upgrading to DFM 2.0.3. This was due to an NOSServer registration problem. This problem has been fixed in DFM 2.0.4 (see Additional Information Online).
Problem Resolutions Inherited from DFM 2.0 Service Pack 2
Table 5 lists all problems that were resolved in DFM 2.0 Service Pack 2.
Problem Resolutions Inherited from DFM 2.0 Service Pack 1
Table 5 lists all problems that were resolved in Service Pack 1 (also called Patch/IDU 2.0.1).
Table 7 Problem Resolutions Inherited from DFM 2.0.1
CSCsa50868
Device takes too long to move to Known state
DFM sometimes required more than 30 minutes to move a device from Learning to Known. This was due to the following:
•
•
This problem no longer occurs.
CSCsa49406
Cannot launch drop-down tools from Alerts and Activities Detail page
When a remote instance of Cisco View or Campus Manager was registered with the CiscoWorks home page, and local versions of those applications were already registered, CiscoWorks could not launch tools from the Alerts and Activities Detail drop-down list. This was because CiscoWorks tries to open the remote link rather than the local link. This problem no longer occurs.
CSCsa41661
Solaris: Sun JDK problem causes some applications (Notification Services) to dump core file and quit after three days
On Solaris machines, a Java problem occasionally caused Notification Services to dump core and quit after three days of notification forwarding. This occurred when the Solaris server was running in a heavy load environment (for example, when 50 events were received every polling cycle, and the polling cycle was every 4 minutes). The Alerts and Activities display and Fault History were not affected.
The Sun JDK defect that caused this problem was tracked through a Common Services 3.0 bug (CSCeg26913). Sun recommends launching JVM with two options:
-server: Launches JVM as server JVM (rather than client JVM)
-Djava.compiler=NONE: Creates meaningful stack trace for future troubleshooting
CSCsa45329
Solaris: DFM hogs CPU when DCR contains more than 5,000 devices
When the DCR contains more than 5,000 devices, the DFMOGSServer may hog CPU cycles due to processing issues. The CPU hogging may occur for four hours or more. This problem is less noticeable in dual CPU machines.
CSCsa45235
Port analysis is provided even when analysis is disabled
If a port was connected to a Layer 3 device (a router) and a user then disabled analysis on the port, DFM continued to analyze the port. This was due to an internal engine issue. This problem no longer occurs.
CSCsa45801
DFM reports IF OperationallyDown events even when analysis is disabled
If a user disabled all interface/port analysis (using the Disable All Threshold Settings check box), DFM occasionally continued to provide interface fault information. This was because DFM applies reachability settings after applying connector port and interface settings. This problem no longer occurs.
CSCsa15285
DFM displays MPLS type as GENERIC
DFM displays Multiprotocol Label Switching (MPLS) interfaces as TYPE=GENERIC. (MPLS interfaces have an ifType=166.) These interfaces are now correctly displayed.
CSCin86754
DFM does not provide a way to list managed access ports
DFM did not provide the capability for listing all managed access ports. A script is now provided for listing ports and interfaces according to their type, name, group membership and managed status. Refer to the online version of User Guide for Device Fault Manager; see Product Documentation.
CSCin86756
Add TrafficRate attribute to UI
On some DFM devices, CurrentUtilization was listed as an exponential number. Users could not interpret this meaning, since the TrafficRate attribute was not listed. The attribute is now listed.
CSCsa49933
Broken help links in Group Administration
In the Group Administration windows, some of the Help links were broken. These are now working correctly.
Problem Resolutions Inherited from DFM 2.0
Table 8 lists all problems that were resolved in the DFM 2.0 release.
Table 8 Problem Resolutions Inherited from DFM 2.0
CSCdx32239
Incorrect duplexity shown for router and switch interfaces and ports
DFM did not always report correct duplexity for router and switch interfaces. One reason this happened was because of assumptions DFM made when port or interface duplexity was UNSPECIFIED. DFM now uses DuplexMode to specify the duplexity (UNSPECIFIED, by default) and DuplexSource to track the source of setting duplexity (NONE by default). DFM now uses this new algorithm to determine duplexity:
1.
a.
b.
2.
a.
b.
(continued)
CSCdx32239 (continued)
Incorrect duplexity shown for router and switch ifs and ports
3.
a.
b.
4.
a.
b.
CSCed27739
DFM manages MPLS logical interfaces, causing duplicate alarms
DFM generated duplicate alarms for Multiprotocol Label Switching (MPLS) interfaces. This occurred because DFM managed logical interfaces, and MPLS logical interfaces have a separate ifIndex.
Logical interfaces with ifType:166 (MPLS) are now unmanaged by default.
CSCsa03104
DFM uses wrong OID to poll CPU utilization on PIX
DFM did not report CPU utilization for PIX Firewalls because the algorithm used by DFM created the proper instrumentation when:
•
•
For PIX Firewalls, cpmCPUTotalPhysicalIndex is always 0, and PIX Firewalls does not support OLD-CISCO-CPU-MIB.
DFM still polls cpmCPUTotalPhysicalIndex, but the value of cpmCPUTotalIndex is verified instead. cpmCPUTotalIndex is used as the index.
CSCea80669
ovtrapd cannot start after reboot because DFM occupies port 162
If a user installed HP OpenView before DFM, HP OpenView used port 162 and DFM used port 9000. This is the correct behavior. However, if the user rebooted the device, the HP OpenView ovtrapd process could not start because DFM occupied port 162 as well as port 9000.
Now, if DFM detects that HP OpenView or NetView is installed, DFM will only use port 9000. (However, if you want DFM to always use port 162 upon reboot—for example, if you remove HP OpenView and NetView—you can use the --privopen option to do so. Refer to the online version of User Guide for Device Fault Manager; see Product Documentation.
CSCeb12662
Layer 3 device port/interface handling is incorrect
When an IP address was assigned to a port on the Catalyst 4506 running Cisco IOS (with Sup III), DFM displayed it as both a port and an interface.
All multilayer switch ports, to which IP addresses are assigned, are now properly modeled as interfaces.
CSCdx64809
DFM should unmanage voice interfaces/ports
In Cisco IOS devices running the Survivable Remote Site Telephony (SRST) feature, a VoiceEncapPeer interface (in ifTable) exists for each phone supported by SRST. These interfaces were operationally DOWN by default, since they were not being used while the local IP phones could reach their remote call manager. DFM generated an OperationallyDown event for these interfaces, which was incorrect, since this was the normal and expected state.
DFM no longer generates an OperationallyDown event for these interfaces.
CSCea11383
DFM should not treat voice dial peers as regular interfaces
DFM treated dial peer interfaces as physical interfaces and was managing them. These interfaces are now not managed because DFM recognizes them (by their ifType) as voice interfaces.
CSCdy43753
DFM cannot discover third power supply in Cat4000 switches
DFM could not discover the third power supply in Catalyst 4000 switches, even though the snmpwalk verified that the power supply was operational. DFM now correctly discovers the power supply.
CSCeb41000
DFM should suppress flapping if device restarts
When a device restarted, all associated interfaces sent link up and link down traps. If the number of restarts exceeded the Link Trap threshold, DFM reported excessive restarts and flapping (depending on the interface type) for all associated interfaces. The flapping event is now suppressed if the device restarts.
CSCdz14890
1% error threshold is too high for critical interfaces
The minimum for the error threshold (ifInerror) in DFM was 1% of the total number of packets, which was too high for high-bandwidth interfaces (such as Gbic and other WAN interfaces). The threshold can now be changed, because DFM 2.0 adds a new ErrorTraffic threshold. Refer to the online version of User Guide for Device Fault Manager; see Product Documentation.
CSCdz86886
Cannot change PacketErrorRate threshold
The PacketErrorRate threshold could not be modified.
The threshold can now be changed, because DFM 2.0 adds a new ErrorTraffic threshold. Refer to the online version of User Guide for Device Fault Manager; see Product Documentation.
CSCec42667
CSS11150 and CSS11050 switches generate incorrect memory exception
On CSS11150 and CSS11050 switches, DFM generated erroneous memory exceptions because instead of monitoring only the SCFM module, it was monitoring other modules (such as the EPIF module). DFM no longer monitors any modules besides the SCFM module.
CSCec77687
Filter out pass-through traps which are not related to managed devices
Whenever pass-through traps were received from unmanaged devices, they were displayed in the Monitoring Console. Pass-through traps for unmanaged devices are no longer displayed in the Monitoring Console.
Guest
