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.
DFM has been giving me a discovery error with the following message: “Agent loops in response to GET_NEXT: Agent: 172.21.200.12, First OID: .1.3.6.1.2.1.31.1.2.1.3.76.0”This is on a 7206VXR (NPE300) router running on IOS version 12.2(15)T10. I have ...
My server team wants to upgrade the server CiscoWorks is running on. They also want to upgrade to Windows Server2003. Is this supported?Applications include:CiscoWorks Common Services w/SP2 version 2.2Campus Manager version 3.3Device Fault Manager...
DFM - Discovery ErrorsMy DFM server has an issue with the discovery of two devices in my network. The specific error info is listed below. The first one is for 7206VXR router and the second one is for a Local Director 430.Both of these devices are ...
Here is my situation; my manager is interested in tracking all changes made to equipment in our infrastructure. This way the changes can be mapped to a specific change control for this change. We are using AAA with local usernames and passwords on ...
I have CiscoWorks LMS 2.2 and RWAN 1.3 running on a Windows 2000 Server. Currently this server is not in the Domain. The server team wants to add this server to the domain, but I remember reading that CiscoWorks does not like the added domain secur...
Yes I did stop and re-start the DFM services several times. Each time I received the same error message on the first rediscovery. I also tried deleting the device in DFM, saving the inventory, then adding it back to DFM. Again, I received the same...
I have a relitively small network and we use DFM for our fault management. With the help of a perl script, we only page on interfaces up/down or if a device is unreachable.
That did it!!Changed my logging trap statement to informational from warning and I can see the change I performed, by name, on the specific device.Thanks this is my answer.
Thanks for your quick reply, however the problem seems to be that all of the changes that are made over the course of 24 hours are not recorded when they are made. We tested this by changing the configs on some routers and RME did not pick up all of...
