Alcatel-Lucent 9500 MXC User Manual page 840

Complex Networks
Vol. VI-D-14
Figure D-6 on page D-15 shows a more complex network of 9500 MXC and
other radio terminals. In this example it has been assumed that the other terminals
are static routed and that the 9500 MXC nodes are to be similarly configured.
Figure D-7 shows the CT static routing screen for Node A. Note that Node A and
Terminal X share the same network address of 192.169.1.0 (on the same LAN),
therefore only one network address is required for these two devices in the static
routing tables in the other nodes/terminals. The same situation applies to Node C
and Terminal U.
Figure D-8 on page D-17 shows the same network, but with the 9500 MXC
portion of the network configured for dynamic routing. This is achieved by
partitioning the 9500 MXC nodes at the junctions with the other terminals in the
network (Nodes A and C), such that each port in use on these two nodes is
numbered (given an IP address) using the interface addressing option, and each
port has its own routing option (static or dynamic).
On the radio side of the 9500 MXC network (LINK NMS), dynamic routing
(RIP2 or OSPF) is selected in the CT Interface Addressing screen. On the
Ethernet side, static routing is entered for the Ethernet port in the Static Routing
screen.
Of specific interest is the addressing for the LINK NMS ports at Nodes A and C.
Given that the radio path for NMS is handled as a PPP link, no real IP addressing
is required on these ports. However, to maintain good routing practice it is
recommended that LINK NMS ports are addressed such that they are shown to
assume the address of the router, the Ethernet port, by entering an IP address of
0.0.0.0 and a subnet mask of 255.255.255.255. Unique IP addresses could have
been used but they would serve no purpose except where the operator wishes to
treat the radio path as a separately identifiable network within the routing tables.
Unique IP addressing may have application in some larger networks where an
operator wishes to number the radio path as a routed network to conform with a
numbering plan used throughout their network. However, for static routed
networks, doing so would require these interfaces to also be entered in the static
route tables for all network devices.
For consistency, the V.24 port has also been set to assume the same IP address.
Changing the IP address of the V.24 port in the Interface Addressing screen does not affect
the default access for V.24 connection of CT.
Figure D-9 on page D-18 shows the Interface IP Addressing screen for Node A in
Figure D-8 on page D-17. Figure D-10 on page D-18 shows the Static Routing
screen for the same node.
Alcatel-Lucent