System Release 2020.1, 2019.

x
ASTRO® 25
INTEGRATED VOICE AND DATA

K Core Remote Site

Setup Guide

MAY 2022
* MN005963A01*
© 2022 Motorola Solutions, Inc. All rights reserved MN005963A01-E
MN005963A01-E
Intellectual Property and Regulatory Notices

Intellectual Property and Regulatory

Notices
Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola
Solutions computer programs. Laws in the United States and other countries preserve for Motorola
Solutions certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted
Motorola Solutions computer programs contained in the Motorola Solutions products described in this
document may not be copied or reproduced in any manner without the express written permission of
Motorola Solutions.
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 Solutions, Inc.

Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or
registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other
trademarks are the property of their respective owners.

License Rights
The purchase of Motorola Solutions 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 Solutions, except for the normal non-exclusive, royalty-free license to use that arises by
operation of law in the sale of a product.

Open Source Content

This product may contain Open Source software used under license. Refer to the product installation
media for full Open Source Legal Notices and Attribution content.

European Union (EU) and United Kingdom (UK) Waste of Electrical and
Electronic Equipment (WEEE) directive

The European Union's WEEE directive and the UK's WEEE regulation require that products sold
into EU countries and the UK must have the crossed-out wheelie bin label on the product (or the
package in some cases). As defined by the WEEE directive, this crossed-out wheelie bin label means
that customers and end-users in EU and UK countries should not dispose of electronic and electrical
equipment or accessories in household waste.
Customers or end-users in EU and UK countries should contact their local equipment supplier
representative or service centre for information about the waste collection system in their country.

Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be
applicable to or licensed for use on a specific system, or may be dependent upon the characteristics of
a specific mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola
Solutions contact for further information.
© 2022 Motorola Solutions, Inc. All Rights Reserved

2
 MN005963A01-E
Contact Us

Contact Us
The Centralized Managed Support Operations (CMSO) is the primary contact for technical support
included in your organization's service agreement with Motorola Solutions.
Service agreement customers should be sure to call the Centralized Managed Support Operations
(CMSO) in all situations listed under Customer Responsibilities in their agreement, such as:
• Before reloading software
• To confirm troubleshooting results and analysis before taking action
Your organization received support phone numbers and other contact information appropriate for your
geographic region and service agreement. Use that contact information for the most efficient response.
However, if needed, you can also find general support contact information on the Motorola Solutions
website, by following these steps:
1 Enter motorolasolutions.com in your browser.
2 Ensure that your organization's country or region is displayed on the page. Clicking or tapping the
name of the region provides a way to change it.
3 Select "Support" on the motorolasolutions.com page.

Comments
Send questions and comments regarding user documentation to
[email protected].
Provide the following information when reporting a documentation error:
• The document title and part number
• The page number or title of the section with the error
• A description of the error
Motorola Solutions offers various courses designed to assist in learning about the system. For
information, go to https://learning.motorolasolutions.com to view the current course offerings and
technology paths.

3
MN005963A01-E
Document History

Document History
Version Description Date
MN005963A01-A Original release of the K Core Remote Site Setup June 2019
Guide.
MN005963A01-B Updated sections: November 2019
• Equipment Checklist on page 16
• Setting Up the Equipment on page 17
• Equipment Setup at the Site on page 17
• Equipment Cabling on page 18
• K Core Sites Architecture with Juniper Hub/Site
Routers on page 19
• Connecting Remote Site Equipment on page 21
• Configuring Juniper SRX Routers in K Core Systems
on page 21
• Setting Up a Root Password on page 23
• Upgrading the Junos OS on Juniper SRX345 on
page 24
• Upgrading the Junos OS on Juniper SRX1500 on
page 25
• Hub Site and Sub-Site Voting Solutions on page 35
Added section: Hub Site Juniper SRX1500 Port Con-
nections on page 19
Removed section: Hub Site Juniper SRX345 Cabling

MN005963A01- Revised for system release A2020.1. June 2020

C01
MN005963A01-D Updated sections: October 2021
• Equipment Checklist on page 16
• Setting Up the Equipment on page 17
• Equipment Cabling on page 18
• K Core Sites Architecture with Juniper Hub/Site
Routers on page 19
• Connecting Remote Site Equipment on page 21
• Conventional Channel Gateway Setup on page 29
• Base Radio Site Equipment on page 33
• Setting Up Base Radios on page 34
• Hub Site and Sub-Site Voting Solutions on page 35
• Channel Configuration on page 36
Deleted section: Preparation Prerequisites, Convention-
al Base Radio Documentation

4
 MN005963A01-E
Document History

Version Description Date

MN005963A01-E Updated sections: May 2022
• Service Laptop and Software Setup on page 79
• On-Premises Software Hub Application on page 80
• Reading/Writing Configuration Files From/To a De-
vice on page 82
• SDM3000 Builder on page 82
New sections:
• Provisioning and Configuration Agent Application on
page 80
• Service Laptop Requirements on page 84

5
MN005963A01-E
Contents

Contents
Intellectual Property and Regulatory Notices.......................................................... 2
Contact Us................................................................................................................... 3
Document History....................................................................................................... 4
List of Figures..............................................................................................................8
List of Tables............................................................................................................... 9
List of Processes...................................................................................................... 10
List of Procedures.....................................................................................................11
About K Core Remote Site Setup Guide................................................................. 12
Related Information..................................................................................................................... 12
Chapter 1: K Core Remote Site Preparation......................................................... 15
1.1 R56 Compliance Audit........................................................................................................... 15
1.2 Preparing Support and Test Equipment................................................................................ 15
Chapter 2: K Core Remote Site Equipment Setup............................................... 16
2.1 Equipment Checklist.............................................................................................................. 16
2.2 Setting Up the Equipment......................................................................................................17
2.3 Equipment Setup at the Site.................................................................................................. 17
2.4 Equipment Cabling................................................................................................................ 18
2.4.1 BR Site Juniper SRX345 Port Connections............................................................. 18
2.4.2 Hub Site Juniper SRX1500 Port Connections......................................................... 19
2.5 K Core Sites Architecture with Juniper Hub/Site Routers......................................................19
2.6 Connecting Remote Site Equipment......................................................................................21
2.7 Configuring Juniper SRX Routers in K Core Systems...........................................................21
2.7.1 Assigning IP Address for Management Interface (fxp0).......................................... 22
2.7.1.1 Setting Up a Root Password...................................................................... 23
2.7.2 Upgrading the Junos OS on Juniper SRX345......................................................... 24
2.7.3 Upgrading the Junos OS on Juniper SRX1500....................................................... 25
2.7.4 Loading Juniper SRX Router Configuration Files.................................................... 27
2.7.5 Rebooting the Juniper SRX..................................................................................... 28
2.7.6 Backing Up Juniper SRX Configurations................................................................. 29
2.8 Conventional Channel Gateway Setup..................................................................................29
2.9 Remote Site LAN Switch Setup............................................................................................. 29
2.9.1 Dual Remote Site LAN Switches............................................................................. 30
2.9.2 Triple Hub Site LAN Switches..................................................................................30
2.10 Ethernet Site Links Setup.................................................................................................... 30
2.11 Dispatch Console Setup...................................................................................................... 31

6
 MN005963A01-E
Contents

2.12 Base Radio Site Equipment.................................................................................................33

2.13 Setting Up Base Radios.......................................................................................................34
2.14 Hub Site and Sub-Site Voting Solutions.............................................................................. 35
2.15 Channel Configuration......................................................................................................... 36
Chapter 3: K Core Remote Site Test and Verification......................................... 37
3.1 GTR 8000 Base Radio Test and Optimization.......................................................................37
3.1.1 Testing the GTR 8000 Base Radio Performance with a Service Monitor................ 37
3.1.1.1 System Test Pattern Deviation Standards................................................. 37
3.1.1.2 Monitoring the Power Supply Module........................................................ 38
3.1.1.3 Verifying Receiver Performance................................................................ 38
3.1.1.4 Checking Receiver Sensitivity (Self-test Method)...................................... 40
3.1.1.5 Monitoring the Transmitter Metering Points............................................... 40
3.1.1.6 Verifying Transmitter Performance............................................................ 41
3.2 Ethernet Site Link Test and Verification.................................................................................42
3.2.1 Latency.................................................................................................................... 42
3.2.2 Inter-Packet Delay Variation (Jitter)......................................................................... 42
3.2.3 Packet Loss............................................................................................................. 43
3.2.4 Ethernet Site Link Statistics for Transport Devices..................................................43
Appendix A: Site Preparation and R56 Compliance Checklist........................... 46
A.1 Site Preparation.....................................................................................................................46
A.2 R56 Compliance Checklist.................................................................................................... 47
Appendix B: Service Laptop and Software Setup................................................79
B.1 Provisioning and Configuration Agent Application................................................................ 80
B.2 On-Premises Software Hub Application................................................................................ 80
B.3 Configuration/Service Software.............................................................................................80
B.3.1 Configuration/Service Software Online Help Access...............................................81
B.3.2 Reading/Writing Configuration Files From/To a Device.......................................... 82
B.4 SDM3000 Builder.................................................................................................................. 82
B.5 Software Download Manager................................................................................................ 82
B.6 Customer Programming Software......................................................................................... 83
B.7 ESU Launchpad.................................................................................................................... 83
B.8 Service Laptop Requirements............................................................................................... 84
Appendix C: Remote Site LAN Switch Configuration Setup...............................85
C.1 Loading/Restoring the Switch Configuration File for the Remote Site LAN Switch...............85
C.2 Setting up Passwords for the Remote Site LAN Switch........................................................86
C.3 Verifying Port Status for the Remote Site LAN Switch..........................................................87

7
MN005963A01-E
List of Figures

List of Figures
Figure 1: K Core Conventional Architecture with Juniper Hub/Site Routers ......................................... 20
Figure 2: MCC 7500 Console in a K Core Hub Site .............................................................................. 33
Figure 3: LAN Switch Connections to Base Radios with the CCGW (GGM 8000 or MCG 8000) ......... 34

8
 MN005963A01-E
List of Tables

List of Tables
Table 1: R56 Compliance Audit .............................................................................................................15
Table 2: Preparing Support and Test Equipment .................................................................................. 15
Table 3: Equipment Checklist ................................................................................................................16
Table 4: BR Site Juniper SRX345 Port Connections .............................................................................18
Table 5: Hub Site Juniper SRX1500 Port Connections ......................................................................... 19
Table 6: Two Aruba 2930F 48G Switches Port Connections (Trunked) ................................................30
Table 7: Three Aruba 2930F 48G Switches Port Connections ..............................................................30
Table 8: Deviation Standards for ASTRO 25 System Test Patterns ..................................................... 37
Table 9: Example Link Planning Template ............................................................................................ 43
Table 10: General ..................................................................................................................................47
Table 11: Building Design and Installation ............................................................................................ 48
Table 12: External Grounding ................................................................................................................50
Table 13: Internal Grounding .................................................................................................................59
Table 14: Power Sources ...................................................................................................................... 66
Table 15: Transient Voltage Surge Suppression ...................................................................................71
Table 16: Equipment Installation ........................................................................................................... 74
Table 17: Audit Summary ...................................................................................................................... 77
Table 18: Installing and Upgrading the Software ...................................................................................81

9
MN005963A01-E
List of Processes

List of Processes
Setting Up the Equipment ......................................................................................................................17
Setting Up Base Radios ........................................................................................................................ 34

10
 MN005963A01-E
List of Procedures

List of Procedures
Connecting Remote Site Equipment ..................................................................................................... 21
Configuring Juniper SRX Routers in K Core Systems ...........................................................................21
Assigning IP Address for Management Interface (fxp0) ........................................................................ 22
Setting Up a Root Password ................................................................................................................. 23
Upgrading the Junos OS on Juniper SRX345 ....................................................................................... 24
Upgrading the Junos OS on Juniper SRX1500 ..................................................................................... 25
Loading Juniper SRX Router Configuration Files ..................................................................................27
Rebooting the Juniper SRX ................................................................................................................... 28
Backing Up Juniper SRX Configurations ...............................................................................................29
Monitoring the Power Supply Module ....................................................................................................38
Verifying Receiver Performance ............................................................................................................38
Checking Receiver Sensitivity (Self-test Method) ..................................................................................40
Monitoring the Transmitter Metering Points ...........................................................................................40
Verifying Transmitter Performance ........................................................................................................41
Reading/Writing Configuration Files From/To a Device ........................................................................ 82
Loading/Restoring the Switch Configuration File for the Remote Site LAN Switch ............................... 85
Setting up Passwords for the Remote Site LAN Switch ........................................................................ 86
Verifying Port Status for the Remote Site LAN Switch .......................................................................... 87

11
 MN005963A01-E
About K Core Remote Site Setup Guide

About K Core Remote Site Setup

Guide
This manual provides basic installation, configuration and optimization content to support initial setup
of equipment at Conventional Hub Sites and Conventional Base Radio Sites supported by a K core
system.

Related Information
See the following documents for associated information about the radio system.

Related Information Purpose

Standards and Guidelines for Communication Sites Provides standards and guidelines that should be fol-
lowed when setting up a Motorola Solutions communi-
cations site. Also known as R56 manual.
System Overview and Recovery Reference Guide Provides an overview of the new features, technical il-
lustrations, and system-level disaster recovery for the
ASTRO® 25 radio communication system.
Configuration Manager for Conventional Systems Covers the use of the Configuration Manager applica-
User Guide tion to set up the Conventional system parameters for
consoles, channels, user objects, and integrated data
services in K Core ASTRO® 25 systems.
DCG 9000 Feature Guide Contains detailed information on the installation, con-
figuration, and operation of the Dynamic Conventional
Gateway (DCG 9000) software and hardware. DCG
9000 provides an interface for digital, analog and IP
conventional channels and for third-party Digital Fixed
Station Interface (DFSI) stations.
Flexible Site and InterZone Links Feature Guide Describes the Flexible Site and InterZone Links fea-
ture, also referred to as Ethernet links, that provides
alternate connectivity options for linking zones and
sites in ASTRO® 25 systems.
K Core Setup Guide Provides basic installation, configuration, and optimi-
zation content to support the initial setup of equipment
at the K Core Conventional Hub Site (Hub Site loca-
tion of the Conventional Site Controller) for either a
non-redundant (K1) or redundant (K2) system.
Juniper SRX Routers and Firewalls Feature Guide This manual provides information on installation, con-
figuration, and management of the Juniper SRX ser-
ies routers used in various network locations within
the ASTRO 25 system.
GGM 8000 System Gateway Feature Guide Provides information relating to the installation, config-
uration, and management of the GGM 8000 Gateway
used in various network locations.
GTR 8000 Base Radio Feature Guide Provides descriptions of the components of the GTR
8000 Base Radio and their function, specifications for
the various configurations, and procedures on instal-

12
 MN005963A01-E
About K Core Remote Site Setup Guide

Related Information Purpose

lation, configuration, optimization, operation, trouble-
shooting, and FRU/FRE replacement.
DCG 9000 Feature Guide Contains detailed information on the installation, con-
figuration, and operation of the Dynamic Conventional
Gateway (DCG 9000) software and hardware. DCG
9000 provides an interface for digital, analog and IP
conventional channels and for third-party Digital Fixed
Station Interface (DFSI) stations.
Dispatch Console Backward Compatibility Reference Provides detailed information on the installation, con-
Guide figuration, and operation of the DSC 8000 Conven-
tional Site Controller software and hardware.
MCC 7500 Dispatch Console with VPM User Guide Describes the site-level characteristics of MCC 7500
Dispatch Console with Voice Processor Module
(VPM) feature - a high-tier, mission-critical, IP-based
radio dispatch console system.
MCC 7500E Dispatch Console User Guide Provides setup and operational details for the MCC
7500E Dispatch Console feature and describes the
requirements and considerations necessary for imple-
menting this feature in ASTRO® 25 systems.
MCG 8000 System Gateway Feature Guide Provides detailed instructions for the installation, con-
figuration, troubleshooting, and recovery of the MCG
8000 that serves as a conventional channel gateway.
MKM 7000 Console Alias Manager Online Help Provides information relating to the MKM 7000 Con-
sole Alias Manager that provides the capability to map
Unit IDs to aliases at the dispatch center level for
display on the MCC 7500 Consoles. These Unit ID-to-
alias mappings override the aliases defined for the
Unit IDs in the Provisioning Manager.
MLC 8000 Setup Guide Provides site-level information and sequences for im-
plementing the MLC 8000 device applied as an an-
alog conventional comparator for analog IP-based si-
mulcast and non-simulcast voting, and as a subsite
link converter for conventional analog, digital and
mixed mode channels.
RF Site Technician Guide Contains the installation, configuration, operation, and
maintenance procedures of the RF Site equipment in
ASTRO® 25 Core Trunking sites, including Compara-
tors, Site Controllers, Base Radios, Receivers, Refer-
ence and Transceiver Modules.
RF Site Technician Reference Guide Describes the ASTRO® site components and tools
used in their installation, configuration, and mainte-
nance in ASTRO® 25 systems, and contains referen-
tial sections that provide additional information rele-
vant when performing operations described in the RF
Site Technician Guide, including feature descriptions,
diagrams, and lists of parameters.
Software Download Manager Online Help Provides information on using the Software Download
Manager (SWDL) application to transfer and install
software in an ASTRO® 25 Repeater subsystem, a

13
 MN005963A01-E
About K Core Remote Site Setup Guide

Related Information Purpose

High Performance Data (HPD) subsystem, a Simul-
cast subsystem, an STRV Subsystem, or ASTRO® 25
Express System.
Ethernet LAN Switches Feature Guide Provides use of Hewlett-Packard (HPE) and Aruba
switches in ASTRO® 25 systems, including LAN
switches and backhaul switches. In addition to com-
mon procedures for installation, configuration, opera-
tion, and troubleshooting of the switches, this manual
provides information for specific ASTRO® 25 system
sites and features that Ethernet LAN switches can
support.
Unified Event Manager User Guide Covers the use of Unified Event Manager (UEM) that
provides reliable fault management services for devi-
ces in ASTRO® 25 systems.

14
 MN005963A01-E
K Core Remote Site Preparation

Chapter 1

K Core Remote Site Preparation

This chapter describes prerequisites and basic preparation steps for an K core remote site.
IMPORTANT: Before setting up the site, fully understand and follow all safety, training, and
certification requirements and considerations.

1.1
R56 Compliance Audit

Table 1: R56 Compliance Audit

Activity Description Reference

R56 Compli- The site should meet R56 standards The Motorola Solutions R56 Stand-
ance and be audited by an ETA-certified ards and Guidelines for Communica-
R56 auditor to verify compliance. tion Sites manual, Appendix F “R56
Compliance Checklist”
The R56 Audit Form is also includ-
ed this document. See Site Prepara-
tion and R56 Compliance Checklist on
page 46.

1.2
Preparing Support and Test Equipment
The following activities should be performed for the K core remote site.

Table 2: Preparing Support and Test Equipment

Activity Description Reference

Service Laptop A service laptop can be used to in- See Appendix Service Laptop and
Setup stall and configure components and to Software Setup on page 79 for
check component status. details regarding the hardware and
software requirements, recommenda-
tions, and considerations for a service
laptop.
Equipment Set- Equipment setup procedures are per- See K Core Remote Site Equipment
up formed in the field. Setup on page 16.
Test and Verifi- Equipment test and optimization pro- See K Core Remote Site Test and
cation cedures are performed in the field. Verification on page 37.

15
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

Chapter 2

K Core Remote Site Equipment Setup

Equipment setup in this guide covers the essential K core equipment necessary to support an ASTRO®
25 Conventional System Remote Site.
NOTE: For other equipment setup scenarios, see the ASTRO® 25 system release
documentation listed in the Appendix “Documentation List,” of the K Core Setup Guide. The
documentation is delivered with the radio system.

2.1
Equipment Checklist
Take an inventory of all equipment with a Motorola Solutions representative present to ensure that
the order is complete. Carefully inspect all equipment and accessories to verify that they are in good
condition. Promptly report any damaged or missing items to the Motorola Solutions representative.
CAUTION: Do not tamper with factory configuration settings for these devices including
software configuration, firmware release, password, and physical connections. Motorola
Solutions configured and connected these devices to meet specific performance requirements.
Tampering with these devices may result in unpredictable system performance or a
catastrophic failure.

Table 3: Equipment Checklist

K1/K2 Remote Site Components See:

Conventional Base Radios Base Radio Site Equipment on page 33
Site LAN Switch Remote Site LAN Switch Setup on page 29
Hub Router (Juniper SRX1500) Juniper SRX Routers and Firewalls Feature
Guide
BR Site Router (Juniper SRX345) Juniper SRX Routers and Firewalls Feature
Guide
LAN-based CCGW GGM 8000: GGM 8000 System Gateway Fea-
ture Guide
DCG 9000: DCG 9000 Feature Guide
2020.1:MCG 8000: MCG 8000 System Gate-
way Feature Guide

Dispatch Console Dispatch Console Setup on page 31

Conventional Comparator “K Core Equipment Setup” and “Base Radio
and Comparator Setup” sections of the K Core
Setup Guide, RF Site Technician Reference
Guide or the RF Site Technician Guide.
MLC 8000 Comparator and MLC Link Converter MLC 8000 Comparator Feature Guide

16
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

2.2
Setting Up the Equipment
The following process provides instructions for setting up the equipment at a K core remote site.
Prerequisites:
Transport devices shipped with the system can be configured for a Layer 2 or Layer 3 backhaul
network. If necessary, check with the pre-configuration setup information Motorola Solutions provided
to set up the system before shipment.

Process:
1 Prepare the site for the equipment installation.
2 Install and configure the Hub Routers. See Configuring Juniper SRX Routers in K Core Systems
on page 21.
3 Install and configure the BR Site Routers. See Configuring Juniper SRX Routers in K Core
Systems on page 21.
4 Install a LAN-based CCGW:
• For the GGM 8000, see "Conventional Channel Gateway – Installation" and "Conventional
Channel Gateway – Configuration" in the GGM 8000 System Gateway Feature Guide.
• For the DCG 8000, see "DCG 9000 Installation and Configuration" in the DCG 9000 Feature
Guide.
• 2020.1: For the MCG 8000, see "MCG 8000 Installation and Configuration" in the MCG 8000
System Gateway Feature Guide.
5 Set up the dispatch console. See Dispatch Console Setup on page 31.
6 Set up the base radio equipment. See Base Radio Site Equipment on page 33.
7 Set up the remote site LAN switch. See Remote Site LAN Switch Setup on page 29.
8 Set up the Ethernet site links. See Ethernet Site Links Setup on page 30.

2.3
Equipment Setup at the Site
Place the following equipment in an equipment rack.
See the documentation supplied with your system for basic hardware installation of the following
components:
• Juniper SRX routers – see the Juniper SRX Routers and Firewalls Feature Guide.
• LAN-based CCGW – for GGM 8000, see the "Conventional Channel Gateway – Installation" and
"Conventional Channel Gateway – Configuration" sections in the GGM 8000 System Gateway
Feature Guide, for DCG 9000, see the DCG 9000 Feature Guide.
• Site LAN Switch – see Ethernet LAN Switches Feature Guide.
• Base Radio Equipment – for a list of documents covering basic hardware installation for
conventional base radio equipment, see GTR 8000 Base Radio Feature Guide.
The following equipment is typically set up at the site without a rack.
• Dispatch Console – see MCC 7500 Dispatch Console with VPM User Guide.
NOTE: To avoid temperatures above 35°C (95°F), rack each device allowing at least one rack
unit of space above and below the device.

17
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

2.4
Equipment Cabling
After the equipment is set up and/or racked, make the cable connections. See the Cable Matrix that
came with your system.
Also, see the following sections supporting setup:
• Hub Router – see K Core Sites Architecture with Juniper Hub/Site Routers on page 19.
• BR Site/Hub Router – see K Core Sites Architecture with Juniper Hub/Site Routers on page 19.
• LAN-based CCGW:
For the GGM 8000, see "Conventional Channel Gateway – Installation" and "Conventional Channel
Gateway – Configuration" in the GGM 8000 System Gateway Feature Guide.
For the DCG 8000, see "DCG 9000 Installation and Configuration" in the DCG 9000 Feature Guide.
2020.1: For the MCG 8000, see "MCG 8000 Installation and Configuration" in the MCG 8000
System Gateway Feature Guide.
• Dispatch Console – see Dispatch Console Setup on page 31.
• Base Radio Equipment – see Base Radio Site Equipment on page 33.
• Remote Site LAN Switch – see Remote Site LAN Switch Setup on page 29.

2.4.1
BR Site Juniper SRX345 Port Connections
In the BR Sites (ASTRO® 25 core system, K1/K2 system), Juniper SRX345 can be used in single-
or dual-router configuration. Juniper SRX345 as a Site Router with Integrated Switch is supported in
non-redundant BR sites.

Table 4: BR Site Juniper SRX345 Port Connections

Router Type Port Device/Function

Site Router (single-router) ge-0/0/0 BR Site LAN Switch
ge-0/0/[1-4] Disabled
ge-0/0/5 Backhaul
ge-0/0/[6-15] Disabled
Site Router (dual-router) ge-0/0/0 BR Site LAN Switch
ge-0/0/[1-2] Disabled
ge-0/0/3 Site Router interconnection
ge-0/0/4 Disabled
ge-0/0/5 Backhaul
ge-0/0/[6-15] Disabled
Site Router with Integrat- ge-0/0/[0-4] BR Site LAN Switch, disabled if not config-
ed Switch (single-router) ured in TNCT
ge-0/0/5 Backhaul

18
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

Router Type Port Device/Function

ge-0/0/[6-15] BR Site LAN Switch, disabled if not config-
ured in TNCT

NOTE: Ports from 0/0/0 to 0/0/7 are copper ports and ports from 0/0/8 to 0/0/15 are SFP ports
that require copper transceivers.

2.4.2
Hub Site Juniper SRX1500 Port Connections
In the Csub Hub Site, Juniper SRX1500 can be used in single- or dual-router configuration.

Table 5: Hub Site Juniper SRX1500 Port Connections

Router Type Port Device/Function

Hub Site Router (single-router) ge-0/0/0 Hub Site LAN Switch
ge-0/0/[1-4] Disabled
ge-0/0/5 Backhaul
ge-0/0/[6-15] Disabled
xe-0/0/[16-19] Disabled
Hub Site Router (dual-router) ge-0/0/0 Hub Site LAN Switch
ge-0/0/[1-2] Disabled
ge-0/0/3 Hub Router interconnection
ge-0/0/4 Disabled
ge-0/0/5 Backhaul
ge-0/0/[6-15] Disabled
xe-0/0/[16-19] Disabled

2.5
K Core Sites Architecture with Juniper Hub/Site Routers
The primary function of the Hub Routers and BR Site Routers is to support Ethernet site links
interfacing with the backhaul to provided site-to-site network transport of audio (voice), data, and
control traffic. See Connecting Remote Site Equipment on page 21.

19
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

Figure 1: K Core Conventional Architecture with Juniper Hub/Site Routers

Conv (Conduit) Hub Site

Core LAN Switches

Hub
Console(s) Routers Comparator(s)

Ethernet Backhaul
Site Links Switches

Conv Hub Site Conv Hub Site

Site LAN Switches Site LAN Switches

Hub Comparator(s) Backhaul Hub Base

Console(s) Console(s)
Routers Network Routers Radio(s)

Backhaul Conventional Backhaul

Switches Site Switches
Controller

Conv Base Radio Site(s) Conv Base Radio Site(s)

Site LAN Switches Site LAN Switches

Conv Channel Site Base Conv Channel Site Base

Gateway Gateway Routers Radio(s)
Routers Radio(s)

Backhaul Base Backhaul

Base
Switches Radio(s) Switches
Radio(s)

K_Core_system_arch_conduit_hub_site_A

NOTE: Juniper SRX Routers do not support conventional channel gateway function, so
whenever you use it as a Site Router, and you need a conventional channel functionality, then
add a LAN-based Conventional Channel Gateway (CCGW) providing support for conventional
base radio and comparator equipment. See Conventional Channel Gateway Setup on page
29.
For the ASTRO® 25 K core configurations, the Hub Routers and BR Site Routers interface to the LAN
switch. See BR Site Juniper SRX345 Port Connections on page 18 and Hub Site Juniper SRX1500
Port Connections on page 19. The ASTRO® 25 K core configuration does not support a T1/E1 WAN.
The remote site router provides Layer 2 or Layer 3 routing and protocol conversion between the
remote site IP devices and the K core. The Site/Hub routers are installed in the rack with the remote
site LAN switches if needed. See Juniper SRX Routers and Firewalls Feature Guide for the site router
installation, and Ethernet LAN Switches Feature Guide for the LAN switch installation.
NOTE: Transport devices shipped with the system can be configured for a Layer 2 or Layer
3 backhaul network. If necessary, check the pre-configuration setup information Motorola
Solutions provided to set up the system before shipment.

20
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

2.6
Connecting Remote Site Equipment
This process provides the steps to set up the following types of remote site equipment: Hub Routers,
BR Site Routers and Site LAN Switches.
NOTE: Juniper SRX Routers do not support conventional gateway function, so whenever you
use it as a Site/Hub router, and you need a conventional channel functionality, then add a
LAN-based CCGW that supports conventional base radio and comparator equipment.
A K core system uses Juniper SRX routers as Hub Routers and BR Site Routers. The primary function
of the routers is to support the Ethernet site links interfacing with the backhaul switches or devices
provided for site-to-site network transport of audio (voice), data, and control traffic.
NOTE: To avoid temperatures above 35°C (95°F), rack each router allowing at least one rack
unit of space above and below.

Procedure:
1 Install the Hub Routers and BR Site Routers in the rack as required. See "Installing the Juniper
SRX Router Hardware" in Juniper SRX Routers and Firewalls Feature Guide for installation
information.
2 Connect the Juniper SRX Ethernet port to the Ethernet port of the backhaul network
demarcation point with a CAT-5e or better Ethernet cable.
The connection data is provided in BR Site Juniper SRX345 Port Connections on page 18
and Hub Site Juniper SRX1500 Port Connections on page 19. Review the Motorola Solutions
documentation to determine the appropriate port on the backhaul switch/router.
3 Connect the Hub Router and BR Site Router to the Site LAN Switch with an RJ-45 straight
through cable.
The connection data is provided in Hub Site Juniper SRX1500 Port Connections on page 19, BR
Site Juniper SRX345 Port Connections on page 18, and in the Ethernet LAN Switches Feature
Guide. Review the Cable Matrix that came with your system to determine the appropriate port
the IP device connects to on the IP LAN switch.
4 Follow the installation procedure described in Configuring Juniper SRX Routers in K Core
Systems on page 21.
5 Back up the Juniper SRX Router configuration. See Backing Up Juniper SRX Configurations on
page 29.
6 Optional: If your system configuration features a redundant site link, use another Juniper SRX
router and repeat steps 1–5.
Postrequisites:
Follow the installation procedures for the Base Radios. See GTR 8000 Base Radio Feature Guide. Use
Configuration/Service Software (CSS) / Radio Service Software (RSS) to configure the base radios.

2.7
Configuring Juniper SRX Routers in K Core Systems
Prerequisites:
See the documentation supplied with your system for basic hardware installation and "Installing the
Juniper SRX Router Hardware" of the Juniper SRX Routers and Firewalls Feature Guide.

Procedure:
1 Ensure that the Juniper SRX router hardware is installed correctly.

21
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

Juniper SRX routers staged by Motorola Solutions CCSI are preconfigured. See the
documentation supplied with your system. In other cases, follow the procedures below.
2 Upgrade the router's OS:
• For Juniper SRX345, see Upgrading the Junos OS on Juniper SRX345 on page 24.
• For Juniper SRX1500, see Upgrading the Junos OS on Juniper SRX1500 on page 25.
3 Configure the router. See Loading Juniper SRX Router Configuration Files on page 27.
4 Back up the Juniper SRX configuration. See Backing Up Juniper SRX Configurations on page
29.

2.7.1
Assigning IP Address for Management Interface (fxp0)
You can log on to the Juniper SRX devices by using the Management Interface (fxp0).
Prerequisites:
If you use the root account for the first time on the device with Junos OS release 7.6 or later, you must
set up a root password. See Setting Up a Root Password on page 23.

Procedure:
1 Connect the service laptop to the Console Port on the Juniper SRX.
2 Launch PuTTY.
3 In PuTTY, open serial connection.
Default settings for serial connection are:
<Speed>: 9600
<Data bits>: 8
<Stop bits>: 1
<Parity>: None
4 At the logon prompt, enter the user credentials.
5 Go to the configuration mode:

If… Then…
If you are in the shell mode root@%, perform the following actions:
a enter: cli
b enter: configure

If you are in the operational mode enter: configure

root@>,

6 Remove the configuration for the management port (fxp0) by entering: delete interfaces
fxp0
7 Remove all SSH configuration statements by entering: delete system services ssh
8 Provide a minimal configuration that ensures establishing an SSH session by entering: set
system services ssh
If any warning messages appear, you can ignore them.

9 Provide a new IP address configuration for the management port (fxp0) by performing one of the
following actions:

22
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

If… Then…
If Juniper SRX is not a part of the Chas- perform the following actions:
sis Cluster, a Enter:
set interfaces fxp0.0 family
inet address 172.31.255.1/24
b Verify if the commit is successful by en-
tering: commit check

If Juniper SRX is a part of Chassis Clus- perform the following actions:

ter, a Enter:
set groups node0 interfaces
fxp0 unit 0 family inet
address 172.31.255.1/24
b Enter:
set groups node1 interfaces
fxp0 unit 0 family inet
address 172.31.255.2/24
c Verify if the commit is successful by en-
tering: commit check

10 Commit configuration changes by entering: commit

11 Change the IP address configuration on the service laptop to 172.31.255.100/24
NOTE: It is not necessary to provide Default Gateway and DNS settings.

12 Connect the service laptop to the Management Interface (fxp0) on the Juniper SRX device.
NOTE: In a cluster configuration, this step is executed on the primary node.

13 Check if connectivity to Juniper SRX device is provided by entering: ping 172.31.255.1

2.7.1.1
Setting Up a Root Password
Use this procedure to set up a root password when you use the root account for the first time.

Procedure:
1 Connect the service laptop to the Console Port on the Juniper SRX.
2 Launch PuTTY.
3 In PuTTY, open serial connection.
Default settings for serial connection are:
<Speed>: 9600
<Data bits>: 8
<Stop bits>: 1
<Parity>: None
4 At the logon prompt, enter the user credentials.
5 Go to the configuration mode:
a Enter: cli

23
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

b Enter: configure
6 In the configuration mode, enter:
set system root-authentication plain-text-password
7 When prompted for a new password, enter your password.
8 When prompted to retype the new password, repeat your password.
9 Commit configuration changes by entering: commit

2.7.2
Upgrading the Junos OS on Juniper SRX345
Prerequisites:
Ensure that:
• Your service laptop runs a software client for uploading configuration files, such as WinSCP.
• You have enough space for the update on the device.
• No other update is pending on the device.
• You set up a root password. See Setting Up a Root Password on page 23.
Obtain:
• Management IP address of the SRX device. See Assigning IP Address for Management Interface
(fxp0) on page 22.
• Service laptop
• Serial cable to connect the PC to the Juniper SRX
• Junos OS update file.

Procedure:
1 Log on to the Juniper SRX with Secure Shell (SSH).
2 Enter: cli
3 Check the Juniper SRX settings:
a Check the model and the OS of the Juniper SRX by entering: show version
b Check snapshots in primary and backup partitions by entering: show system snapshot
media internal
c Check which partition is currently in use by entering: show system storage partition
4 Save a configuration rescue point by entering: request system configuration rescue
save
5 Launch WinSCP.
6 In the WinSCP Login window, perform the following actions:
a Set File protocol to SFTP.
b In the Host name field, enter the management IP address of the Juniper SRX.
c Enter the username and password.
d Click Login.
7 At the authentication prompt, click Yes.
8 Navigate to the Juniper SRX home folder by performing one of the following actions:
• If you used root as your <username>, go to /var/tmp/ folder.

24
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

• If you used a different <username>, go to /cf/var/home/<username>/ folder.

9 Perform one of the following actions:
• If you used root as your <username>, copy the OS file to the /var/tmp/ folder.
• If you used a different <username>, copy the OS file to the /cf/var/home/<username>/
folder.
10 Perform the update by performing one of the following actions:
• If you used root as your <username>, enter:
request system software add no-copy reboot /var/tmp/<JunOS file
name>
• If you used a different <username>, enter:
request system software add no-copy reboot /cf/var/home/<username>/
<JunOS file name>
where:
<username> is the login you use to connect to this Juniper SRX device
<JunOS file name> is the name of the OS file
11 If the installation is unsuccessful, you must enter one of the following commands:
• If you used root as your <username>, enter:
request system software add no-copy partition /var/tmp/<JunOS file
name>
• If you used a different <username>, enter:
request system software add no-copy partition /cf/var/home/
<username>/<JunOS file name>
where:
<username> is the login you use to connect to this Juniper SRX device
<JunOS file name> is the name of the OS file
12 When prompted to reboot the device, enter: request system reboot
13 Confirm reboot by entering: yes
14 After the reboot, log on to the Juniper SRX with SSH.
15 Verify the OS version by entering: show version
16 Copy the new Junos OS to the backup partition by entering: request system snapshot
slice alternate
17 Optional: If the configuration was lost during the upgrade, perform the following actions:
a Launch the configuration mode by entering: configure
b Load the rescue file by entering: rollback rescue
c Exit the configuration mode by entering: commit and-quit

2.7.3
Upgrading the Junos OS on Juniper SRX1500
Prerequisites:
Ensure that:
• Your service laptop runs a software client for uploading configuration files, such as WinSCP.
• You have enough space for the update on the device.
• No other update is pending on the device.

25
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

• You set up a root password. See Setting Up a Root Password on page 23.
Obtain:
• Management IP address of the Juniper SRX. See Assigning IP Address for Management Interface
(fxp0) on page 22.
• Service laptop
• Serial cable to connect the service laptop to the Juniper SRX
• Junos OS update file

Procedure:
1 Log on to the Juniper SRX with Secure Shell (SSH).
2 Enter: cli
3 Check the model of the device by entering: show version
4 Save a configuration rescue point by entering: request system configuration rescue
save
5 Launch WinSCP.
6 In the WinSCP Login window, perform the following actions:
a Set File protocol to SFTP.
b In the Host name field, enter the management IP address of the Juniper SRX.
c For Port number, leave 22.
d Enter the user name and password.
e Select Advanced.
f In the Advanced Site Settings window, select Environment→Shell.
g In the Shell field, type: start shell
h Click OK.
i Click Login.
7 At the authentication prompt, click Yes.
8 Navigate to the Juniper SRX home folder by performing one of the following actions:
• If you used root as your <username>, go to /var/tmp/ folder.
• If you used a different <username>, go to /var/home/<username>/ folder.
9 Copy the OS file to the folder by performing one of the following actions:
• If you used root as your <username>, copy the OS file to /var/tmp/ folder.
• If you used a different <username>, copy the OS file to /var/home/<username>/ folder.
10 Perform the update by performing one of the following actions:
• If you used root as your <username>, enter:
request system software add no-copy no-validate reboot /var/tmp/
<JunOS file name>
• If you used a different <username>, enter:
request system software add no-copy no-validate reboot /var/home/
<username>/<JunOS_file_name>
where:
<username> is the login you use to connect to this Juniper SRX device
<JunOS_file_name> is the name of the OS file

26
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

11 Confirm reboot by entering: yes

12 After the reboot, log on to the Juniper SRX with SSH.
13 Verify the OS version by entering: show version
14 If the configuration was lost during the upgrade, perform the following actions:
a Launch the configuration mode by entering: configure
b Load the rescue file by entering: rollback rescue
c Exit the configuration mode by entering: commit and-quit

2.7.4
Loading Juniper SRX Router Configuration Files
Prerequisites:
Obtain:
• The management IP address of the Juniper SRX
• The configuration file
NOTE: During the first installation of a new Juniper SRX, use the configuration file that was
provided with your system.
If you are recovering a Juniper SRX after a failure, a configuration file saved during the
device's initial installation may be available. You can retrieve the backup configuration file
from its storage and use it in this procedure to restore the configuration of the failed device.
Ensure that your service laptop runs a software client for uploading configuration files, such as
WinSCP.
Ensure that the Juniper firmware is up to date:
• For Juniper SRX345, see: Upgrading the Junos OS on Juniper SRX345 on page 24.
• For Juniper SRX1500, see: Upgrading the Junos OS on Juniper SRX1500 on page 25.

Procedure:
1 Launch WinSCP.
2 In the WinSCP Login window, perform the following actions:
a Set File protocol to SFTP.
b In the Host name field, enter the management IP address of the Juniper SRX.
c For Port number, leave 22.
d Enter the user name and password.
e Select Advanced.
f In the Advanced Site Settings window, select Environment→Shell.
g In the Shell field, type: start shell
h Click OK.
i Click Login.
3 At the authentication prompt, click Continue.
4 Navigate to the Juniper SRX home folder.
The default path for SRX345 devices is cf/var/home/<username>
The default path for SRX1500 devices is var/home/<username>
where <username> is the name of the user

27
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

5 Perform one of the following actions:

• If you used root as your <username>, copy the configuration file to /var/tmp/ folder.
• If you used a different <username>, copy the configuration file to the user home directory.
6 Log on to the Juniper SRX with Secure Shell (SSH), using the same user credentials.
7 Launch configuration mode by entering: configure
8 Replace all current configuration by performing one of the following actions:

If… Then…
If you use a configuration file in stanza enter: Load override <file name>
format,
If you use a configuration file in set for- perform the following actions:
mat, a Delete the current configuration by enter-
ing: Delete
b When prompted if you want to delete the
configuration, enter: yes
NOTE: If you omit this step,
the new configuration will be
merged with the current config-
uration.
c Load new configuration file by entering:
Load set <file name>

where <file name> is the name or the target location of the configuration file
9 Verify configuration by entering: Commit check
10 Commit changes and exit configuration mode by entering: commit and-quit
11 Synchronize rescue configuration with the new configuration by entering: request system
configuration rescue save
Postrequisites:
If you loaded the Juniper SRX configuration files for the first time or if you received warning that the
device requires a restart, reboot the device. See Rebooting the Juniper SRX on page 28.

2.7.5
Rebooting the Juniper SRX
Prerequisites:
Obtain:
• Juniper SRX admin login and password
• Service laptop
• Serial cable to connect the service laptop to the Juniper SRX

Procedure:
1 Connect the service laptop to the serial port of the Juniper SRX.
2 Launch a terminal emulation program.
3 Open a console connection to the Juniper SRX with the following parameters:
• Baud rate: 9600

28
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

• Bits: 8
• Parity: N
• Stop Bit: 1
• Flow control: 1
4 Log on to the Juniper SRX.
5 At the command line prompt, enter: request system reboot
6 If prompted for confirmation, enter: yes
7 Close the console.

2.7.6
Backing Up Juniper SRX Configurations
Procedure:
1 Log on to the Juniper SRX with Secure Shell (SSH).
2 Back up the current configuration by entering:
show configuration | save <file name>
where <file name> is the name or the target location of the backup file.
3 Copy the backup file to a local machine.

2.8
Conventional Channel Gateway Setup
See the documentation supplied with your system for basic hardware installation of the site
components.
Depending on the hardware, see the details for setting up a Conventional Channel Gateway (CCGW)
in the following manuals:
• For the GGM 8000, see "Conventional Channel Gateway – Installation" and "Conventional Channel
Gateway – Configuration" in the GGM 8000 System Gateway Feature Guide.
• For the DCG 8000, see "DCG 9000 Installation and Configuration" in the DCG 9000 Feature Guide.
• 2020.1: For the MCG 8000, see "MCG 8000 Installation and Configuration" in the MCG 8000
System Gateway Feature Guide.

2.9
Remote Site LAN Switch Setup
Basic configuration setup activities for the Remote Site LAN Switch include the following:
• Load the switch configuration file
NOTE: If Motorola Solutions staged the remote site LAN switch, it is configured.

• Set up passwords
• Verify port status
NOTE: See Appendix Remote Site LAN Switch Configuration Setup on page 85 for the
detailed procedures.
See the Ethernet LAN Switches Feature Guide for more information.

29
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

2.9.1
Dual Remote Site LAN Switches
If additional site LAN switch is required, interface the two switches as described in the following table.

Table 6: Two Aruba 2930F 48G Switches Port Connections (Trunked)

Switch Port Connections

1 Port 49 connects to port 50 on switch 2
2 Port 49 connects to port 50 on switch 1

2.9.2
Triple Hub Site LAN Switches
If additional site LAN switches are required, interface the three switches as described in the following
table.
In a configuration with three switches, switch 1 and 3 form a stack. Switch 2 is trunked to them.

Table 7: Three Aruba 2930F 48G Switches Port Connections

Switch Port Connection Port Connection Port Connection

1 (stack member 1) Port 51 connects to Port 52 connects to Port 49 connects to
port 51 on switch 3 port 52 on switch 3 port 49 on switch 2
(stack) (stack) (trunk)
2 Port 49 connects to Port 50 connects to
port 49 on switch 1 port 50 on switch 3
(trunk) (trunk)
3 (stack member 2) Port 51 connects to Port 52 connects to Port 50 connects to
port 51 on switch 1 port 52 on switch 1 port 50 on switch 2
(stack) (stack) (trunk)

2.10
Ethernet Site Links Setup
Review the following assumptions and considerations to set up Ethernet links:
• Ethernet network connectivity to the provider backhaul network is functional at the site.
• The site gateway transport device is available and cabled to the Ethernet backhaul switch/router.
For details for setting up Ethernet site links, see the following manuals:
• Juniper SRX Routers and Firewalls Feature Guide
• Ethernet LAN Switches Feature Guide

30
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

• Flexible Site and InterZone Links Feature Guide

NOTE: In the manuals listed, the following do not apply to a K core system:
• Core routers
• Exit routers
• Zone Core Protection
• S6000 routers
• Unified Network Configurator (UNC Wizard or EMC® Smarts®) procedures
• T1/E1
• Cooperative WAN Routing (CWR)

2.11
Dispatch Console Setup
If a console is installed at a remote site (a hub site other than the core), allocate the space needed
for the console. Un-pack the console computer and Voice Processor Module (VPM). The console
ships pre-installed and configured from the factory. Use the manuals for the console and VPM to
connect the monitor, keyboard, mouse, speakers, microphone, and AC power. One end of an RJ-45
straight-through cable is connected to the console computer, and the other end to the remote site LAN
switch (see the Cable Matrix that came with your system for the specific connection for the console and
VPM to the LAN switch). One end of another RJ-45 straight-through cable is connected to the VPM,
and the other end to the remote site LAN switch. Repeat these connections for each console at this
remote site.
NOTE: For a K2 system with redundant site links, the factory determines which LAN switch the
consoles interface with and balance them across the LAN switches.
The 7500E consoles can be installed at a Conventional Hub Site (K core) inside the Radio
Network Infrastructure (RNI) or outside the RNI using the PRX 7000 Console Proxy in the
Conventional Hub Site.
The following console components are supported in the K core system:
MCC 7500 Dispatch Console
The MCC 7500 Dispatch Console is a personal computer-based console allowing dispatch console
operators the ability to monitor and control conventional channel resources. The MCC 7500 Elite
Admin software is used to set up and configure the dispatch console position for each user. The
MCC 7500 Elite Dispatch software provides the Graphical User Interface (GUI) for the console
operator.
Voice Processor Module
The VPM combines the functions of a voice card and encryption card for the MCC 7500 Dispatch
Console. The VPM provides the interfaces to connect analog devices to the MCC 7500 digital
console. It is responsible for audio routing between the dispatch operator, peripherals, and the local
network. It contains both digital and analog (audio) circuits to support the secure and clear voice
processing.
VPM Peripherals
Various peripheral devices can interface with the VPM to support dispatch console operations. The
VPM supports the following peripheral devices:
• Desktop Speaker (qty 8)
• Desktop Microphone
• Third Party Microphone
• Footswitch
• Instant Recall Recorder Ports

31
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

• External Paging Encoder Port

• Local Logging Recorder Port
• Headset Jacks (qty 2)
• Telephone/Headset Port
• Four local AUX I/O outputs
MCC 7500E Console USB Audio Interface Module (AIM)
Provides a peripheral interface and ports to accommodate the following accessories:
• USB Speaker (qty 8)
• Push-to-Talk (PTT) footswitch
• Desk Microphone
• Headset Jacks (qty 2)
• External Paging Encoder
• External Phone Interface Port
• Local Logging Recorder Port
• Four local AUX I/O outputs
MCC 7500E Enhanced Instant Recall Recorder (EIRR)
The equivalent is MCC 7500 VPM Console IRR. The MCC 7500E Console can record any
combination of the following audio sources:
• Received audio on the currently selected channels
• Transmitted microphone audio to currently selected and unselected channels
• Any tones the dispatch console generates that appear in its speakers
NOTE: Accessories used with the USB AIM can be the same accessories used with the MCC
7500 Dispatch Console. For details, see the MCC 7500 Dispatch Console with VPM User
Guide, or MCC 7500E Dispatch Console User Guide. For details regarding the use of the
Console Alias Manager, see the MKM 7000 Console Alias Manager Online Help.

32
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

Figure 2: MCC 7500 Console in a K Core Hub Site

2.12
Base Radio Site Equipment
Remote Base Radio sites in an K core system support various conventional base radios:
• GTR 8000 Base Radio
• GPW 8000 Receiver
NOTE: For information about Radio Frequency Distribution System (RFDS) equipment shipped
with your system, see the RF Site Technician Guide and RF Site Technician Reference Guide.
Comparators are not supported at Base Radio sites in a K core system. Comparators are supported at
Conventional Hub sites in a K core system. For more information, see Hub Site and Sub-Site Voting
Solutions on page 35.
GTR 8000 Base Radios should be connected to the LAN switch if they need configuration using a LAN
connection instead of local connection to the device.
GGM 8000 devices can be used as Core Gateways or Conventional Channel Gateways (CCGW).
Juniper SRX Routers cannot be used as CCGWs. Additional CCGWs can be GGM 8000, or MCG
8000, or DCG 9000.
GGM 8000 are used as a CGGW in 2020.1 and 2019.x system releases.
MCG 8000 is used as a CCGW in 2020.1 system release.

33
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

Figure 3: LAN Switch Connections to Base Radios with the CCGW (GGM 8000 or MCG 8000)
Exemplary configuration

IP-Based GTR 8000

Remote Site LAN Switch

Conventional Channel Gateway (GGM8000 or MCG 8000)

V.24 12D 7B 12C 12B 12A 11B6B 11A CCGW-HD
8D
Audio, E&M
13D8C 13C8B 13B8A 13A 7A 6A10B 10A
Module
Analog I/O Port
Status
Encrypt
A SYSTEM
B Run
C 5B 5A 4 3 2 1
Console
9D 9C 9B 9AD 8D 8C 8B 8A 7B 7A 6B 6A Carrier Carrier Load
Alarm Alarm Status Test Forward
Active Power
Lpbk Lpbk
/Power /Fault
Reset

Digital GTR 8000

POWER
POWER

ALARM ALARM

STATUS STATUS

FAN FAN
OFF ON OFF ON

Mixed Mode GTR 8000

Analog GTR 8000

POWER

ALARM

STATUS

FAN
OFF ON

2.13
Setting Up Base Radios
Process:
1 Install the CCGW in the rack:
• For the GGM 8000, see "Conventional Channel Gateway – Installation" in the GGM 8000
System Gateway Feature Guide.
• For the DCG 8000, see "DCG 9000 Installation and Configuration" in the DCG 9000 Feature
Guide.
• 2020.1: For the MCG 8000, see "MCG 8000 Installation and Configuration" in the MCG 8000
System Gateway Feature Guide.
2 Connect the CCGW to the LAN switch:
• For the GGM 8000, see Base Radio Site Equipment on page 33.
• 2020.1: For the MCG 8000, see Base Radio Site Equipment on page 33.
• For the DCG 8000, see "DCG 9000 Installation and Configuration" in the DCG 9000 Feature
Guide.
3 For IP devices (IP-based GTR 8000 Base Radios and comparators), use an RJ-45 straight-
through cable for each IP device. Connect one end of the cable to the IP device and the other

34
 MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

end to the IP LAN switch. See the Cable Matrix that came with your system for the specific LAN
switch port used for each base radio and comparator.
4 For other GTR 8000 Base Radios, connect the base radios to the CCGW:
• For the GGM 8000, see "Conventional Channel Gateway – Installation" in the GGM 8000
System Gateway Feature Guide.
• For the DCG 9000, see "DCG 9000 Installation and Configuration" in the DCG 9000 Feature
Guide.
• 2020.1: For the MCG 8000, see "MCG 8000 Installation and Configuration" in the MCG 8000
System Gateway Feature Guide.
See the Cable Matrix that came with your system for the specific port used for each base radio.
5 Connect the CCGW and Base Radios to an AC power source.
6 Use the Configuration/Service Software (CSS) or Radio Service Software (RSS) to configure
the base radios and comparators. To get started with devices supported by CSS, see
“Connecting to a Device Through a Serial Connection” and “Setting a Device's IP Address”
in the Configuration/Service Software (CSS) Online Help. Also see the configuration information
in:
• RF Site Technician Guide
• RF Site Technician Reference Guide
7 Configure the site and channels. See the Configuration Manager for Conventional Systems User
Guide Online Help. For simulcast or voting systems, see Channel Configuration on page 36.
8 Configure subscriber records/access. See the Configuration Manager for Conventional Systems
User Guide Online Help.

2.14
Hub Site and Sub-Site Voting Solutions
A conventional IP simulcast, multicast, or voting sub-site interfaces to the site where the comparator
is located (Conventional Hub Site or prime site) via the customer IP network. The IP network can be
an Ethernet switch, router, or firewall with Point-to-Point radios, an Ethernet switch, or a router from a
service provider, or the customer network with an Ethernet switch, router, or firewall.
NOTE: Juniper SRX Routers do not support conventional gateway function, so whenever you
use it as a Hub/BR Site router, and you need a conventional channel functionality, then add a
LAN-based Conventional Channel Gateway (CCGW) that supports conventional base radio and
comparator equipment.
The Site Router at the sub-site provides one WAN interface that needs connectivity to the
Conventional Hub Site or prime site where the comparator is located.
The Hub Router at the prime site (conventional hub site with a LAN-based CCGW and comparator)
provides one WAN interface that needs connectivity to the sub-sites.
A receive-only sub-site requires only one Site Router. Digital IP GTR 8000 Base Radios at the prime
site (conventional hub site with comparator) do not require an additional CCGW.
When connecting the prime site to multiple sub-sites, an Ethernet switch can be used. For various
topologies, including support for 64 sub-sites, see:
• MLC 8000 Setup Guide
• RF Site Technician Guide
• RF Site Technician Reference Guide
For comparator equipment, see the K Core Setup Guide.

35
MN005963A01-E
Chapter 2 : K Core Remote Site Equipment Setup

2.15
Channel Configuration
After the sub-site base radios are installed and configured using Configuration/Service Software
(CSS) or Radio Service Software (RSS), the Comparators are installed and configured using CSS
or RSS. After the network from the base radios at the sub-site to the comparators at the prime site
is operational, the channels must be configured from the Configuration Manager. The comparators
are associated with a channel for a Conventional Channel Gateway (CCGW) which displays as a
conventional site in the Configuration Manager. See the Configuration Manager for Conventional
Systems User Guide and online help for configuring the conventional site and conventional channel.

36
 MN005963A01-E
K Core Remote Site Test and Verification

Chapter 3

K Core Remote Site Test and

Verification
Before system test and optimization activities, properly prepare and set up the site and site equipment,
and address all safety and installation considerations and requirements.

3.1
GTR 8000 Base Radio Test and Optimization
The GTR 8000 Base Radio is optimized at the factory and configured using Configuration/Service
Software (CSS). This section describes activities that support test and optimization for the GTR 8000
Base Radio at the ASTRO® 25 Conventional Remote Site.

3.1.1
Testing the GTR 8000 Base Radio Performance with a Service
Monitor
Use a service monitor to test and measure the transmitter and receiver characteristics of a Base Radio.
The service monitor may be connected to a Base Radio to perform tests and measurements designed
to determine whether the equipment is operating within specifications.
The sections that follow contain procedures performed when you first set up your system, and can be
scheduled on a regular basis as part of the maintenance policies of your organization. Topics covered
include:
• System Test Pattern Deviation Standards on page 37
• Monitoring the Power Supply Module on page 38
• Verifying Receiver Performance on page 38
• Checking Receiver Sensitivity (Self-test Method) on page 40
• Monitoring the Transmitter Metering Points on page 40
• Verifying Transmitter Performance on page 41

3.1.1.1
System Test Pattern Deviation Standards
Table 8: Deviation Standards for ASTRO 25 System Test Patterns on page 37 lists the deviation
standards for each ASTRO® 25 system test pattern.
NOTE: The specifications in this table allow a spread of ±10%. However, the accuracy of the
service monitor must be considered. Because the accuracy of the service monitor is ±5%, the
allowable spread in the measured deviation is ±5% and not ±10%.

Table 8: Deviation Standards for ASTRO 25 System Test Patterns

Minimum Devia- Nominal Devia- Maximum Devia-

Signal
tion tion tion
low signal deviation 0.84 kHz 0.93 kHz 1.02 kHz

37
MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

Minimum Devia- Nominal Devia- Maximum Devia-

Signal
tion tion tion
sow signal wide pulse deviation undetermined 1.00 kHz undetermined
standard deviation 2.55 kHz 2.83 kHz 3.11 kHz
standard wide pulse deviation undetermined 3.00 kHz undetermined
V.52 deviation 2.91 kHz 3.23 kHz 3.55 kHz
V.52 wide pulse deviation undetermined 3.00 kHz undetermined
C4FM deviation 2.91 kHz 3.23 kHz 3.55 kHz
C4FM wide pulse deviation undetermined 3.00 kHz undetermined
ASTRO® 25 system voice 3.24 kHz 3.60 kHz 3.96 kHz
®
ASTRO 25 system-wide pulse undetermined 3.00 kHz undetermined

3.1.1.2
Monitoring the Power Supply Module
When and where to use: Use this procedure to monitor the power supply module in the base radio.

Procedure:
1 Connect to the base radio in Configuration/Service Software (CSS) through an Ethernet
connection.
2 From the menu, select Service→Metering Screens.
The Metering Screen window opens on the Power Supply tab.

3.1.1.3
Verifying Receiver Performance
When and where to use: Use this procedure to verify receiver performance by measuring the Bit Error
Rate (BER) and Received Signal Strength Indication (RSSI) for the base radio.

Procedure:
1 Make the following connections to the base radio:
a Disconnect the BNC antenna cable from the Receive Antenna Port.
b Connect the service monitor GEN port to the base radio Antenna Port with a BNC connector.
2 Set up the service monitor:
a Set modulation to Project 25 (C4FM) with a Standard 1011 or 1031 test pattern.
b Set the service analyzer to generate at the receive frequency.
c Set the RF level an initial value of -47 dBm.
3 Connect to the base radio through an Ethernet connection.
NOTE: If Configuration/Service Software (CSS) requires a file transfer (FTP or SFTP)
from the device, a login prompt is displayed. Enter the Username and Password in the
pop-up window. Click OK.
4 From the menu, select Service→Test And Measurement Screen.
5 Select the ASTRO BER & RSSI Report tab.
6 If the base radio is not in service mode perform the following, otherwise go to step 7.

38
 MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

a Click Change to Service Mode.

b On the confirmation dialog box, click OK.
The base radio halts activity in the current mode and switches operation to the requested
mode.

c Open the Test And Measurement Screen as described in step 4.

7 Set up the test in CSS:
a In the Pattern Type field, select Project 25
b In the Sampling Period (sec) list box, enter the number of required seconds.
The time specifies the window over which the BER is calculated.
c For BER measurement, in the Rx Branch for BER Test field, select the receive branch.
The available selections for Rx Branch for BER Test are dependent on the set Pattern
Type.
8 Measure the BER and RSSI.
a Click Start BER Measurement or Start RSSI Measurement.
The Test And Measurement Screen dialog box displays the following results:
• BER results in percentage
• RSSI results expressed in dBm
NOTE: With the initial setting of the service monitor set for a carrier level of -47 dBm,
you should expect a BER of 0.0 % and an RSSI level between -49 dBm and -45
dBm. Compensate for the loss of the cable connecting the service monitor to the base
radio.

b To create a log file for the BER and RSSI measurement, click Start Log.
The Log Save As window appears.

c Change the RF level and read the BER and RSSI again at the level appropriate for the base
radio. The value should be less than 5% – GTR 8000 Base Radio Standalone at -118 dBm.
d Key the transmitter in the base radio and readjust the generator output level until 5% BER is
indicated on the service analyzer. Record this level.
Less than 1 dB of degradation should occur due to the transmitters being keyed.

e Dekey the transmitter.

f Click Stop BER Measurement or Stop RSSI Measurement to stop the test.
9 If no further testing is needed, place the base radio into normal mode, as follows:
a Click Change to Normal Mode.
b At the confirmation screen, click OK.
The base radio halts activity in the current mode and switches operation to the requested
mode.

10 Remove and restore the following connections to the base radio:

a Remove the service monitor GEN port connection from the base radio Antenna Port.
b Restore the antenna connection to the Receive Antenna Port.

39
MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

3.1.1.4
Checking Receiver Sensitivity (Self-test Method)
When and where to use: Use this procedure to check the Integrated Voice and Data (IV&D) receiver
sensitivity for the station without any test equipment. The receiver uses a factory calibrated, low-level
noise source at the receiver input to check performance. This procedure can be performed remotely.

Procedure:
1 Connect the transceiver module in Configuration/Service Software (CSS) through an Ethernet
connection.
2 From the menu, select Service→Test And Measurement Screen.
3 Select the ASTRO BER & RSSI Report tab.
4 If the base radio is not already in Service Mode perform the following substeps, otherwise go to
step 5.
a Click Change to Service Mode.
b On the confirmation dialog box, click OK.
The base radio halts activity in the current mode and switches operation to the requested
mode.

c Re-open the Test And Measurement Screen dialog box as described in step 2.
5 Select Start Receiver Test.
A confirmation dialog box appears indicating test progress. After a few seconds, the test
concludes with a pass or fail message.

6 Click OK.
7 If no further testing is needed, place the base radio in Normal Mode, as follows:
a Click Change to Normal Mode.
b On the confirmation dialog box, click OK.
The base radio halts activity in the current mode and switches operation to the requested
mode.

3.1.1.5
Monitoring the Transmitter Metering Points
When and where to use: Use this procedure to monitor the transmitter metering points in the base
radio.

Procedure:
1 Connect to the transceiver module in Configuration/Service Software (CSS) through an Ethernet
connection.
2 From the menu, select Service→Metering Screens.
The Metering Screen dialog box appears.

3 Click Transmitter Test to briefly key up the transmitter.

The status bar on the window confirms whether the transmitter is operating properly or it has
failed. The Current column displays the values read from the individual station for the following:
• Station Forward Power (Watts)
• Station Reflected Power (Watts)

40
 MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

• Station Voltage Standing Wave Ratio (VSWR)

3.1.1.6
Verifying Transmitter Performance
When and where to use: Use this procedure to verify that the base radio transmitter meets the
ASTRO® 25 system standards. Force the base radio to transmit a V.52 standard test pattern. This
procedure explains how to test the transmitter signaling patterns.

Procedure:
1 Connect to the transceiver module in Configuration/Service Software (CSS) through an Ethernet
connection.
2 From the menu, select Service→Test and Measurement Screen.
3 If the base radio is not already in Service Mode perform the following substeps, otherwise go to
step 4.
a Click Change to Service Mode.
b At the confirmation screen, click OK.
The base radio halts activity in the current mode and switches operation to the requested
mode.

c Re-open the Test and Measurement Screen, as described in step 2.

4 Connect the service monitor to the base radio:
a Remove the N-Type connector from the Transmitter Antenna Port.
b Connect an N-to-N cable from the Transmitter Antenna Port to the T/R port of the service
monitor.
c Make the following settings on the service analyzer:
• Click Receiver (TX Test).
• Enter the receive frequency to match that of the base radio TX channel selected.
• Click INPUT PORT. Set to T/R.
• Click ATTEN Set to 20 dB.
• Click DEMOD Set to P25.
• Click IF BW Set to 12.5 kHz.
• Click RF GEN to turn OFF the Signal Generator Output.
d Click Options. Enable and make the following selections in the Spectrum Analyzer, EVM
Data, Power Meter, and Modulation Plot, as follows:
• Expand the Power Meter. Set to AR (Autorange). If necessary, change to 0. Press
RETURN. Verify that Cable Loss is 0. If cable loss is anticipated, expand the Power Meter
and enter the cable loss factor.
• Set the RF Error Meter to AR (Autorange).
• Set the Modulation Meter to AR (Autorange).
5 Set up the test in CSS by selecting V.52 in the Pattern Type field.
6 Click Start Pattern Transmission.
The service monitor displays:
• The test pattern on the modulation scope.

41
MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

• The amount of deviation of the carrier.

• The Modulation Fidelity as a percentage.
• The transmitter carrier frequency error.

7 Record the Bit Error Rate (BER), Modulation Fidelity Error, Symbol Deviation, and Carrier
Error and FREQ readings from the P25 Uplink Data (in the Options menu) for use in digital
Receiver Testing.
8 Click Stop Pattern Transmission to turn off the test tone.
9 Disconnect the service monitor and reconnect the transmit antenna.
10 If no further testing is needed, place the base radio to normal mode, as follows:
a Click Change to Normal Mode.
b At the confirmation screen, click OK.
The base radio halts activity in the current mode and switches operation to the requested
mode.

3.2
Ethernet Site Link Test and Verification
With Ethernet site links, network-introduced jitter can cause link delays which may result in packet loss.
See Latency on page 42, Inter-Packet Delay Variation (Jitter) on page 42, Packet Loss on page 43,
and Ethernet Site Link Statistics for Transport Devices on page 43.
NOTE: For the details regarding Ethernet Site Links, see the following manuals:
• Juniper SRX Routers and Firewalls Feature Guide
• Ethernet LAN Switches Feature Guide
• Flexible Site and InterZone Links Feature Guide
• GGM 8000 System Gateway Feature Guide (systems with MNRs)

3.2.1
Latency
Latency does not affect speech quality up to a certain point. However, it directly impacts system
access time, which manifests itself as truncation and audio throughput delay. Latency must be
understood and quantified for each Ethernet link on the system to meet the system access time
requirements. In addition, the difference between the source and destination links must also be taken
into account since asymmetry may be an additional source of truncation.

3.2.2
Inter-Packet Delay Variation (Jitter)
Inter-packet delay variation, also known as jitter, refers to the variation in latency. Audio performance
relies on a constant, steady delivery of voice packets from the source to all the destinations. The
ASTRO® 25 system can tolerate certain amounts of jitter by using packet hold-off timers referred to as
jitter buffers.
Specifications are established for the amount of jitter that an ASTRO® 25 system can tolerate to ensure
a low probability of exceeding the jitter buffers.

42
 MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

3.2.3
Packet Loss
Packet loss may result from exceeding jitter budgets or an actual packet loss in the network. IP-based
networks are susceptible to packet loss or transient congestion, primarily due to routing component
loading or route convergence on failures. Unlike jitter, packet loss cannot be mitigated and has an
immediate impact on speech quality. The probability of packet loss must be kept low to prevent site
backhaul sourced audio quality issues. The table provides an example of a link planning template.

Table 9: Example Link Planning Template

Maxi-
mum
High
Total backhaul
Re- Priority Maxi-
Site Mini- Laten- Maxi- conges-
Zon mote Mini- mum
Num- mum cy (De- mum tion /
e Site mum Packet
ber Band- lay) Jitter outage
Type Band- Loss
width to avoid
width
site
trunking
1 MCC75 1 384 256 20 ms 10 ms 0.03 % 1.2 s
00 kbps kbps
1 Repeat- 4 512 384 25 ms 8 ms 0.02 % 2s
er kbps kbps
2 IP 5 768 620 10 ms 11 ms 0.02 % 2s
Prime kbps kbps
2 IP Sub- 5–1 512 256 10 ms 10 ms 0.02 % ms
site kbps kbps
... ... ... ... ... ... ... ... ...

3.2.4
Ethernet Site Link Statistics for Transport Devices

Ethernet Link Performance Monitoring (TWAMP)

Juniper SRX Routers in ASTRO systems use the Two-Way Active Measurement Protocol (TWAMP)
for performance monitoring of the link characteristics for the Ethernet Site Link. The TWAMP,
described in RFC 5357, defines the open protocol for measuring the network performance between
any two devices that support the TWAMP protocol.
NOTE: For details on link performance monitoring options of Juniper SRX Routers refer to the
relevant sections of the "Juniper SRX Router Reports" chapter in the InfoVista User Guide.
The generic TWAMP architecture is comprised of two hosts with specific roles.
TWAMP Client:
• Sets up, starts and stops the TWAMP test sessions.
• Creates TWAMP test packets and send it to the TWAMP Server.
• Collects and measures the link performance for different parameters.
• Sends alarm traps when the performance statistics exceed defined thresholds.
TWAMP Server:

43
MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

• Manages one or more sessions with the TWAMP clients and listens for control messages on a TCP
port.
• Sends back a measurement packet for the received test packet, but does not maintain a record of
such information.

TWAMP Framework in ASTRO 25 System

• TWAMP Client initiates the test session every 15 minutes.
- The timer of the TWAMP statistics on the client starts when the router boots up.
- The session timer is not synchronized across the clients.
• TWAMP Client sends 201 test packets during one test session, and measures the different
performance parameters of the site link
• TWAMP client sends SNMP traps to the UEM server when the measured value of a particular
performance parameter exceeds the defined threshold value
- Threshold alarms can be disabled via UNC save commands
• TWAMP Client stores the measured performance values for the completed test session in its MIB
table
• UEM server and InfoVista server collect the performance measurements every 15 minutes from all
TWAMP clients in the system
• The UEM and InfoVista servers allow the user to display statistics in a graphical format
• The performance statistics are available on UEM and InfoVista for the last 30 days

TWAMP Performance Parameters

The TWAMP Client in ASTRO 25 system measures the following performance parameters for Ethernet
site links during the TWAMP test session:
• Minimum Round Trip Delay
• Maximum Round Trip Delay
• Average Round Trip Delay
• Minimum Round Trip Jitter
• Maximum Round Trip Jitter
• Average Round Trip Jitter
• Percentage of Packet Loss

Default Statistic Threshold Configured by TNCT

Transport Network Configuration Tool (TNCT) allows the user to configure the fault alerting thresholds
for Round Trip Delay, Round Trip Jitter and Packet Loss on different site links.
• For Standalone Remote Sites, TSUB / IP Simulcast Prime Sites and Subsites, thresholds can be
configured on site-by-site bases.
- Each site can have its own threshold values for different parameters.
- All links towards a particular site will have the same threshold values for a particular
performance parameter.
• For CSUB site links, the TNCT configures a common threshold value for each of the performance
parameters on all Conventional subsystems within the zone. The site links for the Conventional
subsystems in different zones can have different threshold values.

44
 MN005963A01-E
Chapter 3 : K Core Remote Site Test and Verification

• If the user does not specify threshold values in TNCT; TNCT applies the following default site link
threshold values on TWAMP client configuration:
- Round Trip Delay = 40 ms
- Round Trip Jitter = 20 ms
- IP Packet Loss = 2 packets

45
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Appendix A

Site Preparation and R56 Compliance Checklist

This section provides information about obtaining and preparing all hardware, software, support, and test equipment necessary to set up,
configure, and optimize the system.
A document listing detailed parameter information for all system components is provided with your system.

A.1
Site Preparation
The following table lists the activities for preparing the site and the chapter references in the Motorola Solutions R56 Standards and Guidelines for
Communication Sites manual.

Activity Description R56 Manual Reference

Review the Prevent potential on-site and off-site interference by other local radio Chapter 2, “Site Design and Development”
site plan systems. Minimize cable lengths. Determine the location of telecom equip-
ment.
Determine site Outline site access and security measures. Chapter 2, “Site Design and Development”
access and
security
Review safety Outline general, installation, and environmental safety guidelines and re- Chapter 3, “Communications Site Building De-
considerations quirements, and OSHA-related considerations. sign and Installation”
Schedule in- Ensure options and functions of onsite, two-way communications for per- Chapter 3, “Communications Site Building De-
stallation of sonnel safety and maintenance. sign and Installation”
telephone
service
Review Ensure that the site meets or exceeds the design, grounding, power, and Chapter 4, “External Grounding”
grounding surge suppression requirements listed in R56 Compliance Checklist on Chapter 5, “Internal Ground”
specifications page 47.
Chapter 6, “Power Sources”
Chapter 7, “Surge Protective Devices”

46
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Activity Description R56 Manual Reference

Schedule In- Cover grounding, power sources, and surge protection. Chapter 4, “External Grounding”
stallation of Chapter 5, “Internal Ground”
site power
Chapter 6, “Power Sources”
Chapter 7, “Surge Protective Devices”

A.2
R56 Compliance Checklist

Activity Description Reference

R56 Compliance The site should meet R56 standards and be audited by an ETA- Motorola Solutions R56 Standards and Guide-
certified R56 auditor to verify compliance. lines for Communication Sites Manual, and the
following checklist.

R56 Compliance Checklist

Customer Name: Project Name:
Project Manager: Project No.:
Inspector Name: Audit Date:

Table 10: General

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
1. GENERAL Responsibility bility tions
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
a. A copy of the
Project Man-
ager Compli-
ance Sheet
has been com-
pleted, certi-
fied, and sup-

47
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
1. GENERAL Responsibility bility tions
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
plied for at-
tachment to
this audit.
b. Project Man-
ager Compli-
ance Sheet
shows that all
appropriate re-
quirements
have been
met.
TOTALS for Enter Section 1 totals here and on AUDIT SUMMARY
Section 1

Table 11: Building Design and Installation

Site Name:
2. BUILDING DE- Motorola Solutions Customer Responsi- Motorola Solu- Customer
SIGN AND INSTAL- Responsibility bility tions
LATION
Passed Failed Passed Failed N/A Date Correct- Date Corrected R56 Manual
ed Reference
a. The ceiling 3.6.1
height is suffi-
cient to meet
requirements
for equipment
installation.
b. Cable runway 3.10.5
system meets
the proper in-

48
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
2. BUILDING DE- Motorola Solutions Customer Responsi- Motorola Solu- Customer
SIGN AND INSTAL- Responsibility bility tions
LATION
Passed Failed Passed Failed N/A Date Correct- Date Corrected R56 Manual
ed Reference
stallation re-
quirements.
c. The floor is 3.6.2
sealed as re-
quired.
d. Transmission 3.7.1
line entry
ports, holes, or
openings
which pene-
trate the outer
surface of the
building have
been properly
sealed.
e. Adequate light- 3.11
ing require-
ments have
been met.
f. Maximum re- 3.12
quired fire sup-
pression
equipment is
properly instal-
led.
g. A first aid kit is 3.13.1
available and
meets require-
ments.
h. Required per- 3.13.2
sonal protec-
tive safety

49
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
2. BUILDING DE- Motorola Solutions Customer Responsi- Motorola Solu- Customer
SIGN AND INSTAL- Responsibility bility tions
LATION
Passed Failed Passed Failed N/A Date Correct- Date Corrected R56 Manual
ed Reference
items are avail-
able for servic-
ing batteries
which require
such items.
i. A telephone, 3.14
microwave
link, or cellular
phone has
been made
available.
j. Phone num- 3.14
bers of impor-
tance are post-
ed at the site.
k. The minimum 3.15
required sig-
nage is posted
at the site.
TOTALS for Enter Section 2 totals here and on AUDIT SUMMARY
Section 2

Table 12: External Grounding

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
a. An External 4.4.3
Ground Bus

50
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
bar (EGB) of
suitably sized
material is
properly in-
stalled at the
transmission
line entry
point.
b. The EGB 4.4.3
grounding
electrode con-
ductor has
been properly
installed.
c. When a Tow- 4.4.3.1
er Ground
Bus bar
(TGB) is
used, it meets
the proper in-
stallation and
bonding re-
quirements.
d. Each trans- 4.7.9
mission line
outer shield is
properly
bonded to the
tower or TGB
at the transi-
tion of the ver-
tical transmis-
sion line run

51
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
with a weath-
er-sealed
transmission
line grounding
kit.
e. Each trans- 4.7.9
mission line
outer shield is
properly
bonded to the
EGB with a
weather-
sealed trans-
mission line
grounding kit.
f. The tower is 4.7.6, 4.9
properly
bonded with
the required
number of
grounding
conductors.
g. Ice bridges / 4.7.10.2
cable sup-
ports have
been properly
bonded to the
EGB.
h. Each ice 4.7.10.2
bridge / cable
support post
has been
properly

52
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
bonded to the
grounding
electrode sys-
tem.
i. Ice bridges / 4.7.10.2
cable sup-
ports have
been properly
isolated from
the tower.
j. Guy wires are 4.7.6.2.1
properly
bonded and
their ground-
ing conductor
maintains a
continuous
vertical drop
to the ground-
ing electrode.
k. Fencing has 4.7.10.1
been properly
bonded to a
ground sys-
tem as re-
quired.
l. Each fence 4.7.10.1
gate is prop-
erly bonded to
its supporting
fence post as
required.

53
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
m. Gate support- 4.7.10.1
ing fence
posts are
properly
bonded as re-
quired.
n. Generator 4.7.7.1, 6.9.7
and support
skids have
been properly
bonded as re-
quired.
o. Items listed
are properly
bonded to the
grounding
electrode sys-
tem as re-
quired.
o.1 Metallic 4.7.10
entry ports
o.2 Cable 4.7.10
conduits or
raceways
o.3 Metallic 4.7.10
piping (water,
gas, electrical
conduits, and
so on.)
o.4 Air condi- 4.7.10
tioner units

54
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
o.5 Metal sid- 4.7.10
ing and/or
roofing on
buildings
o.6 Vent cov- 4.7.10
ers and grates
o.7 Metal fuel 4.7.10, 6.9.7
storage tanks
(above or be-
low ground)
o.8 Building 4.7.10
skid or pier
foundations
o.9 Anchors 4.7.10
on prefabri-
cated build-
ings
o.10 Metallic 4.7.6.3, 4.7.10
structures for
antenna sup-
ports, light fix-
tures, and so
on
o.11 Satellite 4.8
dish supports
o.12 GNSS 4.8
antenna sup-
ports
o.13 Hand 4.7.10
and safety
rails

55
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
o.14 Ladders 4.7.10
and safety
cages
o.15 Security 4.7.10
bars and win-
dow frames
o.16 Main 4.3, 6.2.2
electrical
ground
o.17 Main Tel- 4.3, 4.7.10
co ground
p. Approved 4.5
bonding tech-
niques have
been used for
the connec-
tion of dissimi-
lar metals.
q. Approved 4.6
methods have
been used for
conductor
connection
and termina-
tion.
r. Bonding sur- 4.5.4, 4.6.1
faces for lugs
and clamps
are free of
paint and cor-
rosion and a
conductive

56
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
anti-oxidant
compound
has been ap-
plied.
s. All painted or 4.6
galvanized
bonding surfa-
ces for exo-
thermic welds
were cleaned
and painted to
inhibit rusting.
t. All grounding 4.4.2.2
conductors
have been
routed to-
wards the
EGB, TGB, or
the grounding
electrode sys-
tem and the
minimum
bending radi-
us has been
observed.
u. Grounding 4.4.2.3
conductors
are routed as
straight as
possible and
protected
from physical

57
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
3. EXTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Corrected Date Correct- R56 Manual
ed Reference
damage as
required.
v. Grounding 4.4.2.3
conductors
maintain the
minimum re-
quired sepa-
ration from
other cable
groups.
w. Grounding 4.4.2.3
conductors
are securely
fastened as
required.
x. Grounding 4.4.2.1
conductors
meet or ex-
ceed the con-
ductor size re-
quirements.
y. Braided 4.7.9
grounding
conductors
are not used
anywhere in
the external
ground sys-
tem.
TOTALS for Enter Section 3 totals here and on AUDIT SUMMARY
Section 3

58
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Table 13: Internal Grounding

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
a. A properly 5.3.1
sized Master
Ground Bus
(MGB) is in-
stalled as re-
quired.
b. The MGB 5.3.1.3
grounding
electrode
conductor
has been
properly
bonded and
routed to-
wards the
grounding
electrode sys-
tem.
c. All conductor 5.4.3
connections
to the MGB
follow ap-
proved con-
nection meth-
ods.
d. Where re- 5.3.2
quired a Sub-
System
Ground Bus
Bar (SSGB)
has been

59
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
properly in-
stalled.
e. The SSGB 5.3.2.3
has been
bonded back
to the MGB
as required.
f. All conductor 5.4.3
connections
to the SSGB
follow the ap-
proved con-
nection meth-
ods.
g. Where re- 5.3.7
quired, an In-
ternal Perim-
eter Ground
Bus (IPGB) is
properly in-
stalled.
h. Only ancillary 5.3.7
equipment is
bonded to the
IPGB.
i. Each ancillary 5.4.1, 5.5.1.6
support appa-
ratus is prop-
erly bonded
to the IPGB,
MGB, or
SSGB.

60
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
j Items listed
are properly
bonded to the
MGB, SSGB,
or IPGB by
the approved
connection
methods.
j.1 Piping sys- 5.5.1.6, 5.5.1.7
tems
j.2 Steel roof 5.5.1.7
trusses
j.3 Exposed 5.5.1.7
support
beams or col-
umns
j.4 Ceiling 5.8.3.2
grids
j.5 Raised 5.4.2, 5.8.3.2
equipment
floor support
structure at
the proper in-
tervals
j.6 Any ex- 5.5.1.6
posed metal-
lic building
materials
(metal siding)
k. Surge Protec- 5.5.1.6
tion Device

61
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
(SPD) metal
housings are
bonded to the
MGB, SSGB,
or IPGB as
required.
l. Separately 5.5.1.1
derived AC
electrical sys-
tems are
bonded to the
MGB or
SSGB as re-
quired.
m. Primary tele- 5.5.1.8.2
phone, con-
trol, and data
network cir-
cuit SPDs are
properly in-
stalled bond-
ed to the
MGB or
SSGB as re-
quired.
n. RF transmis- 5.5.1.8.1
sion line
SPDs are
bonded to the
MGB or a
separate
equipment

62
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
area SSGB
as required.
o. Cable run- 5.5.1.5
ways are
bonded to the
MGB or
SSGB as re-
quired.
p. Each cable 5.5.1.5
runway sec-
tion is bonded
to the adjoin-
ing section as
required.
q. Ground bus 5.3.5, 5.3.6
conductors
and their ex-
tensions are
sized as re-
quired.
r. All ground 5.3.4
bus conduc-
tors, ground
bus exten-
sions, and
equipment
grounding
conductors
are routed to-
wards the
MGB or
SSGB as re-
quired.

63
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
s. Bonding con- 5.3.4
nections to a
ground bus or
its extensions
have been
properly insu-
lated as re-
quired.
t. Cabinets 5.5.1.4
have been
properly
bonded back
to the MGB,
SSGB, or
ground bus
by approved
methods.
u. Racks have 5.5.1.4
been properly
bonded back
to the MGB,
SSGB, or
ground bus
by approved
methods.
v. Any RGB lo- 5.3.3
cated in a
cabinet or
rack is prop-
erly bonded
back to the
MGB, SSGB,

64
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
4. INTERNAL
Responsibility bility tions
GROUNDING
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
or ground bus
as required.
w. Individual 5.5.1.3
system com-
ponent chas-
sis equipment
is properly
bonded as re-
quired.
x. Secondary 5.5.1.8.3,
telephone, 5.8.3.1
control, and
data network
circuit SPDs
are properly
installed and
bonded back
to MGB or
SSGB as re-
quired.
y. All required 5.8.3
control center
and dispatch
equipment is
properly
bonded back
to the MGB,
SSGB, or
ground bus
conductor as
required.
TOTALS for Enter Section 4 totals here and on AUDIT SUMMARY
Section 4

65
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Table 14: Power Sources

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
5. POWER SOUR-
Responsibility bility tions
CES
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
a. Circuit break- 6.2.6
ers are la-
beled to iden-
tify the recep-
tacle outlet
they are pro-
tecting.
b. Proper clear- 6.2.4
ance require-
ments are be-
ing observed
for power pan-
els.
c. Outlet boxes 6.2.10
are perma-
nently marked
to identify their
assigned cir-
cuit breakers
and panels.
d. Power recep- 6.2.11
tacle outlets
are mounted
securely to the
supporting
structure.
e. Adequate 6.2
service recep-
tacle outlets
are provided

66
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
5. POWER SOUR-
Responsibility bility tions
CES
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
for the techni-
cian.
f. Each critical 6.2.10
piece of
equipment
has a dedicat-
ed branch cir-
cuit and dedi-
cated simplex
receptacle.
g. Power recep- 6.2.10
tacles are in-
stalled by the
equipment
load as re-
quired.
h. Extension 6.2.9
cords, includ-
ing temporary
outlet strips,
are not used
in the final in-
stallation.
i. Exterior re- 6.2.5.1
ceptacle out-
lets and cir-
cuits are GFCI
protected as
required.
j. AC power re- 6.2.11
ceptacle out-
lets and strips

67
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
5. POWER SOUR-
Responsibility bility tions
CES
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
are of the
proper type
and securely
mounted off
the floor.
k. Appropriate 6.5.1
clearance is
being ob-
served for the
safe servicing
of UPS and
battery banks.
l. The neutral – 6.2.2
ground bond-
ing conductor
has been
properly in-
stalled in the
main service
disconnect as
required.
m. Equipment 6.2.7
grounding
conductors
have been in-
stalled as re-
quired.
n. Solar panels 6.6.2
have been lo-
cated away
from objects
that could
damage or

68
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
5. POWER SOUR-
Responsibility bility tions
CES
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
block sunlight
to the panel.
o. Proper mount- 6.6.2
ing practices
are being ob-
served for so-
lar panels or
wind genera-
tors.
p. Battery racks 6.7.9
are bolted to
the floor or
wall.
q. Battery con- 6.7.9
ductors are
enclosed in
PVC, metallic
conduit, or
raceways.
r. A battery dis- 6.7.9
connect and
suitable circuit
protection de-
vice has been
installed as re-
quired.
s. When a stand- 6.8
by power gen-
erator has
been installed,
it meets the
proper instal-

69
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
5. POWER SOUR-
Responsibility bility tions
CES
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
lation require-
ments.
t. Standby gen- 6.9.1
erators are lo-
cated in areas
only accessi-
ble by author-
ized person-
nel.
u. Standby gen- 6.9.1
erators have
an adequate
area provided
for servicing.
v. Fuel storage 6.9.2
tanks for
standby gen-
erators are lo-
cated in a se-
cured area.
w. A dedicated 6.9.4
electrical cir-
cuit has been
provided at
the generator.
x. A transfer 6.9.3
switch of the
proper ampac-
ity rating has
been installed
to switch be-
tween com-

70
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Solu- Customer
5. POWER SOUR-
Responsibility bility tions
CES
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
mercial power
and standby
generator
power.
y. A main serv- 6.2.1, 6.2.5
ice disconnect
has been in-
stalled as re-
quired.
z. Electrical pan- 6.2
el board am-
pacity ratings
are properly
coordinated.
TOTALS for Enter Section 5 totals here and on AUDIT SUMMARY
Section 5

Table 15: Transient Voltage Surge Suppression

Site Name:
6. TRANSIENT Motorola Solultions Customer Responsi- Motorola Sol- Customer
VOLTAGE SURGE Responsibility bility utions
SUPPRESSION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
a. A Type 1 7.4.1
SAD/MOV
Surge Protec-
tion Device
(SPD) is instal-
led as re-
quired.

71
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
6. TRANSIENT Motorola Solultions Customer Responsi- Motorola Sol- Customer
VOLTAGE SURGE Responsibility bility utions
SUPPRESSION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
b. A Type 2 MOV 7.4.1
SPD is instal-
led as re-
quired.
c. Primary SPDs 7.5
for telephone
circuits are in-
stalled as re-
quired.
d. Secondary 7.5
SPDs for tele-
phone circuits
are installed as
required.
e. Primary SPDs 7.5
for control cir-
cuits are instal-
led as re-
quired.
f. Secondary 7.5
SPDs for con-
trol circuits in-
stalled as re-
quired.
g. Primary SPDs 7.5
for data net-
work circuits
are installed as
required.
h. Secondary 7.5
SPDs for data
network cir-

72
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
6. TRANSIENT Motorola Solultions Customer Responsi- Motorola Sol- Customer
VOLTAGE SURGE Responsibility bility utions
SUPPRESSION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
cuits are instal-
led as re-
quired.
i. All RF trans- 7.6
mission lines,
including un-
used spares,
have coaxial
RF SPDs prop-
erly installed
as required.
j. Where a tower 7.6
top amplifier
has been in-
stalled, the
sample port
and its control
cables have
SPDs installed
as required.
k. Tower lighting 7.8
system AC
power and da-
ta/alarm cir-
cuits have
SPDs properly
installed as re-
quired.
TOTALS for Enter Section 6 totals here and on AUDIT SUMMARY
Section 6

73
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Table 16: Equipment Installation

Site Name:
Motorola Solutions Customer Responsi- Motorola Sol- Customer
7. EQUIPMENT IN-
Responsibility bility utions
STALLATION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
a. Equipment 9.3
spacing and
aisle widths
conform to
guidelines.
b. Equipment is 9.5
level and
plumb.
c. Equipment is 9.5
square with
surrounding
equipment and
walls.
d. Where appli- 9.4
cable, seismic
installation
practices have
been ob-
served.
e. Cabinets and 9.6
racks are se-
cured as re-
quired.
f. Cables and 9.9.1.5
cable groups
of different
function main-
tain a mini-
mum 5 cm (2
in.) separation
as required.

74
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Sol- Customer
7. EQUIPMENT IN-
Responsibility bility utions
STALLATION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
Cables and
cable groups
of different
function main-
tain a mini-
mum 5 cm (2
in.) separation
as required.
g. RF cables 9.9.1.4, 9.9.8
meet or ex-
ceed minimum
bending radius
requirements.
h. Plenum-rated 9.9.2
cables are in-
stalled as re-
quired.
i. Proper cable 9.9.1.2
lengths used.
j. Cables are 9.9
properly se-
cured at the
required inter-
vals.
k. AC power con- 3.10.4, 9.9.4
ductors instal-
led on cable
runway sys-
tems meet in-
stallation re-
quirements.

75
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Sol- Customer
7. EQUIPMENT IN-
Responsibility bility utions
STALLATION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
l. Cables are 9.9.12
properly identi-
fied with a
standard, dou-
ble-ended sys-
tem.
m. Distribution 9.9.11
frame wiring
conforms to
the proper
punch-down or
wire-wrap
techniques.
n. CAT-5 cables 9.9.6.4
maintain the
proper separa-
tion from AC
power cables.
o. CAT-5 cables 9.9.6.5
do not have
any sharp
bends.
p. CAT-5 cables 9.9.6
meet all other
installation re-
quirements.
q. Cables instal- 3.10.2, 9.9
led below
raised flooring
systems are
properly instal-
led.

76
 MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

Site Name:
Motorola Solutions Customer Responsi- Motorola Sol- Customer
7. EQUIPMENT IN-
Responsibility bility utions
STALLATION
Passed Failed Passed Failed N/A Date Correct- Date Correct- R56 Manual
ed ed Reference
r. Cables instal- 9.9.3.3
led above sus-
pended ceil-
ings are prop-
erly installed.
s. Electrostatic 9.10
discharge
practices are
observed as
required.
TOTALS for Enter Section 7 totals here and on AUDIT SUMMARY
Section 7

Table 17: Audit Summary

AUDIT SUMMARY
Customer Name: Project Name:
Project Manager: Project No.:
Inspector Name: Audit Date:
Site Name:
Motorola Solutions Customer
Number of Number of Number of Passed Number of Total N/A
Passed Failed Failed
Section Totals
1. General
2. Building Design and Instal-
lation
3. External Grounding

77
MN005963A01-E
Appendix A : Site Preparation and R56 Compliance Checklist

AUDIT SUMMARY
4. Internal Grounding
5. Power Sources
6. Transient Voltage surge
Suppression
7. Equipment Installation
AUDIT TOTALS

78
 MN005963A01-E
Service Laptop and Software Setup

Appendix B

Service Laptop and Software Setup

Depending on your system configuration, you must install the appropriate software on the service
laptop following the instructions on the installation DVDs for each application.
The following applications can be installed on the service laptop:

Provisioning and Configuration Agent (PCA)

The PCA application is a web interface used to configure operating parameters and troubleshoot DSC
8000s.
NOTE: It requires the installation of MSI CA Certs package from ASTRO Windows
Supplemental media on the service laptop to avoid certificate trust warnings from the web
browser.

On-Premises Software Hub

The On-Premises Software Hub application can be used to install, upgrade and recover software on
DSC 8000s.

Configuration/Service Software (CSS)

The CSS application is used to create and back up device configurations and troubleshoot RF site
(G-series) and Voice Processor Module (VPM)-based devices:
• GTR 8000 Base Radios
• GCM 8000 Comparators
• GRV 8000 Comparators
• GPW 8000 Receivers
• GPB 8000 Reference Distribution Modules
• GCP 8000 Site Controllers
• Telephone Media Gateways

Software Download Manager (SWDL)

The SWDL is used to download firmware to the base radios and site controller.

Customer Programming Software (CPS)

The CPS is used to program subscriber radios.

Enhanced Software Update (ESU) Launchpad

The ESU Launchpad is used to deploy, configure, and maintain software on elements of the
infrastructure.

Other Software
It is recommended to install the following software on the service laptop:
• Remote Desktop Connection or a similar utility
• PuTTY (for Serial, Secure Shell (SSH) and Telnet connections) or a similar utility

79
MN005963A01-E
Appendix B : Service Laptop and Software Setup

• Microsoft Internet Explorer (latest) or Firefox (latest) for Configuration/Service Software (CSS)
software
• Microsoft Edge 88.0.705.50 or later for VMware ESXi Embedded Host Client (ESXi 7.0)
• VMware Remote Console (VMRC)
• VMware PowerCLI
• .NET Framework 4.5
• Powershell 5.1

Systems with Unified Event Manager (UEM)

The general functionality of the UEM network fault manager is managed using internal license
configuration based on license key entries and embedded licensing management. For more
information, see the Unified Event Manager User Guide.

Systems with MLC 8000 Hardware

For more information, see MLC 8000 Configuration Tool User Guide and online help.

B.1
Provisioning and Configuration Agent Application
Provisioning and Configuration Agent (PCA) is a web interface for local configuration, status reporting
and managing a site.
The PCA application can be used to perform the following actions:
• Configure operating parameters for infrastructure devices.
• Retrieve status and operational information from a device.
• Perform device configuration and servicing tasks through a direct Ethernet connection to the device
or over the LAN from the Network Management subsystem.

B.2
On-Premises Software Hub Application
The On-Premises Software Hub application can be used to install, upgrade and recover software on
DSC 8000s.
The installation and recovery procedures can be performed from a service laptop connected to the
DSC 8000 service port. The upgrade procedure can be performed from the Network Management
(NM) Client or a service laptop connected to a DSC 8000.
In some cases recovery procedures can be performed from the NM Client. If hardware failure occurs,
recovery must be performed on site with service laptop connected.

B.3
Configuration/Service Software
The Configuration/Service Software (CSS) is a Windows-based application installed on the computer
used to perform configuration, status reporting, and servicing tasks for infrastructure devices in the
system.
The CSS application allows a service technician to:
• Configure operating parameters for Voice Processor Module (VPM)-based devices and RF site
devices.
• Retrieve status and operational information from a device.

80
 MN005963A01-E
Appendix B : Service Laptop and Software Setup

• Perform alignment procedures for the infrastructure devices that can use the CSS.
• Set the IP address for specified devices, which requires a local serial connection.
• Perform most device configuration and servicing tasks either through a serial connection to the
device or over the LAN.
CSS can access each device over the local LAN, or individually through the Ethernet service port. The
DB-9 serial port connection is used to set the IP addresses for devices. CSS also can be used to view
status information, equalize batteries, and check internal logs of the devices.

Table 18: Installing and Upgrading the Software

Activity Description Reference

Install CSS Install the CSS on the service laptop. CSS in- CSS Getting Started Guide
stallation offers the option of installing the Soft-
ware Download Manager (SWDL) application
included on the same DVD.
After installation, two icons appear on the
desktop:

Launches the CSS application.

Launches the SWDL application.

B.3.1
Configuration/Service Software Online Help Access
The online help is accessible from the CSS interface.
To access the Configuration/Service Software (CSS) online help, select CSS Help from the Help menu
in the menu bar. Before performing any procedure or process established in the online help, review the
following CSS online help topics so you are familiar with and have access to the appropriate topics:
CSS Main Window
To become familiar with the CSS elements and navigation components.
Overview of CSS
To become familiar with using CSS locally or through the network management subsystem.
CSS Help Links
For specific online help supporting Comparator Configuration and Site Controller Configuration.

81
MN005963A01-E
Appendix B : Service Laptop and Software Setup

B.3.2
Reading/Writing Configuration Files From/To a Device
When Configuration/Service Software (CSS) is installed, the online help feature provides information
and instructional procedures to read/write a configuration file from/to a device. For information and
instructions on how to read/write a configuration file from/to a device in the CSS, follow this procedure.

Procedure:
1 Access the online help by selecting from the menu Help→CSS Help.
2 From the tree view of the CSS Online Help topics, expand CSS Procedures (list of
procedures).
3 From the CSS Procedures list, select the appropriate help topic.
• Connecting to a Device Through an Ethernet Connection
• Connecting to a Device Through a Serial Connection
• Reading the Configuration File from a Device
• Writing the Configuration File to a Device
4 Follow the instructions provided to perform the task selected from the online help.

B.4
SDM3000 Builder
The SDM3000 Builder software is used to set up and configure SDM3000 hardware-based devices
(RTU, MCC 7500 Aux I/O Server).
The SDM3000 Builder is a Microsoft Windows-based software application that facilitates the planning
of your zones and sites. Based on information you enter in the SDM3000 Builder screens, the software
calculates intersite and intrasite dependencies, such as defining the number, order, and connections of
the CPU and I/Os in the SDM3000 unit with consideration for your equipment and needs.
For details concerning SDM3000 Builder, see the SDM3000 Builder User Guide.

B.5
Software Download Manager
Software Download Manager (SWDL) transfers and installs new firmware in site components including
base radios, site controllers, comparators, and Reference Distribution Modules (RDMs).
NOTE: For detailed information on uploading firmware to the devices, see the Software
Download Manager User Guide.
SWDL allows you to perform the following actions:
• Download software to site devices.
• Download software to one device (such as one base radio) that has been disconnected from the
radio network.
• Update the software on newly added channels or subsites.
• Determine software and hardware versions on target devices.
• Purge (delete) a software version from selected target devices.
• Obtain device IP information.
• Query the site controller for the number of channels and/or subsites in the system.
• Audit a session using historical information recorded by SWDL.

82
 MN005963A01-E
Appendix B : Service Laptop and Software Setup

To download software to an ASTRO® 25 system, perform one of the following actions:

• Software download to the entire site (centralized software download).
• Software download to one device that has been disconnected from the radio network (single device
software download).
NOTE: Conventional devices are supported only in the single device mode.

For more information see Software Download Manager User Guide.

B.6
Customer Programming Software
Subscriber radios are configured through Customer Programming Software (CPS).
A computer running CPS is directly connected to the universal connection port on the subscriber
radio and the codeplug is loaded. The configuration settings in CPS are categorized into different
types, such as Radio-Wide settings, Controls, Display and Menu settings, and Secure settings.
Parameters must be set according to the services the radio uses. CPS is used to configure each radio
with a system ID, a unique individual ID for the radio, and as many talkgroup IDs as needed.
For subscriber radio programming details, see your subscriber radio user guide and Customer
Programming Software online help.

B.7
ESU Launchpad
Enhanced Software Update (ESU) Launchpad is a web-based framework that facilitates the installation
and upgrades of software in other elements of the infrastructure. ESU Launchpad provides a central
point for configuring installation/upgrade scenarios and monitoring their progress. There are two types
of ESU Launchpad; consisting of Red Hat Linux VM only, and built of Red Hat Linux VM and Windows
VM.
ESU Launchpad platform consists of:
• ESU Launchpad web-based interface
• VMware Workstation Player Red Hat Enterprise Linux (64-bit) virtual machine that is used for
storing installation files and installation orchestration.
ESU Launchpad does not include the target software, for example, DCG 9000. Obtain the software
and upload it to ESU Launchpad storage before installation.
ESU Launchpad is installed on a Windows service laptop. It allows for the automation of the following
configuration, installation, and upgrade operations in following platforms:
• CSA – for products which base on Common Server Architecture (HP Server with ESXI and Virtual
Machines). For example, IMW Classic or CMF
• PCR – CSA tuned for PCR System Technology
• SSP – for products which base on Shared Scalable Platform (Linux OS and micro-services). For
example, DCG9000.
For more details, see the ESU Launchpad User Guide.

83
MN005963A01-E
Appendix B : Service Laptop and Software Setup

B.8
Service Laptop Requirements
Laptop hardware and OS requirements depend on the software you intend to use.

Configuration/Service Software (CSS)

Supported Operating System: Windows 10 32-bit and 64-bit
Hardware Requirements:
• 1 GHz or higher Pentium grade processor
• 2 GB RAM recommended for Windows Server 2016
• 2 GB RAM recommended for Windows 10 32-bit
• 4 GB RAM recommended for Windows 10 64-bit
• 300 MB minimum free space for CSS Typical Installation (including Help Text and Software
Download Manager) or 100 MB minimum free space for a Compact Installation
Peripherals:
• Serial port or a USB with a USB-to-serial converter as a connection device (not currently Motorola
Solutions-certified)
• Windows-supported mouse or trackball
• Windows-supported 10Base-T Ethernet port for product communication
• Windows-supported printer port for report printing
• DVD drive for software installation

Customer Programming Software (CPS)

For the CPS service laptop hardware and OS requirements, see CPS_readme.txt file on the CPS
installation DVD or in the program installation directory.

SDM3000 Builder
Operating Systems:
• Windows Server 2016
• Windows 10 32- and 64-bit
Minimum hardware requirements:
• 2 GB of RAM
• 20 GB of free disk space

84
 MN005963A01-E
Remote Site LAN Switch Configuration Setup

Appendix C

Remote Site LAN Switch

Configuration Setup
This section contains the information necessary to set up a remote site LAN switch.

C.1
Loading/Restoring the Switch Configuration File for the Remote
Site LAN Switch
Prerequisites: Before performing this procedure, obtain the IP addresses for your system from your
system administrator or system IP plan.
When and where to use: Follow this procedure to load or restore an Ethernet LAN Switch
configuration locally.

Procedure:
1 Insert the media with the switch configuration file into the drive on the service laptop.
2 Copy the switch configuration file to the service laptop, to the directory the TFTP server
application uses.
3 Connect an Ethernet cable from the Ethernet port on the service laptop to a port designated for
service on the switch.
The hardware is in place for a LAN connection to the switch for the TFTP file transfer.

4 Ensure that the TFTP server application is open.

The service laptop establishes a LAN connection to the switch.

5 Connect a serial cable from the service laptop serial port to the CONSOLE port on the front of
the switch, and establish a serial connection to the switch from the service laptop.
6 Type setup. Enter the following switch information, if it is not already configured on the switch:
• Default gateway
• IP address
• Network Mask
7 Type save to save the configuration.
Other devices on the LAN can recognize the switch.

8 Select Cancel. Press ENTER.

The <Hostname_text_string># prompt appears.

9 Type the following command and press ENTER:

copy tftp startup-config <IP address><file name on PC>
where:
<IP address> is the IP address of the TFTP server on the service laptop

85
MN005963A01-E
Appendix C : Remote Site LAN Switch Configuration Setup

<file name on PC> is the switch configuration file name on the service laptop in the directory
that was set up using the TFTP server application

The file is copied from the TFTP server IP address to the startup-config of the switch. The switch
reboots and runs the new startup-config.

C.2
Setting up Passwords for the Remote Site LAN Switch
Prerequisites: Decide which passwords to configure. You can configure the Manager and Operator
level passwords, only the Operator password, only the Manager password, or neither. Consider the
following:
• If the switch has neither a Manager nor an Operator password, anyone having access to the switch
through the network or the serial port can access the switch with full manager privileges.
• If you set up passwords for both the Manager and the Operator levels, which password is entered
in response to the prompt determines the level of access to the console interface.
• If you configure only an Operator password, entering the Operator password and typing the
enable command enables full manager privileges.
NOTE: The password for the Manager or the Operator can be up to 16 ASCII characters, and
cannot include spaces. The password is case-sensitive. Passwords do not become active until
you reboot the switch.
When and where to use: Use this procedure for adding passwords for the operator and the manager.

Procedure:
1 Perform one the following actions to ensure that the Ethernet LAN Switch is still in the
configuration mode:
• If the command prompt displays (config), proceed to step 2.
• If the command prompt does not display (config), at the command line, type config.
Press ENTER. Proceed to step 2.
2 Perform one the following actions to choose the password you want to change:
• If you want to set the Manager password, at the command prompt, type password
manager. Press ENTER.
• If you want to set the Operator password, at the command prompt, type password
operator. Press ENTER.
The New Password prompt displays. Continue with step 3.

3 Type the new password. Press ENTER.

The prompt changes to Please retype the new password.

4 Perform one the following actions to retype the new password:

• If you typed the password identically both times, the password is set and the command
prompt displays. Continue with step 5.
• If you did not type both passwords identically, an error message appears, and the New
Password prompt displays again, repeat step 1 to step 3 until the system accepts the new
password. Continue with step 5.
5 Choose one of the following actions:
• If you want to change another password, repeat this procedure from step 2.

86
 MN005963A01-E
Appendix C : Remote Site LAN Switch Configuration Setup

• If you are finished changing passwords, continue with the next step.
6 Type write memory. Press ENTER.
The switch console inactivity timer is set and the configuration is written to flash memory.

C.3
Verifying Port Status for the Remote Site LAN Switch
When and where to use: Use this procedure to verify the port status of a LAN switch after installing it.

Procedure:
1 Connect the computer or terminal to the switch console port, using the console cable shipped
with the switch.
NOTE: If the computer or the terminal has a 25-pin serial connector, attach a 9-pin to
25-pin straight-through adapter to the computer end of the console cable.
2 Press ENTER.
NOTE: If for any reason, the command line does not appear, try pressing ENTER several
times.
The command-line prompt appears

3 Type in the password (the default setting is to press ENTER).

NOTE: If there is an enable password on the switch, at the <switch name> prompt,
type enable. Type in the correct user name and password.
The software displays copyright information for the switch software. After the copyright display,
the software displays the Press any key to continue prompt.

4 Press ENTER.
The <switch name># prompt appears.

5 Execute the following command to verify that all connected ports are in the Enabled state and
their status is Up. Also, verify that ports have the correct speed duplex: show interface
brief.
NOTE: For mesh ports, enter show mesh for a summary that includes port states.

A summary containing port states, statuses, types, and modes appears.

6 Type logout. Press ENTER to log off the switch.

The switch prompt displays the following message: do you want to logout [y/n].

7 Select y to logout off the switch.

87