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

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:

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.