Table Of Contents
LLC2 and SDLC Commands
Logical Link Control, type 2 (LLC2) protocol provides connection-oriented service and is widely used in LAN environments, particularly among IBM communication systems connected by Token Ring. The Cisco IOS software supports LLC2 connections over Ethernet, Token Ring, and Fiber Distributed Data Interface (FDDI).
The LLC2 commands provide operations that support the following features:
•
Local acknowledgment in remote source-route bridging (RSRB)
•
•
•
SDLC is used as the primary Systems Network Architecture (SNA) link-layer protocol for WAN links. SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then transmit if they have outgoing data. When configured as primary and secondary nodes, routers are established as SDLC stations.
The SDLC commands described in this chapter pertain to routers configured as SDLC stations. This is in contrast to a device configured for SDLC Transport where the router is not configured as an SDLC station, but acts as an intermediary, passing SDLC frames between two SDLC stations across a mixed-media, multiprotocol environment.
The SDLC commands support the following features:
•
•
Use the commands in this chapter to adjust the LLC2 and SDLC parameters. For LLC2 and SDLC parameter configuration information and examples, refer to the "Configuring LLC2 and SDLC Parameters" chapter in the Cisco IOS Bridging and IBM Networking Configuration Guide.
encapsulation sdlc
To configure an SDLC interface, use the encapsulation sdlc interface configuration command. Use the no form of this command to deactivate the command.
encapsulation sdlc
no encapsulation sdlc
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation sdlc command must be used to configure an SDLC interface if you plan to implement DLSw+ or Frame Relay access support.
SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then transmit if they have outgoing data. When configured as primary and secondary nodes, our routers are established as SDLC stations. Use the sdlc role interface configuration command to establish the role as primary or secondary.
In the IBM environment, a front-end processor (FEP) is the primary station and establishment controllers (ECs) are secondary stations. In a typical scenario, an EC may be connected to dumb terminals and to a Token Ring network at a local site. At the remote site, an IBM host connects to an IBM FEP, which can also have links to another Token Ring LAN. Typically, the two sites are connected through an SDLC leased line.
If a router is connected to an EC, it takes over the function of the FEP, and must therefore be configured as a primary SDLC station. If the router is connected to a FEP, it takes the place of the EC, and must therefore be configured as a secondary SDLC station.
Examples
The following example configures an SDLC interface:
interface serial 2/6no ip addressencapsulation sdlcRelated Commands
encapsulation sdlc-primary
To configure the router as the primary SDLC station if you plan to configure the SDLLC media translation feature, use the encapsulation sdlc-primary interface configuration command. Use the no form of this command to deactivate the command.
encapsulation sdlc-primary
no encapsulation sdlc-primary
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation sdlc-primary or encapsulation sdlc-secondary command must be used to configure an SDLC interface. To use the encapsulation sdlc-primary command, first select the interface on which you want to enable SDLC. Then establish the router as a primary station. Next, assign secondary station addresses to the primary station using the sdlc address command.
SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then transmit if they have outgoing data. When configured as primary and secondary nodes, our routers are established as SDLC stations.
In the IBM environment, a front-end processor (FEP) is the primary station and establishment controllers (ECs) are secondary stations. In a typical scenario, an EC may be connected to dumb terminals and to a Token Ring network at a local site. At the remote site, an IBM host connects to an IBM FEP, which can also have links to another Token Ring LAN. Typically, the two sites are connected through an SDLC leased line.
If a router is connected to an EC, it takes over the function of the FEP, and must therefore be configured as a primary SDLC station. If the router is connected to an FEP, it takes the place of the EC, and must therefore be configured as a secondary SDLC station.
Examples
The following example shows configures serial interface 0 on your router to allow two SDLC secondary stations to attach through a modem-sharing device (MSD) with addresses C1 and C2:
! enter a global command if you have not alreadyinterface serial 0encapsulation sdlc-primarysdlc address c1sdlc address c2Related Commands
encapsulation sdlc-secondary
To configure the router as a secondary SDLC station if you plan to configure the SDLLC media translation feature, use the encapsulation sdlc-secondary interface configuration command. Use the no form of this command to deactivate the command.
encapsulation sdlc-secondary
no encapsulation sdlc-secondary
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
An encapsulation sdlc-primary or encapsulation sdlc-secondary command must be used to configure an SDLC interface. To use the encapsulation sdlc-secondary command, first select the interface on which you want to enable SDLC. Then establish the router as a secondary station. Next, assign secondary station addresses to the primary station using the sdlc address command.
SDLC defines two types of network nodes: primary and secondary. Primary nodes poll secondary nodes in a predetermined order. Secondaries then transmit if they have outgoing data. When configured as primary and secondary nodes, our devices are established as SDLC stations.
In the IBM environment, a front-end processor (FEP) is the primary station and establishment controllers (ECs) are secondary stations. In a typical scenario, an EC may be connected to dumb terminals and to a Token Ring network at a local site. At the remote site, an IBM host connects to an IBM FEP, which can also have links to another Token Ring LAN. Typically, the two sites are connected through an SDLC leased line.
If a router is connected to an EC, it takes over the function of the FEP, and must therefore be configured as a primary SDLC station. If the router is connected to a FEP, it takes the place of the EC, and must therefore be configured as a secondary SDLC station.
Examples
The following example establishes the router as a secondary SDLC station:
interface serial 0encapsulation sdlc-secondaryRelated Commands
llc2 ack-delay-time
To set the amount of time the Cisco IOS software waits for an acknowledgment before sending the next set of information frames, use the llc2 ack-delay-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 ack-delay-time milliseconds
no llc2 ack-delay-time milliseconds
Syntax Description
milliseconds
Number of milliseconds the software allows incoming information frames to stay unacknowledged. The minimum is 1 ms and the maximum is 60000 ms. The default is 100 ms.
Defaults
100 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Upon receiving an information frame, each LLC2 station starts a timer. If the timer expires, an acknowledgment will be sent for the frame, even if the llc2 ack-max number of received frames has not been reached. Experiment with the value of the llc2 ack-delay-time command to determine the configuration that balances acknowledgment network overhead and quick response time (by receipt of timely acknowledgments).
Use this command in conjunction with the llc2 ack-max command to determine the maximum number of information frames the Cisco IOS software can receive before sending an acknowledgment.
Examples
In the following example, the software allows a 100-ms delay before I-frames must be acknowledged:
! enter a global command, if you have not alreadyinterface tokenring 0! sample ack-max commandllc2 ack-max 3! allow a 100 millisecond delay before I-frames must be acknowledgedllc2 ack-delay-time 100At time 0, two information frames are received. The llc2 ack-max amount of three has not been reached, so no acknowledgment for these frames is sent. If a third frame, which would force the software to send an acknowledgment, is not received in 100 ms, an acknowledgment will be sent anyway, because the llc2 ack-delay timer expires. At this point, because all frames are acknowledged, the counter for the ack-max purposes will be reset to zero.
Related Commands
Controls the maximum amount of information frames the Cisco IOS software can receive before it must send an acknowledgment.
Displays the LLC2 connections active in the router.
llc2 ack-max
To control the maximum amount of information frames the Cisco IOS software can receive before it must send an acknowledgment, use the llc2 ack-max internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 ack-max packet-count
no llc2 ack-max packet-count
Syntax Description
packet-count
Maximum number of packets the software will receive before sending an acknowledgment. The minimum is 1 packet and the maximum is 255 packets. The default is 3 packets.
Defaults
3 packets
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An LLC2-speaking station can send only a predetermined number of frames before it must wait for an acknowledgment from the receiver. If the receiver waits until receiving a large number of frames before acknowledging any of them, and then acknowledges them all at once, it reduces overhead on the network.
For example, an acknowledgment for five frames can specify that all five have been received, as opposed to sending a separate acknowledgment for each frame. To keep network overhead low, make this parameter as large as possible.
However, some LLC2-speaking stations expect this to be a low number. Some NetBIOS-speaking stations expect an acknowledgment to every frame. Therefore, for these stations, this number is best set to 1. Experiment with this parameter to determine the best configuration.
Examples
In the following example, the software is configured to receive up to seven frames before it must send an acknowledgment. Seven frames is the maximum allowed by SNA before a reply must be received:
! enter a global command, if you have not alreadyinterface tokenring 0! receive up to seven frames before sending an acknowledgmentllc2 ack-max 7! sample delay-time commandllc2 ack-delay-time 100Related Commands
llc2 idle-time
To control the frequency of polls during periods of idle time (no traffic), use the llc2 idle-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 idle-time milliseconds
no llc2 idle-time milliseconds
Syntax Description
milliseconds
Number of ms that can pass with no traffic before the LLC2 station sends a Receiver Ready frame. The minimum is 1 ms and the maximum is 60000 ms. The default is 10000 ms.
Defaults
10000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Periodically, when no information frames are being transmitted during an LLC2 session, LLC2 stations are sent a Receiver Ready frame to indicate they are available. Set the value for this command low enough to ensure a timely discovery of available stations, but not too low, or you will create a network overhead with too many Receiver Ready frames.
Examples
In the following example, the Cisco IOS software waits 20000 ms before sending a Receiver Ready ("are you there") frame:
! enter a global command, if you have not already interface tokenring 0! wait 20000 milliseconds before sending receiver-ready framesllc2 idle-time 20000Related Commands
llc2 local-window
To control the maximum number of information frames the Cisco IOS software sends before it waits for an acknowledgment, use the llc2 local-window internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 local-window packet-count
no llc2 local-window packet-count
Syntax Description
packet-count
Maximum number of packets that can be sent before the software must wait for an acknowledgment. The minimum is 1 packet and the maximum is 127 packets. The default is 7 packets.
Defaults
7 packets
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An LLC2-speaking station can send only a predetermined number of frames before it must wait for an acknowledgment from the receiver. Set this number to the maximum value that can be supported by the stations with which the router communicates. Setting this value too large can cause frames to be lost, because the receiving station may not be able to receive all of them.
Examples
In the following example, the software will send as many as 30 information frames through Token Ring interface 1 before it must receive an acknowledgment:
! enter a global command, if you have not alreadyinterface tokenring 1llc2 local-window 30Related Commands
Controls the maximum amount of information frames the Cisco IOS software can receive before it must send an acknowledgment.
Displays the LLC2 connections active in the router.
llc2 n2
To control the amount of times the Cisco IOS software retries sending unacknowledged frames or repolls remote busy stations, use the llc2 n2 internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 n2 retry-count
no llc2 n2
Syntax Description
retry-count
Number of times the software retries operations. The minimum is 1 retry and the maximum is 255 retries. The default is 8 retries.
Defaults
8 retries
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An LLC2 station must have some limit to the number of times it will resend a frame when the receiver of that frame has not acknowledged it. After the software is told that a remote station is busy, it will poll again based on the retry-count value. When this retry count is exceeded, the LLC2 station terminates its session with the other station. Set this parameter to a value that balances between frame checking and network performance.
Examples
In the following example, the software will resend a frame up to four times through Token Ring interface 1 before it must receive an acknowledgment. Because you generally do not need to change the retry limit, this example shows you how to reset the limit to the default of 8.
! enter a global command, if you have not alreadyinterface tokenring 1! retry value of 8llc2 n2 8Related Commands
llc2 nw
To increase the window size for consecutive good I-frames received, use the llc2 nw internal adapter configuration command. To revert to the default setting, use the no form of this command.
llc2 nw window-size-increase
no llc2 nw
Syntax Description
window-size-increase
Number of frames to increase the window size for consecutive good I-frames received (0 is disabled). The allowed range is from 1 to 7. The default is 0.
Defaults
0 (disabled)
Command Modes
Internal adapter configuration
Command History
11.0
This command was introduced.
12.1
The allowed range was changed to from 0 to 31.
Examples
In the following example, the window size for Token Ring interface 1 is increased by 1 frame when consecutive good I-frames are received:
! enter a global command, if you have not alreadyinterface tokenring 1! increase window size by 1llc2 nw 1Related Commands
Displays the LLC2 connections active in the router.
Invokes dynamic windowing logic for a link station when the router receives an RNR from the remote link station.
llc2 recv-window
To control the number of frames in the receive window, use the llc2 recv-window internal adapter configuration command. To revert to the default setting, use the no form of this command.
llc2 recv-window frame-count
no llc2 recv-window
Syntax Description
Defaults
7 frames
Command Modes
Internal adapter configuration
Command History
Examples
In the following example, the receive window for Token Ring interface 1 contains 11 frames:
! enter a global command, if you have not alreadyinterface tokenring 1! 11 frames in the receive windowllc2 recv-window 11Related Commands
llc2 rnr-activated
To invoke dynamic windowing logic for a link station when the router receives an RNR from the remote link station, use the llc2 rnr-activated internal adapter configuration command. To disable dynamic windowing logic, use the no form of this command.
llc2 rnr-activated
no llc2 rnr-activated
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
The llc2 nw command must be enabled before the llc2 rnr-activated command can be configured.
Examples
In the following example, the llc2n rnr-activated command is enabled on Adapter 0 4000.cafe.0000:
interface Channel4/2max-llc2-rcvbuffs 750lan TokenRing 12source-bridge 16 1 500adapter 0 4000.cafe.0000llc2 Nw 31llc2 rnr-activatedadapter 1 4000.cafe.0001Related Commands
Increases the window size for consecutive good I-frames received.
Configures the number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA.
llc2 send-window
To control the number of frames in the send window, use the llc2 send-window internal adapter configuration command. To revert to the default setting, use the no form of this command.
llc2 send-window frame-count
no llc2 send-window
Syntax Description
Defaults
7 frames
Command Modes
Internal adapter configuration
Command History
Examples
In the following example, the send window for Token Ring interface 1 contains 11 frames:
! enter a global command, if you have not alreadyinterface tokenring 1! 11 frames in the send windowllc2 send-window 11Related Commands
llc2 t1-time
To control the amount of time the Cisco IOS software will wait before resending unacknowledged information frames, use the llc2 t1-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 t1-time milliseconds
no llc2 t1-time milliseconds
Syntax Description
milliseconds
Number of ms the software waits before resending unacknowledged information frames. The minimum is 1 ms and the maximum is 60000 ms. The default is 1000 ms.
Defaults
1000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Use this command in conjunction with the llc2 n2 command to provide a balance of network monitoring and performance. Ensure that enough time is allowed to account for the round trip between the router and its LLC2-speaking stations under heavy network loading conditions.
Examples
In the following example, the software will wait 4000 ms before resending an unacknowledged frame through Token Ring interface 2:
! enter a global command, if you have not alreadyinterface tokenring 2! wait 4000 milliseconds before retransmitting a frame through tokenring 2llc2 t1-time 4000Related Commands
llc2 tbusy-time
To control the amount of time the Cisco IOS software waits until repolling a busy remote station, use the llc2 tbusy-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 tbusy-time milliseconds
no llc2 tbusy-time milliseconds
Syntax Description
milliseconds
Number of ms the software waits before repolling a busy remote station. The minimum is 1 ms and the maximum is 60000 ms. The default is 9600 ms.
Defaults
9600 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
An LLC2 station has the ability to notify other stations that it is temporarily busy, so the other stations will not attempt to send any new information frames. The frames sent to indicate this are called Receiver Not Ready (RNR) frames. Change the value of this parameter only to increase the value for LLC2-speaking stations that have unusually long busy periods before they clear their busy status. Increasing the value will prevent the stations from timing out.
Examples
In the following example, the software will wait up to 12000 ms before attempting to poll a remote station through Token Ring interface 0 to learn the station's status:
! enter a global command, if you have not alreadyinterface tokenring 0! wait 12000 milliseconds before polling a station through tokenring 0llc2 tbusy-time 12000Related Commands
llc2 tpf-time
To set the amount of time the Cisco IOS software waits for a final response to a poll frame before resending the poll frame, use the llc2 tpf-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 tpf-time milliseconds
no llc2 tpf-time milliseconds
Syntax Description
milliseconds
Number of ms the software waits for a final response to a poll frame before resending the poll frame. The minimum is 1 ms and the maximum is 60000 ms. The default is 1000 ms.
Defaults
1000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
When sending a command that must receive a response, a poll bit is sent in the frame. This is the receiving station's clue that the sender is expecting some response from it, be it an acknowledgment of information frames or an acknowledgment of more administrative tasks, such as starting and stopping the session. Once a sender gives out the poll bit, it cannot send any other frame with the poll bit set until the receiver replies with a frame containing a final bit set. If the receiver is faulty, it may never return the final bit to the sender. Therefore, the sender could be waiting for a reply that will never come. To avoid this problem, when a poll-bit-set frame is sent, a transmit-poll-frame (TPF) timer is started. If this timer expires, the software assumes that it can send another frame with a poll bit.
Usually, you will not want to change this value. If you do, the value should be larger than the T1 time, set with the llc2 t1-time command. The T1 time determines how long the software waits for receipt of an acknowledgment before sending the next set of frames.
Examples
While you generally will not want to change the transmit-poll-frame time, this example sets the TPF time to 3000 ms. Because the TPF time should be larger than the LLC2 T1 time, this example shows the TPF time as double the LLC2 T1 time.
! enter a global command, if you have not alreadyinterface tokenring 0! send a poll bit set through tokenring 0 after a 3000 ms delayllc2 tpf-time 3000! wait 1500 milliseconds for an acknowledgment before resending I-framesllc2 t1-time 1500Related Commands
llc2 trej-time
To control the amount of time the Cisco IOS software waits for a correct frame after sending a reject command to the remote LLC2 station, use the llc2 trej-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 trej-time milliseconds
no llc2 trej-time milliseconds
Syntax Description
Defaults
3200 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
When an LLC2 station sends an information frame, a sequence number is included in the frame. The LLC2 station that receives these frames will expect to receive them in order. If it does not, it can reject a frame and indicate which frame it is expecting to receive instead. Upon sending a reject, the LLC2 station starts a reject timer. If the frames are not received before this timer expires, the session is disconnected.
Examples
In the following example, the software will wait up to 1000 ms to receive a previously rejected frame before resending its reject message to the station that sent the frame:
! enter a global command, if you have not alreadyinterface tokenring 0! wait 1000 milliseconds before resending a reject message through tokenring 0llc2 trej-time 1000Related Commands
Controls the number of times the Cisco IOS software retries sending unacknowledged frames or repolls remote busy stations.
Displays the LLC2 connections active in the router.
llc2 xid-neg-val-time
To control the frequency of exchange of identification (XID) transmissions by the Cisco IOS software, use the llc2 xid-neg-val-tim internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 xid-neg-val-time milliseconds
no llc2 xid-neg-val-time milliseconds
Syntax Description
milliseconds
Number of ms after which the software sends XID frames to other LLC2-speaking stations. The minimum is 0 ms and the maximum is 60000 ms. The default is 0 ms.
Defaults
0 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Do not change the llc2 xid-neg-val-time parameter unless requested by your technical support representative.
LLC2-speaking stations can communicate XID frames to each other. These frames identify the stations at a higher level than the MAC address and also can contain information about the configuration of the station. These frames are typically sent only during setup and configuration periods when it is deemed that sending them is useful. The greatest frequency at which this information is transferred is controlled by this timer.
Examples
The following example shows how to reset the frequency of XID transmissions to the default of
0 ms:! enter a global command, if you have not alreadyinterface tokenring 0! set the frequency of XID transmissions to 0llc2 xid-neg-val-time 0Related Commands
Sets the amount of time the Cisco IOS software waits for a reply to XID frames before dropping the session.
Displays the LLC2 connections active in the router.
llc2 xid-retry-time
To set the amount of time the Cisco IOS software waits for a reply to exchange of identification (XID) frames before dropping the session, use the llc2 xid-retry-time internal adapter configuration command. Use the no form of this command to revert to the default setting.
llc2 xid-retry-time milliseconds
no llc2 xid-retry-time milliseconds
Syntax Description
milliseconds
Number of ms the software waits for a reply to XID frames before dropping a session. The minimum is 1 ms and the maximum is 60000 ms. The default is 60000 ms.
Defaults
60000 ms
Command Modes
Internal adapter configuration
Command History
Usage Guidelines
Set this value greater than the value of the T1 time, or the time the software waits for an acknowledgment before dropping the session. T1 time is set with the llc2 t1-time command.
Examples
The following example sets the software to wait up to 60000 ms for a reply to XID frames it sent to remote stations (which resets the value to its default):
! enter a global command, if you have not alreadyinterface tokenring 0! wait 60000 milliseconds for a reply to XID framesllc2 xid-retry-time 60000Related Commands
max-llc2-rcvbuffs
To configure the number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA, use the max-llc2-rcvbuffs internal adapter configuration command. Use the no form of this command to revert to the default setting.
max-llc2-rcvbuffs buffers
no max-llc2-rcvbuffs buffers
Syntax Description
buffers
The number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA. The allowed range is from 500 to 1250 in multiples of 50. The default is 500.
Defaults
500 buffers
Command Modes
Virtual interface configuration
Command History
Examples
The following example configures the max-llc2-rcvbuffs for 750 buffers on Channel interface 4/2:
interface Channel4/2max-llc2-rcvbuffs 750lan TokenRing 12source-bridge 16 1 500adapter 0 4000.cafe.0000llc2 Nw 31llc2 rnr-activatedadapter 1 4000.cafe.0001Related Commands
Increases the window size for consecutive good I-frames received.
Invokes dynamic windowing logic for a link station when the router receives an RNR from the remote link station.
sdlc address
To assign a set of secondary stations attached to the serial link, use the sdlc address interface configuration command. Use the no form of this command to remove an assigned secondary station.
sdlc address hexbyte [echo] [switched]
no sdlc address hexbyte [echo] [switched]
Syntax Description
Defaults
No secondary stations are assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
Before using this command, first select the interface on which you want to enable SDLC. Then establish the router as a primary station with the encapsulation sdlc-primary command. Next, assign secondary station addresses to the primary station using the sdlc address command. The addresses are given in hexadecimal (base 16) and are given one per line.
The optional keyword echo is valid only for TG interfaces. When you use the echo keyword, hexbyte is the nonecho SDLC address.
Examples
The following example shows how to configure serial interface 0 to have two SDLC secondary stations attached to it through a modem-sharing device with addresses C1 and C2:
interface serial 0encapsulation sdlc-primarysdlc address c1sdlc address c2Related Commands
sdlc address ff ack-mode
To configure the IBM reserved address ff as a valid local address, use the sdlc address ff ack-mode interface configuration command. Use the no form of this command to deactivate the command.
sdlc address ff ack-mode
no sdlc address ff ack-mode
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The sdlc address ff ack-mode command is used to support applications that require local termination of an SDLC connection with address FF. This command should be used only if you use the SDLC address FF as a regular (not a broadcast) address.
Examples
The following example enables local acknowledgment of SDLC address FF:
stun peer-name xxx.xxx.xxx.xxxstun protocol-group 1 sdlcinterface serial 1encapsulation stunstun group 1stun sdlc-role secondarysdlc address c1sdlc address ff ack-modestun route address c1 tcp yyy.yyy.yyy.yyy local-ackstun route address ff tcp yyy.yyy.yyy.yyy local-ackRelated Commands
stun route address tcp
Specifies TCP encapsulation and optionally establishes SDLC local acknowledgment (SDLC transport) for STUN.
sdlc dte-timeout
To adjust the amount of time a data terminal equipment (DTE) interface waits for the data circuit-terminating equipment (DCE) to assert a Clear To Send (CTS) signal before dropping a Request To Send (RTS), use the sdlc dte-timeout interface configuration command. Use the no form of this command to revert to the default setting.
sdlc dte-timeout unit
no sdlc dte-timeout unit
Syntax Description
unit
Timeout wait interval in microseconds. The valid range is 10 to 64000. Each unit is approximately 5 microseconds. The default is 10 units (approximately 50 microseconds).