Table Of Contents
Status of DFM Device Agent Bugs (DFM 1.x and DFM 2.x)
Status of DFM Device Agent Bugs (DFM 1.x and DFM 2.x)
Revised: 30 June 2006
Table 1 lists known problems with how DFM interacts with specific Cisco device agents. To determine whether these bugs are due to a problem with DFM or a problem with a device SNMP agent, bugs have been opened against both DFM and the specific devices.
Table 2 lists the DFM agent-based problems which have been resolved.
This document is updated when a new minor release is made available. Unless a work around is noted in the Description, the bug does not have a resolution.
Note
The base version of DFM 2.0 (shipped with LAN Management Solution 2.5) includes all device support through DFM 1.2.8. The base version of DFM 2.0.3 (shipped with LAN Management Solution 2.5.1) includes all device support through DFM 2.0 Service Pack 2, plus some additional devices (see Release Notes for Device Fault Manager 2.0.3 at http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/dfm/dfm203/rel_note/index.htm).
To download the latest minor release (DFM 2.0.5), log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm.
To obtain more information about any of these problems, access the Cisco Software Bug Toolkit by logging into Cisco.com at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl.
Table 2 lists all DFM bugs that have been fixed or closed.
Table 2 Resolved/Closed Problems
CSCsa45317 (2.0.1)
2600/3600 NAM: Port/IF alarms not generated
The 2600/3600 NAM does not compute CurrentUtilization because HighCounter MIBs are not implemented for interfaces with speeds greater than 20 Mbps. A bug has been opened against the 2600/3600 NAM (CSCef18043).
2.0.1
CSCsa60236 (2.0.1)
IGESM does not generate temperature OutOfRange event
The Intelligent Gigabit Ethernet Switch Module (IGESM) does not support the temperature OutOfRange event because it does not support these MIB values:
ciscoEnvMonTemperatureStatusValue ciscoEnvMonTemperatureThreshold
This problem does not occur if the following (or higher) NAM application image is installed:
3.4(1a-Patch-1)
2.0.1
CSCsa59654 (2.0.1)
ONS-15454: HighQueueDropRate event not generated
HighQueueDropRate events are not generated for the ONS-15454 because the device does not support the locIfInputQueueDrops and locIfOutputQueueDrops MIBs. This bug has been closed because the device team does not plan to add this support.
2.0.1
CSCsa60233 (2.0.1)
2821 Integrated Services Router does not generate temperature OutOfRange event
The Cisco 2821 Integrated Services Router does not support the temperature OutOfRange event because it does not support these MIB values:
ciscoEnvMonTemperatureStatusValue ciscoEnvMonTemperatureThreshold
This problem does not occur if the following (or higher) IOS version is installed:
12.3(11)T
2.0.1
CSCsa60234 (2.0.1)
3825 router does not generate temperature OutOfRange event
The Cisco 3825 router does not support the temperature OutOfRange event because it does not support these MIB values:
ciscoEnvMonTemperatureStatusValue ciscoEnvMonTemperatureThreshold
This problem does not occur if the following (or higher) IOS version is installed:
12.3(11)T
2.0.1
CSCsa38656 (1.2.10)
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. This bug has been closed because the device team does not plan to add this support.
2.0.1,
1.2.10CSCsa23445 (1.2.9)
2600/3600 NAM: no network adapter alarms on IFs > 20,000,000 mbps
The 2600/3600 NAM does not compute CurrentUtilization because HighCounter MIBs are not implemented for interfaces with speeds greater than 20 Mbps.
This problem does not occur if the following (or higher) NAM application image is installed:
3.4(1a-Patch-1)
2.0.1,
1.2.9CSCsa26774
(1.2.9)AP 340 does not generate DuplicateIP event
DFM does not report DuplicateIP events for the AP 340 because the IpAddr table is not populated for AP radio interfaces. Although a bug was opened against the AP 340, this DFM bug has been closed because the AP 340 will not have future releases in which this bug can be fixed.
2.0.1,
1.2.9CSCsa36887 (1.2.10)
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.
This problem does not occur if the following (or higher) IOS version is installed:
012.003
2.0.1,
1.2.10CSCsa33726 (1.2.10)
1841: Port/IF alarms not generated
1841 does not implement High Counters MIB. 1841 has two interfaces of type ethernetCsmacd(6) and speed 100000000 and hence the Network adapter related alarms are not generated in DFM.
This problem does not occur if the following (or higher) IOS version is installed:
12.3 PI6
2.0.1,
1.2.10CSCsa47618
Cat 4908-GL3: Not all FE events are generated
DFM only generates the HighUtilization event for FE interfaces on the Cat 4980-GL3. These events are not generated: HighDiscardRate, HighQueueDropRate, HighCollisionRate, HighBroadcastRate, HighErrorRate. This bug was closed because the Cat 4908-GL3 will not have future releases in which this bug can be fixed.
2.0.1,
1.2.9CSCin72033
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.
This problem does not occur if the following (or higher) ACNS versions are installed:
005.001(003.001), 005.002(000.002)
1.2.8
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. This problem was fixed in patch/IDU 1.2.10, which introduced a new symptom called InvalidResponse (see CSCsa26950 using the Bug Navigator, as described at the beginning of this document). (This problem still exists in DFM 2.0; see CSCin86757). To download the latest patch/IDU, log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
1.2.8
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. This problem was fixed in patch/IDU 1.2.10, which introduced a new symptom called InvalidResponse (see CSCsa26950 using the Bug Navigator, as described at the beginning of this document). (This problem still exists in DFM 2.0; see CSCin86757). To download the latest patch/IDU, log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
1.2.8
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. This problem was fixed in patch/IDU 1.2.10, which introduced a new symptom called InvalidResponse (see CSCsa26950 using the Bug Navigator, as described at the beginning of this document). (This problem still exists in DFM 2.0; see CSCin86757). To download the latest patch/IDU, log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
1.2.8
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.
This problem does not occur if the following (or higher) ACNS versions are installed:
5.2.0
1.2.8
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.
This problem does not occur if the following (or higher) ACNS versions are installed:
5.2.0
1.2.8,
1.2.6CSCin63245
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.
This problem does not occur if the following (or higher) IOS version is installed:
12.3(11)T3
1.2.7
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. This bug has been closed because the problem was in the testing image.
1.2.7
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. This bug has been closed because the device team does not plan to add this support.
1.2.7
CSCin63477
827H router: SNMPAgent Unresponsive alarm is not generated
After changing the SNMP community string setting in the 827H router, DFM does not report an SNMP Unresponsive alarm. This problem was fixed in patch/IDU 1.2.10, which introduced a new symptom called InvalidResponse (see CSCsa26950 using the Bug Navigator, as described at the beginning of this document). (This problem still exists in DFM 2.0; see CSCin86757). To download the latest patch/IDU, log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
1.2.7
CSCsa07592
Cisco 6260: SNMPAgent Unresponsive alarm is not generated
After changing the SNMP community string setting in the Cisco 6260, DFM does not report an SNMP Unresponsive alarm. This problem was fixed in patch/IDU 1.2.10, which introduced a new symptom called InvalidResponse (see CSCsa26950 using the Bug Navigator, as described at the beginning of this document). (This problem still exists in DFM 2.0; see CSCin86757). To download the latest patch/IDU, log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
1.2.7
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.
This problem does not occur if the following (or higher) IOS versions are installed:
12.3(07.02)T, 012.003(007.002)
1.2.7
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.
This problem does not occur if the following (or higher) IOS versions are installed:
1.3(1.12), 2.0(0.18)
1.2.7
CSCin58260
10720 does not report RepeatedRestarts
It was thought that the 10720 router did not support the RepeatedRestarts alarm because the device did not generate cold start and warm start traps. This bug was closed since it was not a problem with the device, but with the trap viewer.
1.2.6
CSCsa02822
uBR 7246VXR: SNMPAgent Unresponsive alarm not generated
After changing the SNMP community string setting in the uBR 7246VXR, DFM does not report an SNMP Unresponsive alarm. This problem was fixed in patch/IDU 1.2.101, which introduced a new symptom called InvalidResponse (see CSCsa26950 using the Bug Navigator, as described at the beginning of this document). (This problem still exists in DFM 2.0; see CSCin86757). To download the latest patch/IDU, log in to Cisco.com and point your browser to: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-dfm
1.2.6
CSCsa03070
Catalyst 2970-24 does not generate DuplicateIP event
DFM does not report DuplicateIP events for the Catalyst 2970-24.
This problem does not occur if the following (or higher) IOS version is installed:
12.1(19)EA1
1.2.6
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.
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.2(16.01)T
1.2.5
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.
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.2(16.01)T
1.2.5
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.) This bug has been closed because the problem was due to an outdated image.
1.2.4
CSCdz69718
3631 does not support RepeatedRestarts alarm.
The Cisco 3631 does not support the RepeatedRestarts 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.
This bug has been closed and will be reopened if/when a customer reports this problem.
1.2.4
CSCdy69761
3640: high utilization for serial interface is over 100%
The Cisco 3640 interface utilization computation is erroneous, sometimes resulting in utilization values over 100%.This bug has been closed because the problem was due to an outdated image.
1.2.4
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.)
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(16)BX, 12.3(00.05)BW0,3 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.3(14.06)PI01, 12.3(14.06)PI00, 12.2(14.06)T
1.2.4
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.)
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.3(14.06)PI01, 12.3(14.06)PI00, 12.2(14.06)T
1.2.4
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.)
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.3(14.06)PI01, 12.3(14.06)PI00, 12.2(14.06)T
1.2.4
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.)
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.2(16.01)T
1.2.4
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.)
This problem does not occur if the following (or higher) IOS version is installed:
12.2(11)JA
1.2.4
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.
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(17a)SX, 12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.3(14.06)PI01, 12.2(15.01)S, 12.3(14.06)PI00, 12.2(14.06)T, 012.002(015.001)
1.2.4
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.
This problem does not occur if the following (or higher) IOS versions are installed:
12.2(17a)SX, 12.2(16)BX, 12.3(00.05)BW03, 12.2(16)B, 12.2(15)ZN, 12.2(16.01)B, 12.3(14.06)PI01, 12.2(15.01)S, 12.3(14.06)PI00, 12.2(14.06)T, 012.002(015.001)
1.2.4
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.
This problem does not occur if the following (or higher) NAM software version is installed:
003.001(000.016)
1.2.4
Guest
