 |
» |
|
|
|
The Network Directory Data screen (#10) shown in Figure 13-5 “Network Directory Data Screen” is displayed when you press the [Add] or [Modify] function key at the Network Directory Select Node Name
screen (Figure 13-4 “Network Directory Select Node Name
Screen”). The function of this screen is to configure path report data
for the node name listed at the top of the screen. One path report
is configured for each NI on a node. To delete a path report, clear all three path report fields
to blanks and press [Save Data]. Fields- Transport
services These three fields describe the transport services
that should be configured in each path. - TCP
TCP must be Y (yes) for all nodes. The default is Y. - Checksum
for TCP The checksum setting indicates whether checksumming
is optional (N) or required (Y) for TCP. If this field is set to N, then the use of checksums is not requested when
communicating with this node. If this field is set to Y then checksums are used when communicating with
this node. Checksumming is required for communication to non-HP
systems. The default is N. - PXP
PXP must be Y (yes) for all nodes. The default is Y.
Note that the selection of transport services here must match
the settings in the remote node's configuration file. If
the checksum enabled field in the path NETXPORT.GPROT.TCP of this node is set to Y, then TCP checksum field in the network directory
should also be set to Y.
- IP Address
One IP address should be entered for each network interface
configured on the remote node that is directly reachable from this
node. Each address must match an IP address configured in the remote
node's configuration file. The path of the screen in the configuration
file that contains IP addresses is NETXPORT.NI.NIname.PROTOCOL.IP. - Type
A number indicating the type of path to configure
is shown in Table 13-1 “Path Type Configuration”: - 1
Select this path type when the NI type is ROUTER (point-to-point); or when the NI type is LAN and the destination node supports probe or ARP;
or when the NI type is TOKEN or FDDI and the destination node supports ARP. - 2
Select this path type when the NI type is LAN, the destination node does not support probe,
and 802.3 framing is used. - 3
Select this path type when the NI type is X25. - 4
Select this path type when the NI type is LAN, the destination node does not support ARP, and
Ethernet framing is to be used. - 5
Select this path type when the NI type is TOKEN and the destination node does not support ARP. - 6
Select this path type when the NI type is FDDI and the destination node does not support ARP.
Table 13-1 Path Type Configuration | NI Type | Framing | Protocols Supported by Remote Node | Type |
|---|
| Point-to-Point (Router) | N/A | N/A | 1 | | LAN, VG100LAN, BT100 | 802.3 and Ethernet | Either Probe or ARP | 1 | | Neither Probe nor ARP | 4 | | 802.3 only | Not Probe | 2 | | Ethernet only | Not ARP | 4 | | X.25 | N/A | N/A | 3 | | Token Ring | N/A | ARP | 1 | | N/A | Not ARP | 5 | | FDDI | N/A | ARP | 1 | | N/A | Not ARP | 6 |
- Additional address
A lower-level address, which depends on the type. Type 1 does not contain lower-level
addressing information. You can leave the field blank, or enter
the keyword NONE. Types 2, 4, 5 and 6 require the destination node's station
address, which is a string of six hexadecimal bytes, separated by
dashes (XX-XX-XX-XX-XX-XX). Type 3 requires an X.25 address key, which is an ASCII string
of as many as eight characters. Each NETXPORT.NI.NIname.X25.SVCPATH screen may contain up to 2048 X.25 address keys.
Each NETPORT.NI.NIname.X25.PVCPATH screen may contain up to 128 X.25 address keys.
No address key may be used more than once per system.
|
Printable version
