CSCuj09556 - PI 2.0 corrupts device config by doing snmp set for location after sync
This bug is marked as "fixed", but it's not. There is a convoluted workaround for it. Will it *actally* be fixed in a future release/patch of PI? It's unreasonable for customers to be expected to have to jockey around with settings for every device they want to add/sync.
had PI mess up over 2500 devices on my network, before I realised what was causing this. I have stopped PI and have no intention of using till I know of a perm. fix. working with our cisco acct. mgr to have good response to this - completely unacceptable behaviour and shows the complete lack of QA on cisco's part. this is my fourth bug in less than a month!
The update I linked to in my second post actually is a permanent fix. Click on the link, then expand the "2" section and click on "2.0.0" and you'll see the "December Update, Prime Infrastructure 2.0". No problems since I installed that. Sucks you had so many affected - I was only testing on a small subset of my gear, so only a couple devices were affected. Hope you're able to get things back on track!
Introduction to Essential Utility for Optical Network ProfessionalsSnapshot of utilityFeature SupportedComposite Power calculatorNet Composite power Change when some channels are added/removedDirect Conversion for multiple parametersUse CasesSupported Tec...
There are few interoperability issues between 2960x and other vendors. In this article we will go over the steps on how to debug these issues.
Check the phy id from “show controllers ethernet-controller phy” output.
<snip from show controllers ethe...
It appears that you are trying to access end of life information from Cisco search. We have detected a problem with your script ("eol...) and would like to help. Please contact email@example.com if you would like support.