HP e3000/iX Network Planning and Configuration Guide (36922-90037)

226 AppendixD
NS X.25 Migration: NS 3000/V and NS 3000/XL Release 1.X to iX Release 2.0 or later
Differences in X.25 Support
Differences in X.25 Support
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 vs. 1984 CCITT
NS 3000/V supports CCITT 1980 and NS 3000/XL 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.
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 NS3 000/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.