•Information on the new script for listing ports and interfaces according to their type, name, group membership and managed status. For more information, see the online help by selecting Device Fault Manager > User Guide > Working with the DFM Inventory > Managing and Unmanaging DFM Inventory Elements > Listing Managed Ports and Interfaces.

•Information on the new InvalidResponse symptom for OperationalExceptions on SNMP agents. For more information, see the online help by clicking the Help button and selecting Device Fault Manager > User Guide > Faults and Exceptions Diagnosed by DFM, Table 3-2, and the Operational Exception topic.

•All new functions and updated online help, which are described in Table 1.

Table 1 New Functions Provided by Earlier DFM 1.2 Patch/IDUs

New Function

Described in the DFM online help or on Cisco.com at...

New default threshold groups for managing/unmanaging ports and interfaces, and unmanaged systems

Downloading the Patch/IDU

Patch/IDU 1.2.10 files are downloaded in a compressed form. To prevent overwriting of files in existing directories as well as ensure that adequate disk space is available, users should download the files to a temporary working area of their server, and then uncompress the files.

Step 2 Make sure you have adequate free space for the uncompression, then uncompress the file in the temporary working area:

# uncompress cw-dfm-idu1-2-10-sol.tar.Z

Step 3 Extract the distribution file:

# tar xvf cw-dfm-idu1-2-10-sol.tar

Installing the Patch/IDU

Caution You cannot remove Patch/IDU 1.2.10 after installing it. To return to your original configuration, you will have to uninstall and reinstall DFM.

Step 1 Move to the directory the downloaded file is in:

# cd SOL_DFM1_2_10/image/disk1

Step 2 Run the installation setup script:

# ./setup.sh

Note You can run the installation remotely. For information on mounting and unmounting disks, refer to Installation and Setup Guide for Device Fault Manager on Solaris. Hardware and software requirements remain unchanged from those needed for the initial installation of DFM 1.2, DFM 1.2 Updated for Common Services Version 2.2, or VHM 1.1. For information on installing DFM 1.2 or DFM 1.2 Updated for Common Services Version 2.2, refer to Installation and Setup Guide for Device Fault Manager on Solaris. You can view this document by logging onto Cisco.com and going to http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm123cd/install/solaris/index.htm.

Step 3 Follow the prompts in the installation script. The options displayed by the installation script depend on your configuration.

The Cisco 1841 does not compute CurrentUtilization because HighCounter MIBs are not implemented for interfaces with speeds greater than 100 Mbps. To determine whether this is due to a device bug, a bug against the Cisco 1841 has been opened (CSCef58995). There is currently no workaround.

CSCsa34254

SNMPAgent InvalidResonse alarm not cleared

DFM does not clear the SNMPAgent InvalidResonse symptom, even after the device is configured with the required (ro) community string. It is not cleared until DFM rediscovers the device.

There is currently no workaround. To clear the symptom, rediscover the device.

CSCsa35088

6509-NEBA: No support for 9-slot vertical chassis

DFM does not support the Catalyst 6509-NEB-A 9-slot vertical chassis.

There is currently no workaround.

CSCsa36156

Trap forwarding IP not validated before configuration

If a user configures trap forwarding without an IP address (by clicking OK without completing the form), DFM configures trap forwarding but with no forwarding address. DFM should validate the IP address before configuring trap forwarding.

Use one of these workarounds:

•Reconfigure trap forwarding and restart the DFM server.

•Disable trap forwarding.

CSCsa36885

WS-SVC-CMM does not fully implement ifXTable

DFM does not generate the following symptoms for the WS-SVC-CMM: HighUtilizationRate, HighDiscardRate, HighCollisionRate, HighBroadcastRate, HighQueueDropRate, and HighErrorRate. This is because a number of OIDs are not implemented in the ifXTable.

There is currently no workaround. A bug has been opened against the WS-SVC-CMM (CSCin83708).

CSCsa36887

Cisco 2801 does not fully implement ifXTable

DFM does not generate the following symptoms for the Cisco 2801: HighUtilization, HighDiscardRate, HighCollisionRate, HighBroadcastRate, HighQueueDropRate, and HighErrorRate. This is because several OIDs are not implemented in the ifXTable.

There is currently no workaround. A bug has been opened against the Cisco 2801 (CSCin83710).

CSCsa38656

WLSE does not fully implement MIB-II ifTable

DFM does not generate the following symptoms for the WLSE: HighDiscardRate, HighCollisionRate, HighBroadcastRate, HighQueueDropRate, and HighErrorRate. This is because several OIDs are not implemented in the ifXTable.

There is currently no workaround. A bug has been opened against the WLSE (CSCin83711).

CSCsa19013

Solaris: Stopping the daemons does not stop sm_server

When CiscoWorks is stopped, the DFM sm_server daemon sometimes continues to run.

The workaround is to manually stop the daemon PID using the kill -9 command.

When a device with SNMP agent looping is added to DFM, the agent loops while querying for device elements. Because DFM continues to create multiple instances of the element, the sm_server eventually hogs all of the CPU and most of the virtual memory, and corrupts the DFM.rps file. This causes the DFM consoles to hang. This was observed on the IAD family of devices.

CSCsa26774

AP 340 does not generate DuplicateIP error

DFM does not report DuplicateIP events for the AP 340 because the IpAddr table is not populated for AP radio interfaces.

A bug has been opened against the AP 340 (CSCef17995). There is currently no workaround.

CSCsa23167

MWR 1900 does not report RepeatedRestarts

The MWR 1900 does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps.

. To determine whether this is due to a device bug, a bug against the MWR 1900 has been opened (CSCee75859). There is currently no workaround.

CSCsa23158

AP 340 does not report RepeatedRestarts

The AP 340 does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the AP 340 has been opened (CSCee76825). There is currently no workaround.

CSCsa25319

CDM-4630 does not report RepeatedRestarts when host listening to custom ports

If a host is listening to custom ports, the CDM-4630 does not send traps to the host. In this situation, no RepeatedRestarts alarms are generated.

To determine whether this is due to a device bug, a bug against the CDM-4630 has been opened (CSCee94244). There is currently no workaround.

CSCsa22854

4908G-L3 does not report RepeatedRestarts

The 4908G-L3does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the 4908G-L3 has been opened (CSCee76829). There is currently no workaround.

DFM stops performing SNMP polling on devices when the device ethernet interfaces go down, even if FrameRelay interfaces are reachable.

There is currently no workaround.

CSCsa26224

3201 MWR does not report RepeatedRestarts

The 3201 MWR does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the 3201 MWR has been opened (CSCef17949). There is currently no workaround.

CSCsa23445

2600/3600 NAM does not support network adapter alarms on interfaces greater than 20,000,000 mbps

The 2600/3600 NAM does not support network adapter alarms for interfaces with speeds greater than 20,000,000 mbps. This is because the ifHCInOctets and ifHCOutOctets variables are not implemented. A bug against the 2600/3600 NAM has been opened (CSCef18043). There is currently no workaround.

Table 5 Known Problems Inherited from Patch/IDU 1.2.8

Bug ID

Summary

Explanation

CSCin72033

CE-7320 does not report RepeatedRestarts

The Cisco CE-7320 content engine does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the CE-7320 has been opened (CSCin73589). There is currently no workaround.

CSCin72028

Catalyst 6000 SSL module does not generate SNMP Unresponsive

After changing the SNMP community string setting in the Catalyst 6000 SSL module, DFM does not report an SNMP Unresponsive alarm.

To determine whether this is due to a device bug, a bug against the Catalyst 6000 SSL module has been opened (CSCin73586). There is currently no workaround.

CSCin72020

Catalyst 6000 SSL module is not sending cold start trap for its own IP

The SSL Services Module for the Cisco Catalyst 6500 does not support the RepeatedRestarts fault because the device does not generate cold start traps for its own IP address. Instead, it is sending the cold start trap with its loopback IP address.

To determine whether this is due to a device bug, a bug against the SSL Services Module has been opened (CSCin73587). There is currently no workaround.

CSCsa12752

SOHO-78 does not generate SNMP Unresponsive

After changing the SNMP community string setting in the SOHO-78, DFM does not report an SNMP Unresponsive alarm.

To determine whether this is due to a device bug, a bug against the SOHO-78 has been opened (CSCin73591). There is currently no workaround.

CSCsa13092

MWR-1941-DC does not report RepeatedRestarts

The Cisco MWR-1941-DC router does not support the RepeatedRestarts symptom because the device does not generate cold start and warm start traps. To determine whether this is due to a device bug, a bug against the MWR-1941-DC has been opened (CSCin73592). There is currently no workaround.

CSCsa13093

MWR-1941-DC does not generate SNMP Unresponsive

After changing the SNMP community string setting in the MWR-1941-DC, DFM does not report an SNMP Unresponsive symptom.

To determine whether this is due to a device bug, a bug against the MWR-1941-DC has been opened (CSCin73593). There is currently no workaround.

The MWR-1941-DC does not support the HighUtilization, HighQueueDropRate, HighCollisionRate, or HighErrorRate symptoms on Fast Ethernet interfaces. This is because the HCInOctets MIB attribute is not implemented. A bug against the MWR-1941-DC has been opened (CSCin73594). There is currently no workaround.

CSCsa13482

GSS 4490 does not report RepeatedRestarts

The CiscoGSS 4490 does not support the RepeatedRestarts symptom because the device does not generate cold start and warm start traps. To determine whether this is due to a device bug, a bug against the GSS 4490 has been opened (CSCin73595). There is currently no workaround.

CSCsa14191

CE-507, 507-AV, 560, 560-AV, 590 do not report RepeatedRestarts

The Cisco CE-507, CE-507-AV, CE-560, CE-560-AV, and CE-590 content engines do not support the RepeatedRestarts symptom because the devices do not generate cold start and warm start traps. To determine whether this is due to a device bug, a bug against the devices has been opened (CSCin73596). There is currently no workaround.

CSCsa14622

GSS-4490 does not generate processor HighUtilization or disk OperationallyDown

The GSS-4490 does not support the processor HighUtilization or disk OperationallyDown symptoms. This is because the hrProcessorLoad and hrDeviceStatus MIB attributes are not implemented. A bug against the GSS-4490 has been opened (CSCin73597). There is currently no workaround.

CSCsa15420

Uninstalling DFM 1.2 on Solaris does not clean installation directory

When uninstalling DFM 1.2, the following files are not removed:

NMSROOT/bin/DeleteDiscoveryJob.pl
NMSROOT/.asasrv.ini

The workaround is to manually delete the files.

CSCsa15955

2948-GL3 does not report RepeatedRestarts

The Cisco 2948-GL3 does not support the RepeatedRestarts symptom because the device does not generate cold start and warm start traps. To determine whether this is due to a device bug, a bug against the 2948-GL3 has been opened (CSCin73590). There is currently no workaround.

This is due to a compiler limitation. There is currently no workaround.

CSCsa18753

Content Engines memory components not created

Memory components not created for Cisco Content Engine devices This is because the hrstoragetype attribute is returning incorrect values. To determine whether this is due to a device bug, a bug against the Content Engines has been opened (CSCsa18753). There is currently no workaround.

CSCdz20700

Unmanage Logical ATM/FrameRelay Interfaces

When DFM detected any instance of ifTable to be AdministratvelyUp/OperationallyDown, it generated an alarm for each instance.

Although Patch/IDU 1.2.7 changed this behavior so that DFM does not manage logical ATM/FrameRelay interfaces, this bug has been reopened to research an easier way to manage groups of interfaces/ports based on any criterion.

There is currently no workaround.

Table 6 Known Problems Inherited from Patch/IDU 1.2.7

Bug ID

Summary

Explanation

CSCin63247

3220 does not support network adapter alarms on interfaces greater than 100 mbps

The Cisco 3220 does not support network adapter alarms for interfaces with speeds greater than 20,000,000 mbps. To determine whether this is due to a device bug, a bug against the Cisco 3220 has been opened (CSCin63022). There is currently no workaround.

CSCin63249

MWAM does not support network adapter alarms on interfaces greater than 100 mbps

The Cisco Multiprocessor WAN Application Module (MWAM) does not support network adapter alarms for interfaces with speeds greater than 20,000,000 mbps. This is because several MIB variables are not implemented. A bug against the MWAM has been opened (CSCin63100). There is currently no workaround.

CSCin63251

RPM-PR does not support network adapter alarms on interfaces greater than 100 mbps

The Cisco Route Processor Module (RPM-PR) RPM-PR does not support network adapter alarms for interfaces with speeds greater than 20,000,000 mbps. This is because several MIB variables are not implemented. A bug against the RPM-PR has been opened (CSCin63101). There is currently no workaround.

CSCin63245

IAD 2430 does not support network adapter alarms on interfaces greater than 100 mbps

The Cisco IAD 2430 Series Integrated Access Device does not support network adapter alarms for interfaces with speeds greater than 20,000,000 mbps. To determine whether this is due to a device bug, a bug against the IAD 2430 has been opened (CSCin63018). There is currently no workaround.

CSCsa07418

1710 VPN does not support network adapter alarms on interfaces greater than 100 mbps

The Cisco 1710 VPN does not support network adapter alarms for interfaces with speeds greater than 20,000,000 mbps. This is because the ifHCInOctets and ifHCOutOctets variables are not implemented. A bug against the 1710 VPN has been opened (CSCin65468). There is currently no workaround.

CSCin65543

ONS 15501-AC power supply is not populated in DFM GUI

The Cisco ONS 15501-AC does not display its power supply when a user expands the ComposedOf tree. (This does not occur on the ONS 15501-DC). To determine whether this is due to a device bug, a bug against the ONS 15501-AC has been opened (CSCin66271). There is currently no workaround.

CSCsa06505

SN-5428 does not report HighQueueDropRate

The Cisco SN-5428 storage router does not support the HighQueueDropRate fault. This is because the locIfInputQueueDrops MIB variable is not implemented. A bug against the SN-5428 has been opened (CSCin65053). There is currently no workaround.

CSCsa07015

VPN 3000 does not report RepeatedRestarts

The Cisco VPN 3000 router does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps. To determine whether this is due to a device bug, a bug against the VPN 3000 has been opened (CSCin65046). There is currently no workaround.

CSCsa05906

MDS 9120 does not report RepeatedRestarts

The Cisco MDS 9120 switch does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps. To determine whether this is due to a device bug, a bug against the MDS 9120 has been opened (CSCin63255). There is currently no workaround.

CSCsa07046

ONS 15501-DC does not generate DuplicateIP error

DFM does not report DuplicateIP events for the ONS 15501-DC.

To determine whether this is due to a device bug, a bug against the ONS 15501-DC has been opened (CSCin67711). There is currently no workaround.

CSCsa26876

DFM displays wrong CPU utilization for the CSS 115xx

The CPU threshold value set in the DFM GUI is different than what is displayed by command line output. This was observed on the CSS 11503.

Table 7 Known Problems Inherited from Patch/IDU 1.2.6

Bug ID

Summary

Explanation

CSCin58260

10720 does not report RepeatedRestarts

The 10720 router does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the Cisco 10720 has been opened (CSCin58259). There is currently no workaround.

CSCsa02381

10720 does not report VoltageOutOfRange

The 10720 router does not support the VoltageOutOfRange alarm because the device does not support the following MIB variables:

•ciscoEnvMonVoltageStatusValue

•ciscoEnvMonVoltageThresholdLow

•ciscoEnvMonVoltageThresholdHigh

To determine whether this is due to a device bug, a bug against the Cisco 10720 has been opened (CSCin60106). There is currently no workaround.

CSCsa02578

ONS 15530 CurrentUtilization for FE interface is grayed out

DFM does not report CurrentUtilization for FE interfaces on ONS 15530 NEBS, ETSI, and ESPX devices because ifHCounters are not implemented.

To determine whether this is due to a device bug, a bug against the ONS 15530 has been opened (CSCec44897). There is currently no workaround.

CSCsa02822

uBR7246VXR does not generate SNMP Agent Unresponsive events

DFM does not generate SNMP agent Unresponsive events for the uBR7246VXR.

To determine whether this is due to a device bug, a bug against the Cisco uBR7246VXR has been opened (CSCin58240). There is currently no workaround.

CSCsa02981

CE-7325 does not support RepeatedRestarts

The CE-7325 does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the CE-7325 has been opened (CSCin58529). There is currently no workaround.

CSCsa03070

Catalyst 2970-24 does not generate DuplicateIP event

DFM does not report DuplicateIP events for the Catalyst 2970-24.

To determine whether this is due to a device bug, a bug against the Cisco 2970-24 has been opened (CSCin60129). There is currently no workaround.

Table 8 Known Problems Inherited from Patch/IDU 1.2.5

Bug ID

Summary

Explanation

CSCeb20298

3725 does not support performance events

DFM does not report any performance-related events on the Cisco 3725 because the ifX table is not properly implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation.

To determine whether this is due to a device bug, a bug against the Cisco 3725 has been opened (CSCeb20254). There is currently no workaround.

CSCeb20571

3725 does not always support RepeatedRestarts

The Cisco 3725 does not support the Repeated Restarts alarm because, although the device generates cold start and warm start traps, the traps are not received in the local subnet upon startup. They are received outside the subnet.

To determine whether this is due to a device bug, a bug against the Cisco 3725 has been opened (CSCeb20376). There is currently no workaround.

CSCeb31385

ISDN D channel shows operationally down when the physical channel is down

ISDN D-Channels are shown as OperationallyDown when it is the Physical channel that is OperationallyDown. There is currently no workaround.

CSCef73757

6503: DFM reports false ExcessiveFragmentation symptoms

DFM reports false ExcessiveFragmentation symptoms for the Catalyst 6503. This is because the 6503 memory component is configured using a router driver (rather than a switch driver).

The workaround is to unmanage the memory component.

Table 9 Known Problems Inherited from Patch/IDU 1.2.4

Bug ID

Summary

Explanation

CSCdz68098

3631 CurrentUtilization for FE interface is grayed out

DFM does not report CurrentUtilization for FE interfaces on the Cisco 3631 because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation. (There is no support for the ifHCInOctets and ifHCOutOctets MIB attributes.)

To determine whether this is due to a device bug, a bug against the Cisco 3631 has been opened (CSCdz67912). There is currently no workaround.

CSCdz69210

1751V CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the Cisco 1751V because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation. (There is no support for the ifHCInOctets and ifHCOutOctets MIB attributes.)

To determine whether this is due to a device bug, a bug against the Cisco 1751V has been opened (CSCdz69186). There is currently no workaround.

CSCdz69202

1721 CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the Cisco 1721 because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation. (There is no support for the ifHCInOctets and ifHCOutOctets MIB attributes.)

To determine whether this is due to a device bug, a bug against the Cisco 1721 has been opened (CSCdz68856). There is currently no workaround.

CSCdz74246

2691 CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the Cisco 2691 because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation. (There is no support for the ifHCInOctets and ifHCOutOctets MIB attributes.)

To determine whether this is due to a device bug, a bug against the Cisco 2691 has been opened (CSCdz73821). There is currently no workaround.

CSCea02995

7513MX CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the Cisco 7513MX because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation. (There is no support for the ifHCInOctets and ifHCOutOctets MIB attributes.)

To determine whether this is due to a device bug, a bug against the Cisco 7513MX has been opened (CSCea02914). There is currently no workaround.

CSCea03550

AP1100 CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the Cisco Aironet AP1100 because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation. (There is no support for the ifHCInOctets and ifHCOutOctets MIB attributes.)

To determine whether this is due to a device bug, a bug against the Cisco Aironet AP1100 has been opened (CSCea04852). There is currently no workaround.

CSCea03541

PIX 535 CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the Cisco PIX 535 because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation.

To determine whether this is due to a device bug, a bug against the PIX 535 has been opened (CSCea04950). There is currently no workaround.

CSCdz81075

WSC-SVC-NAM-1 and -NAM-2 CurrentUtilization for FE interface is grayed out.

DFM does not report CurrentUtilization for FE interfaces on the WSC-SVC-NAM-1 and -NAM-2 because the ifX table is not completely implemented. The cause is under investigation; it may be due to a problem with the device MIB implementation.

To determine whether this is due to a device bug, a bug against the WSC-SVC-NAM-1 and -NAM-2 has been opened (CSCdz81059). There is currently no workaround.

CSCdz69758

1751V does not support RepeatedRestarts alarm.

The Cisco 1751V does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the Cisco 1751V has been opened (CSCdz69754). There is currently no workaround.

CSCdz69718

3631 does not support RepeatedRestarts alarm.

The Cisco 3631 does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the Cisco 3631 has been opened (CSCdz69704). There is currently no workaround.

CSCdz69748

1721 does not support RepeatedRestarts alarm.

The Cisco 1721 does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the Cisco 1721 has been opened (CSCdz69742). There is currently no workaround.

CSCdz81046

WSC-SVC-NAM-1 and -NAM-2 do not support RepeatedRestarts alarm.

The WSC-SVC-NAM-1 and -NAM-2 do not support the Repeated Restarts alarm because the devices do not generate cold start and warm start traps.

To determine whether this is due to a device bug, a bug against the WSC-SVC-NAM-1 and -NAM-2 has been opened (CSCdz81031). There is currently no workaround.

CSCea71942

DFM does not discover 4604 Access Gateway card in Catalyst 4500

DFM does not discover 4604 Access Gateway cards in Catalyst 4506 switches. This is because the Catalyst 4506 supports the CISCO-ENTITY-FRU-CONTROL-MIB, which does not have an entry that contains the IP address of the module. Catalyst 4000 switches do not have this problem because those switches support the CISCO-STACK-MIB, which does have the appropriate entry.

DFM does not display VLAN information for Catalyst 4500 switches that perform Layer 3 routing. This problem was first observed on the Catalyst 4507R running 12.1.12c EW1.

There is currently no workaround.

Resolved DFM Problems

The following tables describe DFM problems that are resolved in Patch/IDU 1.2.10.

Table 10 Problems Resolved in Patch/IDU 1.2.10

Bug ID

Summary

Explanation

CSCsa23290

DFM does not provide a way to list managed access ports

DFM did not provide the capability for listing all managed access ports.

This patch/IDU provides a new script for listing ports and interfaces according to their type, name, group membership and managed status. For more information, see the online help by selecting Device Fault Manager > User Guide > Working with the DFM Inventory > Managing and Unmanaging DFM Inventory Elements > Listing Managed Ports and Interfaces.

CSCsa23284

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.

This patch/IDU adds the TrafficRate attribute to the DFM user interface.

CSCsa26950

DFM does not generate fault when SNMP agent gives null response

DFM was not reporting SNMPAgent Unresponsive symptoms when it received a NULL response from an SNMP agent. This was misleading to users, since the agent was actually responding to SNMP queries with an invalid value, but DFM never detected this. DFM could neither polled the device nor reported there was a device polling problem.

This patch/IDU introduces a new symptom called InvalidResponse. It is part of the OperationalException compound that is reported on SNMP agents. For more information, refer to the online help by selecting Device Fault Manager > User Guide > Faults and Exceptions Diagnosed by DFM > Operational Exception.

Table 11 Problem Resolutions Inherited from Patch/IDU 1.2.9

Bug ID

Summary

Explanation

CSCea71942

DFM does not discover 4604 Access Gateway card in Catalyst 4506

DFM did not discover 4604 Access Gateway cards in Catalyst 4506 switches. This was due to a MIB limitation. The MIB has been enhanced, and this problem no longer occurs.

CSCin76775

DFM creates separate devices for device with multiple IP addresses

DFM added IP addresses belonging to the same device as separate devices. This was due to a timing issue. This problem no longer occurs

CSCdv02386

DFM should have simple function for changing IsManaged state for Access Ports

The DFM default for the IsManaged attribute for switch Access Ports is False.

This IDU provides a new function for performing bulk manage operations. For more information, refer to the online help by selecting Device Fault Manager > User Guide > Working with DFM Groups and Settings > Default Polling and Threshold Groups > Default Threshold Groups.

CSCdz20700

Unmanage logical ATM/FrameRelay interfaces

When DFM detected any instance of ifTable to be AdministrativelyUp or OperationallyDown, it generated an alarm for each interface. Although Patch/IDU 1.2.7 changed this behavior so that DFM does not manage logical ATM/FrameRelay interfaces, this bug was reopened to research an easier way to manage groups of interfaces/ports based on any criteria.

DFM now unmanages the ports and shows the correct data.

CSCin76776

Need ability to turn off interface ping test

DFM did not provide the ability to disable ICMP (ping) polling without also disabling SNMP (availability) polling.

This IDU provides a new function for disabling only ICMP polling. For more information, refer to the online help by selecting Device Fault Manager > User Guide > Polling > ICMP Polling > Disabling ICMP Polling.

CSCdz69748

1721 does not support RepeatedRestarts alarm.

DFM Patch/IDU 1.2.4 added support for the Cisco 1721, but DFM did not report the RepeatedRestarts alarm because the device did not generate cold start and warm start traps.

DFM now reports RepeatedRestarts on the Cisco 1721.

CSCsa03070

Catalyst 2970-24 does not generate DuplicateIP event

DFM Patch/IDU 1.2.6 added support for the Catalyst 2970-24, but DFM did not report DuplicateIP events for the device.

DFM now reports DuplicateIP events on the Catalyst 2970-24.

CSCdz68098

3631 CurrentUtilization for FE interface is grayed out.

DFM Patch/IDU 1.2.4 added support for the Cisco 3631, but DFM does not report CurrentUtilization for FE interfaces because the ifX table is not completely implemented.

DFM now correctly reports Current Utilization for these interfaces on the Cisco 3631.

CSCsa18753

Content Engines memory components not created

Memory components were created for Cisco Content Engine devices This is because the hrstoragetype attribute is returning incorrect values.

DFM now creates the necessary memory components.

Table 12 Problems Resolutions Inherited from Patch/IDU 1.2.8

Bug ID

Summary

Explanation

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. With Patch/IDU 1.2.5 installed, if DFM could not correctly determine the duplex mode setting of a port/interface, it disabled all utilization and attribute rates. No duplexity was reported (eliminating HighUtilization alarms).

DFM now uses a new algorithm to determine duplexity (this information has been added to the user guide provided in the online help, where the Performance Exception is discussed):

Logical interfaces with ifType:166 (MPLS) are now unmanaged by default.

CSCed09810

Cannot change trap community string

DFM did not provide the capability to configure the community string in the trap Protocol Data Unit (PDU). All traps generated by DFM contained a public community string. DFM did not provide the capability to change this configuration.

Users can now change the community string by using the command line to modify the configuration files for the Trap Notifier Adapter and the SNMP Trap Adapter. For more information, see the online help by clicking the Help button and selecting either of the following:

DFM was not reporting CPU utilization for PIX Firewalls because the algorithm used by DFM created the proper instrumentation when:

•cpmCPUTotalPhysicalIndex was nonzero, or

•The OLD-CISCO-CPU-MIB was supported.

For PIX Firewalls, cpmCPUTotalPhysicalIndex is always 0, and PIX Firewalls do not support OLD-CISCO-CPU-MIB.

DFM still polls cpmCPUTotalPhysicalIndex, but the value of cpmCPUTotalIndex is verified instead. cpmCPUTotalIndex is used as the index to make the processor.

CSCed88986

Cannot connect to DFM server when NMSROOT system property attribute not set

The Administration and Monitoring Consoles could not connect to the DFM server. This occurred when the system properties NMSROOT attribute was not set.

This problem no longer occurs.

Table 13 Problems Resolutions Inherited from Patch/IDU 1.2.7

Bug ID

Summary

Explanation

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 help for more information.)

CSCec52269

NCM integration script fails because IDUs reregister DFM process

During Patch/IDU 1.2.5 and 1.2.6 installations, DFM processes were re-registered. This impacted customers who performed NCM integration, because domain name changes were lost when domain names reverted to DFM.

This problem no longer occurs.

CSCsa03510

Cannot launch DFM on Netscape clients

DFM occasionally failed to launch any consoles on Netscape clients when integrating VHM 1.0 with either of the following versions of DFM:

•DFM 1.2 with Patch/IDU 1.2.3

•DFM 1.2 Updated for Common Services Version 2.2

This problem occurred because VHM 1.0 did not have the security mechanism introduced in DFM 1.2 (and later versions). To disable this security, during DFM installation, the installation software asked if the user wanted to connect to VHM 1.0. If the user answered Yes, two files (clientConnect.conf and serverConnect.conf) were populated with information that disabled the security checks. Netscape browsers could not launch DFM consoles because the browsers could not correctly parse the information.

DFM now successfully launches its consoles on Netscape clients.

CSCeb12662

Layer 3 device port/interface handling is incorrect

When an IP address was assigned to a port on the Catalyst 4506 running IOS (with Sup III), DFM displayed it as both a port and an interface. An earlier IDU provided a fix for this problem, but only for a limited group of devices.

All multilayer switch ports, to which IP addresses are assigned, are now properly modeled as interfaces.

CSCdx64809

DFM should unmanage voice interfaces/ports

In IOS devices running the SRST (Survivable Remote Site Telephony) 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 was treating 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 1.2 (and earlier versions) 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.

CSCeb03291

RSM, MSFC not deleted when removed from the switch

DFM retained deleted device components in its network and did not update the DFM repository to exclude nonexistent devices and components.

DFM no longer retains deleted device components in its repository.

CSCeb31587

Default SNMP timeout setting unrealistically low in GUI

The default SNMP timeout defined in DFM was 700 milliseconds for all polling types, which was unrealistically low.

The SNMP timeout can now be set between 1 and 60,000 milliseconds.

CSCeb22215

Unmanaged interfaces not removed from Polling & Thresholds Console

An earlier IDU provided a new method for unmanaging interfaces with a new setting called "Disable Port/Interface Analysis." However, when a user unmanaged a previously managed interface, the interface was removed from the Monitoring and Administration Consoles, but not from the Polling and Thresholds Console.

The interfaces are now properly removed from all consoles.

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.

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.

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.

CSCeb17924

Qmail cannot process mail messages from DFM

Qmail could not process DFM e-mail messages or pages. This problem no longer occurs.

CSCea30379

DFM incorrectly reports CSS-11506 free memory

DFM was reporting insufficient memory alarms for the blades of some Content Switches because the cards are internal and have no memory on them.

DFM will not report these errors (by unmanaging the cards) if it finds that no memory is configured in the module. This applies to modules 7 and 8 on the CSS11506 and module 4 on the CSS11503.

CSCdw43966

Undiscovered MSFC does not correctly go back when re-added

If a switch with an MSFC was added to DFM, and the switch and MSFC have different community strings, DFM was not able to discover the MSFC. By default, DFM used the parent switch community string as the MSFC community string. Users had to rediscover the MSFC; users were also advised to add the parent device before adding the MSFC.

Switches with MSFCs are now discovered correctly.

CSCdt15420

DFM incorrectly classifies MSFC/RSFC/RSM IP added individually

When an MSFC/RSFC/RSM IP address was added to DFM, but the parent switch IP address had not yet been added, the MSFC/RSFC/RSM was discovered but added only in the IP class.

MSFCs, RSFCs, and RSMs are now classified correctly.

CSCdz71499

DFM reports Catalyst 6000 IDSM blade as undiscovered

When a Catalyst 6000 with an IDSM blade was added to DFM, DFM reported the blade as Undiscovered. This error occurred because IDSM blades do not support SNMP.

DFM no longer tries to discover the IDSM blade, which is shown as a card in the parent switch.

CSCea57208

SmartsRestartable handler occasionally blocks and reattaches

During heavy processing, the calls to DFM and VHM were sometimes blocked. This error occurred when inconsistent message streams were sent to the server, the connection was reset by the peer, or an out-of-memory exception occurred.

smNotifInstance is now populated. smNotifCertainty is always 100% for active events and 0 for clear events; more granularity is not reported because it is not helpful to the user. (This information has been added to the online version of the User Guide for Device Fault Manager.)

CSCeb71022

GUI refresh problem after rediscovering rebooted device

The Monitoring Console showed an incorrect display name after rebooting and rediscovering a GSR router (the reboot shuffled the ifIndex).

This problem no longer occurs.

CSCdz09238

Cannot resize the Monitoring Console columns

Users could not resize the columns in the Monitoring Console. The columns can now be resized.

Table 15 Problem Resolutions Inherited from Patch/IDU 1.2.5

Bug ID

Summary

Explanation

CSCdw23386,CSCdy83378,CSCdv53038,CSCdw91367

Improve ISDN modeling

These problems have been fixed through the improved ISDN interface model provided with this patch/IDU. For more information, see:

When a port on a device that supports both Layer 2 and Layer 3, such as a Sup card running IOS, is assigned an IP address, it was displayed in the DFM admin console under both interface and port. It should only be displayed under interface.

This fix also applies to the following devices:

•Catalyst C2955C-12

•Catalyst C2955T-12

•Catalyst C4506-with-Sup

•Catalyst C4507-with-Sup

•Catalyst C4503-with-Sup

•Catalyst C3550-24-PWR

•Catalyst C2955S-12

•WS-C2950ST-24-LRE

CSCdy60517

When DFM is launched, stdout.log displays password in clear text

When DFM 1.2 was launched with password set for client, it showed up as clear text in the stdout.log. The password is no longer displayed.

CSCdz87740

New sm_snmpwalk should be part of the DFM image

A new sm_snmpwalk utility that generates the walk in .mimic, .walk and .snap format is now included in NMSROOT/objects/new_snmpwalk/. Customers are encouraged to use this tool when providing mibwalks for debugging and support purposes.

CSCdw35365

Admin and Monitoring Consoles do not display proper names

The Administration and Monitoring consoles were displaying incorrect names in their title bar. For example, the title bar of the Administration console used to read "http://<IPaddress>/dfm/SmAdminApp.jsp". The title bar has been fixed to read "Device Fault Manager - Administration Console".

This problem no longer occurs.

CSCdz09981

DFM Name Resolution fails if devices are in different DNS domain

DFM was not using the fully qualified domain name entered in the Essentials Inventory Device Name and Domain Name fields for name resolution.

After adding a Catalyst device running IOS, Gigabit Ethernet GE1/1 and GE1/2 interfaces were displayed in both the Interface and Port groups.

This behavior occurred because when you assigned an IP address to a port on a Catalyst switch, and the Catalyst switch was running the IOS operating system, DFM created an object in both the Port and Interface classes. The object in the Interface class represented a logical entity that DFM used to maintain connectivity information.

This behavior has been fixed. Now, when a port has an IP address assigned to it, DFM will only display it in the interface group. It will not be displayed in the ports group.

CSCdx32239

Incorrect duplexity shown for router and switch interfaces and ports

DFM was not always reporting the correct duplexity for router and switch interfaces. One reason this happened was because of the assumptions DFM made when the port or interface duplexity was reported as UNSPECIFIED.

In sysConfigChange traps, DFM was incorrectly translating the sysConfigChangeTime, sometimes showing dates instead of a length of time since the last configuration change.

Because there is currently no function that can map the MIB attribute SysConfigChangeTime to a time format consisting of hours/minutes/seconds, DFM will no longer display this MIB attribute in the sysConfigChange trap.

CSCdx27739

DFM allows adding same device with two IP addresses

If a device was in the Undiscovered class, it was possible to add the same device to DFM using two different IP addresses.

This problem no longer occurs.

CSCdz73265

oid2type.conf needs text fixes

The DFM oid2type.conf file had several typographical errors.

The typographical errors have been fixed.

CSCea24977

3725 SystemObjectID is incorrect

The SystemObjectID was incorrect for the 3725.

This problem has been fixed.

CSCea19690

Remove device support for Cisco 7160

The Cisco 7160 was being supported even though it was never shipped. The device support has been removed.

Table 16 Problem Resolutions Inherited from Patch/IDU 1.2.4

Bug ID

Summary

Explanation

CSCdy27270

DFM 1.2.1 shows false PowerSupplyException for Cat3550

DFM 1.2 with Patch/IDU 1.2.1 displayed a power supply OperationalException for the Catalyst 3550, even though running the 'sh env all' command confirms that the power supply does not have any problems.

DFM no longer displays this exception.

CSCdy77106

DFM needs to add support of Layer 3 Cat4006-SUP3 (WS-X4014)

DFM 1.2 did not support the Cisco Catalyst Supervisor Engine III on the Catalyst 4006. This patch/IDU adds this support.

Table 17 Problem Resolutions Inherited from Patch/IDU 1.2.3

Bug ID

Summary

Explanation

CSCdx55823

DFM domain goes down when restarted after January 2004

If the date on the DFM server machine was changed to the year 2004 and the machine was restarted, the DFM domain manager would go down.

When using DFM to view details of a HighUtilization event, the utilization shown was sometimes abnormally high (sometimes much higher than 100%).

This problem no longer occurs. Note the following scenarios that may affect how DFM reports utilization:

•Some Cisco devices may not have the required SNMP instrumentation to determine CurrentUtilization, in which case DFM will not display CurrentUtilization information.

•Some Cisco devices may not have the required SNMP instrumentation to determine the duplex mode of a port, in which case DFM will assume the duplex mode is half duplex when calculating CurrentUtilization. (When this occurs, the DFM Inventory Browser will display UNSPECIFIED.) If CurrentUtilization ever exceeds 100%, DFM will change this assumption and consider the mode of the port to be full duplex from that point on.

CSdx81905

The SNMP Trap Notifier MIB should include the IP address of device

The agentIpAddress in the DFM SNMP Trap Notifier MIB contained the IP address of DFM, not the IP address of the device.

The device name of the impacted device is now available from the Description field of the varbind.

CSdw43543

Card description should show module type and module number

In DFM, the card description field was empty. (Voice Health Monitor requires the card module type and module number so it can display these values in the Real Time Dashboard.)

This problem no longer occurs (unless the device does not support the CISCO-STACK-MIB).

CSdw64867

DFM periodically stops forwarding traps to HPOV/NNM after a few days

DFM occasionally stopped forwarding traps to HP OpenView or NetView after a few days of normal operation. This occurred when subscription profile information was lost due to a lag between when the Trap Notifier Adapter process started, and when the adapter actually connected to the server. This lag occurred when:

•The Trap Notifier Adapter was configured to start upon system reboot.

•The Trap Notifier Adapter was configured to start upon system reboot AND the DFM server had a large repository to restore.

This problem no longer occurs.

CSdw78953

DfmFileNotifier periodically stops writing file log

The DFM File Notifier Adapter occasionally stopped writing to the alarm log file. This occurred when subscription profile information was lost due to a lag between when the File Notifier Adapter process started, and when the adapter actually connected to the server. This lag occurred when:

•The File Notifier Adapter was configured to start upon system reboot.

•The File Notifier Adapter was configured to start upon system reboot AND the DFM server had a large repository to restore.

This problem no longer occurs.

CSdx51688

CurrentUtilization attributes are not displayed

DFM was not displaying the Current Utilization for many serial interfaces, even though the interfaces were managed and operational.

This problem no longer occurs.

Table 19 Problem Resolutions Inherited from Patch/IDU 1.2.1

Bug ID

Summary

Explanation

CSCdx57088

Rediscovery on unresponsive Media Gateway Host deletes SNMPAgent

After rediscovery of an unresponsive Host device, DFM would delete the SNMP Agent object. This would cause applications that depend on DFM (such as Voice Health Monitor) to fail because DFM no longer provided the agent address and community string.