|
|
LLC2 (IEEE 802.2) type 2 provides connection-oriented service and is widely used in LAN environments, particularly among IBM communication systems connected by Token Ring. Our router supports LLC2 connections over Ethernet, Token Ring, and FDDI.
The LLC2 commands provide operations that support the following features:
SDLC is used as the primary Systems Network Architecture (SNA) link-layer protocol for wide-area network (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 router 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 router's LLC2 and SDLC parameters. For LLC2 and SDLC parameter configuration information and examples, refer to the "Configuring LLC2 and SDLC Parameters" chapter in the Router Products Configuration Guide.
Use the encapsulation sdlc interface configuration command to configure the router as the primary SDLC station if you plan to configure either DLSw+ or Frame Relay access support.
This command has no arguments or keywords.
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, the router 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, the router takes the place of the EC, and must therefore be configured as a secondary SDLC station.
The following example shows how to configure the router as a secondary PU2 station:
Use the encapsulation sdlc-primary interface configuration command to configure the router as the primary SDLC station if you plan to configure the SDLLC media translation feature.
This command has no arguments or keywords.
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, the router 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, the router takes the place of the EC, and must therefore be configured as a secondary SDLC station.
The following example shows how to configure interface serial 0 on your router to have two SDLC secondary stations attached to it through a modem-sharing device (MSD) with addresses C1 and C2:
encapsulation sdlc-secondary
sdlc address
show interfaces
Use the encapsulation sdlc-secondary interface configuration command to configure the router as a secondary SDLC station if you plan to configure the SDLLC media translation feature.
This command has no arguments or keywords.
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 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, the router 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, the router takes the place of the EC, and must therefore be configured as a secondary SDLC station.
The following example shows the use of this command:
encapsulation sdlc-primary
sdlc address
show interfaces
Use the llc2 ack-delay-time interface configuration command to set the amount of time the router waits for an acknowledgment before sending the next set of information frames.
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 router can receive before sending an acknowledgment.
In the following example, the router allows a 100-ms delay before I-frames must be acknowledged:
At 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 router to send an acknowledgment, is not received in 100 ms, an acknowledgment will be sent anyway, because the llc2 ack-delay timer expire. At this point, because all frames are acknowledged, the counter for the ack-max purposes will be reset to zero.
Use the llc2 ack-max interface configuration command to control the maximum amount of information frames the router can receive before it must send an acknowledgment.
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.
In the following example, the router 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:
llc2 ack-delay-time
llc2 local-window
show llc2
Use the llc2 idle-time interface configuration command to control the frequency of polls during periods of idle time (no traffic).
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.
In the following example, the router waits 20000 ms before sending a Receiver Ready ("are you there") frame:
llc2 tbusy-time
llc2 tpf-time
show llc2
Use the llc2 local-window interface configuration command to control the maximum number of information frames the router sends before it waits for an acknowledgment.
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.
In the following example, the router will send as many as 30 information frames through Token Ring interface 1 before it must receive an acknowledgment:
Use the llc2 n2 interface configuration command to control the amount of times the router retries sending unacknowledged frames or repolls remote busy stations.
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 router 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.
In the following example, the router 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:
llc2 t1-time
llc2 tbusy-time
llc2 trej-time
show llc2
Use the llc2 t1-time interface configuration command to control the amount of time the router will wait before resending unacknowledged information frames.
Use 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.
In the following example, the router will wait 4000 ms before resending an unacknowledged frame through Token Ring interface 2:
llc2 n2
llc2 tpf-time
llc2 xid-retry-time
show llc2
Use the llc2 tbusy-time interface configuration command to control the amount of time the router waits until repolling a busy remote station.
An LLC2 station has the ability to tell others 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.
In the following example, the router will wait up to 12000 ms before attempting to poll a remote station through Token Ring interface 0 to learn the station's status:
llc2 n2
llc2 idle-time
show llc2
Use the llc2 tpf-time interface configuration command to set the amount of time the router waits for a final response to a poll frame before resending the poll frame.
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 router 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 router waits for receipt of an acknowledgment before sending the next set of frames.
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:
llc2 idle-time
llc2 n2
llc2 t1-time
show llc2
Use the llc2 trej-time interface configuration command to control the amount of time a router waits for a correct frame after sending a reject (REJ) command to the remote LLC2 station.
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.
In the following example, the router will wait up to 1000 ms to receive a previously rejected frame before resending its reject message to the station that sent the frame:
Use the llc2 xid-neg-val-tim interface configuration command to control the frequency of exchange of identification (XID) transmissions by the router.
Do not change the llc2 xid-neg-val-time parameter unless requested by your technical support representative.
LLC2-speaking stations can communicate exchange of identification (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.
The following example shows how to reset the frequency of XID transmissions to the default of
0 ms:
Use the llc2 xid-retry-time interface configuration command to set the amount of time the router waits for a reply to exchange of identification (XID) frames before dropping the session.
Set this value greater than the value of the T1 time, or the time the router waits for an acknowledgment before dropping the session. T1 time is set with the llc2 t1-time command.
The following example sets the router to wait up to 60000 ms for a reply to XID frames it sent to remote stations (which resets the value to its default):
llc2 xid-neg-val-time
llc2 t1-time
show llc2
Use the sdlc address interface configuration command to assign a set of secondary stations attached to the serial link. Use the no form of this command to remove an assigned secondary station.
No secondary stations are assigned.
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.
The following example shows how to configure serial interface 0 to have two SDLC secondary stations attached to it through a modem-sharing device (MSD) with addresses C1 and C2:
encapsulation sdlc-primary
encapsulation sdlc-secondary
show interfaces
Use the sdlc address ff ack-mode interface configuration command to configure the IBM reserved address ff as a valid local address.
This command has no arguments or keywords.
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.
The following example enables local acknowledgment of SDLC address ff:
A dagger () indicates that the command is documented in another chapter.
Use the sdlc cts-delay interface configuration command to adjust the delay between the detection of RTS (request to send) and the assertion of CTS (clear to send).
3 units (approximately 15 microseconds)
This timer is applicable only on an interface that is set to sdlc half-duplex mode and is acting as a data communication equipment (DCE).
The following example sets the delay between the detection of RTS and the assertion of CTS to 10 (approximately 50 microseconds):
Use the sdlc dlsw interface configuration command to attach sdlc addresses to DLSw+. Use the no form of this command to cancel the configuration.
The following command attaches SDLC address d2 to DLSw+:
encapsulation sdlc
sdlc address
sdlc role
Use the sdlc dte-timeout interface configuration command to adjust the amount of time a data terminal equipment (DTE) interface waits for the DCE to assert a clear to send (CTS) before dropping a request to send (RTS).
10 units (approximately 50 microseconds).
Use this command on an interface that is in half-duplex mode and that has been configured for DTE.
The following example sets the amount of time that the DTE waits for the DCE to assert a CTS to 100 (approximately 500 microseconds):
sdlc cts-delay
sdlc hdx
sdlc rts-timeout
Use the sdlc frmr-disable interface configuration command to indicate that secondary stations on a particular serial link do not support Frame Rejects (FRMRs) or error indications. Use the no form of this command to specify that the secondary station does support FRMRs.
This command has no arguments or keywords.
Support of FRMRs or error indications
FRMRs are error indications that can be sent to an SDLC station indicating that a protocol error has occurred. Not all SDLC stations support FRMRs. If this command is enabled, when the router receives an error, it drops the line by sending a disconnect request to the remote station.
In the following example, the router is set to drop the serial line when it receives a protocol error:
Use the sdlc hdx interface configuration command to configure an interface for half-duplex mode.Use the no form of this command to reset the interface for full-duplex mode.
This command has no arguments or keywords.
In the following example, an SDLC interface has been configured for half-duplex mode:
sdlc cts-delay
sdlc rts-timeout
Use the sdlc holdq interface configuration command to control the maximum number of packets that can be held in a buffer before being transmitted to a remote SDLC station.
This command is particularly useful with the SDLLC feature that allows an LLC2-speaking SNA station on a Token Ring to communicate with an SDLC-speaking SNA station on a serial link. Frame sizes and window sizes on Token Rings are often much larger than those acceptable for serial links. The fact that serial links are often much slower than Token Rings often makes this problem worse. Therefore, temporary backlogs can exist in periods of high data transfer from the Token Ring station to the serial station. A buffer creates a holding place for backlogged frames awaiting transmission on the serial link. This command is specified for each SDLC address, and therefore, for each SDLC secondary station on the serial link.
The following example shows how to change the output hold queue length to 30 frames on an SDLC station of address c1 off serial 0:
Use the sdlc k interface configuration command to set the window size in order to control the maximum number of information frames a router transmits before it must stop transmitting and wait for an acknowledgment from the receiving router.
When the router is communicating with SDLC, it must have a parameter that controls the maximum number of information frames it will send before it must stop sending and wait for an acknowledgment. The k parameter controls this window of acceptable frames. Use this command in conjunction with the sdlc n1 command to create a balance between frame checking and network performance.
In the following example, the router can send up to five frames before it must receive an acknowledgment:
Use the sdlc line-speed interface configuration command to enable adaptive SDLC T1.
This feature is used to calculate the adjusted SDLC T1 value. The adjusted T1 is used to compensate for the delay between the time the system software passes a packet to the microcode, and the time the packet is actually sent out on the line. For DCE, this should be equal to the clockrate on the interface. For DTE, it should be equal to the clockrate on the DCE device to which the DTE is connected.
In the following example, the sdlc line-speed rate is set to rate:
Use the sdlc n1 interface configuration command to control the maximum size of an incoming frame.
Use with the sdlc k command to reduce network overhead while continuing to check frame transmission.
In the following example, the router rejects frames larger than 10000 bits:
Use the sdlc n2 interface configuration command to determine the number of times that a router resends a frame before terminating the SDLC session.
Use with the sdlc t1 command to reduce network overhead while continuing to check transmission.
In the following example, the router is set to drop an SDLC station after five unsuccessful attempts to receive an acknowledgment for a frame:
Use the sdlc partner command to specify the destination address with which an LLC session is established for the SDLC station. Use the no form of this command to cancel the configuration.
The following command establishes the correspondence between an SDLC and QLLC connection:
encapsulation sdlc
sdlc dlsw
sdlc vmac
Use the sdlc poll-limit-value interface configuration command to control how many times a single secondary station can be polled for input before the next station must be polled. Use the no form of this command to retrieve the default value.
As is typical for the primary station of an SDLC connection, if a secondary station sends its full possible window of input to the primary router, the router immediately will repoll the same secondary for more data in an attempt to capture the complete transaction at one time. The sdlc poll-limit-value command indicates how many times this can happen before the next station in the poll loop must be polled.
Increasing the value allows for smoother transaction processing but can delay polling of other stations or giving output to other stations.
The following example specifies that the router can be polled two times before the next station in the poll list must be polled:
sdlc poll-pause-timer
show interfaces
Use the sdlc poll-pause-timer interface configuration command to control how long the router pauses between sending each poll frame to secondary stations on a single serial interface. Use the no form of this command to retrieve the default value.
As is typical for the primary station of an SDLC connection, the router generates polls periodically to each of the secondary stations to solicit their input. After polling each station on a single serial interface, the router will pause before beginning to poll the next station.
Because the secondaries cannot transmit data until they are polled, increasing this timer can increase response time to the users. However, making this parameter too small can flood the serial link with unneeded polls and require the secondary stations to spend wasted CPU time processing them.
In the following example, the router pauses 2000 ms before sending a series of poll frames through serial interface 4:
sdlc poll-limit-value
show interfaces
Use the sdlc poll-wait-timeout interface configuration command when the router has been configured for Local Acknowledgment and some form of SDLC communication (SDLLC or STUN, for example), to specify the interval the router will wait for polls from a primary node before timing out that connection.
This command can be used on an interface that has been configured as a secondary node, but is not to be used on an interface that has been configured as a primary node.
In a locally acknowledged multidrop environment, the polls the primary node sends to the router can be delayed because the primary node is busy polling other secondary nodes. In such situations, this command can be used to extend the timeout, thus reducing the likelihood the router times out the connection to the primary node.
The following example specifies that the local router will wait an interval of 63000 ms for a poll from a primary station before timing out:
sdlc poll-limit-value
sdlc poll-pause-timer
To establish correspondence between an SDLC and QLLC connection, use the sdlc qllc-prtnr interface configuration command.
The following command establishes the correspondence between an SDLC and QLLC connection:
Use the sdlc role interface configuration command to establish the router to be either a primary or secondary SDLC station. Use the no form of this command to cancel the designation.
If the role is none, the router can be either primary or secondary, depending on the end stations. The SDLC end station must be configured as negotiable or primary NT2.1. When the end stations are configured as Physical Unit (PU) type 2, you can set the role of the interface to primary or secondary. When the end station is configured as secondary NT2.1, you must set the role of the interface to prim-xid-poll.
The following example shows how to configure the router as a secondary PU2 station:
Use the sdlc rts-timeout interface configuration command to adjust the amount of time the interface waits for the DCE to assert clear to send (CTS) before dropping a request to send (RTS).
10 units (approximately 50 microseconds)
Use this command on an interface that is in half-duplex mode and that has been configured for DCE.
The following example sets the amount of time that the DTE waits for the DCE to assert a CTS to 100 (approximately 500 microseconds):
Use the sdlc sdlc-largest-frame interface configuration command to indicate the largest information frame (I-frame) size that can be sent or received by the designated SDLC station. Use the no form of this command to return to the default value.
The default largest I-frame is 265 bytes.
In the following example, the router 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 router.
To enable an interface configured as a primary SDLC station to operate in two-way simultaneous mode, use the sdlc simultaneous interface configuration command.
Two-way simultaneous mode is disabled.
By default, the SDLC driver supports alternative mode. This means that in a multidrop environment, the primary station cannot send data to another secondary station until it receives a response (F bit) from the secondary station with which it is currently communicating.
In contrast, two-way simultaneous mode enables the interface configured as a primary SDLC station to send data to a second secondary station, even when it is receiving data from another secondary station. This capability improves utilization of a full-duplex serial line.
To enable all secondary stations to send and receive data at the same time, issue the following command:
The following example enables all secondary stations to send or receive data at the same time:
encapsulation sdlc-primary
show interfaces
Use the sdlc slow-poll interface configuration command to enable the slow-poll capability of the router as a primary SDLC station. Use the no form of this command to disable slow-poll capability.
You can use this command to improve the performance of a multidropped SDLC configuration when one or more of the secondary stations are inactive.
When slow-poll is enabled, if the router acting as a primary station detects that a secondary SDLC station is not responding, it polls that secondary SDLC station less frequently. The router spends less time waiting for the inactive secondary station to respond, thereby minimizing the performance degradation on the active secondary SDLC stations on the multidropped line.
In the following example, the slow-poll capability is enabled for the router:
sdlc poll-limit-value
sdlc poll-pause-timer
show interfaces
Use the sdlc t1 interface configuration command to control the amount of time the router waits for an acknowledgment to a frame or sequence of frames.
When an SDLC station sends a frame, it waits for an acknowledgment from the receiver that the frame has been received. The sending station cannot wait indefinitely for a response. When the frame is sent, a timer is started. To be consistent with the original specification of SDLC, this timer is called the T1 timer and is controlled by this parameter. If this timer reaches its limit before the acknowledgment is received, the router will try again and resend the frame.
In the following example, the router waits up to 4000 ms for a reply to a frame or sequence of frames:
Use the sdlc vmac interface configuration command to configure a MAC address for the serial interface. Use the no form of this command to disable the configuration.
This command must be configured if you plan to configure DLSw+. The last byte of the address must be 00.
The following example specifies a MAC address for the serial interface :
Use the sdlc xid interface configuration command to specify an eXchanged ID (XID) value appropriate for the designated SDLC station associated with this serial interface. Use the no form of this command to disable XID processing for this address.
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 will contain the information you configured in the sdlc xid command. The host will check the XID response it receives with the IDBLK and IDNUM parameters (that are configured in the VTAM). If they match, the host will initiate a session with the router. If they do not match, the host will not initiate a session with the router.
The following example specifies an XID value of 01720002 at address c2:
Use the show interfaces privileged EXEC command to display the SDLC information for a given SDLC interface.
This command has no arguments or keywords.
The following is sample output from the show interfaces command for an SDLC primary interface supporting the SDLLC function:
Table 25-1 shows the timer fields relevant to all SDLC connections.
Table 25-1 Timer Fields and Descriptions when SDLC is Enabled
Table 25-2 shows other data given for each SDLC secondary station configured to be attached to this interface.
Table 25-2 SDLC Field Descriptions
encapsulation sdlc-primary
encapsulation sdlc-secondary
sdlc frmr-disable
sdlc holdq
sdlc n1
sdlc n2
sdlc poll-limit-value
sdlc poll-pause-timer
Use the show llc2 privileged EXEC command to display the LLC2 connections active in the router.
This command has no arguments or keywords.
The following is sample output from the show llc2 command:
The display includes a CMNS addendum, indicating LLC2 is running with CMNS. When LLC2 is not running with CMNS, the show llc2 command does not display a CMNS addendum.
Table 25-3 describes significant fields shown in the display.
Table 25-3 Show LLC2 Field Descriptions
llc2 ack-delay-time
llc2 ack-max
llc2 idle-time
llc2 local-window
llc2 n2
llc2 t1-time
llc2 tbusy-time
llc2 tpf-time
llc2 trej-time
llc2 xid-neg-val-time
llc2 xid-retry-time
Posted: Wed Jul 2 23:45:16 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.