Not a major issue but one which bugs me all the same, has anyone else experienced this? As you can see from the attached I have several devices and every 4500 chassis fails to show up its power status correctly even though there is no fault.
You can just make out that the "Fan OK" LED is lit but the input 1 & 2 LED's don't show, neither does the "Output Fail" LED when there is a fault.
I know it's only a cosmetic thing but it does have its uses, especially when showing the boss the nice colours!
I'm sure I've got an up to date package unless anyone can advise me otherwise.
It's more than cosmetic. It could be misleading if one relies on CiscoView without physically visiting the equipment (which is supposed to be one of CiscoView's benefits). It's the same old "instrumentation issue" that's still there today, i.e.: the Cisco BU did not bother populating the power status info in the SNMP MIBs that CM/CiscoView query. It even takes a bit of digging on the IOS CLI.
As the aforementioned thread reveals, Cisco NMS devs' position is there's nothing wrong with the device packages per se. It's due to the lack of "instrumention" by the hardware BU to provide info such as power status in the the SNMP MIBs. My take is LMS apps (CiscoView, etc.) should do whatever it takes to provide the correct info, not constraining itself to relying only on SNMP. If the SNMP value is ambiguous or simply not there, why couldn't CiscoView fire off a NetShow job to get it from IOS CLI?
ydabear and Richardsma, I think you both have verified that it is an issue with the implementation of the MIB on the device and not with CiscoView, haven't you?
With CiscoView it is the same as with RME (thinking e.g. of serial numbers and sysUptime...) - both apps rely only on SNMP - which I think in general is not a problem. The problem is that it seems that the hardware BUs can decide themself what they implement into the MIB and how they do it instead of the NMS BU saying what must be implemented as a minimum on EVERY hardware for doing proper management. I wonder if this will ever change....
...it would be a small step for the hardware BU but a great step for all the NMS folks out there .... ;-)
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.