[cisco-voip] Slip sec on PRI

[Sreekanth Narayanan (sreenara)]

Hey Scott,

Unfortunately, there is no way you can configure the RTMT or syslogs to catch slips on the lines. You would need something along the lines of an EEM applet running on the router which runs the show controller t1/e1 x/y/z output at regular intervals and looks for increases in the slip counter, and then print a syslog if there are slips.

Just ensure that you’ve got the network-clock-select command configured to ensure that the backplane gets its clocking from that PRI. If all the PRIs come from the same provider, then it would be OK to have clock source line on all of the controllers and make one of them the primary clock source.

If you have different providers, it would be better to keep 1 provider as clock source line and the others as clock source internal, i.e. where the router acts as the clock source, so that you don’t see slips on one of the provider lines because you’ve configured the other provider as the primary clock source.

Sreekanth

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: Friday, February 12, 2016 7:10 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Slip sec on PRI

OK, had an issues where I forgot to set the clock on some PRI's and had slip sec, unavailable sec, etc.  Is there any logging that I can use to see this in the future?  We use syslogs but nothing came in by default.  is there a way to set that up?  or a trigger in RTMT?  Something else I can do to be proactive?  We don't add PRI's very often so I don't expect it to happen for a while, but I would like to put something in place just in case for next time.

TIA

Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160212/78a5854b/attachment.html>