|
Good answer, Francois! Cordially, Leslie A. Clark IT Services Specialist, Network Mgmt Information Technology Services Americas IBM Global Services (248) 552-4968 Voicemail, Fax, Pager
You issue is probably because netmon is trying to monitor the status of this object using snmp instead of ping. If it doesn't answer to snmp, it will still show down, even if it respond to ping. The way this is configured is usually with the "$" in the netmon seed file. You can test if this is the problem with the quicktest command: it will do a status polling using the same method as netmon. Salutations, / Regards, Francois Le Hir Network Projects & Consulting Services IBM Global Technology Services  <sixxl@cse.com.sg>
Hi there, I'm a new netview administrator and facing an issue. We've got a netview is a default installation with a configured netmon.seed, netview discovers all objects and all device status are reflected properly when down. On the user PC objects sometimes it would turn red signifying down status. Verfication of the physical PC is up and netview doing test ping would turn the object to green. After leaving the object for awhile it would turn red again, even though the PC is up. Please advice on what steps should I take to resolve this issue. The netview is 7.1.4 FP4 running on a windows 2003 server and console is using remote desktop to monitor the netview. Best regards, Sixx _______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)  _______________________________________________NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only) _______________________________________________ NV-L mailing list NV-L@lists.ca.ibm.com Unsubscribe:NV-L-leave@lists.ca.ibm.com http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only) |
