syslog/snmp/ping

Unanswered Question
Jan 10th, 2008
User Badges:

Kindly advise the following:


The purpose is to proactively monitor the router/switch. Syslog/SNMP has been configured.


1) syslog/snmp is useful when the router/switch is up and router/switch detected problems which will send error messages to the syslog/snmp server immediately?

2) If the router/switch is down, meaning syslog and snmp traps will not be sent to the syslog/snmp server? The only way is to use ping to reach the router/switch to ensure that it is still working fine?

3) Any other recommendations for monitoring?


Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
PAUL TRIVINO Thu, 01/10/2008 - 11:07
User Badges:
  • Bronze, 100 points or more

General answer: Proactive monitoring is so YOU know the device is down/degraded before the USERS call you...;^)


*Most* network monitors use both SNMP and ICMP/Ping to monitor. Obviously ping just says the device is reachable (and is a good first step). SNMP [udp/161] can get more, and more specific, information from a device.


Syslog is (IMHO) and adjunct to both, inn that you can collect the syslog messages and see what the device says. Similarly SNMP Traps (which are messages sent from the device over snmp-trap [udp/162]) do more or less the same thing.


Get an eval of Solarwinds and put it up on your network, these concept are better learned from experience. Also, check out the Network Management forums and see what others do.


Good luck!


Paul




Actions

This Discussion