ACS 5.4 snmp problem - sysoid

[cmarva]

I've looked through the posts and haven't found anything on this yet.

We have 2 ACSs, 5.4, running on VMs.The ovas were initially deployed via the 5.3 image, then upgraded. The secondary had a storage problem over the weekend and the vm was not backed up as production, so it was deleted. We had to completely rebuild.

This time, the ova was deployed from the 5.4 iso. Did patch 1, AD integration, etc. and then reestablished it as the secondary. Functionally everything

is fine, replication is good, and everything is working.

Looking in our NMS, I do see an issue with the sysoid. Below is the a snippet from the primary:

.1.3.6.1.2.1.1.1.0 = STRING: Cisco Secure Access Control System 5.4

.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.2.1.47.1.1.1.1.13.1

Here is the same from the newly deployed secondary:

.1.3.6.1.2.1.1.1.0 = STRING: Cisco Application Deployment Engine

.1.3.6.1.2.1.1.2.0 = OID: .0.0.0

Has anyone seen this? Once again, everything is functioning fine and this appears to be cosmetic (not affecting normal ops).

Thanks, chris

[Amjad Abdullah]

Have you tried to delete the ACS snmp configuration from both sides (NMS system and ACS) and configure it again?

Try (for testing puroses) to change the community string/credentials and check if same issue happen or not.

HTH

Amjad

Rating useful replies is more useful than saying "Thank you"

[cmarva]

At this point, my plan is to apply patch 2. When I do this, I will reboot the secondary (the VM itself). What I am not sure of is whether or not this was done. I thought when the initial ADE config was done and the setup script installed the app, the

VM rebooted at that point. But that's what I'm going to try, change ticket is set for the 23rd. If I still see the same thing, then I'll look at playing around with the snmp settings, since it's not an issue of snmp not working, it's just not reporting the mib2 values I would expect.

Thanks, chris

[cmarva]

I'll reply to this thread after the 23rd, chris