Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1523
Views
0
Helpful
13
Replies

LMS 3.2 /DFM 3.2.0 - DDV report a unknown status on 45xx series

Go to solution
richard.tetu
Level 1
Level 1

‎12-04-2009 03:19 AM

Hello Dears all,

a DDV report has send a unknown status while the package has been loaded on both kind of routers.

- 4506

- 4507r

The status has reported is "Other" . I have attached the snapshot . It concerns Fan and Power Supply.

The test made , is , as the Power supply are implemented with redundancy, to power off one of the both.

I have made him  a snmp walk on equipements, for get the exact mib description.

1.3.6.1.4.1.9.1.876 and .502 have been  supported. The device package is the Cat4000IOS version 7.2

My end user has experimented this default on anothers machines.

Does the bug CSCsz77616 can be applied for that ?

Is the DDV.Log and Interact.log could be shows us something ?

Thanks

Labels:
Preview file
217 KB
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to richard.tetu

‎12-18-2009 10:28 AM

EMC is the vendor who writes the polling engine for DFM.  We OEM the Smarts InCharge engine as the underlying components of DFM.

View solution in original post

0 Helpful
13 Replies 13

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee

‎12-04-2009 02:43 PM

Device packages and sysObjectIDs don;t have any bearing on this issue.  DFM is reporting that the status of this PS is "OTHER" which is most likely what is getting reported by the device.  Post an SNMP Walk of the ciscoEnvMonMIB branch.

0 Helpful

Go to solution
richard.tetu
Level 1
Level 1
In response to Joe Clarke

‎12-07-2009 05:30 AM

Hello, Joe

The SNMP walk has been launched.

On a 4506 type:

SNMP Walk Output
--------------------------------------------------------------------------------
.1.3.6.1.4.1.9.9.13

CISCO-ENVMON-MIB::ciscoEnvMonPresent.0 = INTEGER: cat4000(9)
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureStatusDescr.1 = STRING: Chassis Temperature Sensor
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureStatusValue.1 = Gauge32: 36 degrees Celsius
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureThreshold.1 = INTEGER: 95 degrees Celsius
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureLastShutdown.1 = INTEGER: 0 degrees Celsius
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureState.1 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonFanStatusDescr.1 = STRING: Chassis Fan Tray 1
CISCO-ENVMON-MIB::ciscoEnvMonFanStatusDescr.2 = STRING: Power Supply 1 Fan
CISCO-ENVMON-MIB::ciscoEnvMonFanStatusDescr.3 = STRING: Power Supply 2 Fan
CISCO-ENVMON-MIB::ciscoEnvMonFanState.1 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonFanState.2 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonFanState.3 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonSupplyStatusDescr.1 = STRING: Power Supply 1
CISCO-ENVMON-MIB::ciscoEnvMonSupplyStatusDescr.2 = STRING: Power Supply 2
CISCO-ENVMON-MIB::ciscoEnvMonSupplyState.1 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonSupplyState.2 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonSupplySource.1 = INTEGER: ac(2)
CISCO-ENVMON-MIB::ciscoEnvMonSupplySource.2 = INTEGER: ac(2)
CISCO-ENVMON-MIB::ciscoEnvMonAlarmContacts.0 = BITS: 00
CISCO-ENVMON-MIB::ciscoEnvMonEnableShutdownNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableTemperatureNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableFanNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableRedundantSupplyNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableStatChangeNotif.0 = INTEGER: false(2)

On 4507R-E equipement

The following is a SNMP walk of device 172.xx.xx.xx starting from .1.3.6.1.4.1.9.9.13

SNMP Walk Output
--------------------------------------------------------------------------------
.1.3.6.1.4.1.9.9.13

CISCO-ENVMON-MIB::ciscoEnvMonPresent.0 = INTEGER: cat4000(9)
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureStatusDescr.21 = STRING: Chassis Temperature Sensor
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureStatusValue.21 = Gauge32: 35 degrees Celsius
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureThreshold.21 = INTEGER: 95 degrees Celsius
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureLastShutdown.21 = INTEGER: 0 degrees Celsius
CISCO-ENVMON-MIB::ciscoEnvMonTemperatureState.21 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonFanStatusDescr.1 = STRING: Chassis Fan Tray 1
CISCO-ENVMON-MIB::ciscoEnvMonFanStatusDescr.2 = STRING: Power Supply 1 Fan
CISCO-ENVMON-MIB::ciscoEnvMonFanStatusDescr.3 = STRING: Power Supply 2 Fan
CISCO-ENVMON-MIB::ciscoEnvMonFanState.1 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonFanState.2 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonFanState.3 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonSupplyStatusDescr.1 = STRING: Power Supply 1
CISCO-ENVMON-MIB::ciscoEnvMonSupplyStatusDescr.2 = STRING: Power Supply 2
CISCO-ENVMON-MIB::ciscoEnvMonSupplyState.1 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonSupplyState.2 = INTEGER: normal(1)
CISCO-ENVMON-MIB::ciscoEnvMonSupplySource.1 = INTEGER: ac(2)
CISCO-ENVMON-MIB::ciscoEnvMonSupplySource.2 = INTEGER: ac(2)
CISCO-ENVMON-MIB::ciscoEnvMonAlarmContacts.0 = BITS: 00
CISCO-ENVMON-MIB::ciscoEnvMonEnableShutdownNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableTemperatureNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableFanNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableRedundantSupplyNotification.0 = INTEGER: false(2)
CISCO-ENVMON-MIB::ciscoEnvMonEnableStatChangeNotif.0 = INTEGER: false(2)

Thanks

Richard

0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to richard.tetu

‎12-07-2009 11:39 AM

This looks okay, but I see no evidence that these SNMP walks line up with the device being shown in DFM.

Start a sniffer trace filtering on SNMP traffic to this same switch seen in the posted DDV screenshot.  Let it run for eight minutes.  Stop the trace, then post the capture file.

0 Helpful

Go to solution
richard.tetu
Level 1
Level 1
In response to Joe Clarke

‎12-17-2009 07:37 AM

Please see after the both snmp trace :

  • from the power supply when she is ok
  • from "       "         "      "       she isn't

An oid has been sending back with ( an 2ND trace)

name: 1.3.6.1.4.1.9.9.13.1.5.1.3.2 (SNMPv2-SMI::enterprises.9.9.13.1.5.1.3.2)

with this value :

Value: INTEGER: 6

What is these value ?

36965-Snmp avec alimentation ok.pcap.zip
0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to richard.tetu

‎12-17-2009 09:08 AM

The object in question is ciscoEnvMonSupplyState, and a value of 6 indicates the PS is not functioning.  It may be that DFM doesn't have the latest information about he allowed values of this object, so it displays OTHER instead of a more specific fault condition.

0 Helpful

Go to solution
richard.tetu
Level 1
Level 1
In response to Joe Clarke

‎12-18-2009 12:08 AM

Thanks Joe for the last information .

Should i open a case to the TAC for having at least a view of the DFM code ?

I think that it will be the best for having maybe a patch.

The problematic is that my end user can't launch snmp debug on the equipement as it's an heart of network.

Richard

0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to richard.tetu

‎12-18-2009 05:27 AM

Yes, a service request should be opened.  The problem does not appear to be with the Cisco code in DFM, but rather with the underlying EMC engine.

0 Helpful

Go to solution
richard.tetu
Level 1
Level 1
In response to Joe Clarke

‎12-18-2009 05:51 AM

what do you mean by EMC ?

0 Helpful

Go to solution
Joe Clarke
Cisco Employee
Cisco Employee
In response to richard.tetu

‎12-18-2009 10:28 AM

EMC is the vendor who writes the polling engine for DFM.  We OEM the Smarts InCharge engine as the underlying components of DFM.

0 Helpful

Go to solution
richard.tetu
Level 1
Level 1
In response to Joe Clarke

‎01-06-2010 01:01 AM

Thanks Joe.

I will open a case to the TAC.

Richard

0 Helpful

Go to solution
richard.tetu
Level 1
Level 1
In response to richard.tetu

‎04-19-2010 07:51 AM

Hello Dears all, Hello Joe,

I appologize to update this thread so lately.

I have opened an SR and we finally found that is a bug

Subject:

The DFM 3.2 don't report alarm when a 4500 series power supply is switched off.

The state reported is "OTHER"

The value send back is "6" in the CISCO-ENV-MIB in the snmp protocol.

The bug referenced is CSCtg29656 .

It will be available for details  in few days.

Thanks

Richard

0 Helpful

Go to solution
mmimmi2005
Level 1
Level 1
In response to richard.tetu

‎09-22-2010 07:11 AM

Hey Richard

Any news on that? We have the same problem here. All patches and updates installed, but we don't get any Alert in the dfm if a device power supply fails... Happens with 4500 and 6500, it worked once...

regards

Stefan

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents