Table Of Contents
Serial Tunnel and Block Serial Tunnel Commands
priority-list protocol stun address
stun route address interface dlci
stun route address interface serial
stun route all interface serial
stun schema offset length format
Serial Tunnel and Block Serial Tunnel Commands
Cisco's serial tunnel (STUN) feature allows Synchronous Data Link Control (SDLC) or High-Level Data Link Control (HDLC) devices to connect to one another through a multiprotocol internetwork rather than through a direct serial link. STUN encapsulates SDLC frames in either the Transmission Control Protocol/Internet Protocol (TCP/IP) or the HDLC protocol. STUN provides a straight passthrough of all SDLC traffic (including control frames, such as Receiver Ready) end-to-end between Systems Network Architecture (SNA) devices.
Cisco's SDLC local acknowledgment provides local termination of the SDLC session so that control frames no longer travel the WAN backbone networks. This means end nodes do not time out, and a loss of sessions does not occur. You can configure your network with STUN, or with STUN and SDLC local acknowledgment. To enable SDLC local acknowledgment, the Cisco IOS software must first be enabled for STUN and routers configured to appear on the network as primary or secondary SDLC nodes. TCP/IP encapsulation must be enabled. Cisco's SDLC transport feature also provides priority queuing for TCP encapsulated frames.
Cisco's block serial tunnel (BSTUN) implementation enables Cisco 2500, 3600, 4000, 4500, 4700 and 7200 series routers to support devices that use the Binary Synchronous Communications (Bisync) datalink protocol and asynchronous security protocols that include Adplex, ADT Security Systems, Inc., Diebold, asynchronous generic, and mdi traffic. Our support of the Bisync protocol enables enterprises to transport Bisync traffic and SNA multiprotocol traffic over the same network.
Use the commands in this chapter to configure BSTUN, Bisync, STUN, and SDLC local acknowledgment networks. For STUN and BSTUN configuration information and examples, refer to the "Configuring Serial Tunnel and Block Serial Tunnel" chapter in the Cisco IOS Bridging and IBM Networking Configuration Guide. To locate documentation of other commands, use the command reference master index or search online.
asp addr-offset
To configure an asynchronous port to transmit and receive polled asynchronous traffic through a BSTUN tunnel, use the asp addr-offset interface configuration command. Use the no form of this command to cancel the specification.
asp addr-offset address-offset
no asp addr-offset
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used to specify the offset from the start of the frame where the address byte is located. This command only applies when the asynchronous-generic protocol has been specified on an interface using a combination of the bstun protocol-group global configuration command and the bstun group interface configuration command.
Interfaces configured to run the asynchronous-generic protocol have their baud rate set to 9600 bps, use 8 data bits, no parity, 1 start bit, and 1 stop bit. If different line configurations are required, use the rxspeed, txspeed, databits, stopbits, and parity line configuration commands to change the line attributes.
The addresses of the alarm panels should be used in the address field of the bstun route address interface configuration command.
Examples
The following example specifies that the first byte in the polled asynchronous frame contains the device address:
asp addr-offset 0Related Commands
asp role
To specify whether the router is acting as the primary end of the polled asynchronous link or as the secondary end of the polled asynchronous link connected to the serial interface and the attached remote device is a security alarm control station, use the asp role interface configuration command. Use the no form of this command to cancel the specification.
asp role {primary | secondary}
no asp role {primary | secondary}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command enables the interface on which ASP is configured. Configure the interface connected to the alarm console as a secondary router and the interface connected to the alarm panel as a primary router.
The addresses of the alarm panels should be used in the address field of the bstun route address interface configuration command.
Examples
The following example specifies the router as the primary end of the link:
asp role primaryRelated Commands
Defines how frames will be forwarded from a BSTUN interface to a remote BSTUN peer.
asp rx-ift
To specify a time period that, by expiring, signals the end of one frame being received and the start of the next, use the asp rx-ift interface configuration command. Use the no form of this command to cancel the specification.
asp rx-ift interframe-timeout
no asp rx-ift
Syntax Description
interframe-timeout
Number of milliseconds between the end of one frame being received and the start of the next frame. The default timeout value is 40 ms.
Defaults
The default timeout value is 40 ms.
Command Modes
Interface configuration
Command History
Usage Guidelines
The interframe timeout is useful when different baud rates are used between the router and the alarm console or alarm panel. For example, you might set an interframe timeout of 6 ms if the polled asynchronous protocol is running at 9600 bps, but set the value to 40 ms if the protocol is running at 300 bps.
This command applies only when the asynchronous-generic protocol has been specified on an interface using a combination of the bstun protocol-group global configuration command and the bstun group interface configuration command.
Interfaces configured to run the asynchronous-generic protocol have their baud rate set to 9600 bps, use 8 data bits, no parity, 1 start bit, and 1 stop bit. If different line configurations are required, use the rxspeed, txspeed, databits, stopbits, and parity line configuration commands to change the line attributes.
The addresses of the alarm panels should be used in the address field of the bstun route address interface configuration command.
Examples
The following example sets the interframe timeout value to 6 ms because the polled asynchronous protocol is running at 9600 bps:
asp rx-ift 6Related Commands
bsc char-set
To specify the character set used by the Bisync support feature in this serial interface as either EBCDIC or ASCII, use the bsc char-set interface configuration command. Use the no form of this command to cancel the character set specification.
bsc char-set {ascii | ebcdic}
no bsc char-set {ascii | ebcdic}
Syntax Description
Defaults
EBCDIC
Command Modes
Interface configuration
Command History
Examples
The following command specifies that the ASCII character set will be used:
bsc char-set asciibsc contention
To specify an address on a contention interface, use the bsc contention interface configuration command. Use the no form of this command to cancel the specification.
bsc contention address
no bsc contention
Syntax Description
Defaults
The default address is 0x01 to accommodate backward compatibility to the previous point-to-point contention implementation.
Command Modes
Interface configuration
Command History
Examples
The following command specifies address 20 on the remote device:
bsc contention 20Related Commands
Specifies a router at the central site as a central router with dynamic allocation of serial interfaces.
bsc dial-contention
To specify a router at the central site as a central router with dynamic allocation of serial interfaces, use the bsc dial-contention interface configuration command. Use the no form of this command to cancel the specification.
bsc dial-contention time-out
no bsc dial-contention
Syntax Description
time-out
Amount of time interface can sit idle before it is returned to the idle interface pool. The range is 2 to 30 seconds. The default is 5 seconds.
Defaults
5 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
A timeout value is configurable to ensure that an interface does not get locked out because of a device outage during transmission.
Examples
The following command defines a dial-in interface at the central site with an idle timeout of 10 seconds:
bsc dial-contention 10Related Commands
bsc host-timeout
To detect deactivation of devices at the host, use the bsc host-timeout interface configuration command. Use the no form of this command to cancel the configuration.
bsc host-timeout interval
no host-timeout interval
Syntax Description
Defaults
The default interval is 600 deciseconds (60 seconds).
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used to detect deactivation of devices at the host. If the host is told to deactivate or not poll a device it will take time for the signal to propagate the network and get the remote end from polling. The timeout can be used to fine tune the delay in detecting the host outage. The remote peer will stop polling the control unit that has timed out in the interval 1 to 2 times the configured timeout value.
Examples
The following example configures a timeout of 500 deciseconds (50 seconds):
bsc host-timeout 500Related Commands
bsc pause
To specify the interval between starts of the polling cycle, use the bsc pause interface configuration command. Use the no form of this command to cancel the specification.
bsc pause time
no bsc pause time
Syntax Description
time
Interval in tenths of a second. The default value is 30 (that is, 30 tenths, or 3 seconds). The maximum time is 255 (25.5 seconds).
Defaults
30 tenths of a second (3 seconds)
Command Modes
Interface configuration
Command History
Usage Guidelines
The following command sets the interval to 20 tenths (2 seconds):
bsc pause 20bsc poll-timeout
To specify the timeout, for a poll or select sequence, use the bsc poll-timeout interface configuration command. Use the no form of this command to cancel the specification.
bsc poll-timeout time
no bsc poll-timeout time
Syntax Description
Defaults
30 tenths of a second (3 seconds)
Command Modes
Interface configuration
Command History
Examples
The following command sets the interval to 20 tenths (2 seconds):
bsc poll-timeout 20bsc primary
To specify that the router is acting as the primary end of the Bisync link connected to the serial interface, and that the attached remote devices are Bisync tributary stations, use the bsc primary interface configuration command. Use the no form of this command to cancel the specification.
bsc primary
no bsc primary
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The Bisync support feature in the serial interface uses the address of the incoming encapsulation for reply.
Examples
The following example specifies the router as the primary role:
bsc primaryRelated Commands
Defines how frames will be forwarded from a BSTUN interface to a remote BSTUN peer.
bsc retries
To specify the number of retries performed before a device is considered to have failed, use the bsc retries interface configuration command. Use the no form of this command to cancel the specification.
bsc retries retries
no bsc retries retries
Syntax Description
Defaults
5 retries
Command Modes
Interface configuration
Command History
Examples
The following command sets the retry count to 10:
bsc retries 10bsc secondary
To specify that the router is acting as the secondary end of the Bisync link connected to the serial interface, and the attached remote device is a Bisync control station, use the bsc secondary interface configuration command. Use the no form of this command to cancel the specification.
bsc secondary
no bsc secondary
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The Bisync support feature in this serial interface uses the address of the poll or selection block in the framing encapsulation. It also generates an end of transmission (EOT) frame preceding each Bisync poll and selection.
Examples
The following example specifies the router as the secondary role:
bsc secondaryRelated Commands
Defines how frames will be forwarded from a BSTUN interface to a remote BSTUN peer.
bsc servlim
To specify the number of cycles of the active poll list that are performed between polls to control units in the inactive poll list, use the bsc servlim interface configuration command. Use the no form of this command to cancel the specification.
bsc servlim servlim-count
no bsc servlim servlim-count
Syntax Description
Defaults
3 cycles
Command Modes
Interface configuration
Command History
Examples
The following command sets the number of cycles to 2:
bsc servlim 2bsc spec-poll
To set specific polls, rather than general polls, used on the host-to-router connection, use the bsc spec-poll interface configuration command. Use the no form of this command to cancel the specification.
bsc spec-poll
no spec-poll
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the bsc spec-poll command when a router is connected to a host, and only when that host issues specific polls rather than general polls. Tandem hosts that poll ATM cash machines are typically configured to use specific polls rather than general polls.
Configuring a downstream (control-unit/device connected) router to support specific polling has no effect.
Examples
The following commands configure serial interface 0 to use specific poll:
interface serial 0description Connection to host.encapsulation bstunbstun group 1bsc secondarybsc spec-pollbsc char-set ebcdicbstun route all tcp 10.10.14.122bstun group
To specify the BSTUN group to which the interface belongs, use the bstun group interface configuration command. Use the no form of this command to remove the interface from the BSTUN group.
bstun group group-number
no bstun group group-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Each BSTUN-enabled interface must be placed in a BSTUN group that was previously defined by the bstun protocol-group command. Packets only travel between BSTUN-enabled interfaces that are in the same group.
Examples
The following example specifies that serial interface 1 belongs to the previously defined protocol group 1:
interface serial 1encapsulation bstunbstun group 1Related Commands
Defines a BSTUN group and the protocol it uses.
Configures BSTUN on a particular serial interface.
bstun keepalive-count
To define the number of times to attempt a peer connection before declaring the peer connection to be down, use the bstun keepalive-count global configuration command. Use the no form of this command to cancel the definition.
bstun keepalive-count count
no bstun keepalive-count
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The following example sets the number of times to retry a connection to a peer to 4:
bstun keepalive-count 4Related Commands
bstun lisnsap
To configure a SAP on which to listen for incoming calls, use the bstun lisnsap global configuration command. Use the no form of this command to cancel the SAP on which to listen.
bstun lisnsap sap-value
no bstun lisnsap
Syntax Description
Defaults
The default SAP value is 04.
Command Modes
Global configuration
Command History
Usage Guidelines
Changes to the bstun lisnsap command configuration will not take effect until after the router has been reloaded.
Examples
The following example configures a SAP for listening:
bstun lisnsapRelated Commands
bstun peer-name
To enable the BSTUN function, use the bstun peer-name global configuration command. Use the no form of this command to disable the function.
bstun peer-name ip-address
no bstun peer-name ip-address
Syntax Description
ip-address
Address by which this BSTUN peer is known to other BSTUN peers that are using the TCP transport.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
The IP address defines the address by which this BSTUN peer is known to other BSTUN peers that are using the TCP transport. If this command is unconfigured or the no form of this command is specified, all BSTUN routing commands with IP addresses are deleted. BSTUN routing commands without IP addresses are not affected by this command.
Examples
The following example enables the BSTUN function:
bstun peer-name 150.10.254.201Related Commands
bstun protocol-group
To define a BSTUN group and the protocol it uses, use the bstun protocol-group global configuration command. Use the no form of this command to delete the BSTUN group.
bstun protocol-group group-number protocol
no bstun protocol-group group-number protocol
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Interfaces configured to run the Adplex protocol have their baud rate set to 4800 bps, use even parity, 8 data bits, 1 start bit, and 1 stop bit.
Interfaces configured to run the adt-vari-poll and adt-poll-select protocols have their baud rate set to 600 bps, use even parity, 8 data bits, 1 start bit, and 1.5 stop bits. If different line configurations are required, use the rxspeed, txspeed, databits, stopbits, and parity line configuration commands to change the line attributes.
Interfaces configured to run the asynchronous-generic protocol have their baud rate set to 9600 bps, use no parity, 8 data bits, 1 start bit, and 1 stop bit. If different line configurations are required, use the rxspeed, txspeed, databits, stopbits, and parity line configuration commands to change the line attributes.
Interfaces configured to run the mdi protocol have their baud rate set to 600 bps, use even parity, 8 data bits, 1 start bit, and 1.5 stop bits. If different line configurations are required, use the rxspeed, txspeed, databits, stopbits, and parity line configuration commands to change the line attributes. The mdi protocol allows alarm panels to be sent to the MDI alarm console.
Examples
The following example defines BSTUN group 1, specifies that it uses the Bisync protocol, and indicates that frames will be locally acknowledged:
bstun protocol-group 1 bsc-local-ackRelated Commands
bstun remote-peer-keepalive
To enable detection of the loss of a peer, use the bstun remote-peer-keepalive global configuration command. Use the no form of this command to disable detection.
bstun remote-peer-keepalive seconds
no bstun remote-peer-keepalive
Syntax Description
Defaults
30 seconds
Command Modes
Global configuration
Command History
Examples
In the following example, the remote-peer-keepalive interval is set to 60 seconds:
bstun remote-peer-keepalive 60Related Commands
Defines the number of times to attempt a peer connection before declaring the peer connection to be down.
bstun route
To define how frames will be forwarded from a BSTUN interface to a remote BSTUN peer, use the bstun route interface configuration command. Use the no form of this command to cancel the definition.
bstun route {all | address address-number} {tcp ip-address | interface serial number}
no bstun route {all | address address-number} {tcp ip-address | interface serial number}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
When the ADplex protocol is specified in the bstun protocol-group command, ADplex device addresses are limited to the range 1 to 127 because ADplex alarm panels invert the device address in the ADplex frame when responding to alarm console commands.
When the adt-poll-select protocol is specified in the bstun protocol-group command, routes for specific addresses cannot be specified on the downstream router (connected to the alarm panel), because no address field is provided within frames that are sent back to the alarm console. The only way to route traffic back to the alarm console is to use the bstun route all form of the bstun route command. This is also true for the diebold protocol and any other protocol supported by the asynchronous-generic protocol group that does not include a device address in the frame.
When the adt-vari-poll protocol is specified in the bstun protocol-group command, ADT device addresses are limited to the range 0 to 255, and address 0 is reserved for use as a broadcast address for adt-vari-poll only. If address 0 is specified in the bstun route address form of the bstun route command, the address is propagated to all configured BSTUN peers.
It is possible to use both the all and the address keywords on different bstun route commands on the same serial interface. When this is done, the address specifications take precedence; if none of these match, then the all specification is used to propagate the frame.
Examples
In the following example, all BSTUN traffic received on serial interface 0 is propagated, regardless of the address contained in the serial frame:
bstun route all interface serial 0bstun route (Frame Relay)
To define how frames will be forwarded from a BSTUN interface to a remote BSTUN peer over Frame Relay, use the bstun route (Frame Relay) interface configuration command. Use the no form of this command to cancel the definition.
bstun route {all | address cu-address} interface serial number [dlci dlci rsap] [priority priority]
no bstun route {all | address cu-address} interface serial number [dlci dlci rsap] [priority priority]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Examples
The following example configures BSTUN over Frame Relay. All BSTUN traffic is propagated to serial interface 0 regardless of the address contained in the serial frame:
bstun route all interface serial 0 dlci 16encapsulation bstun
To configure BSTUN on a particular serial interface, use the encapsulation bstun interface configuration command. Use the no form of this command to disable the BSTUN function on the interface.
encapsulation bstun
no encapsulation bstun
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The encapsulation bstun command must be configured on an interface before any further BSTUN or Bisync commands are configured for the interface.
You must use this command to enable BSTUN on an interface. Before using this command, complete the following two tasks:
•
Enable BSTUN on a global basis by identifying BSTUN on IP addresses. The command is bstun peer-name.
•
After using the encapsulation bstun command, use the bstun group command to place the interface in the previously defined protocol group.
Examples
The following example configures the BSTUN function on serial interface 0:
interface serial 0no ip addressencapsulation bstunRelated Commands
Specifies the BSTUN group to which the interface belongs.
Enables the BSTUN function.
Defines a BSTUN group and the protocol it uses.
encapsulation stun
To enable STUN encapsulation on a specified serial interface, use the encapsulation stun interface configuration command.
encapsulation stun
Syntax Description
This command has no arguments or keywords.
Defaults
STUN encapsulation is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to enable STUN on an interface. Before using this command, complete the following two tasks:
•
•
After using the encapsulation stun command, use the stun group command to place the interface in the previously defined protocol group.
To disable stun encapsulation, configure the default interface encapsulation using the encapsulation command and specify hdlc as the encapsulation-type
There is not a no form for this command.
Examples
This partial configuration example shows how to enable serial interface 5 for STUN traffic:
! sample stun peer name and stun protocol-group global commandsstun peer-name 131.108.254.6stun protocol-group 2 sdlc!interface serial 5! sample ip address commandno ip address! enable the interface for STUN; must specify encapsulation stun! command to further configure the interfaceencapsulation stun! place interface serial 5 in previously defined STUN group 2stun group 2! enter stun route commandstun route 7 tcp 131.108.254.7Related Commands
Places each STUN-enabled interface on a router in a previously defined STUN group.
Enables STUN for an IP address.
Creates a protocol group.
frame-relay map bstun
To configure BSTUN over Frame Relay for passthru, use the frame-relay map bstun interface configuration command. Use the no form of this command to cancel the configuration.
frame-relay map bstun dlci
no frame-relay map bstun dlci
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Direct encapsulation over Frame Relay is supported only for an encapsulation type of cisco, configured using the encapsulation frame-relay command.
Examples
The following example maps BSTUN traffic to DLCI number 16:
frame-relay map bstun 16Related Commands
Configures a SAP on which to listen for incoming calls.
Defines a BSTUN group and the protocol it uses.
encapsulation frame-relay
Enables Frame Relay encapsulation.
priority-list protocol bstun