Configure Neighbor Gateways [ Configuring and Managing Host-Based X.25 Links ] MPE/iX 5.0 Documentation
Configuring and Managing Host-Based X.25 Links
Configure Neighbor Gateways
You need to visit the next two screens only if you are configuringa
non-gateway node that is on the same network as a gateway. In this case,
the non-gateway node needs to know the identity of any neighbor gateway.
Neighbor gateways can be either full or half gateways. (Go back one
level by pressing the [Prior Screen] key, then select [Neighbor Gateways]
key).
Gateways
that are on the same network are called neighbor gateways. A non-gateway
node on an X.25 network may need to go through a neighbor gateway in
order to send messages to an entirely different network. (Two nodes are
on the same network if the network portion of their IP addresses are the
same.) All X.25 nodes that are on the same network as a neighbor gateway
need to know the identity of any neighbor gateways. When you configure
an X.25 node, you enter into its configuration the identity of any
accessible neighbor gateways that share the same network. The identified
gateways may be either full or half gateways.
Idendify Neighbor Gateways (If Any Are Present)
NMMGR displays the Neighbor Gatewaysscreen (see Figure 6-7 )
when you press the [Neighbor Gateways] key at the X.25 Configuration
screen.
Figure 6-7. Neighbor Gateways Screen
1. In the Gateway name field, enter the nameof a gateway that is on
the same network as the node that you are configuring.
2. If you are adding the identified gateway for the first time, press
the [Add] key. If you are modifying the configuration of this
node, press the [Modify] key. The Neighbor Gateway Reachable
Networks screen will be displayed. Proceed to "Identify Neighbor
Gateway Reachable Networks."
3. Repeat steps 1 and 2 for each gateway that is on the same network
as the node that you are configuring. When you have finished,
press the [Next Screen] key to return to the X.25 Configuration
screen.
Fields
Gateway name Each gateway namecan be as long as eight
alphanumeric characters. The first character must
be alphabetic.
Identify Neighbor Gateway Reachable Networks
NMMGR displays the Neighbor GatewayReachable Networks screen(see Figure
6-8 ) when you press the [Add] key or the [Modify] key for a valid
gateway name from the Neighbor Gatewaysscreen.
Figure 6-8. Neighbor Gateways Reachable Networks
1. In the Neighbor Gateway IP Internetwork Address field, enter the
IP address of the gateway specified on the NeighborGateways
screen. An example is:
C 192.007.007 001
2. In the IP Network Address fields
under the title Configured Reachable Networks, enter the IP
addresses of all the remote networks that can be reached through
the gateway whose IP address is configured in the previous field.
3. The IP subnet mask is optional. If entering one, tab to the next
field. In the IP subnet mask
field, enter the number in the same format as an IP address. For
details on deriving an IP subnet mask, refer to the HP 3000/iX
Network Planning and Configuration Guide (36922-61023).
4. In the field labeled
Hops, enter the number of hops (full gateways) needed to get to
the target network. Two partner gateway halves count as one hop.
5. Repeat steps 2, 3, and 4 for each remote reachable network. If
you need to configure more than 10 networks, press the [Save Data]
key then press the [Next Page] key to enter more networks.
6. After you have finished entering the IP addresses of all the
reachable networks, press the [Save Data] key. Press the [Next
Screen] key to return to the Neighbor Gateways screen.
7. Back at the Neighbor Gateways screen, after you have finished
adding all of the neighboring gateways, press the [Next Screen]
key to return to the X.25 Configuration screen. Follow
instruction 7 in the section in this chapter called "Step 6:
Configure X.25 Network."
Fields
If you have identified any neighborgateways, then you will also be
identifying: 1) the IP Network Addresses of all of the networks that you
can reach through that gateway, and 2) the number of hops (corresponding
to the number of gateways) that a packet passes through to reach a remote
network from the local network. Two gateway halves count as one hop.
MPE/iX 5.0 Documentation