Forum Discussion
4 Replies
- amolariCirrusI advise you to open a support case. the ID you're referring to is for a similar but not same error.
- Chris_FPCirrus
I'm also seeing these on my 11.5.3 boxes - can you let me know the outcome of the case you opened with F5?
- Kevin_Davies_40Nacreous
Same here
- Michael_Polloc1Nimbostratus
SNMP polling is the cause. The problem is that they have two SNMP OIDs for blade chassis systems that don't apply, and it triggers that error. I'm not sure why this wasn't posted to the SOL article or they didn't bother to remove it with the latest hotfix, but to fix it, modify /config/snmp/snmpd.conf and create a custom view with exclusions for the two bad OIDs. Note that once you do this, changing SNMP via the GUI will overwrite it, so make your edits in the conf file from now on or be prepared to re-add this afterward. (The comments on top of the file warn you that it is automated, but it will NOT change unless you edit the SNMP config via the GUI or reboot the system. Mine has been in place like this for a year now with no problems.) Restart snmpd when you are done. (type: _bigstart restart snmpd_)
Here's my config with generic values. You can copy and paste this to the very bottom of the file and modify the community and user strings as needed.
Set Access Control View-Based Access Control Model (vacm) RFC 2265 view noBladeStuff included .1.3.6.1.4.1.3375 view noBladeStuff excluded .1.3.6.1.4.1.3375.2.1.3.2.4 view noBladeStuff excluded .1.3.6.1.4.1.3375.2.1.3.2.5 rocommunity "communityname1" 10.10.10.1 -V noBladeStuff rocommunity "communityname2" 10.10.10.2 -V noBladeStuff rouser username1 priv -V noBladeStuff rouser username2 priv -V noBladeStuff