Table Of Contents
IBM Network Media Translation Commands
source-bridge remote-peer interface
IBM Network Media Translation Commands
Use the commands in this chapter to configure and monitor Qualified Logical Link Control (QLLC) or Synchronous Logical Data Link Control (SDLLC) connections. SDLLC is a Cisco IOS software feature that provides translation between Synchronous Data Link Control (SDLC) and Logical Link Control, type 2 (LLC2). For QLLC conversion or SDLLC parameter configuration information and examples, refer to the "Configuring IBM Network Media Translation" chapter in the Cisco IOS Bridging and IBM Networking Configuration Guide.
qllc accept-all-calls
To enable the router to accept a call from any remote X.25 device, use the qllc accept-all-calls interface configuration command. To cancel the request, use the no form of this command.
qllc accept-all-calls
no qllc accept-all-calls
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows QLLC to accept all inbound X.25 calls, provided that the QLLC Call User Data (CUD) is in the call packet and the destination X.121 address in the call packet matches the serial interface's configured destination X.121 address or subaddress. When using this command, the source X.121 address does not need to be configured via an x25 map qllc command for the call to be accepted.
This command is applicable to QLLC support for DLSw+, APPN, and DSPU. It is not applicable to QLLC support for SRB and RSRB.
Examples
The following example enables QLLC connectivity for DLSw+ and allows QLLC to accept all inbound X.25 calls. Every X.25 connection request for X.121 address 0308 with QLLC CUD is directed to DLSw+. The first SVC to be established will be mapped to virtual MAC address 4000.0B0B.0001. If a call comes in with an X.121 address of 0308, the call will be forwarded to MAC address 4001.1161.1234.
interface serial 0encapsulation x25x25 address 0308qllc accept-all-callsqllc dlsw vmac 4000.0B0B.0001 500 partner 4001.1161.1234Related Commands
Specifies the X.121 address of the remote X.25 device with which communication is planned using QLLC conversion.
qllc largest-packet
To indicate the maximum size of the Systems Network Architecture (SNA) packet that can be sent or received on an X.25 interface configured for QLLC conversion, use the qllc largest-packet interface configuration command. To restore the default largest packet size, use the no form of this command.
qllc largest-packet virtual-mac-addr max-size
no qllc largest-packet virtual-mac-addr max-size
Syntax Description
virtual-mac-addr
Virtual Media Access Control (MAC) address associated with the remote X.25 device, as defined using the x25 map qllc or x25 pvc qllc interface configuration commands. This address is written as a dotted triple of four-digit hexadecimal numbers.
max-size
Maximum size, in bytes, of the SNA packet that can be sent or received on the X.25 interface configured for QLLC conversion. This value agrees with the value configured in the remote SNA device. The valid range is 0 to 1024.
Defaults
Maximum size is 265 bytes.
Command Modes
Interface configuration
Command History
Usage Guidelines
SNA packets that are larger than the largest value allowed on the X.25 connection and are received on the LLC2 interface are segmented before being sent on the X.25 interface. When a segmented packet is received on the X.25 interface, it is passed immediately to the LLC2 interface, and no effort is made to wait for the segment to be completed.
When the remote X.25 device has a limit on the maximum total length of recombined X.25 segments it will support, you can use the qllc largest-packet command to ensure the length is not exceeded. For example, a device whose maximum SNA packet size is limited to 265 bytes might not be able to handle a series of X.25 packets that it has to recombine to make a 4, 8, or 17 KM SNA packet, such as one often encounters in an LLC2 environment.
You use the qllc largest-packet command in conjunction with the x25 map qllc and qllc srb commands.
Note
Do not configure the maximum SNA packet size on an X.25 interface to be larger than the maximum SNA packet size allowed on the LLC2 interface.
Consult your IBM documentation to set the maximum packet size on the remote X.25 device.
Examples
In the following example, the maximum packet size that has been established for the virtual circuit is used as the maximum packet size that can be sent or received on the X.25 interface:
interface serial 0encapsulation x25x25 address 31102120100x25 map qllc 0100.0000.0001 31104150101qllc srb 0100.0000.0001 201 100!qllc partner 0100.0000.0001 4000.0101.0132qllc xid 0100.0000.0001 01720001qllc largest-packet 0100.0000.0001 521Related Commands
qllc npsi-poll
To enable a connection between a PU 2 on the LAN side and a front-end processor (FEP) running NPSI on the X.25 side, use the qllc npsi-poll interface configuration command. To disable this capability, use the no form of this command.
qllc npsi-poll virtual-mac-addr
no qllc npsi-poll virtual-mac-addr
Syntax Description
virtual-mac-addr
MAC address associated with the remote X.25 device, as defined using the x25 map qllc or x25 pvc qllc interface configuration commands. This address is written as a dotted triple of four-digit hexadecimal numbers.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The qllc npsi-poll command is necessary only when the upstream device is a FEP running NPSI and the downstream device is a PU 2.
This command is necessary because in a Token Ring or RSRB environment the LAN attached devices start up by sending a null exchange ID packet upstream. If the Cisco IOS software forwards this null XID to an X.25-attached FEP, the FEP responds as if it were connecting to an PU2.1 device, and breaks the connection when the PU 2 next sends an XID Format 0 Type 2. The qllc npsi-poll command intercepts any null XID packet that the software receives on the LAN interface, and returns a null XID response to the downstream device. It continues to allow XID Format 3 and XID Format 0 packets through the X.25 device.
Examples
The following example facilitates a connection between a FEP running NPSI and a downstream PU 2.0:
qllc npsi-poll 0100.0000.0001Related Commands
qllc partner
To enable a router configured for QLLC conversion to open a connection to the local Token Ring device on behalf of the remote X.25 device when an incoming call is received, use the qllc partner interface configuration command. To disable this capability, use the no form of this command.
qllc partner virtual-mac-addr mac-addr
no qllc partner virtual-mac-addr mac-addr
Syntax Description
virtual-mac-addr
MAC address associated with the remote X.25 device, as defined using the x25 map qllc or x25 pvc qllc interface configuration commands. This address is written as a dotted triple of four-digit hexadecimal numbers.
mac-addr
48-bit MAC address of the Token Ring host that will communicate with the remote X.25 device.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
When the Cisco IOS software receives an incoming call from the designated X.121 address, it opens an LLC2 connection with the device at the given MAC address. Both the MAC address of the Token Ring device and the virtual MAC address for the remote X.25 device with which it is to communicate are required in order for the software to initiate connections with the Token Ring device. This allows the Token Ring host to be permanently ready to accept a connection rather than requiring operator action at the host to initiate the connection with the X.25 device.
You must issue the qllc partner command for each remote X.25 device that will communicate with the local Token Ring host through this interface.
You use the qllc partner command in conjunction with the x25 map qllc and qllc srb commands.
Examples
In the following example, the qllc partner command is used to associate the virtual MAC address 0100.0000.0001, as defined in the previous x25 map qllc entry, with the MAC address of the Token Ring host that will communicate with the remote X.25 device:
interface serial 0encapsulation x25x25 address 31102120100x25 map qllc 0100.0000.0001 31104150101qllc srb 0100.0000.0001 201 100!qllc partner 0100.0000.0001 4000.0101.0132qllc xid 0100.0000.0001 01720001Related Commands
qllc sap
To associate a service access point (SAP) value other than the default SAP value with a serial interface configured for X.25 communication and QLLC conversion, use the qllc sap interface configuration command. To return this SAP value to its default state, use the no form of this command.
qllc sap virtual-mac-addr ssap dsap
no qllc sap virtual-mac-addr ssap dsap
Syntax Description
virtual-mac-addr
MAC address associated with the remote X.25 device, as defined using the x25 map qllc or x25 pvc qllc interface configuration commands. This address is written as a dotted triple of four-digit hexadecimal numbers.
ssap
Source SAP value. It can be a decimal number in the range 2 to 254. The default is 4.
dsap
Destination SAP value. It can be a decimal number in the range 2 to 254. The default is 4.
Defaults
The default source SAP value is 4.
The default destination SAP value is 4.
Command Modes
Interface configuration
Command History
Usage Guidelines
A SAP can be viewed as a port through which a higher-layer application can communicate with its counterpart (peer) operating on another system. While the standard SAP value for IBM devices is 4, other values are allowed.
You use the qllc sap command in conjunction with the x25 map qllc and qllc srb interface configuration commands.
Examples
In the following example, source SAP and destination SAP values of 2 are specified for the remote X.25 device at the X.121 address 31370054065:
interface serial 0x25 map qllc 31370054065 4000.0122.0001qllc srb 9 100qllc sap 4000.0122.0001 02 02Related Commands
qllc srb
To enable QLLC conversion on a serial interface configured for X.25 communication, use the qllc srb interface configuration command. To disable QLLC conversion on the interface, use the no form of this command.
qllc srb virtual-mac-addr srn trn
no qllc srb srn trn
Syntax Description
virtual-mac-addr
MAC address associated with the remote X.25 device, as defined using the x25 map qllc or x25 pvc qllc interface configuration commands. It can be 1 to 15 digits long.
srn
Source ring number. This value defines a virtual ring for all of the remote X.25 devices attached to the QLLC interface.
trn
Target ring number. It must be a virtual ring group that has been defined with the source-bridge sdllc-local-ack global configuration command.
Defaults
QLLC conversion is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Any number of QLLC conversion connections using the same X.25 serial interface can share a common source ring. However, this source ring must be a unique hexadecimal ring number within the source-bridged network.
If the router has only one Token Ring interface and is bridging from the remote X.25 devices to this interface, then trn is the number of the ring on that Token Ring interface. If the router has several Token Ring interfaces and interconnects them by means of the source-bridge sdllc-local-ack command, then trn is the number of that virtual ring group, as assigned using the source-bridge sdllc-local-ack
Use the qllc srb command to associate the ring number and bridge number that have been assigned to the interface with a virtual ring group of which the interface will be a part. The serial interface appears to be a ring, or source ring number, on a source-route bridge network, and ties in to the virtual ring group, or target ring number. The target ring number provides access to other real rings that have been designated using the source-bridge global configuration command. Note that you can configure QLLC conversion on a router containing no Token Ring interface cards, such as a router connecting a serial-attached device to an X.25 public data network (PDN).
The qllc srb command automatically turns on the LLC2 process with default values. To change any of the LLC2 parameters (described in the "LLC2 and SDLC Commands" chapter), apply their values to the serial interface that has been configured for QLLC conversion. This is done on the serial interface, even though LLC2 does not technically run on the serial interface, but on the virtual ring associated with the serial interface.
You use the qllc srb command in conjunction with the x25 map qllc command.
Examples
In the following example, the qllc srb command is used to define a virtual ring number of 201 for the remote X.25 device, and an actual or virtual ring number of 100 for the Token Ring interface:
interface serial 0encapsulation x25x25 address 31102120100x25 map qllc 0100.0000.0001 31104150101qllc srb 0100.0000.0001 201 100Related Commands
qllc xid
To associate an exchange ID (XID) value with the remote X.25 device that communicates through the Cisco IOS software using QLLC conversion, use the qllc xid interface configuration command. To disable XID processing for this address, use the no form of this command.
qllc xid virtual-mac-addr xid
no qllc xid virtual-mac-addr xid
Syntax Description
virtual-mac-addr
MAC address associated with the remote X.25 device, as defined using the x25 map qllc or x25 pvc qllc interface configuration command. This address is written as a dotted triple of four-digit hexadecimal numbers.
xid
Combined XID IDBLK and XID IDNUM you are associating with the X.25 device at this X.121 address. This hexadecimal value must be four bytes (eight digits) in length.
Defaults
XID processing is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Most QLLC installations do not need the qllc xid configuration command. It is only needed if the remote X.25 device is not configured to send its own XID. This is only possible for a device that is attached via a permanent virtual circuit (PVC). Even so, most devices that are connected via X.25 will send their own XIDs. Use the qllc xid command when the Token Ring host requires login validation for security purposes and the remote X.25 device does not send an XID. The XID value is used to reply to XID requests received on the Token Ring (LLC2) side of the connection. XID requests and responses are usually exchanged before sessions are started. The XID response to the XID request from the Token Ring host will contain the information you configure using the qllc xid command. The host will check the XID response it receives with the IDBLK and IDNUM parameters (configured in VTAM). If they match, the Token Ring host will initiate a session with the router. If they do not match, the host will not initiate a session with the router.
You use the qllc xid command in conjunction with the x25 map qllc and the qllc srb commands.
Examples
In the following example, the X.25 device at X.121 address 31104150101 must use an XID IDBLK of 017 and XID IDNUM of 20001 to access the Token Ring host whose MAC address is associated with the remote X.25 device, as applied using the sdllc partner command:
interface serial 0encapsulation x25x25 address 31102120100x25 map qllc 0100.0000.0001 31104150101qllc srb 0100.0000.0001 201 100!qllc partner 0100.0000.0001 4000.0101.0132qllc xid 0100.0000.0001 01720001Related Commands
sdllc partner
To enable device-initiated connections for SDLLC, use the sdllc partner interface configuration command. This command must be specified for the serial interface that links to the serial line device. To cancel the original instruction, use the no form of this command.
sdllc partner mac-address sdlc-address
no sdllc partner mac-address sdlc-address
Syntax Description
mac-address
MAC address of the Token Ring host.
sdlc-address
SDLC address of the serial device that will communicate with the Token Ring host.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Both the MAC address of the Token Ring host and the SDLC serial line address are required to initiate connections with the Token Ring host.
The Token Ring host and the serial device communicate with each other through the Cisco IOS software. Although the device is said to initiate connections, the software actually initiates connections with the Token Ring host on behalf of the serial device. As part of Cisco's SDLLC implementation, the serial device "thinks" that it is communicating with a host also on a serial line. It is actually the software that does all the frame and protocol conversions between serial and Token Ring devices.
There are two conditions under which the Cisco IOS software will attempt to initiate a connection to a host on behalf of a serial device:
•
•
The Cisco IOS software will continue trying once a minute to initiate a connection whenever one of these two conditions is met, until the host responds to its requests. When you no longer want the software to initiate connections with a host, use the no sdllc partner command.
Note
Examples
In the following example, a serial device at SDLC address C2 wants to initiate a connection with a Token Ring host at MAC address 4000.0122.0001. The router initiates the connection on behalf of a serial device:
! sample global commandsource-bridge ring-group 100!interface serial 0! router initiates connections with Token Ring host at MAC address! 4000.0122.0001 on behalf of serial device c2sdllc partner 4000.0122.0001 c2Related Commands
Specifies an XID value appropriate for the designated SDLC station associated with this serial interface.
sdllc ring-largest-frame
To indicate the largest I-frame size that can be sent to or received from the LLC2 primary station, use the sdllc ring-largest-frame interface configuration command. To return to the default, use the no form of this command.
sdllc ring-largest-frame value
no sdllc ring-largest-frame value
Syntax Description
value
Frame size in bytes. Possible values include 516, 1500, 2052, 4472, 8144, 11407, and 17800. The default is 516 bytes.
Defaults
516 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
Possible values for the value argument match those that are possible for the lf size of the various source-bridge remote-peer commands. You must ensure that your remote peer connection can support this largest frame size. Possible values for the value argument include 516, 1500, 2052, 4472, 8144, 11407, and 17800.
Faster screen updates to 3278-style terminals often can be obtained by allowing the Token Ring FEP to send as large a frame as possible and by allowing the Cisco IOS software to segment the frame into multiple SDLC I-frames.
Examples
In the following example, the software can send or receive a frame as large as 11407 bytes from the LLC2 primary station. Any frames larger will be fragmented by the software.
! sample global commandsource-bridge ring-group 100!interface serial 3! largest frame sent or received on serial 3 is 11407 bytessdllc ring-largest-frame 11407Related Commands
sdllc sap
To associate a SAP value other than the default SAP value with a serial interface configured for SDLLC, use the sdllc sap interface configuration command. To return this SAP value to its default state, use the no form of this command.
sdllc sap sdlc-address ssap dsap
no sdllc sap sdlc-address ssap dsap
Syntax Description
Defaults
The default source and destination SAP values for IBM SNA devices is 4.
Command Modes
Interface configuration
Command History
Usage Guidelines
You use the sdllc sap command in conjunction with the sdllc traddr interface configuration commands. A SAP can be viewed as a port through which a higher-layer application can communicate with its counterpart (peer) operating on another system. While the standard SAP value for IBM SNA devices is 4, and NetBIOS devices is xF0, other values are allowed.
Examples
In the following example, source SAP and destination SAP values of 2 are specified for the remote SDLC device at the SDLC address C1 02 02:
interface serial 0sdllc sap c1 02 02Related Commands
Enables SDLLC media translation on a serial interface.The address specified is a MAC address to be assigned to the serial station.
sdllc sdlc-largest-frame
To indicate the largest information frame (I-frame) size that can be sent or received by the designated SDLC station, use the sdllc sdlc-largest-frame interface configuration command. To return to the default value, use the no form of this command.
sdllc sdlc-largest-frame address value
no sdllc sdlc-largest-frame address value
Syntax Description
address
Address of the SDLC station that will communicate with the Token Ring host.
value
Largest frame size that can be sent or received by this SDLC station. The default is 265 bytes.
Defaults
265 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
Most SDLC devices are limited to frames of 265 bytes. I-frames received from the Token Ring station that are larger than this size will be properly fragmented.
Examples
In the following example, the Cisco IOS software can send or receive a frame as large as 265 bytes (the default) from the SDLC station at address C6. Any frames larger will be fragmented by the software.
! sample global commandsource-bridge ring-group 100!interface serial 4! largest frame sent or received on serial 4 is 265 bytessdllc sdlc-largest-frame c6 265sdllc traddr
To enable SDLLC media translation on a serial interface, use the sdllc traddr interface configuration command. The address specified is a MAC address to be assigned to the serial station. To disable SDLLC media translation on the interface, use the no form of this command.
sdllc traddr xxxx.xxxx.xx00 lr bn tr
no sdllc traddr xxxx.xxxx.xx00 lr bn tr
Syntax Description
xxxx.xxxx.xx00
MAC address to be assigned to the serial interface.
lr
SDLLC virtual ring number.
bn
SDLLC bridge number.
tr
SDLLC target ring number.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Every control unit hooked off the serial line requires a virtual Token Ring address (VTRA). This usually is assigned by the system administrator as a locally administered MAC address (unique across the network).
When you enable SDLLC Media Translation by specifying the sdllc traddr command on a serial interface, you must specify a VTRA for each serial station attached to the serial line. The last two hexadecimal digits (that is, the last byte) of the VTRA must be 00. The Cisco IOS software uses this byte to represent the SDLC address of a station on the serial link.
Note
The variables lr, bn, and tr represent the SDLLC virtual ring number, bridge number, and target ring number, respectively, that you assign to the interface. In design, the serial interface appears to be a ring, lr, on a source-route bridged network, and ties in through the bridge, bn, to the virtual ring-group, tr. This provides access to other, real rings through remote source-route bridging source-bridge remote-peer commands. Note that SDLLC can be configured on a router containing no Token Ring interface cards.
The sdllc traddr command automatically turns on the LLC2 process with default values. To change any of the LLC2 parameters, specify their values on the serial interface that is being enabled for SDLLC. This is done on the serial interface, even though LLC2 does not technically run on the serial interface, but on the SDLLC virtual ring associated with the serial interface. LLC2 commands can be configured after specifying the sdllc traddr command.
Examples
In the following example, SDLLC media translation is enabled off the serial 0 interface to a serial station at MAC address 0110.2222.3300. The SDLLC virtual ring number is 8, the bridge number is 1, and the target ring number is 100.
! global command to apply commands to the ring groupsource-bridge ring-group 100! remote peer at IP address 131.108.1.1 belongs to ring group 100 and uses! tcp as the transportsource-bridge remote-peer 100 tcp 131.108.1.1source-bridge remote-peer 100 tcp 131.108.2.2!interface serial 0encapsulation sdlc-primary! establish address of SDLC station off serial-0 as c1sdlc address c1! enable SDLLC media translation to serial station 0110.2222.3300! on virtual ring 8, bridge 1, to target ring 100sdllc traddr 0110.2222.3300 8 1 100Related Commands
sdllc xid
To specify an XID value appropriate for the designated SDLC station associated with this serial interface, use the sdllc xid interface configuration command. To disable XID processing for this address, use the no form of this command.
sdllc xid address xxxxxxxx
no sdllc xid address xxxxxxxx
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
XID requests and responses are usually exchanged before sessions are started. Be sure that the XID value configured on the router matches the IDBLK and IDNUM parameters configured on the host. The XID response to an XID request from the Token Ring host will contain the information you configured in the sdllc xid command. The host will check the XID response it receives with the IDBLK and IDNUM parameters (that are configured in virtual telecommunications access method (VTAM)). If they match, the Token Ring host will initiate a session with the router. If they do not match, the host will not initiate a session.
Examples
The following example specifies an XID value of 01720002 at address C2:
! sample global commandsource-bridge ring-group 100!interface serial 0! sdllc exchange identification value of 01720002 at address c2sdllc xid c2 01720002Related Commands
Enables device-initiated connections for SDLLC.Must be specified for the serial interface that links to the serial line device.
show qllc
To display the current state of any QLLC connections, use the show qllc privileged EXEC command.
show qllc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show qllc command.
Router# show qllcQLLC Connections:Serial2: 1000.5a35.3a4f->1000.5a59.04f9. SAPs 4 4. Rings Src 200, Tgt 100.State ConnectRemote DTE 1002. QLLC Protocol State NORMAL lci 1 (PVC)In the display, the first two lines of the show qllc command show that there is a QLLC session between a Token Ring device and an X.25 remote device. The X.25 device has a virtual MAC address of 100.5a35.3a4f with a SAP of 04. It is using a PVC with logical channel number 1. The Token Ring device has a MAC address of 1000.5a59.04f9 with a SAP of 04. The state of the QLLC session is CONNECTED.
Table 38 describes the fields shown in the display.
show sdllc local-ack
To display the current state of any current local acknowledgment connections, as well as any configured passthrough rings, use the show sdllc local-ack privileged EXEC command.
show sdllc local-ack
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show sdllc local-ack command:
Router# show sdllc local-acklocal 1000.5a59.04f9, lsap 04, remote 4000.2222.4444, dsap 04llc2 = 1798136, local act state = connectedPassthrough Rings: 4 7In the display, the first two lines of the show sdllc local-ack command show that there is a local acknowledgment session between two Token Ring devices. The device on the local ring has a MAC address of 1000.5a59.04f9 with a SAP of 04. The remote device has a MAC address of 4000.2222.4444 with a SAP of 04. The state of the local acknowledgment session is connected.
The passthrough rings display is independent of the rest of the show sdllc local-ack command. The passthrough rings display indicates that there are two rings, 4 and 7, configured for passthrough. This means that stations on these rings will not have their sessions locally acknowledged but will instead have their acknowledgments end-to-end.
Table 39 describes significant fields shown in the display.
source-bridge qllc-local-ack
To enable or disable QLLC local acknowledgment for all QLLC conversion connections, use the source-bridge qllc-local-ack global configuration command. To disable this capability, use the no form of this command.
source-bridge qllc-local-ack
no source-bridge qllc-local-ack
Syntax Description
This command has no arguments or keywords.
Defaults
QLLC local acknowledgment is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
In a remote source-route bridged topology, QLLC local acknowledgment is used to configure the QLLC conversion router (connecting the remote X.25 devices) to exchange local acknowledgment information with the Token Ring router (on the Token Ring side of the cloud). This Token Ring device has been configured for LLC2 local acknowledgment using the source-bridge remote peer tcp local-ack command.
You only have to issue the source-bridge qllc-local-ack command on the QLLC conversion router. When this command is issued, all of the QLLC conversion sessions are locally acknowledged at the Token Ring interface of the Token Ring router with which it is communicating using QLLC conversion.
Examples
The following configuration indicates that the local router (131.108.2.2) QLLC conversion sessions will be locally acknowledged at the remote router:
source-bridge ring-group 100source-bridge remote-peer 100 tcp 131.108.1.1 local-acksource-bridge remote-peer 100 tcp 131.108.2.2source-bridge qllc-local-ackRelated Commands
source-bridge remote-peer interface
When specifying a point-to-point direct encapsulation connection, use the source-bridge remote-peer interface global configuration command. To disable previous interface assignments, use the no form of this command.
source-bridge remote-peer ring-group interface interface-name [mac-address] [lf size]
no source-bridge remote-peer ring-group interface interface-name
Syntax Description
Defaults
No point-to-point direct encapsulation connection is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to identify the interface over which to send source-route bridged traffic to another router/bridge in the ring group. A serial interface does not require that you include a MAC-level address; all other types of interfaces do require MAC addresses.
It is possible to mix all types of transport methods within the same ring group.
Note
Examples
The following example shows how to send source-route bridged traffic over serial interface 0 and Ethernet interface 0:
! send source-route bridged traffic over serial 0source-bridge remote-peer 5 interface serial 0! specify MAC address for source-route bridged traffic on Ethernet 0source-bridge remote-peer 5 interface ethernet 0 0000.0c00.1234Related Commands
source-bridge sdllc-local-ack
To activate local acknowledgment for SDLLC sessions on a particular interface, use the source-bridge sdllc-local-ack global configuration command. To deactivate local acknowledgment for SDLLC sessions, use the no form of this command.
source-bridge sdllc-local-ack
no source-bridge sdllc-local-ack
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
