Friday, September 7, 2018

Cisco 819 cellular interface not picking up IP?

I have a Cisco 819 that for whatever reason, will not pick up an IP address on the cell interface. I've ran the activation commands for AT&T, ensured signal, and even replaced the router. Not sure what else to try... any tips?

Config and info:

interface Cellular0 vrf forwarding INET-CELL ip address negotiated no ip redirects ip nat outside ip virtual-reassembly in encapsulation slip ip tcp adjust-mss 1300 load-interval 30 dialer in-band dialer string lte dialer watch-group 1 dialer-group 1 async mode interactive end controller Cellular 0 lte modem link-recovery rssi onset-threshold -110 lte modem link-recovery monitor-timer 20 lte modem link-recovery wait-timer 10 lte modem link-recovery debounce-count 6 no cdp run Router#sh cell 0 r Radio power mode = online Channel Number = 0 Current Band = Unknown Current RSSI = -61 dBm Current ECIO = -31 dBm Radio Access Technology(RAT) Preference = LTE Radio Access Technology(RAT) Selected = AUTO Router#sh cell 0 h Modem Firmware Version = SWI9X15C_05.05.58.00 Modem Firmware built = 2015/03/04 21:30:23 Hardware Version = 1.0 Device Model ID: MC7354 Package Identifier ID: 1102037_9903214_MC7354_05.05.58.00_00_Cisco_005.009_000 International Mobile Subscriber Identity (IMSI) = XXXX International Mobile Equipment Identity (IMEI) = XXXX Integrated Circuit Card ID (ICCID) = XXXX Mobile Subscriber Integrated Services Digital Network-Number (MSISDN) = XXXX Current Modem Temperature = 33 deg C PRI SKU ID = 1102037, PRI version = 005.026, Carrier = AT&T OEM PRI version = 05.09 Router#sh cell 0 net Current System Time = Wed Apr 2 5:41:5 1980 Current Service Status = No service Current Service = Unknown Current Roaming Status = Home Network Selection Mode = Automatic Network = AT&T Mobile Country Code (MCC) = 310 Mobile Network Code (MNC) = 410 Packet switch domain(PS) state = Not attached Cell ID = 0 

Debug shows:

Ce0 DDR: Attempting to dial lte 020625: *Sep 7 13:35:38.620: CHAT3: Attempting async line dialer script 020626: *Sep 7 13:35:38.620: CHAT3: Dialing using Modem script: lte & System script: none 020627: *Sep 7 13:35:38.620: CHAT3: process started 020628: *Sep 7 13:35:38.620: CHAT3: Asserting DTR 020629: *Sep 7 13:35:38.620: CHAT3: Chat script lte started 020630: *Sep 7 13:35:38.620: CHAT3: Sending string: AT!CALL 020631: *Sep 7 13:35:38.620: CHAT3: Expecting string: OK 020632: *Sep 7 13:35:58.620: CHAT3: Timeout expecting: OK 020633: *Sep 7 13:35:58.620: CHAT3: Chat script lte finished, status = Connection timed out; remote host not responding 020634: *Sep 7 13:35:58.620: TTY3: Line reset by "Async dialer" 020635: *Sep 7 13:35:58.620: Ce0 DDR: disconnecting call 020636: *Sep 7 13:35:58.620: TTY3: Modem: (unknown)->HANGUP 020637: *Sep 7 13:35:58.620: TTY3: no timer type 0 to destroy 020638: *Sep 7 13:35:58.620: TTY3: no timer type 1 to destroy 020639: *Sep 7 13:35:58.620: TTY3: no timer type 3 to destroy 020640: *Sep 7 13:35:58.620: TTY3: no timer type 4 to destroy 020641: *Sep 7 13:35:58.620: TTY3: no timer type 10 to destroy 020642: *Sep 7 13:35:58.620: TTY3: no timer type 2 to destroy 020643: *Sep 7 13:35:58.692: TTY3: dropping DTR, hanging up 020644: *Sep 7 13:35:58.692: tty3: Modem: HANGUP->(unknown) 020645: *Sep 7 13:36:03.716: TTY3: restoring DTR 020646: *Sep 7 13:36:13.620: Ce0 DDR: re-enable timeout 020647: *Sep 7 13:36:13.620: DDR: Dialer Watch: watch-group = 1 020648: *Sep 7 13:36:13.620: DDR: network 5.6.7.8/0.0.0.0 DOWN, 020649: *Sep 7 13:36:13.620: DDR: primary DOWN 


No comments:

Post a Comment