Table Of Contents
Bisync-to-IP Conversion for Automated Teller Machines
Mapping the Peer State to Polling
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Mapping the Peer State to Polling
Setting the Reconnect Interval
Enabling BSTUN Remote Keepalive
Configuring BSTUN on the Serial Interface
Assigning a Serial Interface to a BSTUN Group
Configuring Bisync Options on a Serial Interface
Specifying How Frames Are Forwarded
Bisync-to-IP Conversion for Automated Teller Machines
Feature History
12.2(4)T
This feature was introduced.
12.2(13)T
The bstun peer-map-poll command was added.
This document describes the Bisync-to-IP Conversion for Automated Teller Machines feature in Cisco IOS Release 12.2(4)T and the enhancement introduced in Cisco IOS Release 12.2(13)T and includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
The Bisync-to-IP Conversion for Automated Teller Machines feature enables customers to attach a binary synchronous communication (bisync) automated teller machine to a serial interface on a Cisco router running bisync-to-IP (BIP) protocol translation, and then to route the data over a TCP/IP network directly to an IP-based application host.
This feature works by removing the bisync protocol headers enclosing the application data, creating a TCP/IP connection with the application host, and delivering the data directly to the TCP/IP application running on that host.
At the router, application data from the attached bisync device is encapsulated in IP. At the host site, traffic is delivered directly to the application host computer through use of a new command provided with this feature, bstun route (BIP). The bstun route (BIP) command is used to specify BIP peer tunneling as the method to be used to encapsulate data from a Block Serial Tunnel (BSTUN) interface to a bisync device to a remote host over an IP network. For more information about this command, see the "Command Reference" section of this document.
Figure 1 shows how you can configure the bisync link between two devices so that converted traffic is delivered to a host using BIP.
Figure 1 Cisco Router Support of Bisync Devices with BIP
Figure 2 shows how you can configure the bisync link between multiple routers and multiple bisync devices so that converted traffic is delivered to a host using BIP.
Figure 2 Cisco Router Support of Multiple Routers and Multiple Bisync Devices with BIP
This feature is closely associated with BSTUN and the procedures for configuring them. To configure this feature, you will use many of the same procedures and commands required for configuring BSTUN, without the previous requirement of terminating the connection on a peer Cisco router and recreating the bisync serial protocol at the peer. For this feature, rather than one end of the tunnel terminating on another router, the tunnel terminates on a non-Cisco host computer. This feature is designed to address the specific requirements of automated teller machines only, and requires that the host application accommodate this specific method. This restriction is necessary because the Bisync-to-IP Conversion for Automated Teller Machines feature provides conversion for a single device within a 3270 control unit.
For more information, see the "Prerequisites" section and the "Configuration Tasks" section later in this document.
Mapping the Peer State to Polling
When using BIP, Automated Teller Machines (the peer devices) are polled when the BIP tunnel between the host machine and the Automated Teller Machine becomes active. At the same time the Automated Teller Machine is powered on and could be active. Because the state of the host application is unknown at this point, there can be a window in which the host is not ready to receive anything from the Automated Teller Machine even though the Automated Teller Machine is active.
As of Cisco IOS Release 12.2(13)T you can use the bstun peer-map-poll command in global configuration mode to map the Automated Teller Machine state to polling. The default is to not map the peer state to polling. If you configure this command, BIP activates polling when the BIP tunnel becomes active and stops polling when the tunnel connection is terminated. When the peer state-to-polling is not mapped, BIP waits for the host to issue an "active" status message across the BIP tunnel before polling the Automated Teller Machine device and polling is stopped when an "inactive" status message is received across the tunnel or the tunnel connection is terminated.
Benefits
Improves System Performance
This feature has the advantage of removing complexity from central data centers, thus reducing cost and enabling a data center to more easily use multiservice applications. At the same time, it improves system performance by removing potential points of failure and allowing for multiple paths for delivery of the application data.
Accommodates Improved Network Design
This feature supports the conversion of bisync to native TCP for direct delivery to host applications enabled for TCP devices. This enhanced support eliminates the need for headend tunnel routers, and allows for network designs that provide higher availability. It allows the remote, serially attached bisync device to attach to the application host through a LAN interface instead of through a serial interface.
Restrictions
This feature addresses the specific requirements of automated teller machines only. It requires that the host application accommodate removing the BIP headers encapsulating the application data. This restriction is necessary because the Bisync-to-IP Conversion for Automated Teller Machines feature provides conversion for a single device within a 3270 control unit.
Related Features and Technologies
•
•
Related Documents
•
•
Supported Platforms
•
•
•
•
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Note
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
•
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
No new or modified standards are supported by this feature.
Prerequisites
Before you configure the Bisync-to-IP Conversion for Automated Teller Machines feature, BSTUN must be enabled. For more information about BSTUN, refer to the following chapters of the Cisco IOS Bridging and IBM Networking Configuration Guide, Release 12.2:
•
•
Configuration Tasks
See the following sections for configuration tasks for the Bisync-to-IP Conversion for Automated Teller Machines feature. Each task in the list is identified as either required or optional.
•
•
•
•
•
•
•
•
•
•
Enabling BSTUN
To enable BSTUN in IP networks, use the following command in global configuration mode:
The IP address in the bstun peer-name command 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.
Mapping the Peer State to Polling
To map the peer state to polling, us the following command in global configuration mode:
Router(config)# bstun peer-map-poll
Enables BSTUN to map the peer state or received status messages to polling.
Defining the Protocol Group
To define the protocol group, use the following command in global configuration mode:
Router(config)# bstun protocol-group group-number bsc-local-ack
Defines the protocol group.
The bsc-local-ack keyword is the only one supported by BIP.
Setting the Reconnect Interval
To set the amount of time for the system to wait before trying to reconnect to a peer, use the following command in global configuration mode:
Enabling BSTUN Remote Keepalive
To enable detection of the loss of a peer, use the following commands in global configuration mode, as needed:
:
Configuring BSTUN on the Serial Interface
Configure BSTUN on the serial interface before issuing any further BSTUN or protocol configuration commands for the interface. To configure the BSTUN function on a serial interface, use the following commands in interface configuration mode:
Step 1
Router(config-if)# interface serial number
Specifies a serial port.
Step 2
Router(config-if)# encapsulation bstun
Configures BSTUN on an interface.
Note
Assigning a Serial Interface to a BSTUN Group
Each BSTUN-enabled interface on a router must be assigned to a previously defined BSTUN group. Packets will travel only between BSTUN-enabled interfaces that are in the same group. To assign a serial interface to a BSTUN group, use the following command in interface configuration mode:
Router(config-if)# bstun group group-number
Assigns a serial interface to a BSTUN group.
Configuring Bisync Options on a Serial Interface
To configure bisync options on a serial interface, use the following commands in interface configuration mode, as needed:
Specifying How Frames Are Forwarded
To specify how frames are forwarded when received on a BSTUN interface, use the following command in interface configuration mode:
Verifying the Status of BSTUN
To display statistics for BSTUN interfaces, protocol groups, number of packets sent and received, local acknowledgment states, and other activity information, use the following commands in privileged EXEC mode, as needed:
Configuration Examples
This section provides the following BSTUN traffic routing example. BSTUN traffic with the control unit address C5 is routed to and from the host computer specified by the IP address 192.168.60.100. The BIP form of TCP encapsulation (as indicated by the bip keyword) is used to propagate the serial frames.
bstun route address C5 bip 192.168.60.100 fport 2000 lport 3005Command Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
New Commands
Modified Command
bstun peer-map-poll
To map the state of the peer to polling, use the bstun peer-map-poll command in global configuration mode. To disable mapping of the peer state to polling and map to the received status messages, use the no form of this command.
bstun peer-map-poll
no bstun peer-map-poll
Syntax Description
This command has no arguments or keywords.
Defaults
The received status messages are mapped to polling.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the bstun peer-map-poll command to map the peer state to polling. If you configure this command, bisync-to-IP protocol (BIP) activates polling when the BIP tunnel becomes active and stops polling when the tunnel connection is terminated. When the peer state-to-polling is not mapped, BIP waits for the host to issue an "active" status message across the BIP tunnel before polling the Automated Teller Machine (peer) device and polling is stopped when an "inactive" status message is received across the tunnel or the tunnel connection is terminated.
Examples
The following example shows how to map the peer state to polling:
bstun peer-map-pollRelated Commands
bstun peer-name
Enables the BSTUN function.
Set the amount of time for the system to wait before trying to reconnect to a peer.
Displays the current status of STUN connections.
bstun reconnect-interval
To set the amount of time for the system to wait before trying to reconnect to a peer, use the bstun reconnect-interval command in global configuration mode. To return to the default setting, use the no form of the command.
bstun reconnect-interval time-value
no bstun reconnect-interval time-value
Syntax Description
time-value
Amount of time (in seconds). The range is from 1 to 600 seconds. The default is 60 seconds.
Defaults
60 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies only to Block Serial Tunnel (BSTUN) route bisync-to-IP (BIP) connections that are defined as active.
Examples
In the following example, the system is configured to wait 300 seconds before trying to reestablish a peer connection:
bstun reconnect-interval 300Related Commands
bstun route (BIP)
Specifies how frames will be forwarded from a BSTUN interface to a remote host over an IP network.
bstun route (BIP)
To specify how frames will be forwarded from a Block Serial Tunnel (BSTUN) interface to a remote host over an IP network, use the bstun route command in interface configuration mode. To cancel the specification, use the no form of this command.
bstun route {address cu-address} {bip ip-address} {fport port-number} {lport port-number | passive} [tcp-queue-max] [transparent]
no bstun route {address cu-address} {bip ip-address} {fport port-number} {lport port-number | passive} [tcp-queue-max] [transparent]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The remote or foreign IP address and port number are required for all connection types.
The user selects the connection type by either configuring a unique local port or by using the passive keyword. If the passive keyword is used, the foreign port must be unique and the system does not attempt an outbound connection but instead listens on port number 1963 for any connection requests from the host computer. If active is configured (that is, if a local port is configured), the system attempts an outbound connection but also listens for the connection to be established inbound.
The cu-address argument is the control unit poll address for the bisync end station. This address is a hexadecimal number from 01 to FF. Valid addresses vary depending on the setting of the bsc char-set interface configuration command.
The TCP queue length, an optional configuration parameter, defaults to 100 packets.
By default, the method of sending text on a defined route is to use nontransparent bisync text. To send in transparent bisync text, specify the optional transparent keyword.
Examples
In the following example, BSTUN traffic with the control unit address C5 is routed to and from the host computer specified by the IP address 192.168.60.100:
bstun route address C5 bip 192.168.60.100 fport 2000 lport 3005Related Commands
show bstun
To display the current status of serial tunnel (STUN) connections, use the show bstun command in privileged EXEC mode.
show bstun [group bstun-group-number] [address address-list]
Syntax Description
group bstun-group-number
(Optional) Block Serial Tunnel (BSTUN) group number. Valid numbers are decimal integers in the range from 1 to 255.
address address-list
(Optional) List of poll addresses.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show bstun command with no options:
Router# show bstunThis peer: 172.26.54.111*Serial0/0 (group 201 [bsc-local-ack]) route transport address dlci lsap state rx_pkts tx_pkts dropsC1 TCP 172.26.54.2 closed 0 0 0 C2 TCP 172.26.54.2 closed 0 0 0 C3 TCP 172.26.54.2 closed 0 0 0The following is sample output from the show bstun command using the new BIP configuration:
Router# show bstunThis peer: 172.26.54.111*Serial0/0 (group 201 [bsc-local-ack]) route transport address fport lport state rx_pkts tx_pkts dropsC1 BIP 172.26.54.2 2002 1963 closed 0 0 0 C2 BIP 172.26.54.2 2001 1963 closed 0 0 0 C3 BIP 172.26.54.2 2000 1963 closed 0 0 0Table 1 describes the significant fields shown in the output.
Guest
