Re: DDR using wrong dialer map

ccsmith · ‎07-21-2005

I have a 3640 with a PRI that receives inbound DDR calls. Most of the sites use DDR as a backup to frame circuits. One site is DDR only. But when the Mayfield location dials in, it is assigned the wrong IP address by the PRI router. EIGRP still talks and traffic is passed, but now I can't get to that other IP address which happens to be a different location. Here's the maps in order that they appear:

dialer map ip 192.168.1.254 name morrisville2-Southport-Dr "#"

dialer map ip 192.168.9.254 name Columbia broadcast "#"

dialer map ip 192.168.10.254 name Charleston "#"

dialer map ip 192.168.14.254 name mayfield broadcast "#"

Mayfield is the pure DDR site. But it is getting the Morrisville IP assigned to it on the PRI (viewed in PRI's routing table). The Mayfield router NACK's the assignment and doesn't put it into the routing table. I have other customers using a similar config without these types of results. Does anyone know of a situation where the hostname match isn't working and the first dialermap is used instead? BTW the hostname does match exactly including case.

Thank you,

Chris Smith

b-ulrich · ‎07-21-2005

Hi,

You may want to run 'debug ppp authentication' or debug ppp negotiation' on the 3640 when Mayfield is dialing in to see if there are CHAP issues, ect.

Posting configs on the 3460 and the Mayfield router may help too.

ccsmith · ‎07-21-2005

I tried that and found that the PRI router seems to be the issue. Here's the Debug from the PRI router:

Mar 26 09:26:39.440: As81 LCP: I CONFACK [ACKsent] id 31 len 24

*Mar 26 09:26:39.440: As81 LCP: ACCM 0x000A0000 (0x0206000A0000)

*Mar 26 09:26:39.440: As81 LCP: AuthProto PAP (0x0304C023)

*Mar 26 09:26:39.440: As81 LCP: MagicNumber 0x9341806F (0x05069341806F)

*Mar 26 09:26:39.440: As81 LCP: PFC (0x0702)

*Mar 26 09:26:39.440: As81 LCP: ACFC (0x0802)

*Mar 26 09:26:39.440: As81 LCP: State is Open

*Mar 26 09:26:39.440: As81 PPP: Phase is AUTHENTICATING, by this end

*Mar 26 09:26:42.124: As76 EVT: Packet 0 0x61B31CC0

*Mar 26 09:26:49.432: As81 EVT: Auth Packet 0 0x61A7A838

*Mar 26 09:26:49.432: As81 PAP: I AUTH-REQ id 4 len 22 from "mayfield"

*Mar 26 09:26:49.432: As81 PAP: Authenticating peer mayfield

*Mar 26 09:26:49.432: As81 PPP: Phase is FORWARDING, Attempting Forward

*Mar 26 09:26:49.436: As81 EVT: Hook 1 0x00000000

*Mar 26 09:26:49.436: As81 EVT: Forwarded 0 0x00000000

*Mar 26 09:26:49.436: As81 PPP: Phase is AUTHENTICATING, Unauthenticated User

*Mar 26 09:26:49.436: As81 PPP: Sent PAP LOGIN Request

*Mar 26 09:26:49.436: As81 EVT: AAA Response 0 0x61B885DC

*Mar 26 09:26:49.436: As81 PPP: Received LOGIN Response PASS

*Mar 26 09:26:49.440: As81 PPP: Phase is FORWARDING, Attempting Forward

*Mar 26 09:26:49.440: As81 EVT: Hook 1 0x00000000

*Mar 26 09:26:49.440: As81 EVT: Forwarded 0 0x00000000

*Mar 26 09:26:49.440: As81 PPP: Phase is AUTHENTICATING, Authenticated User

*Mar 26 09:26:49.440: As81 PAP: O AUTH-ACK id 4 len 5

*Mar 26 09:26:49.444: As81 PPP: Phase is UP

*Mar 26 09:26:49.444: As81 IPCP: O CONFREQ [Closed] id 1 len 16

*Mar 26 09:26:49.444: As81 IPCP: CompressType VJ 15 slots (0x0206002D0F00)

*Mar 26 09:26:49.444: As81 IPCP: Address 172.30.130.250 (0x0306AC1E82FA)

*Mar 26 09:26:49.444: As81 PPP: Process pending ncp packets

*Mar 26 09:26:49.496: As73 EVT: Packet 0 0x61B250B4

*Mar 26 09:26:49.600: As81 EVT: IPCP Packet 0 0x61A7B12C

*Mar 26 09:26:49.600: As81 IPCP: I CONFREQ [REQsent] id 3 len 16

*Mar 26 09:26:49.600: As81 IPCP: CompressType VJ 15 slots (0x0206002D0F00)

*Mar 26 09:26:49.600: As81 IPCP: Address 192.168.14.254 (0x0306C0A80EFE)

*Mar 26 09:26:49.600: As81 IPCP: O CONFNAK [REQsent] id 3 len 10

*Mar 26 09:26:49.600: As81 IPCP: Address 192.168.1.254 (0x0306C0A801FE)

*Mar 26 09:26:49.612: As81 EVT: IPCP Packet 0 0x61A7AE30

*Mar 26 09:26:49.612: As81 IPCP: I CONFACK [REQsent] id 1 len 16

*Mar 26 09:26:49.612: As81 IPCP: CompressType VJ 15 slots (0x0206002D0F00)

*Mar 26 09:26:49.612: As81 IPCP: Address 172.30.130.250 (0x0306AC1E82FA)

*Mar 26 09:26:49.756: As81 EVT: IPCP Packet 0 0x61A7A838

*Mar 26 09:26:49.756: As81 IPCP: I CONFREQ [ACKrcvd] id 4 len 10

*Mar 26 09:26:49.756: As81 IPCP: CompressType VJ 15 slots (0x0206002D0F00)

*Mar 26 09:26:49.756: As81 IPCP: O CONFACK [ACKrcvd] id 4 len 10

*Mar 26 09:26:49.756: As81 IPCP: CompressType VJ 15 slots (0x0206002D0F00)

*Mar 26 09:26:49.756: As81 IPCP: State is Open

*Mar 26 09:26:49.756: As81 EVT: IPCP UP 0 0x61AE068C

*Mar 26 09:26:49.760: As81 EVT: Add Route 0 0xC0A801FE

*Mar 26 09:26:49.760: As81 IPCP: Install route to 192.168.1.254

*Mar 26 09:26:49.760: As81 IPCP: Add link info for cef entry 192.168.1.254

*Mar 26 09:26:50.440: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async81, changed state to up

*Mar 26 09:26:52.364: As76 EVT: Packet 0 0x61B322B8

*Mar 26 09:26:53.324: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 192.168.14.254 (Async81) is up: new adjacency

You'll notice at the bottom that IPCP installed the /32 route (the wrong one) and that EIGRP was able to get the proper /24 entered into the table. I'll put the other side in the next post.

Thanks,

Chris

ccsmith · ‎07-21-2005

On the remote side you see something like this:

---truncated top of debug-------

1:20:23: As5 PPP: Phase is UP

01:20:23: As5 IPCP: O CONFREQ [Closed] id 3 len 16