| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 08/24/2004 7:58 PM |
|
| I installed NSM 3.1 and will be monitoring Cisco routers and Switches only. After discovery, I have about 8,000 objects including SMO classes. I also enabled Mib2 policy, however the majority of my Mib-2 icons are showing as either ANY:ABSENT or ANY:UNKNOWN. Issuing a secondary discovery from nodeview gets the status to change and I will see the interfaces for a short time before I receive the same message in the console which tells me the agent again went to ANY:ABSENT. I applied the latest DSM patches (QO54741, QO56949 and QO56950) but still see the same problems. I also verified the pollsets are correct and also created new one's. I did leave the default polling interval. At this point I'm not sure what else to check, but will most likely debug the DSM and set up a CATCH. Any other ideas?? |
|
|
|
SuperUser
Posts:26
|
| 08/25/2004 8:30 AM |
|
| If your devices are remote, the SNMP requests may be timing out before the reply arrives. Another possibility is that if you have a slow connection to the DSM or a large number of MIBs reporting, you may be experiencing a network card bottleneck. |
|
|
|
SuperUser
Posts:26
|
| 08/25/2004 10:31 AM |
|
Hey Jeff, thank you for your response. I believe you are correct, since I was performing some further tests with ObjectView and getting information for all the ifOutErrors, I received the following popup:
CAF203: GETNEXT request failed: this may be due to an invalid community name, there is no SNMP agent at the IP address specified, or the attribute is undifined on the agent
So I do think the network to the site may be the bottleneck here. Thanks again |
|
|
|
SuperUser
Posts:26
|
| 10/13/2004 11:18 AM |
|
| Persisting on this issue and researching the ANY:UNKNOWN problem further, Level 2 created a fix for this problem I was having. Apparently it was a problem with the mib-2 policy since I was able to duplicate the problem on my test server with the same Mib-2 policy from the production DSMs. I am testing the new policy completely before rolling out to the production DSMs. |
|
|
|
|