User`s guide
Packet Walk-Throughs
9-3
8000-A2-GB21-10
June 1997
7. The DSL card then forwards the packet over the DSL port to that RTU.
8. Upon receiving the packet, the RTU forwards the packet to its 10BaseT port
because it has a host route for ES1.
Management Packet Walk-Through
To examine how data packets flow through the management domain, an example
of the DCE Manager workstation 1 (WS1) performing a ping to the HotWire 5446
RTU will be used. The following is assumed:
A host route to the RTU (135.1.3.4) exists on the MCC card. (This is
generated automatically.)
A static route to WS1 (135.1.1.1) is configured on the DSL card.
In the following illustration, WS1 is connected to the same LAN as the NMS.
97-15479-01
Router
135.1.1.2
135.1.2.1
135.1.3.254
DCE
Manager
WS1
135.1.1.1
MCC Card
e1a:135.1.2.2
RTU
135.1.3.4
DSL Card
s1b:135.1.3.2
Unnumbered
Interface
s1b:135.1.3.1
1) 135.1.3.4
2) 0.0.0.0
135.1.3.2
135.1.2.1
Host/Net/Subnet Subnet Mask
255.255.255.255
0.0.0.0
Next-Hop Address S/D (Source/Destination)
dst (destination)
dst (destination)
MCC Routing Table
1) 135.1.2.0
2) 135.1.1.0
135.1.3.1
135.1.3.1
Host/Net/Subnet Subnet Mask
255.255.255.0
255.255.255.0
Next-Hop Address S/D (Source/Destination)
dst (destination)
dst (destination)
Partial DSL Routing Table
RTU issues reply to ping
WS1 pings the RTU
12345
1 2 3 4 5 6 7 8