User Manual

ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup
Page 3-18
 2005, ADC Telecommunications, Inc.
8.2 Bracketing of Lost RANs
When a RAN CPU is removed from the network, or if tenant processing is unable to
communicate with one of its RANs, then that RAN ID in the Hostname table is bracketed. For
example hostname would be reported as [hostname]. In addition, the RAN ID in the Address
table is also reported in a different fashion when a RAN is "lost". The IP address is bracketed,
with the IP address string being replaced by another form of the number. For example,
172.20.1.248 could be replaced by [1921681.248]. The point is that if the IP address reported
in the Address table is not a valid combination of 4 octet values with decimal points separating
the octets, then that RAN should be considered not present.
8.3 Clearing of RAN’s
In order to facilitate swap outs of RAN CPUs, it is possible for the RAN Hostname values in
the Hostname table of the Tenant OAM MIB to be cleared by deleting the hostname from the
MIB table. Doing so will allow that RAN ID to be cleared, and will allow the next RAN CPU
discovered to occupy that RAN ID.
9 HUB NODE ACCESS/MANAGEMENT
9.1 Managing Hub Nodes
The Hub in a Digivance CXD network consists of several racks and chassis, which translate to
several CPUs per HUB. Since these CPUs all reside at a single geographical location, it is
necessary to establish a relationship of each CPU to its rack and chassis location such that field
service personnel can be deployed to the correct location within the Hub when the need arises.
There can be many CPUs at a single Hub Site within the many racks and chassis, but there is
no way to correlate an IP address to its physical rack/chassis location automatically. Therefore,
a convention for identifying racks and chassis needs to be established. At installation time,
each hostname, as written on the front tag of each CPU, must be recorded in conjunction with
its physical location. This information is used when the operator fills in the Hub Node MIB,
which is discussed in detail below. Digivance CXD Hub naming conventions are also
discussed below.
The Hub Node MIB correlates Hub node IP addresses with their hostnames and physical
locations. It resides solely at Hubmaster nodes. Refer to Section 11.1 for details.
9.2 Identification using the Network IP Receiver/Sender (NIPR/S)
The Digivance CXD Hubmaster node dynamically keeps track of which nodes are under its
control using a script called NIPR/S (Network IP Receiver/Sender). It receives an IP and
hostname from each element in the subnet it controls via the client functionality of NIPR/S,
which runs on all “slave” nodes. NIPR/S senses any changes to its list of slave nodes, and
updates the Hubmaster DNS accordingly. The NIPR/S script is also a key component to
maintaining the HUB/RAN Node MIBs and, ultimately, tenant processing as a whole, since it
is the mechanism by which the HUB/RAN Node MIB entries are filled.