[cisco-voip] strange t1 issue

[Ryan Huff]

Phillip,

The d channel comes up but the b's will not.


Thanks,

Ryan


From: ryanhuff at outlook.com
To: philip.walenta at polycom.com
Date: Wed, 25 Feb 2015 19:39:13 -0500
CC: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] strange t1 issue




Phillip,

T1 0/1/0 is up.
  Applique type is Channelized T1
  Cablelength is long 0db
  Description: ATT SE Circuit 10.IPZX.518281.001.SB 800-247-2020
  No alarms detected.
  alarm-trigger is not set
  Soaking time: 3, Clearance time: 10
  AIS State:Clear  LOS State:Clear  LOF State:Clear
  Version info FPGA Rev: 08121917, FPGA Type: PRK4
  Framing is ESF, Line Code is B8ZS, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (235 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Data in Interval 1:
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 90 Unavail Secs
  Total Data (last 1 15 minute intervals):
     0 Line Code Violations, 0 Path Code Violations,
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 90 Unavail Secs

Thanks,

Ryan

From: Philip.Walenta at Polycom.com
To: ryanhuff at outlook.com
CC: cisco-voip at puck.nether.net
Date: Wed, 25 Feb 2015 16:25:17 -0800
Subject: Re: [cisco-voip] strange t1 issue

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?

Sent from my iPhone
On Feb 25, 2015, at 5:27 PM, Ryan Huff <ryanhuff at outlook.com> wrote:







Doing a PRI migration from a 2811 vwic2 T1 to a 2911 vwic3 T1

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 

Only thing in the logs are:

%MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
: %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to up
: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10
: %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to down
: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1
: %LINK-3-UPDOWN: Interface Serial0/1/0:23, changed state to up

Every so often it repeats. Any ideas

thanks,

ryan

 		 	   		  
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
 		 	   		  

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150225/cda1e6a4/attachment.html>