HPlogo HP e3000/iX Network Planning and Configuration Guide > Appendix B NS X.25 Migration: NS 3000/V to NS 3000/iX

Differences in X.25 Support

MPE documents

Complete PDF
Table of Contents
Index

There are differences in X.25 support between NS 3000/V and NS 3000/iX which need to be considered when you migrate as described in the following paragraphs.

1980 Versus 1984 CCITT


NS 3000/V supports CCITT 1980 and NS 3000/iX supports both 1980 and 1984.

General Level 3 Differences


In MPE V X.25, a Reset is sent to initialize or clear a Permanent Virtual Circuit. In MPE/iX X.25, a Reset is not sent to initialize or clear a Permanent Virtual Circuit.

MPE V X.25 has a timeout on an interrupt collision. MPE/iX X.25 does not.

Level 3 Access with NetIPC


In addition to the X.25 features supported on NS 3000/V, NetIPC 3000/XL provides the following CCITT 1984 features:
  • Fast select facility.

  • The capability of modifying and reading the facility field in call packets.

  • A new option in IPCDEST (called the destination network address option) allows you to directly specify an X.25 address or PVC number instead of a remote node name. See the NetIPC 3000/XL Programmers Reference Manual for more information. If using this feature, you can configure POOL as an X.25 Address Key with its security option set to "O" (outbound) in the X.25 SVC Address Key Paths screen to allow outbound calls to any destination address.

  • IPCCONTROL request 12, reason for error or event, on NS 3000/V can return 14 (network shutdown), 15 (restart sent by local network), 16 (level 2 failure), 17 (restart sent by local protocol module), and 18 (restart packet received). IPCCONTROL on NS 3000/XL only returns 10 (Clear), 11 (Reset), or 12 (Interrupt).

  • In NS 3000/V, IPCSHUTDOWN does not complete until a clear confirmation arrives. In NS 3000/XL, IPCSHUTDOWN completes immediately.

  • In NS 3000/V, IPCCREATE requires that the network name be padded with nulls. In NS 3000/XL, IPCCREATE requires the network name be padded with blanks.

Facilities


The supported facilities of the DTC/X.25 XL Network Link are shown in Table B-1 "Supported Facilities".

Table B-1 Supported Facilities

Supported Facilities 1984 CCITT X.25 Reference
Extended packet sequence number6.2
Incoming calls barred6.5
Outgoing calls barred6.6
Nonstandard default packet size6.9
Nonstandard default window size6.10
Flow control parameter negotiation6.12
Throughput class negotiation6.13
Closed user group selection (1980 CCITT)6.14
Fast select request and acceptance6.16-17
Reverse charging and acceptance6.18-19
Local charging prevention6.20
Hunt group6.25
Supported Facilities with X.25 Level 3 Programmatic Access
Closed user group related facilities6.14
Bilateral closed user groups6.15
Network user identification6.21
Called line modified address notification6.26
Call redirection and notification6.25-27
Transit delay selection and indication6.28

Security


When configuring a host, you can now set security for each remote system using the Security field on the X.25 SVC Address Key Paths screen. System to System Local User Groups (LUGs) are now assigned on the DTC instead of on the host. The LUG provides security in the same way a CUG does, but you don't have to subscribe to a CUG.

Pad Support


For complete information on migrating PAD support from NS 3000/V to NS 3000/iX Release 2.0 or later, refer to Appendix C "NS X.25 Migration: NS 3000/V PAD Access to NS 3000/iX"




Differences Between NS 3000/V and NS 3000/iX


Converting NS 3000/V Configuration Files to NS 3000/iX