 |
» |
|
|
|
You need to visit the next two screens only if you are configuring
a 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. Gateways that are on the same network are called neighbor
gateways. A non-gateway node on a LAN, Token Ring, FDDI,
100VG-AnyLAN, or 100Base-T 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 LAN, Token Ring,
FDDI, 100VG-AnyLAN or 100Base-T nodes that are on the same network
as a neighbor gateway need to know the identity of any neighbor
gateways. When you configure a LAN, Token Ring, FDDI, 100VG-AnyLAN,
or 100Base-T 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. You may designate gateways as default gateways. Messages for a network will be routed
to a default gateway if there is no gateway configured for the destination
network. The default gateway will then attempt to locate the destination
of the message. To Identify Neighbor Gateways (If Any Are Present) | |
The Neighbor Gateways screen (#152) in Figure 6-7 “Neighbor Gateways Screen” is displayed when you press the [Neighbor Gateways]
key at the selected configuration screen for the LAN, Token Ring,
FDDI, 100VG-AnyLAN, and 100Base-T via screen numbers 41, 49, 201,
296, and 306 respectively. Figure 6-7 Neighbor Gateways Screen
![[Neighbor Gateways Screen]](img/gfx30.gif)
In the Gateway name
field, enter the name of a gateway that is on the same
network as the node that you are configuring. (Nodes
are on the same network if the network portions of their IP addresses
are the same.). 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." 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 selected configuration screen (LAN, Token Ring, FDDI, 100VG-AnyLAN,
or 100Base-T) and proceed to Chapter 10 “Validating Network Transport and
Cross-Validating with SYSGEN”
Fields- Gateway name
Each gateway name can be as long as eight alphanumeric
characters. The first character must be alphabetic.
To Identify Neighbor Gateway Reachable Networks | |
The Neighbor Gateway Reachable Networks screen (#158) in Figure 6-8 “Neighbor Gateway Reachable Networks
Screen” is displayed when you
press the [Add] or [Modify] key
for a valid gateway name from the Neighbor Gateways screen (#152)
in Figure 6-7 “Neighbor Gateways Screen”. Figure 6-8 Neighbor Gateway Reachable Networks
Screen
![[Neighbor Gateway Reachable Networks Screen]](img/gfx31.gif)
In the Neighbor Gateway IP Internet Address
field, enter the IP address of the gateway specified on the Neighbor
Gateways screen. C 192.191.191 009
is a typical address. 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. If you want to designate this gateway as
a default gateway, enter an at sign (@)
in one of the fields as well. 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. 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. Repeat steps 2, 3, and 4 for each remote reachable network.
The information configured in this screen can extend
to more than one page, if necessary, to allow configuration of up
to 2550 reachable networks per link (255 pages and 10 reachable
nets per page). If you need to configure more than 10
networks, press the [Save Data] key then press
the [Next Page] key to enter more networks. After you have finished entering the IP addresses of
all the reachable networks, press the [Save Data]
key. Press the [Prior Screen] key to return to
the Neighbor Gateways screen. Back at the Neighbor Gateways screen, after you have
finished adding all of the neighboring gateways, press the [Prior Screen]
key to return to the selected configuration screen (LAN, Token Ring,
FDDI, 100VG-AnyLAN, or 100Base-T). Proceed to Chapter 10 “Validating Network Transport and
Cross-Validating with SYSGEN”
FieldsIf you have identified any neighbor gateways, 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. - Neighbor Gateway IP Internet Address
The IP address of the gateway whose name you have
specified on the Neighbor Gateways Screen. The IP address is in
the same format as the selected configuration screen (LAN, Token
Ring, FDDI, 100VG-AnyLAN, or 100Base-T).
- IP Network Address
In the fields under this heading, you list the IP
addresses of all of the networks that you will be able to reach
through the gateway you are configuring. You also use
this field to indicate whether or not the gateway is to serve as
a default gateway by entering an at sign (@)
to specify that it is a default gateway. Only one gateway can be
designated as a default gateway for each HP 3000 Series 900 system. - IP Mask (Optional)
The fields under this heading allow you to specify
a subnet mask for each reachable network. This mask is optional. - Hops
In the fields under this heading, enter the number
of hops corresponding to the number of gateways that a packet travels
to reach a remote network from a local network.
|
