Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

VSS and ciscoEnvMonSupplyState

Hi,

We are using two cat 6500with one IP address as using VSS. We use ciscoEnvMonSupplyState to check the state of PSU's and we get wrong information state of second switch's PSU as not functioning.

We are looking at CSCso57334 and we are using s72033-adventerprisek9_wan-mz.122-33.SXH4.bin.

Is there a way to fix this issue or is there any IOS recommended for fix.

Thanks.

5 REPLIES
Cisco Employee

Re: VSS and ciscoEnvMonSupplyState

The bug is triggered when a PS is removed from one of the switches in the VSS. If that is happening for you, the workaround is to re-insert the PS.

The fix for this is in 12.2(33)SXI.

New Member

Re: VSS and ciscoEnvMonSupplyState

Hi,

We have just implemented it and have not removed the PS. But even then it shows the wrong information.

The OID that we're querying is:

1.3.6.1.4.1.9.9.13.1.5.1.3

It's currently reporting 4 instances.

.11 = 1 (Normal)

.12 = 1 (Normal)

.201 = 6 (Not Functioning)

.202 = 6 (Not Functioning)

is there any solution to it.

It looks like SXI is based on SXH3a, not SXH4. So I'm not sure that we'll want to upgrade to SXI at this time, as we had to go to SXH4 to fix bugs we were experiencing in SXH3. (ones causing much more impact than lack of correct SNMP responses).

Thanks for help!

Cisco Employee

Re: VSS and ciscoEnvMonSupplyState

Are all of the power supplies present in the VSS? Are they all on?

New Member

Re: VSS and ciscoEnvMonSupplyState

Hi,

Yes they all are on.

thanks for help.

Cisco Employee

Re: VSS and ciscoEnvMonSupplyState

If the VSS hasn't failed over, and the PS have not been removed or turned off since powering on the switches, then you may be seeing a different bug.

Based on what I have read from this bug, a reboot of the VSS should restore the correct status (if it is this bug). The only fix is to upgrade to 12.2(33)SXI or higher.

272
Views
0
Helpful
5
Replies