User Manual

ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup
Page 3-16
 2005, ADC Telecommunications, Inc.
7.15 Enabling / Disabling RAN slots
transceptTenantOAMTable.transceptTenantRanDisableX, where X = 1-8
The RAN paths belonging to a tenant can be disabled using the RAN Enable/Disable
parameters of the Tenant OAM MIB. Doing so will disable the PA in the RAN. These MIB
fields are enumerated types with values "Enabled" = 0, and "Disabled" = 1. The reason for the
inverse boolean logic is so that the desired default values are set to be zero, which is the MIB
default value. For example:
To disable RAN 3 in a simulcast, set transceptTenantOAMTable.transceptTenantRANDisable3
to a “1” (disabled).
7.16 FSC Attenuator Offsets
transceptTenantCalTable.transceptTenantFscAttenX
If not using Composite Mode, there is a step during Forward RF Path Balancing that requires
that the FSC Digital path attenuators be adjusted. These adjustments need to be made in the
Tenant OAM MIB in the FSC Attenuator Offset fields, of which there is one per channel in the
Tenant OAM MIB with the naming convention. The values that are set in the Tenant OAM
MIB will be pushed down to the appropriate FSC MIB Attenuator fields. Doing these settings
in the Tenant OAM MIB will allow consistency with the maintenance of configuration data.
7.17 Target Simulcast Degree
In order for the Digivance CXD software to determine the correct number of tenant paths
throughout the system, it can be provided with the target simulcast degree. This will allow the
Tenant process to properly determine and report missing boards and path conditions and
quantities. The Tenant Simulcast Degree field in the Tenant OAM MIB is used to configure
this parameter. This MIB parameter accepts values ranging from 1-8, the range of simulcasting
supported in Digivance CXD on a per sector basis.
7.18 Module Attenuators
In order to be consistent with all other configuration parameters in the system, and to ensure
that configuration data is properly managed, the Tenant OAM MIB contains several
parameters to allow the configuration of tenant module attenuators. When configured in the
Tenant OAM MIB, tenant processing will push these attenuators offsets to the appropriate
HCP MIB. It is important to note that it is not always desirable to modify HCP attenuators, and
should only be done per operating instructions (see Path Balancing, Section 4, Subsection 2). It
is also important to note that the attenuator offset values configured in the Tenant OAM MIB
will supercede (and therefore overwrite) those configured in the HCP MIBs. The following is
the list of all supported tenant attenuators in the Tenant OAM MIB:
• TransceptTenantGenTwoTable.transceptTenantRucYAttenOffset - Y = RAN 1-8.
• TransceptTenantGenTwoTable.transceptTenantRdcYAttenOffsetPrimary - Y = RAN
1-8.