Wesley

Jkump. Do you have a link to the bug listed on Cisco's site? 

It hasn’t been changed.

Problem back after updating NPM and SAM. Ran permission checker with no luck. It appears the file is never downloaded or at least its not able to write the file to the temp directory.

Deleted the MIBs.cfg file from the temp location. I let the 24 hour poll occur on it's own. All better now. I just wonder if the existing MIBs.cfg file permissions were the issue.

I spoke to soon. When I look at the temp folder now I see a modified data on the Mib.cfg file of 2/5/15. Something is a miss.

Ran Orion Permission Checker and now with a manual copy the age shows zero. I still need to see if the file gets downloaded and renamed correctly.

The MIBs.cfg file in the temp folder never updates. So I have 2 issues. 1. The download or renaming of the new MIBs.cfg is failing. 2. Even though I manually copy over the file to the production data folder the script still comes up with the file as being 37 days old (everyday).

No joy.

I stopped the services today. Copied the MIB.cfg (dated 2/5/2015) from the temp folder to the production location then restarted services. I manually polled after the system was back up and functioning and got a result of 37 days old (which was what I had before copying the file). Typically when the template was…

The template has been showing that the MIB database is 31 days old for approximately 5 days. Has anything changed? I went as far as manually downloading and swapping out the MIB.cfg file.

Running 11.5 and VMNQ at 4.2.4. No it doesn't work.

I have the same problem as nrunge. I have had UCS in place for a while now and a ticket in. Fix it or remove the visibility.

Cisco ASA 5508-X SysObjectID1.3.6.1.4.1.9.1.2120

1.3.6.1.4.1.8072.3.2.10 Barracuda Load Balancer 340

The link on the download page for the Release Candidate still points to RC2.