Table Of Contents
X.25 Record Boundary Preservation for
Data Communications NetworksWhen to Use Record Boundary Preservation
How Record Boundary Preservation Works
Supported Standards, MIBs, and RFCs
Configuring a PVC to Use RBP for Incoming X.25 Connections
Configuring SVCs to Use RBP for Incoming X.25 Connections
Configuring a PVC to Use RBP for Incoming TCP Connections
Configuring SVCs to Use RBP for Incoming TCP Connections
Verifying Record Boundary Preservation
Monitoring and Maintaining RBP
PVC Configured to Use RBP for Incoming X.25 Connections Example
SVCs Configured to Use RBP for Incoming X.25 Connections Example
PVC Configured to Use RBP for Incoming TCP Connections Example
SVCs Configured to Use RBP for Incoming TCP Connections Example
X.25 Record Boundary Preservation for
Data Communications Networks
Feature History
12.2(8)T
This feature was introduced.
12.4(5th)T
Capability was added for conveying Q-bit data packets between X.25 and TCP/IP hosts.
This document describes the X.25 Record Boundary Preservation for Data Communications Networks feature in Cisco IOS Release 12.2(8)T. It includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
The X.25 Record Boundary Preservation for Data Communications Networks feature enables hosts using TCP/IP-based protocols to exchange data with devices that use the X.25 protocol, retaining the logical record boundaries indicated by use of the X.25 "more data" bit (M-bit).
When to Use Record Boundary Preservation
Before the introduction of the X.25 Record Boundary Preservation for Data Communications Networks feature, Cisco IOS software provided two methods for enabling the exchange of data between X.25 hosts and hosts using TCP/IP-based protocols: protocol translation and X.25 over TCP (XOT). Protocol translation supports a variety of configurations, including translation of a data stream between an X.25 circuit that is using X.29 and a TCP session. The X.29 protocol is an integral part of protocol translation. One aspect of X.29 is that it is asymmetric and allows the packaging of data into X.25 packets to be controlled in one direction only. The TCP protocol is stream-oriented, rather than packet-oriented. TCP does not attach significance to TCP datagram boundaries, and those boundaries can change when a datagram is retransmitted. This inability to preserve boundaries makes protocol translation appropriate only for configurations in which the X.25 packet boundary is not significant.
The XOT feature allows X.25 packets to be forwarded over a TCP session. This allows full control over the X.25 circuit, but the host terminating the TCP session must implement the XOT protocol and the X.25 packet layer protocol.
The Record Boundary Preservation (RBP) feature offers a solution positioned between these two options: it allows logical message boundaries to be indicated without requiring the TCP host to be aware of X.25 protocol details.
How Record Boundary Preservation Works
The TCP protocol does not attach significance to datagram boundaries, so a protocol must be layered over a TCP session to convey record boundary information. The Record Boundary Preservation protocol implements a 6-byte record header that specifies the amount of data following and indicates whether that data should be considered the final part of a logical record. Table 1 describes the format and contents of the record header.
When a router configured with RBP receives an X.25 call that matches a configured X.25 RBP map, the router attempts to open a TCP connection to the specified TCP destination. Each TCP session is mapped to one X.25 virtual circuit. If the TCP session is established, then X.25 data packets received from the caller are combined into logical records as indicated by use of the X.25 M-bit, and the contents of the data packets are forwarded to the TCP destination. The boundaries of these records are preserved by the record header.
The router will not split an X.25 data packet across multiple records unless the data packet exceeds the configured maximum record size; however, TCP will segment the data stream at arbitrary byte boundaries in accordance with TCP specifications.
X.25 data packets with the M-bit set may be combined as long as the resulting record does not exceed the configured maximum record size or, if a maximum record size was not configured, the maximum datagram size for the X.25 interface. The "more data" flag in the record header will reflect the value of the M-bit in the final X.25 data packet. This process of combining packets results in a series of zero or more records whose "more data" flag is set to the value 1 followed by a record whose "more data" flag is set to 0.
Incoming X.25 calls with the "delivery confirmation" bit (D-bit) set will be answered with the D-bit set. However, since the router is the endpoint of the X.25 circuit, X.25 data packets will be acknowledged as soon as their contents have been passed to the TCP connection without waiting for an acknowledgment for the TCP data, regardless of the value of the D-bit. TCP data will be acknowledged as soon as it has been converted to X.25 data packets.
The router will not send Receiver Not Ready (RNR) packets on the X.25 circuit; flow control will be accomplished by withholding acknowledgment.
The following situations will cause the X.25 circuit to be cleared (for an SVC) or reset (for a PVC) and the TCP connection to be closed: receipt of a data packet with the "qualified" bit (Q-bit) set; receipt of any packet type other than data, Receiver Ready (RR), or RNR; or a restart or lower-layer reset on the X.25 interface. When the circuit is cleared or reset, any data not yet passed to the TCP connection will be discarded.
When the router receives the records from the TCP session, it strips the record header and, on the basis of the information in the record header, reassembles the records into X.25 data packets. The data is interpreted as a fixed-length header followed by a variable-length payload whose length is specified in the record header. If the protocol ID or flag field in the header is invalid, the TCP connection will be closed and the X.25 circuit will be cleared or reset. The payload length may be greater than the X.25 packet size and need not be a multiple of the X.25 packet size.
A record that has the "more data" flag set will be logically combined with following records until a record that has the "more data" flag cleared is received. This process results in a sequence of maximum-sized X.25 data packets, each with the M-bit set, followed by an X.25 data packet containing the remaining data that does not have the M-bit set. The router will not wait for an entire record to be received before sending a maximum-size X.25 data packet.
As the records are reassembled into X.25 data packets, the packets are forwarded to the corresponding X.25 circuit.
The router will not set the D-bit or Q-bit on X.25 data packets being sent over circuits that are configured with RBP.
Data received by a router from a TCP session will be buffered while waiting for the other connection to be established. If the connection attempt fails, the data will be discarded. When a TCP connection is closed, the X.25 circuit will be cleared or reset, and any data not yet sent on the X.25 circuit will be discarded.
Benefits
The X.25 Record Boundary Preservation for Data Communications Networks feature enables X.25 and TCP/IP hosts to exchange data while preserving X.25 packet boundaries and without having to carry the full X.25 protocol over the TCP session.
Restrictions
•
•
•
•
Related Documents
For more information about configuring X.25 networks, refer to the following documents:
•
•
Supported Platforms
•
•
•
•
•
•
•
•
•
•
•
Determining Platform Support Through Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Feature Navigator. Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image.
Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Feature Navigator home page at the following URL:
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
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 RFCs are supported by this feature.
Prerequisites
Documentation of the configuration tasks in this document assumes that you know how to configure X.25 networks.
Configuration Tasks
See the following sections for configuration tasks for the X.25 Record Boundary Preservation for Data Communications Networks feature. One or more of the following tasks must be completed:
•
•
•
•
Configuring a PVC to Use RBP for Incoming X.25 Connections
To configure the router to establish a TCP session in response to data received on an X.25 PVC and to use RBP protocol to transfer data between the X.25 host and the TCP session, use the following command in interface configuration mode:
When the x25 pvc rbp remote command is configured, the router will wait until a data packet is received on the specified X.25 PVC; in the meantime, the router will acknowledge any X.25 reset packets on the circuit. When a data packet is received, the router will attempt to establish a TCP connection to the configured IP address and TCP port, using a dynamically assigned local TCP port number. If the connection attempt fails, the router will reset the permanent virtual circuit and will wait for another data packet before attempting to establish the TCP connection. Since this command is associated with a specific X.25 circuit, at most one connection may be active per command.
Configuring SVCs to Use RBP for Incoming X.25 Connections
To configure the router to establish TCP sessions in response to incoming X.25 calls, and to use RBP to transfer data between the X.25 circuit and the corresponding TCP session, use the following command in interface configuration mode:
When the x25 map rbp remote command is configured, the router will accept an incoming X.25 call if the destination address matches an X.25 address configured on the interface on which the call is received, and if the calling address and call user data matches the configured value. When the call is accepted, the router will attempt to open a TCP connection to the configured IP address and TCP port, using a dynamically assigned local TCP port number. If the TCP connection cannot be opened, the X.25 call will be cleared. The number of X.25 calls that may be accepted is limited only by router resources. No information from the X.25 call packet is provided to the TCP/IP host.
Configuring a PVC to Use RBP for Incoming TCP Connections
To configure the router to accept an incoming TCP connection on a specified TCP port, and to use RBP over that session to transfer data between the TCP host and an X.25 PVC, use the following command in interface configuration mode:
When the x25 pvc rbp local command is configured, the router will listen for a TCP connection request to the configured TCP port. Until the connection request is received, any data packets received on the X.25 PVC will cause the PVC to be reset. When the TCP connection request is received, the connection will be accepted, and the router will send an X.25 reset packet over the configured X.25 destination circuit. If the reset packet is not acknowledged, the TCP connection will be closed. Since this command is associated with a specific X.25 circuit, only one connection may be active per command.
Configuring SVCs to Use RBP for Incoming TCP Connections
To configure the router to establish X.25 circuits in response to incoming TCP connections, and to use RBP to transfer data between the TCP session and the corresponding X.25 circuit, use the following command in interface configuration mode:
When the x25 map rbp local port command is configured, the router will listen for a TCP connection request to the configured TCP port. When the connection is accepted, the router will place an X.25 call using the configured X.25 destination interface, destination address, and call user data. If the call is not successfully completed, the TCP connection will be closed. The number of connections that may be established to the TCP port is limited only by router resources. No information from the TCP connection is included in the X.25 call packet sent to the X.25 host.
Verifying Record Boundary Preservation
To verify that RBP connections are configured and performing correctly, complete the following steps.
Step 1
The following is sample output of the show x25 map command for a router that is configured with RBP using the x25 pvc rbp remote command:
Router# show x25 mapSerial1/0:-> rbp, destination host 10.0.0.33 port 9999PVC, 1 VC:1/PThe following is sample output of the show x25 map command for a router that is configured with RBP using the x25 map rbp remote command:
Router# show x25 mapSerial3/0:12132 -> rbp, destination host 10.0.0.32 port 9999permanent, 1 VC:1024The following is sample output of the show x25 map command for a router that is configured with RBP using the x25 pvc rbp local command:
Router# show x25 mapSerial3/0:<- rbp, listening at port 9999PVC, 1 VC:2/PThe following is sample output of the show x25 map command for a router that is configured with RBP using the x25 map rbp local command:
Router# show x25 mapSerial1/0:12131 <- rbp, listening at port 9999permanent, 1 VC:1For descriptions of the show x25 map display fields, see the show x25 map command page later in this document.
Step 2
The following is sample output of the show x25 vc command for a PVC configured with record boundary preservation:
Router# show x25 vcPVC 2, State:D1, Interface:Serial3/0Started 00:08:08, last input 00:00:01, output 00:00:01recordsize:1500, connectedlocal address 10.0.0.1 port 9999; remote address 10.0.0.5 port 11029deferred ack:1Window size input:2, output:2Packet size input:128, output:128PS:2 PR:2 ACK:1 Remote PR:2 RCNT:1 RNR:noP/D state timeouts:0 timer (secs):0data bytes 8000/8000 packets 80/80 Resets 9/0 RNRs 0/0 REJs 0/0 INTs 0/0For descriptions of the show x25 pvc display fields, see the show x25 vc command page later in this document.
Step 3
The following is sample output of the show tcp command:
Router# show tcpStand-alone TCP connection from host 10.0.0.5Connection state is ESTAB, I/O status:1, unread input bytes:0Local host:10.0.0.1, Local port:9999Foreign host:10.0.0.5, Foreign port:11003Enqueued packets for retransmit:0, input:0 mis-ordered:0 (0 bytes)TCP driver queue size 0, flow controlled FALSEEvent Timers (current time is 0x1D0CF8):Timer Starts Wakeups NextRetrans 11 0 0x0TimeWait 0 0 0x0AckHold 10 0 0x0SendWnd 0 0 0x0KeepAlive 20 0 0x1DF68CGiveUp 0 0 0x0PmtuAger 0 0 0x0DeadWait 0 0 0x0iss:2946187848 snduna:2946188909 sndnxt:2946188909 sndwnd: 7132irs:1353667951 rcvnxt:1353669012 rcvwnd: 7132 delrcvwnd: 1060SRTT:231 ms, RTTO:769 ms, RTV:538 ms, KRTT:0 msminRTT:0 ms, maxRTT:300 ms, ACK hold:200 msFlags:passive open, retransmission timeout, keepalive runninggen tcbsDatagrams (max data segment is 1460 bytes):Rcvd:22 (out of order:0), with data:10, total data bytes:1060Sent:21 (retransmit:0, fastretransmit:0), with data:10, total data bytes:1060
Monitoring and Maintaining RBP
To monitor RBP, use the following command in privileged EXEC mode:
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
PVC Configured to Use RBP for Incoming X.25 Connections Example
Interface Serial1/0encapsulation x25x25 pvc 1 rbp remote host 10.0.0.1 port 9999SVCs Configured to Use RBP for Incoming X.25 Connections Example
In the following example, if serial interface 1/0 receives an X.25 call from 12132, the router will map the call and open a TCP connection to port number 9999 at the remote TCP/IP host that has the IP address 10.0.0.1.
interface Serial1/0encapsulation x25 dcex25 address 12030x25 map rbp 12132 remote host 10.0.0.1 port 9999PVC Configured to Use RBP for Incoming TCP Connections Example
Interface serial2/1encapsulation x25x25 pvc 2 rbp local port 9999SVCs Configured to Use RBP for Incoming TCP Connections Example
interface Serial1/0encapsulation x25 dcex25 address 13133x25 map rbp 12131 local port 9999Command Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Wide-Area Networking Command Reference at http://www.cisco.com/en/US/docs/ios/wan/command/reference/wan_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
•
•
•
•
•
•
•
Glossary
CUD—call user data. Field in an X.25 data packet that contains encapsulated upper-layer information.
CUG—closed user group. A collection of DTE devices for which the network controls access among members and between members and nonmembers. A DTE may subscribe to zero, one, or more CUGs. A DTE that does not subscribe to a CUG is referred to as being in the open part of the network.
D-bit—"delivery confirmation" bit. Data packet flag used to request end-to-end acknowledgment for the packet.
DCE—data communications equipment. Devices and connections of a communications network that make up the network end of the user-to-network interface. The DCE provides a physical connection to the network, forwards traffic, and provides a clocking signal used to synchronize data transmission between DCE and DTE devices. Modems and interface cards are examples of DCE.
DTE—data terminal equipment. Device at the user end of a user-network interface that serves as a data source, destination, or both. DTE connects to a data network through a DCE device (for example, a modem) and typically uses clocking signals generated by the DCE. DTE includes such devices as computers, protocol translators, and multiplexers.
local acknowledgment—Method whereby a switch acknowledges a received data packet before it has received acknowledgment of the data from the next hop.
M-Bit—"more data" bit. Data packet flag that indicates that at least one more data packet is required for completion of a message of contiguous data.
PVC—permanent virtual circuit. Virtual circuit that is permanently established.
Q-bit—"qualified" bit. Data packet flag that signifies that the packet's user data is a control signal for the remote device, not a message for the user.
RBP—record boundary preservation. Protocol that defines a way for hosts using TCP/IP-based protocols to exchange data with devices that use the X.25 protocol, preserving the logical record boundaries conveyed by the X.25 M-bit ("more data" bit).
SVC—switched virtual circuit. Virtual circuit that is dynamically established on demand and is torn down when transmission is complete. SVCs are used in situations in which data transmission is sporadic.
X.121—ITU-T standard describing an addressing scheme used in X.25 networks. Sometimes called the X.25 address.
X.25— ITU-T standard that defines how connections between DTE and DCE are maintained for remote terminal access and computer communications in PDNs. X.25 specifies LAPB, a data-link layer protocol, and PLP, a network layer protocol.
XOT—X.25 over TCP.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
Guest