[ Previous | Next | Contents | Search ]
AIXLink/X.25 1.1 for AIX: Guide and Reference

Differences Between AIX Versions

The following table shows the main characteristics and differences between X.25 support on AIX versions 3 and 4.

Differences between AIX Version 3.1, 3.2, 3.2.5, and 4

AIX V3 BOS AIX X.25 V1.1 AIXLink/X.25 V1.1
AIX Operating System AIX Version 3.2 AIX Version 3.2.5 (minimum) AIX Version 4.1.5, 4.2.1, and 4.3.0 or higher
Packaging Basic X.25 support in BOS X.25 support through the Licensed Program X.25 support through the Licensed Program. Selectable v.c. capacity:
Entry Up to 4
Basic Up to 16
Extended Up to 64
Advanced Up to 256
Full unrestricted
Applications:
TCP/IP X (xt#), x25xlate X (xs#), X25ip
PAD support 3rd Party x
SNMP agent /MIB - X (x25smuxd) (subsets of RFCs 1381 and 1382)
NPI (packet layer NPI) - x
DLPI (frame layer API) - x*
Application Compatibility - COMIO emulation provides X.25 access through /dev/x25s# for X.25 BOS applications and commands
SNA x COMIO emulation -* (Available in 4.1 and later platforms)
AIX Version 3 X.25 API x COMIO emulation
Commands:
xcomms x - -
xroute x COMIO emulation COMIO emulation
xtalk x COMIO emulation COMIO emulation
xmanage x - -
x25 line trace xmonitor -packet -frame x25s# x25mon -p -f -n sx25a#

AIX V3 BOS AIX X.25 V1.1 AIXLink/X.25 V1.1
Installation:
SMIT Installation All X.25 software is installed at once Selectable Install: All   DLPI   TCP/IP* Runtime*   NPI   Triple-X PAD   COMIO
Adapter microcode Copy from Options disk Installed with Licensed Program
Notes:
  1. A port cannot be used for running both frame and packet layer applications - DLPI interface is enabled via SMIT.
  2. With the X.25 licensed program product for AIX 3.2.5, xmanage allows the user to view, but not change, the connection status.
  3. The Runtime software component is the minimum required for X.25 - all other components require the runtime software.
  4. To run TCP/IP over X.25, the user must also install the TCP/IP software component.
Miscellaneous:
Driver names x25s# (device driver) twd#* (streams device driver)
X.25 port names x25s# sx25a#
CCITT Conformance 1980, 1984 1980, 1984, 1988
Hardware:
X.25 Interface CoProcessor/2 (Micro Channel) x25s# (until AIX 3.2.3e) ampx# (from AIX 3.2.3e)       X ampx#
ARTIC PortMaster/A: V.24 (8-port fanout) V.35 (6-port fanout) X.21 (6-port fanout)    -       X* amp#
ARTIC960: V.36 (6-port fanout) X.21 (8-port fanout) EIA-232E (8-port fanout)    -         ricio#
X.25 Interface CoProcessor (ISA bus)    -    -    X* ampx#
2-Port Multiprotocol PCI Adapter    -    - X*dpmp#
Maximum adapters per system 4 per bus* Limited to 8 adapters per system.
Maximum virtual circuits 64 virtual circuits 512 total Virtual Circuits per port, 1024 total Virtual Circuits per board (512 on a single port*) and 4096 total Virtual Circuits per system.
Packets Per Second (pps) 128-octet packets 35 pps 100 pps per X.25 Interface adapter, 200 pps per PortMaster adapter, 1000 pps per ARTIC960 adapter, 650 pps per 2-Port Multiprotocol adapter.
Modem Cable Interface / Maximum speeds:
X.21 (15-pin) 64 Kbps 64 Kbps 64 Kbps*
V.24 (24-pin) 19.2 Kbps 19.2 Kbps 19.2 Kbps
V.35 (34-pin) 64 Kbps* 64 Kbps* 64 Kbps*
Network Attachment (synchronous, full duplex, network/modem clocking):




Dedicated leased line x x
Dial-up (X.32, V.25bis) - x
Notes:
  1. ARTIC PortMaster support is made of three components: a base PortMaster adapter with at least 1 MB memory, a V.24, V.35, or X.21 electrical interface board/daughter card (EIB), and the matching interface cable/fanout box.
  2. ARTIC960 support is made of three components: a base ARTIC960 adapter with at least 4 MB memory, a V.24, V.36, or X.21 application interface board/daughter card (AIB), and the matching interface cable/fanout box.

    Note: The ARTIC960 adapter is supported on AIXLink/X.25 1.1.3 (and later).

  3. The ISA and microchannel bus versions of the X.25 Interface Co-Processor adapters use the same modem cables (V.24, V.35, X.21).
  4. Up to eight adapters are supported on systems with dual Micro Channel. Each microchannel supports 4 adapters.
  5. 512 virtual circuits is the recommended maximum because the X.25 Interface Co-Processor adapters have only one port.
  6. Packet per second (pps) values assume full 128-octet packets and were measured at the packet level.
  7. The CCITT V.35 specification defines 56 Kbps as the maximum line speed.
  8. The twd streams device driver is not used for X.25 ports configured over the 2-Port Multiprotocol PCI Adapter. Please refer to "Appendix H" for more information.
  9. The ARTIC960 Adapter supports speeds up to Mbs on the V.35/V.36 and x.

Differences Between X.25 Licensed Program and AIX Version 3 Base X.25 Support

If you are migrating from the AIX Version 3 base X.25 support to the X.25 Licensed Program, read the following. This section explains what hardware, functionality, configuration and setup procedures have been changed with the new X.25 Licensed Program.

Hardware Differences

The X.25 Licensed Program supports the:

X.25 Supported Adapters
Adapter AIX Version 3 Base X.25 X.25 Licensed Program
X.25 Co-Processor/2 supported supported
X.25 Co-Processor ISA-bus not supported supported
RIC Portmaster Adapter/A 1MB not supported supported
RIC Portmaster Adapter/A 2MB not supported supported
ARTIC960 4MB not supported supported
2-Port Multiprotocol PCI Adapter not supported supported

Functionality Differences

The X.25 Licensed Program provides the following new features:

Packet Layer

The main differences between CCITT 1984 and 1988 X.25 recommendations at the packet level are:

Network User Identification (NUI) Network User Identification (NUI) related facilities are divided into three facilities:
  • NUI_subscription
  • NUI_override
  • NUI_selection
DTE/DTE Operation DTE-to-DTE operation without an intervening network is defined. In this situation, one DTE must act as DCE. The DTE acting as DCE at packet layer may be acting as DTE at Data Link Layer and vice versa. This is an optional facility.
Circuit-switched Connection without Prior Agreement
                          A circuit-switched connection without prior agreement (such as electronic mail-order) is defined and default values specified for all applicable parameters. This is an optional capability.
Throughput Class of 64000 bits/s A new throughput class of 64000 bits per second is defined. This is an optional capability.
Address Block Definition A new address block is defined for call setup and clearing packets that allows addresses of 12 or 15 digits. This is an optional capability.
TOA/NPI Address Subscription A new facility, TOA/NPI_Address_Subscription, is added to accommodate E.164 (ISDN) addresses of up to 17 digits in length. This addition results in a redefinition of the address block and the consequent definition of new formats for the CALL_REQUEST, CALL_ACCEPTED, CALL_CONNECTED, CLEAR_REQUEST, CLEAR_INDICATION and CLEAR_CONFIRMATION packets. This is an optional capability.
Call Deflection Call_Deflection_selection facilities whereby the DTE forwards calls after receiving an INCOMING_CALL packet (unlike CALL_REDIRECTION that is handled in the network and the originally called DTE never receives an INCOMING_CALL packet) is added. There are three call deflection facilities:
  • Call_Deflection_Subscription enables the DTE to request a Call_Deflection_Selection.
  • Call_Deflection_Selection may be used on a per-virtual-call basis only if Call_Deflection_Subscription is subscribed to.
  • Call_Deflection_Notification which informs the alternate DTE that the call is forwarded.

    These are optional user facilities.

Priority Facility A priority facility specifies the priority of data on a connection, and priority to keep a connection. This is an optional capability.
Maximum size of Called and Calling Address Extension
                          The maximum size of the called and calling address extension fields is extended from 32 to 40 digits, and an OSI/non-OSI indicator has been added. Support of the larger address is optional. However, a test of the OSI/non-OSI indicator is required to determine the size of the called and calling address.

Recognized Private Operating Agency RPOA related facilities are subdivided into:

  • RPOA_Subscription applies to all virtual calls.
  • RPOA_Selection applies to a given virtual call and does not require RPOA_Subscription.

    These are optional capabilities.

Mandatory Address Length Fields in CALL_ACCEPTED packets
                          The use of the Address Length Fields in CALL_ACCEPTED packets is mandatory, even if they are set to zero.
Mandatory Facility Length Fields in CALL_ACCEPTED packets
                             The use of the Facility Length Fields in CALL_ACCEPTED packets is mandatory, even if they are set to zero.
Virtual Circuit Clearing/Resetting Failure When a CLEAR_REQUEST packet is not confirmed within time-limit T23, the DTE will retry the call-clearing procedure up to R23 times, at T23 intervals, before notifying the higher layer (virtual circuit user) of the failure; leaving the logical channel in the DTE_CLEAR_REQUEST rate (p6) rather than placing the logical channel in an inoperative state as specified by early versions.

When a RESET_REQUEST packet is not confirmed within time-limit T22, the DTE will retry the resetting procedure up to R22 times, at T22 intervals, before notifying the higher layer (virtual circuit user) of the failure; leaving the logical channel in the DTE_RESET_REQUEST state (d2) rather than placing the logical channel in an inoperative state as specified by early versions.

Frame Layer

The main differences between CCITT 1984 and 1988 X.25 recommendations at the frame level are:

DTE/DTE Operation Although not specified in CCITT Recommendation X.25, International Standard Organization ISO 7776 supports communication between two DTEs without an intervening network. Since there is no intervening network, link layer characteristics must be made by bilateral agreement rather than at subscription time. This is an optional capability but is required for communication using Open Systems-Interconnect (OSI).
Clearing a FRMR Condition at the DCE After the DCE has transmitted a FRMR response, the frame rejection condition is cleared when the DCE receives a FRMR response (in addition to when a SABM/SABME, DISC or DM is sent or received).
Maximum Number of Outstanding I-Frames American National Standards ANS X3.100 specifies that all networks must support k=7. K is the maximum number of outstanding I-frames.

Installation, Configuration, and Setup Differences

Since X.25 is a licensed program, the first step in your configuration and setup procedure is to install the X.25 code. You do not need to install the microcode from diskette anymore; it is now installed with the licensed program.

The next step is to configure the device driver and the X.25 port. As soon as the X.25 port is configured and available, the X.25 licensed program software tries to bring up the frame and packet layer, which means that you don't have to use the xmanage command to connect to the X.25 network. The xmanage command is not supported by the X.25 licensed program.

You'll probably need to change some attributes such as number of virtual circuits and throughput. If you are going to use SMIT fast paths, be aware that many of them have changed.

SMIT Fast Path Differences
Parameter Old SMIT Fast Path New SMIT Fast Path
Change / Show X.25 General Parameters x25csg x25str_mp_csp_g_sel
Change / Show X.25 Frame Parameters x25csf x25str_mp_csp_f_sel
Change / Show X.25 Packet Parameters x25csp x25str_mp_csp_p_sel

The xroute command works only with X.25 ports that have COMIO emulation configured and must be used only when you have applications which use this emulation (such as xtalk and SNA ). The new TCP/IP implementation does not use the COMIO emulation, so you no longer need to add xroute entries when using more than one X.25/IP interface.

The X.25 licensed program allows you to enable or disable only these two facilities:

Command Differences

Many commands that were used for management and configuration purposes have changed.

The x25ip command has the same syntax as the x25xlate command. The lsx25 command uses information available from the system configuration database to display the relationship between adapters, drivers, ports, and other components. that are configured to use X.25.

Attributes Differences

The following table shows the differences in attribute names.

Attribute Names
AIX Version 3 X.25 Support AIX X.25 Licensed Program
num_in_out_svc bi_vc_num
in_out_svc bi_vc_start
ccitt_support ccitt
connection_mode connect_seq
d_bit d_bit_accept
pvc_d_bit def_pvc_d_bit
def_rx_pkt_size def_rx_size
def_rx_through def_rx_th
def_rx_pkt_win def_rx_win
def_tx_pkt_size def_tx_size
def_tx_through def_tx_th
def_tx_pkt_win def_tx_win
frame_modulo f_modulo
fast_select fs_mode
num_in_svcs in_vc_num
in_svc in_vc_start
line_type line_type
local_nua local_nua
max_rx_pkt_size max_rx_size
max_rx_pkt_win max_rx_win
max_tx_pkt_size max_tx_size
max_tx_pkt_win max_tx_win
n2_counter n2
network_id network_id
num_out_svcs out_vc_num
out_svc out_vc_start
pkt_modulo pkt_modulo
num_of_pvcs pvc_num
pvc_channel pvc_start
rev_charging rev_charge
t1_timer t1
t21_timer t21
t22_timer t22
t23_timer t23
t24_timer t24
t25_timer t25
t26_timer t26
t4_timer t4
zero_address zero_address

Default Values of Important Parameters

The default values of several important parameters have changed, the following table shows the differences between the AIX Version 3 Base X.25 support and the X.25 Licensed Program.

Default Values of Important Parameters
Parameter AIX Version 3 Base X.25 Defaults X.25"Licensed Program Defaults
Frame window size 7 7
Frame modulo 8 8
Packet Modulo 8 8
CCITT support 1980 1984
Default receive packet size 128 128
Default transmit packet size 128 128
Default receive packet window 2 3
Default transmit packet window 2 3
Default receive throughput class 9600 64000
Default transmit throughput class 9600 64000

[ Previous | Next | Contents | Search ]