From: Michael Brady (cisco@xxxxxxxxx)
Date: Sun Jan 06 2002 - 19:24:40 GMT-3
Hello Group,
I have a DLSW question on Lab 20. I could not get my DLSW peer between R5
and R14 (which is being NATed through R13) to come up. The peers to R1 and
R3 are working fine. After spending some time trying to figure out what was
happening, I looked at the answer configs. In the configs on R5 the local
peer ID is 200.150.150.5 (which is on Lo1). I was using 155.10.5.5 (lo0).
Other than that, my configuration was the same. I didn't see where Lo1 was
supposed to be created in the lab, but I figured I would give it a try to
see if it fixed the problem. After creating Lo1 and configuring
200.150.150.5 and putting this network into OSPF, I reconfigured my local
peer to 200.150.150.5. My peer to R14 (200.100.100.14) then came up. I
tried to put my configs back the way they were to see if maybe I was missing
something, but it still didn't work. Has anyone else come across this, or
does anyone know why the peer works when the peer id is 200.150.150.5 but
not when it is 155.10.5.5?
Thanks,
Michael
When I did a debug dlsw, this is what I was getting...
00:19:04: DLSw: START-TPFSM (peer 200.100.100.14(2065)): event:TIMER-TIMER
EXPIR
ED state:PCONN_WT
00:19:04: DLSw: dtp_action_b() close connection for peer
200.100.100.14(2065)
00:19:04: DLSw: aborting tcp connection for peer 200.100.100.14(2065)
00:19:04: DLSw: aborting tcp connection for peer 200.100.100.14(11022)
00:19:04: DLSw: END-TPFSM (peer 200.100.100.14(2065)):
state:PCONN_WT->DISCONN
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:17 GMT-3