 |
» |
|
|
|
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: 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.
Facilities | |
Following are the supported facilities of the DTC/X.25 XL
Network Link. | Supported Facilities | 1984 CCITT X.25 Reference |
|---|
| Extended packet sequence number | 6.2 | | Incoming calls barred | 6.5 | | Outgoing calls barred | 6.6 | | Nonstandard default packet size | 6.9 | | Nonstandard default window size | 6.10 | | Flow control parameter negotiation | 6.12 | | Throughput class negotiation | 6.13 | | Closed user group selection (1980 CCITT) | 6.14 | | Fast select request and acceptance | 6.16-17 | | Reverse charging and acceptance | 6.18-19 | | Local charging prevention | 6.20 | | Hunt group | 6.25 | | Supported Facilities
with X.25 Level 3 Programmatic Access | | Closed user group related facilities | 6.14 | | Bilateral closed user groups | 6.15 | | Network user identification | 6.21 | | Called line modified address notification | 6.26 | | Call redirection and notification | 6.25-27 | | Transit delay selection and indication | 6.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. |
