×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

dlsw backup-peer problem

Unanswered Question
Jan 3rd, 2003
User Badges:

hi,

my problem:


i have a 3640 router which has a "production"-dlsw connection to a 7513 router.

i also configured a "backup"-dlsw connection to a backup 7513 router with the "backup-peer"

command.

everything looks fine - if the prodconnection fails the 3640 turns over to the backup7513.

if the prod7513 comes back again and the linger timer goes over, the 3640 gets the connection

back to the prod7513 and turns of the dlsw-connection to the backup7513.

so far - so good.


but if the enddevice tries to connect it fails for several times.

after about 10 to 15 minutes the connection is ok.


i checked the dlsw reachability-cache in the 3640 (sh dlsw reach) and saw that it could not find

the mac-adr for the 10 to 15 minutes.


the two 3640 are connected over two escon-channels to a ibm host.


i turned on "debug dlsw reach", ... and saw that the 3640 sends out a "test-frame" and

there was no response from the prod7513.


after the 10 to 15 minutes everything is ok - the 3640 sends the test-frame - the pro7513

sends a response and so on - everything ok.


i really do not understand why it takes so long that the prod7513 needs so long

to answer to the test-frame.


any idea ????

here is debug:

XOT-GW1#sh dlsw re

DLSw Local MAC address reachability cache list

Mac Addr status Loc. port rif

4000.1111.0000 FOUND LOCAL Serial0/1 --no rif--

4000.7507.1000 SEARCHING LOCAL

DLSw Remote MAC address reachability cache list

Mac Addr status Loc. peer

4000.7507.1000 SEARCHING REMOTE

DLSw Local NetBIOS Name reachability cache list

NetBIOS Name status Loc. port rif

DLSw Remote NetBIOS Name reachability cache list

NetBIOS Name status Loc. peer

XOT-GW1#

Jan 3 18:26:38.348: CSM: smac 4000.1111.0000, dmac 4000.7507.1000, ssap 4 , d

sap 4

Jan 3 18:26:38.348: DISP Sent : CLSI Msg : TEST_STN.Req dlen: 46

Jan 3 18:26:53.344: Serial0/1: X.25 O R1 Clear (5) 8 lci 1

Jan 3 18:26:53.344: Cause 0, Diag 114 (DTE originated/International protocol

problem)

Jan 3 18:26:53.344: Serial0/0: X.25 I R1 Clear (5) 8 lci 1

Jan 3 18:26:53.344: Cause 0, Diag 114 (DTE originated/International protocol

problem)

Jan 3 18:26:53.344: [10.22.223.10,15198/10.18.254.221,1998]: XOT O P4 Clear (5)

8 lci 1

Jan 3 18:26:53.344: Cause 0, Diag 114 (DTE originated/International protocol

problem)

Jan 3 18:26:53.600: [10.22.223.10,15198/10.18.254.221,1998]: XOT I P6 Clear Con

firm (3) 8 lci 1

Jan 3 18:26:53.600: Serial0/0: X.25 O R1 Clear Confirm (3) 8 lci 1

Jan 3 18:26:53.604: Serial0/1: X.25 I R1 Clear Confirm (3) 8 lci 1

Jan 3 18:26:54.141: DLSw: Keepalive Request sent to peer 10.18.254.243(2065))

Jan 3 18:26:54.145: DLSw: Keepalive Response from peer 10.18.254.243(2065)

XOT-GW1#

XOT-GW1#

XOT-GW1#

XOT-GW1#


it really looks that the 7513 sends no answer to the test-frame !


thanks for an answer !

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
mmolina2 Fri, 01/03/2003 - 12:07
User Badges:

Have you considered "statically" configuring your reachability cache on the PROD 7513/backup 7513 with a "dlsw icanreach mac" command ? Also, you can use costing as opposed to the "backup peer" configuration for quicker failover/recovery. Basically, if you make the cost of the backup 7513 greater than the PROD 7513, the 3640 will always have 2 connected peers but will prefer the PROD 7513 until it fails. If there is a failure on the PROD 7513, your peer will already be connected and ready to use for the backup 7513 . Good luck !

Actions

This Discussion