From: Shaun Wakelen (Shaun.Wakelen@xxxxxxxxxxxxxx)
Date: Fri Feb 08 2002 - 13:31:17 GMT-3
I follow the same 3920 steps as you, and unless otherwise stated, is
probably best. If you wanted to bridge between the two rings, then let them
have the same BRF, otherwise, keep them separate. When giving names to BRF's
and CRF's, use the ring number as it is easier to follow if you have to
troubleshoot your config for any reason. There is a good document on CCO
that deals with configuring 3900 and Cat5k's. It is called 'Using a Switch
for Ring Microsegmentation'. Sorry but I have not got the URL for it.
DLSw is not my strongest subject, but I thought backup peers did not drop if
there were sessions open. I'll have to check on that, as I'm sure there must
be a config option to drop them quicker.
-----Original Message-----
From: DAN DORTON [mailto:DHSTS68@dhs.state.il.us]
Sent: 08 February 2002 14:50
To: ccielab@groupstudy.com; Shaun.Wakelen@telindus.co.uk;
jantocin@yahoo.com
Subject: DLSW+ Backup & TR3900 configuration questions.
Is anyone able to make backup peers sucessfully drop when you cannot use
the promicuous keywords in any of the local peer statements?
I seen a few examples on ciscos tac site & decided to try it for
myself.
I have lab'ed this up a bunch of times, but the backup peer always
stays up even if I use linger 0.
Should I maybe try dynamic for the remote peer statements?
Any help would be greatly appreciated.
Also I would like an opinion on how most would configure a 3900
switch.
In one of my practice labs it says to configure ring 1 & ring 2, set
ring 1's bridge number to 1 & ring 2's bridge number to 2 & do not use
any default configurations.
I am assuming the no default means that you cannot use the default
trbrf, or trcrf.
In the past I have been creating a trbrf called bridge1 & then creating
a trcrf called ring1 under that & giving them both bridge number 1.
I do the same for ring2.
I am not sure that I am doing this correctly due to my lack of token
ring switching experience & lack of decent example material.
Anyone that can elaborate on the topics for me would be greatly
appreciated.
Thanks a bunch.
Dan
>>> Shaun Wakelen <Shaun.Wakelen@telindus.co.uk> 02/08/02 06:53AM >>>
On Vader, don't have a remote peer to skywalker, and use promiscuous on
the
local peer. That way, it will only peer to skywalker, if skywalker
requests
it.
-----Original Message-----
From: Janto Cin [mailto:jantocin@yahoo.com]
Sent: 08 February 2002 08:38
To: ccielab@groupstudy.com
Subject: DLSW+ Backup
Hi All,
I have problem when configuring DLSW+ Backup feature.
The network model same like in page 907 of Karl Solie's CCIE Practical
Studies Vol. I book.
I tried to configure backup peer for router skywalker, the primary
peer
is router solo, and the backup peer is router vader.
The DLSW+ configuration for the each router is like below:
Router Skywalker configuration:
=======================
skywalker#sh ru
Building configuration...
Current configuration:
!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname skywalker
!
dlsw local-peer peer-id 172.16.128.5
dlsw remote-peer 0 tcp 172.16.128.9
dlsw remote-peer 0 tcp 172.16.128.1 backup-peer 172.16.128.9 linger 5
dlsw bridge-group 1
!
interface Loopback20
ip address 172.16.128.5 255.255.255.252
!
interface Ethernet0
ip address 172.16.5.1 255.255.255.0
no keepalive
bridge-group 1
!
interface Serial0
ip address 172.16.1.5 255.255.255.0
encapsulation frame-relay
frame-relay map ip 172.16.1.6 111 broadcast
frame-relay map ip 172.16.1.1 111 broadcast
no frame-relay inverse-arp
frame-relay lmi-type ansi
!
interface Serial1
no ip address
shutdown
!
router eigrp 65001
network 172.16.0.0
no auto-summary
!
ip classless
!
bridge 1 protocol ieee
!
line con 0
line aux 0
line vty 0 4
login
!
end
Router Solo configuration:
===================
solo#sh ru
Building configuration...
Current configuration:
!
version 11.2
no service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname solo
!
dlsw local-peer peer-id 172.16.128.9
dlsw remote-peer 0 tcp 172.16.128.5
dlsw bridge-group 1
!
interface Loopback20
ip address 172.16.128.9 255.255.255.252
!
interface Ethernet0
ip address 172.16.6.1 255.255.255.0
no keepalive
bridge-group 1
!
interface Serial0
ip address 172.16.1.6 255.255.255.0
encapsulation frame-relay
no fair-queue
frame-relay map ip 172.16.1.5 131 broadcast
frame-relay map ip 172.16.1.1 131 broadcast
no frame-relay inverse-arp
!
interface Serial1
no ip address
shutdown
!
router eigrp 65001
network 172.16.0.0
!
no ip classless
!
bridge 1 protocol ieee
!
line con 0
line aux 0
line vty 0 4
login
!
end
Router Vader configuration:
====================
vader#sh ru
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname vader
!
memory-size iomem 15
ip subnet-zero
!
source-bridge ring-group 110
dlsw local-peer peer-id 172.16.128.1
dlsw remote-peer 0 fst 172.16.128.13
dlsw remote-peer 0 tcp 172.16.128.5
!
interface Loopback20
ip address 172.16.128.1 255.255.255.252
no ip directed-broadcast
!
interface Ethernet0/0
no ip address
no ip directed-broadcast
shutdown
!
interface Serial0/0
no ip address
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
frame-relay lmi-type ansi
!
interface Serial0/0.1 multipoint
ip address 172.16.1.1 255.255.255.0
no ip directed-broadcast
no ip split-horizon eigrp 65001
frame-relay map ip 172.16.1.5 110 broadcast
frame-relay map ip 172.16.1.6 130 broadcast
!
interface Serial0/0.2 point-to-point
ip address 172.16.2.1 255.255.255.252
no ip directed-broadcast
frame-relay interface-dlci 180
!
interface TokenRing0/0
ip address 172.16.30.1 255.255.255.0
no ip directed-broadcast
ring-speed 16
source-bridge 1 1 110
source-bridge spanning
!
interface Serial0/1
no ip address
no ip directed-broadcast
shutdown
!
router eigrp 65001
network 172.16.0.0
no auto-summary
no eigrp log-neighbor-warnings
!
ip classless
no ip http server
!
line con 0
transport input none
speed 19200
line aux 0
line vty 0 4
!
no scheduler allocate
end
Router Chewbacca configuration:
========================
chewbacca#sh ru
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname chewbacca
!
memory-size iomem 20
ip subnet-zero
!
source-bridge ring-group 111
dlsw local-peer peer-id 172.16.128.13
dlsw remote-peer 0 fst 172.16.128.1
!
interface Loopback20
ip address 172.16.128.13 255.255.255.252
no ip directed-broadcast
!
interface Ethernet0/0
no ip address
no ip directed-broadcast
shutdown
!
interface Serial0/0
ip address 172.16.2.2 255.255.255.252
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
no fair-queue
frame-relay interface-dlci 181
!
interface TokenRing0/0
ip address 172.16.3.1 255.255.255.0
no ip directed-broadcast
ring-speed 16
source-bridge 1 2 111
source-bridge spanning
!
interface Serial0/1
no ip address
no ip directed-broadcast
shutdown
!
router eigrp 65001
network 172.16.0.0
no eigrp log-neighbor-warnings
!
ip classless
no ip http server
!
line con 0
transport input none
speed 19200
line aux 0
line vty 0 4
!
no scheduler allocate
end
Below is the result of 'show dlsw peer' command for each router:
Skywalker
========
skywalker#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.9 CONNECT 506 506 conf 0 0
0
04:16:05
TCP 172.16.128.1 DISCONN 0 0 conf 0 0
-
-
skywalker#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.9 CONNECT 506 506 conf 0 0
0
04:16:07
TCP 172.16.128.1 DISCONN 0 0 conf 0 0
-
-
skywalker#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.9 CONNECT 506 506 conf 0 0
0
04:16:08
TCP 172.16.128.1 DISCONN 0 0 conf 0 0
-
-
skywalker#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.9 CONNECT 506 506 conf 0 0
0
04:16:08
TCP 172.16.128.1 DISCONN 0 0 conf 0 0
-
-
skywalker#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.9 CONNECT 506 506 conf 0 0
0
04:16:09
TCP 172.16.128.1 CONNECT 2 2 conf 0 0
0
00:00:00
skywalker#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.9 CONNECT 506 506 conf 0 0
0
04:16:10
TCP 172.16.128.1 CONNECT 2 2 conf 0 0
0
00:00:01
Solo
===
solo#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
TCP 172.16.128.5 CONNECT 524 524 conf 0 0
0
04:22:22
Vader
=====
vader#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
FST 172.16.128.13 CONNECT 17 17 conf 0 - -
00:07:56
Expected: 0 Next Send: 0 Seq errors: 0
TCP 172.16.128.5 CONNECT 15 15 conf 0 0 0
00:06:33
Total number of connected peers: 2
Total number of connections: 2
Chewbacca
=========
chewbacca#sh dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts
TCP
uptime
FST 172.16.128.1 CONNECT 18 18 conf 0 - -
00:08:22
Expected: 0 Next Send: 0 Seq errors: 0
Total number of connected peers: 1
Total number of connections: 1
The question is why the peer connection between skywalker and vader
can
be CONNECT ?
Is this correct ? Pls help me.
TIA,
Janto
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:15 GMT-3