[cisco-voip] PRI Clocking

[Mike King]

Unfortuanlty, the String in the case is still Telco.

Is the loopback diag and the BERT service affecting?  (I think so, but
I want to verify)

I haven't seen any slips...  But then again, I was more than 24 hours
after the fact, so they had all aged out by then.

So in the last 24, I've gotten 1 more CRC, for a total of 2.

Last clearing of "show interface" counters 2d20h
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/1/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 48 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     41005 packets input, 481747 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort

I'll continue to push my provider.

On Thu, Aug 26, 2010 at 11:41 AM, Go0se <me at go0se.com> wrote:
> You should be able to run a loopback diag and a BERT on your equipment to
> test the vwic. If it tests ok then escalate. Have them do after hours
> intrusive testing if possible.
>
> I'm waiting for cisco to release their new line of VWIC-xTC&S-V2 vwics. They
> will be much easier to troubleshoot. (TC&S = Tin Can & String)
>
> VWIC-TC&S-V2 Troubleshoot guide:
>        1) check can
>        2) check string
>
> Thanks,
>
> Go0se
>
> My blog:
> http://atc.go0se.com
>
> --------------------------------------------
> Help Hopegivers International
> Feed the orphans of Haiti and India
> http://www.hopegivers.org
> --------------------------------------------
>
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike King
> Sent: Thursday, August 26, 2010 10:10 AM
> To: Cisco VoIPoE List
> Subject: Re: [cisco-voip] PRI Clocking
>
> I'm assuming I didn't screw it up.
>
> network-clock-participate wic 0
> network-clock-select 1 T1 0/0/0
>
> Only PRI (and PRI VWIC) on the box.
>
>
>
> On Thu, Aug 26, 2010 at 11:00 AM, Go0se <me at go0se.com> wrote:
>> You should expect a PRI to ALWAYS ALWAYS ALWAYS run clean. Faxing is
>> especially susceptive to errors/failure across a PRI that has errors.
>> And you should ALWAYS clock off of the TELCO. That is ridiculous that
>> they suggested you provide an internal clock for a PRI. Do you have
>> your network clock participate and network clock select correct?
>>
>> Thanks,
>>
>> Go0se
>>
>> My blog:
>> http://atc.go0se.com
>>
>> --------------------------------------------
>> Help Hopegivers International
>> Feed the orphans of Haiti and India
>> http://www.hopegivers.org
>> --------------------------------------------
>>
>> -----Original Message-----
>> From: cisco-voip-bounces at puck.nether.net
>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike King
>> Sent: Thursday, August 26, 2010 9:41 AM
>> To: Cisco VoIPoE List
>> Subject: [cisco-voip] PRI Clocking
>>
>> Just for someone to check my sanity.
>> I'm having the standard argument with Telco today  (We don't see
>> anything, it must be your equipment)
>>
>> I have a PRI that I've had complaints of dropped calls.
>>
>> I go an check the log on the 2921 router, and see this  (Across 3
>> different dates, just one posted for brevity)
>>
>> 092856: Jul 30 2010 09:49:36.861 EDT: %MARS_NETCLK-3-HOLDOVER:
>> Entering Holdover for Controller T1 0/0/0
>> 092857: Jul 30 2010 09:49:38.613 EDT: %LINK-3-UPDOWN: Interface
>> Serial0/0/0:23, changed state to down
>> 092858: Jul 30 2010 09:49:47.113 EDT: %MARS_NETCLK-3-HOLDOVER_TRANS:
>> Holdover timer exceeded for Controller T1 0/0/0
>> 092859: Jul 30 2010 09:49:47.113 EDT: %MARS_NETCLK-3-CLK_TRANS:
>> Network clock source transitioned from priority 1 to priority 10
>> 092861: Jul 30 2010 09:57:23.612 EDT: %LINK-3-UPDOWN: Interface
>> Serial0/0/0:23, changed state to up
>> 092863: Jul 30 2010 09:57:32.112 EDT: %MARS_NETCLK-3-CLK_TRANS:
>> Network clock source transitioned from priority 10 to priority 1
>>
>> I also have CRC's on the serial0/0/0:23  (not a whole lot, just some)
>>
>> Telco of course says they've pulled PM's and see nothing. I've been
>> pushing the issue with my Telco Rep, and he's suggested that since it
>> seems to be a clocking issue (His words) that maybe we should set our
>> PRI to internal clocking.
>>
>> I reset the counters on my serial interface, and in the past 2 days,
>> I've recieved 1 CRC.  I've also not had the PRI drop any calls. (Or
>> the whole PRI drop, which is what I assume from those log messages)
>>
>>
>> I have another circuit at a different site, I reset it's counters at
>> the same time 48 hours ago, and It had this today (also I don't have
>> any reports of dropped calls, just problems faxing)..
>> 12 runts, 0 giants, 0 throttles
>> 32 input errors, 32 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort
>>
>> My question is this:
>>
>> Is it Normal to have some number of CRC's on a PRI?
>> My personal experience is to ALWAY clock off Telco, and you should not
>> have any errors on my lines.  Am I wrong with this assumption?
>>
>> Mike
>> _______________________________________________
>> 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
>
>