Table of Contents
Advertisement
MCC Card Proxy ARP
8000-A2-GB21-20
DSL Card 1
RTU
RTU
RTU
NOTE:
It is not recommended that the DCE Manager access a DSL card via its
Ethernet port because the Entity MIB on the DSL card does not reflect a view
of the entire HotWire DSLAM system. It reflects only the view of the DSL card
discovered . Also, in a fully configured DSLAM, 18 additional devices will be
discovered and appear on your network map.
If you want to manage DSL devices across the NSP network, use telnet. For
more information on telnet see Chapter 8, Diagnostics and Troubleshooting ,
of the HotWire DSLAM for 8540 and 8546 DSL Cards User's Guide .
Proxy ARP is also supported by the MCC card. In a HotWire DSLAM network
configuration, when an ARP request is sent by a device (such as a router) to the
MCC card's 10BaseT interface to resolve either the DSL card or HotWire 5446
RTU MAC address, the MCC card will proxy ARP for those devices so long as
their IP addresses are on the same network (135.1.3.n) as the backplane
interface of the MCC card. The MCC card responds to these ARP requests with
its own MAC address (proxy ARP). Incoming packets are then forwarded to that
appropriate DSL card across the HotWire DSLAM system backplane.
NOTE:
Management functions of RTUs associated with an 8540 DSL card are
performed by an internal agent on the 8540 DSL card.
November 1997
Components of the Network Model
MCC Card
DSL Card 2
RTU
RTU
RTU
97-15492
4-7
Advertisement
Table of Contents
