![](/images/new-backgrounds/1306932/3069323x1.webp)
Configuring
Technology Overview
DLSw Standard
The DLSw standard, documented in RFC 1795, defines the
The DLSw standard does not specify when to establish TCP connections. The capabilities exchange allows compliance to the standard, but at different levels of support. The standard does not specify how to cache learned information about MAC addresses, RIFs, or NetBIOS names. It also does not describe how to track either capable or preferred DLSw partners for either backup or
DLSw Version 2 Standard
In the Version 1 standard, a network design requires fully meshed connectivity so that all peers were connect to every other peer. This design creates unnecessary broadcast traffic because an explorer propagates to every peer for every broadcast.
The Version 2 standard is documented in RFC 2166. It includes RFC 1795 and adds the following enhancements:
•IP Multicast, page 282
•UDP Unicast, page 283
•Enhanced
•Expedited TCP Connection, page 283
Users implement DLSw Version 2 for scalability if they are using multivendor DLSw devices with an IP multicast network. DLSw Version 2 requires complex planning because it involves configuration changes across an IP network.
IP Multicast
Multicast service avoids duplication and excessive bandwidth of broadcast traffic because it replicates and propagates messages to its multicast members only as necessary. It reduces the amount of network overhead in the following ways:
•Avoids the need to maintain TCP
•Ensures that each broadcast results in only a single explorer over every link
DLSw Version 2 is for customers who run a multicast IP network and do not need the advantages of border peering.
| Cisco IOS Bridging and IBM Networking Configuration Guide |
|