HP 3000 Manuals HP 3000 Manuals
To Configure Path Report Data for a Node The Network Directory Data screen (#10) in figure 11-5 is displayed when you press the [Add] or the [Modify] function key at the Select Node Name screen (#9) in figure 11-4.Figure 11-5. Network Directory Data 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. Because the maximum number of NIs per node is eleven (twelve including loopback), each node can contain as many as eleven path reports.
NOTE NS/SNA is no longer offered as a product and has been removed from the Corporate Price List. The product is obsolete with no plans for support.
Steps 1. Verify that the yes and no indicators in the TCP, Checksum for TCP required, and PXP fields are set correctly. 2. In the IP address field, type in the IP address of the node listed in the Node name field. 3. In the type field, enter the number that indicates the type of the path (1 = IP, 2 = LAN/IEEE802.3, 3 = X.25, 5 = LAN/Ethernet, 6 = Token Ring, or 7 = FDDI.) 4. If appropriate for the type of path you are configuring, enter an address in the Additional Address field. (Type 1 requires no additional address. Types 2, 5, and 6 require a station address. Type 3 requires an X.25 address key. Type 4 requires an LU name.) See additional explanation under "Fields". 5. Press the [Save Data] key. 6. Repeat steps 2, 3, and 4 for each path report for the specified node. If you need to make additional entries in the network directory, press the [Prior Screen] key to return to the Network Directory Select Node Name screen. If you have finished making network directory entries, home the cursor and type EXIT in the command field, then press [ENTER]. 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: 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 NS/SNA is no longer offered as a product and has been removed from the Corporate Price List. 5 Select this path type when the NI type is LAN, the destination node does not support ARP or probe, and Ethernet framing is to be used. 6 Select this path type when the NI type is TOKEN and the destination node does not support ARP. 7 Select this path type when the NI type is FDDI and the destination node does not support ARP. Table 11-1. Path Type Configuration ------------------------------------------------------------------------------------------- | | | NI Type Framing Protocols Type | | | ------------------------------------------------------------------------------------------- | | | | | Point-to-Point N/A N/A 1 | | (Router) | | | - - | LAN 802.3 and Ethernet Either Probe or ARP 1 | | | | 802.3 and Ethernet Neither Probe nor ARP 5 | | | | 802.3 only Not Probe 2 | | | | Ethernet only Not ARP 5 | | | - - | X.25 N/A N/A 3 | | | - - | NS/SNA N/A N/A 4 | | | - - | Token Ring N/A ARP 1 | | | | N/A Not ARP 6 | | | - - | FDDI N/A ARP 1 | | | | N/A Not ARP 7 | | | ------------------------------------------------------------------------------------------- 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, 5, 6, and 7 require the destination node's station address, which is a string of six hexadecimal bytes, separated by dashes (XX-XX-XX-XX-XX-XX). The station address must correspond to the address configured on the remote node. Type 3 requires an X.25 address key, which is an ASCII string of up to 15 characters. The X.25 address key must correspond to an X.25 address key entered in the NETXPORT.NI.NIname.PROTOCOL.X25.SVPATH or the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH screen for the destination node. Type 4 requires the destination node's LU name. The LU name is taken from the host generation file of the IBM computer to which this HP 3000 is connected.
![[]](../../pic3k/M013399/FFN473c50.gif)