IP Address Allocation
5-8
8000-A2-GB21-30
April 1998
Management IP Address Allocation
The primary functionality of the management domain is monitoring and
configuring the network. To provide this capability, IP addresses must be
allocated for the components that are monitored and configured by an NMS and
MCC card.
Component
IP Address Requirement
MCC Card The MCC card must have two IP addresses:
H One IP address for connectivity to the NMS or Router
(connecting to the NMS). This address is also known as
the Router ID.
H One IP address to communicate to the DSL cards (over
the s1b system backplane interface) in the Hotwire
DSLAM chassis.
These two IP addresses must be on separate
subnetworks of the NMS domain. That is, they can be on:
H Completely separate networks (e.g., 135.1.0.0/16 and
143.1.0.0/24),
H Completely separate subnets (e.g., 135.1.1.0/24 and
135.1.2.0/24), or
H Subnets of the management domain (e.g., 135.1.0.0/16
and 135.1.2.0/24).
DSL Card Each DSL card must have one management IP address in
the same subnetwork as the MCC card’s system
backplane IP address.
NOTE: The backplane subnet cannot be set to the
same e1a subnet on that DSL card.
Hotwire 5446 RTU Each 5446 RTU must have one management IP address
in the same subnetwork as the MCC card’s system
backplane IP address.
NOTE: Since there could be four Hotwire 5446 RTUs
per DSL card and 18 DSL cards per Hotwire
DSLAM, a maximally configured system
would have 72 Hotwire 5446 RTU
management IP addresses. These must be in
the same subnetwork as the MCC card’s
system backplane interface and the 18 DSL
cards’ management IP addresses (total of
91 addresses).
Hotwire 5546 RTU The IP address of the router interface connected to the
5546 RTU should reside in the same subnet as the MCC
card’s backplane.
NOTE:
Management functions of RTUs associated with an 8540 DSL card are
performed by an internal agent on the 8540 DSL card. Management functions
of the 5546 RTU are performed by an internal agent on the 8546 DSL card.
