user manual

Configuring Data-Link Switching Plus
DLSw+ Configuration Task List
BC-288
Cisco IOS Bridging and IBM Networking Configuration Guide
78-11737-02
Figure 129 VDLC Interaction with Higher-Layer Protocols
The higher-layer protocols make no distinction between the VDLC and any other data-link control, but
they do identify the VDLC as a destination. In the example shown in Figure 129, SNASw has two ports:
a physical port for Token Ring and a virtual port for the VDLC. When you define the SNASw VDLC
port, you can specify the MAC address assigned to it. Data transport from SNASw to DLSw+ by way of
the VDLC is directed to the VDLC MAC address. The type of higher-layer protocol you use determines
how the VDLC MAC address is assigned.
DLSw+ Configuration Task List
DLSw+ supports local or remote media conversion between LANs and SDLC or QLLC.
To configure DLSw+, complete the tasks in the following sections:
• Defining a DLSw+ Local Peer for the Router, page 288
• Defining a DLSw+ Remote Peer, page 289
• Mapping DLSw+ to a Local Data-Link Control, page 292
• Configuring Advanced Features, page 295
• Configuring DLSw+ Timers, page 310
See the “DLSw+ Configuration Examples” section on page 312 for examples.
Defining a DLSw+ Local Peer for the Router
Defining a DLSw+ local peer for a router enables DLSw+. Specify all local DLSw+ parameters as part
of the local peer definition. To define a local peer, use the following command in global configuration
mode:
The following is a sample dlsw local peer statement:
dlsw local peer peer-id 10.2.34.3
SNASw
DLSw+ Data-link users
5
1909
Data-link contro
ls
CLSI
VDLC
Ethernet
Token
Ring
Command Purpose
Router(config)# dlsw local peer [peer-id
ip-address] [group group] [border] [cluster
cluster-id] [cost cost] [lf size] [keepalive
seconds] [passive] [promiscuous]
[init-pacing-window size] [max-pacing-window
size] [biu-segment]
Defines the DLSw+ local peer.