From: Mike Schlenger (mschlenger@xxxxxxxxxxxxxxxx)
Date: Wed May 16 2001 - 16:53:52 GMT-3
The dlsw bgroup and ring list commands will forward netbios and explorer
traffic to ONLY those rings listed in the command. ( Ex:dlsw bgroup-list
1 bgroups 1 2) will only forward netbios to bridge groups 1 and 2. Don't
forget to add the bgroup list to your remote peer. (dlsw remote-peer 1 tcp
1.1.1.1) Apply the same concept to Token Ring segments.... Remember, this is
configured for what you want to happen locally.....you apply it to the
remote peer statement on the local router so the remote router gets the info
during the capabilities exchange....
Mike
7079
-----Original Message-----
From: Kurt Bergsbaken [mailto:kbergsbaken@c-lcom.com]
Sent: Wednesday, May 16, 2001 11:44 AM
To: 'Ccielab (E-mail)
Subject: DLSW+ bgroup command
Can anyone help me understand when to use, and how to apply the dlsw
bgroup-list command?
Would this be useful if there were 2 vlans, vlan a has 2 ethernet attached
router interfaces, then across the ip cloud vlan b had the same. If the 4
interfaces need to establish peer connectivity, can this be done without the
border statement or without a full mesh. Does
the bgroup list command help here, and what would the config look like? I
have not found a single sample config in any of the Cisco Press books, or on
the CD, that uses this command.
Thanks
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:42 GMT-3