-
Router Products Configuration Guide
-
About This Manual
-
Router Product Overview
-
Understanding the User Interface
-
Loading System Images, Microcode Images, and Configuration File
-
Configuring Terminal Lines and Modem Support
-
Managing the System
-
Configuring ATM
-
Configuring DDR
-
Configuring SMDS
-
Configuring X.25
-
Configuring Apollo Domain
-
Configuring AppleTalk
-
Configuring Banyan VINES
-
Configuring DECnet
-
Configuring ISO-CLNS
-
Configuring XNS
-
Configuring Transparent Bridging
-
Configuring Source-Route Bridging
-
Configuring Remote Source-Route Bridging
-
Configuring DLSw+
-
Configuring STUN and BSTUN
-
Configuring LLC2 and SDLC Parameters
-
Configuring DSPU and SNA Service Point
-
Configuring APPN
-
Table Of Contents
Configuring DSPU and SNA Service Point Support
Cisco's Implementation of DSPU and SNA Service Point
Explicitly Define a Downstream PU
Configure DSPU to Use a Data Link Control
Configure DSPU to Use Token Ring or Ethernet
Configure DSPU to Use RSRB with Local Acknowledgment
Configure DSPU to Use Frame Relay
Define the Number of Outstanding, Unacknowledged Activation RUs
Configure SNA Service Point Support
Configure Service Point Support to Use a Data Link Control
Configure Service Point to Use Token Ring or Ethernet
Configure Service Point to Use RSRB
Configure Service Point to Use RSRB with Local Acknowledgment
Configure Service Point Support for Frame Relay
Configure Service Point Support for SDLC
Configure Service Point Support for X.25
Specify Names for All Attached LANs
Specify the Physical Location of the Router
Upstream Host via RSRB DSPU Configuration Example
Downstream PU via SDLC DSPU Configuration Example
Upstream host via SDLC DSPU Configuration Example
Downstream PU via QLLC/X.25 DSPU Configuration Example
Upstream Host via Frame Relay DSPU Configuration Example
SNA Service Point Support Configuration Example
Configuring DSPU and SNA Service Point Support
This chapter describes our support for Systems Network Architecture (SNA) downstream physical unit (DSPU) devices and SNA Service Point. For a complete description of the commands mentioned in this chapter, refer to the "DSPU Configuration Commands" chapter of the Router Products Command Reference publication.
Cisco's Implementation of DSPU and SNA Service Point
DSPU is a software feature that enables the router to function as a physical unit (PU) concentrator for SNA PU type 2 nodes. PU concentration at the router simplifies the task of PU definition at the upstream host while providing additional flexibility and mobility for downstream PU devices.
The DSPU feature allows you to define downstream PU type 2 devices in the router. DSPU reduces the complexity of host configuration by letting you replace multiple PU definitions that represent each downstream device with one PU definition that represents the router.
Because you define the downstream PUs at the router rather than the host, you isolate the host from changes in the downstream network topology. Therefore you can insert and remove downstream PUs from the network without making any changes on the host.
The concentration of downstream PUs at the router also reduces network traffic on the wide-area network (WAN) by limiting the number of sessions that must be established and maintained with the host. The termination of downstream sessions at the router ensures that idle session traffic does not appear on the WAN.
Our SNA Service Point support in the Cisco Router assumes NetView or an equivalent product at the SNA host. The user interacts with the network management feature in both the Router and at the SNA host. At the router you can configure the host connection, and show the status of this connection. At the SNA host you can use the Netview operator's console to view Alerts, and to send and receive Cisco syntax commands to the router.
shows a router functioning as a DSPU concentrator.
Figure 30-1 Router Acting as a DSPU Concentrator
Typically, the router establishes one or more upstream connections with one or more hosts and many downstream connections with PU type 2 devices. From an SNA perspective, the router appears as a PU type 2 device to the upstream host and assumes the role of a system services control point (SSCP) appearing as a PU type 5 device to its downstream PUs.
The SSCP sessions established between the router and its upstream host are completely independent of the SSCP sessions established between the router and its downstream PUs. SNA traffic is routed at a logical unit (LU) level using a routing algorithm that maps downstream LUs onto upstream LUs.
illustrates the SNA perspective of DSPU.
Figure 30-2 SNA Perspective of DSPU
DSPU Configuration Task List
To configure DSPU, perform the tasks in the following sections. The last two tasks are optional.
•
Configure DSPU to Use a Data Link Control
•
•
See the end of this chapter for "DSPU Configuration Examples."
Define DSPU Upstream Hosts
The upstream host provides LUs that the router will assign for use by its downstream PUs. Because one upstream host can only provide a maximum of 255 LUs, the DSPU feature supports multiple hosts. Multiple upstream host support allows the DSPU router to provide more than 255 LUs for use by its downstream PUs.
To define a DSPU host over TokenRing, Ethernet, or RSRB connections, perform the following task in global configuration mode:
To define a DSPU host over an SDLC connection, perform the following task in global configuration mode:
To define a DSPU host over an X.25/QLLC connection, perform the following task in global configuration mode:
To define a DSPU host over a Frame Relay connection, perform the following task in global configuration mode:
Define Downstream PUs
To define the downstream PUs, perform either of the tasks in the following sections, depending on your circumstances:
•
Explicitly Define a Downstream PU
Explicitly define a downstream PU if you require the router to perform verification checking on incoming downstream connections or to initiate an outgoing downstream connection.
To explicitly define a downstream PU over TokenRing, Ethernet, or RSRB connections, perform the following task in global configuration mode:
To define a DSPU host over an SDLC connection, perform the following task in global configuration mode:
To define a DSPU host over an X.25/QLLC connection, perform the following task in global configuration mode:
To define a DSPU host over a Frame Relay connection, perform the following task in global configuration mode:
Note that a PU definition must have either an xid-rcv parameter or an address (rmac, sdlc, x25 or dlci) parameter.
If the router will perform verification checking on incoming downstream connections, there are several combinations of parameters that you can configure for verification matching. Note that the address parameter, when specified, is considered to be the primary key on the PU definition. Therefore, if both an address and xid-rcv are configured, the matching algorithm will match on the address and ignore the xid-rcv parameter.
•
User may define a downstream PU using only the xid parameter so that any connecting PU that specifies the value of the configured xid will match that PU definition.
•
User may define a downstream PU using the xid and interface parameters so that any PU connecting into the configured interface that specifies the value of the configured xid will match the PU definition.
•
User may define a downstream PU using only the addressing parameters (rmac/rsap/lsap, sdlc, dlci/rsap/lsap, or x25/qllc) so that any connecting PU with addressing that matches the configured addressing will match that PU definition. If no PU definition is found to match the incoming RSAP, then a match is accepted on a PU that has the correct RMAC/LSAP or DLCI/LSAP.
•
User may define a downstream PU using the interface and addressing parameters (rmac/rsap/lsap, sdlc, dlci/rsap/lsap, or x25/qllc) so that any PU connecting into the configured interface with addressing that matches the configured addressing will match the PU definition. If no PU definition is found to match the incoming RSAP, then a match is accepted on a PU that has the correct RMAC/LSAP or DLCI/LSAP and interface.
The router will reject any incoming downstream connections that do not match the parameters of a defined downstream PU unless the default PU option is also enabled.
Enable the Default PU Option
Configure the DSPU default PU option if you do not require the router to verify incoming downstream connections. The default PU option allows the router to accept incoming downstream connections without an explicit definition for the downstream PU.
To enable the default PU option, perform the following task in global configuration mode:
Enable the default PU option.
dspu default-pu [window window-size] [maxiframe max-iframe]
Define DSPU LUs
Specify the LU routing algorithm used to map the upstream LUs to the downstream LUs and to define all LUs for each upstream and downstream PU.
The DSPU feature assigns upstream LUs to downstream LUs based on the selected LU routing algorithm and performs the mapping necessary for SNA data transfer.
The DSPU feature supports two alternative mapping algorithms that are described in the following sections:
An upstream host PU or downstream PU can support up to 255 LU sessions. The DSPU feature allows each LU to be individually configured for either dedicated LU routing or pooled LU routing.
Dedicated LU Routing
You can configure an upstream LU so that it is reserved, or dedicated, for use by a specific downstream LU.
To define a dedicated LU or a range of dedicated LUs for an upstream host and downstream PU, perform the following task in global configuration mode:
Define a dedicated LU or a range of dedicated LUs for a downstream PU.
dspu lu lu-start [lu-end] host host-name host-lu-start [pu pu-name]
See the "Dedicated LU Routing Example" section later in this chapter for an example of dedicated LU routing.
Pooled LU Routing
You can configure an upstream host LU so that it is a member of a pool of LUs. When a downstream connection is established and the downstream LU is configured as a pooled LU, the router selects an upstream LU from the pool for assignment to the downstream LU.
Pooled LU routing allows a limited number of upstream host LUs to be shared (at different times) among many downstream PUs.
To define a host LU or a range of host LUs in an LU pool, perform the following task in global configuration mode:
Define a host LU or a range of host LUs in an LU pool.
dspu pool pool-name host host-name lu lu-start [lu-end] [inactivity-timeout inactivity-minutes]
You can configure a downstream LU as a pooled LU. When a downstream connection is established and the downstream LU is configured as a pooled LU, the router selects an upstream LU from the specified pool for assignment to the downstream LU.
To define a pooled LU or a range of pooled LUs for a downstream PU, perform the following task in global configuration mode:
Define a pooled LU or a range of pooled LUs for a downstream PU.
dspu lu lu-start [lu-end] pool pool-name [pu pu-name]
See the "Pooled LU Routing Example" section later in this chapter for an example of pooled LU routing.
Configure DSPU to Use a Data Link Control
The final step in configuring DSPU is to define the data link controls that will be used for upstream host and downstream PU connections.
The DSPU feature supports the data link controls described in the following sections:
•
•
•
Configure DSPU to Use Token Ring or Ethernet
You can configure DSPU to use the Token Ring and/or Ethernet data link controls by enabling a Service Access Point (SAP) address on the interface. Each interface can support up to 255 local SAPs enabled for either upstream or downstream connections; a local SAP cannot be enabled for both upstream and downstream connections on the same interface.
To enable a local SAP on the Token Ring or Ethernet interfaces for use by upstream hosts, perform the following task in interface configuration mode:
To enable a local SAP on the Token Ring or Ethernet interfaces for use by downstream PUs, perform the following task in interface configuration mode:
To initiate a connection with a remote upstream host or downstream PU, perform the following task in interface configuration mode:
Initiate connection with upstream host or downstream PU via Token Ring or Ethernet.
dspu start host-name|pu-name
Configure DSPU to Use RSRB
To configure DSPU to use RSRB you must create a DSPU/RSRB data link control.
Similar to our implementation of SDLLC, the DSPU/RSRB data link control uses the concept of a virtual Token Ring device residing on a virtual Token Ring to represent the router to upstream hosts and downstream PUs across an RSRB network.
Because the upstream host and/or downstream PU expects its peer to also be on a Token Ring, you must assign a virtual Token Ring address (the DSPU virtual MAC address) to the DSPU/RSRB data link control. Like real Token Ring addresses, the DSPU virtual MAC address must be unique across the network.
In addition to assigning the DSPU virtual MAC address, you must also assign a DSPU virtual ring number to the DSPU/RSRB data link control. The DSPU virtual ring number must be unique across the network.
Note
The combination of the DSPU virtual MAC address and the DSPU virtual ring number identifies the DSPU/RSRB data link control interface to the rest of an RSRB network.
When an end station (either an upstream host or a downstream PU) attempts to connect with the DSPU router, the following events occur:
1
2
3
To define the DSPU/RSRB data link control interface, perform the following tasks in global configuration mode:
Define an RSRB ring group.
source-bridge ring-group ring-group1
Define a remote peer with the local acknowledgment feature.
source-bridge remote-peer ring-group tcp ip-address2
Define the DSPU/RSRB interface.
dspu rsrb local-virtual-ring bridge-number target-virtual-ring virtual-macaddr
1 This command is documented in the "Source-Route Bridging Commands" chapter of the Router Products Commands Reference publication.
2 This command is documented in the "Remote Source-Route Bridging Commands" chapter of the Router Products Command Reference publication.
After you define the DSPU RSRB data link control, you configure DSPU to use the RSRB data link control by enabling a local SAP for either upstream or downstream connections.
To enable a local SAP on RSRB for use by upstream hosts, perform the following task in global configuration mode:
To enable a local SAP on RSRB for use by downstream PUs, perform the following task in global configuration mode:
To initiate a connection with a remote upstream host or downstream PU over RSRB, perform the following task in global configuration mode:
Initiate connection with upstream host or downstream PU via RSRB.
dspu rsrb start host-name
Configure DSPU to Use RSRB with Local Acknowledgment
Configuring DSPU to use RSRB with local acknowledgment is identical to configuring RSRB with local acknowledgment. If you add the local-ack keyword to the source-bridge remote-peer configuration command, DSPU will use local-acknowledgment for any end stations that connect to DSPU from that peer.
To configure DSPU to use RSRB with local acknowledgment, perform the following tasks in global configuration mode:
Define an RSRB ring group.
source-bridge ring-group ring-group1
Define a remote peer with the local acknowledgment feature.
source-bridge remote-peer ring-group tcp ip-address local-ack2
Define the DSPU/RSRB interface.
dspu rsrb local-virtual-ring bridge-number target-virtual-ring virtual-macaddr
1 This command is documented in the "Source-Route Bridging Commands" chapter of the Router Products Commands Reference publication.
2 This command is documented in the "Remote Source-Route Bridging Commands" chapter of the Router Products Command Reference publication.
Configure DSPU to Use SDLC
Before DSPU may be configured to use the SDLC data link control, the serial interface must be defined for SDLC encapsulation and assigned an SDLC role. The SDLC role must be primary if DSPU will be initiating connections to the SDLC partner; the SDLC role must be secondary if the SDLC partner will be initiating connections with DSPU.
To define the serial interface to use SDLC, perform the following tasks in interface configuration mode:
Enable SDLC encapsulation on the serial interface.
encapsulation sdlc1
Specify the SDLC role of the router.
sdlc role {primary | secondary}1
1 This command is documented in the "LLC2 and SDLC Commands" chapter of the Router Products Command Reference publication.
The SDLC address(es) used on the SDLC link must also be defined. If the SDLC role is primary, the SDLC address identifies the SDLC partner to which a connection will be initiated. If the SDLC role is secondary, the SDLC address identifies the address to which a connection will be accepted.
To configure the SDLC address, perform the following task in interface configuration mode:
Define the SDLC address.
sdlc address sdlc-address1
1 This command is documented in the "LLC2 and SDLC Commands" chapter of the Router Products Command Reference publication.
Finally, the SDLC address must be enabled for use by DSPU. Each interface can support up to 255 SDLC addresses enabled for either upstream or downstream connections; an SDLC address cannot be enabled for both upstream and downstream connections on the same interface.
To enable an SDLC address for use by upstream host connections, perform the following task in interface configuration mode:
To enable an SDLC address for use by downstream PU connections, perform the following task in interface configuration mode:
Note
Configure DSPU to Use QLLC
Before DSPU may be configured to use the QLLC data link control, the serial interface must be defined for X.25 encapsulation and assigned an X.121 address.
To define the serial interface to use X.25, perform the following tasks in interface configuration mode:
Enable X.25 encapsulation on serial interface.
encapsulation x25 [dce]1
Define an X.121 address.
x25 address local-x121-addr1
1 This command is documented in the "X.25 and LAPB Commands" chapter of the Router Products Command Reference publication.
X.25 routing must also be configured so that incoming calls to the local X.121 address can be appropriately routed to the serial interface and mapped into the QLLC data link control.
To define X.25 routing, perform the following tasks in global configuration mode:
Enable X.25 routing.
x25 routing1
Enable routing of X.25 packets to serial interface
x25 route ^local-x121-addr.* alias serial slot/port1
1 This command is documented in the "X.25 and LAPB Commands" chapter of the Router Products Command Reference publication.
To define the which calls get mapped into QLLC, perform the following task in interface configuration mode:
Define remote X.121 address for mapping into QLLC.
x25 map qllc remote-x121-addr1
1 This command is documented in the "IBM Network Media Translation Commands" chapter of the Router Products Command Reference publication.
Finally, the local X.121 subaddress must be enabled for use by DSPU. An X.121 subaddress can be enabled for either upstream or downstream connections; an X.121 subaddress cannot be enabled for both upstream and downstream connections on the same interface.
To enable an X.121 subaddress for use by upstream host connections via QLLC, perform the following task in interface configuration mode:
To enable an X.121 subaddress for use by downstream PU connections via QLLC, perform the following task in interface configuration mode:
To initiate a connection with a remote upstream host or downstream PU, perform the following task in interface configuration mode:
Initiate connection with upstream host or downstream PU via QLLC/X.25.
dspu start host-name |pu-name
Configure DSPU to Use Frame Relay
Before DSPU may be configured to use the LLC2/FrameRelay data link control, the serial interface must be defined for Frame Relay encapsulation.
To define the serial interface for Frame Relay encapsulation, perform the following task in interface configuration mode:
Enable Frame Relay encapsulation on a serial interface.
encapsulation frame-relay IETF1
1 This command is documented in the "Frame Relay Commands" chapter of the Router Products Command Reference publication.
The DLCI used on the Frame Relay link must be mapped into LLC2
To configure the mapping of a DLCI into LLC2, perform the following task in interface configuration mode:
Configure DLCI mapping into LLC2.
frame-relay map llc2 dlci-number1
1 This command is documented in the "SNA Frame Relay Access Support Commands" chapter of the Router Products Command Reference publication.
Finally, the local SAP address must be enabled for use by DSPU. A SAP address can be enabled for either upstream or downstream connections; a SAP address cannot be enabled for both upstream and downstream connections on the same interface.
To enable a local SAP on the LLC2/FrameRelay interface for use by upstream hosts, perform the following task in interface configuration mode:
To enable a local SAP for the LLC2/FrameRelay interface for use by downstream PUs, perform the following task in interface configuration mode:
To initiate a connection with a remote upstream host or downstream PU, perform the following task in interface configuration mode:
Initiate connection with upstream host or downstream PU via LLC2/FrameRelay.
dspu start host-name | pu-name
Define the Number of Outstanding, Unacknowledged Activation RUs
The DSPU feature allows you to define the number of activation request units (RUs) such as ACTLUs or DDDLU NMVTs that can be sent by the router before waiting for responses from the remote PU.
The DSPU activation window provides pacing to avoid depleting the router buffer pool during PU activation. Increasing the window size allows more LUs to become active in a shorter amount of time (assuming the required buffers for activation RUs are available). Decreasing the window size limits the amount of buffers the DSPU may use during PU activation. Typically, you do not need to change the default window size.
To define the number of unacknowledged activation RUs that can be outstanding, perform the following task in global configuration mode:
Configure SNA Service Point Support
Our implementation of SNA Service Point support includes support for three commands, Alerts, RUNCMD, and Vital Product Data support.
Alert support is provided as the router sends unsolicited Alerts to Netview (or an equivalent network management application) at the host. This function occurs at the various router interfaces and protocol layers within the router.
RUNCMD support enables you to send router commands to the router from the Netview console using the Netview RUNCMD facility, and the router sends the relevant replies back to the RUNCMD screen.
Vital Product Data support allows you to request Vital Product Data from the Netview console. The router replies to Netview with the relevant information.
To configure SNA Service Point support, perform the tasks in the following sections:
•
•
•
Define a Link to an SNA Host
To define a link to an SNA host over TokenRing, Ethernet, or RSRB connections, perform the following task in global configuration mode:
To define a link to an SNA host over an SDLC connection, perform the following task in global configuration mode:
To define a link to an SNA host over an X.25/QLLC connection, perform the following task in global configuration mode:
To define a link to an SNA host over a Frame Relay connection, perform the following task in global configuration mode:
Configure Service Point Support to Use a Data Link Control
To configure Service Point to use a data link control, perform the tasks in one of the following sections:
•
•
•
•
•
•
Note
Configure Service Point to Use Token Ring or Ethernet
To enable a local SAP on the Token Ring or Ethernet interfaces for use by SNA Service point, perform the following task in interface configuration mode:
To initiate a connection with a remote host, perform the following task in interface configuration mode:
Configure Service Point to Use RSRB
To define the Service Point/RSRB data link control interface, perform the following tasks in global configuration mode:
Define an RSRB ring group.
source-bridge ring-group ring-group1
Define the Service Point/RSRB interface.
sna rsrb local-virtual-ring bridge-number target-virtual-ring virtual-macaddr
1 This command is documented in the "Source-Route Bridging Commands" chapter of the Router Products Command Reference publication.
To enable a local SAP on RSRB for use by hosts, perform the following task in global configuration mode:
To initiate a connection with a remote host over RSRB, perform the following task in global configuration mode:
Configure Service Point to Use RSRB with Local Acknowledgment
To configure Service Point to use RSRB with local acknowledgment, perform the following tasks in global configuration mode:
Define an RSRB ring group.
source-bridge ring-group ring-group1
Define a remote peer with the local acknowledgment feature.
source-bridge remote-peername ring-group ring-group tcp ip-address local-ack
Define the Service Point/RSRB interface.
sna rsrb local-virtual-ring bridge-number target-virtual-ring virtual-macaddr
1 This command is documented in the "Source-Route Bridging Commands" chapter of the Router Products Command Reference publication
Configure Service Point Support for Frame Relay
To configure Service Point support for Frame Relay, perform the following tasks in interface configuration mode:
Define DLCI mapping into LLC2.
frame-relay map llc2 dlci-number1
Enable a local SAP for hosts.
sna enable-host lsap lsap-addr
1 This command is documented in the "SNA Frame Relay Access Support Commands" chapter of the Router Products Command Reference publication.
Configure Service Point Support for SDLC
To configure Service Point support for SDLC, perform the following tasks in interface configuration mode:
Specify the SDLC role of the router.
sdlc role {primary | secondary}1
Define the SDLC address.
sdlc address sdlc-addr1
Enable the SDLC address for the host.
sna enable-host sdlc sdlc-addr
1 This command is documented in the "LLC2 and SDLC Commands" chapter of the Router Products Command Reference publication.
Configure Service Point Support for X.25
To configure Service Point support for Frame Relay, perform the following tasks in interface configuration mode:
Define an X.121 address.
x25 address x121-addr1
Define remote X.121 address for mapping to QLLC.
x25 map qllc remote-x121-addr2
Enable QLLC subaddress for host.
sna enable-host qllc x121-sub-addr
Enable routing of X.25 packets to serial interface.
x25 route ^x121-addr.* alias serial interface1
1 This command is documented in the "X.25 and LAPB Commands" chapter of the Router Products Command Reference publication.
2 This command is documented in the "IBM Network Media Translation Commands" chapter of the Router Products Command Reference publication.
Specify Names for All Attached LANs
You can specify names for all Token Ring or Ethernet LANs attached to the router. These names are used to identify the LAN when the router sends an Alert to the host. To specify names for all attached LANs, perform the following tasks in interface configuration mode:
Specify the Physical Location of the Router
You can specify the physical location of the router if you intend requesting Vital Product Data from the router. To specify the physical location of the router, perform the following tasks in interface configuration mode:
Define the physical location of the router.
location physical-location (up to 50 characters, including blanks)
Monitor DSPU Feature Status
You can monitor the status of the DSPU feature. To display information about the state of the DSPU feature, perform the following tasks in EXEC mode:
DSPU Configuration Examples
The following sections provide DSPU configuration examples:
•
•
•
•
•
•
Dedicated LU Routing Example
illustrates the use of dedicated LU routing. Each upstream host LU is dedicated for use by a specific downstream LU.
Figure 30-3 Dedicated LU Routing
The following is a configuration file for the dedicated LU routing shown in :
dspu host ciscohost xid-snd 06500001 rmac 4000.3745.0001dspu pu ciscopu-a xid-rcv 05D00001 rmac 1000.5AED.0001dspu lu 1 2 host ciscohost 2dspu lu 3 3 host ciscohost 20dspu pu ciscopu-b xid-rcv 05D00002 rmac 1000.5AED.0002dspu lu 1 2 host ciscohost 4dspu lu 3 3 host ciscohost 21Pooled LU Routing Example
illustrates the use of pooled LU routing. Each upstream LU is configured in the LU pool and each downstream LU is configured as a pooled LU.
Figure 30-4 Pooled LU Routing
The following is the configuration example for the pooled LU routing shown in :
dspu host ciscohost xid-snd 06500001 rmac 4000.3745.0001dspu pool lupool host ciscohost lu 2 21dspu pu ciscopu-a xid-rcv 05D00001 rmac 1000.5AED.0001dspu lu 1 3 pool lupooldspu pu ciscopu-b xid-rcv 05D00002 rmac 1000.5AED.0002dspu lu 1 3 pool lupooldspu pu ciscopu-c xid-rcv 05D00003 rmac 1000.5AED.0003dspu lu 1 3 pool lupoolUpstream Host via RSRB DSPU Configuration Example
The following configuration example represents one possible definition for the network topology shown earlier in .
This example demonstrates the configuration of an upstream host via RSRB (with local-acknowledgment) and downstream PUs via Token Ring.
source-bridge ring-group 99source-bridge remote-peer 99 tcp 150.10.13.1source-bridge remote-peer 99 tcp 150.10.13.2 local-ackdspu rsrb 88 1 99 4000.ffff.0001dspu rsrb enable-host lsap 4dspu host ciscohost xid-snd 06500001 rmac 4000.3172.0001 rsap 4 lsap 4dspu pool ciscopool host ciscohost lu 2 8dspu rsrb start ciscohostdspu pu ciscopu1 xid-rcv 05d00001dspu lu 2 3 pool ciscopooldspu pu ciscopu2 xid-rcv 05d00002dspu lu 2 4 pool ciscopooldspu pu ciscopu3 xid-rcv 05d00003dspu lu 2 2 pool ciscopooldspu pu ciscopu4 xid-rcv 05d00004dspu lu 2 2 pool ciscopooldspu lu 3 3 host ciscohost 9interface TokenRing 0description TokenRing connection for downstream PUsring-speed 16dspu enable-pu lsap 8Downstream PU via SDLC DSPU Configuration Example
This example demonstrates the configuration of downstream PUs via SDLC and an upstream host via Token Ring.
dspu host ciscohost xid-snd 06500001 rmac 4000.3172.0001 rsap 4 lsap 12dspu pool ciscopool host ciscohost lu 2 11dspu pu pu-sdlc0 sdlc C1 interface Serial0dspu lu 2 6 pool ciscopooldspu pu pu-sdlc1 sdlc C1 interface Serial1dspu lu 2 6 pool ciscopoolinterface Serial0description SDLC connection for pu-sdlc0encapsulation sdlcsdlc role primarysdlc address C1dspu enable-pu sdlc C1clockrate 56000interface Serial1description SDLC connection for pu-sdlc1encapsulation sdlcsdlc role primarysdlc address C1dspu enable-pu sdlc C1clockrate 56000interface TokenRing 0description TokenRing connection for ciscohostring-speed 16dspu enable-host lsap 12dspu start ciscohostUpstream host via SDLC DSPU Configuration Example
This example demonstrates the configuration of an upstream host via SDLC and downstream PUs via Token Ring and Ethernet.
dspu host ciscohost xid-snd 06500001 sdlc C1 interface Serial0dspu pool ciscopool host ciscohost lu 2 11dspu pu pu-token rmac 4000.4444.0001 rsap 4 lsap 8dspu lu 2 6 pool ciscopooldspu pu pu-ether rmac 0200.2222.0001 rsap 4 lsap 8dspu lu 2 6 pool ciscopoolinterface Serial0description SDLC connection for ciscohostencapsulation sdlcsdlc role secondarysdlc address C1dspu enable-host sdlc C1clockrate 56000interface TokenRing 0description TokenRing connection for pu-tokenring-speed 16dspu enable-pu lsap 8interface Ethernet0description Ethernet connection for pu-etherdspu enable-pu lsap 8Downstream PU via QLLC/X.25 DSPU Configuration Example
This example demonstrates the configuration of a downstream PU via QLLC/X.25 and upstream host via Ethernet.
x25 routingdspu host ciscohost xid-snd 06500001 rmac 0200.2222.0001 rsap 4 lsap 12dspu pool ciscopool host ciscohost lu 2 11dspu pu pu-qllc x25 320108 qllc 08dspu lu 2 11 pool ciscopoolinterface Serial0description QLLC connection for pu-qllcencapsulation x25x25 address 3202x25 map qllc 320108dspu enable-pu qllc 8interface Ethernet0description Ethernet connection for pu-etherdspu enable-host lsap 12dspu start ciscohostx25 route ^3202.* alias Serial0Upstream Host via Frame Relay DSPU Configuration Example
This example demonstrates the configuration of an upstream host via Frame Relay and downstream PUs via Token Ring and Ethernet.
dspu host ciscohost xid-snd 06500001 dlci 200 rsap 4 lsap 12dspu pool ciscopool host ciscohost lu 2 11dspu pu pu-token rmac 4000.4444.0001 rsap 4 lsap 8dspu lu 2 6 pool ciscopooldspu pu pu-ether rmac 0200.2222.0001 rsap 4 lsap 8dspu lu 2 6 pool ciscopoolinterface Serial0description Frame Relay connection for ciscohostencapsulation frame-relay ietfframe-relay map llc2 200dspu enable-host lsap 12dspu start ciscohostinterface TokenRing 0description TokenRing connection for pu-tokenring-speed 16dspu enable-pu lsap 8interface Ethernet0description Ethernet connection for pu-etherdspu enable-pu lsap 8SNA Service Point Support Configuration Example
The following is an example of an RSRB configuration that implements SNA Service Point:
source-bridge ring-group 99source-bridge remote-peer 99 tcp 150.10.13.2 local-acksna rsrb 88 1 99 4000.ffff.0001sna host CNM02 xid-snd 05dbc000 rmac 4001.3745.1088 rsap 4 lsap 4 focalpointsna rsrb enable-host lsap 4sna rsrb start CNM02
