Extra Info: Error Decoding packet."ĮDIT: After attempting the walk with the tool in the engineer's toolset, it fails at different times.
SOLAR WALK 2 FOR WINDOWS TRIAL
I have run snmpd logging debug information but don't see anything indicating any errors.Īny further speculation on where to look would be helpful.Īfter searching thwack, I noted that a user had used the mib walking tool in the engineers toolset to successfully get results after experiencing an error similar to mine, so I downloaded the trial and ran the MIB Walk tool that comes with the toolset - unfortunate I also received an error there - "Error during Walk: An attempt was made to load a program with an incorrect format. Is it absolutely necessary to configure/specify a view? Everything else appears to function properly by just specifying the OID. The nf man page at shows an example specifying either a view or an OID.
The fact that I can use the SNMPv3 user/credentials that I created to walk the entire tree of the server using other methods indicates that SNMPv3 is configured correctly. I have tried other processes to monitor in this way as well - all can be selected from the list of processes, but all fail when trying to poll. When I select the process I wish to monitor and complete the procedure, Orion SAM attempts to poll the process and delivers the timeout message mentioned above. SAM Settings>Find Processes, Services.>Select component monitor type - Process Monitor SNMP>Select a target - browse to server>Check onr or more processes.Īt this point, Orion SAM appears to load a list of all processes running on the indicated server, including the process which I wish to monitor - it identifies an instance count, with some process running multiple instances, telling me it is actually pulling this information from the server, not just from a generic entry in a MIB. I first set up this process monitor by doing the following: Using an external MIB-Browser, with these credentials I am able to walk the entire tree on the server in question, and locate the process I am trying to monitor from the HOST-RESOURCES-MIB-rfc2790. I have a read-only user (rouser) set up in just this fashion. I cannot understand how an identical RHEL + SNMP installation using an identical nf file will work on one machine but not others.Īny advice on where to look would be appreciated, for resolving either matter above.Īccording to the Red Hat documentation on SNMPv3 configuration, after creating a v3 user and specifying the encryption and authentication protocols, modifying the nf file as follows would be enough to grant access to all available MIBs: However, when I hit "next" and Orion starts to poll the server to see what resources are available, it comes up empty, with nothing available for monitoring. Adding the nodes back in after rebuild, when running an SNMP test, the results come back with a PASS. When the servers were being rebuilt, the nodes were removed from Orion. The nf file used for SNMPv2 is identical to the one I use on the test server (which works fine) and is the same conf file that was used on these servers prior to being rebuilt. There are currently no firewall restrictions in place. The same version of SNMP is installed on these RHEL servers as is installed on my test server. On a side note, I have a few production servers that were rebuilt. Whether I use credentials that were set up as an SNMPv3 user, or root credentials, I cannot get the application monitor to run successfully using SNMPv3. The application monitor is set to the default timeout of 300 seconds, yet this error occurs immediately. This process monitor works fine in SNMPv2. However, when trying to monitor a particular running process, immediately after polling I get the error message "SNMP Monitor Execution Error.
I was hoping to move to SNMPv3, but after creating an SNMPv3 user for Orion to connect with, I am getting an issue.Īll polling seems to work - when adding the node to Orion I see all the details/resources I expect to see. I am using a test server running REHL 6 that is configured identically to some of our production servers, but is not joined to our AD environment.
0 kommentar(er)
