Guest

CiscoWorks Device Fault Manager

Status of DFM Device Agent Bugs (DFM 1.x and DFM 2.x)

  • Viewing Options

  • PDF (300.5 KB)
  • Feedback
Status of DFM Device Agent Bugs (DFM 1.x and DFM 2.x)

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 1 Known Problems Under Investigation 

Bug ID
Summary
Explanation
Supported in DFM...

CSCsd10237
(2.0.4)

Cisco 1801, 1802, 1811: Temperature OutOfRange events not generated

DFM does not report temperature OutOfRange events for the Cisco 1801, 1802, or 1811 because the following OIDs are not implemented in the devices:

ciscoEnvMonTemperatureStatusValue: .1.3.6.1.4.1.9.9.13.1.3.1.3 ciscoEnvMonTemperatureThreshold: .1.3.6.1.4.1.9.9.13.1.3.1.4

A bug has been opened against these devices (CSCsd45881).

2.0.4

CSCsd64093
(2.0.4)

3750 devices: Temperature StateNotNormal events not generated

DFM 2.0.4 does not report temperature StateNotNormal events for these devices: 3750-24FS, 3750-24PS, 3750-24TS, 3750-48PS, 3750G-16TD, 3750G-24PS, 3750G-24TS1U, 3750G-48PS, 3750G-48TS.

This is because the ciscoEnvMonTemperature object is incorrectly implemented. A bug has been opened against the devices (CSCsd88978).

2.0.4

CSCsd70857
(2.0.4)

3750 devices: Temperature components are not managed or displayed

DFM 2.0.4 does not manage or display any temperature components for the following 3750 devices: 3750-24FS, 3750-24PS, 3750-24TS, 3750-48PS, 3750G-16TD, 3750G-24PS, 3750G-24TS1U, 3750G-48PS, 3750G-48TS.

This is because the ciscoEnvMonTemperature object is correctly implemented. A bug has been opened against the devices (CSCsd88978).

2.0.4

CSCsb57133
(2.0.3)

857 router does not report RepeatedRestarts

The 857 router does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps. A device agent bug will be opened. There is no workaround.

2.0.3

CSCsa82905
(2.0.2)

CE-511: Port/interface alerts not generated

The CE-511 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 CE-511 (CSCeh60145). There is no workaround.

2.0.2

CSCsa80319
(2.0.2)

IPCC: Port/interface alerts not generated

The IPCC does not compute CurrentUtilization because HighCounter MIBs are not implemented for ETHERNETCSMACD interfaces with speeds greater than 1,000 Mbps. A bug has been opened against the IPCC (CSCeh62329). There is no workaround.

2.0.2

CSCsa83484
(2.0.2)

SB101 does not implement high counter MIBs

The SB101 does not compute CurrentUtilization because HighCounter MIBs are not implemented for PPP interfaces with maxSpeed = 100000000. A device agent bug will be opened. There is no workaround.

2.0.2

CSCsa53657
(2.0.2)

1841: Port/IF alarms not generated

The Cisco 1841 does not implement HighCounter MIBs. The 1841 has two interfaces of type ethernetCsmacd(6) with speeds of 100,000,000; therefore, the network adapter-related events are not generated. A device agent bug will be opened. There is no workaround.

2.0.2

CSCsa62858
(2.0.1)

WLSE 1030 does not report RepeatedRestarts

The WLSE 1030 does not support the RepeatedRestarts fault because the device does not generate cold start and warm start traps. A bug has been opened against the WLSE 1030 (CSCsa68834).

2.0.1

CSCsa63372 (2.0.1)

WLSE 1030 reports SNMP Unresponsive after switchover

When a WLSE 1030 switchover occurs (from active to standby), the device becomes unresponsive and may remain unresponsive for several hours. A bug has been opened against the WLSE 1030 (CSCsa68849).

2.0.1

CSCsa64376 (2.0.1)

WLSE: Switchover time is not updated after consecutive switchovers

The value for switchover time is not updated after consecutive WLSE switchovers. This is due to a device agent problem. A bug has been opened against the WLSE (CSCsa68778).

2.0.1

CSCsa45304 (2.0.1)

MWR-1900: Port/IF alarms not generated

The MWR-1900 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 MWR-1900 (CSCsa13224).

2.0.1

CSCsa60229 (2.0.1)

MWR-1900 does not generate temperature OutOfRange event

The MWR-1900 does not support the temperature OutOfRange event because it does not support these MIB values:

ciscoEnvMonTemperatureStatusValue ciscoEnvMonTemperatureThreshold

A bug has been opened against the MWR-1900 (CSCsa68907).

2.0.1

CSCsa45853 (2.0.1)

CDM 4630/4650: Port/IF alarms not generated

The CDM 4630 and 4650 do not compute CurrentUtilization because HighCounter MIBs are not implemented for interfaces with speeds greater than 20 Mbps. A bug has been opened against these devices (CSCeh29440).

2.0.1

CSCsa47035 (2.0.1)

CE-2636: Port/IF alarms not generated

The CE-2636 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 CE-2636 (CSCeg61459).

2.0.1

CSCsa60235 (2.0.1)

Cat 6500 CMM does not generate temperature OutOfRange event

The Communications Media Module (for the Catalyst 6500) does not support the temperature OutOfRange event because it does not support these MIB values:

ciscoEnvMonTemperatureStatusValue ciscoEnvMonTemperatureThreshold

A bug has been opened against the CMM (CSCsa68930).

2.0.1

CSCsa53666 (2.0.1)

Cat 4948: Port/IF alarms not generated

The Catalyst 4948 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 Catalyst 4948 (CSCeg81421).

2.0.1

CSCsa55521 (2.0.1)

CSCsa36885 (1.2.10)

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. A bug has been opened against the WS-SVC-CMM (CSCin83708).

2.0.1,
1.2.10

CSCsa23167
(1.2.9)

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. A bug has been opened against the MWR 1900 (CSCeb20376).

2.0.1,
1.2.9

CSCsa25319
(1.2.9)

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. A bug has been opened against the CDM-4630 (CSCee94244).

2.0.1,
1.2.9

CSCsa22854
(1.2.9)

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. A bug has been opened against the 4908G-L3 (CSCee76829).

2.0.1,
1.2.9

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. A bug has been opened against the MWR-1941-DC (CSCeb20376).

1.2.8

CSCsa13224

MWR-1941-DC does not generate FE HighUtilization, HighQueueDropRate, HighCollisionRate, HighErrorRate

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 (CSCin73594).

1.2.8

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. A bug has been opened against the GSS 4490 (CSCin73595).

1.2.8

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 (CSCin73597).

1.2.8

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. A bug has been opened against the 2948-GL3 (CSCin73590).

1.2.8

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. A bug has been opened against the Cisco 3220 (CSCin63022).

1.2.7

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 (CSin63101).

1.2.7

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). A bug has been opened against the ONS 15501-AC (CSCin66271).

1.2.7

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. A bug has been opened against the VPN 3000 (CSCdt01583).

1.2.7

CSCsa07046

ONS 15501-DC does not generate DuplicateIP error

DFM does not report DuplicateIP events for the ONS 15501-DC. A bug has been opened against the ONS 15501-DC (CSCin67711).

1.2.7

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

A bug has been opened against the Cisco 10720 (CSCin60106).

1.2.6

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. A bug has been opened against the ONS 15530 (CSCee24673).

1.2.6

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. A bug has been opened against the CE-7325 (CSCin58529).

1.2.6

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. A bug has been opened against the PIX 535 (CSCea04950).

1.2.4

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. A bug has been opened against the WSC-SVC-NAM-1 and -NAM-2 (CSCef18043).

1.2.4

CSCdx24447

VG200: DFM does not display T1 interfaces

When a VG200 is added to DFM, DFM displays it as Unsupported. In addition, T1 interfaces are not displayed. A device bug will be opened.

1.2

CSCdx34570

Cat6000+MSFC: PowerDown event not getting cleared

The Catalyst 6000 with an MSFC does not clear a power down event after a module is powered down and powered back up. A device bug will be opened.

1.2

CSCdt64368

AS5300: cold/warm start trap not generated

The AS5300 does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps. A device bug will be opened.

1.1

CSCdp88058

7200VXR: cold/warm start trap not generated

The 7200 VXR does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps. A device bug will be opened.

1.0

CSCdt63744

3640: cold/warm start trap not generated

The Cisco 3640 does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps.A device bug will be opened.

1.0

CSCdr00300

8540 MSR: cold/warm start trap not generated

The 8540 MSR does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps. A device bug will be opened.

1.0

CSCdr04559

8540 MSR: duplex info not known

DFM does not correctly compute interface utilization on the 8540 MSR because the device has not correctly implemented the SNMP MIB.A device bug will be opened.

1.0

CSCdr00318

8540 MSR: module down not reported

The 8510 MSR does not generate a card down event after a card is removed. A device bug will be opened.

1.0

CSCdp85901

8510 CSR: module down not reported

The 8510 CSR does not generate a card down event after a card is removed. A device bug will be opened.

1.0

CSCdp85997

8510 CSR: duplex information not generated

DFM does not correctly compute interface utilization on the 8510 CSR. A device bug will be opened.

1.0

CSCdp88115

7200 VXR: module down not reported

The 7200 VXR does not generate a card down event after a card is removed. A device bug will be opened.

1.0

CSCdr57293

Cat6000:%utilization shown as 394.6%

The Catalyst 6000 interface utilization computation is erroneous, sometimes resulting in utilization values over 100%.A device bug will be opened.

1.0

CSCdp68659

7000 router: cold/warm start trap not generated

The Cisco 7000 does not support the RepeatedRestarts alarm because the device does not generate cold start and warm start traps. A device bug will be opened.

1.0


Table 2 lists all DFM bugs that have been fixed or closed.

Table 2 Resolved/Closed Problems

Bug ID
Summary
Explanation
Supported in DFM...

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.10

CSCsa23445 (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.9

CSCsa26774
(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.9

CSCsa36887 (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.10

CSCsa33726 (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.10

CSCsa47618

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.9

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.

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.6

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.

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