Dear Expert
Its very easy to monitor the latency from NMS server to Host, however we desperately looking some solution to monitor latency of the link.
We have many links DS3/STM1/STM4/STM16/STM64, all the links having point-to-point IP.
This below example from Juniper and can be also from Cisco
show interfaces ge-1/0/0
Destination: 10.10.253.208/30, Local: 10.10.253.209, Broadcast: 10.10.253.211
ping 10.10.253.210 source 10.10.253.209
64 bytes from 10.10.253.210: icmp_seq=0 ttl=255 time=143.026 ms
How to monitor the latency between 10.10.253.209 (A End at our side Dubai) to 10.10.253.210 (B End at provider side UK). This 143ms seconds need to monitor (with Warning/Critical alert) and need graph too.
Regards
how to monitor latency on STM link
how to monitor latency on STM link
Zajil NMS
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: how to monitor latency on STM link
Hi zaji_nms,
The deal is most statistics we pull are using SNMP and they're layer 2 stuff. The latency you're looking at involves layer 3.
If these were 2 Linux routers the problem would be trivial to solve, you could just do a check_ping from one to the other using NRPE. Would an adequate alternative be to put a similar check on a host just inside the near router? If all of the links are remote from 1 site that would be super easy. If you have a mesh layout instead of a hub and spoke it would be more difficult as you'd need to bounce off hosts all over the place.
If what I'm saying doesn't make sense let me know and I'll be happy to draw a diagram. Basically though I'm saying just use a Linux or Windows host to run a check ping from to the remote router interface.
The deal is most statistics we pull are using SNMP and they're layer 2 stuff. The latency you're looking at involves layer 3.
If these were 2 Linux routers the problem would be trivial to solve, you could just do a check_ping from one to the other using NRPE. Would an adequate alternative be to put a similar check on a host just inside the near router? If all of the links are remote from 1 site that would be super easy. If you have a mesh layout instead of a hub and spoke it would be more difficult as you'd need to bounce off hosts all over the place.
If what I'm saying doesn't make sense let me know and I'll be happy to draw a diagram. Basically though I'm saying just use a Linux or Windows host to run a check ping from to the remote router interface.