understanding 3g / 4g debug logs

prathikr · ‎11-14-2015

Hello All ,

I have a Cisco 829 router , trying to configure for 3g and 4g , i am unable to get the cellular interface up , the same sim card works fine on cisco 877 router , i believe there should be some configurational changes to be made

I have enabled debug logs

debug modem

debug chat

debug dialer

debug cellular 0 messages call control

Can anybody help me understand the debugs

Also if you have any documents to understand the debug logs and dm logs , kindly share

Any help will be greatly appreciated !!

*Nov 13 04:44:26.249: CHAT3: Attempting async line dialer script
*Nov 13 04:44:26.249: CHAT3: Dialing using Modem script: ipwan & System script: none
*Nov 13 04:44:26.249: CHAT3: process started
*Nov 13 04:44:26.249: CHAT3: Asserting DTR
*Nov 13 04:44:26.249: CHAT3: Chat script ipwan started
*Nov 13 04:44:26.249: CHAT3: Sending string: AT!SCACT=1,1
*Nov 13 04:44:26.249: CHAT3: Expecting string: OK
*Nov 13 04:44:26.275: CHAT3: Completed match for expect: OK
*Nov 13 04:44:26.275: CHAT3: Chat script ipwan finished, status = Success
*Nov 13 04:44:26.275: TTY3: no timer type 1 to destroy
*Nov 13 04:44:26.275: TTY3: no timer type 0 to destroy
*Nov 13 04:44:26.275: TTY3: no timer type 2 to destroy
*Nov 13 04:44:26.283: cellwan_api_pkt_session_notify: instance id:0 profile:0 status:1
*Nov 13 04:44:26.283: %CELLWAN-2-BEARER_UP: Instance id=0, Default bearer (bearer_id=5) in Cellular0 is now UP
*Nov 13 04:44:26.283: cellular_update_profile_id_for_latest_call_setup: pending_idb:0xF26C988

*Nov 13 04:44:26.283: Cellular0 profile 0, session ACTIVE
*Nov 13 04:44:26.283: cellwan_api_pkt_session_notify:connected idb_subunit:0
*Nov 13 04:44:26.411: cellwan_api_pkt_session_notify: instance id:0 profile:0 status:0
*Nov 13 04:44:26.411: %CELLWAN-2-BEARER_DELETED: Instance id=0, Default bearer (bearer_id=5) in Cellular0 is now deleted.
*Nov 13 04:44:26.411: Cellular0 profile 0, session INACTIVE
*Nov 13 04:44:26.411: Cellular0 DirectIP: Remove negotiated IP interface address
*Nov 13 04:44:28.275: %LINK-3-UPDOWN: Interface Cellular0, changed state to up

*Nov 13 04:44:26.411: %CELLWAN-2-BEARER_DELETED: Instance id=0, Default bearer (bearer_id=5) in Cellular0 is now deleted.
*Nov 13 04:44:26.411: Cellular0 profile 0, session INACTIVE
*Nov 13 04:44:26.411: Cellular0 DirectIP: Remove negotiated IP interface address
*Nov 13 04:44:28.275: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
*Nov 13 04:44:28.275: Ce0 DDR: Dialer statechange to up
*Nov 13 04:44:28.275: Ce0 DDR: Dialer call has been placed
*Nov 13 04:44:28.275: cellular_dip_ip_address_negotiated: failed to find profile ID for Cellular0
*Nov 13 04:44:28.275: Ce0 DDR: dialer protocol up
*Nov 13 04:44:29.275: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to up
*Nov 13 04:44:37.631: TTY0: pause timer type 1 (OK)
*Nov 13 04:44:37.631: TTY0: resume timer type 1 (OK)
*Nov 13 04:44:44.117: TTY0: pause timer type 1 (OK)
*Nov 13 04:44:44.119: TTY0: resume timer type 1 (OK)
*Nov 13 04:45:09.577: TTY0: pause timer type 1 (OK)
*Nov 13 04:45:09.577: TTY0: resume timer type 1 (OK)
IR800#     
*Nov 13 04:46:26.249: cellwan_api_pkt_session_notify: instance id:0 profile:0 status:0
*Nov 13 04:46:26.251: %CELLWAN-2-BEARER_DELETED: Instance id=0, Default bearer (bearer_id=0) in Cellular0 is now deleted.
*Nov 13 04:46:26.251: cellular_update_profile_id_for_latest_call_setup: pending_idb:0xF26C988
*Nov 13 04:46:26.251: LSI DIP call set-up failure for Cellular0: profile_id = 1, active_status = 0, pdp_ctxt = 0

*Nov 13 04:46:26.251: Cellular0 profile 0, session INACTIVE
*Nov 13 04:46:26.251: TTY3: Async Int reset: Dropping DTR
*Nov 13 04:46:26.251: Cellular0 DirectIP: Remove negotiated IP interface address
*Nov 13 04:46:26.877: TTY3: DSR was dropped
*Nov 13 04:46:26.877: tty3: Modem: READY->(unknown)
*Nov 13 04:46:26.877: %TRACK-6-STATE: 100 interface Ce0 line-protocol Up -> Down
*Nov 13 04:46:27.877: TTY3: dropping DTR, hanging up
*Nov 13 04:46:27.877: tty3: Modem: HANGUP->(unknown)
*Nov 13 04:46:28.251: %LINK-5-CHANGED: Interface Cellular0, changed state to reset

hugocastrodigital1 · ‎12-05-2015

i had the same issue.

watch your line configuration.

line 3

dialer script gsm

i had to change it for dialer script lte

i have been working with a 819 router last days, copy your running config and may be i can help you.

prathikr · ‎12-12-2015

Thank you for the response , i was able to figure out the root cause

Raul Ricano · ‎02-02-2016

What was your resolution? I have the correct scripts, dialer and config, but still flaps on Cell 0

*Feb 2 17:16:07.899 EST: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
*Feb 2 17:16:08.899 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to up
*Feb 2 17:16:35.739 EST: %CELLWAN-2-BEARER_DELETED: Instance id=0, Default bearer (bearer_id=6) in Cellular0 is now deleted.
*Feb 2 17:16:37.739 EST: %LINK-5-CHANGED: Interface Cellular0, changed state to reset
*Feb 2 17:16:38.739 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to down
*Feb 2 17:16:42.739 EST: %LINK-3-UPDOWN: Interface Cellular0, changed state to down
*Feb 2 17:16:53.915 EST: %CELLWAN-2-BEARER_UP: Instance id=0, Default bearer (bearer_id=6) in Cellular0 is now UP
*Feb 2 17:16:56.223 EST: %LINK-3-UPDOWN: Interface Cellular0, changed state to up
*Feb 2 17:16:57.223 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to up
*Feb 2 17:17:23.643 EST: %CELLWAN-2-BEARER_DELETED: Instance id=0, Default bearer (bearer_id=6) in Cellular0 is now deleted.
*Feb 2 17:17:25.647 EST: %LINK-5-CHANGED: Interface Cellular0, changed state to reset
*Feb 2 17:17:26.647 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0, changed state to down

Thanks

Raul

Raul Ricano · ‎02-03-2016

After working with Cisco TAC the issue seemed to be caused by having an IP SLA that was routing icmp traffic to the WAN interface while the primary track route was down, but was not allowed in the NAT list. Apparently Verizon does not like this and tends to terminate the connection in a way of letting you know they are receiving traffic they shouldn't. The Fix was adding this Subnet to the NAT List ACL which resolved the down/up issue. Hopes this helps someone else.

-Raul