Uptime
You may use SNMP Get test method (OID 1.3.6.1.2.1.1.3.0) or you may use Performance Counter test method (\System\System Up Time)
http://www.ks-soft.net/hostmon.eng/mfra ... tm#chkSNMP
http://www.ks-soft.net/hostmon.eng/mfra ... erfcounter
Regards
Alex
http://www.ks-soft.net/hostmon.eng/mfra ... tm#chkSNMP
http://www.ks-soft.net/hostmon.eng/mfra ... erfcounter
Regards
Alex
uptime for netscreen devices
The O.I.D. mentioned above seems not to be working for Juniper Netscreen devices I need to monitor.
But it does work for HP and 3com switches.
Any idea for the right variable to read?
M Heijkoop
But it does work for HP and 3com switches.
Any idea for the right variable to read?
M Heijkoop
This is pretty standard counter, it should be supported by all SNMP agents.The O.I.D. mentioned above seems not to be working for Juniper Netscreen devices I need to monitor
Are you sure Juniper Netscreen SNMP agent is enabled? What exactly error message do you see when you are trying to request this device? May be there is some network/firewall error? Can you request 1.3.6.1.2.1.1.1.0 counter?
Its qood idea to ask manufacturer of the device, not usAny idea for the right variable to read?

Do you have manual, MIB files that comes with this device?
Regards
Alex
Thanks for the quick service !
I was caught by the unexpected 'feature' that the <get value> button in the RCC console sends the SNMP request from the my workstation, instead of the management server running Advanced Hostmonitor.
( The source IP address filter is a used security feature in our netscreens.)
The workaround : define the full test, save it and request a refresh executed from the Hostmonitor server.
Both OID values work with the netscreens.
Marcel
I was caught by the unexpected 'feature' that the <get value> button in the RCC console sends the SNMP request from the my workstation, instead of the management server running Advanced Hostmonitor.
( The source IP address filter is a used security feature in our netscreens.)
The workaround : define the full test, save it and request a refresh executed from the Hostmonitor server.
Both OID values work with the netscreens.
Marcel
Correct. RCC GUI sends requests directly to target system while tests are performed by HostMonitor. However if you specify some agent for test execution, RCC will use this agent for test setup as well.I was caught by the unexpected 'feature' that the <get value> button in the RCC console sends the SNMP request from the my workstation, instead of the management server running Advanced Hostmonitor
Regards
Alex