Cisco Systems BC-281 manual LLC1 Circuits, Dynamic Peers, Configures a dynamic peer, BC-302

Page 22

Configuring Data-Link Switching Plus

DLSw+ Configuration Task List

LLC1 Circuits

Support for LLC1 circuits more efficiently transports LLC1 UI traffic across a DLSw+ cloud. With LLC1 circuit support, the LLC1 unnumbered information frames (UI) are no longer subject to input queueing and are guaranteed to traverse the same path for the duration of the flow. This feature improves transportation of LLC1 UI traffic because there is no longer the chance of having a specifically routed LLC1 UI frame broadcast to all remote peers. The circuit establishment process has not changed except that the circuit is established as soon as the specifically routed LLC1 UI frame is received and the DLSw+ knows of reachability for the destination MAC address. Furthermore, the connection remains in the CIRCUIT_ESTABLISHED state (rather than proceeding to the CONNECT state) until there is no UI frame flow for a MAC/SAP pair for 10 minutes.

This feature is enabled by default.

Dynamic Peers

In TCP encapsulation, the dynamic option and its suboptions no-llcand inactivity allow you to specify and control the activation of dynamic peers, which are configured peers that are activated only when required. Dynamic peer connections are established only when there is DLSw+ data to send. The dynamic peer connections are taken down when the last LLC2 connection using them terminates and the time period specified in the no-llcoption expires. You can also use the inactivity option to take down dynamic peers when the circuits using them are inactive for a specified number of minutes.

Note Because the inactivity option may cause active LLC2 sessions to be terminated, you should not use this option unless you want active LLC2 sessions to be terminated.

To configure a dynamic peer, use the following command in global configuration mode:

Command

Purpose

 

 

Router(config)# dlsw remote-peer list-numbertcp

Configures a dynamic peer.

ip-address [backup-peer [ip-address

 

frame-relay interface serial number dlci-number

 

interface name]] [bytes-netbios-out

 

bytes-list-name][circuit-weightweight]

 

[cluster cluster-id] [cost cost] [dest-mac

 

mac-address][dmac-output-list

 

access-list-number][host-netbios-out

 

host-list-name] [inactivity] [dynamic]

 

[keepalive seconds] [lf size] [linger minutes]

 

[lsap-output-list list] [no-llc minutes]

 

[passive] [priority] [rif-passthru

 

virtual-ring-number][tcp-queue-maxsize]

 

[timeout seconds]

 

 

 

The following command specifies a dynamic peer with TCP encapsulation:

dlsw remote-peer 0 tcp 10.23.4.5 dynamic

Promiscuous Peer Defaults

If you do not configure a dlsw remote-peerstatement on the DLSw+ router, then you must specify the promiscuous keyword on the dlsw local-peerstatement. The promiscuous keyword enables the router to accept peer connection requests from those routers that are not preconfigured. Setting the dlsw prom-peer-defaultscommand allows the user to determine various settings for the promiscuous transport.

 

Cisco IOS Bridging and IBM Networking Configuration Guide

BC-302

78-11737-02

Image 22
Contents Configuring Data-Link Switching Plus BC-281IP Multicast DLSw StandardDLSw Version 2 Standard BC-282UDP Unicast DLSw+ FeaturesEnhanced Peer-on-Demand Routing Feature Expedited TCP ConnectionLocal Acknowledgment BC-284BC-285 LLC2 Session without Local AcknowledgmentBC-286 DLSw+ Support for Other SNA Features BC-287Defines the DLSw+ local peer Command PurposeDefining a DLSw+ Local Peer for the Router Following is a sample dlsw local peer statementTCP Encapsulation Defining a DLSw+ Remote PeerBC-289 Defines a remote peer with FST encapsulation TCP/IP with RIF Passthrough EncapsulationFST Encapsulation BC-290Defines a remote peer with direct encapsulation Direct EncapsulationDLSw Lite Encapsulation Defines a remote peer with DLSw Lite encapsulationToken Ring Mapping DLSw+ to a Local Data-Link ControlBC-292 Ethernet BC-293Associated with this serial interface Enables DLSw+ on an Sdlc interfaceBC-294 Configuring Advanced Features BC-295Peer Groups and Border Peers ScalabilityBC-296 BC-297 Enables peer groups and border peers BC-298Local, remote, and group caches Configures peer-on-demand defaultsBC-299 Following command enables NetBIOS DDR Displays content of group, local and remote cachesNetBIOS Dial-on-Demand Routing Explorer FirewallsSNA Dial-on-Demand Routing Following command configures the SNA DDR featureUDP Unicast Feature BC-301LLC1 Circuits Configures a dynamic peerPromiscuous Peer Defaults Dynamic PeersLoad Balancing Configures promiscuous peer defaultsAvailability BC-303Local router BC-304Ethernet Redundancy Configures transparent redundancyBackup Peers Addresses on a transparent bridged are mappedModes of Operation Configures a backup peerBC-306 Traffic Bandwidth and Queueing Management Access ControlNetwork Management BC-307DLSw+ Bridge Group List Defines a port listBC-308 Static Resources Capabilities Exchange Filter Lists in the Remote-Peer CommandStatic Paths BC-309Configuring DLSw+ Timers BC-310BC-311 Following sections provide DLSw+ configuration examples BC-312Router B Router aBC-313 BC-314 DLSw+ with Peer Groups Specified ExampleRouter C BC-315BC-316 FEPRouter D BC-317Following example, all devices are type PU DLSw+ with Sdlc Multidrop Support Configuration ExamplesRouter E BC-318Following example, all devices are type PU 2.1 Method BC-319BC-320 Hostname Router aBC-321 DLSw+ Translation Between Fddi and Token RingDLSw+ Translation Between Sdlc and Token Ring Media Example BC-322BC-323 Sdlc partner 1000.5aed.1f53 d2 sdlc dlsw d2Ring DLSw+ over Frame Relay Configuration ExampleBC-324 Example DLSw+ over Qllc Configuration ExamplesFollowing three examples describe Qllc support for DLSw+ BC-325DLSw+ with RIF Passthrough Configuration Example BC-326DLSw+ with Enhanced Load Balancing Configuration Example BC-327DLSw+ Peer Cluster Feature Configuration Example BC-328DLSWRTR2 BC-329Shows a DLSw+ border peer network configured with DLSw+ Rsvp BC-330DLSw+ with Ethernet Redundancy Configuration Example BC-331DLSw+ with Ethernet Redundancy in a Switched Environment BC-332BC-333 BC-334