RE: dlsw direct encapsulation

From: McCallum, Robert (Robert.McCallum@xxxxxxxxxxxxxxxxxx)
Date: Wed Jan 09 2002 - 13:31:38 GMT-3


   
Stephen,

to be honest it is one of the configs that I haven't tried so you are probably
correct. I just squizzed through the config and noted the glaring errors. I h
ave a lab setup just now so I will rattle off some config and see what happens.

Good work!

-----Original Message-----
From: Stephen C. Feldberg [mailto:scfeldberg@hotmail.com]
Sent: 09 January 2002 15:51
To: McCallum, Robert; 463946@hongkong.com; ccielab@groupstudy.com
Subject: Re: dlsw direct encapsulation

Robert,

According to the chart on p.905 of CCIE Practical Studies, direct
encapsulation does not support backup peers. I have read your threads on
DLSW, so I know that you have worked with it in your lab(often longer than
you wanted to). Is this a misprint, or a feature of newer IOS?

Steve
----- Original Message -----
From: "McCallum, Robert" <Robert.McCallum@let-it-be-thus.com>
To: <463946@hongkong.com>; <ccielab@groupstudy.com>
Sent: Wednesday, January 09, 2002 4:32 AM
Subject: RE: dlsw direct encapsulation

> remove the local-peer ip address on your spokes i.e. just have dlsw local
peer promiscuous and then remove your remote peer statements back to your
hub on your spokes. See if that helps.
>
> Remember you are doing direct encapsulation so why state that your peer id
is an ip address??
>
> -----Original Message-----
> From: 463946@hongkong.com [mailto:463946@hongkong.com]
> Sent: 09 January 2002 09:03
> To: ccielab@groupstudy.com
> Subject: dlsw direct encapsulation
>
>
> Hi Group,
>
> I am testing the dlsw with different encapsulations and I cannot do the
backup peer with frame relay
> direct encapsulation.
>
> R1 is connecting to R2 and R3 with FR. I want R3 to backup R2.
> My problem is: I have to enter the dlsw remote-peer.... in R3. If not, R3
cannot peer with R1
> even R2 is gone. But, when I enter that command, R3 will peer with R1 if
R2 is still alive.
>
> The configurations:
>
>
> R1's Configuration:
>
> dlsw local-peer peer-id 172.2.1.1
> dlsw remote-peer 0 frame-relay interface Serial0/0.1 502
> dlsw remote-peer 0 frame-relay interface Serial0/0.1 503 backup-peer
frame-relay interface Serial0/0.1 502 circuit-inactivity 1
> !
> interface Loopback0
> ip address 172.2.1.1 255.255.255.0
> !
> interface Serial0/0
> no ip address
> encapsulation frame-relay
> no fair-queue
> !
> interface Serial0/0.1 multipoint
> ip address 172.2.10.1 255.255.255.0
> frame-relay map llc2 503 broadcast
> frame-relay map llc2 502 broadcast
> frame-relay map ip 172.2.10.2 102 broadcast
> frame-relay map ip 172.2.10.3 103 broadcast
>
> R1#sh dlsw peer
> Peers: state pkts_rx pkts_tx type drops ckts TCP
uptime
> LLC2 Se0/0.1 102 CONNECT 19 19 conf 0 0 -
00:08:18
> LLC2 Se0/0.1 103 CONNECT 17 17 conf 0 0 -
00:08:03
> Total number of connected peers: 2
> Total number of connections: 2
>
>
> R2's Configuration:
>
> dlsw local-peer peer-id 172.2.23.2 promiscuous
> dlsw remote-peer 0 frame-relay interface Serial0 201
> !
> interface Ethernet0
> ip address 172.2.23.2 255.255.255.240
> no ip directed-broadcast
> bridge-group 1
> !
> interface Serial0
> ip address 172.2.10.2 255.255.255.0
> no ip directed-broadcast
> encapsulation frame-relay
> frame-relay map llc2 205 broadcast
> frame-relay map ip 172.2.10.3 201 broadcast
> frame-relay map ip 172.2.10.5 201 broadcast
>
> R3's Configuration:
>
> dlsw local-peer peer-id 172.2.23.3 promiscuous
> dlsw remote-peer 0 frame-relay interface Serial0 301
> dlsw bridge-group 1
>
> interface Ethernet0
> ip address 172.2.23.3 255.255.255.240
> no ip directed-broadcast
> bridge-group 1
> !
> interface Serial0
> ip address 172.2.10.3 255.255.255.0
> no ip directed-broadcast
> encapsulation frame-relay
> frame-relay map llc2 305 broadcast
> frame-relay map ip 172.2.10.2 301 broadcast
> frame-relay map ip 172.2.10.5 301 broadcast
>
> TIA
>
> Alex
> ----------------------------------------------
> Ew*o(O%NHongKong.com6l%s(t2N
> Thank you for using hongkong.com Email system



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:21 GMT-3