Dialer Persistent
by David Sudjiman ~ February 3rd, 2010. Filed under: Uncategorized.What did I do wrong when I was configuring dialer watch as a backup link. All I could see was this.
003855: .Feb 3 19:45:41.736 AEDT: DDR: Dialer Watch: watch-group = 8 003856: .Feb 3 19:45:41.736 AEDT: DDR: network 10.10.10.0/255.255.255.252 UP, 003857: .Feb 3 19:45:41.736 AEDT: DDR: primary UP 003858: .Feb 3 19:45:42.736 AEDT: Ce0/0/0 DDR: rotor dialout [best] least recent failure is also most recent failure 003859: .Feb 3 19:45:42.736 AEDT: Ce0/0/0 DDR: rotor dialout [best] also has most recent failure 003860: .Feb 3 19:45:42.736 AEDT: Ce0/0/0 DDR: rotor dialout [best] 003861: .Feb 3 19:45:42.736 AEDT: Di1 DDR: Nailing up the Dialer profile [attempt 1] 003862: .Feb 3 19:45:42.736 AEDT: Di1 DDR: Dialer dialing - persistent dialer profile 003863: .Feb 3 19:45:42.736 AEDT: Ce0/0/0 DDR: Dialing cause Persistent Dialer Profile
My mind was wandering around checking why my dialer keeps dialing even when the network is UP. Checking the Cisco TAC case collection (case # K10813467) didn’t actually help much.
Apparently, the command dialer persistent causes this.
To force a dialer interface to be connected at all times, even in the absence of interesting traffic, use the dialer persistent command in interface configuration mode.