Manualshelf

User Manual

ManualsBrandsADC Telecommunications ManualsElectronicsDigivance CXD 800 MHz A and B Band System
71727374757677787980
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup
Page 3-3
2005, ADC Telecommunications, Inc.
A CPU called the Hubmaster is a special Hub node that controls tenant processing for
Digivance CXD nodes on its subnet. For a definition of tenant sectors, see Section 6.1. The
Hubmaster also functions as a time server for a Digivance CXD subnet (using Network Timing
Protocol), and can be set up to provide DHCP (Dynamic Host Configuration Protocol) and
DNS (Domain Name Service) to its subnet as well. It is important for Digivance CXD system
software that only one Hubmaster node resides on each subnet, and that each subnet has a
unique domain name. The Hubmaster node is the only node that requires a static IP. The
Digivance CXD network architecture utilizes DHCP and DNS to identify the rest of the nodes,
either through pre-existing LAN servers, or through the Digivance CXD Hubmaster CPU. For
more on configuring these features and the Hubmaster itself, see Section 10, "Configuring the
Hubmaster node.
3 NODE IDENTIFICATION SCHEMES
It is important to follow a convention when naming nodes in the Digivance CXD system so that
CPUs can be quickly located and accessed for troubleshooting and maintenance. The suggested
naming conventions for both Hub and RAN nodes are discussed in the following sections. For
more information concerning node identity configuration, see Sections 11.1 and 11.2.
4 IDENTIFICATION USING THE NETWORK IP RECEIVER/SENDER SYSTEM
The Digivance CXD Hubmaster node dynamically keeps track of which nodes are under its
control using a script called NIPR (Network IP Receiver). It receives an IP and hostname from
every node it controls via NIPS (Network IP Sender), which runs on all “slave” nodes. NIPR
senses any changes to its list of slave nodes, and updates the Hubmaster DNS accordingly. The
NIPR/S system is also a key component to maintaining the Hub/RAN Node MIB’s and tenant
processing, since it is the mechanism by which the Hub/RAN Node MIB entries are filled. For
more on these MIB’s, see Sections 11.1 and 11.2.
5 HUB EQUIPMENT IDENTIFICATIONS
Table 3-1 shows the recommended convention to be used for identifying and placing Hub
equipment: