Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

What can be the cause of "Recvd L1 prim ISDN_PH_DEACT_IND"?

Hi!

We are using 2811 with VWIC2-1MFT-G703.

S/W ver. is 12.4.7a

Periodically all our calls, that are going thtough E1, are dropping. The log shows following:

Jul 3 14:09:56: ISDN Se0/1/0:15 EVENT: service_queue_from_physical_layer: Recvd L1 prim ISDN_PH_DEACT_IND state is IF_ACTIVE

Jul 3 14:09:56: ISDN Se0/1/0:15 EVENT: isdn_pri_t1_state_change: setting State to 0

Jul 3 14:09:56: ISDN Se0/1/0:15 CC: CCPRI_Go: source id 0x300, call id 0x0, event 0x7F0 (pre-ccb recovery)

Jul 3 14:09:56: ISDN Se0/1/0:15 EVENT: CCPRI_Go: received MNL_RESET_REQ

Jul 3 14:09:56: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/1/0:15, TEI 0 changed to down

Jul 3 14:09:56: ISDN Se0/1/0:15 MGMNT: ME_ShutDown()

Jul 3 14:09:56: ISDN Se0/1/0:15 MGMNT: ME_Remove_TEI: LMTR[0][1].Tei=0, Sapi=0, State=2

Jul 3 14:09:56: ISDN Se0/1/0:15 MGMNT: ME_ShutDown: sending MNL_DEACT_IND

Jul 3 14:09:56: ISDN Se0/1/0:15 CC: CCPRI_Go: source id 0x300, call id 0x0, event 0x7F0 (pre-ccb recovery)

Jul 3 14:09:56: ISDN Se0/1/0:15 EVENT: CCPRI_Go: received MNL_RESET_REQ

Jul 3 14:09:57: ISDN Se0/1/0:15 BACKHAUL: L2IF_rx_L3_bindinfo: rx'd bindinfo

Jul 3 14:09:57: ISDN Se0/1/0:15 BACKHAUL: L2IF_rx_L3_bindinfo: rx'd bindinfo

Jul 3 14:09:57: ISDN Se0/1/0:15 BACKHAUL: L3IF_rx_L2_bindinfo: rx'd bindinfo

Jul 3 14:09:57: ISDN Se0/1/0:15 BACKHAUL: handle_mail: received (DL_REL_REQ):

dest_id = 0, source_id = 3, prim = 210

priv_ln = 4, int_id = 1181329424, datasize = 0

Jul 3 14:09:57: ISDN Se0/1/0:15 CC: CCPRI_Go: source id 0x300, call id 0xFFFF, event 0x313 (pre-ccb recovery)

Jul 3 14:09:57: ISDN Se0/1/0:15 EVENT: CCPRI_Go: received NL_REL_CONF

Jul 3 14:09:58: %LINK-5-CHANGED: Interface Serial0/1/0:15, changed state to administratively down

Jul 3 14:09:58: ISDN Se0/1/0:15 EVENT: isdn_sw_cstate: State = 6, Old State = 4

Jul 3 14:10:00: ISDN Se0/1/0:15 EVENT: service_queue_from_physical_layer: Recvd L1 prim ISDN_PH_ACT_IND state is IF_DOWN

Jul 3 14:10:00: ISDN Se0/1/0:15 EVENT: isdn_pri_t1_state_change: setting State to 4

Jul 3 14:10:00: ISDN Se0/1/0:15 EVENT: Pri_Activate_L2: sending NL_EST_REQ

Jul 3 14:10:00: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/1/0:15, TEI 0 changed to up

Jul 3 14:10:00: ISDN Se0/1/0:15 EVENT: isdn_pri_t1_state_change: setting State to 4

Jul 3 14:10:00: ISDN Se0/1/0:15 CC: CCPRI_Go: source id 0x300, call id 0xFFFF, event 0x303 (pre-ccb recovery)

Jul 3 14:10:02: %LINK-3-UPDOWN: Interface Serial0/1/0:15, changed state to up

Jul 3 14:10:02: ISDN Se0/1/0:15 EVENT: isdn_sw_cstate: State = 4, Old State = 6

"show controllers E1" does not show any errors.

I think we have a L1 issue. Perhaps bad cable or faulty NT1 unit. Am I right?

Thank you!

1 REPLY
Silver

Re: What can be the cause of "Recvd L1 prim ISDN_PH_DEACT_IND"?

Suggestion are regarding BRI interface.See if this helps in E1.Clear the BRI interface.Make a call; bring up the 2 b channels wait for them to go down( idle timeout),make another call(this is where it wont come back up again.Do this when trying to debug

debug isdn q931; debug isdn q921; debug ppp nego, debug ppp authen, debug dialer.These are the commands

690
Views
0
Helpful
1
Replies