Manualshelf

User Manual

ManualsBrandsADC Telecommunications ManualsElectronicsDigivance CXD 800 MHz A and B Band System
919293949596979899100
ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup
Page 3-24
2005, ADC Telecommunications, Inc.
10.2.5 Incorporating Existing LAN DNS
The method of incorporating an existing LAN DNS begins with configuring the Hubmaster
DNS forwarding as outlined in Section 10.1.5 and continues with some maintenance at the
upstream DNS. At a minimum, the upstream DNS needs to be updated with each Hubmaster
node’s IP address and full hostname (including its domain). Ideally, this maintenance would be
automated, and the RAN nodes would also be maintained in the upstream DNS.
Implementations of this are as varied as the networks being maintained, and may need to be
custom designed by a network administrator.
11 CONFIGURING THE HUB “SLAVE” AND RAN NODES
The Digivance CXD system takes care of networking setup for the Hub “Slave” and RAN
nodes Non network setup is shown on the following sections.
11.1 Managing The Hub Node MIB
This MIB correlates Hub node IP addresses with their hostnames and physical locations. It
resides solely at Hubmaster nodes. It is comprised of the following elements:
11.1.1 Site ID
transceptHubNodeTable.transceptHubNodeSiteID
The Site ID designates the physical location of the CXD Hub. Often, wireless operators
already have site IDs laid out for their markets and BTS installations, such as “Memphis203”
or “Cell29PA”, and these designators work well for pinpointing the location of the CXD Hub.
GPS coordinates or road names also work well. The Site ID can be up to 64 characters long.
11.1.2 CPU Rack ID
transceptHubNodeTable.transceptHubNodeCPURackID
Hub Racks must be given unique identifiers using the CPU Rack ID field. This can be as
simple as numbering Hub Racks from 1...N, numbering them based on their serial number, or
coming up with some other naming convention. Once a plan is adopted, it is highly
recommended that the racks be labeled accordingly at installation. The CPU Rack ID is limited
to 15 characters.
11.1.3 CPU Chassis ID
transceptHubNodeTable.transceptHubNodeCPUChassisID
Any chassis in a rack needs to be uniquely identifiable by using the CPU Chassis ID field. The
convention is to number the chassis based on the highest U-number they occupy in the rack.
The CPU Chassis ID can be comprised of up to 15 characters.