Diagnostic Sanity returns inconsistent result

[Paddy S]

Hello all,

   We have just upgraded our 6500 VSS pairs (3 VSS - 6 chassis) to version 15.5(1)SY8 on all systems.

Since then, I notice when I run "show diagnostic sanity" it returns inconsistent results and seems to trigger false alerts on our NMS.

If anyone else has seen this, please feel free to let me know if there's a reason why this may now be happening with this command.

If anyone knows why this command is now appearing intrusive and inconsistent or has seen this on this version please do share your result here.

In the past we could run this command with no impact and not showing port channels as down on our NMS

Thanks.

[Georg Pauwen]

Hello,

which NMS are you running the sanity check on/from ?

[Paddy S]

Not running the command from our NMS, sorry.  I just noticed the sensors we have configured on our NMS (which is Paessler PRTG), show as Down briefly while the command runs (run from the CLI on the 6500 )

The NMS uses SNMP to watch the port-channels and fiber links on the 6500 systems.

"show diagnostic sanity" is now returning inconsistent results when I run it. It reports fiber links as having duplex mis-match (they aren't), and it seems to randomly change which interfaces it reports in this state.

[Georg Pauwen]

Hello,

I checked for bugs, but could not find one that relates to SFPs. Are these Cisco or third-party SFPs ?

[Leo Laohoo]

I have several 6840 on this version and I have no issue with our NMS.

[Paddy S]

Thanks for the input you guys

I'll definitely verify our SFPs are Cisco or at least a supported SFP type - We don't have anything in our running-config to allow the line cards to accept un-supported SFPs.

We do have a server farm switch setup for that, and that's where I saw the config for that "service unsupported-transceiver" is the config for that but we don't have that config on any of our 3 6500 VSS pairs.

Since we just moved to this IOS release Version 15.5(1)SY8 on all of our VSS, I'm wondering if this is an un-documented bug.

I also have a case open with TAC, and am still awaiting a response.  I figured I would ask here, since this is where I usually find the answer in most cases.

[Georg Pauwen]

Hello,

the 'service unsupported-transceiver' command is very old, and has been deprecated for ages, it is not directly related to ALL third party SFPs, meaning an SFP could be third party and work without that command. But the SFPs could still cause your 'issue'.

Of course there is always a chance that this is a (new/undocumented) bug.

[Paddy S]

Yep. That config is set on an old 3750-X switch so not surprising it's a deprecated command.  That switch isn't directly linked to our 6500 chassis as it's a L2 server farm switch.

I'm still awaiting response from TAC to see if others have noticed this change.

running the "show diagnostic sanity" command is no strictly needed, but it's a good tool to have in case we need it later on.

If I hear anything back from TAC I'll be sure to post here.