user manual

Configuring Data-Link Switching Plus
DLSw+ Configuration Task List
BC-308
Cisco IOS Bridging and IBM Networking Configuration Guide
78-11737-02
Figure 130 Mapping Traffic Using Port Lists
The definition of a port list is optional. If you want all peers and all interfaces to receive all traffic, you
do not have to define a port list. Simply specify 0 for the list number in the remote peer statement.
To define a port list, use the following command in global configuration mode:
Note Either the ring list or the port list command can be used to associate rings with a given ring list. The
ring list command is easier to type in if you have a large number of rings to define.
DLSw+ Bridge Group List
DLSw+ bridge group lists map traffic on the local Ethernet bridge group interface to remote peers. You
can create a bridge group list and apply the list to remote peer definitions. Traffic received from a remote
peer is only forwarded to the bridge group specified in the bridge group list. Traffic received from a local
interface is only forwarded to peers if the input bridge group number appears in the bridge group list
applied to the remote peer definition. The definition of a bridge group list is optional. Because each
remote peer has a single list number associated with it, if you want traffic to go to a bridge group and to
either a ring list or port list, you should specify the same list number in each definition
To define a bridge-group list, use the following command in global configuration mode:
51860
Token
Ring
19
Token
Ring
22
Token
Ring
12
Token
Ring
15
Port list 2
Explorer
Port list 1
Peer B: Port list 1
Peer C: Port list 2
Peer B
Peer C
Peer A
Command Purpose
Router(config)# dlsw port-list list-number type
number
Defines a port list.
Command Purpose
Router(config)# dlsw bgroup-list list-number
bgroups number
Defines a ring list.