<div dir="ltr"><span style="font-size:13.1999998092651px;line-height:20px">What's the output of the following commands:</span><br style="font-size:13.1999998092651px;line-height:20px"><br style="font-size:13.1999998092651px;line-height:20px"><div style="font-size:13.1999998092651px;line-height:20px">sh run | in network-clock</div><div style="font-size:13.1999998092651px;line-height:20px">show network-clock</div><div style="font-size:13.1999998092651px;line-height:20px">show isdn status</div><div style="font-size:13.1999998092651px;line-height:20px">show voice-port summary</div></div><br><div class="gmail_quote">On Wed, Feb 25, 2015 at 7:16 PM Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Phillip,<br><br>The d channel comes up but the b's will not.<br><br><br>Thanks,<br><br>Ryan<br><br><br><div><hr>From: <a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a><br>To: <a href="mailto:philip.walenta@polycom.com" target="_blank">philip.walenta@polycom.com</a><br>Date: Wed, 25 Feb 2015 19:39:13 -0500<br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></div></div></div><div><div dir="ltr"><div><br>Subject: Re: [cisco-voip] strange t1 issue<br><br>
<div dir="ltr">Phillip,<br><br>T1 0/1/0 is up.<br> Applique type is Channelized T1<br> Cablelength is long 0db<br> Description: ATT SE Circuit <a href="http://10.IPZX.518281.001.SB" target="_blank">10.IPZX.518281.001.SB</a> 800-247-2020<br> No alarms detected.<br> alarm-trigger is not set<br> Soaking time: 3, Clearance time: 10<br> AIS State:Clear LOS State:Clear LOF State:Clear<br> Version info FPGA Rev: 08121917, FPGA Type: PRK4<br> Framing is ESF, Line Code is B8ZS, Clock Source is Line.<br> CRC Threshold is 320. Reported from firmware is 320.<br> Data in current interval (235 seconds elapsed):<br> 0 Line Code Violations, 0 Path Code Violations<br> 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins<br> 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs<br> Data in Interval 1:<br> 0 Line Code Violations, 0 Path Code Violations<br> 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins<br> 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 90 Unavail Secs<br> Total Data (last 1 15 minute intervals):<br> 0 Line Code Violations, 0 Path Code Violations,<br> 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,<br> 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 90 Unavail Secs<br><br>Thanks,<br><br>Ryan<br><br><div><hr>From: Philip.Walenta@Polycom.com<br>To: <a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a><br>CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>Date: Wed, 25 Feb 2015 16:25:17 -0800<br>Subject: Re: [cisco-voip] strange t1 issue<br><br><div>Do you have the clock sourced to a specific t1? It sounds like the clock isn't syncing correctly. What do the t1 counters show?<br><br>Sent from my iPhone</div><div><br>On Feb 25, 2015, at 5:27 PM, Ryan Huff <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<br><br></div><blockquote><div>
<div dir="ltr">
<div dir="ltr">Doing a PRI migration from a 2811 vwic2 T1 to a 2911 vwic3 T1<br><br>I can get the D Channel (Serial 0/1/0:23) to come up but I can't get the B channels to come up. The <br><br>Only thing in the logs are:<br><br>%MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1<br>: %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to up<br>: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10<br>: %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to down<br>: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1<br>: %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to up<br><br>Every so often it repeats. Any ideas<br><br>thanks,<br><br>ryan<br></div>
</div>
</div></blockquote><blockquote><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br></div></blockquote></div> </div>
<br>_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div></div></div>
______________________________<u></u>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/<u></u>mailman/listinfo/cisco-voip</a><br>
</blockquote></div>