Professional Documents
Culture Documents
GCP 8000 Site Controller PDF
GCP 8000 Site Controller PDF
GCP 8000 Site Controller PDF
*6871008P67* 6871008P67-A
2007 Motorola, Inc. All rights reserved. December 2007
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countries
preserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained in
the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the
copyrights, patents or patent applications of Motorola, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale
of a product.
Disclaimer
Please note that certain features, facilities and capabilities described in this document may not be applicable to or licensed for use on a particular system, or
may be dependent upon the characteristics of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola contact
for further information.
Trademarks
Motorola, the Motorola logo, and all other trademarks identified as such herein are trademarks of Motorola, Inc. All other product or service names are the
property of their respective owners.
Copyrights
2007 Motorola, Inc. All rights reserved.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by
any means, without the prior written permission of Motorola, Inc.
European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive
The European Unions WEEE directive requires that products sold into EU countries must have the crossed out trashbin label on the product (or the package
in some cases).
As defined by the WEEE directive, this cross-out trashbin label means that customers and end-users in EU countries should not dispose of electronic and
electrical equipment or accessories in household waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or service centre for information about the waste collection
system in their country.
Document
History
Document History
Contents
List of Figures
Figure 9-4: GCP 8000 Site Controller showing connections to backplane through backplane cover . . . 9-10
Figure 9-5: Fan Cable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Figure 9-6: Expansion Hub FRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Figure 10-1: GCP 8000 Software and Services-Controlled LEDs . . . . . . . . . . . . . . . . . . . 10-2
Figure 10-2: Expansion Hub LEDs Photo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Figure 10-3: Lightning Arrestor System Connections . . . . . . . . . . . . . . . . . . . . . . . 10-9
Figure 10-4: GPS Lightning Arrestor Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
List of Tables
Table 1-1: GCP 8000 Hardware Congurations and the Systems Supported . . . . . . . . . . . . . . 1-4
Table 1-2: GCP 8000 Site Controller Technical and Environmental Specications . . . . . . . . . . . 1-10
Table 1-3: Expansion Hub Technical and Environmental Specications . . . . . . . . . . . . . . . . 1-12
Table 2-1: Time Synchronization and Frequency Reference Table for Different Site Controller
Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Table 2-2: Description of Ports on the GCP 8000 Site Controller (Front View) . . . . . . . . . . . . . 2-7
Table 2-3: Description of Ports on the GCP 8000 Site Controller (Rear View) . . . . . . . . . . . . . 2-8
Table 2-4: GCP 8000 Site Controller Port Default Speed/Duplex Settings . . . . . . . . . . . . . . . 2-10
Table 2-5: X-Hub Port Default Speed/Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Table 2-6: GCP 8000 ON/OFF Switch States for Power Supply and Battery Charger . . . . . . . . . 2-16
Table 2-7: GCP 8000 Power Supply Module Backplane Connections . . . . . . . . . . . . . . . . . 2-17
Table 2-8: Ports on the Expansion Hub (Front View) GTR 8000 Expandable Site Subsystem . . . . . 2-21
Table 3-1: GCP 8000 Site Controller Hardware Congurations and Systems Supported . . . . . . . . 3-8
Table 3-2: GCP 8000 Site Controller Connections (Front View) Standalone Conguration . . . . . . 3-11
Table 3-3: GCP 8000 Site Controller Connections (Rear View) Standalone Conguration. . . . . . . 3-13
Table 3-4: Expansion Hub Connections (Front View) . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Table 3-5: Standalone GCP 8000 Site Controller Input Power Wiring . . . . . . . . . . . . . . . . . 3-22
Table 8-1: GCP 8000 Site Controller General Troubleshooting . . . . . . . . . . . . . . . . . . . 8-1
Table 8-2: Alarm Severity Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Table 8-3: GCP 8000 Site Controller Objects in FullVision INM . . . . . . . . . . . . . . . . . . . 8-5
Table 8-4: FullVision INM State/Cause Alarms GCP 8000 HPD Site Controller . . . . . . . . . . . 8-6
Table 8-5: FullVision INM Transient Alarms GCP 8000 HPD Site Controller . . . . . . . . . . . . 8-9
Table 8-6: FullVision INM State/Cause Alarms GCP 8000 GCP 8000 Site Controller . . . . . . . . 8-10
Table 8-7: FullVision INM State/Cause Alarms Repeater Site Subsystem Site Controller . . . . . . . 8-11
Table 8-8: FullVision INM Transient Alarms Repeater Site Subsystem Site Controller . . . . . . . . 8-14
Table 8-9: FullVision INM State/Cause Alarms Simulcast Site Subsystem Site Controller . . . . . . 8-16
Table 8-10: FullVision INM Transient Alarms Simulcast Site Subsystem Site Controller . . . . . . . 8-17
Table 8-11: GCP 8000 Site Controller Diagnostic Options . . . . . . . . . . . . . . . . . . . . . . 8-20
Table 9-1: GCP 8000 Site Controller Field Replaceable Units . . . . . . . . . . . . . . . . . . . . 9-2
Table 9-2: Standalone GCP 8000 Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Table 9-3: Expansion Hub Field Replaceable Unit . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Table 10-1: GCP 8000 Site Controller Reference Matrix . . . . . . . . . . . . . . . . . . . . . . . 10-1
Table 10-2: GCP 8000 Site Controller Software-Controlled LEDs . . . . . . . . . . . . . . . . . . 10-3
Table 10-3: Services-Controlled LEDs for GCP 8000 Site Controller . . . . . . . . . . . . . . . . . 10-3
Table 10-4: Status LED Assignment for GCP 8000 Site Controller . . . . . . . . . . . . . . . . . . 10-4
Table 10-5: Status Denitions for the GCP 8000 Site Controller Status/Alarm LEDs . . . . . . . . . . 10-4
Table 10-6: GCP 8000 Site Controller Active/Inactive Status LEDs . . . . . . . . . . . . . . . . . . 10-5
Table 10-7: GCP 8000 Site Controller Switch or Active/Inactive LEDs . . . . . . . . . . . . . . . . 10-5
Table 10-8: GCP 8000 Site Controller Link LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Table 10-9: Expansion Hub LEDs with Description . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Table 10-10: Status/Alarm LED Assignment for the Expansion Hub . . . . . . . . . . . . . . . . . 10-7
Table 10-11: Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
List of Procedures
Procedure 3-1: How to Mount the GCP 8000 Site Controller in a Standalone Conguration . . . . . . 3-10
Procedure 3-2: How to Ground the GCP 8000 Site Controller . . . . . . . . . . . . . . . . . . . . 3-24
Procedure 5-1: How to Align the GCP 8000 Site Controller Reference Oscillator . . . . . . . . . . . 5-2
Procedure 8-1: How to Initiate a Diagnostics Command . . . . . . . . . . . . . . . . . . . . . . . 8-19
Procedure 9-1: How to Replace the Site Controller Module. . . . . . . . . . . . . . . . . . . . . . 9-3
Procedure 9-2: How to Replace the GCP 8000 Site Controller Fan Assembly . . . . . . . . . . . . . 9-8
Procedure 9-3: How to Replace the GCP 8000 Site Controller Power Supply . . . . . . . . . . . . . 9-9
Procedure 9-4: How to Replace a Standalone GCP 8000 Site Controller Backplane . . . . . . . . . . 9-10
Procedure 9-5: How to Replace the Expansion Hub . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Procedure 9-6: How to Replace the Expansion Hub . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
List of Processes
Process 4-1: Conguration Process for the GCP 8000 Site Controller . . . . . . . . . . . . . . . . . 4-3
Process 6-1: Site Initialization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Process 6-2: Site Initialization Master Site Interaction . . . . . . . . . . . . . . . . . . . . . . . 6-3
This booklet provides descriptive and procedural information on the GCP 8000 Site Controller. Included
in the booklet are description of the GCP 8000 Site Controller. It also describes the congurations
where the GCP 8000 Site Controller can be found: Standalone, GTR 8000 Site Subsystem, GTR 8000
Expandable Site Subsystem and Console Site Hardware Conguration. Additional information is provided for
procedures on installation, conguration, operation, troubleshooting, and FRU/FRE replacement. Finally
a reference section provides information on the GCP 8000 Site Controller LED indicators.
This booklet is intended to be used by technicians and system operators as a resource for understanding
and installing the GCP 8000 Site Controller after they have attended the Motorola formal training.
The booklet should be used in conjunction with the ASTRO 25 system documentation and
Standards and Guidelines for Communication Sites (68P81089E50).
When using this manual for an ASTRO 25 Trunking System with an ARC 4000 Master
Site, please note that the following features/hardware are not available:
System Statistical Server (SSS)
WAN Switch
Exit Routers
Multizone System
HPD
CADI
InfoVista
Simulcast
Chapter 4, "GCP 8000 Site Controller Conguration". This chapter provides conguration
information for the GCP 8000 Site Controller using the Conguration/Service
Software and Zone Conguration Manager.
Chapter 5, "GCP 8000 Site Controller Optimization". This chapter provides
optimization information for the GCP 8000 Site Controller.
Chapter 6, "GCP 8000 Site Controller Operation". This chapter provides operations
information for the GCP 8000 Site Controller.
Chapter 7, "GCP 8000 Site Controller Maintenance". This chapter provides
maintenance information for the GCP 8000 Site Controller.
Chapter 8, "GCP 8000 Site Controller Troubleshooting". This chapter provides
troubleshooting information for the GCP 8000 Site Controller and the different
systems supported by its hardware congurations.
Chapter 9, "GCP 8000 Site Controller FRU/FRE Procedures". This chapter provides
information and procedures for replacing Field Replaceable Units (FRUs) and
Field Replaceable Entities (FREs) for both the GCP 8000 Site Controller and
the Expansion Hub. Part numbers are also listed.
Chapter 10, "GCP 8000 Site Controller Reference". This chapter provides information on
the LED indicators for both the GCP 8000 Site Controller and the Expansion Hub.
Related Information
Refer to the following documents for associated information about the radio system.
1
GCP 8000 Site Controller Description
This chapter provides a high-level description of GCP 8000 Site Controller and the
function it serves on your system.
The GCP 8000 Site Controller is comprised of two site controller modules with embedded LAN
switches, a power supply, a fan assembly, and two remote GPS connections. One site controller
module acts as the active module and the second module as standby. The redundancy ensures that
any single point of failure at the site does not reduce overall functionality.
Figure 1-1 shows the front view of the GCP 8000 Site Controller in a chassis.
Figure 1-2 shows the front view with the fan assembly removed revealing the redundant
GCP 8000 modules inside the chassis.
Figure 1-3 shows the GCP 8000 Site Controller rear view.
Under the direction of the zone controller and depending on the network status, the GCP 8000
controls whether the site is in wide area mode or in site trunking mode. When the site is not in wide
trunking mode, the channels at the site are under the direction of the GCP 8000 Site Controller. The
selection and assignment of subscribers to the channels, including the control channels assignment
and channel loading features are dictated by the GCP 8000 Site Controller. When the site is in
wide trunking mode, the zone controller dictates the channel assignment.
The GCP 8000 Site Controller is used for any one of the following hardware congurations:
Standalone conguration
GTR 8000 Site Subsystem conguration
GTR 8000 Expandable Site Subsystem conguration
Console Site Hardware conguration
Standalone Conguration
The standalone conguration is comprised of the GCP 8000 Site Controller modules, the power
supply, and the fan module. The number of site controller modules differ slightly depending on
whether it is in an HPD subsystem or in an Simulcast Site Subsystem.
In the standalone conguration for an HPD subsystem, one chassis holds two GCP
8000 Site Controller modules that have embedded LAN switches, a power supply,
a fan assembly, and two remote GPS connections.
In the standalone conguration for a Simulcast subsystem, two chassis are required, each
chassis holding a single GCP 8000 Site Controller module, a single power supply, and a fan
assembly. The single GCP 8000 Site Controller replaces one MTC 9600 Site Controller.
Figure 1-4 shows the standalone conguration of the GCP 8000 Site Controller.
Figure 1-6 GTR 8000 Expandable Site Subsystem Conguration HPD Subsystem
The GTR 8000 Expandable Site Subsystem supports the HPD Expandable Site Subsys-
tem with a maximum of ve base radios.
Figure 1-7 GTR 8000 Expandable Site Subsystem Conguration IV&D Subsystem
The GCP 8000 Site Controller is used to provide zone controller functionality for site conventional
operation when the control path to the zone controller is lost as shown in Figure 1-8.
The GCP 8000 Site Controller LEDs are found at the nose of the site controller module as well as in the
chassis above the ports. Figure 1-9 identies the general areas where LEDs appear on the GCP 8000 module.
See the GCP 8000 Site Controller Reference chapter for information on specic LEDs.
All equipment at the site supports operation from 90/264 VAC nominal single phase power sources
at 47/63 Hz or a 43.2-60 VDC power source or battery. 60 VDC maximum input voltage limit
includes consideration of the battery charging oat voltage associated with the intended supply
system, regardless of the marked power rating of the equipment.
The GCP 8000 has automatic battery revert capabilities and can charge batteries from the AC
power supply. The power supply includes an integrated charging system that eliminates the
need for UPS. The power supply provides battery equalization.
The GCP 8000 has an internal power supply and is able to provide 29 VDC auxiliary
power output as a backup power source. This allows, for example, a connected RMC with
a power supply failure to maintain continued operation.
Table 1-2 lists the operation and environmental specications for the GCP 8000 Site Controller.
Table 1-2 GCP 8000 Site Controller Technical and Environmental Specications
The Expansion Hub (X-Hub) is a non-intelligent switching and interface module that connects to the GCP
8000 Site Controller. The Expansion Hub has the same clamshell type of housing as the site controller.
The Expansion Hub is only used in the GTR 8000 Expandable Site Subsystem.
The Expansion Hub is only used as part of an ASTRO 25 Repeater Site.
The X-Hub allows the GCP 8000 Site Controller to support additional GTR 8000 Base Radios beyond
what the Site Controller supports on its own. One site controller supports up to four Expansion Hubs
with each Expansion Hub supporting up to six GTR 8000 Base Radios.
X-Hub Specications
Physical dimensions Height: 1.4 in. (36mm)
Width: 14.2 in. (360mm)
Depth: 15.3 in. (390mm)
Weight 6.6 lbs (3 kg)
Temperature:
Operating temperature -30 to 60C (-22 to 140F)
Storage temperature -30 to 70C (-22 to 158F)
Relative humidity 90% relative humidity at 50C (122F)
non-condensing
Input supply voltage 28.9 V DC
Power consumption 10 W
Operating altitude Up to 1800 m (6000 ft) above mean sea level
2
GCP 8000 Site Controller Theory of
Operation
This chapter explains how the GCP 8000 Site Controller works in the context of your system.
Registration Function
For registration events, the GCP 8000 is responsible for forwarding requests and responses between
the GTR 8000 Base Radios and the zone controller. The GCP 8000 maintains, in memory, a
database of active Mobile Subscriber Units (MSUs) at the site. This database includes the channel
assignment and registration status for each MSU operating at the site.
GTR 8000
Subsystem GTR 8000 Site
Standalone Expandable Site
Type Subsystem
Subsystem
HPD Subsystem Remote GPS (RGPS) Remote GPS (RGPS) Remote GPS (RGPS)
is the primary NTP is the primary NTP is the primary NTP
source, providing source, providing source, providing time
Table 2-1 Time Synchronization and Frequency Reference Table for Different Site Controller
Congurations (Continued)
GTR 8000
Subsystem GTR 8000 Site
Standalone Expandable Site
Type Subsystem
Subsystem
time synchronization time synchronization synchronization and
and frequency and frequency frequency reference.
reference. reference.
Repeater Site NA NA The internal reference
Subsystem oscillator is used to
provide frequency
reference to the base
radio.
Simulcast Site TRAK 9100 at the NA NA
Subsystem prime site is the
primary NTP source.
In an HPD Subsystem:
The active GCP 8000 Site Controller acts as the Network Time Protocol (NTP) client for
the site, providing the time to the GTR 8000 Base Radios and other devices at the site. The
Remote GPS connected to the site controller is the primary NTP source. The time and
frequency reference is supplied to GTR 8000 Base Radios at the site through the Ethernet
cable. The GCP 8000 is capable of keeping time accurate to within +/- 1 microsecond
per day across the valid temperature range of the Site Controller.
The active GCP 8000 Site Controller broadcasts time updates every 64 seconds. The idle
GCP 8000 uses the NTP source time to verify correct time setting. If the internal time
variance in a device is equal to, or greater than 500 milliseconds from the NTP source time,
the device corrects the NTP Time of Day clock to match the received NTP time.
The frequency reference is distributed on the backplane, no cables are required. The GPS
receivers provide the necessary references for site operation, 1 pulse per second and a high
stability frequency reference. The 1 pulse per second time reference is needed to synchronize
the data transmissions from the radios, and the high stability frequency reference is needed to
provide a reference for both the transmit and receive frequency synthesizers in the radios.
The GCP 8000 Site Controller includes a high-stability ovenized crystal oscillator, which is
trained by input from a GPS antenna. One GPS antenna must be connected to each GCP 8000
Site Controller. The Conguration/Service Software (CSS) indicates whether the GPS capability
is congured. The GCP 8000 indicates the status and alarms for GPS service to FullVision INM.
Redundancy Function
The GTR 8000 conguration provides two site controller modules, one module acts as the active
module and the second is the standby module. To provide maximum availability, the two modules
actually take on some aspects of the active tasks at the same time. For example, if the LAN
connected to the active site controller fails, the standby site controller LAN becomes active, even
though the active site controller continues to handle site administration.
In an HPD system, the two site controller modules are contained within a single chassis, in a simulcast
subsystem, one site controller module is mounted in each of two chassis.
The two site controllers operate in an active/standby conguration for protection against a single point of
failure at the site. The active GCP 8000 manages operations at the site while the standby SC monitors the
periodic status messages from the active SC. A programmed set of rules determines which site controller
assumes the role of primary controller and when it is necessary for the other controller to take over the
operation of the subsystem. Depending on the site conguration and the type of loss, the standby site
controller becomes active when no status messages are received by the previously active site controller.
If both Site Controllers (SC0 and SC1) try to go active at the same time, they both have a brief wait time. SC0
has a shorter wait and becomes active rst, sending a status message. When SC1 tries to become active, it
receives the status message from SC0. This identies SC0 as the active site controller, and SC1 remains standby.
During the failover process, the newly active site controller must transit through the initialization process
from standby state into the wide area state. During this time, base radios remained keyed, and MSUs
leave the site searching for a wide area site. The MSUs run a hold-off timer before registering with the
site. The MSUs at the site need to register again with the system after the failover process has completed
to update the database stored in memory of the newly active GCP 8000 Site Controller.
Afliation
The CSC allows console operation to afliate to conventional channels in the site conventional mode.
This is similar in wide conventional mode, except that the operations are required to re-afliate
whenever there is transition from wide to site conventional mode.
The CSC stores afliation information throughout the period of site conventional operation. When the
console site link goes down and then comes back up, the CSC uses the stored afliation information to
update console operations with the statuses of conventional channels they are afliated to.
Association
Association is an attribute of afliation. The CSC supports association as a part of Cross
Busy/Cross Mute feature. Console operation associated to a given conventional channel receives
all call processing events related to that channel, but no audio.
The ports on the front of the GCP 8000 Site Controller module are the same, whether the module is in
an HPD conguration, a Repeater site conguration, or a Simulcast site conguration.
The GCP 8000 Site Controller has ports on both the front and the back that allow it to connect
to a variety of devices, including base radios, expansion ports, remote GPS, and a router. In
a GTR 8000 Expandable Site Subsystem conguration, the Ethernet connections from the
individual base radios are run on the backplane and connect to the switch on the GCP 8000 Site
Controller. This conguration minimizes the need for Ethernet cables.
Figure 2-1 provides a view of the ports on the front of the GCP 8000.
Figure 2-1 Photo of Ports on the GCP 8000 Site Controller (Front View)
Table 2-2 explains each port on the front of the GCP 8000 Site Controller.
Table 2-2 Description of Ports on the GCP 8000 Site Controller (Front View)
Figure 2-2 provides a view of the interfaces on the rear of the site controller.
Figure 2-2 Photo of Ports on the GCP 8000 Site Controller (Rear View)
Table 2-3 explains each port on the back of the GCP 8000 Site Controller.
See table GCP 8000 Site Controller Port Default Speed/Duplex Settings and X-Hub
Port Default Speed/Duplex and for port default speed/duplex settings.
Table 2-3 Description of Ports on the GCP 8000 Site Controller (Rear View)
Table 2-3 Description of Ports on the GCP 8000 Site Controller (Rear View) (Continued)
Port Description Hardware Conguration
Internal Alarm Not in use Not in use
Remote GPS B Connection between the Standalone
RGPS B and the GCP 8000
GTR 8000 Site Subsystem
Site Controller.
GTR 8000 Expandable Site
Subsystem
External Alarm Not in use Not in use
Comparator A, B/ Not in use Not in use
RJ-45
SC A to Base Radio Connection between site Standalone
1-6/ RJ-45 controller A and GTR 8000
GTR 8000 Site Subsystem HPD
Base Radios at the site.
only Port 1 to base radio Ports
26 not used
GTR 8000 Expandable Site
Subsystem has a direct
connection to the base radios
through the backplane.
In an Expandable Site Subsystem
used with HPD, only ports 15
are used.
EXT FREQ REF Not in use Not in use
1 PPS Not in use Not in use
SC B to Base Radio Connection between site Standalone
1-6/ RJ-45 controller B and GTR 8000
GTR 8000 Site Subsystem HPD
Base Radios at the site.
only Port 1 to base radio Ports
26 not used
GTR 8000 Expandable Site
Subsystem has a direct
connection to the base radios
through the backplane.
In an Expandable Site
Subsystem used with HPD, only
ports 15 are used.
Battery Temp Connection to temperature Standalone
sensor, allowing for
GTR 8000 Site Subsystem
temperature compensated
battery charging. GTR 8000 Expandable Site
Subsystem. Only one is needed
for each cabinet.
AUX PWR Output Reserved for Future Use Reserved for Future Use
Table 2-3 Description of Ports on the GCP 8000 Site Controller (Rear View) (Continued)
Port Description Hardware Conguration
AUX PWR Input The auxiliary input is Standalone
connected with a GTR
GTR 8000 Site Subsystem
8000 Base Radio as a
secondary power source. GTR 8000 Expandable Site
Subsystem. Internally wired.
+ Batt/DC Input from a +/- 48 VDC Standalone
nominal power supply.
GTR 8000 Site Subsystem
Input from, and charging
output to, backup battery. GTR 8000 Expandable Site
Subsystem
AC Input from 90/264 VAC Standalone
nominal power source.
GTR 8000 Site Subsystem
GTR 8000 Expandable Site
Subsystem
GND Two grounding lugs and Standalone
cable.
GTR 8000 Site Subsystem
GTR 8000 Expandable Site
Subsystem
See Table 2-4 and Table 2-5 for port default speed/duplex settings.
Table 2-4 GCP 8000 Site Controller Port Default Speed/Duplex Settings
Table 2-4 GCP 8000 Site Controller Port Default Speed/Duplex Settings (Continued)
Switch Port Speed/Duplex
Service Port Auto-Negotiate
Local Site Controller 1 Auto-Negotiate
External Router 100BaseT/Full Duplex
Local Site Controller 2 Auto-Negotiate
Base Radio 1 100BaseT/Full Duplex
Base Radio 2 100BaseT/Full Duplex
Base Radio 3 100BaseT/Full Duplex
Base Radio 4 100BaseT/Full Duplex
Base Radio 5 100BaseT/Full Duplex
Base Radio 6 100BaseT/Full Duplex
Alarm Card Auto-Negotiate
CPU on Red Site Controller Auto-Negotiate
The GCP 8000 Power Supply is shown in Figure 2-3. This power supply is used for the GCP 8000
Site Controller, regardless of its conguration, and for the Expansion Hub.
The GCP 8000 power supply operates from either an AC or DC input and provides the
DC operating voltage for the site controller.
When operating from an AC source (90 to 264 VAC, 47-63 Hz), the supply generates 2
DC output voltages of 29 V with respect to output ground. The power supply automatically
adjusts to AC input ranges and supplies a steady output.
In AC mode, the power supply provides a separate battery charger, which is used to maintain the charge on a
48 VDC nominal system, positive or negative ground, if installed. The supply generates 2 DC output voltages
of 29V with reference to output ground, when operating from a DC source (43.2 VDC to 60 VDC maximum,
positive or negative ground). This voltage limit includes consideration of the battery charging oat voltage
associated with the intended supply system, regardless of the marked power rating of the equipment.
The battery charger is not usable when operating from a DC input power source.
The power supply contains several switching-type power supply circuits as follows:
Power factor correction circuitry
Battery charging circuitry
Diagnostics and monitoring circuitry
The battery charger outputs of the power supply are designed to be bussed together so that up to
six power supplies provide charging services to a single battery bank.
The power supply controls its own continuously running fan, changing its speed to fast or slow as needed.
Figure 2-4 AC and DC Power Distribution in the GCP 8000 Site Controller
The GCP 8000 Site Controller operates from AC power as the preferred power source. When
AC power is not available, the site controller switches to operate from the DC source. Operation
returns to the AC source when the AC source is restored. Switch over from AC to DC and
back again is fully automatic. No operator action is required.
The Main DC output of the power supply is used to provide power to the site controller modules. The
Auxiliary output of the power supply is reserved for use as a redundant power input.
The sensing element of the temperature sensor needs to be mounted so that it detects the
actual battery temperature (or the ambient temperature as close as possible to the batteries
being charged). Two examples of mounting are:
Example 1: Use cable ties to attach the sensing cable to the positive (or negative) power cable. A
minimum of two cable ties must be used (spaced 6 inches apart), with one of the cable ties not more
than 2 inches from the sensing element. The sensing element itself must be not more than 2 inches
from the battery post where the power cable connects. See Figure 2-5.
Example 2: Attach the sensing cable to an existing battery tray support bracket using cable ties or nylon
loop straps of the proper size. The sensing element must be placed so that it is not more than 2 inches from
the surface of the batteries being monitored. A minimum of two cable ties and/or loop straps must be used
to secure the sensing cable to the bracket. The cable ties or loop straps must be placed no more than 6
inches apart with one placed no more than 2 inches from the sensing element. See Figure 2-6.
Port/Type Description
AC Input only
Battery / 48 VDC:
DC Power
Provides the DC input to the power supply when operating from a DC
and Control
source.
Signal
Connects the charger output to the standby battery when operating from
an AC input with a standby DC battery.
29 VDC:
Provides the Main and Aux DC outputs of the power supply for use by
the power amplier, transceiver, and site controller.
Other signals handled by this connector include control interface and battery
temperature interface.
The GCP 8000 Conventional Site Controller does not use the Power Sup-
ply module backplane connection.
The GCP 8000 Site Controller receives auxiliary power from other devices as well as provides auxiliary
power. For example, it receives auxiliary power through its port, AUX PWR Input, from the GTR
8000 Base Radio, and benet from the backup power source when needed.
The GCP 8000 Site Controller also provides 29 VDC auxiliary power to other devices. For example, from
the RFDS port of the GTR 8000 Expandable Site Subsystem backplane, the GCP 8000 Site Controller
provides auxiliary power to another device such as the Receiver Multi-coupler.
For subsystems, a power supply is removed without disabling site controllers if the site controllers are cabled
to auxiliary power. Auxiliary power is available from any base radio that is still connected to a power supply.
In Expandable Site Subsystems, an Aux DC bus is automatically set up to
provide backup power to the site controllers.
In the Standalone conguration of a Simulcast Site Subsystem, the auxiliary power is not used.
Conguration of the GCP 8000 Site Controller is performed using the Conguration/Service Software
(CSS), Software Download (SWDL) application, and Zone Conguration Manager (ZCM).
SWDL
SWDL is used to transfer and install software to remote site devices through
a direct connection or central remote location.
Both primary and redundant site controller modules have two memory banks for loading and
running software. One bank is active while the other bank is inactive. The transfer of software
using SWDL is a background process that loads the software into inactive bank. The GCP
8000 executes the software in one bank, while software is simultaneously downloaded to the
inactive bank. This is done in the background without interruption of services at the site. An
install causes the GCP 8000 to reset and activates the bank to run with the new software.
The GCP 8000 Site Controllers are proxy devices for software downloading.
All software downloads to GTR 8000 Base Radios are rst loaded to
the GCP 8000 Site Controllers, and the Site Controller then transfers
the software to each base radios at the site.
For detailed information on conguring the GCP 8000 Site Controller, see Chapter
4, GCP 8000 Site Controller Conguration.
Expansion Hub
The Expansion Hub (X-Hub) is a non-intelligent switching and interface module. The X-Hub connects
with the GCP 8000 Site Controller as part of a GTR 8000 Expandable Site Subsystem. Up to ve X-Hubs
are connected to one Site Controller through an Ethernet cable from the EXPSN Input port on the front
of the X-Hub to one of the Site Control Expansion ports on the front of the GCP 8000 Site Controller.
Each X-Hub is capable of supporting six additional base radios or Comparators.
The X-Hub has two modes of operation: Normal and Impaired Normal.
In the Normal mode of operation, the X-Hub extends the switching and interface
capabilities of the Site Controller in an expansion chassis. In normal mode, the
Ethernet switch is congured by the Site Controller.
The Impaired Normal mode occurs when the link between the Site Con-
troller and the X-Hub is lost.
Redundant X-Hubs are required to support system expansion in congurations with redundant Site
Controllers. Redundant X-Hubs share many common external interfaces. A hardware mechanism
ensures that only one X-Hub is capable of driving these interfaces at a given time.
Figure 2-8 Ports on the XHub (Front View) GTR 8000 Expandable Site Subsystem
Table 2-8 explains each port on the front of the GCP 8000 for both site controller modules.
Table 2-8 Ports on the Expansion Hub (Front View) GTR 8000 Expandable Site Subsystem
Port Description
EXPSN Input Connection to the site controller.
Net AUX Spare port available for router or other Ethernet
connectivity.
3
GCP 8000 Site Controller Installation
This chapter details installation procedures relating to GCP 8000 Site Controller.
Observe the following general safety precautions during all phases of operation, service, and repair of the
equipment described in this manual. Follow the safety precautions listed below and all other warnings and
cautions necessary for the safe operation of all the equipment. Refer to the appropriate section of the product
service manual for additional pertinent safety information. Because of the danger of introducing additional
hazards, do not install substitute parts or perform any unauthorized modications of equipment.
The installation process requires preparation and knowledge of the site before
installation begins. Review installation procedures and precautions in the Motorola
R56 manual Standards and Guidelines for Communications Sites (68P81089E50)
before performing any site or component installation.
Always follow all applicable safety procedures, such as Occupational Safety and Health Administration
(OSHA) requirements, National Electrical Code (NEC) requirements, local code requirements, safe working
practices, and good judgment must be used by personnel. General safety precautions include the following:
Read and follow all warning notices and instructions marked on the product or
included in this manual before installing, servicing, or operating the equipment.
Retain these safety instructions for future reference.
If troubleshooting the equipment while power is on, be aware of the live circuits.
Do not operate the radio transmitters unless all RF connectors are secure
and all connectors are properly terminated.
All equipment must be properly grounded in accordance with the Motorola R56
manual Standards and Guidelines for Communications Sites (68P81089E50) and
specied installation instructions for safe operation.
Slots and openings in the cabinet are provided for ventilation. Do not block or
cover openings that protect the devices from overheating.
Only a qualied technician familiar with similar electronic equipment
must service the equipment.
Some equipment components can become extremely hot during operation. Turn off all
power to the equipment and wait until sufciently cool before touching.
Maintain emergency rst aid kits at the site.
Have personnel call in with their travel routes to help ensure their safety
while traveling between remote sites.
Institute a communication routine during certain higher risk procedures where
the on-site technician continually updates management or safety personnel of
the progress so that help is dispatched if needed.
Never store combustible materials in or near equipment racks. The combination of combustible
material, heat and electrical energy increases the risk of a re safety hazard.
Equipment is to be installed in the site meeting the requirements of a restricted access
location per UL60950-1, which is dened as follows: Access is gained by service
persons or by users who are warned about the possible burn hazard on equipment
metal housing and hazardous energy level at the BATT/DC port. Access to the
equipment is through the use of a tool or lock and key, or other means of security,
and is controlled by the authority responsible for the location.
Burn hazard. The metal housing of the product becomes extremely hot.
Use caution when working around the equipment.
DC input voltage must not be higher than 60 VDC. This maximum voltage
includes consideration of the battery charging oat voltage associated with the
intended supply system, regardless of the marked power rating of the equipment.
Failure to follow this guideline may result in an electric shock.
Replaceable Batteries
Equipment Racks
Equipment racks should only be lifted without the use of lifting equipment when sufcient personnel are
available to ensure that regulations covering health and safety are not breached. Motorola recommends the use
of an appropriate powered mechanical lifting apparatus for moving and lifting the equipment racks. In addition
to these points, refer to and comply with any local regulations that govern the use of lifting equipment.
Do not use the eyenuts if damage is apparent. Contact Motorola for replacements.
Use all four eyenuts when lifting the equipment rack. The minimum distance from each eyenut to the
lifting point must be 1.2 m (47.2 in.). Using a shorter length than that specied could cause the eyenuts
to fail. Figure 3-2 shows the minimum lengths and proper lifting angles using the eyenuts.
Figure 3-2 Lengths and Angles for Lifting Using the Eyenuts
If eyenuts are removed or becomes loose, install them properly before lifting the equipment rack. Tighten
the eyenuts and bolt assembly by hand. Correct eyenut tightness and alignment are crucial to ensure the
eyenut assembly performs to its intended lifting capacity. The eyenuts must be aligned to point towards
the center lifting point of the cabinet and tightened to between 90 to 120 in-lbs torque.
Figure 3-3 shows the proper alignment of the eyenuts.
Refer to R56 manual, Standards and Guidelines for Communication Sites, for guidelines on designing
and installing equipment at an RF site. The following guidelines are covered:
Safety guidelines
Site selection, design, and development
Site building design and installation
External/internal grounding
Power sources
Transient voltage surge suppression
Minimizing site interference
Equipment installation
Antenna installation
The GCP 8000 Site Controller is installed in one of three hardware congurations:
GCP 8000 Standalone Site Controller. This is only available as a unit. Hardware is available
to mount it to a customer rack. It does not ship with a rack or a cabinet. For detailed
information, see GCP 8000 Site Controller Standalone Conguration.
As part of the GTR 8000 Site Subsystem. This is a specic set of hardware
modules in a special 52 inch rack. It includes a base radio, two site controller
modules, and an RFDS system. For detailed information, see GCP 8000 Site
Controller GTR 8000 Site Subsystem Conguration.
As part of the GTR 8000 Expandable Site Subsystem. This is available in a cabinet
or an open rack. For detailed information, see GCP 8000 Site Controller GTR
8000 Expandable Site Subsystem Conguration.
Table 3-1 summarizes the hardware congurations and the systems they support.
Table 3-1 GCP 8000 Site Controller Hardware Congurations and Systems Supported
The GCP 8000 Site Controller is installed as a standalone site controller. This is only available as a unit.
Hardware is available to mount it to a customer rack. It does not ship with a rack or a cabinet.
In the HPD subsystem, the two site controller modules are mounted in one chassis.
In the Simulcast Site Subsystem, one site controller module is mounted in each of the two chassis.
Procedure 3-1 explains how to mount the standalone GCP 8000 into an open rack.
It is suggested that two people perform this installation so that one person holds the GCP
8000 in place while the other person attaches the brackets to the rack.
Procedure 3-1 How to Mount the GCP 8000 Site Controller in a Standalone Conguration
1 Determine where on the rack you will mount the GCP 8000 and mark the location.
The brackets are useful in making this determination, and the pin on the back of
the bracket helps nding the exact location on the rack.
2 Attach the brackets to the sides of the GCP 8000:
Use M6x1x13 machine screws with captivated washer (zinc plated).
Screw one bracket into the clinch nuts on the side of the site controller
chassis.
Now do the same with the second bracket: Screw it into the clinch nuts on
the other side of the site controller chassis.
3 Lift the GCP 8000 into place on the rack using the pins on the brackets to
properly line up the device.
4 Next, attach the two brackets to the rack:
For a Motorola modular rack, use M6x1x10 thread forming screws with
black nish.
For a Motorola open rack, use 1224x5/8 in. thread forming screws (zinc
plated).
For your own rack, use hardware appropriate for the rack.
Attach the brackets to both sides of the rack through the upper back
openings on the brackets.
Now, through the lower back openings, attach the brackets to the rack on
both sides.
5 In the front, attach the chassis to the brackets:
Screw two M6x1x10 thread forming screws (black nish) through the front
holes on one side of the GCP 8000 chassis and into the bracket.
Screw two M6x1x10 thread forming screws (black nish) through the front
holes on the other side of the GCP 8000 chassis and into the bracket.
Figure 3-5 shows the front connections for the site controller. These connections differ only in that there are
two modules in a chassis for an HPD subsystem, and one module in a chassis for a Simulcast Site Subsystem.
Figure 3-5 GCP 8000 Site Controller Connections (Front View) Standalone Conguration
Make sure to set the speed/duplex on the LAN ports to 100 MB full duplex.
Table 3-2 GCP 8000 Site Controller Connections (Front View) Standalone Conguration
Table 3-2 GCP 8000 Site Controller Connections (Front View) Standalone Conguration
(Continued)
Connects Port Hardware
Port / Type Description
to... Type Congurations
Net AUX / MOSCAD LAN LAN connection to Standalone
RJ-45 (optional) port 1, the MOSCAD site In a Simulcast subsystem,
RJ-45 device manager this port connects to an
for local fault external site switch.
monitoring, or in a
Simulcast subsystem,
to an external switch.
Site Control Not in use Not in Not in use Not in use
Expansion use
(15) / RJ-45
Frequency calibration Port available Standalone
Calibration / equipment on each site
BNC controller module
for measuring and
calibrating the
frequency reference.
Fan Connector Fan Plug in connection Standalone
assembly when the fan
assembly is mounted.
Figure 3-6 illustrates the connections on the rear of the site controller in a Standalone conguration.
These connections differ only in that there are two modules in a chassis for an HPD subsystem,
and one module in a chassis for a Simulcast Site Subsystem.
Figure 3-6 GCP 8000 Site Controller Connections (Rear View) Standalone Conguration
Table 3-3 describes the connections on the rear of the site controller. The Hardware
Congurations column of the table indicates how the connection applies to each of the three
hardware congurations for the GCP 8000 Site Controller.
Table 3-3 GCP 8000 Site Controller Connections (Rear View) Standalone Conguration
Hardware
Port / Type Connects to... Port Type Description Congura-
tions
RFDS / 50 - pin RFDS equipment Monitors Standalone
(power monitor, RFDS alarms
receiver multi- from the
coupler) power monitor
and receiver
multi-coupler.
Remote GPS A / Lightning arrestor Line terminals Connection Standalone
Line terminals / RGPS unit A between RGPS
A and the
GCP 8000
Site Controller.
See gure,
Lightning
Arrestor
System
Connections,
for terminal
connection
details.
Internal Alarm / External alarm Not in use Not in use
DB-25 connections
Remote GPS B / Lightning arrestor Connection Standalone
Line terminals / RGPS unit B between RGPS
B and the
GCP 8000
Site Controller.
See gure,
Lightning
Arrestor
System
Connections,
for terminal
connection
details.
External Alarm / Not in use Not in use Not in use
50 - pin
Comparator A, B Not in use Not in use Not in use
/ RJ-45
Table 3-3 GCP 8000 Site Controller Connections (Rear View) Standalone Conguration
(Continued)
Hardware
Port / Type Connects to... Port Type Description Congura-
tions
SC A to Base GTR 8000 Base SITE CTRL A Connection Standalone
Radio 1-6 / RJ-45 Radio (16) between site Port 1 to
controller A base radio
and the base Ports 26
radios at the not used
site.
EXT FREQ REF / Not in use Not in use Not in use
BNC
1 PPS / BNC Not in use Not in use Not in use
SC B to Base GTR 8000 Base SITE CTRL B Connection Standalone
Radio 1-6 / RJ-45 Radio (16) between site Port 1 to
controller B base radio
and the base Ports 26
radios at the not used
site.
Batt Temp / 6- pin customer supplied Battery Standalone
battery temperature
sensor.
Connection to
temperature
sensor,
allowing for
temperature
compensated
battery
charging.
AUX Pwr Output Reserved for Reserved for
Future Use Future Use
AUX Pwr Input GTR 8000 Base AUX Pwr The auxiliary Standalone
Radio Output input is
connected with
a GTR 8000
Base Radio as
a secondary
power source.
Table 3-3 GCP 8000 Site Controller Connections (Rear View) Standalone Conguration
(Continued)
Hardware
Port / Type Connects to... Port Type Description Congura-
tions
+ Batt/DC DC power supply Input from Standalone
or battery a 48 VDC
power supply.
Input from,
and charging
output to,
backup battery
or backup
battery.
AC In 120/240 VAC Input from Standalone
power source 120/240 VAC
nominal power
source.
GND lugs and Rack grounding Grounding Standalone
cable bar cable attaches
to the rack
grounding bar.
The GTR 8000 Site Subsystem conguration comes from the factory pre-wired and installed. Figure 3-7
is an example of the GTR 8000 Site Subsystem hardware conguration.
When the GCP 8000 Site Controller is part of the GTR 8000 Site Subsystem, the wiring is internal through
the junction panel. Figure 3-8 illustrates the junction panel for a GTR 8000 Site Subsystem.
The GTR 8000 Expandable Site Subsystem conguration comes from the factory pre-wired and installed
with up to ve cabinets for HPD. The cabinet has two redundant GCP 8000 Site Controllers.
Figure 3-9 is an example of the GTR 8000 Expandable Site Subsystem in an HPD Subsystem.
Figure 3-9 GTR 8000 Expandable Site Subsystem Conguration Example of an HPD Subsystem
The GCP 8000 Site Controller is part of the GTR 8000 Expandable Site Subsystem and
the wiring is internal through the junction panel and connected at the factory. Figure 3-10
illustrates the junction panel for the subsystem.
Figure 3-10 GTR 8000 Expandable Site Subsystem Junction Panel with Primary Sub-panel #1
The GTR 8000 Expandable Site Subsystem conguration comes from the factory pre-wired and installed
with up to six cabinets for IV&D. The rst cabinet has two redundant GCP 8000 Site Controllers. In the
second through sixth cabinets, an expansion hub is provided (instead of a site controller).
Figure 3-11 is an example of the GTR 8000 Expandable Site Subsystem in an IV&D Subsystem.
Figure 3-11 GTR 8000 Expandable Site Subsystem Conguration Example of an IV&D
Subsystem
The GCP 8000 Site Controller is part of the GTR 8000 Expandable Site Subsystem and the wiring is
internal through the junction panel and connected at the factory. Figure 3-12 illustrates the junction
panel for the subsystem. Additional sub-panels are added for expansion cabinets.
Figure 3-12 GTR 8000 Expandable Site Subsystem Junction Panel with Primary Sub-panel #1
Each Expansion Hub (X-Hub) is connected to its corresponding site controller through the sub-panels on
the Junction Panel. Figure 3-13 show the connections on the front of the X-Hub.
Table 3-4 describes the two ports available on the Expansion hub.
Table 3-4 Expansion Hub Connections (Front View)
Connects Hardware
Port Port Type Description
to... Conguration
NET AUX Junction Not Used Not Used
panel, NET
AUX port
EXPSN Input Network RJ-45 Provides connection GTR 8000
Expansion between X-Hub Expandable Site
sub-panel module and Junction Subsystem
on Junction Panel, and site
panel controllers in Cabinet
#1.
Figure 3-14 illustrates the Network Expansion sub-panel. This sub-panel is part of the Junction
Panel in the Primary cabinet of a GTR 8000 Expandable Site Subsystem.
Power Requirements
Table 3-5 lists the power connections for the standalone GCP 8000 Site Controller for both
DC and AC power. Follow the guidelines in the R56 manual, Standards and Guidelines for
Communication Sites, for information on providing electrical service, power budgeting, selecting
batteries, and other topics for supplying power at the site.
You must provide proper strain relief for the power cable. Route and secure the power
cable to protect it from strain and external forces. Careful cable routing and securing the
cables with tie wraps (or other devices) is one way to provide this protection.
Table 3-5 Standalone GCP 8000 Site Controller Input Power Wiring
Table 3-5 Standalone GCP 8000 Site Controller Input Power Wiring (Continued)
If the GCP 8000 uses: Then:
GTR 8000 Expandable Site Subsystem: The power source for the site controllers and expansion
hubs is shared by site controllers, base radios, and other devices in Cabinet #1. The expansion hubs,
base radios, and other devices in the expansion cabinets share the power.
Cabinets and racks include a Rack Grounding Bar (RGB) with the capacity to terminate
numerous ground wires. Equipment added to the cabinet or rack must be attached to the
ground bar using solid or stranded 6 AWG copper wire.
The RGB uses dual-hole lugs to terminate ground wires. The minimum number of dual-hole attachments is
system dependent and is specied by the customer. This bar provides electrical continuity between all bonds
and ground wire with a current carrying capacity equal to or exceeding that of a 6 AWG copper wire.
Refer to Motorola R56 manual Standards and Guidelines for Communication Sites (68P81089E50)
for more information on proper bonding and ground at a site.
The GCP 8000 Site Controller has a double lug with two lock nuts on the rear panel where the
ground wire connects to the site controller on one end, and to the rack grounding bar on the other.
The rack grounding bar is connected to the internal ground system. Figure 3-15 identies the two
grounding lugs. To use the grounding lug, you need a length of #6 AWG wire with UL - listed ring
lugs on both ends. This wire is shipped with the GCP 8000 Site Controller.
Figure 3-15 GCP 8000 Site Controller Rear View with Grounding Lugs
Procedure 3-2 explains how to ground the GCP 8000 Site Controller.
Procedure 3-2 How to Ground the GCP 8000 Site Controller
1 Take the ground wire already attached to the two grounding lugs at the rear of the
GCP 8000, and connect the other end to the rack grounding bar.
2 Tighten the ground lock nut to 60 inch-pounds (6.94 newton-meters).
This instruction assumes that all telephone lines, antenna cables, and AC or DC power
cables are properly grounded and lightning-protected.
GTR 8000 Expandable Site Subsystems: When rack installations have a primary rack and one
or more expansion racks, all these racks must be connected to the same Sub System Ground Bus
Bar (SSGB) (and no other rack connected to the SSBB). This is to ensure surge events do not
produce ground potential differences that affects signals between the racks.
Detailed grounding information is beyond the scope of this manual. Refer to R56 manual, Standards and
Guidelines for Communication Sites for detailed information about grounding and lightning protection.
The Conventional Site Controller (CSC) is an optional device that can be installed at a console site. The
CSC provides fallback capability for the console site and conventional channels co-located with this site,
when the link between the zone controller and the console site is lost. See Figure 3-16.
4
GCP 8000 Site Controller Conguration
This chapter details conguration procedures relating to GCP 8000 Site Controller.
Conguration Parameters
Conguration of the GCP 8000 Site Controller is performed using the Software Download (SWDL)
software, the Conguration/Service Software (CSS), and the Zone Conguration Manager.
SWDL transfers and installs software to the GCP 8000 Site Controller through
a direct connection or central remote location.
CSS is used to congure the device owned parameters on the GCP 8000 Site
Controller. CSS accesses devices remotely over the network, or locally through an
Ethernet connection to the service port on the site controller.
ZCM is used to congure manager owned parameters on the GCP 8000 Site Controller,
specically the Site ID, which is the ID of the site in which the device is congured.
The GCP 8000 Site Controller programming consists of two sets of parameters: device-owned
parameters and manager-owned parameters. Device-owned parameters are programmed at
the site controller using CSS, and include the following:
Site controller name (Controller Name)
Site controller number (Controller Number)
Site controller IP address (Controller IP Address)
Power supply
Battery type
The device-owned parameters are not overwritten with the values in the Zone Conguration Manager (ZCM).
Manager-owned parameters marked with an asterisk (*) at the CSS are programmed in the ZCM and
downloaded to the site controller when the link is established between the site controller and the zone
controller. Manager-owned parameters are programmed or changed locally at the site controller using CSS.
But the values are overwritten by values from the ZCM once the link is established to the zone controller.
Several areas of the CSS conguration are specic to the GCP 8000 Site Controller:
Band plan information (click System, and then either Frequency Band
Plan or Other Band Trunking)
Band Plan Information tab identies the Band Plan ID and Band Plan
name. The HPD, ASTRO 25 Repeater Site, and Simulcast Site Subsystems
can all congure up to 20 Band Plan IDs.
Frequency Band Plan tab denes the band plan and identies the number
of elements (index) for a Band Plan ID.
- Two elements are congured in an HPD system. Set this eld to
either 1 (800 MHz) or 2 (700 MHz).
The fans, battery, and power supply are owned by the site controller, and the parameters for
these devices are set locally in the CSS, not zone wide by the Zone Conguration Manager. The
HPD, ASTRO 25 Repeater Site, Simulcast Site Subsystems all congure these parameters.
The switch conguration is set at the factory and need not be changed, though it is possible.
Changing the switch conguration parameter impacts the site and site performance. One
switch parameter, Port 20, is used as a communication path between Site Controllers,
and is Enabled or Disabled based on the network conguration at the site.
Process 4-1 provides the steps for conguring the site controller.
Process 4-1 Conguration Process for the GCP 8000 Site Controller
The IP Address and Box Number are set only through a serial
connection.
3 Complete the information in the elds of the Set IP Address / Box Number
window. Refer to CSS Online Help for eld information.
4 Click the Set button, then click the Restart button.
Result: The data is stored.
5 Connect to the GCP 8000 using an Ethernet connection.
6 Read the current conguration from the site controller by selecting File then
Read Configuration From Device from the menu, or click the shortcut button in
the tool bar.
7 Click System in the System tree.
Result: The System window opens, allowing you to congure the system-level
parameters that are stored in the site controller.
8 In the System Id eld, enter a hexadecimal value (between 001 and FFE).
9 Dene the frequency band plan through the Frequency Band Plan Window in CSS
for each site controller. Refer to CSS Online Help for GCP 8000 Site Controller.
10 Dene the zone ID and IP addresses in the Zone Window in CSS. Refer to CSS
Online Help for GCP 8000 Site Controller.
11 Dene site parameters in the Site Window in CSS. Refer to CSS Online Help
for GCP 8000 Site Controller.
12 Dene capabilities for the channels connected to this site controller through
the Channel Window in CSS. Refer to CSS Online Help for GCP 8000 Site
Controller.1
13 Dene site controller parameters through the Site Controller Window in CSS.
Refer to CSS Online Help for GCP 8000 Site Controller.
Process 4-1 Conguration Process for the GCP 8000 Site Controller (Continued)
14 View the parameters for the site controller switch through the Site Controller
Switch Window in CSS. This applies only to the HPD and Repeater sites.
Two GCP 8000 records are automatically created for each Site record. If necessary, the
Security Group for the GCP 8000 record is changed and notes are added. Otherwise, no
conguration is necessary for the Site Controller records.
5
GCP 8000 Site Controller Optimization
This chapter contains optimization procedures and recommended settings relating to GCP
8000 Site Controller. The only process for optimizing the GCP 8000 Site Controller is
Aligning the Reference Oscillator after Installation.
After the GCP 8000 Site Controller is installed, and every two years thereafter, the reference oscillator must
be aligned. See Aligning the GCP 8000 Site Controller Reference Oscillator for detailed instructions.
Procedure 5-1 provides the instructions for adjusting the reference oscillator and align-
ing the frequency error to within 0.1 ppb.
Procedure 5-1 How to Align the GCP 8000 Site Controller Reference Oscillator
1 Measure the GTR 8000 Base Radio frequency accuracy using the procedure,
How to Measure BR Tx Power, Frequency Accuracy and Tx BER. Refer to the
manual, GTR 8000 Base Radio for these instructions.
2 After you have a frequency error on the base radio, connect to the GCP 8000 Site
Controller as follows:
1. Connect the service computer to the DB-9 service port of the site controller
using the appropriate cable.
2. Running the Conguration/Service Software (CSS) on the service computer,
select Tools, then Connection Configuration.
Result: The CSS Connection screen appears.
3. Select the Serial connection, the Serial Port and Baud Rate, and then click
Connect.
4. When the message indicates you are connected, select File, then Read
Configuration From Device.
Result: The parameters are downloaded from the site controller to the computer.
When the download is complete, the CSS main window opens.
3 From the CSS Service menu, select Reference Oscillator.
Result: The Reference Oscillator Alignment dialog box appears.
4 At the base radio, before adjusting the reference oscillator, monitor the Frequency
Error.
Procedure 5-1 How to Align the GCP 8000 Site Controller Reference Oscillator (Continued)
8 After adjusting the Freq Error to within 0.1 ppb, click Save to save the value to
the site controller conguration.
9 Close the Reference Oscillator Alignment screen.
10 Disconnect the laptop or PC from the site controller.
6
GCP 8000 Site Controller Operation
This chapter details tasks that you will perform once the GCP 8000 Site Controller is
installed and operational on your system.
The GCP 8000 Site Controller at a remote site follows the general site initialization process
illustrated in Figure 6-1, and as described in Process 6-1.
The standalone GCP 8000 Site Controller receives power from both its power supply as well
as from the GTR 8000 Base Radio connected to the AUX PWR Input port.
In a GTR 8000 Expansion Site Subsystem, the GCP 8000 Site Controller
receives power from up to six power supplies.
1 After the GCP 8000 is powered up, it enters standby mode and checks for status
messages from the redundant GCP 8000.
2 If status messages are not received before a time-out period, the GCP 8000
becomes active, monitors the LAN for base radios, and begins sending status
messages.
3 When the redundant GCP 8000 is powered up, it enters standby mode and
receives status messages from the active GCP 8000. The redundant GCP 8000
remains in standby mode.
4 When the active GCP 8000 detects a base radio on the LAN, it sends a report
status message to the base radio through the site LAN. This activity takes place
with all base radios simultaneously.
5 The base radio responds with a channel status reply to the active GCP 8000.
The base radio then begins to monitor periodic status messages from the active
GCP 8000.
6 The active GCP 8000 receives the channel status response from the base radio
and begins to send background messages to the base radio, then sends a channel
grant to the base radio.
7 The base radio enters the assigned operational state and keys up. It is now
available for operation. If the zone controller has the greatest preference setting
in ZCM the base radio may be assigned as the control channel.
In addition to the interactions at the site, there are also a number of transactions that take place between the
GCP 8000 Site Controller and master site equipment during site initialization. Process 6-2 describes these
interactions between the GCP 8000, Zone Controller (ZC), and RNG during site initialization.
Figure 6-2 illustrates the Master Site and GCP 8000 Site Controller interaction during site initialization
1 Information between the active GCP 8000 and the zone controller is exchanged
during initialization.
2 The zone controller determines whether the site transits into wide area mode.
When ready, the zone controller noties the GCP 8000 to transit to wide area
mode.
3 The GCP 8000 responds to the ZC and initiates a connection with the RNG.
4 The RNG establishes the link with the GCP 8000.
5 The GCP 8000 noties the ZC that the site is wide capable.
6 The ZC sends a wide grant message to the GCP 8000 and updates the adjacent
sites.
7 The GCP 8000 updates its system broadcast status (Network Available) and its
status message (Wide Area).
7
GCP 8000 Site Controller Maintenance
This chapter describes periodic maintenance procedures relating to GCP 8000 Site Controller.
If the station equipment is installed in a particularly dusty environment, precautions must be taken
to lter the air used for forced cooling of the station. Excessive dust drawn across and into the
station circuit modules by the cooling fans adversely affects the heat dissipation and circuit
operation. In such installation, be sure to clean or replace external ltering devices periodically.
If dust has accumulated on the fan grills, cleaning of the fan grills is recommended. When cleaning, ensure to
prevent dust from being pulled into the modules. It is recommended that a damp cloth be used to wipe the front
of the fan grills. When removing the power supply, make sure that the unit is turned off before proceeding.
After the GCP 8000 Site Controller is installed, and every two years thereafter, the
reference oscillator must be aligned.
The GCP 8000 Site Controller reference oscillator must be aligned to within 1 ppb (parts per billion). The
frequency reference used to make this alignment should be accurate to within 0.1 ppb. This accuracy
typically requires test equipment with a double oven or a Rubidium reference oscillator.
8
GCP 8000 Site Controller Troubleshooting
This chapter provides fault management and troubleshooting information relating to GCP 8000 Site Controller.
General Troubleshooting
Table 8-1 describes the steps for troubleshooting the GCP 8000 Site Controller.
Table 8-1 GCP 8000 Site Controller General Troubleshooting
Problem Troubleshooting
General connectivity 1. If you have access to the equipment, check the LEDs
problems to verify that each piece of equipment is connected and
operational.
2. In FullVision INM, check the condition of the site
controller and all associated devices and links.
3. Verify the conguration of the site controller through
ZCM and CSS. Verify that the IP address, subnet mask, and
default gateway for the site controller is correct. In ZCM, send
a diagnostic command to enable the site controller.
4.
5. Verify that the physical cabling is rmly connected and in
good condition. Check for any sharp bends or kinks in cabling.
Test suspected cabling for noise, continuity, attenuation, and
crosstalk. Replace the cabling if necessary.
6. If the connection fails to operate normally, check the
diagnostics, and if needed, contact the Motorola System
Support Center.
7. If the site controller still fails to operate properly, create a
backup of the current conguration, then reinstall the software
and recongure the site controller.
Troubleshooting Tools
Several tools are available for troubleshooting the GCP 8000 Site Controller:
FullVision INM. For more information, see Troubleshooting GCP 8000
Site Controller FullVision INM.
Zone Conguration Manager (ZCM). For more information, see Using the Zone Conguration
Manager (ZCM) to Troubleshoot the GCP 8000 Site Controller.
Conguration/Service Software (CSS). For more information, see Using Conguration/Service
Software (CSS) to Troubleshoot the GCP 8000 Site Controller.
The site controller monitors the state and activities throughout the site, and reports any relevant events
to FullVision INM. The site controller also reports the status and events of its own subcomponents
including the fan, GPS reference, internal switch, and power supply.
A failure of the power supply is reported by the base radio instead of the site controller. The
GCP 8000 Site Controller always shows the power supply as Operational or Enabled because
the actual status of the power supply is provided by the GTR 8000 Base Radio.
The colors of the icons represent a particular alarm severity level. This is documented in Table 8-2.
Table 8-2 Alarm Severity Levels
Table 8-3 shows each of the icons that appear on the FullVision INM for the GCP 8000 Site Controller.
Table 8-3 GCP 8000 Site Controller Objects in FullVision INM
Object Description
This FullVision INM icon is the container object for all GCP
8000 Site Controller devices. Double click the container object
to allow you to drill down to the site controller device, fan
module, GPS, internal switch, and power supply for the site
controller.
This FullVision INM icon represents the GCP 8000 Site
Controller device or module. The color of the object indicates
the current operational state of the site controller.
This FullVision INM icon represents the fan unit on the GCP
8000 Site Controller. The color of the object indicates the
current operational state of the fan.
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
HpdSiteController UNKNOWN No Reason Reported in FullVision
INM when the Network
Manager cannot contact the
device.
HpdSiteController ENABLED No Reason The site controller has
enabled.
HpdSiteController USER User The site controller has
DISABLED Requested disabled due to a user
request through ZCM.
HpdSiteController RESTART User The site controller is
Requested resetting due to a user
request through ZCM.
HpdSiteController INITIALIZA- No Reason The site controller is
TION initializing.
HpdSiteController CRITICAL Multiple SCs Multiple site controllers
MALFUNC- With Same SC at the site are provisioned
TION Number with the same site controller
number. Check and correct
the site controller records
in ZCM.
HpdSiteController CRITICAL Corrupt NVM A corrupt NVM failure is
MALFUNC- detected. Replace the failed
TION site controller module.
HpdSiteController CRITICAL Software The software version
MALFUNC- Version mismatch is detected.
TION Mismatch Check the software
versions through CSS
and SWDL. Reload if
necessary.
HpdSCrFan UNKNOWN No Reason Reported in FullVision
INM when the Network
Manager cannot contact the
device.
HpdSCrFan ENABLED No Reason The site controller fan
module is operational.
HpdSCrFan MAJOR MAL- Hardware The site controller fan has
FUNCTION Failure failed. Replace the fan
module.
Table 8-4 FullVision INM State/Cause Alarms GCP 8000 HPD Site Controller (Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
HpdSCrGPS UNKNOWN No Reason Reported in FullVision
INM when the Network
Manager cannot contact the
device.
HpdSCrGPS ENABLED No Reason The site controller GPS
functionality is operational.
HpdSCrGPS MAJOR MAL- Not Enough The site controller GPS
FUNCTION Satellites functionality cannot
Visible acquire enough satellites.
Check the condition of the
GPS antenna.
HpdSCrGPS MINOR MAL- Hardware A general GPS hardware
FUNCTION Failure failure is detected. Check
CSS for additional
information. Replace
the site controller module
if the problem cannot be
corrected.
HpdSCrSwitch UNKNOWN No Reason Reported in FullVision
INM when the Network
Manager cannot contact the
device.
HpdSCrSwitch ENABLED No Reason The internal switch on
the site controller is
operational.
HpdSCrSwitch CRITICAL Hardware A connectivity problem
MALFUNC- Failure between the two site
TION controller modules has
failed indicating a hardware
failure. Verify that the
modules are properly
seated in the backplane.
Check each site controller
through CSS for additional
details.
HpdSCrSwitch CRITICAL Connectivity The connectivity between
MALFUNC- Failure the site controller and
TION expansion hub switch
components has failed
indicating a potential
hardware failure. This
alarm does not apply to
HPD.
HpdSCrSwitch MAJOR MAL- Power Supply A power supply on one
FUNCTION Failure of the expansion hubs has
failed. This alarm does not
apply to HPD.
Table 8-4 FullVision INM State/Cause Alarms GCP 8000 HPD Site Controller (Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
HpdSCrSwitch MINOR MAL- Fan Failure A fan on one of the
FUNCTION expansion hubs has failed.
This alarm does not apply
to HPD.
HpdSCrPwrSupply UNKNOWN No Reason Reported in FullVision
INM when the Network
Manager cannot contact the
device.
HpdSCrPwrSupply ENABLED No Reason The site controller power
supply has enabled.
HpdSCrPwrSupply CRITICAL Input Voltage The power supply has
MALFUNC- Failure a critical input voltage
TION failure. Check the power
source and connection.
HpdSCrPwrSupply CRITICAL 29V Line The power supply has a
MALFUNC- Failure critical 29 V line failure.
TION Check CSS for additional
details. If the problem
cannot be corrected,
replace the power supply
module.
HpdSCrPwrSupply CRITICAL Power Supply The power supply has a
MALFUNC- Hardware critical hardware failure.
TION Failure Check CSS for additional
details. If the problem
cannot be corrected,
replace the power supply
module.
HpdSCrPwrSupply MAJOR MAL- Detected A battery voltage failure
FUNCTION Battery Voltage is detected. Check the
Failure connection to the battery
and replace if necessary.
HpdSCrPwrSupply MINOR MAL- Input Voltage A minor input voltage
FUNCTION Failure failure has occurred. Check
the power source and
connection.
Table 8-4 FullVision INM State/Cause Alarms GCP 8000 HPD Site Controller (Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
HpdSCrPwrSupply WARNING Power Supply The power supply fan has
MALFUNC- Fan Failure failed. Replace the power
TION supply fan.
HpdSCrPwrSupply WARNING Excessive The power supply has
MALFUNC- Battery detected that the battery
TION Temperature temperature is too high.
Check the battery cooling.
HpdSCrPwrSupply WARNING Detected The power supply has
MALFUNC- Battery Voltage detected that the battery
TION Failure voltage is too low. Charge
or replace the battery.
Alarm
Object Name Transient Alarm Text Severity
Code
HpdSiteController 0,1 No Alarm (The Site Controller never Normal
sends a trap with this value. The value is
dened in case the alarm code value is
ever polled.)
HpdSiteController 2 Active Site Controller Contention: One Major
SC temporarily loses then regained
communication with the rest of the
network. Possible network hardware
(switch/hub/cable) problem. Data services
is reset.
HpdSiteController 3 New Active Site Link (ASL): Normal Warning
when SC transitions to ENABLED and
for SWDL Install Procedure. At any other
time, indicates possible failure of previous
ASL. UNDEFINED indicates link failure
to zone controller. Current ASL is SC
number.
HpdSiteController 5 New Active Site Controller: Normal Warning
only after rst SC becomes ENABLED
and for SWDL install Procedure. At any
other time, it indicates possible failure of
previous Active SC. Data services will be
reset. New Active SC is SC number.
HpdSiteController 6 NTP Uncongured. Major
HpdSiteController 7 NTP Server Unreachable Minor
Table 8-5 FullVision INM Transient Alarms GCP 8000 HPD Site Controller (Continued)
Alarm
Object Name Transient Alarm Text Severity
Code
HpdSiteController 11 Reserved
HpdSiteController 12 New Home Channel: Normal when site Warning
rst goes into SITE TRUNKING or WIDE
TRUNKING and for SWDL Install. At
any other time, indicates possible failure
of previous Home Channel. UNDEFINED
means no Home Channel. The current
Home Channel is channel #.
HpdSiteController 13 Internal Alarm Card Not Operational: No Major
longer able to communicate to the internal
alarm card.
HpdSiteController 14 Internal Alarm Card Operational: A Normal
previously reported non-operational alarm
card is now operational.
HpdSiteController 15 ASC NTP Primary Reference: Active Warning
Site Controller is becoming NTP Primary
Reference Server for Site.
State Cause
Enabled No reason
User Disabled User Requested
Restart User Requested or SC Power up
Initialization No reason
Critical Malfunction NVM Corrupted
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
RptrSiteController UNKNOWN No Reason Reported in
FullVision INM
when the Network
Manager cannot
contact the device.
RptrSiteController ENABLED No Reason The site controller
has enabled.
RptrSiteController USER DISABLED User Requested The site controller
has disabled due
to a user request
through ZCM.
RptrSiteController RESTART User Requested The site controller
is resetting due
to a user request
through ZCM.
RptrSiteController INITIALIZATION No Reason The site controller
is initializing.
RptrSiteController CRITICAL Multiple SCs With Multiple site
MALFUNCTION Same SC Number controllers at
the site are
provisioned with
the same site
controller number.
Check and correct
the site controller
records in ZCM.
RptrSiteController CRITICAL Corrupt NVM A corrupt NVM
MALFUNCTION failure is detected.
Replace the failed
site controller
module.
RptrSiteController CRITICAL Software Version The software
MALFUNCTION Mismatch version mismatch
is detected.
Check the
software versions
through CSS and
SWDL. Reload if
necessary.
Table 8-7 FullVision INM State/Cause Alarms Repeater Site Subsystem Site Controller
(Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
RptrSCrFan UNKNOWN No Reason Reported in
FullVision INM
when the Network
Manager cannot
contact the device.
RptrSCrFan ENABLED No Reason The site controller
fan module is
operational.
RptrSCrFan MAJOR Hardware Failure The site controller
MALFUNCTION fan has failed.
Replace the fan
module.
RptrSCrSwitch UNKNOWN No Reason Reported in
FullVision INM
when the Network
Manager cannot
contact the device.
RptrSCrSwitch ENABLED No Reason The internal
switch on the
site controller is
operational.
RptrSCrSwitch CRITICAL Hardware Failure A connectivity
MALFUNCTION problem between
the two site
controller
modules has
failed indicating a
hardware failure.
Verify that the
modules are
properly seated
in the backplane.
Check each site
controller through
CSS for additional
details.
RptrSCrSwitch CRITICAL Connectivity Failure The connectivity
MALFUNCTION between the
site controller
and expansion
hub switch
components has
failed indicating a
potential hardware
failure. This alarm
does not apply to
HPD.
Table 8-7 FullVision INM State/Cause Alarms Repeater Site Subsystem Site Controller
(Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
RptrSCrSwitch MAJOR Power Supply Failure A power supply
MALFUNCTION on one of the
expansion hubs
has failed. This
alarm does not
apply to HPD.
RptrSCrSwitch MINOR Fan Failure A fan on one of
MALFUNCTION the expansion
hubs has failed.
This alarm does
not apply to HPD.
RptrSCrPwrSupply UNKNOWN No Reason Reported in
FullVision INM
when the Network
Manager cannot
contact the device.
RptrSCrPwrSupply ENABLED No Reason The site controller
power supply has
enabled.
RptrSCrPwrSupply CRITICAL Input Voltage Failure The power supply
MALFUNCTION has a critical
input voltage
failure. Check
the power source
and connection.
RptrSCrPwrSupply CRITICAL 29 V Line Failure The power supply
MALFUNCTION has a critical 29 V
line failure. Check
CSS for additional
details. If the
problem cannot be
corrected, replace
the power supply
module.
RptrSCrPwrSupply CRITICAL Power Supply The power supply
MALFUNCTION Hardware Failure has a critical
hardware failure.
Check CSS
for additional
details. If the
problem cannot be
corrected, replace
the power supply
module.
Table 8-7 FullVision INM State/Cause Alarms Repeater Site Subsystem Site Controller
(Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
RptrSCrPwrSupply MAJOR Detected Battery A battery
MALFUNCTION Voltage Failure voltage failure
is detected. Check
the connection
to the battery
and replace if
necessary.
RptrSCrPwrSupply MINOR Input Voltage Failure A minor input
MALFUNCTION voltage failure has
occurred. Check
the power source
and connection.
RptrSCrPwrSupply WARNING Power Supply Fan The power supply
MALFUNCTION Failure fan has failed.
Replace the power
supply fan.
RptrSCrPwrSupply WARNING Excessive Battery The power supply
MALFUNCTION Temperature has detected
that the battery
temperature is too
high. Check the
battery cooling.
RptrSCrPwrSupply WARNING Detected Battery The power supply
MALFUNCTION Voltage Failure has detected that
the battery voltage
is too low. Charge
or replace the
battery.
Alarm
Object Name Transient Alarm Text Severity
Code
RptrSiteController 0, 1 No Alarm (The site controller never Normal
sends a trap with this value. The value is
dened in case the alarm code value is
ever polled.)
RptrSiteController 2 Active Site Controller Contention: One Major
SC temporarily loses then regained
communication with the rest of the
Table 8-8 FullVision INM Transient Alarms Repeater Site Subsystem Site Controller (Continued)
Alarm
Object Name Transient Alarm Text Severity
Code
network. Possible network hardware
(switch/hub/cable) problem. Data services
is reset.
RptrSiteController 3 New Active Site Link (ASL): Normal Warning
when SC transitions to ENABLED and
for SWDL Install Procedure. At any other
time, indicates possible failure of previous
ASL. UNDEFINED indicates link failure
to zone controller. Current ASL is SC
number.
RptrSiteController 4 New Control Channel (CC): Normal when Warning
site rst goes into SITE TRUNKING
or WIDE TRUNKING and for SWDL
install Procedure. At any other time,
indicates possible failure of previous CC.
UNDEFINED means no CC. The current
CC is channel #:
RptrSiteController 5 New Active Site Controller (SC): Normal Warning
only after rst SC becomes ENABLED
and for SWDL install Procedure. At any
other time, indicates possible failure of
previous Active SC. Data services is reset.
New Active SC is SC number.
RptrSiteController 6 NTP Uncongured. Major
RptrSiteController 7 NTP Server Unreachable. Minor
RptrSiteController 8 Data Capability Unavailable: Normal Minor
during SWDL Install Procedure. At any
other time, indicates:
Site is not capable (due to not Wide
Trunking, Split VLAN, or reset due
to ASC contention or Rollover
Failed connection to the RNG.
Reason is: Site Not Capable,
RNG Link Down
RptrSiteController 9 Data Capability Available: Normal when Normal
site rst goes into Wide Trunking or
nishes with SWDL. At any other time,
indicates recovery from some failure that
was preventing Data Service.
Table 8-8 FullVision INM Transient Alarms Repeater Site Subsystem Site Controller (Continued)
Alarm
Object Name Transient Alarm Text Severity
Code
RptrSiteController 10 Split VLAN: Normal if performing SWDL Warning
Install Procedure. At any other time,
indicates Site Controllers (SC) VLANs
are improperly congured possibly due to:
A failed SWDL session was not
cleaned up
A new SC was installed improperly
RptrSiteController 13 Internal Alarm Card Not Operational: No Major
longer able to communicate to the internal
alarm card.
RptrSiteController 14 Internal Alarm Card Operational: A Normal
previously reported non-operational alarm
card is now operational.
RptrSiteController 15 ASC NTP Primary Reference: Active Warning
Site Controller is becoming NTP Primary
Reference Server for Site.
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
MultiSiteController UNKNOWN No Reason Reported in FullVision
INM when the Network
Manager cannot contact
the device.
MultiSiteController ENABLED No Reason The site controller has
enabled.
MultiSiteController USER User Requested The site controller has
DISABLED disabled due to a user
request through ZCM.
MultiSiteController RESTART User Requested The site controller is
resetting due to a user
request through ZCM.
MultiSiteController INITIALIZA- No Reason The site controller is
TION initializing.
Table 8-9 FullVision INM State/Cause Alarms Simulcast Site Subsystem Site Controller
(Continued)
Description/
Object Name Alarm State Alarm Cause
Troubleshooting
MultiSiteController CRITICAL Multiple SCs With Multiple site controllers
MALFUNC- Same SC Number at the site are
TION provisioned with the
same site controller
number. Check and
correct the site controller
records in ZCM.
MultiSiteController CRITICAL Corrupt NVM A corrupt NVM failure
MALFUNC- is detected. Replace
TION the failed site controller
module.
MultiSiteController CRITICAL Software Version The software version
MALFUNC- Mismatch mismatch is detected.
TION Check the software
versions through CSS
and SWDL. Reload if
necessary.
Alarm
Object Name Transient Alarm Text Severity
Code
MultiSiteController 0, 1 No Alarm (The site controller never Normal
sends a trap with this value. The value is
dened in case the alarm code value is
ever polled.)
MultiSiteController 2 Active Site Controller Contention: One Major
SC temporarily loses, then regained
communication with the rest of the
network. Possible network hardware
(switch/hub/cable) problem. Data services
is reset.
MultiSiteController 3 New Active Site Link (ASL): Normal Warning
when SC transitions to ENABLED and
for SWDL Install Procedure. At any other
time, indicates possible failure of previous
ASL. UNDEFINED indicates link failure
to zone controller. Current ASL is SC
number.
Table 8-10 FullVision INM Transient Alarms Simulcast Site Subsystem Site Controller
(Continued)
Alarm
Object Name Transient Alarm Text Severity
Code
MultiSiteController 4 New Control Channel (CC): Normal when Warning
site rst goes into SITE TRUNKING
or WIDE TRUNKING and for SWDL
install procedure. At any other time,
indicates possible failure of previous CC.
UNDEFINED means no CC. The current
CC is channel #:
MultiSiteController 5 New Active Site Controller (SC): Normal Warning
only after rst SC becomes ENABLED
and for SWDL install Procedure. At any
other time, indicates possible failure of
previous Active SC. Data services is reset.
New Active SC is SC number.
MultiSiteController 6 NTP Uncongured. Major
MultiSiteController 7 NTP Server Unreachable. Minor
MultiSiteController 8 Data Capability Unavailable: Normal Minor
during SWDL Install Procedure. At any
other time, indicates:
Site is not capable (due to not Wide
Trunking, Split VLAN, or reset due
to ASC contention or Rollover)
Failed connection to the RNG.
Reason is: Site Not Capable,
RNG Link Down
MultiSiteController 9 Data Capability Available: Normal when Normal
site rst goes into Wide Trunking or
nishes with SWDL. At any other time,
indicates recovery from some failure that
was preventing Data Service.
MultiSiteController 10 Split VLAN: Normal if performing SWDL Warning
Install Procedure. At any other time,
indicates Site Controllers (SC) VLANs
are improperly congured possibly due to:
A failed SWDL session was not
cleaned up
A new SC was installed improperly
Table 8-10 FullVision INM Transient Alarms Simulcast Site Subsystem Site Controller
(Continued)
Alarm
Object Name Transient Alarm Text Severity
Code
MultiSiteController 13 Internal Alarm Card Not Operational: No Major
longer able to communicate to the internal
alarm card.
MultiSiteController 14 Internal Alarm Card Operational: A Normal
previously reported non-operational alarm
card is now operational.
MultiSiteController 15 ASC NTP Primary Reference: Active Warning
Site Controller is becoming NTP Primary
Reference Server for Site
1 In ZCM, select the appropriate object for the device that is to have a change
of state.
2 Right-click on the record for that device, and select Diagnostics from the menu.
3 In the Diagnostics window, select the command to be sent to the device and
click Apply.
Result: The command is sent to the device. Depending on the type of command
that is sent, the result is viewed in FullVision INM.
ZCM conguration takes precedence over any conguration changes made in CSS. These
specic parameters are referred to as system-owned parameters and in CSS, they are designated
with an asterisk [*]. For example, CSS is used to temporarily modify system-owned
parameters in order to perform a test. Soon after you bring the device online, ZCM
overwrites the parameters. Refer to CSS Online Help for more details.
Table 8-11 summarizes the GCP 8000 Site Controller diagnostic options. These options apply
to site controllers in all hardware congurations, and includes the systems supported by these
congurations: HPD, Repeater Site, and Simulcast Site Subsystem.
Table 8-11 GCP 8000 Site Controller Diagnostic Options
Option Description
User Disabled Requests that the selected site controller disable. After
disabling, the site controller isolates itself from the redundant
site controller and the RNG. If the site controller was the active
site controller and the standby site controller is not isolated
from the system, then the standby site controller will become
active and take over operations at the site.
Enabled Requests that the selected site controller enable.
Restart Requests that the site controller perform a reset. The site
controller resets back in its current state.
ZCM conguration takes precedence over any conguration changes made in CSS. These
specic parameters are referred to as system-owned parameters and in CSS they are designated
with an asterisk [*]. For example, CSS is used to temporarily modify system-owned
parameters in order to perform a test. Soon after you bring the device online, ZCM
overwrites the parameters. Refer to CSS Online Help for more details.
The GCP 8000 is designed with internal diagnostic tests that occur on power up and reset. Diagnostic
tests are available for the control module and power supply. If a problem occurs during operation,
it is reported as an alarm. All alarms are stored in the Alarm Log, accessible with CSS. The alarm
log contains the name of the diagnostic test that failed and the time since the last power up. Critical
alarm conditions alarms are reported directly to the Site Control Manager.
If the active site controller fails, and the standby site controller has a connection with the master site, then a
site controller switch over occurs. During the switch over period, the standby site controller must re-initialize
and the site temporarily enters a site trunking mode. Depending on the site preferences, Mobile Subscriber
Units (MSUs) that are active on the site attempt to nd an adjacent wide area site. After the switch over is
completed, the site resumes normal operation. MSUs register with the site and resumes the data services.
During the site controller switch over process, the system exhibits characteristics that
are similar to SC-RNG, SC-BR, and SC-ZC link failures. The general sequence of
activities during GCP 8000 failure is explained below:
1. The standby site controller detects the loss of the active site controller within 150 ms.
The standby site controller begins sending TSP messages immediately after switch
over. The TSP contains new active site controller information.
2. Behavior for other devices in the system is similar to the behavior during a
SC-RNG, SC-BR, and SC-ZC link failure.
3. The new active site controller performs an initialization process (similar to the
power up initialization). During this initialization process, the base radios will
advertise that the site is in the local area mode. Depending on the site preferences,
MSUs leave the site and search for a wide area site.
4. After the base radios receive the TSP messages from the new active site controller, the base radios
clean their database, but do not dekey. The base radios then begin to accept registration requests.
5. Adjacent sites broadcasts, that the site is in wide area mode. MSUs begin to register
with the site. Any existing MSUs not registered with another site will perform another
registration as the standby site controller and active site controller do not share databases.
Holdoff timers (RRHOT and FRHOT) are used to prevent a large volume of MSUs
from trying to register with the recovered site simultaneously.
If the CSC fails when the console site is in the Wide Conventional mode, the use of conventional channel
resources at the Console Site continues. But if the CSC fails in the Site Conventional mode or before the
transition to the Site Conventional mode, the conventional channel resources at the Console Site stops operating.
If both the active and standby GCP 8000 Site Controllers fail, or if the active site controller fails and the
redundant one is isolated from the system, the site controllers are in-operational and in failsoft mode. MSUs
leave the site and attempt to register with another site that is in wide area mode. In voice systems, channels
provide limited functionality and making a call is possible using the channels working in failsoft mode.
The following are the general sequence of activities when both active and
standby GCP 8000 Site Controllers fail:
1. Channels detect the link failure within 500 ms (since TSP messages are not received from the
site controllers). All the channels at the site dekey and broadcast information ceases.
2. Behavior for other devices in the system is similar to the behavior during a
SC-RNG, SC-BR, and SC-ZC link failure.
3. MSUs that are operating on the site scan through their adjacent site list and attempt
to register with another site that is in wide area mode.
4. If one or both site controllers recover, the rst site controller to recover initializes
and becomes the active site controller. The base radios at the site will then begin to
accept registration requests and handle trafc after the site initialization has completed.
Holdoff timers (RRHOT and FRHOT) are used to prevent a large volume of MSUs
from trying to register with the recovered site simultaneously.
The GCP 8000 Site Controller uses several types of hold-off timers:
CAHOT = Channel Access Hold-Off Timer. (Used only in HPD systems.)
The CAHOT is used to determine how long a MSU holds off registering with the
system, or performing a location update under failure conditions. The CAHOT
value is one of the GCP 8000 parameters in the CSS.
FRHOT = Failure Random Hold-Off Timer. The time value broadcasted by Wide Area
sites adjacent to a failed site. The MSU must wait a random time period up to a maximum
of the FRHOT time before it registers to sites in Wide Area mode.
RRHOT = Recovery Random Hold-Off Timer. The time value broadcasted by Wide Area
sites adjacent to a site that has just recovered. The MSU is allowed to roam back to the
recovered site in a random time period based on the RRHOT time.
When a site fails, the zone controller sends a FRHOT value > 0 to an adjacent site. The GCP
8000 compares the CAHOT value and FRHOT value, and broadcasts the larger of the two. If the
default values for the hold-off timers are not changed, an MSU waits or holds off for as long as
16 minutes before resuming services. If multiple sites have failed, the FRHOT will be 16 minutes
per site. If the CAHOT value is received and the value is zero, the MSU cannot run the Access
Hold-off timer, but proceeds immediately with the registration message.
For HPD systems only:
To set the CAHOT value, perform the following calculation: the number of MSUs in the
system / 1666.7 mobility events per minute. The mobility events number is based on the
ability of the zone controller to handle up to 100,000 mobility events per hour.
For example, if the maximum number of MSUs in a system is 20,000, the
hold-off timer is calculated as follows: 20,000 MSUs / 1666.7 mobility events
per min = up to 11.9 minutes of hold-off per MSU.
Another example is a system with 1000 MSUs. In this example, the calculation is: 1000
MSUs / 1666.7 mobility events per minute = .60 minutes or 1 minute. It is important
that the CAHOT value is calculated based on the actual number of users on the system.
If the defaults are used, the length of the hold-off timer is excessive.
Motorola support centers help technicians and engineers to resolve system problems and ensure that
warranty requirements are met. Check your contract for specic warranty information.
Motorola assigns a tracking ticket number that identies each support call. This allows Motorola to track
problems, resolutions, and activities for the call. If possible, communicate the resolution and a status
of call so that the Service Support Center (SSC) notes the resolution and closes the ticket.
Because Motorola advanced manufacturing techniques and methodology require advanced test
equipment and tools, the SSC and Motorola local service centers should perform board-level repairs.
Use of Subcontractors
The Motorola System Service Subcontractor Assessment program ensures that service people contracted
by Motorola meet strict minimum requirements before they can work on any trunking systems. For
more information on this program, contact the Motorola representative.
9
GCP 8000 Site Controller FRU/FRE
Procedures
This chapter lists the Field Replaceable Units (FRUs) and Field Replaceable Entities (FREs) and
includes replacement procedures applicable to GCP 8000 Site Controller.
The following items are necessary to bring to the replacement site when replacing any
equipment in the GCP 8000 Site Controller:
Electrostatic discharge (ESD) strap (Motorola part number RSX4015A, or equivalent)
Laptop PC with Conguration/Service Software and Software Download applications installed
DB-9 straight-through serial cable
Ethernet patch cable
Crosstip and slotted screwdrivers
TORX driver set
1/2 drive torque wrench capable of torque settings to 110 inch pounds
This section covers FRU kit numbers, part numbers, and procedures for replacing the FRUs.
Component
FRU Kit Number Replacement Procedure
Type
Expansion Hub DLN6636A See procedure How to Replace the Site
Controller Module.
The site controller module can be hot swapped out without losing functionality. The redundant site
controller automatically becomes the active site controller and take over for the other site controller.
Procedure 9-1 describes how to replace a site controller module.
When replacing the module in the Simulcast Site Subsystem, use the upper
slot for the single site controller module.
Procedure 9-1 How to Replace the Site Controller Module
1 Wear an Electrostatic Discharge (ESD) strap and connect its cable to a veried
good ground. Be sure to wear this strap throughout this procedure to prevent ESD
damage to any components.
2 If the site controller module is non-operational, go to step 7.
3 Connect to the Site Controller using Conguration Service Software (CSS) in
the following way:
1. Connect a laptop PC to the service port on the front of the site controller
module using an Ethernet patch cable. The PC must be congured to
automatically receive an IP address from the network (Dynamic Host
Conguration Protocol or DHCP).
2. Open the CSS, select Tools, then Connection Configuration.
3. Click Connect.
4. In the CSS, select Tools menu, then Set Device IP Address.
5. Enter the box number (1 or 2) and click Set.
6. Enter the IP address of the site controller module to be replaced and click Set.
7. Depress the Reset button for three (3) seconds to reboot the site controller
module with the new IP address.
8. Click OK to conrm the action to reset.
16 Download and install the necessary software on the GCP 8000 Site Controller as
follows:
1. Connect the laptop PC to the port using an Ethernet patch cable.
Set the IP address of the laptop to the same subnet as the GCP 8000.
2. Open the Software Download application.
3. Select the ASTRO 25 Site Type: Voice/IVD or HPD.
4. Select the Zone, Site, and if applicable, the Subsite.
The Subsite ID is only available when the Site ID is between
164.
Result: The system connects to the specied zone and site.
For an IVD site: select both Repeater Site Controller and Site Repeater
Select the leset, click Generate to create a new component for the
imported leset, then click OK.
If you were not able to back up the conguration from the previous
site controller module, you can use the conguration from your
system build book or use the default conguration le for the site
controller module. Specic settings for the site controller module
must still be congured. Refer to CSS Online Help for GCP 8000
HPD Site Controller for detailed conguration instructions.
6. From the File menu, select Write Configuration To Device, then click OK
on the conrmation message.
Result: The conguration from the le you selected is loaded into the new site
controller module.
The GCP 8000 Site Controller has a fan assembly. To prevent overheating, this fan must
be in place at all times, except during servicing.
The GCP 8000 Fan Assembly is designed to be swapped out without shutting the power
off. The replacement fan assembly must be in place within a reasonable amount of time,
so the site controller module does not overheat and shut down.
Figure 9-2 is a photo of the fan assembly FRU. Follow Procedure 9-2 to replace the
GCP 8000 Site Controller Fan Assembly.
Procedure 9-2 How to Replace the GCP 8000 Site Controller Fan Assembly
1 Wear an Electrostatic Discharge (ESD) wrist strap and connect its cable to a
veried good ground. This strap must be worn throughout this procedure to
prevent ESD damage to any components.
2 Loosen the three captivated screws on the front of the fan assembly using a
T20 bit.
3 Using the handle on one end and the edge on the other side, gently pull the fan
assembly straight out to disengage the connector.
4 Using the guide pins and the connector on the FRU, push the new fan assembly
into place until it is secured.
5 Tighten the three captivated screws.
6 Verify that the fan assembly is operating properly, and that the Fan Alarm LED
is off. Use software tools, such as FullVision INM, to verify the status of the
equipment.
The GCP 8000 Site Controller has a power supply that is a FRU.
The GCP 8000 power supply can be swapped out without shutting the power off if the site
controller is cabled to use the Auxiliary Power input from a co-located GTR 8000 Base Radio. If
the site controller is not cabled for this, the power must be shut off to replace the FRU.
Figure 9-3 identies the power supply FRU. Follow Procedure 9-3 to replace the GCP
8000 Site Controller Power Supply.
The Power Supply module contains dangerous voltages that can cause
electrical shock to people or damage to equipment.
Procedure 9-3 How to Replace the GCP 8000 Site Controller Power Supply
1 Wear an Electrostatic Discharge (ESD) wrist strap and connect its cable to a
veried good ground. This strap must be worn throughout this procedure to
prevent ESD damage to any components.
2 Push the power button to Off on the power supply unit.
3 Loosen the two captivated screws with a T20 bit.
4 Pull on the metal handle to disengage the power supply from the backplane, and
remove it completely from the chassis.
5 Slide the FRU power supply into place, pushing gently until it seats.
6 Tighten the two captivated screws.
7 Turn On the power button, and verify that the power supply is operating properly.
The power supply Status LED is green.
The power supply Alarm LED is off.
The power supply Fan LED is off.
Use software tools, such as FullVision INM, to verify the status of the
equipment.
In a standalone GCP 8000 Site Controller, the backplane is the circuit board at the rear of the card cage,
which connects the power supply and site controller modules. Figure 9-4 shows the metal cover that must be
removed to access the backplane and the ports. The cables must be disconnected in order to remove the cover.
Figure 9-4 GCP 8000 Site Controller showing connections to backplane through backplane cover
Follow Procedure 9-4 to replace the backplane in a GCP 8000 Site Controller.
Procedure 9-4 How to Replace a Standalone GCP 8000 Site Controller Backplane
1 Wear an Electrostatic Discharge (ESD) strap and connect its cable to a veried
good ground. Be sure to wear this strap throughout this procedure to prevent ESD
damage to any components.
2 If the site controller modules are not operational, skip to step 8.
3 Connect to one of the site controller modules using Conguration/Service
Software (CSS) as follows:
Procedure 9-4 How to Replace a Standalone GCP 8000 Site Controller Backplane (Continued)
1. Connect a laptop PC to the service port on the front of the site controller
module using an Ethernet patch cable. The PC must be congured to
automatically receive an IP address from the network (Dynamic Host
Conguration Protocol or DHCP).
2. Open the CSS, select Tools menu, then Connection Configuration.
3. On the Conguration screen, under connection type, select Ethernet. Type
the appropriate IP address for the device, or use the Fetch Domain Name Server
(DNS) feature.
4. Click Connect to establish a connection with the site controller module.
5. At the success message, click OK.
4 Read the Site Controller conguration as follows:
1. From the File menu, select Read Configuration From Device.
2. At the success message, click OK.
Result: The Site Controller conguration tree displays in the left pane of the
CSS window.
5 Disable the site controller module as follows:
1. From the Service menu, select Status Panel Screen.
2. In the Service Panel dialog box, select the Site Controller tab.
3. In the User Requested Site Controller State list box, select User Disabled.
Result: The site controller module resets, and, after approximately two minutes,
becomes disabled. If this is the active site controller module, control of trunking
switches over to the redundant site controller module.
6 Disconnect the Ethernet cable from the Service port on the site controller module.
7 Repeat the steps above for the other site controller module.
8 Push the power rocker switch to Off (0) on the power supply unit.
9 Label, then disconnect all cables from the site controller backplane.
10 Remove the power supply module from the chassis as follows:
Using a T20 bit, loosen the two captivated screws on the front of the power
supply, so that they disengage from the chassis.
Pull on the metal handle to disengage the power supply module from the
backplane, and remove it completely from the chassis.
11 Remove the fan assembly unit to gain access to the site controller modules. See
Replacing the GCP 8000 Site Controller Fan Assembly for instructions on
removing the fan unit.
Procedure 9-4 How to Replace a Standalone GCP 8000 Site Controller Backplane (Continued)
12 Disengage the site controller modules from the backplane as follows:
Using a T20 bit, loosen the two captivated screws on the front of each
module, so that they disengage from the chassis.
Using their handles, gently pull the modules until they disengage from the
backplane.
13 Remove the fan cable from the backplane, accessing it from the front of the
chassis, with the backplane still secured to the chassis, as follows:
1. Follow the fan cable with your hand from its connector at the front of the
chassis to its connection to the backplane, through the card cage section from
which you removed the power supply module.
2. Remove the fan cables multi-pin connector from the backplane.
SUGGESTION
Squeeze the top and bottom of the connector and pull the connector
straight out from the backplane.
14 Using a T20 bit, remove the seven screws that secure the metal backplane cover
and the backplane circuit board to the rear of the site controller chassis.
15 Remove the metal backplane cover and the backplane circuit board.
16 Place the new backplane circuit board in the same location and orientation as the
one that you removed.
17
Seat the seven screws into the backplane circuit board and backplane
cover. Start all screws before fully securing them.
Secure the new backplane circuit board and the backplane cover to the rear of
the site controller chassis with the seven screws previously removed.
Torque to 18 +/- 2 in.-lbs.
Procedure 9-4 How to Replace a Standalone GCP 8000 Site Controller Backplane (Continued)
18 Connect the fan cable to the new backplane from the front of the chassis with the
backplane secured to the chassis, as follows:
1. Locate the port in the new backplane for the fan cables multi-pin connector.
2. Follow the fan cable with your hand from its connector at the front of the
chassis to the connector at the other end of the cable.
3. Push the fan cables multi-pin connector, with the tab up, into the correct
location in the backplane. See Figure 9-5.
19 Slide the site controller modules into the new backplane. A slight push may be
needed to engage the modules.
20 Secure the site controller modules to the chassis with the two captivated screws
on the front of each module.
21 Reinstall the fan assembly unit. See Replacing the GCP 8000 Site Controller
Fan Assembly.
22 Slide the power supply into the chassis, pushing gently until it seats in the new
backplane.
23 Tighten the two captivated screws on the front of the power supply.
24 Reconnect all cables at the rear of the site controller.
25 Set the power supply rocker switch to On (1).
Procedure 9-4 How to Replace a Standalone GCP 8000 Site Controller Backplane (Continued)
26 Enable the site controllers modules as follows:
1. Connect to one of the site controller modules, using Conguration/Service
Software (CSS).
2. From the Service menu, select Service Panel Screen.
3. In the Service Panel dialog box, select the Site Controller tab.
4. In the User Requested Site Controller State list box, select Enabled.
Result: The site controller module is enabled after approximately two minutes.
Repeat these steps for the other site controller module.
27 Disconnect the laptop PC from the site controller module.
28 Verify that the LEDs indicate the modules you removed and reinstalled are
operational.
The Status LEDs are green.
The Alarm LEDs are off.
The power supply Fan LED is off.
29 Verify proper operation using software tools, such as FullVision INM, and
Conguration/Service Software (CSS).
When an Expansion Hub is removed, the GCP 8000 Site Controller detects that the hub is not in place and
sends a switch fault to FullVision INM. When the Expansion Hub is replaced, the site controller automatically
detects the new one, enables it, and sends a message to clear the fault in FullVision INM.
Replacing an Expansion Hub only applies in a GTR 8000 Expandable Site Subsystem.
Figure 9-6 shows the Expansion Hub FRU.
The Expansion Hub can be hot swapped out without losing functionality. The redundant
Expansion Hub automatically becomes active and take over for the other Expansion Hub.
Follow Procedure 9-5 to replace the Expansion Hub.
Procedure 9-5 How to Replace the Expansion Hub
1 Wear an Electrostatic Discharge (ESD) strap and connect its cable to a veried
good ground. Be sure to wear this strap throughout this procedure to prevent ESD
damage to any components.
2 Remove the Fan assembly unit to gain access to the Expansion Hub module. See
procedure How to Replace the GCP 8000 Site Controller Fan Assembly for
instructions.
1 Wear an Electrostatic Discharge (ESD) strap and connect its cable to a veried
good ground. Be sure to wear this strap throughout this procedure to prevent ESD
damage to any components.
2 Remove the Fan assembly unit to gain access to the Expansion Hub module. See
procedure How to Replace the GCP 8000 Site Controller Fan Assembly for
instructions.
10
GCP 8000 Site Controller Reference
This chapter contains supplemental reference information relating to GCP 8000 Site Controller.
Table 10-1 illustrates the similarity across the different GCP 8000 Site Controller cong-
uration. The applicable system type is also identied.
Table 10-1 GCP 8000 Site Controller Reference Matrix
GTR
Reference GTR 8000 Expandable
Standalone 8000 Site
Information Site Subsystem
Subsystem
HPD Site Simulcast HPD Site HPD Site Repeater
Subsystem Site Subsystem Subsystem Site
Subsystem Subsystem
Reset Button Yes Yes Yes Yes Yes
GCP 8000 Yes Yes Yes Yes Yes
Site Controller
LEDs
Power Supply Yes Yes Yes Yes Yes
LEDs
Fan LEDs Yes Yes Yes Yes Yes
GPS Lightning Yes No Yes Yes No
Arrestor
Reset Button
The GCP 8000 Site Controller has a Reset button located on the nose on the front of the
device. Each site controller module has its own RESET button.
The RESET button is used to reboot the device. You must depress the button for 3 seconds or more to reset or
reboot the module. The button is set into the chassis, so it is difcult to accidentally engage.
Light Emitting Diodes (LEDs) indicate whether something is wrong or not with a device. If all LEDs are Green,
everything is ne. There is no reason for concern. Yellow warns of a potential problem that requires attention,
though not necessarily an immediate issue. Red is an immediate problem requiring immediate attention.
LED colors and states are listed here in order of severity:
Green - Good/Active
Green Flashing - Good, In progress, Standby
Yellow - Warning
Yellow Flashing - Minor
Red Flashing - Major Fault
Red - Critical
Table 10-2 identies the LEDs that are software-controlled. These LEDs apply to the different
GCP 8000 Site Controller congurations: Standalone, GTR 8000 Site Subsystem, GTR 8000
Expandable Site Subsystem, and Console Site Hardware Conguration.
The Trunking and ZC Link LEDs shown in Table 10-2 are only valid if the GCP 8000 is the Active
or Standby site controller, in a fully Enabled box state. In a Disabled or Critical Malfunction (CR
Malf) box state, the LEDs will be off. A GCP 8000 Site Controller in one of these states does
not know the state of the site nor does it try to communicate with the zone controller.
Table 10-2 GCP 8000 Site Controller Software-Controlled LEDs
Green Yel-
Application Green Yellow Red
LED Blink- low Red On Off
Use On Blinking Blinking
ing On
1 SC state Ac- Standby Dis- Critical
tive abled Malfunc-
(User tion (CR
Req) Malf)
2 RNG link Link Estab-
Up lishing
link with
RNG
3 Trunking Wide Site Local
State Area Off area (site
trunking)
4 ZC Link Ac- Standby Down
tive
Ser-
Green Green Yellow Yellow Red
LED vices Red On Off
On Blinking On Blinking Blinking
Use
5 SWDL/ Version SWDL SWDL Not in
VLAN valida- with with split SWDL
tion or common VLAN with split
auto- VLAN VLAN
VLAN
detection
6 Local (all Warning Minor Major Critical Good
hardware (such as hardware hardware hardware no
including fan un- failure failure failure faults
GPS) plugged) (such as
switch
failure)
7 HW Active
Active
LED 7, the HW Active LED, is controlled completely by the hardware. When active, it indicates
that the Site Controller has ownership of the SC shared external interfaces.
Table 10-5 Status Denitions for the GCP 8000 Site Controller Status/Alarm LEDs
Status Denitions
No Power The device is currently without power, both primary power and auxiliary
power. The No Power state is needed to tell the service technician that there
is a fundamental problem.
Lamp Test The Lamp Test state is used to verify that the indicators are operational.
Booting Up The Booting Up state indicates that the device is booting or is undergoing
diagnostics and is not yet ready to place into service. Even though no failure
or impairment is identied, the device is not ready to place into service.
Online The GCP 8000 Site Controller is fully operational, whether in Active
or Standby mode. The Online state is used to indicate that the
site controller is fully operational. It may be in a Standby mode
or In service. The Online state indicates that the site controller
should not be removed as it is possibly involved in active calls.
The Standby mode is included in this state, as it is important that a eld
technician should not remove a standby site controller without rst
informing the system of what he is about to do. This keeps the system from
switching over to the standby site controller as it is pulled from the frame.
Impaired The GCP 8000 Site Controller is not fully operational due
to internal or external causes. Some corrective ac-
tion must be taken to return to 100% functionality.
The impaired state also indicates that the current state does not
equal the User Requested State of the site. For example, a site in
the Site Trunking state due to the diagnostic state from the Network
Manager has the Online state. If the site is staying out of Wide
Trunking due to a reason other than the User Requested State,
such as zone controller Link failure, the Impaired LED will be lit.
The device state, Enabled/Disabled, is always User Requested. Therefore,
the Impaired LED is not shown for this state.
Failure This status indicates a failure that is xed only through replacement. If
something other than a hardware fault is causing the state, the status is
Impaired.
If both site controllers are disabled, one site controller still provides the site reference to the GTR
8000 Base Radio, so the channels can maintain failsoft functionality.
Switch of Active/Inactive
Description
LEDs
SW Status of connection between the active switch and the
redundant switch.
CPU Status of connection between the active CPU and the
redundant switch.
CP2 Status of connection between the active CPU and the
redundant CPU.
SVC Status of connection between the site controller and the
service computer.
Link LEDs
The Link LEDs include the LEDs associated with the Service port, Site Controller Expansion ports,
Net AUX port, and the Router port. Table 10-8 describes the Link LEDs.
Table 10-8 GCP 8000 Site Controller Link LEDs
Link Established
LED Link Inactive (assumes no Link Active
activity)
Activity LED Off Off Yellow/Amber
(yellow/amber) constant
Link LED (green) Off Green constant Green constant
The LEDs on the Expansion Hub are in the front, on the nose of the Expansion Hub.
Figure 10-2 depicts where the LEDs are found.
Table 10-10 shows how the Status and Alarm LEDs work together to indicate status on the Expansion Hub.
The Impaired State of the X-Hub indicates No Connection with the GCP 8000 Site Controller.
Table 10-10 Status/Alarm LED Assignment for the Expansion Hub
No Lamp Im-
LED Failure Online
Power Test paired
Status LED (green) Off On Off On On
Alarm LED (red) Off On On Flash Off
The POWER switch on the front of the power supply is used to enable or disable the DC outputs of the
power supply for the GCP 8000 Site Controller. The power supply has three LEDs, which provide a visual
image of the operating condition of the power supply. Table 10-11 explains power supply LEDs.
LED Explanation
Alarm Red LED: When illuminated, it indicates the power supply is no longer
operating within its design specications.
Status Green LED: When illuminated, it indicates the power supply is operating
within its design specications.
Fan Red LED: When illuminated, it indicates the fan for the power supply is no
longer functioning as per its design specications.
The fan assembly has one LED, the Fan Alarm, located on the front in the corner. The LED
provides a visual image of the operating condition of the fan assembly. Table 10-12 explains
the possible colors of the LED and what they mean.
A lightning arrestor must be installed between the GCP 8000 Site Controller and the GPS antenna. One GPS
antenna is connected to each of the GCP 8000 Site Controllers. Each antenna requires its own arrestor.
The Lightning Arrestor can be installed in an HPD supported hardware conguration, and in an ASTRO
25 Repeater Site Subsystem. The Simulcast Site Subsystem does not use the lightning arrestor.
Figure 10-3 illustrates the connections between the lightning arrestor and the GCP 8000 Site Controller.
Figure 10-4 shows one possible conguration of the connections and terminal assign-
ments for installing the lightning arrestor.
Index
GCP 8000 Conventional Site Controller GCP 8000 Site Controller (contd.)
state/cause alarms . . . . . . . . . . . . . . 8-10 FREs . . . . . . . . . . . . . . . . . . . . 9-1
transient alarms . . . . . . . . . . . . . . . 8-10 front ports . . . . . . . . . . . . . . . . . . 2-7
GCP 8000 Expansion Hub front view . . . . . . . . . . . . . . . . . . 1-1
description. . . . . . . . . . . . . . . . . . 1-10 function descriptions . . . . . . . . . . . . . 2-1
overview . . . . . . . . . . . . . . . . . . 1-10 functions . . . . . . . . . . . . . . . . . . 1-2
GCP 8000 HPD Site Controller grounding . . . . . . . . . . . . . . . . . . 3-23
state/cause alarms . . . . . . . . . . . . . . 8-6 GTR 8000 Expandable Site Subsystem . . . . 1-1
transient alarms . . . . . . . . . . . . . . . 8-9 GTR 8000 Site Subsystem . . . . . . . . . . 1-1
GCP 8000 Site Controller GTR 8000 Site Subsystem conguration . . . . 1-5
administering broadcasts function . . . . . . . 2-2 hardware congurations . . . . . . . . . . . 3-9
backplane connections . . . . . . . . . . . . 2-17 icons in FullVision INM . . . . . . . . . . . 8-5
box specic theory . . . . . . . . . . . . . . 2-1 installation guidelines . . . . . . . . . . . . 3-8
conguration . . . . . . . . . . . . . . . . 4-1 LEDs
conguration process . . . . . . . . . . . . . 4-3 status and alarm . . . . . . . . . . . . . . 10-4
Conguration/Service Software . . . . . . . . 8-20 monitoring base radios function . . . . . . . . 2-4
connections . . . . . . . . . . . . . . . . . 3-10 MOSCAD function . . . . . . . . . . . . . 2-4
context activation function . . . . . . . . . . 2-2 mounting in rack . . . . . . . . . . . . . . . 3-9
database in memory . . . . . . . . . . . . . 2-4 MSUs in memory . . . . . . . . . . . . . . 2-4
description. . . . . . . . . . . . . . . . . . 1-1 objects in FullVision INM . . . . . . . . . . 8-5
expandable site subsystem conguration . . . . 1-5 operation . . . . . . . . . . . . . . . . . . 6-1
failure . . . . . . . . . . . . . . . . . . . . 8-22 overview . . . . . . . . . . . . . . . . . . 1-1
failure of active . . . . . . . . . . . . . . . 8-21 ports . . . . . . . . . . . . . . . . . . . . 2-8
frequency reference function . . . . . . . . . 2-2 front view . . . . . . . . . . . . . . . . . 2-6
icon interaction
for GCP 8000 Site Controller . . . . . . . . . 8-5 between master site and GCP 8000 Site Controller
impaired status . . . . . . . . . . . . . . . . . 10-4 during site initialization . . . . . . . . . . 6-2
inactive memory bank internal alarm port
SWDL and GCP 8000 . . . . . . . . . . . . 2-19 connection. . . . . . . . . . . . . . . . . . 3-12
installation description. . . . . . . . . . . . . . . . . . 2-8
general safety precautions . . . . . . . . . . 3-1 internal auxiliary power. . . . . . . . . . . . . 3-22
guidelines for GCP 8000 Site Controller . . . . 3-8
standalone GCP 8000 Site Controller . . . . . 3-9