[cisco-voip] Checking hardware -- PRI

[Peter Slow]

ideally, we want all of those debugs starting abotu two minutes prior
to the failure. also... debug isdn q921 probably wouldnt hurt either.

-Peter

On Mon, Feb 15, 2010 at 11:36 AM, Peter Slow <peter.slow at gmail.com> wrote:
> there are definitely going to be things going on with MGCP when this
> is happening.... We need to see what's going on what that in relation
> to the point at which the 921/931 states change. Is it possible for us
> to get the debugs leading up to and including one of the events?
>
> -Pete
>
> On Mon, Feb 15, 2010 at 11:33 AM, Scott Voll <svoll.voip at gmail.com> wrote:
>> mgcp packets are following back and forth.
>> isdn: Feb 15 16:31:19.360: %ISDN-6-LAYER2DOWN: Layer 2 for Interface
>> Se0/3/0:23, TEI 0 changed to down
>> Feb 15 16:31:48.852: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/3/0:23, TEI
>> 0 changed to up
>> not seeing any ccm manager events.  should I?
>> Scott
>>
>>
>>
>>
>>
>> On Mon, Feb 15, 2010 at 8:25 AM, Peter Slow <peter.slow at gmail.com> wrote:
>>>
>>> Errrr.... Also I sort of jumped the gun....
>>>
>>> > I have shut not shut the interface but I continue to get RTMT reports
>>> > that the D channel is down(every 1 - 3 minutes).  Router has been up for
>>> > multiple days.(had a power outage last week). but d channel went down
>>> > yesterday afternoon.
>>>
>>> ...This can mean a TON of things... You're goign to see this alert if
>>> your GW ungesisters from your CCM. That could easily be due to a
>>> network issue. Its entirely possible that your interface is bouncing
>>> at one layer or another when it unregisters or re-registers with your
>>> CCM, that could explain your controller errors. We need to see what's
>>> happening first. Is the GW losing registration with the CCM for a
>>> network or software-related reason, or is the actual T1 interface
>>> bouncing, or is there a different issues thats just causing a problem
>>> with the q.931 signaling.
>>>
>>> we need:
>>> debug mgcp packet
>>> debug isdn q931
>>> debug ccm-manager backhaul events
>>> debug ccm-manager config-download all
>>>
>>> ...and anythign that appears in syslog, such as interface protocol
>>> state changes (int x is up down etc)
>>>
>>> ...begging before and ending after the occurrence of one of the
>>> D-Channel OOS events.
>>>
>>> -Peter
>>>
>>> On Mon, Feb 15, 2010 at 11:17 AM, Peter Slow <peter.slow at gmail.com> wrote:
>>> > I recommend doing one of two things:
>>> >
>>> > if you have hardware to accommodate a second PRI, wire it up to this
>>> > one and set them up back to back, and we'll see if the issue
>>> > continues, and if you keep getting errors or not.
>>> >
>>> > If you can't go with option 1, you need to slap a loopback into that
>>> > bad boy and set it up as an HDLC encapsulated data T1 and we can send
>>> > packets of various sizes over it to see if you get any errors that
>>> > way.
>>> >
>>> > Pick one, and we'll go through the specifics =)
>>> >
>>> > -Peter
>>> >
>>> >
>>> >
>>> > On Mon, Feb 15, 2010 at 11:10 AM, Scott Voll <svoll.voip at gmail.com>
>>> > wrote:
>>> >> show isdn stat shows multiple frames established which makes me still
>>> >> think
>>> >> it's a Telco issue.  any other ideas?
>>> >> Scott
>>> >> ps. I have no mgcp -- mgcp.
>>> >>
>>> >> On Mon, Feb 15, 2010 at 7:53 AM, Scott Voll <svoll.voip at gmail.com>
>>> >> wrote:
>>> >>>
>>> >>> I have a ticket in with the local telco, but I have a D channel on my
>>> >>> PRI
>>> >>> that is bouncing about every 1-3 minutes.
>>> >>> How do I check to make sure it's not a hardware issue on my side?
>>> >>> it's a 2851 with vwic-2mft-t1=
>>> >>> I see on the controller in the last 24 hours it has 1610 path code
>>> >>> violations, 9 line code violoations, 2 serverly err secs, and 6
>>> >>> unavail
>>> >>> secs. but nothing in the current interval.
>>> >>> I have shut not shut the interface but I continue to get RTMT reports
>>> >>> that
>>> >>> the D channel is down(every 1 - 3 minutes).  Router has been up for
>>> >>> multiple
>>> >>> days.(had a power outage last week). but d channel went down yesterday
>>> >>> afternoon.
>>> >>> What else should I be looking at.
>>> >>> Thanks
>>> >>> Scott
>>> >>> ps. CM 6.1.3 and MGCP.
>>> >>
>>> >> _______________________________________________
>>> >> cisco-voip mailing list
>>> >> cisco-voip at puck.nether.net
>>> >> https://puck.nether.net/mailman/listinfo/cisco-voip
>>> >>
>>> >>
>>> >
>>
>>
>