Specifications

Reference Guide 4-27
CPU Card IP Packet Routing
•
If a match is not found for the packet, it is routed to the interface specified in the DEF
DEST field. If the default destination matches the interface the packet arrived from, the
packet is dropped.
Figure 4-10 shows a typical routing arrangement. Although 24 units are used in this example,
the number of remote units is unlimited except for bandwidth and link-down considerations.
Figure 4-10. Typical Routing Diagram
In Figure 4-10, 24 system units transmit alarm information to an IP routing system unit
(System 25) via the optional paths of separate WAN links. The network administrator assigns
IP addresses for each system on the TCP/IP screen of each system’s Interface card (PORT IP
ADDR). System 20 is connected by any of the optional paths to System 25, which supports
NMS equipment (the communications server) with either a local SLIP connection directly
from the CPU card or any optional path of a T1 or E1 WAN link. In this example, all alarms
received by any of the system units will be forwarded to system 25 over a single WAN link.
Each of the 24 reporting units use System 25's IP address as the RPT1 IP ADDR on the TCP/IP
screen of its interface card. First, routing is initiated by the
off/on
command for each sub-unit.
The local port is included to be able to transmit the IP packets generated by the routing unit to
the same destination. In most cases, the DEF DEST of all units controlled by this router will
be the same place (either the local port or optional WAN paths to a distant location).
#1
#2 #3
#4
#5
#6 #7
#8
#9
#10 #11
#12
#13
#14 #15
#16
#17
#18 #19
#20
#21
#22
#24
#23
#25 NMS