Supply Voltage Sensor Alerts in LMS Prime

Farooq Razzaque · ‎01-20-2013

Dear All

I am getting following messages on Cisco prime LMS.

These errors are generating in LMS for the different ports of the folloiwng modules of Cat 6513

1) WS-X6708-10GE

2) WS-Sup720-10GE

3) WS-X6748-GE-TX

OutOfRange::Component=VOLT-10.x.x.x/11067 [Te2/7/5 Supply Voltage Sensor];ComponentClass=VoltageSensor;ComponentEventCode=1080;HighThreshold=5.0;Status=OK;CurrentValue=0.0;

LowThreshold=1.0;entSensorValue=0;RelativeVoltageThreshold=0.0 %

Marvin Rhoads · ‎01-20-2013

Your post reminded me that I am seeing a similar issue with a SolarWinds NPM installation monitoring some 10GBase-SR optics in a 4500X switch running IOS-XE 3.04.00 (equivalent to IOS 15.1(2)).

I've not opened a TAC case but I believe the root cause may be an IOS bug that is incorrectly reporting the transceiver status. I base that on some extended disucssion over in the SolarWinds Thwack user community here.

It would make sense that in the case of an IOS bug any SNMP-based polling tool would report the value as out of range. The switch itself and the links connected via these transceivers are perfectly healthy.

(Depending on your IOS version you may also be hitting related bug CSCtt00490.)

Farooq Razzaque · ‎01-22-2013

Dear Marvin

Thanks for the reply.

In the below thread "Joseph clarke" mentioned that this is known limitation by DFM. Is there any document of DFM which is mentioning this limitation of DFM. I m using Cisco Prime 4.1 LMS

https://supportforums.cisco.com/message/3260929#3260929

Joseph Clarke

Jan 3, 2011 10:43 PM (in response to orsonjoon)

Re: VoltageSensor OutOfRange

This is a known limitation of DFM. Certain GBIC/XenPak modules do not have a voltage sensor. In that case, they will report a voltage of 0 (which is fine). In this case, you can unamange those interface voltage sensors that are not present under DFM > Device Management > Device Details.

I was also going through your discussion int the following post which is having the same error which i m getting

https://supportforums.cisco.com/thread/2127711

Following is the ouput of the show interface transceiver detail of my switch

sh interfaces transceiver detail switch 1
Transceiver monitoring is disabled for all interfaces.

mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.
++ : high alarm, + : high warning, - : low warning, -- : low alarm.
A2D readouts (if they differ), are reported in parentheses.
The threshold values are calibrated.

                                   High alarm High Warn Low Warn   Low Alarm
            Voltage            Threshold   Threshold Threshold Threshold
Port        (Volts)            (Volts)     (Volts)    (Volts)    (Volts)
---------- ---------------    ---------- --------- --------- ---------
Te1/7/4     0.00                   N/A         N/A         N/A        N/A
Te1/7/5     0.00                   N/A         N/A         N/A        N/A
Te1/9/1     0.00                   N/A         N/A         N/A        N/A
Te1/9/2     0.00                   N/A         N/A         N/A        N/A
Te1/9/3     0.00                   N/A         N/A         N/A        N/A
Te1/9/4     0.00                   N/A         N/A         N/A        N/A
Te1/9/5     0.00                   N/A         N/A         N/A        N/A
Te1/9/6     0.00                   N/A         N/A         N/A        N/A
Te1/9/7     0.00                   N/A         N/A         N/A        N/A
Te1/9/8     0.00                   N/A         N/A         N/A        N/A
Te1/10/1    0.00                   N/A         N/A         N/A        N/A
Te1/10/2    0.00                   N/A         N/A         N/A        N/A
Te1/10/3    0.00                   N/A         N/A         N/A        N/A
Te1/10/4    0.00                   N/A         N/A         N/A        N/A
Te1/10/5    0.00                   N/A         N/A         N/A        N/A
Te1/10/6    0.00                   N/A         N/A         N/A        N/A
Te1/10/7    0.00                   N/A         N/A         N/A        N/A
Te1/10/8    0.00                   N/A         N/A         N/A        N/A

                            High Alarm High Warn Low Warn   Low Alarm
            Current            Threshold   Threshold Threshold Threshold
Port        (milliamperes)     (mA)        (mA)       (mA)       (mA)
---------- ----------------- ---------- --------- --------- ---------
Te1/7/4       7.4         --     N/A        N/A        N/A       N/A
Te1/7/5       7.7         --     N/A        N/A        N/A       N/A
Te1/9/1       8.0         --     N/A        N/A        N/A       N/A
Te1/9/2       8.0         --     N/A        N/A        N/A       N/A
Te1/9/3       7.9         --     N/A        N/A        N/A       N/A
Te1/9/4       8.4         --     N/A        N/A        N/A       N/A
Te1/9/5       0.0                N/A        N/A        N/A       N/A
Te1/9/6       0.0                N/A        N/A        N/A       N/A
Te1/9/7       7.8         --     N/A        N/A        N/A       N/A
Te1/9/8       7.9         --     N/A        N/A        N/A       N/A
Te1/10/1      8.1         --     N/A        N/A        N/A       N/A
Te1/10/2      8.1         --     N/A        N/A        N/A       N/A
Te1/10/3      7.8         --     N/A        N/A        N/A       N/A
Te1/10/4      7.4         --     N/A        N/A        N/A       N/A
Te1/10/5      7.9         --     N/A        N/A        N/A       N/A
Te1/10/6      8.1         --     N/A        N/A        N/A       N/A
Te1/10/7      7.7         --     N/A        N/A        N/A       N/A
Te1/10/8      7.7         --     N/A        N/A        N/A       N/A

Marvin Rhoads · ‎01-22-2013

I think the linked threads only add weight to my and other customers' experiences that LMS' Fault application (still mostly DFM or the SMARTS product under the covers) is inconsistent or buggy in its support of transceiver details. Engineers can debate whether this stems from the limitations of the built-in sensors themselves (as Joe asserts) or the product interpreting and presenting the output (as I assert) but the bottom line is that your optical links and transceivers can be operating perfectly fine and the tool reports them as in a fault condition. In my opinion simply ignoring the fault or unmanaging the transceivers is contrary to the whole purpose of network management.

I don't think you'll find a document per se saying that it's a limitation of DFM - unless you count Joe's post (authoritative enough for me - he's a well-known and respected engineer at Cisco). The bug I mentioned hitting on my ASRs was indeed an official bug with Cisco number and all that. That's why I suggest opening your own TAC case to get the need for a fix documented officially at Cisco. That's one big way things get better - customer feedback through the official support channels.

Farooq Razzaque · ‎01-22-2013

Dear Marvin

Thanks for the reply.

Can you please let me know what exact error message you were getting in case of ASR and 4500X switch.

As Joseph mentioned that "Certain GBIC/XenPak modules do not have a voltage sensor. In that case, they will report a voltage of 0 (which is fine). " so it means there is no limitatoin with DFM but the limitation with GBIC/Xenpak modules.

In the following log generated by LMS, from where the following values picked by LMS

HighThreshold=5.0;Status=OK;CurrentValue=0.0; LowThreshold=1.0

OutOfRange::Component=VOLT-10.x.x.x/11067 [Te2/7/5 Supply Voltage Sensor];

ComponentClass=VoltageSensor;ComponentEventCode=1080;HighThreshold=5.0;Status=OK;CurrentValue=0.0;

LowThreshold=1.0;entSensorValue=0;RelativeVoltageThreshold=0.0 %

Marvin Rhoads · ‎01-22-2013

Farooq,

My 4500X errors were reported by SolarWinds NPM. If you look a the link I posted above to the SolarWinds user forum (Thwack), you will see a screenshot I posted showing the reported error for 4500X with 10GBase-SR transceivers.

The issue I had with the ASRs was about 2 years ago for another employer and I don't have the SR or notes on the exact error message on hand any more.

Farooq Razzaque · ‎01-22-2013

Dear Mavin

Thanks...

Do u have any idea, in the following log generated by LMS, from where the following values picked by LMS. Is it real time value or threshold value set in LMS. In switch, I have values as N/A in the show interface transceiver detail except volt value which is 0.00. Out of show interface transceiver detail is shown below at the end

Below is the LMS snap of voltage sensor for some of those ports which is shwoing following values

HighThreshold=5.0;Status=OK;CurrentValue=0.0; LowThreshold=1.0

OutOfRange::Component=VOLT-10.x.x.x/11067 [Te2/7/5 Supply Voltage Sensor];

ComponentClass=VoltageSensor;ComponentEventCode=1080;HighThreshold=5.0;Status=OK;CurrentValue=0.0;

LowThreshold=1.0;entSensorValue=0;RelativeVoltageThreshold=0.0 %

sh interfaces transceiver detail switch 1
Transceiver monitoring is disabled for all interfaces.

mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.
++ : high alarm, + : high warning, - : low warning, -- : low alarm.
A2D readouts (if they differ), are reported in parentheses.
The threshold values are calibrated.

                                   High alarm High Warn Low Warn   Low Alarm
            Voltage            Threshold   Threshold Threshold Threshold
Port        (Volts)            (Volts)     (Volts)    (Volts)    (Volts)
---------- ---------------    ---------- --------- --------- ---------
Te1/7/4     0.00                   N/A         N/A         N/A        N/A
Te1/7/5     0.00                   N/A         N/A         N/A        N/A
Te1/9/1     0.00                   N/A         N/A         N/A        N/A
Te1/9/2     0.00                   N/A         N/A         N/A        N/A
Te1/9/3     0.00                   N/A         N/A         N/A        N/A
Te1/9/4     0.00                   N/A         N/A         N/A        N/A
Te1/9/5     0.00                   N/A         N/A         N/A        N/A
Te1/9/6     0.00                   N/A         N/A         N/A        N/A
Te1/9/7     0.00                   N/A         N/A         N/A        N/A
Te1/9/8     0.00                   N/A         N/A         N/A        N/A
Te1/10/1    0.00                   N/A         N/A         N/A        N/A
Te1/10/2    0.00                   N/A         N/A         N/A        N/A
Te1/10/3    0.00                   N/A         N/A         N/A        N/A
Te1/10/4    0.00                   N/A         N/A         N/A        N/A
Te1/10/5    0.00                   N/A         N/A         N/A        N/A
Te1/10/6    0.00                   N/A         N/A         N/A        N/A
Te1/10/7    0.00                   N/A         N/A         N/A        N/A
Te1/10/8    0.00                   N/A         N/A         N/A        N/A