Re: C1112-8PLTEEA LTE Config / %Remove Legacy DDR Configuration first

beblos0003 · ‎12-18-2018

hi everyone,

i am using a Cisco 1112 LTE Router and i cannot get LTE to start working.

This is the config I was using on a Cisco 8xx router before:

interface Dialer1
ip address negotiated
encapsulation slip
dialer pool 1
dialer idle-timeout 0
dialer string lte
dialer persistent

interface Cellular0
ip address negotiated
encapsulation slip
dialer in-band
dialer pool-member 1
async mode interactive
routing dynamic

Now when I try to do the same on the 1112, the following happens:

TEST(config)#int cel0/2/0
TEST(config-if)#dialer in-
TEST(config-if)#dialer in-band
TEST(config-if)#dialer pool-
TEST(config-if)#dialer pool-member 1
%Remove Legacy DDR Configuration first

I do not see any DDR configuration at all on this router...

Another problem for me:
"encapsulation slip" is not know under the cellular interface.

Any Ideas how to fix these issues?

attached you will find the complete config for the router (almost empty)

Georg Pauwen · ‎12-18-2018

Hello,

the 'dialer in-band' might be the problem, try and remove that...

beblos0003 · ‎12-18-2018

Hi Georg,

thanks for your answer.

I already tried that, unfortunately i will get the following error:

TEST(config)#int cel 0/2/0
TEST(config-if)#no dialer in
TEST(config-if)#no dialer in-band
TEST(config-if)#dialer pool-m
TEST(config-if)#dialer pool-member 1
%Configure a "dialer in-band", or "dialer pool" first.
TEST(config-if)#
TEST(config-if)#int dia1
TEST(config-if)#dialer
Dec 18 15:16:57.551: %LINK-3-UPDOWN: Interface Dialer1, changed state
TEST(config-if)#dialer pool 1
TEST(config-if)#int cell 0/2/0
TEST(config-if)#dialer pool-mem
TEST(config-if)#dialer pool-member 1
%Configure a "dialer in-band", or "dialer pool" first.
TEST(config-if)#

ninel · ‎05-19-2019

Hi,

I've opened a case to Cisco TAC and there answer was to use the code below because this is the new config style and the use of dialer interface will not work anymore for those routers ISR 4k / C1111

#[ISR 4k / C1111]
configure terminal
 dialer watch-list 1 ip 123.123.123.123 0.0.0.0 
 dialer watch-list 1 delay connect 1
dialer watch-list 1 delay route-check initial 60
interface cellular 0/2/0
 no dialer-group 1
 dialer watch-group 1

Georg Pauwen · ‎05-19-2019

Hello,

very good information ! I just checked the config guide for the ISR 1100, this is what is says:

--> The following features are not supported on Cisco 4G LTE Advanced C1100 Series ISR, when compared to Classic IOS:

TTY support or Line

Chat script/dialer string

External Dialer

That said, as far as I recall the dialer watch is used for dial backup...? I think the below should be sufficient to get the 4G working (and you do need the dialer-group and dialer-list):

interface Cellular0/2/1
ip address negotiated
dialer in-band
dialer idle-timeout 0
dialer-group 1
pulse-time 1
!

dialer-list 1 protocol ip permit

ninel · ‎05-20-2019

Helo, Georg,

The configuration you posted is exactly what I used before opening a case to Cisco.

It has a issue in C1111 (any IOS version), meaning that the Cellular interface will never get up by it self.

It will stay line protocol down no mater how you use it (VPN, direct route, etc).

#Valid code, but not working as expected
cellular 0/2/0 lte profile create 1 my.apn.name none ipv4
!
conf t
!
service internal
!
controller Cellular 0/2/0
 lte sim data-profile 1 attach-profile 1 slot 0
!
interface Cellular0/2/0
 description *** Link to ISP (GSM) ***
 ip address negotiated
 load-interval 30
 dialer in-band
 dialer idle-timeout 0
 dialer-group 1
 pulse-time 1
 ip virtual-reassembly in
!
ip route 0.0.0.0 0.0.0.0 Cellular0/2/0
dialer-list 1 protocol ip permit
!
end
!

To make this working (bring the interface UP manually) I had to ping something thru this interface.

But this is not a solution. So I used a event manager script to do that for me (It works with IP Sla as well)

ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
...!!
000098: Mar 17 13:44:27.725 : %LINK-3-UPDOWN: Interface Cellular0/2/0, changed state to up
000099: Mar 17 13:44:28.726 : %LINEPROTO-5-UPDOWN: Line protocol on Interface Cellular0/2/0, changed state to up
Success rate is 40 percent (2/5), round-trip min/avg/max = 32/112/192 ms

event manager session cli username "admin"
event manager applet FORCE_ENABLE_CELLULAR
 description *** Ping VPN server thru Ce0/2/0 - Otherwise Cellular int. will not get up ***
 event syslog pattern "CELLWAN-2-MODEM_RADIO: Cellular.* Modem radio has been turned on" ratelimit 120
 action 0 cli command "enable"
 action 1 cli command "ping 123.123.123.123"
 action 3 syslog priority alerts msg "EMA: *** BugFix Cellular: Pinging VPN server to bring it UP ***"
!

After that, I use the new code which seems to work as expected.

Remove anything related to Cellular/Dialer and add this.

Probably dialer watch is used for dial backups (use another sim/apn/whatever), but here is just used to activate the interface :D

cellular 0/2/0 lte profile create 1 my.apn.name none ipv4
!
configure terminal
!
#This is useful if you want to restart the cellular modem later
#test cellular 0/2/0 modem power-cicle
 service internal
!
 controller Cellular 0/2/0
  lte sim data-profile 1 attach-profile 1 slot 0
!
 dialer watch-list 1 ip 123.123.123.123 0.0.0.0 
 dialer watch-list 1 delay connect 1
 dialer watch-list 1 delay route-check initial 60
!
interface cellular 0/2/0
 no dialer-group 1
 dialer watch-group 1
!
ip route 0.0.0.0 0.0.0.0 Cellular0/2/0

Giuseppe Larosa · ‎05-20-2019

Hello Ninel,

you are reporting interesting info.

In old times the dialer watch was used when the backup interface was on a different router then the one having the primary interface with a routing protocol between them.

The dialer watch monitors the IP routing table if any route of the watch-list disappears it triggered a a call on backup interface.

I used it in this way many years ago.

Looking at your configuration I would say the following:

you have a single router

you just have a defaut route out of cellular interface

You are monitoring an host route 123.123.123.123/32 that is not present in your IP routing table.

As a result of this the dialer watch makes the device to trigger DDR on the cellular all times.

To be honest this looks like more a workaround then a new feature.

Hope to help

Giuseppe

ninel · ‎05-20-2019

Hello Giuseppe,

Maybe this is a workaround (recommended by cisco TAC), but it is the only thing that works for me :)
Ping something thru Cellular interface using 'IP SLA' or 'event manager applets' are other options, but those are not working as expected.

Giuseppe Larosa · ‎05-20-2019

Hello Ninel,

no problems ! I don't discuss this is a working solution suggested by Cisco TAC.

I just wanted to point out that dialer watch is not a new feature or new way to perform DDR as far as I know.

Best Regards

Giuseppe

asai1641979 · ‎10-18-2019

dialer watch-list worked for me

RouteOps_gm · ‎12-09-2021

I only just applied the dialer watch-list config as mentioned in the posts above, but my Cellular 0/2/0 interface came straight up when I did. I have a default route via Cellular0/2/0 so the IP being watched is in the routing table.

Time will tell whether the interface stays up - I will revert with more info.