Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I recently upgraded from 1.0.1.3 to 1.0.2.6. I tried to change on of my port VLANs and couldn't find the port vlan configuration anymore. After a lot of searching, I reloaded 1.0.1.3, reconfigured the port vlans and then reloaded 1.0.2.6. All is fine...
Previous to last update we received DFM messages about Blade Switch Power Problems. Seems to be fixed in current DFM, but now we keep getting FAN problems on Blade Switches. Nothing in Blade logs and environments look fine. Any ideas on what I can do...
Some special characters fail when passwords are changed via UCP, but are okay if I enter them directly into ACS. Any ideas on where to start? Problem always seen with the & character, but the $ character seems to be position dependent.
Is there a way to force SNMP v1 on Campus for User Tracking if RME has both Version 1 and Version 3 configured?Seems Campus defaults to Version 3 in this case and I can't get User Tracking to work with V3, only V1.
I had a user tracking database that was originally populated by SNMP V1. It got corrupted and I reinitialized the database. Now, I get No User, nothing.Campus is doing discovery and collections fine, but not User Tracking. It runs and ends fine, but ...
VLAN Membership in 1.0.2.6 only allows you to tag or not tag the frames with vlan. It does not allow you to specify which vlans are on a port, or if the port is trunked. In 1.0.1.3 I had set one port to VLAN 402. Once I upgraded to 1.0.2.6 I attemp...
Although a good product, I believe CiscoWorks should be considered an Element Manager that would report to a Network Manager. That is how I've always placed CiscoWorks. I've used Tivoli Netview or HP Openview NNM as the network manager and NetCool, S...
Guess I should have added: I have multiple blades and multiple CiscoWorks. When I added the February updates to DFM it changed the failures from Power to FAN: StateNotNormal::Component=FAN-NSAU99P202;Status=CRITICAL;
Specifying ranges seems to only be for discovery, not devices already in DCR.Anyway, since the problem is really the lack of a Version 2 Bridge-MIB on most IOS, is there a way for force Campus to use Version 1 mibs?Surely someone thought of user trac...