LACR - Capacity Max Installation and Configuration Manual

Capacity Max
Installation and
Configuration Manual
*MN002731A01*
MN002731A01-A
©2016 Motorola Solutions, Inc. All rights reserved. Motorola Solutions Confidential
Copyrights
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media.
Laws in the United States and other countries preserve for Motorola certain exclusive rights for
copyright computer programs, including the exclusive right to copy or reproduce in any form the
copyright computer program. Accordingly, any copyright Motorola computer programs contained in
the Motorola products described in this document may not be copied or reproduced in any manner
without the express written permission of Motorola. Furthermore, the purchase of Motorola products
shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license
under the copyrights, patents or patent applications of Motorola, except for the rights that arise by
operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language or computer language, in any form or by any
means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this
document and to make changes from time to time in content hereof with no obligation to notify any
person of revisions or changes. Motorola does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
Motorola, Moto, Motorola Solutions, PremierOne, and the stylized M logo are trademarks or
registered trademarks of Motorola Trademark Holdings, LLC and are used under license.
Microsoft, Windows, Windows XP, Windows Vista, Windows 7, Windows 8, and Windows Server are
registered trademarks of Microsoft Corporation. All other product or service names are the property
of their respective owners.
2 Send Feedback
Motorola Solutions Confidential
MN002731A01-A
Contents
Chapter 1: Configuration Overview .......................................................................1

Capacity Max System Confuration..........................................................................................1
System Staging ...............................................................................................................1
Phased Integration ..........................................................................................................1
Capacity Max Configuration High Level Steps ................................................................1
Floor Plan, Racking, and Power......................................................................................3
Software Installation and Firmware Upgrade ..................................................................3
Equipment Cabling ..........................................................................................................3
Site Topology Example............................................................................................3
Pre-Configuration Planning .............................................................................................7
Network Configuration.....................................................................................................7
Radio Management Configuration...................................................................................8
Import Software Licenses................................................................................................8
System Parameters Configuration in Radio Management ..............................................9
Repeater Configuration in Radio Management ...............................................................9
Subscriber Configuration in Radio Management.............................................................9
Capacity Max System Server (CMSS) Configuration within Radio Management .........10
Trunking Controller Parameters Configuration ......................................................10
Subscriber Access Control ............................................................................10
Talkgroup to Site Association ........................................................................11
VRC Gateway Parameter Configuration................................................................11
Voice Console Audio Routing Configuration..................................................11
Voice Recorder Audio Routing Configuration ................................................11
Phone Gateway Audio Routing Configuration ...............................................11
Configuring the Parameters for the System Advisor Server .........................11
System Advisor Client Configuration.............................................................................12
MNIS Data Gateway Configuration within Radio Management.....................................12
Battery Management Configuration...............................................................................12
Voice Applications Configuration...................................................................................12
Data Applications Configuration ....................................................................................13
System Redundancy Configuration...............................................................................13
Chapter 2: Pre-Configuration Planning ...............................................................15

Understanding IP Addressing ...............................................................................................15
Wide Area Network (WAN)............................................................................................15
Capacity Max Networks.................................................................................................16
Capacity Max Subnetworks...........................................................................................17
Creating a Capacity Max Overlay Network ...................................................................18
Send Feedback i
MN002731A01-A
Contents
Detailed Capacity Max IP Plan ..................................................................................... 23

Special Considerations for Private (Enterprise) Wide Area Networks .......................... 26
Special Considerations for Point-to-Point Links............................................................ 26
Capacity Max IP Plan Summary ................................................................................... 28
Entity Identifier Assignments ................................................................................................ 29
Unique Identifier in DMR Trunking Systems ................................................................. 29
Unique Site ID of an RF Site in the System .................................................................. 30
Unique Site ID of a Gateway in the System.................................................................. 30
Unique Device ID for a Repeater at a Site.................................................................... 31
Unique Device ID for a CMSS, MNIS Data Gateway, and Device
Programmer in the System ...................................................................................... 31
Unique Radio ID of a Sourcing Entity in the System..................................................... 32
Summary of Recommended Identifiers......................................................................... 33
Radio Identifier Assignments ................................................................................................ 34
DMR Mobile Subscriber IDentifier (MSID) Addressing Range...................................... 34
Radio IDs Identification ................................................................................................. 34
Talkgroup Identifier Assignments ......................................................................................... 35
DMR Talk Group IDentifier (TGID) Addressing Range ................................................. 35
Short Talk Group IDentifier (TGID) Addressing Range................................................. 35
Understanding the Channel Plan.......................................................................................... 36
DMR Trunking Protocol................................................................................................. 36
Multiple Channel Plans ................................................................................................. 36
Fixed and Flexible Channel Plan Mapping ................................................................... 37
Fixed Mapping....................................................................................................... 37
Setting a Channel Plan with Fixed Mapping.................................................. 39
Flexible Mapping ................................................................................................... 42
Chapter 3: Network Configuration ...................................................................... 45

Configuring a Capacity Max System Transport Network ...................................................... 45
Configuring the IP Network ........................................................................................... 46
Loading The OS on a HP MSR2003 Router Using TFTP..................................................... 62
Loading The OS on an HP 2530 Switch Using TFTP........................................................... 65
Loading The Configuration on an HP MSR2003 Router Using TFTP .................................. 66
Loading The Configuration on an HP 2530 Switch Using TFTP........................................... 68
User Credentials in Transport Network Configuration .......................................................... 69
Configuring the Password for the User ‘root’ on Routers.............................................. 70
Configuring Passwords for the Users on Switches ....................................................... 70
Configuring SNMP Credentials on Routers .................................................................. 71
Configuring SNMP Credentials on Switches................................................................. 71
ii Send Feedback
MN002731A01-A
Contents
Configuring the Password for the User ‘capacitymax’ on Routers ................................72

Pre-shared Keys in Transport Network Configuration...........................................................72
Configuring the Pre-shared Key for the IKE Keychain ..................................................72
Configuring the Pre-shared Key and User Password for the VAM Client .....................73
Configuring the Pre-shared Key for the VAM Server ....................................................74
Chapter 4: System Configuration ........................................................................75

Radio Management Configuration ........................................................................................75
Radio Management Components..................................................................................75
Radio Management Deployments .................................................................................76
Radio Management Component Configuration .............................................................77
Radio Management Licenses........................................................................................78
Adding a Radio Management License...................................................................78
System Parameter Configuration ..........................................................................................78
Capacity Max System Set .............................................................................................78
Adding a New System Set.....................................................................................79
Capacity Max System Set Parameters..................................................................79
Adding a Channel Plan..........................................................................................86
Adding a Flexible Channel Plan ............................................................................86
Adding Capacity Max Sites....................................................................................87
Capacity Max Site Parameters ..............................................................................87
Adding Capacity Max Channels ............................................................................88
Capacity Max Channels Parameters .....................................................................89
Configuring a Site Announcement .................................................................91
Capacity Max Site Selection Set ...................................................................................92
Selecting a Capacity Max Site...............................................................................92
Capacity Max Radio Wide Features Set .......................................................................92
Configuring the Capacity Max Radio Wide Features.............................................93
Capacity Max Radio Wide Features Parameters ..................................................93
IP System Settings ........................................................................................................94
Editing the IP System Settings ..............................................................................94
IP System Setting Parameters ..............................................................................94
Selecting the IP System Settings for a CMSS ...............................................95
Capacity Max System Server Data ...............................................................................95
Configuring the Capacity Max System Server Data ..............................................95
Subscriber Access Control ............................................................................95
Capacity Max Subscriber Access Control Parameters ..................................95
Creating New Allowed Sites Lists ..................................................................97
Talkgroup Site Association ............................................................................98
Send Feedback iii

MN002731A01-A
Contents
Configuring the Talkgroup Site Association .................................................. 98

Talkgroup Site Association Parameters ........................................................ 99
Creating New Talkgroup Allowed Sites ......................................................... 99
Trunking Repeater Configuration.......................................................................................... 99
Adding the Repeater into Radio Management............................................................ 100
Scheduling a Repeater Read...................................................................................... 100
Upgrading the Repeater Firmware.............................................................................. 100
Entering the Licenses for the Repeater ...................................................................... 101
Editing the Repeater Configuration............................................................................. 101
Capacity Max Repeater Configuration Parameters .................................................... 102
Setting the Device ID .................................................................................................. 104
Setting an Alias and Radio IP for a Repeater ............................................................. 104
Analyzing the Repeater............................................................................................... 104
Scheduling a Repeater Write ...................................................................................... 104
Trunking Subscriber Configuration ..................................................................................... 105
Adding the Radio to Radio Management .................................................................... 105
Scheduling a Radio Read ........................................................................................... 105
Upgrading the Radio Firmware ................................................................................... 106
Entering the Licenses for the Radio............................................................................ 106
Editing or Selecting a Radio Configuration ................................................................. 107
Editing a Radio Configuration ............................................................................. 107
Selecting a Radio Configuration.......................................................................... 107
Capacity Max Radio Configuration Parameters.......................................................... 107
Adding a Radio Contact .............................................................................................. 110
Setting the Radio ID and Radio Alias.......................................................................... 110
Analyzing the Radio .................................................................................................... 111
Scheduling a Radio Write ........................................................................................... 111
Capacity Max System Server (CMSS) Configuration ......................................................... 111
Ethernet Port Configuration ........................................................................................ 112
IP Configuration .......................................................................................................... 113
Adding the CMSS to Radio Management ................................................................... 114
Setting the IP System for the CMSS in Radio Management....................................... 115
Adding a CMSS Configuration in Radio Management................................................ 115
Configuring the Capacity Max Features.............................................................. 115
MNIS ........................................................................................................... 116
Selecting the Configuration for the CMSS Device ...................................................... 116
Setting the Device ID and Redundancy Group ........................................................... 117
Scheduling a CMSS Read .......................................................................................... 117
iv Send Feedback
MN002731A01-A
Contents
Licensing the CMSS....................................................................................................117

Analyzing the CMSS ...................................................................................................118
Scheduling a CMSS Write...........................................................................................118
MNIS VRC Gateway Configuration .....................................................................................118
Adding a MNIS VRC Gateway ....................................................................................119
Configuring a MNIS VRC Gateway .............................................................................119
Adding an Alternate VRC Gateway .............................................................................120
Configuring the Capacity Max System Server Data ....................................................120
Firewall Setting on the MNIS Data Gateway PC Configuration...................................121
System Advisor Configuration.............................................................................................122
System Advisor Server Configuration .........................................................................122
System Advisor Licenses in CMSS .............................................................................122
Starting the System Advisor Client..............................................................................122
Configuring Outbound Communication Credentials ....................................................123
Configuring System Parameters in the System Advisor..............................................124
Configuring the Call Monitoring (ATIA) Port Number ..................................................124
Configuring the Language and Date Format ...............................................................125
Discovering Non-Capacity Max IP Plan Devices.........................................................125
MNIS Data Gateway Configuration .....................................................................................125
MNIS Data Gateway Site and Site Selection System Set ...........................................126
Adding a MNIS Data Gateway Device ........................................................................126
Adding a MNIS Data Gateway Configuration ..............................................................126
Selecting the Configuration for the MNIS Data Device ...............................................129
Setting the Device ID and Redundancy Group ...........................................................129
Analyzing the MNIS Data Gateway .............................................................................129
Exporting MNIS Data Gateway Configurations from RM and Importing
into the Data Gateway Config Folder .....................................................................130
MOTOTRBO Network Interface Service Configuration Utility .....................................130
Firewall Setting on the MNIS Data Gateway PC .........................................................131
Adding a MNIS Data Gateway Radio ID to the Subscriber Access Control ........131
Chapter 5: Redundancy ......................................................................................133

Fault Tolerance ...................................................................................................................133
Failure of a Repeater...................................................................................................133
Failure of a Capacity Max System Server (CMSS) .....................................................134
Failure of a Wide Area Network Connection or an IP Network Router........................135
Failure of the IP Network Switch .................................................................................137
Failure of the MNIS Data Gateway..............................................................................137
Failure of the Radio Management Server ...................................................................137
Send Feedback v
MN002731A01-A
Contents
IP Network Multiple Site Switch Configuration.................................................................... 137

Example of Standardized Switch Configuration .................................................. 138
Site Network Topology ........................................................................................ 140
Assignment of Repeaters to Ethernet Switches at a Physical Location.............. 142
Assignment of Trunked Repeaters to Ethernet Switches at a
Physical Location ................................................................................... 142
Assignment of Revert Channel Repeaters to Ethernet Switches
at a Physical Location ............................................................................ 142
Assignment of Hardware Redundant Repeaters to Ethernet
Switches at a Physical Location............................................................. 144
Capacity Max System Server (CMSS) Redundancy .......................................................... 144
Repeater Hardware Redundancy ....................................................................................... 145
Why Utilize Hardware Redundant Repeaters ............................................................. 145
Redundancy Considerations for Trunked Repeaters .......................................... 145
Redundancy Considerations for Data Revert Repeaters .................................... 145
Redundancy Considerations for Control Channel Repeaters ............................. 146
Configuration and Wiring of Hardware Redundant Repeaters.................................... 146
Setting GPIO Physical Pins................................................................................. 146
RF Output Configuration ..................................................................................... 147
RF Input Configuration ........................................................................................ 149
Recovery of Redundancy Configuration ..................................................................... 149
Chapter 6: Optimizations ................................................................................... 151

Data Revert Channel Optimization ..................................................................................... 151
Data Revert Channel Configuration ............................................................................ 151
Different Message Sizes on EGPS Channels............................................................. 151
Transmission of EGPS Location Data at Sites Without Configured
EGPS Revert Channels ......................................................................................... 151
Periodic Window Reservation (Channel Loading) ...................................................... 152
Persistent LRRP ......................................................................................................... 153
High Efficiency Data Location Update Configuration .................................................. 154
Multi-Site Roaming Optimization ........................................................................................ 154
Roamable Sites........................................................................................................... 154
Site Adjacency ............................................................................................................ 155
Site Model for Roaming .............................................................................................. 157
Acceptable RSSI Threshold........................................................................................ 158
Roaming RSSI Threshold ........................................................................................... 159
Typical Multi-Site Network Coverage.......................................................................... 160
Dense Overlapping Coverage (Urban)................................................................ 160
Isolated No Overlapping Coverage (Rural) ......................................................... 161
vi Send Feedback
MN002731A01-A
Contents
Corridor Coverage ...............................................................................................162

Multi-Floor Coverage ...........................................................................................163
Determining Site Preference Level..............................................................................165
Preference Level Based on User Mobility ...........................................................166
Preference Level Based on Site Strategy (Infill Sites).........................................167
Preference Level Based on Site Strategy (Co-located Sites)..............................167
Call Priority Optimization.....................................................................................................168
Example of Call Priority ...............................................................................................168
Use of Call Priority in the System................................................................................169
Chapter 7: Capacity Max Hardware Specifications ..........................................171

CMSS Hardware Specifications ..................................................................................171
Repeater Hardware Specifications..............................................................................172
MTR 3000 Repeater ............................................................................................172
XPR 8400 Repeater ............................................................................................173
XPR 8380 Repeater ............................................................................................173
SLR 5700 Repeater.............................................................................................173
Hardware Specifications for Recommended IP Network Equipment ..........................174
Specifications for IP Network Routers .................................................................174
MSR 2003 AC Router Specifications ...........................................................174
Cisco 2911 Router Specifications ................................................................175
Specifications for IP Network Switches ...............................................................175
Procurve 2530-24 Switch Specifications .....................................................175
Cisco 3650 Switch Specifications ................................................................176
Specifications for Computer Hosting Applications.......................................................176
Radio Management Computer Specifications .....................................................177
Operating System Requirements.................................................................177
Recommended Hardware Requirements for Small Fleets ..........................177
Battery Management Computer Specifications ...................................................177
Hardware Minimum Requirements ..............................................................178
MNIS Data Gateway Computer Specifications....................................................178
System Advisor Client Computer Specifications .................................................179
Software Requirements ...............................................................................179
ESU Client Computer Specifications ...................................................................179
Software Requirements ...............................................................................179
Send Feedback vii

MN002731A01-A
Contents
Chapter 8: Common System Configurations and

Recommended IP Plans ............................................................................ 181
Quick Setup Reference System #1............................................................................. 182
Chapter 9: Configuration Files .......................................................................... 213

HP MSR2003 Router Configuration File Overview............................................................. 213
HP 2530 Switch Configuration File Overview ..................................................................... 222
Chapter 10: MSR WAN IP Identification and Changes .................................... 229

Changing the WAN IP Address .......................................................................................... 229
Adding a NAT Entry to Access a Service from the Internet ................................................ 232
Configuring the Static NAT Entry Under the GigabitEthernet0/1 interface ................. 232
viii Send Feedback

MN002731A01-A
List of Figures
Figure 1: High Level Process of Capacity Max System Configuration. . . . . . . . . . . . . . . . . . . . . . . . 2

Figure 2: Example Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 3: HP Enterprise 2530 Ethernet Switch Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 4: Interconnect Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 5: Connection from CMSS to Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 6: Connection from Switch to Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 7: Connection from Switch to Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 8: An Underlay Network (IP Addresses Defined by ISP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 9: NBMA Network (Foundation of Overlay) (IP Addresses Defined by Overlay) . . . . . . . . . 19
Figure 10: Physical Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 11: Additional Static VPN Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 12: Full Mesh of Tunnels Between Physical Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 13: Built-Out System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 14: Point-to-Point Links for a Four-Site System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 15: Radio ID as Code or Radio Type Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 16: Radio ID as Attribute Based Code Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 17: Two-Site Capacity Max System Reference Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 18: HP Enterprise MSR 2003 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 19: Rear View of MSR 2003 with 4-Port Switch Module Installed . . . . . . . . . . . . . . . . . . . . 48
Figure 20: Hewlett Packard Enterprise 2530 Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 21: Default Hewlett Packard Enterprise 2530 Ethernet Switch Layout . . . . . . . . . . . . . . . . . 51
Figure 22: Default Cisco 3650 Ethernet Switch Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 23: ADVPN Dynamic Tunnel Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 24: Two HP 2530 Ethernet Switches at a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 25: Typical Laptop Connections to Load Operating System . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 26: Test the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 27: Radio Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 28: HP ProLiant DL380 Gen9 Capacity Max System Server . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 29: HP ProLiant DL380 Gen9 Capacity Max System Server Ethernet Ports . . . . . . . . . . . 113
Figure 30: Example of Site with Multiple Repeaters Connected to an HP 2530 Switch . . . . . . . . 139
Figure 31: Example of Site with Multiple Repeaters Connected to a Cisco Switch . . . . . . . . . . . . 140
Figure 32: Example of Integrated Switch Module Connected to Two Ethernet Switches . . . . . . . 141
Figure 33: Primary Repeater Pin #19 Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 34: Redundant Repeater Pin #19 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 35: Example of XPR Repeater Hardware Redundancy Switching Circuit . . . . . . . . . . . . . 148
Figure 36: Impact of Voice Call Duration on Data Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 37: System With Four Sites Using Different Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 38: Roamable Sites Configured in Radio-A, Radio-B and Radio-C . . . . . . . . . . . . . . . . . . 155
Figure 39: Network With Co-Located Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 40: Site Coverage Model for Roaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Figure 41: Boundary of Strong Signal Area Determined by Default RSSI Sampling Threshold . . 159
Figure 42: Impact of Adjustments to Roaming RSSI Threshold on Automatic Roaming . . . . . . . . 160
Figure 43: Dense Overlapping Multi-site Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Send Feedback ix
MN002731A01-A
List of Figures
Figure 44: Isolated No Overlapping Multi-site Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Figure 45: Corridor Multi-site Coverage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 46: Multi-floor Multi-site Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 47: Impact of Setting Preference Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 48: User Mobility Used to Determine Site Preference Level . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 49: Infill Site Strategy Used for Determining Site Preference Level . . . . . . . . . . . . . . . . . . 167
Figure 50: Co-located Sites Strategy Used to Determine Site Preference Level . . . . . . . . . . . . . 168
Figure 51: Reference System #1 for Single Site and Four Repeaters. . . . . . . . . . . . . . . . . . . . . . 182
Figure 52: Reference System #2 for Single Site, Four Repeaters, Co-location
CMSS Redundancy, and Ethernet Switch Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Figure 53: Reference System #3 for Single Site, Four Repeaters, and Applications . . . . . . . . . . 191
Figure 54: Reference System #4 for Two Sites, Four Repeaters Per Site, and Applications . . . . 195
Figure 55: Reference System #5 for Four Sites, Four Repeaters Per Site, Geographic CMSS
Redundancy, Multiple Site Switches, and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
x Send Feedback
MN002731A01-A
List of Tables
Table 1: Classless Inter-Domain Routing (CIDR) Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 2: Allocated Subnets per Sites for Each Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 3: Dynamic Tunneling Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 4: Radio Infrastructure Network Subnets IP Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 5: Radio Network Subnets IP Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 6: Gateway Network Subnets IP Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 7: Gateway Network Subnets IP Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 8: IP Plan for the Application Network Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 9: External Network Subnets IP Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 10: IP Addresses for Each These Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 11: Point-to-Point Links for a Four-Site System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 12: Capacity Max IP Plan Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 13: Unique Identifier in DMR Trunking Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 14: Unique Site ID of an RF Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 15: Summary of Entity Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 16: Channel Plan Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 17: Segmentation of Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 18: Possible Channel Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 19: Channel Plan Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 20: Overlapping Frequency Range by Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 21: Typical Configured Parameters for Routers and Switches . . . . . . . . . . . . . . . . . . . . . . . 48
Table 22: VLANs Configuration Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 23: VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 24: Additional Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 25: IP Packet Source and Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 26: Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 27: Three Ethernet Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 28: Capacity Max System Server IP Addressess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Table 29: TC and VRC Gateway Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Table 30: MOTOTRBO Network Interface Service Configuration Methods . . . . . . . . . . . . . . . . . . 130
Table 31: Example of Standardized 24-Port Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Table 32: Recommendations for Assignment of Repeaters to Ethernet Switches. . . . . . . . . . . . . 143
Table 33: Recommend Pins Numbers per Repeater Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Table 34: Configurations Required to Send Radio to Server Data on an
Enhanced GPS Revert Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Table 35: Site Adjacency of Network Shown in Figure 37 and Figure 38 . . . . . . . . . . . . . . . . . . . 156
Table 36: Site Adjacency With Co-Located Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Table 37: Recommended Threshold Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 38: Configured Site Preference Level in Radio-A and Radio-B for
Network in Figure 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Table 39: Recommended Site Preference Level for Sites as Illustrated in Figure 48 . . . . . . . . . . 166
Table 40: Recommended Site Preference Level for Sites Shown in Figure 49 . . . . . . . . . . . . . . . 167
Table 41: Recommended Site Preference Level for Sites Shown in Figure 50 . . . . . . . . . . . . . . . 168
Send Feedback xi
MN002731A01-A
List of Tables
Table 42: Capacity Max System Server (CMSS) Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Table 43: MTR 3000 Repeater Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Table 44: XPR 8400 Repeater Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 45: XPR 8380 Repeater Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 46: SLR 5700 Repeater Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 47: Hewlett Packard MSR 2003 AC Router Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 174
Table 48: Cisco 2911 Router Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Table 49: Hewlett Packard Procurve 2530-24 Switch Specifications . . . . . . . . . . . . . . . . . . . . . . 175
Table 50: Cisco 3650 Switch Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Table 51: Common System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Table 52: Reference System #1 Configuration for Single Site and Four Repeaters . . . . . . . . . . . 182
Table 53: Reference System #1 IP Address for System with Single Site and
Four Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Table 54: Reference System #2 Configuration for with Single Site, Four Repeaters,
Co-location CMSS Redundancy, and Ethernet Switch Redundancy . . . . . . . . . . . . . . . . . . . . 186
Table 55: Reference System #2 IP Address for Single Site, Four Repeaters,
Co-location CMSS Redundancy, and Ethernet Switch Redundancy . . . . . . . . . . . . . . . . . . . . 189
Table 56: Reference System #3 Configuration for Single Site, Four Repeaters,
and Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Table 57: Reference System #3 IP Address for Single Site, Four Repeaters,
Table 58: Reference System #4 Configuration for Two Sites, Four Repeaters Per Site,
Table 59: Reference System #4 IP Address for Two Sites, Four Repeaters Per Site,
Table 60: Reference System #5 Configuration for System With Four Sites,
Four Repeaters Per Site, Geographic CMSS Redundancy Multiple Site Switches,
Table 61: Reference System #5 IP Address for Four Sites, Four Repeaters Per Site,
Geographic CMSS Redundancy Multiple Site Switches, and Applications . . . . . . . . . . . . . . . 208
Table 62: Conditions for Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
xii Send Feedback

MN002731A01-A
Configuration Overview
Chapter 1
Configuration Overview 1
Capacity Max System Confuration

This document is not intended to provide step by step instructions on training or navigating through
Radio Management.
This chapter describes the high level order of configuring a Capacity Max system. It provides a brief
explanation of each step within the process. The brief explanations are not meant to describe the exact
procedures, but rather to provide a high level understanding of the overall process and scope. The
chapters that follow cover high level configuration steps in more detail and address specific
configuration topics.
Prior to configuring a Capacity Max System, a couple configuration strategies should be considered:
System Staging and Phased Integration.
System Staging
When configuring and integrating large complex communication systems, it is almost always
recommended to stage the system in a controlled environment prior to deploying the equipment.
Motorola offers system staging services. This allows configuration, testing, and debugging to occur with
the convenience of equipment collocation. System Staging can sometimes be difficult to properly stage
the RF antenna system and the wide area links of a communication system accurately. But the more
similar the staged system can be to the actual deployed system, the fewer configurations are required in
the field. Knowing how features function in a controlled environment aids in troubleshooting issues that
arise in the field.
Phased Integration
When configuring and integrating large complex communication systems, it is almost always
recommended to segment the configuration into phases. Core hardware and features are commonly
configured and tested first, then addition features are added, enabled, and tested. This allows the
testing of the core features without the distraction of complex interactions between features. Knowing
how features function prior to enabling other features and hardware aids in troubleshooting issues that
arise. As experience and confidence grows, fewer phases are necessary.
For example, one might wish to verify voice group calls operate correctly before adding advanced data
features, or verify radio to radio operation at a single site prior to radio to radio calls across multiple
sites. Voice consoles, data applications, and phone service may be added after. Another smart
approach is to verify that a radio configuration operates as desired prior to programming thousands of
radios with that configuration. Same is true for verifying that repeaters at a site operate correctly before
programming every repeater in the system. These strategies may save hours of re-programming.
Capacity Max Configuration High Level Steps

Although there is no single long required sequential order to the overall configuration process, there are
a few best practices to consider if configuring a Capacity Max System for the first time. As experience
grows, adjusting the configuration order to meet customer constraints (such as access to equipment or
sites) will become obvious.
Send Feedback 1
MN002731A01-A
Chapter 1: Configuration Overview
As a pre-requisite to configuring the system, it is assumed that the “system planning” phase has already
been completed. This includes determining what equipment and deployment is necessary to meet the
needs of the customer: number of sites, number of repeaters, and others.
The following figure identifies the high level configuration steps. Each step is described briefly in the
subsequent paragraphs.
Figure 1: High Level Process of Capacity Max System Configuration
FLOOR PLAN, RACKING CONFIGURE REPEATERS

& POWER
SOFTWARE INSTALL & CONFIGURE

FIRMWARE UPGRADE SUBSCRIBERS
CONFIGURE CAPACITY
EQUIPMENT CABLING MAX SYSTEM SERVER
(CMSS)
PRE-CONFIGURATION CONFIGURE SYSTEM

PLANNING ADVISOR CLIENT
CONFIGURE CONFIGURE
THE NETWORK DATA GATEWAY
CONFIGURE RADIO CONFIGURE BATTERY

MANAGEMENT MANAGEMENT
IMPORT SOFTWARE CONFIGURE VOICE

LICENSES APPLICATIONS
CONFIGURE SYSTEM CONFIGURE DATA

PARAMETERS APPLICATIONS
2 Send Feedback
MN002731A01-A
Floor Plan, Racking, and Power

An important step is determining how and where the equipment is going to fit into the customer’s sites.
This includes the routers, switches, repeaters, Capacity Max System Server (CMSS), and other PCs.
RF receiving and combining equipment and antenna space on the tower should also be considered.
A summary of the dimensions, rack units, power requirements, and operating temperature for the
Capacity Max System Server, repeaters, and recommended network equipment are provided in the
Data Revert Channel Optimization on page 151.
Software Installation and Firmware Upgrade

Before configuring, software must be installed and firmware upgraded, if necessary. In most cases,
repeaters and subscribers are shipped with the latest firmware versions. If they do not have the latest,
Radio Management can be used to upgrade the firmware. The appropriate upgrade packages must be
acquired and loaded into Radio Management. The repeaters and subscriber’s can be upgraded at the
same time they are configured. The Capacity Max System Server (CMSS) is shipped pre-loaded with
the latest software versions. If it does not have the latest, a software application (ESU) is provided to
upgrade the software. Radio Management, the data gateway (MNIS), and Battery Management must be
installed on the appropriate computer. The computer specifications are provided in Appendix Chapter
29, “Capacity Max Hardware Specifications”. Third party voice and data applications may require a
software install as well.
Equipment Cabling
Capacity Max inter-equipment cabling is primarily network cabling. The Capacity Max System Server,
repeaters, Radio Management, MNIS data gateway, system advisor client, and battery management
connect to a network switch, and then to a network router with standard network cables. The ports used
on the network switch for each device is dependent on the network switch configuration. See
Configuring a Capacity Max System Transport Network on page 45 for a common switch layout and
more details on the network configuration.
There are a few exceptions. Radio Management uses USB cables when initially programming
subscribers and repeaters. There is also specialized wiring between main and alternate repeaters when
hardware redundancy is required. The repeaters require RF cabling to and from transmit and receiving
RF equipment. See Repeater Hardware Redundancy on page 145.
Site Topology Example

This section provides a very simple example site and displays the port connections for reference. The
CMSS, repeaters, switch, and routers are shown in the following figures. The PCs that hold the Radio
Management, MNIS Data Gateway, and System Advisor Client are not shown.
Send Feedback 3
MN002731A01-A
Figure 2: Example Site Topology
Figure 3: HP Enterprise 2530 Ethernet Switch Layout
4 Send Feedback
MN002731A01-A
Figure 4: Interconnect Overview
Figure 5: Connection from CMSS to Switch
Send Feedback 5
MN002731A01-A
Figure 6: Connection from Switch to Router
Figure 7: Connection from Switch to Repeaters
6 Send Feedback
MN002731A01-A
Pre-Configuration Planning
Prior to starting the configuration, some pre-configuration planning is recommended. The system
planning documentation discusses the necessary equipment and quantity for ordering purposes.
Additional big picture planning for assigning unique identifiers is now required. Detailed explanations are
provided on the following topics:
• Understanding IP Addressing on page 15
• Entity Identifier Assignments on page 29
• Radio Identifier Assignments on page 34
• Talkgroup Identifier Assignments on page 35
• Understanding the Channel Plan on page 36
Network Configuration
It is recommended to configure the network first. This allows the equipment to start communicating on
the network immediately after they are programmed. Programming the equipment before programming
the network is also acceptable if the network or wide area connection availability is an issue.
Guidance is provided so that the appropriately sized wide area links can be acquired from an internet
service provider or a customer’s IT department. The required link bandwidth is dependent on the call
loading of each site.
In most cases, each physical site has a wide area modem, a network router, and a network switch.
Wide area modems are typically provided by the internet service provider. Recommended brands and
models for the network router and network switch are provided as well as selection requirements for
alternate models if utilization of the recommended models is not possible. Single site systems do not
require wide area modems, but they do require a network router.
Guidance in the form of example configurations are available for the recommended brands and models.
The selected configuration then needs to be customized to match the specific customer’s IP network
address plan. See Configuring a Capacity Max System Transport Network on page 45 for more details.
Appendix B: Common System Configurations and Recommended IP Planson page 181 has example
systems.
The HP router and switch operating system may need to be updated if not up to date. Directions on how
to load a new operating system can be found in Loading The OS on a HP MSR2003 Router Using TFTP
on page 62 and Loading The OS on an HP 2530 Switch Using TFTP on page 65.
Directions on how to load configurations in HP routers and switches is included in Loading The
Configuration on an HP MSR2003 Router Using TFTP on page 66 and Loading The Configuration on an
HP 2530 Switch Using TFTP on page 68.
Directions on how to add user log ins and configuring pre-shared keys can be found in User Credentials
in Transport Network Configuration on page 69, and Pre-shared Keys in Transport Network
Configuration on page 72.
See IP Network Multiple Site Switch Configuration on page 137 for details of setting up a multiple
switches at a site.
Send Feedback 7
MN002731A01-A
Radio Management Configuration

Radio Management (RM) can be deployed in various configurations. It consists of a four major
components that can be installed on the same or different computers:
• RM Configuration Client: Edits and Manages Configuration Data
• RM Server: Storage of Configurations
• RM Device Programmer: Programs All Managed Devices
• RM Job Processor: Processes Scheduled Jobs
For the initial configuration of a system, all four components can be installed on the same computer for
simplicity. To speed up the programming of numerous equipment, device programmers can be installed
on several computers at various physical locations and communicate to the RM server through an IP
connection. An offline mode is also available if IP network connectivity is not available. Each device
programmer can support 16 USB connections simultaneously if each radio was pre-programmed with a
unique USB IP address. Otherwise, due to IP conflict, one radio must be connected per device
programmer at a time. Each device programmer is configured with the RM server’s IP address.
Radio Management can perform over the air programming once a MNIS data gateway is configured and
all subscribers are initially configured through the USB and can communicate on the system. An OTAP
authentication key is required in the subscribers during their initial configuration. The device
programmer must be on the same computer as the MNIS data gateway and be set to ‘over the air’
programming.
The following equipment is configured within Radio Management:
• Trunking Controller
• Repeaters,
• Subscribers
• MNIS VRC Gateway
• MNIS Data Gateway
The trunking controller and voice gateway reside on the Capacity Max System Server (CMSS). Radio
Management exports a configuration file that is manually copied over to the MNIS data gateway.
See Radio Management Configuration on page 75 for more details.
Import Software Licenses

During the system planning phase prior to ordering, the necessary Capacity Max licensed features were
identified. Prior to configuration, the provided license identifiers (EID) are available and ready to be
applied to the devices in Radio Management. During initial programming, Radio Management
Configuration Client requires a connection to the internet so that the licensed features can be activated
and registered with an online service. Licenses are applied once the new firmware and configuration is
identified within Radio Management. New firmware, new configuration, and licenses can all be
programmed into a device at the one time. Licenses are required for the number of devices stored in the
RM Database, the CMSS, the repeaters and the subscribers. How to register licenses are briefly
discussed in their configuration sections.
8 Send Feedback
MN002731A01-A
System Parameters Configuration in Radio Management

The first step to configuring the system is to configure the system level parameters within Radio
Management. The trunking controller, repeaters, and subscribers reference the same system level
parameters. This minimizes entering duplicate information for each device type, and therefore lowers
the probability of mistakes.
A system set is created within Radio Management and the system level parameters are set. There are
four major categories of system level parameters, and a couple sub-categories:
• Capacity Max System Set
• Capacity Max Sites
• Capacity Max Channels
• Capacity Max Site Selection Set
• Capacity Max Radio Wide Features Set
• IP System Settings
See System Parameter Configuration on page 78 for details on every system level parameters.
Repeater Configuration in Radio Management

The repeaters can be configured next. The repeaters must be read into Radio Management. Their
physical serial numbers must be provided, and read from the repeater through the USB. Each repeater
requires a unique configuration.
Unique identifiers (ID, IP, and alias) must be assigned to each repeater. This helps identify the repeaters
in the list. A unique IP (the USB IP address) provides the ability to program more than one repeater
through the USB at a time.
Each repeater must reference the previously configured system parameter set. The appropriate system,
site, and channel from the system parameter set must be set for each repeater. The device ID and
redundancy group must be set. The appropriate IP System should be selected.
Each repeater must be plugged into the device programmer through the USB to be programmed with its
configuration the first time. If a unique IP (the USB IP address) has not been written to the repeater
previously, then only one repeater can be connected to the device programmer at a time. After initial
configuration, and a successful registration with the controller, repeaters can be programmed using
Radio Management through their network IP connection.
See Trunking Repeater Configuration on page 99 for more details. See Repeater Hardware
Redundancy on page 145 for information about setting up redundant repeaters. See Data Revert
Channel Optimization on page 151 for more detailed information on configuring data revert repeaters.
Subscriber Configuration in Radio Management

The subscribers can be configured next. The subscribers must be read into Radio Management. Their
serial number must be provided, and then read through the USB. In the initial configuration of the
system, a few subscribers should be sufficient. Subscribers can reference the same configuration.
Unique identifiers (ID, Radio IP, and alias) must be assigned to each subscriber. This helps identify the
subscribers in the list. A unique IP (the USB IP address) provides the ability to program more than one
subscriber through the USB at a time.
Send Feedback 9
MN002731A01-A
A common subscriber configuration has to be created. It should reference the previously configured
system parameter set. A list of contacts can be created for the configuration. Personalities are created
and assigned to zones. The subscriber’s site preference and site restrictions are then configured.
Further guidance on setting these parameters, and others, are provided.
Each subscriber must be plugged into the device programmer through the USB to programmed with its
configuration. If a unique IP (the USB IP address) has not been written to the subscriber previously, then
only one subscriber can be connected to the device programmer at a time.
Once the common subscriber configuration is validated, the remaining radios can be added into Radio
Management and reference the common configuration. Variations of the common configuration can be
made if different groups have different configurations, talkgroup assignments, buttons, and others.
See Trunking Subscriber Configuration on page 105 for more details. See Multi-Site Roaming
Optimization on page 154 for details on optimizing subscriber roaming.
Capacity Max System Server (CMSS) Configuration within Radio

Management
The Capacity Max System Server (CMSS) can be configured next. The CMSS must be added to Radio
Management. The physical serial number, model number, version number and options must be
provided. A configuration must then be created and referenced to the added CMSS device.
The trunking controller, MNIS VRC gateway, and system advisor server reside on the Capacity Max
System Server (CMSS).
The CMSSs Base IP address can be changed within Radio Management. The Base IP address is used
by the CMSS to derive the IP address for the trunking controller, MNIS VRC gateway, and the system
advisor server. The CMSS comes from the factory with a default IP address. Radio Management Device
Programmer must have direct IP connectivity to the Capacity Max System Server (CMSS) to program it
with its configuration. The first time the CMSS is programmed, Radio Management’s computer IP
address must be configured in the same network as the CMSS default IP address and both be
connected to the same IP network switch.
The CMSS references the previously configured system parameter set. The appropriate IP System
Settings should be selected.
See Capacity Max System Server (CMSS) Configuration on page 111 for more details. See Capacity
Max System Server (CMSS) Redundancy on page 144 for more details on redundancy.
The trunking controller and the MNIS VRC gateway have specific configuration parameters in the CMSS
within Radio Management. They are discussed in the following sections.
Trunking Controller Parameters Configuration

There are two additional system configurations for the trunking controller: Subscriber Access Control,
and Talkgroup to Site Association. These are referred to as Capacity Max System Server Data. See
System Parameter Configuration on page 78 for more details on setting the system parameters. A high
level summary is given in the following sections.
Subscriber Access Control

The subscriber access control (SAC) is then configured. The subscriber access control (SAC) is where
subscriber access to the system and the features allowed by that subscriber are centrally controlled. All
subscribers that use a radio ID to access the system can be controlled, including radios, data gateways,
and voice applications.
10 Send Feedback
MN002731A01-A
Talkgroup to Site Association

The talkgroup to site association is then configured. Subscribers affiliate their selected primary talkgroup
on power up, channel change, and site change. Once a subscriber has affiliated a talkgroup at a site,
group calls for that talkgroup are routed to the site. The talkgroup to site association controls which sites
a talkgroup should always be routed to regardless of affiliation, and which sites a talkgroup is specifically
not allowed at.
VRC Gateway Parameter Configuration

The MNIS VRC gateway (the voice gateway) requires a unique site ID, device ID, and redundancy
group that are configured in the CMSS configuration. The active voice talkpath limit must be set to the
number of talkpath licenses purchased for the system.
See MNIS VRC Gateway Configuration on page 118 for more details.
A voice gateway can be utilized by different types of voice applications. Some common applications are:
voice consoles, voice recorders, and phone gateways. The trunking controller must be configured to
route the appropriate call types (group, individual, phone) based on the needs of the voice application.
Voice Console Audio Routing Configuration

A voice console typically monitors voice group calls. The controller must be configured with a list of the
talkgroups to route to the voice gateway used by the voice console. The voice console then dynamically
requests a subset of the talkgroups configured in the voice gateway. Therefore, the voice gateway is
then configured with all the talkgroups a voice console may request. The talkgroup to site association in
the controller is utilized for this. The talkgroups must be configured to always route to the site ID of the
voice gateway.
Voice Recorder Audio Routing Configuration

A voice recorder typically monitors voice individual and group calls. For individual calls, the controller
must be configured with a list of the subscribers IDs to route to the voice gateway used by the voice
recorder. The subscriber access control (SAC) within the controller is used for this. If the subscriber is to
be monitored, it must have the site ID of the voice gateway used by the voice recorder specified in its
SAC record. For group calls, the controller must be configured with a list of all the talkgroups to route to
the voice gateway used by the voice recorder. The talkgroups must be configured to always route to the
site ID of the voice gateway in the talkgroup to site association within the controller.
Phone Gateway Audio Routing Configuration

A phone gateway typically supports radio to phone calls. Therefore, the controller must be configured
with a list of the individuals to route to the voice gateway used by the phone gateway. The subscriber
access control (SAC) within the controller is used for this. Any subscriber allowed to make a phone call
must have a phone gateway specified in the SAC. The site ID of the voice gateway used by the phone
gateway is specified in the SAC record.
Configuring the Parameters for the System Advisor Server

There are no parameters directly related to the system advisor server within the CMSS. The system
advisor server is configured from the system advisor client.
Once the IP network, Capacity Max System Server (CMSS), repeaters, and a few subscribers have
been configured and programmed, the system is able to process wide area radio to radio group and
individual voice calls.
Send Feedback 11
MN002731A01-A
System Advisor Client Configuration

After the Capacity Max System Server (CMSS) is programmed, the system advisor client can be started.
The IP address and port of the system advisor server (https://<SA_SERVER_IP>:9090/) can be entered
as the URL of a web browser on any computer with a direct IP connection to the CMSS. This prompts
the automatic download and install of a java client. Once installed, the system advisor can be
configured. The configuration is available in System Advisor Client (from the main menu, select Tools 
Configure System Advisor Properties). Once configured, the system advisor client shows the
equipment inventory of the system, including sites, channels, and call activity.
See the System Advisor Configuration on page 122 for more details.
MNIS Data Gateway Configuration within Radio Management

The MNIS data gateway can be configured next. The data gateway device must be added to Radio
Management. A configuration must then be created and referenced to the added data gateway device.
A data gateway is not read by Radio Management.
The MNIS data gateway references the previously configured system parameter set. The unique site ID,
device ID, and radio ID must be set. The data gateway does not have a redundancy group.
The radio ID configured for the data gateway is configured in the subscribers as the target for server
data. For example: the text message server ID in the subscriber configuration references the configured
radio ID of the data gateway. Any data messages targeted towards the configured radio ID of the data
gateway is routed to the data gateway and onto the data application.
If the data application needs to monitor data transmissions targeted towards talkgroups, the controller
must be configured to route the talkgroup data to the data gateway’s configured site ID. The talkgroup to
site association in the controller is utilized for this. The talkgroups must be configured to always route to
the site ID of the data gateway.
The data gateway can reside on its own designated computer or on the same computer as the data
application, but not on the CMSS. Radio Management exports a configuration file that must be manually
copied to the computer where the data gateway resides. The data gateway service must be restarted for
the new configuration to take effect.
See MNIS Data Gateway Configuration on page 125 for more details.
Battery Management Configuration

The IMPRES Battery Management application can be configured next. The Battery Management
application must have an MNIS data gateway on the same computer. Battery management is enabled
on the subscribers and the radio ID of the MNIS data gateway is configured as the battery management
radio ID. After power up, within a few hours, the subscribers register their batteries with the battery
management application and their battery data is read. They are read again every few weeks.
Voice Applications Configuration

The voice applications, such as voice consoles, voice recorders, and phone systems can be configured
next. The configuration differs per vendor and per application. Review the particular vendor’s
documentation for configuration details.
12 Send Feedback
MN002731A01-A
Data Applications Configuration

The data applications, such as text message, location, and telemetry can be configured next. The
configuration differs per vendor and per application. Review the particular vendor’s documentation for
configuration details.
System Redundancy Configuration

See Fault Tolerance on page 133 for more details on the impact of hardware failures in a Capacity Max
system. Understanding of hardware failures determines if the impact is acceptable or if the available
software and hardware remedies should be considered.
Send Feedback 13
MN002731A01-A
This page left blank
14 Send Feedback
MN002731A01-A
Pre-Configuration Planning
Chapter 2
Pre-Configuration Planning 2
Understanding IP Addressing
Wide Area Network (WAN)

The Capacity Max system builds an overlay network on top of a WAN underlay network.
The underlay network can be a public internet (such as, Internet Service Provider) comprising
subscriber links (such as, DOCSIS, ADSL, and others.) and modems; private enterprise IP networks
comprising microwave, leased line (such as, T-Carrier, E-Carrier), and/or fiber optic links (such as, OC-
1, OC-3, and others.) and appropriate associated line terminating equipment; or other type of network
technology as long as IPv4 service over an IEEE 802.3u 100BASE-TX Interface (such as Fast Ethernet)
using port speed and duplex auto-negotiation is provided to the Capacity Max system. The underlay
network provider/operator controls and manages the IP address scheme used within their network. In
this chapter, the term Wide Area Network (WAN) generically refers to the underlay network. The
Capacity Max system requires one IP address from the WAN provider for each Physical Location
containing Capacity Max system components. At least one of these IP addresses must be a statically
allocated IP address (does not change over time) while the remaining IP addresses may be dynamically
allocated (possibly changing over time). The statically allocated IP address may be administered as
either a true static IP address or as static DHCP (a.k.a. DHCP reservation). If a higher availability
Capacity Max network is desired, additional statically allocated IP addresses may be required as
described herein.
The overlay network, called the Capacity Max overlay or the Capacity Max network, uses its own IP
address space and this chapter describes a recommended IP addressing scheme to be used in the
Capacity Max network. This IP addressing scheme attempts to anticipate a wide range of deployments
across a wide variety of customers and should suit most situations without significant modifications;
however, some customization of this scheme may be necessary to accommodate a particular system’s
needs. The Capacity Max network uses IP addresses in the RFC-1918, “Address Allocation for Private
Internets”, 172.16.0.0 / 12 address space, using the Classless Inter-Domain Routing (CIDR) notation
(see the following table), which includes all IP addresses in the range 172.16.0.0 through
172.31.255.255. If the WAN provider uses IP addresses in this space, there may be IP address conflicts
between the WAN (underlay) and the Capacity Max (overlay) networks, so the Capacity Max IP address
scheme may require modification to eliminate the conflict should this situation arise.
Table 1: Classless Inter-Domain Routing (CIDR) Notation
Network Mask Network Mask Max Number of

CIDR Notation Dot-Decimal Notation Hosts per Subnet
/8 255.0.0.0 16,777,214
/ 12 255.240.0.0 1,048,574
/ 16 255.255.0.0 65,534
/ 20 255.255.240.0 4,094
/ 24 255.255.255.0 254
/ 25 255.255.255.128 126
Send Feedback 15
MN002731A01-A
Chapter 2: Pre-Configuration Planning
Table 1: Classless Inter-Domain Routing (CIDR) Notation (Cont.)
Network Mask Network Mask Max Number of

CIDR Notation Dot-Decimal Notation Hosts per Subnet
/ 26 255.255.255.192 62
/ 27 255.255.255.224 30
/ 28 255.255.255.240 14
/ 29 255.255.255.248 6
/ 30 255.255.255.252 2
/ 31 255.255.255.254 2
/ 32 255.255.255.255 1
Capacity Max Networks

The Capacity Max network comprises three networks which serve to isolate and manage different types
of network traffic:
• Radio Infrastructure Network
• Gateway Network
• Application Network
Radio Infrastructure Network
The Radio Infrastrucure Network is the principal network of a Capacity Max system. The network
provides IP connectivity between all repeaters in the system and hosts the repeaters and technicians
service laptop computers exclusively.
Gateway Network
The Gateway Network is a network that provides interfaces between the Capacity Max system and
third party applications and hosts the Capacity Max System Server (CMSS, Trunk Controller, System
Advisor, MOTOTRBO™ Network Interface Service (MNIS) Voice & Radio Command (VRC)
Gateway), MNIS Data Gateway, and application servers.
Application Network
The Application Network is a network that primarily hosts non-Motorola equipment, including
application servers and application clients.
The Capacity Max IP Plan recommends using 172.16.0.0 / 16 for the Radio Infrastructure Network and
172.20.0.0 / 16 for combined Gateway and Application Networks.
16 Send Feedback
MN002731A01-A
Capacity Max Subnetworks

Subnetworks belonging to the Radio Infrastructure, Gateway, and Application networks are allocated to
each physical location of a Capacity Max system, as needed, based on the equipment that is present at
a physical location. Repeaters, MNIS Voice & Radio Command Gateways, and MNIS Data Gateways
are provisioned with unique site IDs. These site IDs are also used in this IP plan, which is intended to be
“user-friendly” by having the third octet of an IP address indicate the site ID provisioned into the radio
equipment hosted by a subnet. Table 2 specifies the subnets allocated to each site for these three
networks.
Table 2: Allocated Subnets per Sites for Each Network
Recommended
Equipment siteID Range Network Name Subnet Address
Repeater 1 ≤ siteID ≤ 30 Radio Infrastructure 172.16.siteID.0 / 24
MNIS Data Gateway 31 ≤ siteID ≤ 35 Gateway 172.20.siteID.0 / 25
MNIS Voice & Radio Command 36 ≤ siteID ≤ 40 Gateway 172.20.siteID.0 / 25

Gateway
Non-Motorola N/A Application 172.20.phyLocID.128 /

25
A physical location ID (mnemonic phyLocID) is defined and set equal to the lowest valued siteID used at
a physical location. If the physical location has no Repeaters, MNIS VRC Gateways, or MNIS Data
Gateways present (such as there is no siteID at the location), then the Physical Location ID can be set to
any unique value in the range 1 ≤ phyLocID ≤ 255. However, be advised that Repeaters, MNIS VRC
Gateways, and MNIS Data Gateways must use a site ID in the range 1 ≤ siteID ≤ 40, so physical
locations that never have these devices present (including a CMSS with no VRC Gateway) preferably
select a physical location ID the range 41 to 48. Subnets 172.20.SN.0 / 25, where 36 ≤ SN ≤ 47, can be
used for Capacity Max System Servers (either VRC Gateway, Trunk Controller, or VRC Gateway and
Trunk Controller), as needed, in large systems having more than five CMSSs present.
The CMSS may host a Trunk Controller, MNIS VRC Gateway, or both a Trunk Controller and a MNIS
VRC Gateway. A successful Capacity Max deployment ensures that co-located CMSSs, MNIS Data
Gateways, and repeater sites are each allocated unique siteIDs and provided with their own subnets.
The following are guidances:
• Co-located CMSSs w/ VRC Gateway must each be allocated unique siteIDs and their own subnets
• A redundant CMSS uses the same siteID as its corresponding primary; however, they must each
reside on their own subnet
• Co-located CMSSs w/o VRC Gateway must each be allocated their own subnets
• Co-located MNIS Data Gateways must each be allocated unique siteIDs and their own subnets
• Co-located repeater sites must each be allocated unique siteIDs and their own subnets
• Any combinations of these guidances must each be allocated unique siteIDs and their own subnets
Example 1:
A physical location has a repeater site and a CMSS w/ VRC Gateway co-located. In this example, the
repeater site is allocated a site ID (such as, 1) and a subnet (such as, 172.16.1.0 / 24) and the VRC
Gateway is allocated a site ID (such as, 36) and a subnet (such as, 172.20.36.0 / 25).
Send Feedback 17
MN002731A01-A
Example 2:
A physical location has a repeater site and two non-redundant CMSS w/ VRC Gateway co-located. In
this example, the repeater site is allocated a site ID (such as, 1) and a subnet (such as, 172.16.1.0 / 24),
the first VRC Gateway is allocated a site ID (such as, 36) and a subnet (such as, 172.20.36.0 / 25), and
the second VRC Gateway is allocated a site ID (such as, 37) and a subnet (such as, 172.20.37.0 / 25).
Example 3:
A physical location has a repeater site, a CMSS w/ VRC Gateway, and an MNIS data gateway co-
located. In this example, the repeater site is allocated a site ID (such as, 1) and a subnet (such as,
172.16.1.0 / 24), the VRC Gateway is allocated a site ID (such as, 36) and a subnet (such as,
172.20.36.0 / 25), and the MNIS data gateway is allocated a site ID (such as, 31) and a subnet (such as,
172.20.31.0 / 25).
Example 4:
A physical location has two repeater sites and a CMSS w/ VRC Gateway co-located. In this example,
the first repeater site is allocated a site ID (such as, 1) and a subnet (such as, 172.16.1.0 / 24), the
second repeater site is allocated a site ID (such as, 2) and a subnet (such as, 172.16.2.0 / 24), and the
VRC Gateway is allocated a site ID (such as, 36) and a subnet (such as, 172.20.36.0 / 25).
Creating a Capacity Max Overlay Network

There are many technologies available to create underlay and overlay networks. This section assumes
the underlay network comprises a public Internet Service Provider (ISP) using Data Over Cable Service
Interface Specification (DOCSIS) or Asymmetric Digital Subscriber Line (ADSL) links. This section
further assumes the overlay minimally comprises Generic Routing Encapsulation (GRE) tunneling. For
additional security, IPsec Tunnel Mode (not Transport Mode) can be used in conjunction with GRE
tunneling and has the following possible modes of operating:
• Authentication Header (AH) – provides data integrity protection, sender authentication, and replay
attack protection
• Encapsulating Security Payload (ESP) – provides data integrity protection, sender authentication,
replay attack protection, and confidentiality
• Authentication Header (AH) & Encapsulating Security Payload (ESP)
To simplify the configuration of network equipment to create the overlay network, use a dynamic
tunneling protocol, which automatically creates site-to-site tunnels upon demand. Auto Discovery Virtual
Private Network (ADVPN) and Dynamic Multipoint Virtual Private Network (DMVPN) are examples of
dynamic tunneling protocols. In addition, use a Link-State routing protocol, such as Open Shortest Path
First (OSPF), within the overlay network (for example, within the VPN tunnel network).
Dynamic tunneling protocols firstly rely upon a Non-Broadcast Multiple Access (NBMA) network being
the foundation of the overlay network. Every router requires an IP address on the NBMA network to
establish tunnel endpoints. The Capacity Max network IP plan recommends using IP addresses
belonging to 172.30.0.0 / 20 for the NBMA network using the convention 172.30.0.phyLocID / 20, where
1 ≤ phyLocID ≤ 255 and phyLocID is as previously defined. When the underlay network uses
dynamically allocated IP addresses, dynamic tunneling protocols additionally rely upon a server, integral
to a centralized “hub” router, to track associations between every router’s IP address in the underlay
WAN network and the router’s corresponding IP address in the overlay network. ADVPN calls this a
VPN Address Management (VAM) server and DMVPN calls this a Next Hop Server (NHS). The
centralized hub router must be located at a physical location having a statically allocated IP address in
the underlay network. Figure 8 on page 19 and Figure 9 on page 19 illustrate physical locations with
underlay (WAN) IP addresses on the left (such as, WAN_IP_1) and corresponding overlay (NBMA) IP
addresses on the right (such as, 172.30.0.1).
18 Send Feedback
MN002731A01-A
Figure 8: An Underlay Network (IP Addresses Defined by ISP)
WAN IP_1 WAN IP_2

phyLocID 1 phyLocID 2
Wide
Area
Network
WAN IP_6 WAN IP_3
WAN IP_5 WAN IP_4
Figure 9: NBMA Network (Foundation of Overlay) (IP Addresses Defined by Overlay)
phyLocID 1 172.30.0.2/20 phyLocID 2
172.30.0.1/20
172.30.0.6/20 172.30.0.3/20
Non-Broadcast
Multiple Access
Network
172.30.0.5/20
172.30.0.4/20
Send Feedback 19
MN002731A01-A
A Capacity Max network assumes that physical location 1 has a statically allocated IP address in the
underlay network and therefore physical location 1 provides a hub, or core, router for the Capacity Plus
network. To connect physical locations together in the overlay network, static VPN tunnels are
configured between every physical location’s router (each assumed to have a dynamically allocated
WAN IP address) and the hub router (having a statically allocated WAN IP address). This is shown in
Figure 10.
Figure 10: Physical Location
172.30.0.2/20
172.30.0.1/20
172.30.0.6/20 172.30.0.3/20
Non-Broadcast
Multiple Access
Network
172.30.0.5/20
` phyLocID 4
phyLocID 5
172.30.0.4/20
STATIC TUNNEL
The hub router is a single point of failure for the initial creation of the overlay network; therefore, it is
recommended to additionally request a static WAN IP address for physical location 2 from the ISP
provider and configure the router at physical location 2 as an alternate hub router. If this option is
desired, additional static VPN tunnels are configured between every physical location’s router (each
assumed to have a dynamically allocated WAN IP address) and physical location’s 2 router (having a
statically allocated WAN IP address). This is shown in Figure 11 on page 21.
20 Send Feedback
MN002731A01-A
Figure 11: Additional Static VPN Tunnel
172.30.0.2/20
172.30.0.1/20
172.30.0.6/20 172.30.0.3/20
Non-Broadcast
Multiple Access
Network
172.30.0.5/20
172.30.0.4/20
STATIC TUNNEL
DYNAMIC TUNNEL – OPTIONAL STATIC TUNNEL
Further levels of dynamic tunneling redundancy may be achieved, depending on router capabilities, by
configuring additional hub routers within the network. Table 3 indicates redundancy level, phyLocID
assignment, and IP address of hub routers for non-redundant and redundant configurations.
Table 3: Dynamic Tunneling Redundancy
Non VAM Server or

Redundant Redundant Next Hop Server
Redundancy Level Configuration Configuration phyLocID (NHS) IP Address
Primary (1), Required X X 1 172.30.0.1 / 20
Secondary (2), X 2 172.30.0.2 / 20

Recommended
It is common practice to allocate a loopback IP address to every router in the network and the loopback
IP address can be used to remotely manage the router. Therefore, it is recommended to add a loopback
IP addresses from the 172.30.16.0 / 20 IP space as 172.30.16.phyLocID / 32 to every router in the
Capacity Max network.
Once the static tunnels are established and a dynamic routing protocol is enabled, the routers build the
remaining tunnels dynamically, on demand, as needed. This results in a full mesh of tunnels between
physical locations, as shown in Figure 12 on page 22.
Send Feedback 21
MN002731A01-A
Figure 12: Full Mesh of Tunnels Between Physical Locations
172.30.0.2/20
172.30.0.1/20
172.30.0.6/20 172.30.0.3/20
Non-Broadcast
Multiple Access
Network
172.30.0.5/20
172.30.0.4/20
STATIC TUNNEL
DYNAMIC TUNNEL – OPTIONAL STATIC TUNNEL
DYNAMIC TUNNEL – Setup Automatically When Needed
Figure 13 illustrates a built-out system having six physical locations. Not every physical location requires
a subnet for all three networks.
Figure 13: Built-Out System
22 Send Feedback
MN002731A01-A
Detailed Capacity Max IP Plan

A detailed IP plan for the Radio Infrastructure, Gateway, and Application networks is now addressed. In
general, each of these three networks reserves the first 16 IP addresses (including the IETF-defined
subnet address) of their respective site subnets for Motorola use, and should not be used for any other
purpose. Each of these three networks also reserves the next eight IP addresses for networking
equipment (such as, switches and routers) and the last five IP addresses for a Dynamic Host
Configuration Protocol (DHCP) pool.
Table 4 specifies an overview of the IP plan for the Radio Infrastructure Network subnets.
Table 4: Radio Infrastructure Network Subnets IP Plan
IP Address (all are / 24) Function
172.16.siteID.0 IETF-Defined Subnet Address
172.16.siteID.1 – 172.16.siteID.15 Reserved for Motorola Use
172.16.siteID.16 – 172.16.siteID.23 Switches and Routers
172.16.siteID.24 – 172.16.siteID.86 Repeaters
172.16.siteID.87 – 172.16.siteID.249 Reserved for Future Use
172.16.siteID.250 – 172.16.siteID.254 DHCP Pool
172.16.siteID.255 IETF-Defined Subnet Directed Broadcast
Table 5 specifies detailed host IP assignments for the Radio Network subnets.
Table 5: Radio Network Subnets IP Assignments
IP Address (all are / 24) Function Comments
172.16.siteID.1 Registrar Agent Virtual IP Address
172.16.siteID.2 Control Channel Manager Virtual IP Address
172.16.siteID.16 Ethernet Switch N/A
172.16.siteID.17 2nd Ethernet Switch, if N/A

present
172.16.siteID.20 Router (Default Gateway) N/A
172.16.siteID.24 Repeater #1 Management Derived from SubnetAddr, RptrID, &

RedundancyID
172.16.siteID.25 Redundant Repeater #1 Derived from SubnetAddr, RptrID, &

Mgmt RedundancyID
172.16.siteID.26 Repeater #1 Payload Virtual IP Address
172.16.siteID.27 Repeater #2 Management Derived from SubnetAddr, RptrID, &

RedundancyID
172.16.siteID.28 Redundant Repeater #2 Derived from SubnetAddr, RptrID, &

Mgmt RedundancyID
172.16.siteID.29 Repeater #2 Payload Virtual IP Address
Send Feedback 23
MN002731A01-A
Table 5: Radio Network Subnets IP Assignments (Cont.)
172.16.siteID.250 - DHCP Pool (5 IP Addresses) Technician Laptop (such as, System Advisor
172.16.siteID.254 Client, CPS-RM Client, Repeater Diagnostics
Client, and others.)
Virtual IP Addresses are automatically derived from provisioned parameters such as SubnetAddr,
RptrID, & RedundancyID and their use by a particular repeater may change with time.
The repeater host IDs (4th octet of the IP address) are computed as follows:
Rptr(n)MgmtHostID = 3n + 21
RedundantRptr(n)MgmtHostID = 3n + 22
Rptr(n)PayloadHostID = 3n + 23
Table 6 specifies an overview of the IP plan for the Gateway Network subnets.
Table 6: Gateway Network Subnets IP Plan
172.20.siteID.0 IETF-Defined Subnet Address
172.20.siteID.1 – 172.20.siteID.15 Reserved for Motorola Use
172.20.siteID.16 – 172.20.siteID.23 Switches and Routers
172.20.siteID.24 – 172.20.siteID.39 Motorola MNIS Data Gateway & Application

Servers
172.20.siteID.40 – 172.20.siteID.121 Reserved for Future Use
172.20.siteID.122 – 172.20.siteID.126 DHCP Pool
172.20.siteID.127 IETF-Defined Subnet Directed Broadcast
Table 7 specifies detailed host IP assignments for the Gateway Network subnets.
Table 7: Gateway Network Subnets IP Assignments
172.20.siteID.1 Trunk Controller N/A
172.20.siteID.3 ESU N/A
172.20.siteID.4 MNIS VRC Gateway (see N/A

Note)
172.20.siteID.5 System Advisor N/A
172.20.siteID.16 Ethernet Switch Used only when Radio Subnet is not present
172.20.siteID.17 2nd Ethernet Switch, if Used only when Radio Subnet is not present
present
172.20.siteID.20 Router (Default Gateway) N/A
24 Send Feedback
MN002731A01-A
Table 7: Gateway Network Subnets IP Assignments (Cont.)
172.20.siteID.24 MNIS Data Gateway (see May additionally host server applications and
Note) clients
172.20.siteID.25 Radio Management Server If not co-resident on MNIS Data Gateway
172.20.siteID.26 Battery Management Server If not co-resident on MNIS Data Gateway
172.20.siteID.27 - Available for other servers N/A

172.20.siteID.39
(13 IP Addresses)
172.20.siteID.122 - DHCP Pool Technician Laptop (such as, System Advisor

172.20.siteID.126 Client, CPS-RM Client, Repeater Diagnostics
(5 IP Addresses) Client, and others.)
NOTICE:
Either an MNIS VRC Gateway or and MNIS Data Gateway may be present in a subnet, but not
both.
Table 8 specifies an overview of the IP plan for the Application Network subnets.
Table 8: IP Plan for the Application Network Subnets
172.20.phyLocID.128 IETF-Defined Subnet Address
172.20.phyLocID.129 – 172.20.phyLocID.143 Reserved for Motorola Use
172.20.phyLocID.144 – 172.20.phyLocID.151 Switches and Routers
172.20.phyLocID.152 – 172.20.phyLocID.167 Third Party Application Servers
172.20.phyLocID.168 – 172.20.phyLocID.191 Reserved for Future Use
172.20.phyLocID.192 – 172.20.phyLocID.254 DHCP Pool
172.20.phyLocID.255 IETF-Defined Subnet Directed Broadcast
Table 9 specifies detailed host IP assignments for the External Network subnets.
Table 9: External Network Subnets IP Assignments
172.20.phyLocID.144 Ethernet Switch Used only when Radio and Gateway Subnets are
not present
172.20.phyLocID.145 2nd Ethernet Switch, if Used only when Radio and Gateway Subnets are
present not present
172.20.phyLocID.148 Router (Default Gateway) N/A
172.20.phyLocID.152 3rd Party Network May additionally host server applications and
Management Server clients
172.20.phyLocID.153 Console Server If not co-resident on MNIS Data Gateway
Send Feedback 25
MN002731A01-A
Table 9: External Network Subnets IP Assignments (Cont.)
172.20.phyLocID.154 Location Server If not co-resident on MNIS Data Gateway
172.20.phyLocID.155 Text Message Server If not co-resident on MNIS Data Gateway
172.20.phyLocID.156 - Third Party Application N/A

172.20.phyLocID.167 Servers (12 IP Addresses)
172.20.phyLocID.192 - DHCP Pool (63 IP Technician Laptop and Application Clients

172.20.phyLocID.254 Addresses)
Special Considerations for Private (Enterprise) Wide Area Networks

The underlay network need not be provided by a public ISP, rather, it could be a private (enterprise)
network. A recommendation is to minimally use GRE tunneling as described previously so that the
recommended Capacity Max IP plan can be adhered to. If GRE tunneling is not desired or not possible,
then a suitable IP plan needs to be created while working with the customer’s IT department. The
constraints regarding co-located CMSSs, MNIS Data Gateways, Repeaters Sites, siteIDs, and unique
subnets, previously described, must be followed.
Special Considerations for Point-to-Point Links

When creating a private IP network, physical locations may be connected with point to point links (such
as, private microwave). Point to point links each form their own, small IP network with each end of the
link requiring an IP address. The 172.31.0.0 / 16 IP address space is available for this purpose. Every
point to point link is allocated a CIDR “/ 30” subnet from the 172.31.0.0 / 16 address space. Each of
these subnets has four IP addresses, which are used in Table 10.
Table 10: IP Addresses for Each These Subnets
Subnet Offset (added to 4th Octet) Usage
+0 IETF-Defined Subnet Address
+1 The Site with the Lower phyLocID
+2 The Site with the Higher phyLocID
+3 IETF-Defined Subnet Directed Broadcast
A clever way to assign subnets to point-to-point links is to allocate a unique phyLocID to every physical
location in the Capacity Max system (consistent with guidelines previously presented), beginning with
phyLocID 1. Then, allocate subnets according to the following rules:
• The first two octets of the subnet IP address shall be 172.31.
• The 3rd octet of the subnet IP address shall be equal to the value of the lower phyLocID of the two
physical locations sharing the point-to-point link.
• The 4th octet of the subnet IP address shall be equal to four multiplied by one less than the value of
the higher phyLocID of the two physical locations sharing the point-to-point link (such as,
4x(phyLocID-1)).
26 Send Feedback
MN002731A01-A
For example, using this system, the subnets and IP addresses for a full mesh of point-to-point links for a
four site system are listed in Table 11.
Table 11: Point-to-Point Links for a Four-Site System
Link Subnet Site w/ Low phyLocID Site w/ High phyLocID
phyLocID = 1 172.31.1.4 / 30 172.31.1.5 172.31.1.6
phyLocID = 2
phyLocID = 1 172.31.1.8 / 30 172.31.1.9 172.31.1.10
phyLocID = 3
phyLocID = 1 172.31.1.12 / 30 172.31.1.13 172.31.1.14
phyLocID = 4
phyLocID = 2 172.31.2.8 / 30 172.31.2.9 172.31.2.10
phyLocID = 3
phyLocID = 2 172.31.2.12 / 30 172.31.2.13 172.31.2.14
phyLocID = 4
phyLocID = 3 172.31.3.12 / 30 172.31.3.13 172.31.3.14
phyLocID = 4
The resulting 4-site system using a full mesh of private point-to-point links is shown in Figure 14.
Figure 14: Point-to-Point Links for a Four-Site System
172.31.1.5 172.31.1.6
172.31.1.4 / 30
SITE 1 SITE 2
172.31.1.13 172.31.1.9 172.31.2.13 172.31.2.9
172.31.1.8 / 30 172.31.2.12 / 30
172.31.1.12 / 30 172.31.2.8 / 30
172.31.1.14 172.31.2.14 172.31.1.10 172.31.2.10
172.31.3.14 172.31.3.13
172.31.3.12 / 30
SITE 4 SITE 3
Send Feedback 27
MN002731A01-A
Capacity Max IP Plan Summary

A high level summary of the entire Capacity Max IP Plan is provided in Table 12.
Table 12: Capacity Max IP Plan Summary
IP Space Network Name Comments
172.16.0.0 / 16 Radio Infrastructure Network 172.16.0.0 / 24 Is Reserved – Do Not Use
172.17.0.0 / 16 Reserved – Do Not Use
172.20.0.0 / 16 Gateway & Application Networks 172.20.0.0 / 24 Is Reserved – Do Not Use
172.270.0 / 16 Reserved – Do Not Use
172.28.0.0 / 16 Available for Dealer Use
172.29.0.0 / 16 Available for Dealer Use
172.30.0.0 / 20 Non-Broadcast Multiple Access (NBMA)
172.30.16.0 / 20 Router Loopback
172.31.0.0 / 16 Point to Point
28 Send Feedback
MN002731A01-A
Entity Identifier Assignments

This section describes ways how to set the identifiers of various entities in a Capacity Max system.
Unique Identifier in DMR Trunking Systems

A Capacity Max system has a unique identifier among the DMR trunking systems in its coverage area. A
DMR trunking system is identified by an ID, which is called “Network ID” in DMR Trunking Protocol. The
range of the Network ID is 0 to ‘n’, where the value of ‘n’ depends upon the “model” (such as vaguely
speaking “size of a system in terms of number of sites”) of the system as defined by the DMR Trunking
Protocol. Table 13 shows the range of network ID and the maximum number of RF sites for each model
for a DMR Trunking system.
Table 13: Unique Identifier in DMR Trunking Systems
Maximum Number
Model Network ID of RF Sites
Tiny 0 to 511 7
Small 0 to 127 31
Large 0 to 15 255
Huge 0 to 3 1023
The model and the network ID of a system is transmitted periodically over-the-air by the system. A radio
uses the over-the-air broadcast of model and the network ID to acquire a control channel of its system.
While selecting the model and the network ID of the system, a system administrator should keep the
following two suggestions in mind:
• The model should be the smallest model, whose “max number of RF sites” is not less than the
maximum number of RF sites required by the system currently or in future. For example, if the
system currently has six sites and may add up to two additional sites in the future, then the model
should be “Small”. The use of “smallest model” allows co-locating more DMR based trunking
systems.
• The model and the network ID together are unique among all DMR trunking systems in the coverage
area of the system. The uniqueness ensures that a radio always attaches to its system and not a
neighboring system.
NOTICE:
Any change in the model or the network ID, in the future, requires reprogramming of all the radios
in the system.
The System's Network ID is configured in the System Set within Radio Management (RM). It must also
be entered in the Capacity Max Repeater IP System Settings to allow RM to join the system. See
System Parameter Configuration on page 78 for more details.
The Network ID is also configured in the System Advisor Server to allow the System Advisor to join the
system. See System Advisor Configuration on page 122 for more details.
Send Feedback 29
MN002731A01-A
Unique Site ID of an RF Site in the System

Every RF site has a unique Site ID among all the sites of its Capacity Max system. Within a Capacity
Max system, an RF Site is identified by a Site ID. A system administrator has to ensure that the Site ID
allocated to an RF site is unique. The range of available Site IDs depends upon the “model” of the
system as defined by the DMR Trunking Protocol. This is shown in Table 14 for a Capacity Max system.
Table 14: Unique Site ID of an RF Site
Site ID of an RF
Site or a
Model Network Id Gateway Comment
Tiny 0 to 511 1 to 7
Small 0 to 127 1 to 31
Large 0 to 15 1 to 40 A Capacity Max system supports a maximum of 30 RF

sites, 5 VRC gateways and 5 Data gateways
Huge 0 to 3 1 to 40
NOTICE:
A physical location may have multiple site IDs if more than one RF site or more than one gateway
or a combination of them are co-located.
Number the RF Site IDs in sequence 1 to 15. These Site IDs should align with the 3rd octet of the IP
address as indicated in Understanding IP Addressing on page 15.
The Site ID for an RF site is configured in the Capacity Max Sites in the System Set within Radio
Management. See System Parameter Configuration on page 78 for more details.
Unique Site ID of a Gateway in the System

A gateway (MNIS VRC Gateway and MNIS Data Gateway) should also have a unique site ID. Within a
Capacity Max system, an MNIS VRC Gateway and an MNIS Data Gateway are identified by a Site ID. A
system administrator should ensure that the Site ID allocated to a gateway is unique. The range of
available Site IDs depends upon the “model” of the system as defined by the DMR Trunking Protocol.
See Table 14.
It is important to note that a redundant MNIS VRC Gateway has the same site ID as its corresponding
primary MNIS VRC Gateway. Since data gateway redundancy is not supported, every MNIS Data
Gateway requires a unique site ID.
NOTICE:
A physical location can have multiple site IDs if more than one RF site or more than one gateway
or a combination of them are co-located.
Number the MNIS Data gateway Site IDs from 31 to 35 and the MNIS VRC gateway Site IDs from 36 to
40. These Site IDs should align with the 3rd octet of the IP address as indicated in Understanding IP
Addressing on page 15. In order to utilize these recommended site IDs, the network model must be
configured as Large.
The site ID for a gateway site (MNIS VRC Gateway and MNIS Data Gateway) is configured in the
Capacity Max Sites in the System Set within Radio Management. A site must be added for each primary
gateway. See System Parameter Configuration on page 78 for more details.
30 Send Feedback
MN002731A01-A
Each primary gateway site must be added to its own Site Selection List. The MNIS VRC gateway site
selection list is referenced from the primary and redundant CMSS configuration, and the MNIS data
gateway site selection is referenced from the MNIS data gateway configuration.
Unique Device ID for a Repeater at a Site

A primary repeater at a site is uniquely identified by a Device ID. A system administrator should ensure
that the Device ID allocated to a primary repeater is unique per site. The range of device IDs for a
repeater is 1 to 21.
The first repeater at each site should be device ID 1, second device ID 2, and so forth. The device ID is
used to derive the repeater's IP address. See Understanding IP Addressing on page 15 for more details.
A Capacity Max system supports the MOTOTRBO hardware redundancy configuration, in which a GPIO
output line of the primary repeater is connected to a GPIO input line of the redundant repeater. A failure
or major alarm of the primary repeater triggers the redundant repeater to become active.
The Device ID of the primary and the redundant repeaters should be same and their Redundancy Group
ID should be different. The Redundancy Group ID is either ‘Primary’ or ‘Alternate’. The Redundancy
Group ID is applicable to all repeaters including the Data Revert repeaters and the Control Channel
repeaters.
The Device ID and Redundancy Group ID are configured in the Radio Systems view (antenna icon) in
Radio Management.
Unique Device ID for a CMSS, MNIS Data Gateway, and Device

Programmer in the System
The following devices are also uniquely identified by a Device ID:
• CMSS (Trunking Controller, MNIS VRC Gateway, and System Advisor Server)
• Radio Management Device Programmer
Within a Capacity Max system, these devices are identified by a Device ID. A system administrator
should ensure that the Device ID allocated to these devices is unique between them. They do not have
to be unique with repeaters. The range of device ID for these devices is 1 to 63.
The primary CMSS should be configured with a Device ID of 1, and the alternate CMSS should be
configured with a Device ID of 2. The Primary should have a Redundancy Group ID of Primary, and the
Alternate should have a Redundancy Group ID of Alternate. The Device ID and Redundancy Group ID
of the CMSS are configured in the Radio Systems view (antenna icon) in Radio Management.
The Trunking Controller that resides on a CMSS acquires their Device ID and Redundancy Group ID
from the CMSS configuration. Therefore no additional configuration required.
The MNIS VRC Gateways that reside on a CMSS acquire their Device ID and Redundancy Group ID
from the CMSS configuration. Therefore no additional configuration required.
The System Advisor Server that resides on a CMSS must be configured with the same Device ID as a
corresponding CMSS. The Device ID of the System Advisor Server is configured from the System
Advisor Client. The setting is available from the Tools  Configure System Advisor Properties menu
item. The Device ID must be configured separately for each System Advisor Server. Each System
Advisor Server is primary; therefore the Redundancy Group ID does not apply. See System Advisor
Configuration on page 122 for more details.
Send Feedback 31
MN002731A01-A
The MNIS Data Gateway should be configured with a Device ID from 31 to 35. Each MNIS Data
Gateway requires a unique Device ID. These Device IDs align with the Site ID and the 3rd octet of the IP
address as indicated in Understanding IP Addressing on page 15. Since the MNIS Data Gateway does
not support redundancy, it always has a Redundancy Group ID of Primary. The Device ID and
Redundancy Group ID of the MNIS Data Gateway are configured in the Radio Systems view (antenna
icon) in Radio Management.
The Radio Management Device Programmer should be configured with a Device ID of 21. If a Device
Programmer is configured with a Communication Method of IP Program, then it requires a unique
Device ID. There is usually only one Device Programmer in a system configured with a Communication
Method of IP Program. Multiple Device Programmers can be supported if Radio Management “Groups”
are appropriately deployed. Each Device Programmer with a Communication Method of IP Program
must have a unique Device ID. The Device ID of the Device Programmer is configured in the RM Device
Monitor application. From the RM Device Monitor application click Settings Communication
Method as IP Program and then set the Device ID.
Unique Radio ID of a Sourcing Entity in the System

An entity that acts as a source of a call must have a unique Radio ID. Radios, MNIS Data Gateways,
and Voice Consoles require a unique Radio ID. The range of Radio ID is 1 – 16,776,415.
Each Radio in the system requires a unique Radio ID. The Radio ID of the radio is configurable in the
Radio View (radio icon) within Radio Management. See Radio Identifier Assignments on page 34 for
more details on setting Radio IDs.
Each MNIS Data Gateway in the system requires a unique Radio ID. The MNIS Data gateway acts as
the source of a call on behalf of the data applications using it. The MNIS Data Gateway should be
configured with a Radio ID from 3000031 to 3000035. See Radio Identifier Assignments on page 34 for
more details on setting Radio IDs. Each MNIS Data Gateway requires a unique Device ID. These Radio
IDs align with the Device ID, Site ID and the 3rd octet of the IP address as indicated in Understanding IP
Addressing on page 15. The Radio ID of the MNIS Data Gateway is configured in the MNIS Data
Gateway Configuration Set in Radio Management. Select MNIS object, then MNIS System, then set the
Data Gateway Radio ID.
Each voice console application connected to an MNIS VRC Gateway in the system requires a unique
Radio ID. The voice console application acts as a source of a call. It is recommended that the voice
console be configured with a Radio ID from 4000000 to 4999999. See Radio Identifier Assignments on
page 34 for more details on setting Radio IDs. The Radio ID of the voice console is configured in the
voice console application.
A voice recorder does not act as a source and does not require a radio ID. In the DMR Trunking
protocol, a phone gateway is identified by a fixed gateway identifier called PSTNI.
32 Send Feedback
MN002731A01-A
Summary of Recommended Identifiers

Table 15 summarizes the recommended entity identifiers for each device in the system. It also identifies
where the identifiers are configured.
Table 15: Summary of Entity Identifiers
Send Feedback 33
MN002731A01-A
Radio Identifier Assignments

This section describes way to set the identifiers of radio entities in a Capacity Max system.
DMR Mobile Subscriber IDentifier (MSID) Addressing Range

Each radio in the system, as well as each data gateway and each console position when deployed, is
required to have a unique Radio ID. Capacity Max supports the DMR defined Mobile Subscriber
Identifier (Radio ID) addressing range as defined below.
00000116 – FFFCDF16 (1 – 16,776,415)
Per the DMR specification, all other values in the entire 24-bit field are not valid and are reserved for
future use or used for Gateway or Service identification.
Radio IDs Identification

There are two approaches to identifying Radio IDs:
Option A:
As a general practice, create contiguous ID ranges, but allow room for future expansion. As an example,
a department has a current requirement for 1200 IDs. However, the department may need up to 2000
IDs in 12 months. Assigning the IDs during planning saves future re-programming of radios and
subscriber records.
Option B:
The radio ID can be created so that each ID provides certain information about the radio. Each digit in
the Radio ID can represent a certain code or radio type. For example:
Figure 15: Radio ID as Code or Radio Type Example
16776415
Range 0 - 9999 Sequence

Number
Range 0 - 6
0 - Reserved
1 - Portable
2 - Mobile
3 - Data Gateway
4 - Console Position
5 - Reserved
34 Send Feedback
MN002731A01-A
Alternatively each digit in the Radio ID can represent a certain code that is attribute based. For example:
Figure 16: Radio ID as Attribute Based Code Example
16776415
Range 0 - 9999 Sequence

Number
Range 0 - 6
0 - Reserved
1 - Customer
2 - Function/Role
3 - Rank/Position
4 - Specialty
5 - Reserved
Talkgroup Identifier Assignments

This section explains the acceptable and reserved ranges for talkgroups in Capacity Max, including the
proprietary features that benefit from the short talk group addressing range.
DMR Talk Group IDentifier (TGID) Addressing Range

Capacity Max supports the entire DMR defined Talk Group IDentifier addressing range.
1 – 16,776,415 (00000116 – FFFCDF16)
In addition, Capacity Max supports the DMR defined special talk group identifiers.
Site All Call ID: 16,777,213 (FFFFFD16)
Multi-Site All Call ID: 16,777,214 (FFFFFE16)
Short Talk Group IDentifier (TGID) Addressing Range

Capacity Max supports a smaller Talk Group IDentifier addressing range that reduces the size of
proprietary messaging. The reduced TGID range reduces message latency and improves signaling
efficiency. To take advantage of the improved efficiency, assignment of Talk Group IDentifiers must fall in
the following range.
1 – 1020 (00000116 – 0003FC16)
Send Feedback 35
MN002731A01-A
Operating with only Short TGIDs on a system in either Open Mode or Advantage Mode optimizes
signaling to MSI radios for the following proprietary features.
• Emergency Call Priority Monitor
• Site All Call Priority Monitor
• Multi-Site All Call Priority Monitor
Operating with only Short TGIDs on a system in Advantage Mode optimizes signaling for the following
proprietary feature.
• Improved TG call late entry: Supports two to four times improvement in signaling efficiency
In the future, more features will have optimized signaling in Advantage Mode when only Short TGIDs are
used in a system.
Understanding the Channel Plan

This chapter provides the considerations for designing the mapping between channel frequencies and
the channel number.
DMR Trunking Protocol

The DMR Trunking Protocol uses an identifier to represent a pair of transmit and receive frequencies.
Capacity Max uses the DMR Trunking Protocol for over-the-air communication between radios and the
infrastructure. In some cases, such as granting a service request of a radio, the infrastructure assigns a
channel to the radios.
The DMR Trunking Protocol uses a number to represent a channel. The range of the Channel Number
(also called Channel ID) is from 1 to 4094 (inclusive). A Channel Number is a logical entity and
represents an ordered pair of a physical transmit (with respect to a radio) frequency and a physical
receive (with respect to a radio) frequency. This one-to-one mapping between the Channel Number and
the frequency pair is called a Channel Plan.
Multiple Channel Plans

The infrastructure of a Capacity Max system supports multiple channel plans because the system can
have RF sites of different frequency bands. Each band may require a different channel plan. A gateway
(voice or data) has a site ID, but it is not an RF site and does not require a channel plan.
The channel plans in a radio should be per the following rules:
1 A radio has only one channel plan for a Capacity Max system, which is used by all the personalities
for the system.
2 All the sites in the roaming list of a radio’s personality should have the personality’s channel plan.
3 The rules 1 and 2 imply that all sites listed in roaming lists of a radio’s personalities for a system
should have the same channel plan. This is required because a radio can roam only to the sites
where the frequency pairs of all trunked channels are within the radio’s band.
4 All the channels at a site support the same channel plan, such as a site has only one channel plan.
Table 16 explains these rules with the help of an example:
36 Send Feedback
MN002731A01-A
Radios 1, 2, and 3 are operating on the same system. Radios 1 and 2 can operate in UHF band 1 only
and Radio 3 can operate in UHF band 2 only:
Table 16: Channel Plan Rules
Personalities Sites, where the

Radio of the system radio roams Comment
Radio 1 Personality 1 {Site 2, Site 4, Site 5} Personality 1 is using Channel Plan 1.
Personality 3 {Site 1, Site 4, Site 5} As per rule 1, Personality 3 should also use Channel
Plan 1.
As per rule 3, sites 1, 2, 4, and 5 should use Channel

Plan 1.
Radio 2 Personality 2 {Site 4, Site 6} Since site 4 uses channel plan 1, Personality 2 has
channel plan 1 (rule 2).
Personality 5 {Site 3, Site 7}
As per rule 1, Personality 5 should also use Channel
Plan 1.
As per rule 3, sites 3, 6, and 7 should use Channel Plan

1.
Radio 3 Personality 1 {Site 8, Site 9} The site 8 and 9 should have the same channel plan (say
channel plan 2).
Sites 1, 2, 4, and 5 are a closed set for the purpose of roaming, meaning that all the radios at sites 1, 2,
4, and 5 roam within those sites only. Similarly, sites 8 and 9 form another closed set. If the system adds
another radio (radio 4), which is required to operate at site 1 and 9 then:
• Radio 4 must be capable of operating in both UHF band 1 and 2; and
• Sites 1, 2, 3, 4, 5, 6, 7, 8, and 9 should use the same channel plan, such as the previous two closed
sets have merged to form a single closed set. A closed set of sites has one channel plan.
Fixed and Flexible Channel Plan Mapping

The DMR Trunking Protocol provides two ways to specify the mapping between the Channel Numbers
and the frequency pairs. The two ways are Fixed and Flexible. The Fixed specify the mapping by rules
and the Flexible specify the mapping individually by listing the frequency pair and its channel number.
A Capacity Max system (both radios and repeaters) uses both Flexible and Fixed mapping. A radio can
have Flexible mapping for some Channel Numbers. All other Channel Numbers (except the Channel
Numbers defined by Flexible mapping) are mapped using Fixed mapping. By default, a radio supports a
Fixed mapping.
Fixed Mapping
For Fixed mapping, the following rule is used to map a Channel Number into absolute transmit / receive
frequencies of a radio.
FMS_Tx = Fbase + ((CHAN - MIN_CHAN_Num) x (Fseparation /1000))
FMS_Rx = FMS_Tx + Fduplexsplit
Send Feedback 37
MN002731A01-A
where:
FMS_Tx : absolute transmit frequency of a radio, in MHz
FMS_Rx : absolute receive frequency of a radio, in MHz
CHAN : Channel Number, between 1 to 4094 (inclusive)
MIN_CHAN_Num : Minimum Channel Number is the minimum values of the Channel Number
Fseparation : Channel Separation (or spacing), (12.5 KHz or 25 KHz)
Fduplexsplit : Duplex Split or the difference (positive or negative number) of the receive frequency
from the transmit frequency, (-50MHz to 0 MHz to 50 MHz in 2.5 kHz steps)
Fbase : Base frequency, in MHz
Fixed channel mapping is sufficient for most of the cases, except in the following cases:
• When the difference between the minimum and maximum Tx frequencies is greater than the
Fseperation * 4093. For example, with Channel Separation of 12.5 KHz, the Channel Number from 1
to 4094 can map frequencies within 51.1625 (= 12.5 KHz * 4093) MHz only.
• When the Duplex Split or Channel Separation is not the same for all the frequency pairs.
• When the difference between the base frequency and a transmit frequency is not an integral multiple
of Fseperation.
To overcome this, the Capacity Max allows a user to split the frequencies into a sequence of up to four
segments, where each segment has its own Base Frequency, Number of Channels, Separation, and
Duplex Split. The range of a Channel Number for a segment starts just after the previous segment has
ended. Table 17 lists the segmentation of frequencies.
NOTICE:
(N1+N2+N3+N4) less than or equal to 4094.
Table 17: Segmentation of Frequencies
Channel Number Range Number

(Min Channel to Max of Base Channel Duplex
Segment Channel) Channels Frequency Separation Split
1 1 … (N1) N1 Fbase_1 Fseparation_1 Fduplexsplit_1
2 N1+1 … (N1+N2) N2 Fbase_2 Fseparation_2 Fduplexsplit_2
3 N1+N2+1 … (N1+N2+N3) N3 Fbase_3 Fseparation_3 Fduplexsplit_3
4 N1+N2+N3+1 … (N1+N2+N3+N4) N4 Fbase_4 Fseparation_4 Fduplexsplit_4
Example 1:
Radios support both 800 MHz and 900 MHz bands. The set of sites where these radios roam can have
channels from both the bands. If a set of sites uses channels from both the bands, then all the radios at
those sites must support both the bands.
The radios transmit frequency range for 800 MHz band is 806 MHz to 824 MHz, Channel separation is
12.5 KHz, and duplex split is 45 MHz. The radios transmit frequency range for 900 MHz band is 896
MHz to 901 MHz, Channel separation is 25 KHz, and duplex split is 39 MHz. It is not possible to cover
both the bands with one segment, due to following reasons:
38 Send Feedback
MN002731A01-A
• The difference between the minimum (806 MHz) and maximum (901 MHz) Tx frequencies is 95
MHz, which is greater than the 51.1625 (= 12.5 KHz * 4093) MHz.
• The duplex splits of both the bands are different.
The two bands require their own segment. Table 18 shows a possible channel plan.
Table 18: Possible Channel Plan
Base Channel Duplex

Radios Tx Number Frequency Separation Split
Segment Frequency range of channels (In MHz) (In KHz) (In MHz)
1 (806.0125, 823.9875) N1 = 1440 806 12.5 45
2 (896.0125, 900.9875) N2 = 400 896 12.5 39
Example 2:
The following example shows a channel plan using fixed mapping for a closed set of sites of a Capacity
Max system. The trunked repeaters at the sites use the following transmit and receive frequency pairs
(in MHz):
{451.025, 456.025}, {472.1125, 475.1125}, {454.05, 459.05}, {464.975, 469.975}, {499.3125, 504.3125},
{511.9875, 514.9875}, {451.3125, 456.3125}
The frequency band has the channel separation of 12.5 KHz.
Setting a Channel Plan with Fixed Mapping

The steps needed to obtain a channel plan for the frequency pairs, are as follows:
Procedure:
1 Sort the frequency pairs in increasing order of the transmit frequencies.
{451.025, 456.025}, {451.3125, 456.3125}, {454.05, 459.05}, {464.975, 469.975}, {472.1125,

475.1125}, {499.3125, 504.3125}, {511.9875, 514.9875}.
2 Find the duplex split (such as the difference of the receive frequency from the transmit frequency)
and group the frequency pairs based on their duplex split.
5 MHz group: {451.025, 456.025}, {451.3125, 456.3125}, {454.05, 459.05}, {464.975, 469.975},
3 MHz group: {472.1125, 475.1125}, {499.3125, 504.3125}, {511.9875, 514.9875}

NOTE
NOTICE:
Each group requires at least one segment.
3 Select a Base Frequency and a Channel Number Range for each group.
The criteria for selection of a Base Frequency are as follows:
• It should be less than or equal to the lowest transmit frequency in the group (such as 451.025
MHz for 5MHz group).
• If it is less than the lowest, then the difference between the Base frequency and the lowest
transmit frequency is an integral multiple of the channel separation.
Send Feedback 39
MN002731A01-A
The criteria for selection of a Channel Number Range are as follows:
• It should be greater than or equal to the channel number of the highest transmit frequency in the
group (such as 464.975 MHz for 5MHz group).
• The Channel Number Range and Base Frequency cover the frequency pairs planned for future
expansion of the system.
For the 5 MHz group, let the Base Frequency be 450 MHz. Since this is the first segment, the
Channel Number Range starts with 1.
The Channel Numbers for the frequency pairs in this group are 83 (=1+(451.025- 450)/0.0125), 106
(=1+(451.3125-450)/0.0125), 325 (=1+(454.05-450)/0.0125), and 1199 (=1+(464.975-450)/0.0125).
Since the largest Channel Number is 1199, let the Channel Number Range end at 1200. There are
1200 frequency pairs in this segment.
For the 3 MHz group let the Base Frequency be 470 MHz. The Channel Number Range starts with
1201.
The Channel Numbers for the frequency pairs in this group are 1370 (=1201+(472.1125-470)/
0.0125), 3546 (=1201+(499.3125-470)/0.0125), 4560 (=1201+(511.9875-470)/0.0125). Since 4560
is greater than the max channel number (= 4094), the frequency pair {511.9875, 514.9875} cannot
be mapped into this segment.
Since the largest Channel Number that can fit within this segment is 3546, let the Channel Number
Range end at 3600. There are 2400 frequency pairs in this segment.
NOTE
NOTICE:
The channel numbers for all the frequency pairs must be an integer. If the channel number for
a frequency pair is a real number, then a segment is required for the frequency pair.
4 Create a new segment for the frequency pairs that do not fit into the previous segment.
Let the Base Frequency be 511 MHz. The Channel Number Range starts with 3601.
The Channel Number for the frequency pair in this group is 3680 (=3601+(511.9875-511)/0.0125).
The Channel Number Range ends at 4094. There are 494 frequency pairs in this segment.
40 Send Feedback
MN002731A01-A
Table 19 is a summary of the Channel Plan:
Table 19: Channel Plan Summary
Duplex
Number Base Channel Split
Tx of Frequency Separation (In
Segment Frequencies Channels (In MHz) (In KHz) MHz) Comments
1 451.025, N1 = 1200 450 12.5 5 This segment covers

451.3125, all frequencies from
454.05, 450 to 464.9875
464.975 MHz.The Channel
Numbers for the
given frequencies
are 83, 106, 325,
and 1199.
2 472.1125, N2 = 2400 470 12.5 3 Since the Duplex

499.3125, Split changes at 470
MHz a new segment
is required. This
segment covers all
frequencies from
470 to 499.9875
MHz. The Channel
Numbers for the
given frequencies
are 1370, and 3546.
3 511.9875 N3 = 494 511 12.5 3 This frequency is

outside the range of
the second segment
with N2 = 2894 (=
4094-1200) and
therefore requires a
new segment. This
segment covers all
frequencies from 511
to 517.175 MHz. The
Channel Number for
the given frequency
is 3680.
Send Feedback 41
MN002731A01-A
NOTICE:
The mapping need not cover all the frequency pairs of a band. For example, the mapping in
Table 19 on page 41 does not represent the frequencies between 500 and 511 MHz.
The frequency range covered by segments may overlap. For example, the channel plan for the
following frequency pairs are shown in Table 20: {451.025, 456.025}, {451.3125, 456.3125},
{451.31875, 456.31875}, {454.05, 459.05}, {464.975, 469.975}, {454.06875, 459.06875}
Table 20: Overlapping Frequency Range by Segments
Channel Duplex
Number Base Separati Split
Tx of Frequency on (In
Segment Frequencies Channels (In MHz) (In KHz) MHz) Comments
1 451.025, N1 = 1200 450 12.5 5 This segment covers

451.3125, all frequencies from
454.05, 450 to 464.9875 MHz.
464.975 The Channel Numbers
for the given
frequencies are 83,
106, 325, and 1199.
2 451.31875, N2 = 2894 450.00625 12.5 5 Since the channel

454.06875 numbers for these
frequency pairs in the
first segment are
105.5 and 325.5, a
new segment is
required. This
segment covers all
frequencies from
450.00625 to
486.16875 MHz. The
Channel Numbers for
the given frequencies
are 1306, and 1526.
Flexible Mapping
In the following cases, the fixed mapping cannot map all the frequency pairs to channel numbers.
• The mapping requires more than four segments. The fixed mapping requires a segment for every
combination of Channel Separation and Duplex Split.
• One or more frequency pairs are beyond the range of frequency pairs covered by all the four
segments.
• One or more frequency pairs are within the range of segments but cannot be mapped by them.
To overcome the limitations of fixed mapping, a Capacity Max system allows flexible mapping. It should
be used to map all the frequency pairs that are exception cases of the fixed mapping. The flexible
mapping does not have rules. All the frequency pairs are individually specified with corresponding
channel numbers.
Any Channel Number in the fixed mapping, which is least likely to be used by a frequency pair, should
be used for the Flexible Channel plan. In the first example, the frequencies from 455 MHz to 460 MHz
(corresponding to channel numbers 400 to 799) are not used as transmit frequency because those
frequencies are the ‘Receive’ frequencies of the 450 MHz to 455 MHz.
42 Send Feedback
MN002731A01-A
The fixed mapping is the preferred way to map frequency pairs to a channel number. It supports future
expansion of a system better than flexible mapping. It is likely that the frequency pair of the newly added
trunked repeater at a site is covered by the fixed mapping. In that case the addition of a trunked repeater
at a site does not require reprogramming of the radios.
Send Feedback 43
MN002731A01-A
44 Send Feedback
MN002731A01-A
Network Configuration
Chapter 3
Network Configuration 3
Configuring a Capacity Max System Transport Network

There are numerous different strategies to follow when configuring a Capacity Max IP Network sub-
system. Although there are many possible ways to configure routers and Ethernet switches for a
Capacity Max system, this section details the configurations that Motorola used in various test labs for a
Capacity Max system testing.
As a pre-requisite to configuring the IP Network for a Capacity Max system, it is assumed that:
1 The “system planning” phase has already been completed.
a The IP Plan for the Capacity Max System has been determined
b A network “topology” diagram is available
1) A network topology diagram including aspects, such as:
- Routers, switches, and modems able or ADSL)
- Links (with link type (fiber, copper, microwave, and others.) and type (point-to-point, point-
to-multipoint, public internet cloud, and others.)
- Physical locations
c The Wide Area Network (WAN) IP plan. Are the sites connected via Dynamic Host Configuration
Protocol or a Static IP addresses?
1) Configuration Documents are other sections are written assuming the WAN connectivity is via
an Ethernet Interface that is set to AUTO Negotiation for the WAN.
d The hosts have been determined the connections to each port on each Ethernet Switch at every
site.
2 The network toolkit has been acquired
a A Laptop computer running Windows with a serial/USB to serial adapter and Ethernet interface
b Serial cables to connect the laptop computer to the router and Ethernet switch
c Windows Software (Required vs. optional) and used by
1) Terminal program such as TeraTerm (required)
2) Telnet/SSH program such as Putty (optional)
3) TFTP program such as Solarwinds TFTP server (required)
4) Packet capture tool such as Wireshark (optional)
5) Text comparison tool such as Beyond Compare or Winmerge (optional)
Send Feedback 45
MN002731A01-A
Chapter 3: Network Configuration
d Minimum of Cat 5 or Cat 5e (for Gigabit Ethernet Links) Ethernet cables for configuration and test
of the network.
e Common software version for the vendor’s routers and Ethernet Switches. It is not uncommon to
have products arrive with different software versions and as part of the IP Network configuration
a common version should be used on all routers and all Ethernet Switches. Software is available
from the respective vendor websites (Accounts may be required for access)
Motorola used the following versions for the network products tested:
1) HP MSR Version HP Comware Software, Version 7.1.059, Release 0305
2) HP 2530 Version YB.15.17.0007
3) Cisco 2911 Version 15.4 (3) M3
4) Cisco 3650 Version 03.03.05SE
NOTICE:
If these versions are no longer available at the vendor's web site, a newer version in the
same family of software can be used, such as the last digits after the decimal point should
be greater than what is in the listing. For example, if the vendor website has YB.15.17.0012
available, it can be used since YB.15.17.0007 is listed for the HP 2530.
Configuring the IP Network

The IP Network is configured depending on the number of sites, number of hosts, and complexity of the
configurations. The following prerequisites must be considered before performing the IP network
configuration.
Prerequisites:
• Approximately one day of planning should be allocated.
A small two- or three-site system may take a half day, while a system larger than five sites may
require a day.
• One day to load the correct software, develop the configurations, and load the configurations.
• Pre-stage all the network equipment in one location before deploying at each site. Plan on one to
two hours for the first device to load the operating systems and configurations. Once the first unit
is configured, subsequent routers or Ethernet switches probably require 15 minutes each to
configure.
• If significant changes are being made to the router or Ethernet Switch configurations, they may
require an hour each to modify the configurations.
• Several hours per site to test the IP network configurations.
46 Send Feedback
MN002731A01-A
Perform this high-level procedure to configure the IP Network.
Procedure:
1 Develop a diagram of the Capacity Max system to be configured or obtain the diagram if it has
already been created. Figure 17 is an example of a two-site Capacity Max system.
Figure 17: Two-Site Capacity Max System Reference Diagram
2 Understand the Network Equipment to be used. The preferred network equipment for the Capacity
Max solution is the:
• Hewlett Packard Enterprise MSR 2003 Router (JG411A)
• Optional 4 Port Switch Module (JD573B)
• Hewlett Packard Enterprise 2530 24 Port Ethernet Switch (J9782A)
The MSR 2003 router is multiport WAN router used to route traffic between the various networks at a
site and in the case of a multiple site system, Wide Area Network (WAN) connectivity to the various
sites. See the Hewlett Packard Enterprise product information for this router: http://www8.hp.com/
lamerica_nsc_carib/en/products/networking-routers/product-detail.html?oid=5408900.
Figure 18: HP Enterprise MSR 2003 Router
If a site design requires multiple Ethernet switches (not shown in Figure 17), then an optional 4-port
switch module is installed in the rear of the MSR 2003 router.
Send Feedback 47
MN002731A01-A
Figure 19: Rear View of MSR 2003 with 4-Port Switch Module Installed
3 2 1
DO NOT INSTALL DO NOT INSTALL DO NOT INSTALL

ANY MODULE ANY MODULE ANY MODULE
WITH WITH WITH
POWER ON POWER ON POWER ON
0 1 2 3 P 4FSW
NOTE
NOTICE:
The module will not be detected by the MSR 2003 if installed in slot 1.
The Hewlett Packard Enterprise 2530 Ethernet Switch is a managed Ethernet switch with 24 ports of
10/100, 2 ports of 10/100/1000 and 2 SFP ports. The 24 ports of 10/100 are used to connect the
Capacity Max devices to the network. At the time this document was created this was a working link
to Hewlett Packard Enterprise product information for this Ethernet Switch: http://www8.hp.com/us/
en/products/networking-switches/product-detail.html?oid=5385008.
Figure 20: Hewlett Packard Enterprise 2530 Ethernet Switch

HP 2530-24 10/100Base-TX Ports (1 - 24) All RJ-45 Ports (1 - 26) are Auto-MDIX
Switch
Link 1 Mode 3 5 7 9 11 Link 13 Mode 15 17 19 21 23
J9782A
Power 10/100/1000Base-T Ports (25 - 26) SFP Ports (27 - 28)
Fault Link 25 Mode 26

Locator
* Spd Mode:
Off = 10 Mbps, 27 28
Act Link Link
Status LED Flash = 100 Mbps,
Mode
Fan FDx On = 1000+ Mbps
Test * Spd
Console
Mode Mode
Reset Clear Link 2 Mode 4 6 8 10 12 Link 14 Mode 16 18 20 22 24
Console Use only supported transceivers
If network equipment other than the preferred Hewlett Packard Enterprise equipment is used,
Motorola Solutions recommends that the article “Network Components for IP Connectivity” be
reviewed.
3 Review and understand the network equipment configuration aspects. In general, the typically
configured parameters used in network transport device configurations for routers and switches are:
Table 21: Typical Configured Parameters for Routers and Switches
Configuration
Aspect Description
hostname A user defined variable to provide a friendly name to the device, this is very helpful when
remotely accessing the device to confirm that the user is connected to the correct device.
monitor A configuration aspect to monitor traffic on the Local Area Network (LAN) to an Ethernet
switch port so that a laptop can be connected to this port to capture the Ethernet traffic with a
or software package such as Wireshark. The default configuration is to send traffic from all host
ports to the mirror/span port. This can potentially cause the mirror port to drop packet copies
monitor session on busy systems, but should otherwise not interfere with normal system operation.
banner motd Sets a banner message of the day, an optional security feature to provide the system owner a
means to warn a user about appropriate access to the device
or
header motd
port-security An optional feature to improve the security of the switch by defining the valid number of Media
Access Control (MAC) addresses on a port. Most host ports should only have 1 MAC address
and if more than one MAC address is detected a trap to the System Advisor is sent.
48 Send Feedback
MN002731A01-A
Table 21: Typical Configured Parameters for Routers and Switches (Cont.)
Configuration
Aspect Description
timesync sntp Configures the device to use a Simple Network Time Protocol (SNTP) client, or Network Time
Protocol (NTP) client to set the date and time on the device usually to Coordinated Universal
or Time (UTC). As an example this series of commands on the Hewlett Packard Enterprise
switch enable this functionality
ntp server
timesync sntp (enables SNTP client)
or
sntp unicast (sets SNTP client as unicast)
ntp-service
unicast-server sntp 60 (polls the time server every 60 seconds)
or sntp server priority 1 172.30.16.1 (IP address of time server, in the example configurations
that Motorola Solutions is providing, router 1 is the time server, and the loopback address is
clock protocol used)
ntp
ip authorized- An optional configuration parameter to restrict the IP range that the Ethernet switch will
managers accept for management connections. These example commands for an Hewlett Packard
Enterprise Ethernet switch restrict access to hosts that are on the Radio Infrastructure or
Gateway Networks
ip authorized-managers 172.16.0.0 255.255.0.0 access manager
ip default- Is a mandatory configuration parameter to set the IP address that the switch will forward
gateway management traffic to:
ip default-gateway 172.16.1.20 will send the management traffic to the router. The IP address
is unique at each site
no ip ssh cipher Is an optional configuration parameter to remove SSH/SCP ciphers that have been
documented as less secure. These commands from an Hewlett Packard Enterprise Ethernet
switch:
no ip ssh cipher 3des-cbc
no ip ssh cipher rijndael-cbc@lysator.liu.se
remove these two ciphers from the offer list of ciphers
no ip ssh mac Is an optional configuration parameter to remove SSH/SCP message authentication codes
(macs) that have been documented as less secure. These commands from an Hewlett
Packard Enterprise Ethernet switch:
no ip ssh mac hmac-md5
no ip ssh mac hmac-md5-96
remove these macs as options
Interface Mandatory commands to configure the interfaces. Each physical interface on an Ethernet
switch or router that will have a host connected to it needs to be configured. Interfaces may
Or also be logical and refer to loopback addresses, VLANS or tunnels
interface
GigabitEthernet
VLAN Virtual Local Area Networks (VLANs) VLANs are used extensively in the configuration
examples. The following table documents the structure that Motorola defined for the example
Capacity MAX configurations.
Send Feedback 49
MN002731A01-A
Table 22: VLANs Configuration Examples
VLAN
Number VLAN Name Function
1 Default_VLAN Unused in accordance with industry standard practice
9 Unused Assign Ethernet Switch Ports to VLAN 9 that are not in

use
10-19 Radio Infrastructure Networks Support for up to 10 Radio Infrastructure Networks at a

site. VLAN 10 would be for first Radio Infrastructure
Network (Radio), VLAN 11 would be the second.
20-29 Gateway Infrastructure Network Support for up to 10 Gateway Infrastructure Networks at

a site. VLAN 20 would be for first Gateway Infrastructure
Network (Gateway1), VLAN 21 would be the second
(Gateway2).
30-39 Application Network Support for up to 10 Application Networks at a site.

VLAN 30 would be for first Application Network
(Application)
40 Mirror Port This is a best practice to put a mirror port on a separate

VLAN as it prevents some issues with duplicate packets
Table 23: VLAN Commands
VLAN These commands from an Hewlett Packard Enterprise Ethernet switch configure VLAN 10 on
ports 1-12 and 23 on a recommended switch configuration with router connected to port 25:
vlan 10
name "Radio" – friendly name for the VLAN
untagged 1-12,23 – untagged is always used for connection to hosts
tagged 25 – tagged is used for router connections
ip address 172.16.1.16 255.255.255.0 – since this switch is managed from the Radio
Infrastructure Network the IP address is assigned on this VLAN
Exit – exits from the vlan 10 configuration
This command from an Hewlett Packard Enterprise would configure VLAN ID 10 on the
router:
vlan-type dot1q vid 10
This matches the Hewlett Packard Enterprise Ethernet Switch which uses VLAN 10 for the
Radio Infrastructure Network VLAN.
Physical Ports The example Ethernet Switches and Router Interfaces are configured as AUTO for Speed and
Duplex, this allows for hosts and Ethernet switch to negotiate speed and duplex to simplify
configuration.
Motorola Solutions has developed a default switch configuration template for both a Hewlett Packard
Enterprise 2530 Ethernet Switch and a Cisco 3650 Ethernet Switch to help with the initial Ethernet
Switch layout for hosts. This default Ethernet Switch layout allocate ports to:
50 Send Feedback
MN002731A01-A
• Five VLANs/Networks
a VLAN 10 – Radio Infrastructure Network, Ports 1-12 and 23
b VLAN 20 – Gateway Network (for CMSS), Ports 18-21
c VLAN 21 – Gateway Network, (for MNIS Data Gateway) Port 22
d VLAN 30 – Application Network, Ports 13-17
e VLAN 40 – Monitor, Port 24
f VLANs 10, 20, 21, and 30 – Router on Port 25
g Port 26 is not used when a single switch is deployed at a site
Figure 21: Default Hewlett Packard Enterprise 2530 Ethernet Switch Layout
Send Feedback 51
MN002731A01-A
The default Ethernet Switch layout for Cisco is in Figure 22 on page 52 which allocates ports to:
• Five VLANs/Networks
a VLAN 10 – Radio Infrastructure Network, Ports 1-10 and 21
b VLAN 20 – Gateway Network , (For CMSS) Ports 16-19
c VLAN 21 – Gateway Network, (for MNIS Data Gateway) Port 20
d VLAN 30 – Application Network, Ports 11-15
e VLAN 40 – Monitor, Port 22
f VLANs 10, 20, 21, and 30 – Router on Port 23
g Port 24 is not used when a single switch is deployed at a site
Figure 22: Default Cisco 3650 Ethernet Switch Layout
52 Send Feedback
MN002731A01-A
Table 24: Additional Commands
SNMP SNMP is used for exchanging management information between the network device and the
System Advisor.
no tftp client Optional commands to remove the trivial file transfer protocol (tftp) service. Secure Copy SCP
is used as an option to transfer files to and from the network device
or
no tftp server
ospf Routing protocol Open Shortest Path First (OSPF) that is used to provide connectivity
information for the network routers to determine the appropriate path for the IP traffic. OSPF
area 0.0.0.0 is used in the example configurations
silent-interface Prevents interface from sending OSPF Hello packets, which prevents neighbor adjacencies
network Every site requires networks to be defined in the routers. An Example of networks configured
at a Site from a Hewlett Packard Enterprise MSR 2003 Router looks like
network 172.16.1.0 0.0.0.255 – Radio Infrastructure Network per the IP plan
network 172.20.36.0 0.0.0.127 – Gateway Network per the IP plan
network 172.20.1.128 0.0.0.127 – Application Network per the IP plan
network 172.20.31.0 0.0.0.127 – Gateway Network per the IP plan
network 172.30.0.0 0.0.15.255 – Network for tunnel end points per the IP plan
network 172.30.16.1 0.0.0.0 – Network for Router Loopbacks per the IP plan
GRE Generic Routing Encapsulation (GRE) is a tunneling protocol that encapsulates the IP traffic
between sites
dhcp Dynamic host configuration protocol (DHCP) used to assign IP addresses to select hosts at
sites.
ACL or packet Access control lists (ACLs) are used to restrict traffic that traverses the router.
filters
Table 25: IP Packet Source and Destination
Destination
Radio Gateway -
Infrastructure Gateway - TC Others Application
Radio Allowed Allowed Allowed Blocked (note 1)

Infrastructure
Source
Gateway - TC Allowed Allowed Allowed Allowed
Gateway - Allowed Allowed Allnowed (note 2) Allowed

Others
Application Blocked Blocked (note 3) Allowed Allowed (note 4)
Send Feedback 53
MN002731A01-A
Table Notes:
1. Exception: UDP Source Ports 65008 (Rptr Slot 1), 65009 (Rptr Slot 2) can send IP packets from the Radio
Network to the Application Network for ATIA traffic.
2. IP Packets may be exchanged between any Gateway subnert; however, it may be desirable to block traffic
between different Application Sites. In the case of a multiple customer system ACLS between Gateway networks at
customer sites should be applied.
3. Exception: The application Network CAN send/receive packets to/from the TC’s Presense Service (UDP and
TCP ports 65015).
4. IP Packets may be exchanged between any External subnert; however, it may be desirable to block traffic
between different Application Sites. In the case of a multiple customer system ACLS between Application networks
at customer sites should be applied.
Table 26: Definitions
loopback A loopback address is a common implementation to define a single management IP address

for a device. In this case the Hewlett Packard Enterprise MSR 2003 Router uses a loopback
address
interface LoopBack0
ip address 172.30.16.1 255.255.255.255
These commands define the loopback address on the 172.30.16.1/32 network
WAN IP Every Site that is connected to a Wide Area Network (WAN) will require one of the router
interfaces to be configured to connect to the WAN. In the case of dynamic tunnel protocols
discussed below at least the ADVPN hub site or the DMVPN hub site must have a static IP
address so the other sites can connect to the hub. It is also recommended that if the system
has multiple sites a second site also be configured as a backup hub site with a static IP
address. All other sites can have DHCP addresses on the WAN interface.
54 Send Feedback
MN002731A01-A
Table 26: Definitions (Cont.)
NAT Network Address Translation – Network Address Port Translation is an optional configuration
in Capacity Max systems to support connections to and from External Networks. In the
Or example configurations that MSI provides the NAT configurations are for:
NAPT System Advisor:

9090 TCP HTTPS
36002 TCP TLS
35003 TCP NMS FE
50111 TCP REST
51919 TCP REST
Battery Management Server:

TCP 58041
The example implementations use the Static WAN IP address or the alias for that port to
define a port translation to and from the inside host address.
Battery Management (on MNIS Data GW assuming the data gateway is on the 172.20.31.0/
25network):
public_IP:58041 maps to 172.20.31.24:58041
System Advisor assuming the system advisor is on the 172.20.36.0/25 network):

public_IP:9090 maps to 172.20.36.5:9090
public_IP:36002 maps to 172.20.36.5:36002
public_IP:35003 maps to 172.20.36.5:35003
public_IP:50111 maps to 172.20.36.5:50111
public_IP:51919 maps to 172.20.36.5:51919
NAT exposes these ports to a port scanner if the router is connected to the Internet. The site
NAT implementation should be carefully reviewed and only enable the minimum connections
required.
Inside to outside NAT is also enabled on the Application and Gateway subnets.
NAT implementations can fail if the WAN IP address is changed without updating the router
configuration when the WAN IP address is changed.
Stateful firewall A function in the routers to keep state (track) of connections such as TCP streams
aspf policy 1 Optional command on Hewlett Packard Enterprise MSR router to enable stateful firewall
inspection of TCP connections inbound into the MSR router.
tcp syn-check
ADVPN Auto Discovery Virtual Private Networks (ADVPN) or Dynamic MultiPoint Virtual Private
Networks (DMVPN) are dynamic overlay networks protocols that also provide a simplified
Or routing configuration for the enablement of tunnels. These two techniques allow the network to
be configured with a hub or hubs and spokes. In the example configurations, if two or more
DMVPN sites exists two sites are configured as hubs (requiring static IP addresses) and the remaining
sites as spokes that only require dynamic IP addresses on the WAN.
Send Feedback 55
MN002731A01-A
Table 26: Definitions (Cont.)
IPSEC An optional configuration aspect to secure the GRE tunnels. Internet Protocol Security
(IPSEC) is a protocol suite to authenticate and encrypt IP traffic in a communication session.
Export requirements can limit the ciphers and macs available in network products. The
configuration examples provided may not have used the strongest encryption options. In the
case of the Hewlett Packard Enterprise routers the routers ship with encryption limits. These
limits can be removed if the final country of use is allowed to have high encryption. Follow the
Hewlett Packard Enterprise FAQ at:
http://www8.hp.com/h20195/v2/GetPDF.aspx%2F4AA4-8338ENW.pdf
HP MSR2000/3000/4000 Router Series Encryption Upgrade
VAM Server Part of the ADVPN solution on Hewlett Packard Enterprise MSR routers the VPN Address
Manager (VAM) maintains the database of all routers in the network using the ADVPN
protocol. The VAM server is enabled in the configuration examples at the hub sites.
Figure 23 illustrates the tunnels between Site 1-2 and Site 1-3 as the permanent tunnels and Site 2-
3 as the dynamic tunnel that is initiated on demand when traffic needs to flow from Site 2 to Site 3.
This is based on the configuration of Site 1 Router as the primary VAM server. The VAM server
(located on the MSR Router in Site 1) is using OSPF to inform Site 2 and Site 3 with the IP
addresses of every site. If the dynamic tunnel is down, because the tunnel timed out when traffic is
present at Site 2 that needs to terminate at Site 3, the traffic actually flows through Site 1 (Site 2-1,
then Site 1-3) and then transition to the dynamic tunnel (Site 2-3). The traffic transitions after a
couple of packets to the Site 2-3 dynamic tunnel.
Figure 23: ADVPN Dynamic Tunnel Example

y VAM Server
work
OKE6WPPGN
The example configurations for the routers provided do not require any bandwidth information for
configuration as the routers will clock packets at the port speed of the interface.
When a Capacity Max Site has the need for more than one Switch a diagram would look like
Figure 24 on page 57.
56 Send Feedback
MN002731A01-A
Figure 24: Two HP 2530 Ethernet Switches at a Site
The additional protocols/features/functions implemented in Ethernet Switch Configurations when two

Hewlett Packard Enterprise 2530 switches are at a site include:
• “spanning-tree” – as depicted in Figure 24 where there is a switching loop. To prevent the loop
condition, a port needs to be blocked. To enable this functionality spanning tree, a rapid spanning
tree is enabled. This protocol is designed to prevent the loop condition from occurring by
determining the topology and then blocking a port to prevent the loop.
• “spanning-tree force-version rstp-operation” – the switch module in the Hewlett Packard

Enterprise MSR 2003 Router is configured as the root bridge and the port being blocked is port
26 between Switch 1 and Switch 2.
• Ethernet Switch Port layout is now different as the repeaters are distributed between the two
switches. The Interfaces on the Ethernet Switches might look like the following table:
Table 27: Three Ethernet Switch Configuration
Switch 1 Switch 2 Switch 3

Hewlett Packard Hewlett Packard (4-Port Switch Option
Port Enterprise 2530 Enterprise 2530 Module in MSR 2003)
0 NA NA Switch 1 Port 26
1 Repeater_01 VLAN 10 Open VLAN 9 Switch 2 Port 26
2 Open VLAN 9 Repeater_02 VLAN 10 NA
Send Feedback 57
MN002731A01-A
Table 27: Three Ethernet Switch Configuration (Cont.)

3 Repeater_03 VLAN 10 Open VLAN 9 NA
13 External Equip VLAN 30 External Equip VLAN 30 NA
18 CMSS-R&TC VLAN 20 CMSS-R&TC VLAN 22 NA
19 CMSS-Voice-GW VLAN CMSS-Voice-GW VLAN NA

20 22
20 CMSS-System- CMSS-System- NA
Advisor&ESU VLAN 20 Advisor&ESU VLAN 22
21 CMSS-iLO VLAN 20 CMSS-iLO VLAN 22 NA
22 Data-Gateway VLAN 21 Data-Gateway VLAN 23 NA
23 Technician-Port VLAN 10 Technician-Port VLAN 10 NA
24 Mirror VLAN 40 Mirror VLAN 40 NA
25 Router_01 VLAN 10, Router_01 VLAN 10, NA

20,21,22,23, 30 20,21,22,23, 30
58 Send Feedback
MN002731A01-A
Table 27: Three Ethernet Switch Configuration (Cont.)

26 Switch_02 VLAN 10, Switch_01 VLAN 10, NA

20,21,22,23, 30 20,21,22,23, 30
Repeater_05 – Application network Gateway Network 3 Gateway Network 4

Repeater_12 VLAN VLAN 30. Even though VLAN 22 is configured in VLAN 23 is configured
10 the diagram shows only the example in the example
1 client computer on the configurations, however configurations,
Even though the site Application network the the diagram does not however the diagram
has only 4 channels default configuration show a redundant CMSS, does not show a Data
the default allocates 5 ports per so these ports can be left Gateway, so this port
configuration switch. The user can as default or moved to can be left as default or
allocates 12 either accept defaults or the Open VLAN 9 moved to the Open
channels. The user configure unused ports VLAN 9
can either accept to Open VLAN 9
defaults or configure
unused ports to the
Open VLAN 9
4 Determine the configurations for the network equipment. Review the example configurations that
MSI provides on Motorola Online and in other documentation to determine which configurations are
the closest to the system to be configured. Use the example configurations that most closely match
the system configuration, load the configurations and then edit the configurations from the command
line interface. If the system is using the recommended Hewlett Packard Enterprise equipment,
additional documentation is available that provides procedures on how to:
• Load operating systems on the HP Enterprise Routers and Ethernet Switches
• Load and save configurations of the HP Enterprise Routers and Ethernet Switches
• Change Ethernet Switch port configurations of the HP Enterprise Ethernet Switches
• Configure credentials of the HP Enterprise Routers and Ethernet Switches
5 Power on the network equipment. Power on the network equipment and confirm it is operation by
logging into the console port of the device as shown in Figure 25 on page 60. Most network
equipment has online manuals that can be searched for to understand how to connect to the device
and use the command line interface.
6 Verify and Update Operating Systems. Using the CLI type the appropriate command(s) to determine
the operating system version. If the system is using the recommended network equipment and the
operating system version is different than what Motorola tested with it, use the procedures to change
the version to the same version that Motorola Solutions tested with. Figure 25 on page 60 shows the
typical connectivity for how to load a new version of an operating system on a new device.
Send Feedback 59
MN002731A01-A
Figure 25: Typical Laptop Connections to Load Operating System
See Loading The OS on a HP MSR2003 Router Using TFTP on page 62 and Loading The OS on an
HP 2530 Switch Using TFTP on page 65 for more details on loading OS on the HP router and switch.
7 Load configurations on the network devices. If the system is using the recommended network
equipment load the configuration file on the network device that most closely resembles the system
configuration. Use the procedures provided to load the configuration.
Once the configuration file has been loaded, use the Command Line Interface (CLI) to edit the
running configuration of the device to modify the necessary parameters.
Helpful Hewlett Packard Enterprise Ethernet Switch CLI commands are:
• show
• configure
• write memory
Helpful Hewlett Packard Enterprise MSR commands are:
• Display
• Command for entering configuration mode for routers:
<Site1Router1>system-view
System View: return to User View with Ctrl+Z.
[Site1Router1]
NOTICE:
Notice the change of the prompt.
See Loading The Configuration on an HP MSR2003 Router Using TFTP on page 66 and Loading
The Configuration on an HP 2530 Switch Using TFTP on page 68” for more details on loading
Configuration on the HP router and switch.
See User Credentials in Transport Network Configuration on page 69 and Pre-shared Keys in
Transport Network Configuration on page 72 for additional procedures for configuring user accounts,
passwords, and pre-shared keys.
60 Send Feedback
MN002731A01-A
8 Test the network. Test the network to confirm it is operational. Every tunnel should be established
and able to pass traffic. One of the most basic ways to test is to use a laptop plugged into a switch
port and ping every host at the site and every network in the system. In Figure 26 on page 62, the
laptop at Site 1 would:
a Ping all the repeaters plugged into Switch 1 on the 172.16.1.0/24 network. Repeater 1 would be
172.16.1.24, repeater 2 would be 172.16.1.27 and continue until all repeaters are pinged.
b Ping the Site 1 router at 172.16.1.20.
c Ping the Site 2 router interfaces on the various networks that the ACLs allow.
- 172.16.2.20
- 172.20.32.20
- 172.20.35.20
- 172.20.37.20
- 172.20.40.20
d Ping hosts on Site 2 Switch 1 or Switch 2. Assuming Site 2 has two CMSSs, then ping:
- 172.20.37.1
- 172.20.40.1
Send Feedback 61
MN002731A01-A
Figure 26: Test the Network
9 Save the network configurations. After testing the transport network, the network device
configurations should be saved to an alternate location. If the system is using the recommended
network equipment load use the procedures to save the configurations to a laptop computer. It is
also recommended to store the configurations on a different computer, memory stick or CD.
Loading The OS on a HP MSR2003 Router Using TFTP

Prerequisites: Obtain the following:
• The OS file for HP MSR2003 router
• A PC with terminal emulation software like Teraterm
• A console cable for out of band access or network connectivity to the switch
• Ethernet cable
Procedure:
1 Put the router OS file on a local directory in the PC.
2 Configure the TFTP server on the PC to point to the directory where the router OS file is located.
3 Access the router command line interface using the console cable and terminal emulation software
like Teraterm.
Common settings for terminal emulators:
Bits per sec : 9600

Data bits : 8
62 Send Feedback
MN002731A01-A
Parity : none
Stop bits : 1
Flow control : none
4 If the router is new, configure an IP address on one of the Ethernet interfaces using the following
commands:
a Enter the configuration mode of the router using system-view command.
b Enter the interface configuration mode using interface <interface name> command.
c Configure the IP address on this interface using ip address <IP address> <mask> command.
Example: This process is summarized in the following example:
[Site4Router1]
[Site4Router1]interface GigabitEthernet 0/0
[Site4Router1-GigabitEthernet0/0]
[Site4Router1-GigabitEthernet0/0]ip address 192.168.3.1 255.255.255.0
[Site4Router1-GigabitEthernet0/0]exit
[Site4Router1]
5 If the router is already deployed in the system with a configuration, use the display ip interface
brief command to find the IP address of the Ethernet interface you wish to use for loading the OS.
6 Configure the PC with an IP address in the same subnet as the router and connect the Ethernet
cable from PC to the router to establish IP connectivity.
7 Check if the router has enough flash storage available using the command dir from the user view.
Example: Highlighted portion in the output shows the free flash storage available
<Site1Router1>dir
Directory of flash:
0 -rw- 67667968 Sep 09 2015 06:23:07 MSR2000-CMW710-R0304P02.IPE
1 drw- - Aug 11 2015 00:33:51 diagfile
2 -rw- 735 Sep 25 2015 06:04:32 hostkey
3 -rw- 305 Nov 07 2015 06:26:24 ifindex.dat
4 drw- - May 19 2015 20:36:53 license
5 drw- - Aug 12 2015 02:25:14 logfile
6 -rw- 7221248 May 19 2015 20:36:00 msr2000-cmw710-boot-
r0106p04.bin
7 -rw- 6372352 Sep 09 2015 06:23:30 msr2000-cmw710-boot-
r0304p02.bin
8 -rw- 1945600 May 19 2015 20:36:22 msr2000-cmw710-data-
r0106p04.bin
9 -rw- 2729984 Sep 09 2015 06:23:59 msr2000-cmw710-data-
r0304p02.bin
10 -rw- 332800 May 19 2015 20:36:20 msr2000-cmw710-security-
r0106p04.bn
11 -rw- 349184 Sep 09 2015 06:23:57 msr2000-cmw710-security-
r0304p02.bn
12 -rw- 49044480 May 19 2015 20:36:19 msr2000-cmw710-system-
r0106p04.bin
13 -rw- 56514560 Sep 09 2015 06:23:56 msr2000-cmw710-system-
r0304p02.bin
Send Feedback 63
MN002731A01-A
14 -rw- 1404928 May 19 2015 20:36:20 msr2000-cmw710-voice-

r0106p04.bin
15 -rw- 1693696 Sep 09 2015 06:23:58 msr2000-cmw710-voice-
r0304p02.bin
16 drw- - Aug 11 2015 00:33:51 seclog
17 -rw- 591 Sep 25 2015 06:04:32 serverkey
18 -rw- 9919 Nov 07 2015 06:26:24 startup.cfg
19 -rw- 100325 Nov 07 2015 06:26:24 startup.mdb
262144 KB total (69288 KB free)
<Site1Router1>
8 [Optional] If there is not enough flash storage or if you want to delete unwanted files, delete the
existing software images or the unwanted files using the delete flash:/<file name> command from
the user view. The router will prompt for a confirmation. Answer Y at the prompt.
Example: Showing how to delete an older image file from the flash
<Site1Router1>delete flash:/msr2000-cmw710-boot-r0106p04.bin
Delete flash:/msr2000-cmw710-boot-r0106p04.bin? [Y/N]:y
Deleting file flash:/msr2000-cmw710-boot-r0106p04.bin... Done.
<Site1Router1>
9 [Optional] Sometimes the available space might not increase after deleting unwanted files from the
flash. This is because the files are being sent into a recycle bin (similar to the concept of windows).
Since the available space shown in the output of dir command is the entire storage on the router,
you need to empty the recycle bin to make the space for new files in the flash. Delete the files in the
recycle bin permanently using the following command:
reset recycle-bin
Answer y to the router prompts to delete the files.
10 Copy the OS file into the router’s flash storage directory using the following command:
tftp <IP address of the TFTP server> get <OS file name with .IPE extension>
11 Specify the newly loaded software package as the primary startup software images at the next
reboot using the following command:
boot-loader file flash:/< OS file name with .IPE extension> main
The router returns the following prompt:
This command will set the main startup software images. Continue? [Y/N]:
Answer Y at the prompt.
Example: The following example illustrates the process router goes through after configuring the
newly loaded software package as primary.
<Site4Router1>boot-loader file flash:/MSR2000-CMW710-R0304P02.IPE ?

backup Specify the packages as the backup startup software images
main Specify the packages as the main startup software images
<Site4Router1>boot-loader file flash:/MSR2000-CMW710-R0304P02.IPE ma
<Site4Router1>boot-loader file flash:/MSR2000-CMW710-R0304P02.IPE main ?
<cr>
<Site4Router1>boot-loader file flash:/MSR2000-CMW710-R0304P02.IPE main
Verifying the IPE file and the images....Done.
HP MSR2003 images in IPE:
msr2000-cmw710-boot-r0304p02.bin
msr2000-cmw710-system-r0304p02.bin
64 Send Feedback
MN002731A01-A
msr2000-cmw710-security-r0304p02.bin
msr2000-cmw710-voice-r0304p02.bin
msr2000-cmw710-data-r0304p02.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to the device.
Decompressing file msr2000-cmw710-boot-r0304p02.bin to flash:/msr2000-
cmw710-boot-r0304p02.bin....Done.
Decompressing file msr2000-cmw710-system-r0304p02.bin to flash:/msr2000-
cmw710-system-r0304p02.bin...........................Done.
Decompressing file msr2000-cmw710-security-r0304p02.bin to flash:/msr2000-
cmw710-security-r0304p02.bin...Done.
Decompressing file msr2000-cmw710-voice-r0304p02.bin to flash:/msr2000-
cmw710-voice-r0304p02.bin...Done.
Decompressing file msr2000-cmw710-data-r0304p02.bin to flash:/msr2000-
cmw710-data-r0304p02.bin...Done.
The images that have passed all examinations will be used as the main
startup software images at the next reboot on the device.
<Site4Router1>
12 Reboot the router using the reboot command and answer Y at the prompt to reboot the router.
Loading The OS on an HP 2530 Switch Using TFTP

• The OS file for HP 2530 switch
• Ethernet cable
Procedure:
1 Put the switch OS file on a local directory in the PC
2 Configure the TFTP server on the PC to point to the directory where the switch OS file is located.
3 Access the switch command line interface using the console cable and terminal emulation software
like Teraterm.
Bits per sec : 9600

Data bits : 8
Parity : none
Stop bits : 1
Flow control : none
4 If the switch is brand new, follow the following steps. If the switch is currently deployed with
configuration, go to step 5.
a Enter the configuration mode of the switch using configure terminal command.
b Enter the VLAN 1 (default VLAN) configuration mode using vlan 1 command.
c Configure an IP address on the switch in VLAN 1 using ip address <X.X.X.X/mask> command.
Send Feedback 65
MN002731A01-A
d Configure an IP address on the PC from the same subnet as the IP address on the switch.
e Connect the PC to the switch using an Ethernet cable on any port.
f Load the OS into the switch using the following command:
copy tftp flash <IP address of TFTP server> <OS file name on the TFTP server>
NOTICE:
The IP address of the TFTP server is the same as IP address of the PC.
5 If the switch is currently deployed with configuration, follow the following steps.
a Find the IP address of the switch and the VLAN in which the IP address is configured using the
show ip command.
b Find the ports assigned to this VLAN using show vlans <vlan ID or vlan name> command.
c Connect the PC to the switch with the Ethernet cable into one of the ports that belong to the
VLAN identified in the previous step. This establishes the LAN connection from the PC to the
switch.
d Assign the PC an IP address in the same subnet as the IP address of the switch.
e Load the OS into the switch using the following command:
copy tftp flash <IP address of TFTP server> <OS file name on the TFTP server>
NOTICE:
The IP address of the TFTP server is the same as IP address of the PC.
6 Reboot the switch using reboot command for the new OS to take effect
Loading The Configuration on an HP MSR2003 Router Using

TFTP
• The configuration file for HP MSR2003 router
• Ethernet cable
Procedure:
1 Place the router configuration file on a local directory in the PC.
2 Configure the TFTP server on the PC to point to the directory where the router configuration file is
located.
3 Access the router command line interface using the console cable and terminal emulation software
like Teraterm.
66 Send Feedback
MN002731A01-A
Bits per sec : 9600

Data bits : 8
Parity : none
Stop bits : 1
Flow control : none
4 If the router is brand new, configure an IP address on one of the Ethernet interfaces using the
following commands:
a Enter the configuration mode of the router using system-view command.
b Enter the interface configuration mode using interface <interface name> command.
c Configure the IP address on this interface using ip address <IP address> <mask> command.
Example: This process is summarized in the following example:
[Site4Router1]
[Site4Router1-GigabitEthernet0/0]ip address 192.168.3.1 255.255.255.0
[Site4Router1-GigabitEthernet0/0]exit
[Site4Router1]
5 If the router is already deployed in the system with a configuration, use the display ip interface
brief command to find the IP address of the Ethernet interface you wish to use for loading the
configuration.
6 Configure the PC with an IP address in the same subnet as the router and connect the Ethernet
cable from PC to the router to establish IP connectivity.
7 Copy the configuration file from the TFTP server to the router using the following command:
tftp <IP address of the TFTP server> get <Config file name on the TFTP server> startup.cfg
If prompted to overwrite the existing configuration, answer Y.
8 Reboot the router using reboot command.
9 If unsaved configuration changes exist, the router prompts if it can be saved. Answer and follow the
steps as needed. If you answer Y at this prompt and press Return at the next step, these unsaved
changes are written to the newly copied configuration (startup.cfg) file.
Send Feedback 67
MN002731A01-A
10 Answer Y at the prompt when asked to reboot the router.
Example: The following example summarizes steps 7 through 10. Note that step 9 happens only
under certain circumstances.
<Site4Router1>tftp 172.16.1.251 get Site4-Router1.cfg startup.cfg

startup.cfg already exists. Overwrite it? [Y/N]:y
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left Speed
100 3634 100 3634 0 0 4673 0 --:--:-- --:--:-- --:--:--
39500
Writing file...Done.
<Site4Router1>reboot
Start to check configuration with next startup configuration file, please
wait..
.......DONE!
This command will reboot the device. Continue? [Y/N]:y
Loading The Configuration on an HP 2530 Switch Using

TFTP
• The configuration file for HP 2530 switch
• Ethernet cable
Procedure:
1 Put the switch configuration file on a local directory in the PC
2 Configure the TFTP server on the PC to point to the directory where the switch configuration file is
located.
3 Access the switch command line interface using the console cable and terminal emulation software
like Teraterm.
Bits per sec : 9600

Data bits : 8
Parity : none
Stop bits : 1
Flow control : none
4 If the switch is brand new, perform the following steps. If the switch is currently deployed with
configuration, go to step 5.
a Enter the configuration mode of the switch using configure terminal command.
b Enter the VLAN 1 (default VLAN) configuration mode using vlan 1 command.
68 Send Feedback
MN002731A01-A
c Configure an IP address on the switch in VLAN 1 using ip address <X.X.X.X/mask> command.
d Configure an IP address on the PC from the same subnet as the IP address on the switch.
e Connect the PC to the switch using an Ethernet cable on any port.
f Load the configuration into the switch using the following command:
copy tftp startup-config <IP address of TFTP server> <Config file name on the TFTP
server>
NOTICE:
The IP address of the TFTP server is the same as IP address of the PC
5 If the switch is currently deployed with configuration, perform the following steps.
a Find the IP address of the switch and the VLAN in which the IP address is configured using the
show ip command.
b Find the ports assigned to this VLAN using
c show vlans <vlan ID or vlan name> command.
d Connect the PC to the switch with the Ethernet cable into one of the ports that belong to the
VLAN identified in the previous step. This establishes the LAN connection from the PC to the
switch.
e Assign the PC an IP address in the same subnet as the IP address of the switch.
f Load the configuration into the switch using the following command:
copy tftp startup-config <IP address of TFTP server> <Config file name on the TFTP
server>
NOTICE:
The IP address of the TFTP server is the same as IP address of the PC
6 The copy command in step 4 or step 5 prompts the user if switch can be rebooted. Press Y to
accept. A Switch reboot is necessary for the new configuration to take effect.
User Credentials in Transport Network Configuration

The MSR 2003 routers and 2530 Ethernet Switches configuration files still require unique user/system
data to be entered. This section provides the details to enable these aspects.
Send Feedback 69
MN002731A01-A
Configuring the Password for the User ‘root’ on Routers

Router configurations provided for Capacity Max are already configured with a user name ‘root’ with no
password. After loading the configurations on routers, configure the password for this user on each
router using the following procedure.
Procedure:
1 Enter the configuration mode using the command system-view
2 Enter the local user configuration mode using the command local-user root class manage
3 Configure the password using the command password simple <password>
4 Verify the password configuration using the command display this.
Example:
<Site3Router1>
[Site3Router1]local-user root class manage
[Site3Router1-luser-manage-root]password simple capacitymax
[Site3Router1-luser-manage-root]display this
#
local-user root class manage
password hash $h$6$I7vB5lz1Mf8Zm0Nt$iV9uWyHA/
DYPBK22TfYyc9OlakVNvMK2KYivwxB173I
g3MAS1Jg3qu/s7Eyv7DAQTBPdpergJoe54icsR6YmPA==
service-type ssh terminal
authorization-attribute user-role network-admin
authorization-attribute user-role network-operator
#
return
[Site3Router1-luser-manage-root]quit
[Site3Router1]
NOTE
NOTICE:
The password configured in plain text will be converted to a hash by the router for privacy.
Configuring Passwords for the Users on Switches

Switch configurations provided for Capacity Max don’t include any user accounts or passwords. After
loading the configurations, configure the usernames and passwords for each switch using the following
procedure.
Procedure:
1 Enter the configuration mode using the command configure terminal or config
2 Configure the username and password for the manager account using the command password
manager user-name <username> plaintext <password>
3 If required, create another user account with operator privileges using the command password
operator user-name <username> plaintext <password>
70 Send Feedback
MN002731A01-A
Example:
Site1-Switch1# config
Site1-Switch1(config)# password manager user-name root plaintext capacitymax
Site1-Switch1(config)# password operator user-name capmax plaintext motorola
Site1-Switch1(config)#
Configuring SNMP Credentials on Routers

Router configurations include user defined SNMP group name, IP addresses of System Advisors and
security mode AuthPriv. Configure the SNMP credentials matching the System Advisor on each router
using the following procedure.
Procedure:
2 Configure the credentials using the following command:
snmp-agent usm-user v3 <username> <group name> simple authentication-mode sha

<password> privacy-mode aes128 <password>
NOTE
NOTICE:
The group name should match group name already configured on the router
3 Verify the configuration using the command display current-configuration
Example:
<Site3Router1>sys
[Site3Router1]
[Site3Router1]snmp-agent usm-user v3 MotoMaster capacity-max simple
authentication-mode sha capacitymax privacy-mode aes128 capacitymax
[Site3Router1]
Configuring SNMP Credentials on Switches

Switches are configured with the System Advisor IP addresses and few other parameters. When
configuration is loaded, switches create a default SNMP user called ‘initial’. Create the MotoMaster user
and its credentials needed for System Advisor to register with the switches.
Procedure:
1 Enter the configuration mode using the command configure terminal or config
2 Add the SNMP user and credentials using the following command:
snmpv3 user MotoMaster auth sha <password> priv aes <password>
3 Delete the user ‘initial’ if necessary using the command no snmpv3 user initial
NOTE
NOTICE:
Do not delete the user ‘initial’ before adding ‘MotoMaster’. At least one user is needed on the
switch. Otherwise SNMP will be disabled automatically.
Send Feedback 71
MN002731A01-A
Example:
Site1-Switch1# config
Site1-Switch1(config)# snmpv3 user MotoMaster auth sha capacitymax priv
aes capacitymax
Site1-Switch1(config)#
Configuring the Password for the User ‘capacitymax’ on Routers

Routers are configured with a user called ‘capacitymax’ exclusively for the purpose of securing and
authenticating ADVPN sessions. Change the password for this user on each router if necessary using
the following procedure.
NOTICE:
The password for this user on all routers in a system must be same.
Procedure:
2 Enter the user configuration mode using the command local-user capacitymax class network
3 Change the password using the command password simple <password>
Example:
[Site3Router1]local-user capacitymax class network
[Site3Router1-luser-network-capacitymax]
[Site3Router1-luser-network-capacitymax]password simple capacitymax
Pre-shared Keys in Transport Network Configuration

This section provides the details on configuring pre-shared keys in the MSR 2003 routers and 2530
Ethernet switches.
Configuring the Pre-shared Key for the IKE Keychain

On systems with encryption, pre-shared key is configured for the IKE keychain which is used in IKE
profile which is in turn used in the IPsec profile. Change the pre-shared key if necessary using the
following procedure.
NOTICE:
This pre-shared key must be the same on all routers of a system.
Procedure:
2 Enter the IKE key chain configuration mode using the command ike keychain ike-keychain
3 Remove the existing pre-shared key using the command undo pre-shared-key address 0.0.0.0
72 Send Feedback
MN002731A01-A
4 Configure the new pre-shared key using the command pre-shared-key address 0.0.0.0 0.0.0.0 key
simple <pre-shared key>
Example:
<Site3Router1>sys
[Site3Router1]ike keychain ike-keychain
[Site3Router1-ike-keychain-ike-keychain]
[Site3Router1-ike-keychain-ike-keychain]undo pre-shared-key address
0.0.0.0
[Site3Router1-ike-keychain-ike-keychain]pre-shared-key address 0.0.0.0
0.0.0.0 key simple capacitymax
Configuring the Pre-shared Key and User Password for the VAM
Client
Routers with the VAM client setup for the ADVPN domain are configured with a pre-shared key and user
authentication. Change these credentials if necessary using the following procedure.
NOTICE:
This pre-shared key and credentials must be the same on all routers of a system.
Procedure:
2 Enter the VAM client configuration mode using the command vam client name spoke
3 Change the pre-shared key using the command pre-shared-key simple <pre-shared key>
4 Change the user credentials using the command user capacitymax password simple
<password>
Example:
<Site3Router1>sys
[Site3Router1]
[Site3Router1]vam client name spoke
[Site3Router1-vam-client-spoke]pre-shared-key simple capacitymax
[Site3Router1-vam-client-spoke]user capacitymax password simple
capacitymax
[Site3Router1-vam-client-spoke]
Send Feedback 73
MN002731A01-A
Configuring the Pre-shared Key for the VAM Server

Routers with VAM server setup for the ADVPN domain are configured with a pre-shared key. Change
these credentials if necessary using the following procedure.
NOTICE:
This pre-shared key must be the same on all routers configured as VAM server.
Procedure:
2 Enter the VAM server configuration mode using the command vam server advpn-domain
capacitymax id 1
3 Change the pre-shared key using the command pre-shared-key simple capacitymax
Example:
[Site1Router1]vam server advpn-domain capacitymax id 1
[Site1Router1-vam-server-domain- capacitymax]pre-shared-key simple capacitymax
[Site1Router1-vam-server-domain- capacitymax]
74 Send Feedback
MN002731A01-A
System Configuration
Chapter 4
System Configuration 4
Radio Management Configuration

This section describes the minimum configuration to get Radio Management (RM) functional in a
Capacity Max system and considerations for the Radio Management Server, Client, and Device
Programmer deployments.
Radio Management Components

Radio Management is a distributed software suite of applications that allow the user to manage their
fleet of MOTOTRBO™ devices.
Figure 27: Radio Management Components
There are four main components in the RM suite:
Radio Management Server
The RM Server is the main hub of RM. The RM database resides on the RM Server. All other RM
components connect with the RM Server to interface with the RM Database. The RM Server Utility
(included with the RM Sever installation) allows a user to modify RM Server settings.
Radio Mangement Client
Capacity Max systems can be configured by the RM Configuration Client. There are two RM Clients.
One is included and launched from within the CPS. This client is not used for Capacity Max. Using
the RM Configuration Client the user can manage radios in the database and schedule programming
jobs for radios. An RM system can have multiple RM Clients simultaneously connected to the same
RM Server.
Send Feedback 75
MN002731A01-A
Chapter 4: System Configuration
RM Device Programmer (DP)
The RM device programmer is a thin application whose responsibility is to complete programming

jobs scheduled by the RM Client. The device programmer supports USB, over the air programming,
and IP programming for devices that support it. The RM Device Programmer comes with a RM
Device Monitor. The Device Monitor displays settings for the DP and also displays the status of jobs
currently running in the DP. An RM System can have multiple DPs to enable remote programming
stations.
RM Job Processor
The Job Processor (JP) is responsible for combining all the programming elements of the radio
managed in the RM database into a single package that is sent to the Device Programmer. It also
deconstructs the information read from the radio into all the programming elements managed in the
RM Database. An RM system can have multiple JPs to support concurrent job processing.
To configure radios over the air (OTAP), an MNIS data gateway must be used. Typically the device
programmer is on the same PC as the MNIS data gateway.
Radio Management Deployments

The Radio Management Components can all be installed on the same PC, or each on its own PC. This
allows for great flexibility in deployment.
The PCs must all have network connectivity to each other, and the device programmer must have
network connectivity to the system. During initial configuration of the system, the RM Client must have
connectivity to the public internet to verify licenses. The following are basic deployment options to
consider:
Local Radio Management Deployment
A local radio management deployment is when the Radio Management client, server, job processer
and device programmer are all installed on the same PC. As described previously, the device
programmer communicates with the system, therefore it must have an IP connection to the Capacity
Max System Server (CMSS) and the repeaters during programming of those components. In this
deployment, it is assumed that the PC is physically located (long term) at the dealer site and an IP
network connection is established to the customer network. During initial configuration, repeaters
and radios need to be connected through the USB to the device programmer; therefore the PC
needs to be physically close to those devices during initial system installation.
Remote Client (Server at Customer Site) Deployment
A remote client deployment is when the Radio Management server, job processer and device
programmer are located at the customer site with the infrastructure, and a Radio Management client
(or another Radio Management client) is located at the dealer site. This allows the dealer to use the
client to connect the server, change configurations, schedule jobs, and then disconnect from the
server. The jobs can then execute without the need of an ongoing network connection between the
dealer site and the customer site.
Remote Device Programmer (Server at Dealer Site) Deployment
A remote device programmer deployment is when the Radio Management client, server, and job
processer are located at the dealer site, and only the device programmer is located at the customer
site with the infrastructure. This deployment presumes there is a stable network connection between
dealer site and the customer site. The network connection needs to be up when programming the
76 Send Feedback
MN002731A01-A
Capacity Max System Server (CMSS) and repeaters. The network connection must also be up when
executing large over the air radio programming jobs. As radios become present throughout a shift,
their jobs execute, and the device programmer contacts the server, and then requires connectivity to
the server throughout.
Radio Management Component Configuration

Radio Management is utilized to configure radios and infrastructure in the system, but there are only a
few parameters required to configure Radio Management itself. The parameters are identified below for
each component:
Radio Management Client Configuration
The RM Client requires the address and port of the RM Server. On startup, the RM client prompts for
the address and the port number. By default it uses ‘localhost’ and port 8675. The port number
should only be changed if there is a conflict with a non-Motorola software application.
If the RM server is not installed on the same PC, then ‘localhost’ should be replaced with the IP
address or host name (if available) of the RM Server and the Windows ‘hosts’ file on the RM Client
should be updated with the host and IP address of the RM Server. If the network supports DNS, the
‘hosts’ file does not need to be updated. The time between the RM Client and RM Server should
match, and the appropriate time zone should be set based on their locations.
Radio Management Device Programmer Configuration
The RM Device Programmer requires the address and port of the RM Server. The RM Device
Programmer comes with an RM Device Monitor. The Device Monitor can be used to configure the
address and the port number. By default it uses ‘localhost’ and port 8675. The port number should
only be changed if there is a conflict with a non-Motorola software application.
If the RM server is not installed on the same PC, then ‘localhost’ should be replaced with the IP
address or host name (if available) of the RM Server and the Windows ‘host’ file on the RM Device
Programmer should be updated with the host and IP address of the RM Server. If the network
supports DNS, the 'host' file does not need to be updated. The time between the RM Device
Programmer and RM Server should match, and the appropriate time zone should be set based on
their locations.
For the device communication setting, select the appropriate communication method (or all) for the
particular device programmer: USB, Wireless (LAN), Over the Air, IP Program.
For the IP programming settings, a unique Device ID should be utilized. The Local UDP port,
Minimum and Maximum TCP port should only be changed if there is a conflict with some non-
Motorola software application. See Entity Identifier Assignments on page 29 for more details on
setting the Device ID.
The Use Presence Notifier (PN) Server checkbox is selected only if the device programmer is
being used for over the air programming of radios. If the device programmer is being used, the IP
address of the trunking controller should be configured as the PN Server address. The port should
only be changed if there is a conflict with a non-Motorola software application. Any software firewall
on the RM Server should be disabled.
Radio Management Server Configuration
The RM Server Utility (included with the RM Server installation) allows a user to modify RM Server
settings. The RM Server Utility allows for backup and restore of the RM database and creation of
radio management users. Radio Management users can be domain accounts from the current
domain, or non-domain accounts. If they are non-domain accounts, a password can be configured.
Send Feedback 77
MN002731A01-A
Radio Management Licenses

The licenses for Radio Management must be entered. Radio Management provides ten devices without
a license. After ten devices have been added, a license must be added for additional devices to be
added.
Adding a Radio Management License

Procedure:
1 Click the green Actions icon.
2 From the dropdown menu, select Manage  Licenses Application Licenses.
3 Click the Add icon (star).
4 Enter the EID. Click Query.
The results section shows all the features in the license, the amount purchased, the amount
available, and a quantity field.
5 Select the appropriate features and enter the desired quantity for the selected feature.
6 Click Register.
The Radio Management Client contacts the licensing server and generates a license for the
features.
System Parameter Configuration

All devices in a Capacity Max system reference the same system level parameters. This minimizes
entering duplicate information for each device type, therefore lowers the probability of mistakes. There
are five major categories of system level parameters, and a couple sub-categories:
• Capacity Max System Set
• Capacity Max Sites
• Capacity Max Channels
• Capacity Max Site Selection Set
• Capacity Max Radio Wide Features Set
• IP System Settings
• Capacity Max System Server Data
• Subscriber Access Control
• Talkgroup Site Association
Capacity Max System Set

The first step in configuring a Capacity Max system is creating a System Set. All devices in a Capacity
Max system reference the system set.
78 Send Feedback
MN002731A01-A
Adding a New System Set

Procedure:
2 From the dropdown menu, select Manage  Sets.
The System Set appears. Two sets of categories are shown: General and Capacity Max Features.
Within the Capacity Max Features category, there is Capacity Max Systems, Capacity Max Site
Selection, and Capacity Max Radio Wide Features.
3 Highlight Capacity Max Systems, and select New Set.
Capacity Max System Set Parameters

The following provides guidance on setting the parameters in the Capacity Max System Set.
General
This section contains general system parameters.
System Name
Assigns an appropriate System Name.
System Type
Sets the system type to Capacity Max Advantage, Capacity Max Open System, and Capacity
Max Open Radio.
Capacity Max Open System
This system type uses the DMR trunking protocol and therefore it supports both MSI and non-
MSI radios. In this mode, a Capacity Max system provides more capacity when it is working
with the MSI radios.
Capacity Max Advantage
This system type provides more capacity than the Capacity Max Open System. All the
capacity enhancements of Open System with MSI radios are also available in Capacity Max
Advantage.
Capacity Max Open Radio
This system type applies to the radio only and not the system. The radio transmits and
receives only standard DMR trunking protocol messages. This system type is used when
radios are on a DMR system of another manufacturer.
Network Model and Network ID
In the DMR trunking protocol, the network model and network ID are used together to make up a
system ID. As the size of the network increases, Tiny, Small, Large, Huge, the range of the
network ID decreases. The combination of the Network Model and Network ID should not match
that of a neighboring system. See Entity Identifier Assignments on page 29 for more details.
Send Feedback 79
MN002731A01-A
Ehanced Channel Access
Enhanced Channel Access is a high speed handshake between the radios initiating
transmissions and their traffic channel repeaters. It manages floor control for the transmissions
within a call. It is always enabled.
Text Message Type
There are three types of protocols for Text Messaging:
• DMR Standard
• Motorola Proprietary
• Capacity Max Short Data
Capacity Max Short Data is sent on the control channel; while other protocols are sent on the
trunked channels. Sending data on the control channel is not recommended, since it may
degrade performance and capacity. The DMR Standard protocol is recommended in most cases.
The other protocols are available for interoperability. Short Data is not supported through the
MNIS Data Gateway.
Location Area Length in bits (DMRLA)
A location area is a group of sites where the radio is not required to register explicitly while
roaming among the sites in the group. In Capacity Max, a location area only contains one site,
and therefore is not configurable if the system type is Capacity Max Open System, or Capacity
Max Advantage. If a radio is configured with a system type of Capacity Max Open Radio and
therefore operating on another manufacturer system, then a location area mask length can be
configured. The value of the location area mask length is limited by the configured Network
Model.
Comprehensive Hunting
If a radio cannot find a suitable control channel at adjacent and non-adjacent sites, the radio can
optionally start comprehensive hunting. Comprehensive hunting looks through all the frequencies
which can be converted into a channel ID using the configured fixed channel plan of the radio. It
uses the channel IDs that are convertible to an absolute frequency through the fixed channel
plan mapping. Comprehensive hunting is configurable only when the radio is configured with a
system type of Capacity Max Open System or Capacity Max Advantage. See Multi-Site Roaming
Optimization on page 154 for more details.
RSSI Acceptable Threshold
This threshold determines the coverage area where the strength of the signal received by a radio
is sufficient to establish and maintain communication with the base repeater, either for a control
channel or for a trunked channel. See Multi-Site Roaming Optimization on page 154 for more
information on setting this parameter.
Individual Voice Call Type
Capacity Max supports two types of individual calls. All radios in the system must utilize the same
call type.
OACSU (Off Air Call Set Up)
An individual call is set up after checking the availability of the destination radio.
80 Send Feedback
MN002731A01-A
FOASCU (Full Off Air Call Set Up)
An individual call is set up after checking the availability of the destination radio and the
willingness of the radio user to participate in the call.
Call Queue Enable
When there are no resources available to grant a call request, the trunking controller places the
call in the queue. When a resource becomes available, the call is removed from the queue and
granted the resource. If a system is designed for proper channel loading, on average, a low
percentage (3%) of calls should be placed in the queue. The call queuing can be disabled, if
queuing is causing unacceptable delay. If disabled, when there are no resources available to
grant a call request, the call is denied.
Max Infrastructure Voice Interrupt Attempts
The maximum infrastructure voice interrupt attempts sets how many times the infrastructure
attempts a voice interrupt command. The default is 3. The default is highly recommended.
Max Preemption Interrupt Attempts
The maximum preemption interrupt attempts sets how many times the infrastructure attempts to
preempt an ongoing call. The default is 6. The default is highly recommended.
Primary Trunking Controller IP
This is the IP address of the Primary Trunking Controller. The Capacity Max System Server
(CMSS), where the Primary Trunking Controller resides on, is configured with a base IP address
(a subnet) in the CMSS Configuration within RM. The IP addresses of all the virtual appliances
within the CMSS maintain a fixed offset from its base IP address. The Trunking Controller is +1
from the base IP address configured in the CMSS. The CMSS comes pre-configured as
172.20.36.0, if not changed, the Trunking Controller IP is 172.20.36.1. See Understanding IP
Addressing on page 15 and Capacity Max System Server (CMSS) Configuration on page 111 for
more information.
This field does not set the IP address used by the Primary Trunking Controller, this is used by
other devices in the system to communicate to the Primary Trunking Controller.
Primary Trunking Controller UDP Port
This is the UDP Port used by the Trunking Controller. It should remain as the default unless a
conflict is discovered.
Call Monitoring Application 1-3 IP
These are the IP address of the Call Monitoring Applications. The system supports three. Call
Monitoring Applications include the System Advsior Servers and Genesis.
The Capacity Max System Server (CMSS), where the System Advisor Servers reside on, is
configured with a base IP address (a subnet) in the CMSS Configuration within RM. The IP
addresses of all the virtual appliances within the CMSS maintain a fixed offset from its base IP
address. The System Advisor Server is +5 from the base IP address configured in the CMSS.
The CMSS comes pre-configured as 172.20.36.0, if not changed, the System Advisor Server IP
is 172.20.36.5. If following the recommended IP plan, the System Advisor Server IP on the
redundant CMSS is 172.20.37.5. See Understanding IP Addressing on page 15 and Capacity
Max System Server (CMSS) Configuration on page 111 for more information.
Send Feedback 81
MN002731A01-A
Call Monitoring Application 1-3 Port
These are the UDP Port used by the Call Monitoring Applications. It should remain as the default
unless a conflict is discovered.
Voice Interrupt Support
Capacity Max supports the ability to interrupt a transmitting radio. The ability to interrupt can be
configured per radio within the Subscriber Access Control (SAC). This checkbox disables the
feature system wide without the need to individually set each radio within the SAC. This is useful
in scenarios when there is a need to temporarily disable all voice interrupt capability, and then
quickly restore it to the same radios that were previously enabled.
Telephone Support
Capacity Max supports the ability for radios to initiate calls to phone users. The ability to initiate
phone calls can be configured per radio within the Subscriber Access Control (SAC). This
checkbox disables the feature system wide without the need to individually set each radio within
the SAC. This is useful in scenarios when there is a need to temporarily disable all radio’s
capability to initiate telephone calls, and then quickly restore it to the same radios that were
previously enabled. Since phone systems go through the trunking controller, inbound calls are
also blocked.
GPS Revert Parameters
These parameters are related to GPS Revert. These parameters apply to all radios in the system
and all data revert repeaters in the system.
Enhanced (Scheduled) GPS
This field is always enabled to specify that any configured data revert channels are Enhanced
GPS Revert channels (scheduled). See Data Revert Channel Configuration on page 151 for
details on data revert channels.
Enhanced (Scheduled) GPS Window Size
The GPS window size of the Enhanced (scheduled) GPS must be configured. The size of the
window (the duration of the scheduled time window) is a function of the amount of data
requested by the location server. Third party developers can provide the window size they
require for their location server. A typical window size is 7 if using IP data, and 1 if using High
Efficiency Data (alternately “compressed GPS”) and the MNIS data gateway. To enable High
Efficiency Data in the radio, select the Efficiency option (CSBK Data) in the radio personality.
See Data Revert Channel Optimization on page 151 for details on selecting a GPS Window
Size.
GPS on Revert Channel Only
When this field is checked, GPS data is only sent on data revert channels. If unchecked, and
no data revert channels are configured at a site, the GPS data is sent on the trunked
channels.
This parameter is important if some sites have data revert, while others do not. If radios that
are configured to send GPS move from a site that has data revert to a site that does not have
data revert, this checkbox controls whether those radios transmit their GPS on the trunked
channels or not.
82 Send Feedback
MN002731A01-A
The trunked channels support significantly less GPS than the data revert channels. If a high
rate of GPS is sent on the trunked control channel when the data revert channel fails, The
GPS affects voice call reliability and can result in overwhelming the inbound control channel.
This parameter should only be unchecked if the site’s GPS rate can be supported on the
trunked channels.
The control channel supports up to 200 inbound messages/min at its site. Inbound messages
include requests from a radio for voice, text, location, and others. If voice, text, and location
data together exceeds 200 inbound messages/min, then the location data needs to be sent
on a revert channel.
Data Revert Admit Criteria
This is the channel admit criteria for the data revert channel. The Admit Criteria can be
Channel Free or Color Code Free. Color Code Free is almost always recommended.
Authentication Parameters
These are the system level parameters related to authentication.
Authentication of Radios by System
If radios must authenticate with the system during registration, then select authentication
required. If authentication is required, a Master Key must be provided.
Authentication of System by Radio for Stun/Revive
If radios must authenticate the system before processing a stun command, then select stun/
revive authentication. If stun/revive authentication is required, a Master Key must be
provided.
Authentication Master Key
The Master Key is used for radio authentication during registration and for stun/revive
authentication. If either are enabled, a master key must be provided.
Timers
The majority of the timers in this section can remain at their default values. See the explanations
below to determine if adjustment is required.
Channel Grant Waiting Timer
This is the maximum time a radio waits for its channel grant after receiving an initial response
(WACK/QACK) from the system for a service request that requires a trunk channel. In a properly
designed system (call rate and call duration versus number of repeaters) calls should only be
briefly queued before granted a resource. If radios are experiencing long queuing times, and
then Call Fails, this timer could be increased to allow them to wait longer. The call request
remains in the trunking controller queue after the radio’s Channel Grant Waiting Timer expires.
The range is 4 to 60 sec, in increments of 1 sec. The default value is 15 seconds.
Response Waiting Timer
This is the maximum time a radio waits for a response from the system for a service request that
does not require a trunked channel (such as a Registration, Call Alert, or UDT data message).
The range is 2 to 20 sec, in increments of 0.1 sec. The default value is 4 seconds.
Send Feedback 83
MN002731A01-A
Denied Registration Duration
This is the minimum duration for which a radio does not register at a site where its request for
registration was explicitly denied. 0 sec implies that the denied sites are to be removed only after
the radio power cycles. The range is 0 sec to 10000 sec in increment of 10 sec and the default
value is 300 sec. Therefore by default, once a radio is explicitly denied registration at a site, it
waits 5 minutes before it attempts to register again, or until it power cycles. This is sometimes
referred to as placing a site in the ‘penalty box’.
Comprehensive Hunting Timer
Comprehensive hunting may take a long time and therefore short hunting is mixed in. The
comprehensive hunting timer is used to prevent a radio from spending a long time in this hunting
state. Upon expiry of this timer the radio leaves comprehensive hunting to restart short hunting.
The radio remembers the last attempted frequency before leaving comprehensive hunting. Upon
entering comprehensive hunting again, the radio continues from where it left. The range is 5 to
30 sec in increment of 1 sec and the default value is 10 sec.
Group Call Hang Time
The group call hangtime sets the duration the repeater reserves the channel after the end of a
group call transmission. During this time, only members of the Group that the channel is reserved
for can transmit. Setting the duration of the call hangtime can change the system operation from
transmission trunking (0 sec), quasi-transmission trunking (2-6 sec), and message trunking (20-
30 seconds). Capacity Max supports explicitly clearing of call hangtime by the user by hanging
up. The range of the group call hangtime duration is from 0 to 60 seconds in 1 second intervals
with a default value of 3 seconds.
Private Call Hang Time
The private call hangtime sets the duration the repeater reserves the channel after the end of an
individual call transmission. During this time, only the two participants of the individual call can
transmit. Typically the private call hangtime is longer than the group call hangtime since it often
takes longer to dial and setup the start of an individual call. The range of the private call hangtime
duration is from 0 to 60 seconds in 1 second intervals with a default value of 4 seconds. Capacity
Max supports explicitly clearing of call hangtime by the user by hanging up.
Emergency Call Hang Time
The emergency call hangtime sets the duration the repeater reserves the channel after the end
of an emergency group call transmission. During this time, only members of the Group that the
channel is reserved for can transmit. Typically the emergency call hangtime is longer than the
group call hangtime since it is desirable to reserve the channel for a longer period of time for the
emergency situation. The range of the emergency call hangtime duration is from 0 to 60 seconds
in 1 second intervals with a default value of 4 seconds. Capacity Max supports explicitly clearing
of call hangtime by the user by hanging up.
No Signaling Timeout
The no signaling timeout sets the duration the radio remains on a control channel without
receiving a synchronization message. If the radio flywheels out (such as looses synchronization)
while on the control channel, then it begins hunting for a new control channel. The range of the
no signaling timeout is from 1 to 15 seconds in 1 second intervals with a default value of 2
seconds.
84 Send Feedback
MN002731A01-A
Payload Channel Flywheel Duration
The payload channel flywheel duration sets the duration the radio remains in call without
receiving a synchronization message on the trunked channel. If the radio flywheels out (such as
looses synchronization) while on the trunked channel, then it attempts to perform a call handover
to an adjacent site. If the handover is not possible, it returns to the control channel. The range of
the payload channel flywheel duration is from 720ms to 5400ms in 230ms intervals with a default
value of 2160 ms.
Call Reconnect Duration
A radio in a call returns to the control channel when it flywheels out on the trunked channel. The
call reconnect duration is how long a radio will not join another call whose priority is the same or
less than the dropped call. In this case, the user has a chance to rejoin the dropped call, by
ignoring other ongoing call grants for a while. The call reconnect duration range is 1 seconds to
10 seconds in increment of 1 seconds and a default value of 3 seconds.
Inter-Repeater Messaging Delay
The inter-repeater messaging delay is the expected worst case repeater to repeater network
delay. The options are normal (60ms) and high (90ms). The default is normal (60ms). If the
network delay is especially high in your network, then the value can be set to high (90ms).
Increasing the inter-repeater messaging delay to high (90ms) increases response timers to
accommodate longer delays. This ultimately impacts call performance even if actual delays are
normal. Most networks have inter-repeater delays well below 60ms.
Inactivity Check Timer
The inactivity check timer sets the periodic registration interval in the radio and the de-
registration interval in the system. If for the duration of the periodic registration interval, the
system monitors no activity from a registered radio, then it may de-register the radio. If the timer
is non-zero and the radio has not received any response for its requests (such as a registration,
call, and others) from the system in the last periodic registration interval then it re-registers itself.
The range of the periodic registration interval is 1/2 hour to 48 hours in increment of half hour and
a default value of 4 hours. A periodic registration interval of 0 implies that the radio is not required
to perform any Periodic Registration.
Channel Plan List
Capacity Max (and the DMR Trunking Protocol) uses a number to represent a channel over the air.
The range of the Channel Number (also called Channel ID) is from 1 to 4094 (inclusive). A Channel
Number is a logical entity and represents an ordered pair of a physical transmit (with respect to a
radio) frequency and a physical receive (with respect to a radio) frequency. This one-to-one mapping
between the Channel Number and the frequency pair is called a Channel Plan.
Capacity Max (and the DMR Trunking Protocol) provides two ways to specify the mapping between
the Channel Numbers and the frequency pairs. The two ways are called Fixed and Flexible. The
Fixed specify the mapping by rules and the Flexible specify the mapping individually by listing the
frequency pair and its channel number.
The fixed mapping is the preferred way to map frequency pairs to a channel number. It supports
future expansion of a system better than flexible mapping. It is likely that the frequency pair of the
newly added trunked repeater at a site is covered by the fixed mapping. In that case the addition of a
trunked repeater at a site does not require reprogramming of the radios.
It is recommended to determine the Channel Plan list prior to setting up the channels within the
system set. The frequencies of the channels are specified by the number within the channel plan. If
the channel plan is not complete when setting up the channels, the desired frequencies are not
selectable.
Send Feedback 85
MN002731A01-A
See Understanding the Channel Plan on page 36 and Adding a Channel Plan on page 86 for more
details.
Fixed Channel Plan
For the Fixed Channel Plan mapping, the following rule is used to map a Channel Number into
absolute transmit / receive frequencies of a radio.
F
MS_Tx = Fbase +((CHAN - MIN_CHAN_Num) x (Fseparation /1000))
F
MS_Rx = FMS_Tx + Fduplexsplit
where:
F
MS_Tx : absolute transmit frequency of a radio, in MHz
FMS_Rx : absolute receive frequency of a radio, in MHz
CHAN : Channel Number, between 1 to 4094 (inclusive)
MIN_CHAN_Num : Minimum Channel Number is the minimum values of the Channel Number
Fseparation : Channel Separation (or spacing), (12.5 kHz or 25 kHz)
Fduplexsplit : Duplex Split or the difference (positive or negative number) of the receive
frequency from the transmit frequency, (-50 MHz to 0 MHz to 50 MHz in
2.5 kHz steps)
Fbase : Base Frequency, in MHz
The MIN_CHAN_Num is 1 for the first segment, and one plus the number of channels in the first
segment for the second segment, and so forth. See Understanding the Channel Plan on page 36
for more details.
Flexible Channel Plan
The Flexible Channel Plan should be used to map all the frequency pairs that are exception
cases of the Fixed Channel Plan mapping. The flexible mapping does not have rules. All the
frequency pairs are individually specified with corresponding channel numbers. Any Channel
Number in the fixed mapping, which is least likely to be used by a frequency pair, should be used
for the Flexible Channel plan. See Adding a Flexible Channel Plan on page 86.
Adding a Channel Plan

Procedure:
2 Select the type that equals your frequency band.
3 To edit the channel plan, right click on the new channel plan and select Edit.
Adding a Flexible Channel Plan

Procedure:
2 Enter the physical channel number, repeater Rx frequency, and the repeater Tx frequency.
3 To edit the flexible channel plan, right click on the new flexlible channel plan and select Edit.
86 Send Feedback
MN002731A01-A
Adding Capacity Max Sites

In the System Set, the system’s sites must be added.
Procedure:
3 Within the Capacity Max Features category, highlight Capacity Max Systems.
4 Within the System Set, select Capacity Max Sites.
6 Select the Site Type.
7 Edit the newly added site.
Capacity Max Site Parameters

Site Type
A Capacity Max System has RF Sites and Gateway sites. A Gateway site can be a MNIS Data
Gateway, or an MNIS Voice and Radio Command (VRC) gateway.
NOTE
NOTICE:
A site must be added for each RF, each MNIS Data Gateway, and each primary MNIS VRC
Gateway. A separate site does not need to be made for a redundant MNIS VRC Gateway.
General
Site ID
RF Sites and Gateways are identified by a Site ID. The Site ID allocated to a site must be unique.
The range of available Site IDs depends upon the Network Model (Tiny, Small, Large, Huge)
defined earlier in the System Set. See Entity Identifier Assignments on page 29 for more details
on setting the Site ID.
Channel Plan
An RF Site has one Channel Plan. Select a Channel Plan previously defined. Channel
frequencies at this site are selectable through the defined channel number from the selected
Channel Plan. A Gateway site does not have a Channel Plan.
Network
The network parameters are only available for RF Sites. Network information for the gateways is
configured elsewhere.
Base IP
The Base IP address is the subnet address of the RF site. The IP addresses of the repeaters and
their roles are automatically calculated from this Base IP and the repeater’s Device ID. Typically,
the Base IP address for site 1 is 172.16.1.0, and the Base IP address for site 2 is 172.16.2.0, and
others. See Understanding IP Addressing on page 15 for more details.
Send Feedback 87
MN002731A01-A
Base UDP Port
The Base UDP port is the first UDP port for a RF site. All UDP ports utilized by the repeaters are
calculated from the base UDP port. The Base UDP port should remain at the default value of
65000 unless a conflict has been identified.
Network Gateway IP
The Network Gateway IP is the address of the node that is assumed to know how to forward
packets on to other networks. For RF sites, this is typically the site router’s IP address. The
Network Gateway IP for site 1 is typically 172.16.1.20, for site 2 it is typically 172.16.2.20, and
others. See Understanding IP Addressing on page 15 for more details.
Network Gateway Netmask
The Network IP Address and Gateway Netmask together describe the Network ID. For example,
destination 172.16.1.0 and netmask 255.255.255.0 can be written as network ID 172.16.1.0/24.
For an RF site, the Network Gateway Netmask is typically 255.255.255.0. See Understanding IP
Addressing on page 15 for more details.
GPS Longitude and Latitude
If High Efficiency Data is enabled in the system, the GPS coordinates of the site must be entered.
Subscriber
These parameters are utilized by the subscribers at a site level.
Roaming RSSI Threshold
This Roaming RSSI Threshold divides the acceptable signal coverage into no-roaming and
roaming-in-acceptable area. It also determines the strong signal area within the acceptable
signal coverage.
Adjusting the default value can be done to affect the radio roaming behavior. Increasing the
Roaming RSSI Threshold decreases the distance from the site where the radio starts roaming.
Decreasing the Roaming RSSI Threshold increases the distance from the site where the radio
starts roaming. See Multi-Site Roaming Optimization on page 154 for more details.
Handover RSSI Threshold
Capacity Max supports a proprietary in call handover, only for the radios that are either receiving
or are in a call hangtime state in a voice talkgroup call. The transmitting radio does not support
call handover. There are two signal conditions that must be fulfilled, the signal of the current
trunked channel is lower than the Handover RSSI Threshold value and there is at least one
adjacent trunked channel that has signal strength more than 6 dBm greater than the current
trunked channel. In most cases, this value should match the Roaming RSSI Threshold value.
See Multi-Site Roaming Optimization on page 154 for more details.
Adding Capacity Max Channels

From the System Set, the site’s channels must be added.
Procedure:
88 Send Feedback
MN002731A01-A
5 Within Channels, click the Add icon (star).
6 Select the new channel.
7 Select Edit.
Each channel represents a repeater with two logical channels (timeslots).
Capacity Max Channels Parameters

General
Channel Name
Provide a channel name for the channel. Typical names may be Trunking Channel 1, Data
Revert Channel 1, and others.
Channel Type
A channel can be a Trunked Channel or a Data Revert Channel.
Use Fixed Channel Plan
The channel’s transmit and receive frequencies are set by their corresponding physical channel
ID in the Site’s selected Channel Plan. When checked, the channel frequencies are calculated
using the Fixed Channel Plan. When unchecked, the channel frequencies are calculated using
the Flexible Channel Plan.
Control Channel Capable
The Control Channel Capable checkbox sets whether a repeater is capable of becoming the
site’s control channel. Up to four control channel capable repeaters are allowed per site. Only
repeaters with exclusive frequency licenses should be configured as control channel capable.
The control channel of a Capacity Max system is always on the first slot of a physical channel.
This option is not applicable to a Data Revert channel.
Preferred Control Channel
Capacity Max allows tagging one or more candidate control channel as “Preferred”. A non-
Preferred candidate control channel acts as a control channel only if the site has no “Preferred”
candidate control channel. In case of multiple preferred control channels, the preferred channel
having the lowest Device ID is selected as the control channel. The “Preferred” option is useful
when a frequency pair is more suitable (such as less interference) as a control channel over
other candidate control channels. This option is not applicable to a Data Revert channel.
Trunked Channel Preferences
A Capacity Max system allows the system owner to configure his/her preference for usage of a
physical trunked channel (both slots) in a repeater. The guidelines for assigning the preference
level for a trunk channel are as follows:
• Exclusively licensed channels should have higher preference than the shared channels.
• Within shared channels, the preference is should be for channels with the least co-channel
user activity.
Send Feedback 89
MN002731A01-A
When a service request is selected for allocation of channels, the system assigns a trunk
channel at a site as per the following rules.
• Within all ‘Idle’ trunk channels at that site, the high preference trunk channel is assigned
before the low preference trunk channel.
• Within same preference level, trunk channels are assigned in round robin method.
• The trunk channel on the second slot of a control channel repeater is assigned only when no
other idle channel is available at the site. The second slot of a control channel is used by MSI
radios for registration.
This option is not applicable to a Data Revert channel.
Physical Channel ID and Repeater RX/TX Frequencies
Capacity Max (and the DMR Trunking Protocol) uses a number to represent a channel over the
air. The range of the Channel Number (also called Channel ID) is from 1 to 4094 (inclusive). A
Channel Number is a logical entity and represents an ordered pair of a physical transmit (with
respect to a radio) frequency and a physical receive (with respect to a radio) frequency. This one-
to-one mapping between the Channel Number and the frequency pair is called a Channel Plan.
Select the Channel ID that represents the transmit and receive frequency pair for the repeater.
Note that this requires that the appropriate Channel Plan has been developed and entered into
Radio Management. See Understanding the Channel Plan on page 36 for more details.
Color Code
The color code is used to differentiate multiple signals that may be present on a single
frequency. If neighboring DMR sites share the same frequencies, the repeaters should be
configured with a different color code. Control channel repeaters should have exclusive
frequencies. If using a Fixed Channel Plan, all repeaters at a site must have the same color
code.
Enhanced GPS
Window Size
The Window Size for Enhanced GPS is set per system. It is not configurable different per
timeslot, or per repeater, or per site. It is shown here for reference.
Periodic Window Reservation
If enabled for Data Revert, the Periodic Window Reservation window for a timeslot can be set
to 45, 60, 75, or 90%.
Shared Channel Frequency
If enabled for Data Revert, the repeater must be identified as a shared channel frequency or
exclusively licensed (unshared). If marked as a shared channel frequency, the periodic
windows are assigned adjacent to each other, rather than spread out over time. This results
in longer idle periods that are more useful for other systems that are sharing the channel.
Adjacent Sites
Site adjacency defines which sites are next to each other. This information is announced over the air
at every site, to help the radios with roaming. The radios receive the announcement about the sites
that are adjacent to the site that the radio currently registers with.
90 Send Feedback
MN002731A01-A
All sites in the system are automatically added to the list in the Adjacent Sites list. Each site can have
up to seven adjacent sites. Site adjacency should be reciprocal to support roaming in both directions
between two sites. This means that if Site-3 is configured to be adjacent to Site-1, Site-1 is
automatically configured to be adjacent to Site-3. See Multi-Site Roaming Optimization on page 154
for more details.
Site Announcement
Traditionally, when a new RF site is added to the system, the system administrator has to go through
the arduous task of reprogramming the radios within a short amount of time. Capacity Max system
allows the addition of a new RF site by announcing the new site at other sites. The radios listening to
the announcement learn and persistently store the new site information and use it to roam to the new
site.
When a new RF site has to be added to the system, the site needs to be configured in Radio
Management (RM) and pushed to the infrastructure. This includes configuring site parameters such
as adjacent sites of the new site, adding repeaters to the new site, Talkgroups’ association with the
new site, radio access to the new site in the Subscriber Access Control (SAC), and others.
Announcement Duration
Select the announcement duration such that all the radios at the site get a chance to listen to the
announcement. For example, the announcement duration may need to be in the range of a week
(168 hours) if some radio users only use the system once a week. Site announcement entries
can be modified and pushed to CMSS to make a new announcement. If needed, same
announcement can be made multiple times by pushing the configuration to CMSS again.
Announcement Sites
If all the radios in the system need to know the new site, select all the RF sites except the new
site as announcing sites. If radios within a region need to know the new site, select the sites in
that region as announcing sites.
Configuring a Site Announcement

Procedure:
5 Within Site Announcement, click the Add icon (star).
6 Select the new site to be announced.
7 Select the Announcement Duration and which sites to announce to, for example, the
Announcement Sites.
8 Schedule a Write job to the CMSS within Radio Management to push the site announcement into
the CMSS.
After the Write job is complete, the CMSS announces the site for the specified announcement
duration.
Send Feedback 91
MN002731A01-A
Capacity Max Site Selection Set

All sites, that the radio is allowed or supposed to roam to must be configured into the radio. In a multi-
site network, not all sites in the network are roamable sites. Some sites may not be ever roamable due
to permanent technical reasons such as a frequency band difference or large geographical separation.
Other reasons may be due to permanent administrative or operational arrangement which requires
some radios to never roam to some particular sites. Sites included in the site selection can be
dynamically allowed or disallowed from the Subscriber Access Control per radio and talkgroup.
See Roamable Sites on page 154 for more details.
Multiple sets of sites can be created in Radio Management and linked to radio configurations. Some
examples of ‘site sets’ may be UHF Sites, Chicago Sites, St. Louis Sites, Northern Sites, Southern Sites,
Maintenance Sites, Tactical Sites, and others.
NOTICE:
A separate site selection list must be made that contains the MNIS Data Gateway site.
Another separate site selection list must be made that contains the MNIS VRC Gateway site.
Additional MNIS Data Gateway sites or Primary MNIS VRC Gateway sites must have their own site
selection list as well. The same MNIS VRC Gateway site selection list is referenced from both the
primary and redundant CMSS configuration. Each MNIS Data Gateway site selection list is referenced
separately from its specific MNIS Data Gateway configuration.
Selecting a Capacity Max Site

Procedure:
3 Within the Capacity Max Features category, highlight Capacity Max Site Selection.
4 Select Create a New Set.
6 Select the system, and then select the desired sites.
7 When editing or creating a Radio Configuration, select the created site set.
Capacity Max Radio Wide Features Set

These radio wide parameters are shared by all radios utilizing the configured set. Normally, a system
only has one radio wide feature set, but if different users require different parameters, multiple sets are
required. In most cases, these parameters can remain at their default value.
92 Send Feedback
MN002731A01-A
Configuring the Capacity Max Radio Wide Features

Procedure:
3 Within the Capacity Max Features category, highlight Capacity Max Radio Wide Features.
4 Select Create a New Set.
Capacity Max Radio Wide Features Parameters

Control Channel Response Timer
The control channel response timer is the duration the radio waits for a response to a request on the
control channel. The default value of 180ms is strongly recommended. Decreasing the control
channel response timer increases the percent of channel access failures, “Call Failed” indication, the
radio experiences when pressing the PTT. If operating close to the outbound control channel limit of
20,000 cph, increasing the control channel response timer may improve the ability to access the
channel.
Non Emergency Random Access Attempts
This parameter controls the number of channel access attempts the radio makes for every call type
except emergencies. The default value of 6 attempts is strongly recommended. Radios access the
control channel using a random access procedure. As the number of radios attempting to access the
control channel increases, two or more radios may randomly select the same time-slot to send their
request. This collision may result in the control channel manager not receiving one or both of the
requests due to RF contention and burst corruption. If the control channel manager does not receive
the message, then it does not transmit a response. If the radio does not receive a response the radio
attempts again.
Decreasing the number of random access attempts increases the percent of channel access
failures, “Call Failed” indication, the radio experiences when pressing the PTT. Increasing the
number of random access attempts decreases the maximum number of request a control channel
can support (12,000cph). If a high level of interference is present on the control channel, increasing
the number of random access attempts may improve the ability to access the channel. Although note
that control channels in Capacity Max do require exclusive use frequencies.
Emergency Random Access Attempts
This parameter controls the number of channel access attempts the radio makes for emergencies.
The default value of 10 attempts is strongly recommended. See the description in the “Non
Emergency Random Access Attempts” parameter for more details.
Site Trunking Tone Interval
This parameter is the periodic interval for the Site Trunking Tone. When a radio is at a site that is in
Site Trunking, the radio sounds the Site Trunking Tone after each interval. The default value is 2
minutes.
Out of Range Tone Duration
This parameter is the periodic interval for the Out of Range Tone. When a radio is Out of Range of
any RF site, the radio sounds the Out of Range Tone after each interval. The default value is 1
minute.
Send Feedback 93
MN002731A01-A
IP System Settings
The IP System Settings is used by Radio Management to communicate with the system when a read or
write is scheduled for CMSSs or repeaters. There are three types of IP System Settings:
• Capacity Max System Server
• Capacity Max Repeater
• Link Establishment ( Link Establishment is not utilized in Capacity Max.)
A Capacity Max system typically requires at least two IP Systems, three if utilizing a redundant CMSS.
One Capacity Max System Server IP System must be created for the primary CMSS and one must be
created for the redundant CMSS (if applicable). One Capacity Max Repeater IP System must be created
for the repeaters to use.
Editing the IP System Settings

Prodedure:
2 From the dropdown menu, select Manage  IP System Settings.
IP System Setting Parameters

System Type
The system type should be selected to Capacity Max System Server.
System Alias
Provide an appropriate system alias for easy reference. Example, “Customer X Primary CMSS”,
“Customer X Alternate CMSS”, “Customer X Repeaters”
Trunking Controller IP
This is the IP address of the Trunking Controller.
• The IP System Settings utilized by the Primary CMSS should utilize IP address of the primary
Trunking Controller.
• The IP System Settings utilized by the repeaters should have the IP address of the primary
• The IP System Settings utilized by the Alternate CMSS should utilize IP address of the alternate
UDP Port
The port is only required for the Capacity Max Repeater IP System. The UDP port should match the
Primary Trunking Controller UDP port configured in the Primary CMSS and in the System Set.
Default is 50000. This should remain default unless a conflict was encountered.
94 Send Feedback
MN002731A01-A
Network ID
The Network ID is only required for the Capacity Max Repeater IP System. The Network ID should
match the Network ID configured in the in the System Set.
The appropriate IP System set must be selected for each CMSS and repeater within the Radio View
list.
Selecting the IP System Settings for a CMSS

Procedure:
1 From the Radio View screen, right click on a device (CMSS or Repeater).
2 From the dropdown menu, select Select IP System Set.
Capacity Max System Server Data

The Capacity Max System Server (CMSS) contains two configurable sets of data: The Subscriber
Access Control (SAC) and the Talkgroup Site Association data.
Configuring the Capacity Max System Server Data

Motorola radios are automatically added to the SAC list when the system parameter set is selected
within a radio configuration.
When the Subscriber Access Control (SAC) and the Talkgroup Site Association data is updated, the
CMSS is not identified as modified in Radio Management. After updating the Subscriber Access Control
(SAC) and the Talkgroup Site Association data, the CMSS should be programmed.
Procedure:
2 From the dropdown menu, select Manage  Capacity Max System Server Data.
Subscriber Access Control

Capacity Max allows maintaining a list of permitted services and a list of permitted sites for each radio in
the system. The Subscriber Access Control (SAC) is useful for restricting the services temporarily for a
radio, may be due to non-payment of dues. The SAC also allows the system owner to charge for
services based on the type of services and/or number of sites. The SAC can be utilized for dynamic
changes the capabilities of a radio without reprogramming the radio.
Capacity Max Subscriber Access Control Parameters

Device Type
There are four device types in the Subscriber Access Control:
• Motorola Radio
• Non-Motorola Radio
• Console (Voice Application)
Send Feedback 95
MN002731A01-A
• Data Gateway
Motorola Radios are automatically added to the SAC list, but the other device types must be
manually added.
Serial Number
The serial number is a unique identifier of the device. Unless altered, this should match what is
shown on the radio’s printed label. For non-Motorola radios, Data Gateways, and Voice Consoles,
this value is always zero.
Physical Serial Number
The physical serial number is a unique identifier of the device. This value is derived from the
hardware IDs of the radio and is used for authentication. For non-Motorola radios, Data Gateways,
and Voice Consoles, this value is always zero.
Device ID
The Device ID is the radio ID of the Subscriber Access Control entry. A Motorola Radio, Non-
Motorola Radio, Console (Voice Application), and Data Gateway all have radio IDs.
Enabled on System
The enabled on the system checkbox enables and disables the device from gaining access to the
system.
Radio Queue Priority
The Queue Priority is the priority of a radio (or console) in the call queue. The priority range for a
radio is 1 (highest) to 10 (lowest). See Call Priority Optimization on page 168 for more information on
radio queue priority and its interaction with talkgroup queue priority.
Allowed Sites
A radio can only register at the Allowed Sites and therefore the radio can only initiate or receive a call
at the specified sites.
Some sites may not be allowed due to technical reasons such as a frequency band difference. Other
reasons may be due to an administrative or operational arrangement which requires some radios to
never register at a site. Any site allowed here must be included in the Capacity Max Site Selection
list of the radio.
By default all sites are allowed.
Telephone Gateway Site
The Telephone Gateway Site should be set to the Site ID of the Phone Application’s VRC Gateway.
Voice Recording Site
The Voice Recording Site should be set to the Site ID of the Voice Recorder’s VRC Gateway.
Controlling the ability to Initiate particular Call Types
The ability to initiate the following call types can be enabled or disabled per SAC entry by checking
or unchecking the box.
• Group Data Call
• Individual Data Call
96 Send Feedback
MN002731A01-A
• Group Voice Call
• Broadcast Voice Call
• Individual Voice Call
• Multi-Site All Call
• Site All Call
• Telephone Call
• Emergency Call
• Short Data Call
Controlling the Ability to Initiate a Particular Command and Control Messages
The ability to initiate the following call types can be enabled or disabled per SAC entry by checking
or unchecking the checkbox.
• Remote Monitor
• Call Alert
• Radio Check
• Voice Interrupt
• Initiate Stun/Revive
Receive Call Types
The ability to receive the following call types and commands can be enabled or disabled per SAC
entry by checking or unchecking the check box.
• Receive Telephone Call
• Receive Remote Monitor
• Receive Stun/Revive
Creating New Allowed Sites Lists

Procedure:
3 From the Allowable Sites list, select Edit.
A popup dialog appears.
4 Right click under the Allowed Site List section and select New RF Site Selection, New Gateway
Site Selection, or Delete.
If New RF Site Selection is selected, an entry for “Allowed RF Site” is created.
Send Feedback 97
MN002731A01-A
5 To rename the “Allowed RF Site”, double click on the entry and rename to a more appropriate name.
Some examples of ‘Allowed RF Sites” may be UHF Sites, Chicago Sites, St. Louis Sites, Northern
Sites, Southern Sites, Maintenance Sites, Tactical Sites, and others.
Voice Application’s radio IDs can be allowed at the VRC Gateway sites that the voice application is
using. The data gateway’s radio ID can be allowed at the data gateway’s site ID.
6 Select the sites from the Available Sites.
7 To move them to the Selected List, click Add. Click Save.
The “Allowed RF Site” appears in the Allowed Sites dropdown menu for easy selection for other
SAC entries.
Talkgroup Site Association

Radios affiliate their selected primary talkgroup on power up, channel change, and site change. Once a
radio has affiliated a talkgroup at a site, group calls for that talkgroup are routed to the site. The
talkgroup to site association controls which sites a talkgroup should always be streamed to regardless of
affiliation, and which sites a talkgroup is allowed at. For voice and data applications, talkgroups must be
configured to always stream to the corresponding VRC or Data gateway site. See MNIS Data Gateway
Configuration on page 125 and MNIS VRC Gateway Configuration on page 118 for more details.
It is not advised to select to always stream talkgroup calls to a large number of sites since this increases
the number of channel resources required for one call (such as sites per PTT), which decreases system
efficiency and ultimately raises how often a radio user experiences a queuing tone. Normally, calls are
only routed to sites that have at least one radio that affiliated the talkgroup.
Talkgroups in a radio’s receive list are not affiliated. Therefore selecting always stream for that talkgroup
at a site may be required if no other radio usually affiliates that talkgroup.
If reverting to a dedicated emergency talkgroup, that talkgroup must be configured to always stream to
RF sites and gateways. Emergency revert talkgroups are not affiliated on power up, channel change, or
on roam.
Configuring the Talkgroup Site Association

Procedure:
3 Select Talkgroup Site Association.
5 Select the number of talkgroup records to add.

NOTE
NOTICE:
This is not the Talkgroup ID. Entering a large number of records to add may take a few
minutes to complete.
98 Send Feedback
MN002731A01-A
Talkgroup Site Association Parameters

Talkgroup ID
This is the Talkgroup ID of the talkgroup. The Talkgroup IDs must match those entered in the radio
configuration’s address book. See Talkgroup Identifier Assignments on page 35 for more details.
Allowed Sites
The default setting has the “<All Sites>” option selected, which means all sites are allowed, but none
are streamed.
Talkgroup Queue Priority
The Queue Priority is the priority of a talkgroup in the call queue. The priority range for a talkgroup is
1 (highest) to 10 (lowest). See Call Priority Optimization on page 168 for more information on
talkgroup queue priority and its interaction with radio queue priority.
Creating New Talkgroup Allowed Sites

Procedure:
3 Select Talkgroup Site Association.
4 From the Allowed Sites list, select Edit.
A popup dialog appears.
5 Right click under the site selection label and select New Allowed Sites List.
6 To rename the “Allowed Site List”, double click on the entry and rename to a more appropriate name.
Some examples of an ‘Allowed Site List” may be Admin Sites, Mainenance Sites, Tactical Sites,
Customer X Sites, Customer Y Sites, and others.
7 For each site in the list, select if the talkgroup is ‘Allowed’, and then if it should ‘Always Stream’.
The “New Allowed Site List” appears in the Site Selection dropdown menu for easy selection for
other Talkgroup entries.
Trunking Repeater Configuration

This section attempts to identify the minimum configuration required to get a repeater configured and
functional on a Capacity Max system. This section assumes that a Capacity Max System set has
already been created and configured. This configuration can be found from the Manage Sets menu.
This set is referenced while creating a radio configuration. This set is shared by infrastructure and
radios. See System Parameter Configuration on page 78 for more details.
Send Feedback 99
MN002731A01-A
Adding the Repeater into Radio Management

Procedure:
1 From the Radio View screen (radio icon), click the Add icon (star).
2 Enter the serial number.
Only the serial number is required at this time. The other identifiers can be updated later through the
list in the Radio View screen.
Scheduling a Repeater Read

Procedure:
1 From the Radio View screen (radio icon), highlight the newly added repeater.
2 Click the Schedule icon (orange clock).
The Schedule Job window appears.
3 Select the job type as Read.
4 Click Generate a configuration and Apply to radio options.
Each repeater rquires a unique configuration.
5 Select the connection method as USB.
6 In the Job Name field, enter a meaningful job name.
7 Connect the specified repeater to the device programmer through the USB. Click OK.
Upgrading the Repeater Firmware

It may be necessary to upgrade the firmware of the repeater. If the current firmware does not support
Capacity Max, the configuration of Capacity Max features may not be available. The upgrade package
must be installed and then imported into Radio Management.
Steps 1 through 4 are to import the upgrade package, which only needs to be performed once. Steps 5
and 6 are to upgrade the repeater to the upgrade package, which has to be performed for every
repeater.
Procedure:
2 From the dropdown menu, select Manage  Firmware.
4 Select the upgrade package that was installed. Click Import.
5 From the Radio View screen (radio icon), highlight the newly added repeater, right click and select
Upgrade Firmware.
100 Send Feedback

MN002731A01-A
6 Select the appropriate firmware.
The firmware, configuration, and licenses can all be written to the repeater in one write job.
Therefore it is recommended to wait until the configuration and licensing is complete before
scheduling a write job.
Entering the Licenses for the Repeater

The licenses for the repeater must be entered.
Procedure:
2 From the dropdown menu, select Manage Licenses Radio Licenses.
The results section displays all the features in the license, the amount purchased, the amount
5 Select the appropriate features.
6 Select the repeater to apply the feature to the Available Radios list.
7 Click the Add icon (star) to move the repeater to the Selected Radios list.
8 Click Register.
features.
Editing the Repeater Configuration

After a repeater is read and optionally upgraded, the repeater’s configuration must be edited.
NOTICE:
Some repeaters (non-SLR) may need to be upgraded in CPS (Not RM) if they are not in at a
firmware that is Capacity Max capable.
Procedure:
1 From the Radio View screen (radio icon), highlight the repeater.
2 Right click and choose Edit Configuration.
The repeater’s configuration view is displayed.
Send Feedback 101

MN002731A01-A
Capacity Max Repeater Configuration Parameters

A repeater configuration consists of numerous configurable options. A repeater can operate on many
system types as well: Analog, Capacity Plus, IPSC, and others. This section only identifies those
parameters important to Capacity Max. In addition, there are some fine tuning parameters. This section
assumes that the default values for these parameters are acceptable and therefore does not address
them here.
There are various folders under the repeater configuration, and categories under the folders. The
following discusses the parameters under each category and folder important to Capacity Max. Note
that folders and categories not listed are either not applicable to Capacity Max, or default values are
acceptable. Create a New Set, or select an Existing Set in the categories that require configuration.
General
These are general high level radio wide parameters; therefore, there are very few Capacity Max
specific parameters. The following are some specific parameters to consider:
General Settings
All the parameters within the category can remain default with the exception of power level and
CWID. Configure the power and CWID parameters.
Accessories
There are no parameters for accessories that need to specifically be updated.
Security
If utilizing privacy services (encryption), configure the Privacy Type field to Enhanced. Restricted
Access to System (RAS) is not applicable to Capacity Max system.
Link Establishment
There are no parameters that need to specifically be updated in the Link Establishment category
for a Capacity Max system.
Network
Disable DHCP. Capacity Max does not use DHCP.
Enable IP Repeater Programming. Programming the repeater remotely through Radio

Management is not possible if not enabled.
Talkgroups
There are no parameters that to be updated in the Talkgroups category.
Capacity Max Features
The specific Capacity Max parameters are contained within this folder. This section assumes that a
Capacity Max System Set has already been created and configured. These can be found from the
Manage Sets menu. These sets are shared by infrastructure and radios. See System Parameter
Capacity Max Systems
A Capacity Max System set should have already been created from the Manage Sets menu.
Therefore instead of adding a new set, the existing set should be referenced. The Capacity Max
System set is where all system parameters, channel plan, sites, and channels were configured.
102 Send Feedback

MN002731A01-A
Zone/Channel Assignment
The zone/channel assignments allow the system administrator to add a personality and change the
way the repeater functions.
Zone
Select the zone and provide an appropriate zone name.
Personality
Create a new channel/personality; select a personality type of Capacity Max Trunking. Edit the
newly added personality. The following parameters should be configured:
General
Provide an appropriate personality name.
The Repeater RSSI threshold can be adjusted for desired level at which interference is detected.
Select the BSI Mode. Recommendation is to select digital BSI when permitted by regulatory
authorities.
Capacity Max supports digital or analog Base Station Identifier (BSI) transmission. Digital BSI is
transmitted on the slot2 of the repeater. For digital BSI, configuring the ID and TX Interval fields
in the CWID section is sufficient. Selection of analog or digital BSI is done in the Capacity Max
personality.
Digital BSI has the following advantages over analog BSI (CWID):
• Slot1 of the repeater is available for normal communication when digital BSI transmission is
in progress on the slot2.
• The transmission duration of digital BSI for a given ID is less than the analog BSI (CWID)
transmission duration. This increases the slot2 availability for normal communication.
RX/TX
Set the required power level in the TX section.
Capacity Max System
Select the previously defined Capacity Max System.
Select the site at which this repeater is to be deployed.
Select the Capacity Max channel/personality of this repeater.
Transmit and Receive frequencies, color code, trunk/data revert selection, and control
channel selection are defined when the Capacity Max Channel is created in the Capacity Max
System Set.
NOTICE:
Only one Capacity Max personality is allowed on the repeater. If a new Capacity Max
personality is required, the existing personality has to be deleted.
If the zone already contains channels/personalities of other system types (such as

Digital, Capacity Plus Voice, and others), Capacity Max personality is added at the
bottom. Use Up button to move the Capacity Max personality to the top position.
Send Feedback 103

MN002731A01-A
Setting the Device ID

Every repeater at a site must be configured with a unique Device ID. Set the first repeater with a device
ID of one, the second ID of two, and so forth. The derived IP addresses of the repeaters are based off of
the Device IDs. See Understanding IP Addressing on page 15 for more details.
Procedure:
1 From the Radio Systems View screen (antenna icon), highlight the newly added repeater and enter
a unique Device ID.
Setting an Alias and Radio IP for a Repeater

An alias helps identify the repeaters in the list. A unique Radio IP must be assigned to each repeater. A
unique Radio IP (the USB IP address of the repeater) provides the ability to program more than one
repeater through the USB at a time. The Accessory IP automatically changes when the Radio IP is
changed.
Procedure:
1 From the Radio View screen (radio icon), highlight the newly added repeater and enter a unique
Radio IP and Radio Alias.
Analyzing the Repeater

If there are any errors with a repeater configuration, the configuration write will fail. Every repeater
should be analyzed prior to writing and all errors must be resolved.
Procedure:
2 Right click and select Analyze.
3 Select the blue Analyze Results tab in the lower left corner.
4 If there are any errors indicated, read the description and double click on the item in the list.
The configuration field that has the error appears. All errors must be resolved before a write job
succeeds.
Scheduling a Repeater Write

Procedure:
2 Click the Schedule icon (orange clock). Specify the job type as a Write and the connection method
of the USB.
3 Connect the specified repeater to the device programmer through the USB.
The device programmer programs the firmware, configuration, and licenses into the repeater.
104 Send Feedback

MN002731A01-A
Trunking Subscriber Configuration

This section attempts to identify the minimum configuration required to get a radio configured and
functional on a Capacity Max system. This section assumes that a Capacity Max System set, Capacity
Max Site Selection set, and a Capacity Max Radio Wide Features set have already been created and
configured.
These can be found from the Manage Sets menu. These sets are referenced while creating a radio
configuration. These sets are shared by infrastructure and radios. See the section on System Parameter
Adding the Radio to Radio Management

Procedure:
2 Enter the serial number.
Only the serial number is required at this time. The other identifiers can be updated later through the
list in the Radio View screen.
Scheduling a Radio Read

Procedure:
2 Click the Schedule icon (orange clock).
The Schedule Job window appears.
3 Select the job type as Read.
4 Click Generate a configuration and Apply to radio options.
If this is the first radio of a particular model, version, and options, then click Generate a
configuration. This can act as the base configuration for this particular MVO (Model, Version
Options). If you don’t have a default configuration for a MVO, then create one from this radio.
5 Select the connection method as USB.
6 In the Job Name field, enter a meaningful job name.
7 Connect the specified repeater to the device programmer through the USB. Click OK.
Send Feedback 105

MN002731A01-A
Upgrading the Radio Firmware

It may be necessary to upgrade the firmware of the radio. If the current firmware does not support
Capacity Max, the configuration of Capacity Max features may not be available. The upgrade package
must be installed and then imported into Radio Management.
Steps 1 through 4 are to import the upgrade package, which only needs to be performed once. Steps 5
and 6 are to upgrade the radio to that upgrade package, which has to be performed for every radio.
Procedure:
2 From the dropdown menu, select Manage Firmware.
4 Select the upgrade package that was installed. Click Import.
5 From the Radio View screen (radio icon), highlight the newly added radio. Right click and select
Upgrade Firmware.
6 Select the appropriate firmware.
The firmware, and configuration, and licenses can all be written to the radio in one write job.
Therefore it is recommended to wait until the configuration and licensing is complete before
scheduling a write job.
Entering the Licenses for the Radio

The licenses for the radio must be entered.
Procedure:
2 From the dropdown menu, select Manage Licenses Radio Licenses.
5 Select the appropriate features.
6 Select the radio to apply the feature to in the Available Radios list.
7 Click the Add icon (star) to move the radio to the Selected Radios list.
8 Click Register.
features.
106 Send Feedback

MN002731A01-A
Editing or Selecting a Radio Configuration

After a radio is read, the radio configuration must be edited or selected.
Editing a Radio Configuration

After a radio is read, the radio’s configuration must be edited, if a configuration was generated from
reading a radio.
Procedure:
1 From the Radio View screen (radio icon), highlight the radio.
2 Right click and select Edit Configuration.
The radio’s configuration view is displayed.
Selecting a Radio Configuration

If a radio configuration was previously created, the configuration can be selected by performing the
following:
Procedure:
2 Right click and select Select Configuration.
3 Select the desired radio configuration from the list.
Capacity Max Radio Configuration Parameters

A radio configuration consists of numerous configurable options. A Capacity Max radio can operate on
numerous system types as well: MDC, 5 Tone, Capacity Plus, IPSC, and others. This section only
identifies those parameters important to Capacity Max. In addition, there are many fine tuning of timers,
tones, buttons, menus, and others. This section assumes the default values for these options are
acceptable and therefore does not address them here. Other sections may address the fine tuning of
system level timers, and online help addresses tones, buttons, menus, and others.
There are various folders under the radio configuration, and categories under the folders. The following
discusses the parameters under each category and folder important to Capacity Max. Folders and
categories not listed are either not applicable to Capacity Max, or default values are acceptable. Create
a New Set, or select an Existing Set in the categories that require configuration.
General
These are general high level radio wide parameters; therefore, there are very few Capacity Max
specific parameters. The following are specific parameters to consider:
General Settings
All the parameters within the category can remain default with the exception of one parameter.
The GPS checkbox should be checked when the radio utilizing this configuration utilizes its GPS.
Send Feedback 107

MN002731A01-A
Control Buttons
The button configuration of a radio is highly dependent on the end user’s needs. A typical button
configuration may have an Emergency Button, High/Low power, Backlight, amongst many
others. Selection of conventional functions such as Scan, Monitor, and Talkaround can be
removed as they are unnecessary if the radio is only operating in a Capacity Max system. If the
radio is operating in conventional systems as well, then these functions can remain.
Three button functions to consider for Capacity Max are:
• Site Alias
• Site Lock
• Manual Site Roam
These are helpful to technicians when troubleshooting roaming during initial system testing. In
general, the radio should automatically select the appropriate site. It might not be appropriate to
allow users to have manual control over site roaming. Viewing the Site Alias may be useful to
some radio users that need to understand which site they are at.
Security
If utilizing privacy services (encryption), the privacy or symmetric keys should be referenced
here. Keys and their key values should have already been added to the key kettle through the
Manage menu. Reference the keys this radio needs for receiving communications here.
Network
There are no parameters that need to specifically be updated in the network category for a
Capacity Max system. Bluetooth connections can be configured here if being utilized. The
Battery Management Server ID can be set here if being utilized on the system. User defined UDP
ports can be set for advanced data applications. An ARS Radio ID (the automatic registration
service ID) need not be set for Capacity Max.
Contacts
This is where the address book (the contact list) for the radios utilizing the configuration is
configured.
A contact type can be Five Tone, MDC, Quick-Call II, Digital, Capacity Plus, or Phone entry. Capacity
Max utilizes the contact type of Digital.
Capacity Max (Digital) supports the following contact call types: Group Call, Private (Individual) Call,
Dispatch, PC, Site All Call, and Multi-Site All Call. Capacity Max does not currently support All Call
(All System Call).
Capacity Max Features
The specific Capacity Max parameters are contained within this folder. Their explanation is below.
This section assumes that a Capacity Max System set, Capacity Max Site Selection set, and a
Capacity Max Radio Wide Features set has already been created and configured. These can be
found from the Manage Sets menu. These sets are shared by infrastructure and radios. See
System Parameter Configuration on page 78 for more details.
Capacity Max Radio Wide Features
A Capacity Max Radio Wide Features set should have already been created from the Manage 
Sets menu. Therefore instead of adding a new set, the existing set should be referenced. All
parameters in the set may remain default.
108 Send Feedback

MN002731A01-A
Capacity Max Systems
A Capacity Max System set should have already been created from the Manage Sets menu.
Therefore instead of adding a new set, the existing set should be referenced. The Capacity Max
System set is where all system parameters, channel plan, sites, and channels were configured.
Capacity Max Emergency Systems
If emergency is supported in the system, it is configured here. See the section on “Capacity Max
Emergency Handling” for more information on configuring Emergency operation in Capacity Max.
The emergency contact name must be added to the contact list prior to selecting it here. The
emergency system set is referenced from the desired personality during the Zone/Channel
Assignment configuration.
Flexible Capacity Max RX Group List
If enabled through the menu, the radio user can add or remove talkgroups from a radio wide
flexible receive talkgroup list (RX Group List). These are in addition to the talkgroups in the digital
receive group list configured per personality, which is uneditable by the radio user. In most cases
the flexible receive talkgroup list remains empty by default and allows the radio user to populate
when necessary.
Capacity Max Site Selection
A Capacity Max Site Selection set should have already been created from the Manage Sets
menu. Therefore instead of adding a new set, the existing set should be referenced. The site
selection set contains the sites that radios with this configuration have access to.
RX Group Lists
The Capacity Max RX group list is configured in the Digital RX group list.
Digital RX Group List
If a personality needs to monitor more than one talkgroup at a time, the talkgroups need to be
added to a RX Group List. The RX Group List is referenced from the desired personality during
the Zone/Channel Assignment configuration.
Zone/Channel Assignment
The zone and channel assignments allow the radio user to change the way the radio functions. The
radio user can select between predefined radio personalities through a knob, a button, or menu.
Personalities can be separated into zones for categorization and organization. In a trunking system
such as Capacity Max, typically the difference between personalities is the talkgroup the radio user
is utilizing. But there are numerous configurable parameters within a personality that allow a variety
of control to be provided to the radio user. The name provided to the zone and the personality should
help the radio user understand the configuration of the personality within that zone.
Zone
Create a new zone, select a zone type of “Normal”, and provide an appropriate zone name.
Personality
Create a new personality; select a personality type of “Capacity Max Trunking”. Edit the newly
added personality. The following parameters should be configured:
Send Feedback 109

MN002731A01-A
General
Provide an appropriate personality name. The personality name is displayed when the radio
user selects this personality. Enable privacy and select a transmission key if encryption is
desired for this personality.
RX/TX
Set the Contact Name to the primary talkgroup for this personality. This is the transmit
talkgroup when the user presses the PTT. Select the previously defined Emergency System.
It’s recommended to keep the default In Call Criteria as Polite.
Capacity Max System
Select the previously defined Capacity Max System.
Create additional Personalities, and additional Zones with additional Personalities.
Adding a Radio Contact

Procedure:
2 Right click and select Edit Configuration.
3 Select Contacts.
4 To add a contact, right click and select Create New Set. Specify a unique contact alias.
5 To add a Capacity Max contact, click the Add (star) icon next to the Digital (Capacity Max) label, and
then select the type (Group Call, Private Call, and others).
If there is already a digital entry for a contact of a particular call type, it must be deleted first and then
the new digital entry can be added.
6 Specify a unique Call ID. See the section on Radio Identifier Assignments on page 34 and Talkgroup
Identifier Assignments on page 35. Specialized tones can also be selected if desired.
Setting the Radio ID and Radio Alias

Every radio at a site must be configured with a unique Radio ID. The derived IP addresses of the radios
are based off of the Device IDs.
A unique Radio IP must be assigned to each radio. A unique Radio IP (the USB IP address of the radio)
provides the ability to program more than one radio through the USB at a time. The Accessory IP
automatically changes when the Radio IP is changed. See Radio Identifier Assignments on page 34 for
more details.
A unique Radio Alias should be assigned to each radio. The Radio Alias helps identify the radios in the list.
Procedure:
1 From the Radio View screen (radio icon), highlight the newly added radio and choose a unique
Radio ID and Radio Alias.
110 Send Feedback

MN002731A01-A
Analyzing the Radio

If there are any errors with a radio configuration, the configuration write will fail. Every radio should be
analyzed prior to writing and all errors must be resolved.
Procedure:
1 From the Radio View screen (radio icon), highlight the newly added radio.
succeeds.
Scheduling a Radio Write

Procedure:
1 From the Radio View screen (radio icon), highlight the newly added radio.
2 Click the Schedule icon (orange clock). Specify the job type as a Write and the connection method
of the USB.
3 Connect the specified radio to the device programmer through the USB.
The device programmer programs the firmware, configuration, and licenses into the radio.
Capacity Max System Server (CMSS) Configuration

The Capacity Max System Server (CMSS) is a HP ProLiant DL380 Gen9 server, which runs a set of
virtual machines. Each virtual machine has its own operating system and a hypervisor (VMware ESXi)
provides a virtual operating platform to an operating system of a virtual machine. The virtual machines
run a set of appliances.
Send Feedback 111

MN002731A01-A
Figure 28: HP ProLiant DL380 Gen9 Capacity Max System Server
The following appliances are pre-installed on the CMSS in the factory:
• Trunking Controller. This appliance manages the overall operation of the Capacity Max system.
• MNIS Voice and Radio Command (VRC) Gateway. Authorized voice applications interact with the
Capacity Max radio system through the VRC Gateway.
• System Advisor. The user can monitor the health of the Capacity Max radio system with the System
Advisor.
• ESU. The user carries out maintenance tasks related to the CMSS using ESU.
Ethernet Port Configuration

The CMSS physically has nine Ethernet ports in the back:
• Ports 1 through 4 are directly connected to the main motherboard.
• Ports 5 through 8 are connected through an HP FlexibleLOM adapter.
• A port is dedicated to the HP Integrated Lights-Out (iLO) module. The port can optionally be used to
remotely manage the server in an Enterprise environment. The port also supports hardware
management functionalities that may be helpful in diagnosing hardware issues. See the HPE iLO 4
User Guide (http://www8.hp.com/us/en/products/servers/ilo/resources.html) for additional
information regarding the iLO.
112 Send Feedback

MN002731A01-A
Figure 29: HP ProLiant DL380 Gen9 Capacity Max System Server Ethernet Ports
The CMSS’s Ethernet ports are configured into active/standby pairs as depicted in the above diagram.
For example, ports 1 and 5 are paired together, with port 1 being the active port, and port 5 being the
standby port. The standby port may optionally be connected to a second network switch to provide some
level of link layer redundancy. The standby port may be left unconnected if such redundancy is not
required.
As indicated in the diagram, ports 1/5 are shared by the ESXi, System Advisor and ESU. To ensure
optimal system performance, ports 2/6 are dedicated to the Trunking Controller, and ports 3/7 are
dedicated to the VRC Gateway. Ports 4/8 are reserved for future use.
IP Configuration
When shipped from the factory, the CMSS is pre-configured with the following IP addresses:
Table 28: Capacity Max System Server IP Addressess
Virtual Applicance Address
Trunking Controller 172.20.36.1
ESXi 172.20.36.2
Send Feedback 113

MN002731A01-A
Table 28: Capacity Max System Server IP Addressess (Cont.)
Virtual Applicance Address
ESU 172.20.36.3
VCR Gateway 172.20.36.4
System Advisor 172.20.36.5
The base address (or subnet address) of the CMSS is configurable within Radio Management. It comes
pre-configured as 172.20.36.0. The IP addresses of all the virtual appliances maintain the same fixed
offset from this base address as shown in Table 28 on page 113. Radio Management (RM) uses the
Trunking Controller address to communicate with the CMSS. If the base address is changed using RM,
it automatically updates the IP addresses of all the CMSS virtual appliances to ensure that they always
maintain the same offsets from the new base address.
The current address assigned to the virtual machines can always be determined based on knowledge of
this fixed IP allocation plan and what is currently displayed on the CMSS console. When the system is
running, the hypervisor always displays the IP address allocated to the ESXi. The IP addresses of other
virtual appliances from the ESXi address can be derived using Table 28 on page 113. For example,
suppose the console indicates that the IP address of the ESXi is 10.22.36.2. From Table 28 on
page 113, the IP of the Trunking Controller is always 1 less than the ESXi, or in this case, 10.22.36.1.
The CMSS is configured with an internal network for internal communications between the virtual
appliances. The factory default IP address of this internal network is 192.168.231.0/24. Since this
network is completely internal to the CMSS, it is not directly exposed outside of the box and the default
setting normally does not need to be changed. However, one consequence is that if there happens to be
any other entity in the IP network allocated to that same IP address, it can not directly communicate with
any of the CMSS virtual appliances. In this case, the IP address of this internal network can be changed
using RM.
Adding the CMSS to Radio Management

Procedure:
2 Enter the CMSS’s Serial Number and a Radio Alias such as “Primary Controller” Click OK.
The other fields: Radio ID, CAI, Radio IP, and Region can be left blank.
The serial number entered for the CMSS must be the actual serial number of the CMSS, as this is
verified while writing to the CMSS. There is a label on top of the CMSS hardware that indicates its
Serial Number.
3 Highlight the added CMSS device and right click. Select MVO.
4 In the pop up window, select Create Infrastructure Device.
5 Select Product Family to Capacity Max System Server.
6 Select the appropriate Version of the CMSS.
114 Send Feedback

MN002731A01-A
Setting the IP System for the CMSS in Radio Management

Procedure:
1 From the Radio View screen (radio icon), highlight the newly added CMSS device
2 Right click to select the appropriate IP System Settings.
If not already created, the CMSS should have its own IP System Settings created. The IP System
Settings is used by Radio Management to communicate with the system when a read or write is
scheduled for CMSSs. The Trunking Controller IP is the only parameter required.
The IP System Settings used by the Primary CMSS should use the IP address of the primary
Trunking Controller. The IP System Settings used by the Alternate CMSS should have a separate IP
System and use the IP address of the alternate Trunking Controller.
Adding a CMSS Configuration in Radio Management

Procedure:
2 From the dropdown menu, select Manage  Configuration.
3 Select Add a Configuration.
4 Select a Product Family of Capacity Max System Server.
Configuring the Capacity Max Features

Procedure:
1 From the Configuration view, right click on the newly added CMSS configuration and select Edit.
2 Select Capacity Max System, right click and select an existing set.
3 Select the previously created Capacity Max System Set.
More information about the system set can be found in System Parameter Configuration on page 78
4 Select Capacity Max Site Selection, right click and select an existing set. If utilizing an MNIS VRC
Gateway, then select the site selection list that contains the MNIS VRC gateway site created during
the system set configuration.
5 Select Network, the network settings for the CMSS are displayed.
If using one of the common system configurations discussed in Chapter 30,“Common System
Configurations and Recommended IP Plans”, then the following settings should be used:
• CMSS IP = 172.20.36.0
• CMSS UDP Port = 50000
• CMSS Internal Network = 192.168.231.0
• Gateway IP = 172.20.36.20
• Gateway Netmask = 255.255.255.128
Send Feedback 115

MN002731A01-A
• NTP Server = 0.0.0.0
If utilizing a redundant CMSS, the following settings should be used:
• CMSS IP = 172.20.37.0
• CMSS UDP Port = 50000
• CMSS Internal Network = 192.168.231.0
• Gateway IP = 172.20.37.20
• Gateway Netmask = 255.255.255.128
• NTP Server = 0.0.0.0
The CMSS UDP Port and CMSS Internal Network should almost always remain default.
6 Optional: If the network is equipped with an NTP server, enter the IP address here. However, it is not
required.
See Understanding IP Addressing on page 15 and Chapter 30, “Common System Configurations
and Recommended IP Plans” for more details on the IP addresses of the CMSS.
As explained earlier, the IP addresses of all the virtual appliances maintain the same fixed offset
from the configured base address. They are shown here in Radio Management for reference.
MNIS
Under the MNIS item is where to find the settings for the MNIS VRC gateway, which is a virtual
appliance on the CMSS. Details on setting these parameters can be found in MNIS VRC Gateway
The majority of these parameters need not to be updated with the exception of VRC Gateway Enabled
checkbox and the Active Voice Talkpath Limit (under the MNIS System). The active voice talkpath limit
must be set to the number of talkpath licenses purchased for the system. If the VRC Gateway is
enabled, then a Capacity Max Site Selection set is required.
Selecting the Configuration for the CMSS Device

Procedure:
1 From the Radio View screen (radio icon), highlight the newly added CMSS
2 Select the Select Configuration item.
3 Select the newly created CMSS Configuration.
116 Send Feedback

MN002731A01-A
Setting the Device ID and Redundancy Group

Procedure:
1 From the Radio System View screen (antenna icon), highlight the newly added CMSS and select a
unique Device ID.
Every CMSS in the system must be configured with a unique Device ID. The redundancy group of
the Primary CMSS should be primary and the Alternate CMSS should be alternate.
Scheduling a CMSS Read

Before licensing the CMSS, it must be read one time to retrieve needed information.
Procedure:
1 From the Radio View screen (radio icon), highlight the newly added CMSS and click the Schedule
icon (orange clock).
2 Specify the job type as a Read, and the connection method of IP.
Licensing the CMSS

The licenses for the CMSS must be entered.
Procedure:
2 From the dropdown menu, select Manage  Licenses Capacity Max Server Licenses.
available, and a quantity field. The following items are licensed in the CMSS:
• Capacity Max Data Gateway
• Capacity Max Trunked Controller
• Capacity Max Site
• Capacity Max System Advisor
• Capacity Max System Advisor NBI
• Capacity Max VRC Gateway
• Capacity Max VRC Gateway Single Talkpath
5 In the Quantity field, enter the number of each feature to register.
Some features can only be registered once; as there is only one per CMSS.
6 Select the CMSS to apply the features.
Send Feedback 117

MN002731A01-A
7 Click Register.
features.
Analyzing the CMSS

If there are any errors with a CMSS configuration, the configuration write fails. Every CMSS should be
analyzed prior to writing and all errors must be resolved.
Procedure:
1 From the Radio View screen (radio icon), highlight the newly added CMSS .
succeeds.
Scheduling a CMSS Write

Procedure:
1 From the Radio View screen (radio icon), highlight the newly added CMSS and click the Schedule
icon (orange clock).
2 Specify the job type as a Write, and the connection method of IP.
The configuration and licenses are written into the CMSS.
MNIS VRC Gateway Configuration

This section identifies the minimum configuration required to get a MNIS VRC gateway configured and
functional on a Capacity Max system. This section assumes the following high level tasks are already
completed prior to configuration of the VRC gateway:
• Capacity Max MNIS VRC gateway license is enabled in the RM.
• If the VRC gateway license is supporting voice calls, then Capacity Max MNIS VRC talkpath license
is enabled. Without talkpath licenses, the gateway supports only Radio Commands.
• The Capacity Max System set is configured in Radio Management (RM). See System Parameter
• Identify the talkgroups that are to be utilized by each VRC gateway (for dispatch, group voice
recording, or group phone calls).
• If a voice recorder application(s) is using the VRC gateway, then identify the radios whose individual
voice call is to be recorded by the application.
• If a phone application(s) is using the VRC gateway, then identify the radios whose individual phone
calls are to be served by the application.
118 Send Feedback

MN002731A01-A
The VRC gateway resides in the CMSS. The following TC and VRC gateway configurations are
possible:
Table 29: TC and VRC Gateway Configurations
TC MNIS Voice Comments
Primary none Capacity Max VRC Gateway Talkpath license is enabled on the CMSS
with the TC. Capacity Max VRC Gateway License is enabled on the
Alternate none CMSS with the VRC Gateway.
Primary Primary Capacity Max VRC Gateway and Talkpath license are enabled on the
CMSS.
Alternate Alternate
Primary Alternate Not Supported.
Alternate Primary Not Supported.
none Primary Capacity Max VRC Gateway Talkpath license is enabled on the CMSS
with the TC. Capacity Max VRC Gateway License is enabled on the
none Alternate CMSS with the VRX Gateway.
Adding a MNIS VRC Gateway

Typically, the VRC gateway resides on an existing CMSS (primary or alternate). If a VRC gateway is not
residing on the existing CMSS, then a new CMSS must be added and configured. Perform the
procedures in Capacity Max System Server (CMSS) Configuration on page 111 for information on
adding a CMSS into Radio Management.
Procedure:
1 On an existing CMSS, right click on the CMSS Configuration view and select Edit.
Configuring a MNIS VRC Gateway

Procedure:
1 Under the CMSS Configuration view, select the MNIS folder and perform the following:
a Select MNIS System.
1) In the VRC Gateway Enabled checkbox, select if the CMSS has a VRC Gateway. If
unselected, the Site Selection List in the Capacity Max Features is not required.
2) In the MNIS Gateway UDP Port field, leave it to the default setting.
This field represents the UDP port used by the VRC gateway. The assigned UDP port, UDP
Port + 1 and UDP port + 2 are used by the VRC gateway for communication with Capacity
Max infrastructure.
3) In the Transmission TOT field, set the transmission time-out-timer.
4) In the Active Voice Talkpath Limit field, enter the number of voice calls the VRC gateway is
to support concurrently.
The number should not be greater than the VRC Gateway Talkpath license or ‘VRC Gateway
Active Talkpath Max Capacity’ whichever is lesser.
Send Feedback 119

MN002731A01-A
b Select MNIS Network and right click. Select Create New Set.
1) In the Server TCP Port field, leave it to the default setting.
This field represents the VRC gateway server TCP port.
2) In the Voice UDP Port field, leave it to the default setting.
This field represent the VRC gateway Voice UDP port. Voice packets from the application are
sent/received from this port.
Adding an Alternate VRC Gateway

Perform the following steps to add an alternate VRC gateway to Radio Management as described in
Adding a MNIS VRC Gateway on page 119 and Configuring a MNIS VRC Gateway on page 119.
Procedure:
1 Select the same Site Selection Set as the one selected for the primary VRC gateway.
The alternate gateway site must be same as the ‘primary’ VRC gateway site. All the configurations
under the MNIS folder should be made the same as in the primary VRC gateway.
2 Under the Radio System view (antenna icon), highlight the newly added CMSS and choose a
unique Device ID. Every CMSS in the system must be configured with a unique Device ID. The
redundancy group of the Primary CMSS should be primary and Alternate CMSS should be alternate.
Configuring the Capacity Max System Server Data

The Capacity Max System Server Data is configured to enable routing of the calls to the VRC Gateway
Site. Routing of Group Calls (Group Voice, Group Phone, Group Radio Command – Emergency Alarm),
Individual Voice Call, Individual Phone Calls and Individual Voice Calls for recording is done in this
configuration. Whenever possible the configuration can be done while adding talkgroups and radios to
the server data. This avoids any extra steps of adding the changes for the VRC gateway later. The VRC
Gateway is configured before adding the talkgroups and radios to the server data. Perform steps to
configure the Capacity Max System Server Data for the VRC Gateway.
Procedure:
1 Talkgroup affiliations from the VRC gateway cannot be done dynamically, rather it is configured in
Radio Management. If the application is setup to receive or send group calls, then the Talkgroup
Site Association has to be updated, as follows:
a Select the VRC gateway site to Allowed and Always Stream for the talkgroup.
b Update the other talkgroups that the application uses. Do not update talkgroups which the
application is not using.
2 If the VRC gateway is supporting a Phone or Voice Recording application, then the TC has to know
which VRC gateway the phone or individual voice call from the radio it is routed to. Perform the
following:
a In the Subscriber Access Control (SAC) select the radio and update the Telephone Gateway
Site and the Voice Recording Site to the GW site.
120 Send Feedback

MN002731A01-A
b Update all radios whose phone call or individual voice call is to be routed to the VRC gateway.
NOTE
NOTICE:
Multiple phone and recording applications can be deployed in a Capacity Max System. The
applications can either be supported on the same VRC gateway or separate VRC gateways.
The following restrictions apply.
- A phone call from a radio can be routed to only one designated phone application.
- A phone call to a group can be initiated from one designated phone applications.
- An Individual call from a radio can be routed to only one designated recording application.
Additionally, the VRC gateway routes the individual phone call to the phone application based
on the radio IDs subscribed by the application. The radio IDs are subscribed as range (radio
ID 1 – 5000). Up to 32 ranges can be subscribed by the application. In case of multiple phone
applications are supported by the gateway then the ranges subscribed by the phone
applications must be mutually exclusive.
3 The radio IDs assigned to the voice application (this is typically the radio ID assigned to the dispatch
positions) needs to be provisioned in the SAC. Perform the following:
a Add a Console device type to the SAC.
b Assign a unique device ID to it.
c Select the appropriate permissions for the radio ID.
Since the ID is assigned to a dispatch console, select all the voice and radio command
capabilities. Data calls can be unselected as they are not sent to the VRC gateway. The Queue
Priority of the radio ID can be raised to prioritize calls from the dispatcher over calls from the
radios in the Trunking Controller queue.
d Add all the radio IDs; that are be used by the voice application, to the SAC.
e Select the allowable site to be the VRC gateway site. If there are multiple VRC gateway sites and
the application is connecting with them, then those VRC gateway sites should also be selected
as allowable sites.
4 Ensure that the application has the connection setting to connect with the VRC gateway.
5 If there is an alternate VRC gateway, then configure the connection setting to connect with the
alternate VRC gateway.
6 Ensure that the application is configured to register the groups, radio IDs and phone/recording
registration with the VRC gateway. This should match the configuration in the System Server Data.
Firewall Setting on the MNIS Data Gateway PC Configuration

The firewall must be configured to open the following ports:
• UDP Ports - MNIS LE Port, MNIS LE Port+1, MNIS LE Port+2
• MNIS Voice Server TCP Port MNIS
• MNIS Voice UDP Port
Send Feedback 121

MN002731A01-A
System Advisor Configuration
System Advisor Server Configuration

The System Advisor Server comes from the factory with a predefined IP address and other network
configurations and it is enabled by default.
The network configuration (such as IP addresses, and others) can be changed using Radio
Management (RM). RM sets the base IP address for the Capacity Max System Server (CMSS) and the
IP address of the System Advisor is derived from the base IP. See Understanding IP Addressing on
page 15 to learn how to calculate the System Advisor Server IP address based on the base CMSS IP
address.
If using the common IP plan, the primary System Advisor Server IP address is 172.20.36.5, and the
redundant is 172.20.37.5. See Understanding IP Addressing on page 15 for more information on the
System Advisor Server IP address.
System Advisor Licenses in CMSS

The System Advisor is not functional without being licensed in the CMSS. The following features are
available for the System Advisor:
• General System Advisor feature - without a license for this feature, the System Advisor does not
function.
• Northbound Interface feature – enables the SNMP Northbound Interface functionality.
See Capacity Max System Server (CMSS) Configuration on page 111 for more details.
Starting the System Advisor Client

Make sure the computer meets the minimum specification for System Advisor Client application
described in the Capacity Max Hardware Requirements article, and it has a direct IP connection to the
CMSS and the System Advisor Server.
NOTICE:
The System Advisor Client requires Java be installed. If not already installed, the computer/
laptop may not have access to the internet during installation.
Procedure:
1 Start the System Advisor client by entering the IP address and port of the System Advisor server as
the URL in a web browser:
https://<SA_SERVER_IP>:9090/
A webpage opens that allows starting the client application.
2 Click Launch.
The Java Web Start client is automatically downloaded and started. Later, once all client resources
are downloaded to the local machine, the application can be started by double-clicking on the Java
Web Start jnlp file.
122 Send Feedback

MN002731A01-A
In a redundant CMSS configuration, the provided IP address of the System Advisor server determines
the System Advisor instance the user launches. To start another instance (for example, the first instance
is not reachable due to the network issue), the procedure should be repeated with the IP address of the
other System Advisor server instance.
There may be some security warnings shown depending on the Java security settings or if an expired
version of Java is used. Each Java version has an expiration date and when the date is reached. Java
provides additional warnings and reminders to the users to update to the newer version.
Once the System Advisor client is started, the following configurations are available:
• Outbound Communication Credentials
• System Parameters in System Advisor
• Call Monitoring (ATIA) Port Number
• Language and Data Format
Configuring Outbound Communication Credentials

The configuration of inbound and outbound credentials includes the following:
• Simple Network Management Protocol version 3 (SNMPv3) – Configure Global SNMPv3 Credentials option
• Web Service used to manage CMSS server – Configure Global Web Service Credentials option
• North Bound Interface (NBI) – Configure North Bound Interface option
The System Advisor has a predefined configuration for the above interfaces that matches the default
configuration of the Capacity Max devices.
If the devices were configured with different credentials, appropriate updates must be made.
Procedure:
1 Perform one of the following tasks:
If..... Then.....
For devices managed using SNMPv3 protocol from the main menu Tools  Configure Global
(such as Switches and Routers), the System SNMPv3 Credentials.
Advisor uses a hardcoded MotoMaster user and
noAuthNoPriv security level as default. Change
of the security level is possible in the System
Advisor Client,
For devices managed using Web Service from the main menu, select Tools  Configure
protocol (such as CMSS), the System Advisor Global Web Service Credentials.
uses a hardcoded MotoMaster user and default
password. Change of the Web Service password The MotoMaster user account created on the CMSS
is possible in the System Advisor Client, server is done in the factory, and cannot be changed.
Therefore it should not be changed.
2 The North Bound Interface (NBI) uses the default credentials (MotoNorth user and noAuthNoPriv
security level). To change the security level in the System Advisor Client, perform the following:
a From the main menu, select Tools Configure Global SNMPv3 Credentials.
Automatic discovery of the devices in a system always uses the global configuration; however it is
possible to provide different credentials for each manual discovery session.
Send Feedback 123

MN002731A01-A
Configuring System Parameters in the System Advisor

Automatically discovering the devices with System Advisor requires configuration of the source of
information about such devices (trunking controller address) and additionally some System Advisor
identification parameters (as information about System Advisor presence is also broadcasted to other
devices in the system).
The following parameters need to be configured:
• Network ID
• Device ID
• UDP base port number(defaulted to 65000)
• Trunking Controller IP*
• Trunking Controller port number
* In redundant CMSS configuration, both System Advisors must be configured with the primary Trunking
Controller IP address.
Procedure:
1 From the main menu, select Tools  Configure System Advisor Properties.
2 Once the change is made, restart the System Advisor server.
The command to restart the System Advisor Server is available in the Administration menu.
See Entity Identifier Assignments on page 29 and Radio Identifier Assignments on page 34 for guidance
on setting the identifiers.
Configuring the Call Monitoring (ATIA) Port Number

The System Advisor Server opens a UDP port for incoming call monitoring traffic (ATIA) from repeaters,
trunking controllers, MNIS VRC gateways, and MNIS data gateways. The call monitoring port number
on the System Advisor is defaulted to 51112, but can be changed to another number in the range 49152-
65535.
Procedure:
1 From the main menu, select Tools  Configure System Advisor Properties.
The port number must match the call monitoring (ATIA) destination port number configured on the
devices that are the source of call monitoring traffic (repeaters, trunking controllers, MNIS VRC
gateways, and MNIS data gateways).
124 Send Feedback

MN002731A01-A
Configuring the Language and Date Format

The System Advisor GUI is available in seven languages – EN (default), DE, ES-LA, FR, PT-BR, RU,
ZH-CN.
The language configuration (and accompanying date format) is available in the System Advisor Client.
Procedure:
1 From the main menu, select Administration  Change Language and Date Format.
Discovering Non-Capacity Max IP Plan Devices

Capacity Max devices such as repeaters, trunking controllers, MNIS VRC gateways, MNIS data
gateways, site switches, and routers should be discovered automatically once the configuration of the
system parameters (the trunking controller IP address and others described earlier) are entered. There
may be other devices in the system that do not follow the recommended IP plan, such as some
customer specific devices attached to the system. These devices are not discovered automatically and
must be discovered manually.
Procedure:
1 From the main menu, select Tools  Discovery.
2 Enter the following parameters:
• IP address
• SNMP port
• Site ID if it is a site level device.
The discovery process is successful if the System Advisor recognizes the type of the device as
supported.
The Site ID parameter determines the logical location of the device that is being discovered and is used
when the site ID cannot be retrieved directly from the device (so for all devices other than the repeater).
MNIS Data Gateway Configuration

This section identifies the minimum configuration required to get a MNIS Data Gateway configured and
functional on a Capacity Max system. This section assumes the following steps have been completed
before configuring the MNIS Data Gateway:
• The Capacity Max MNIS data gateway license has been purchased.
• The Capacity Max System set has been configured in the Radio Management (RM).
• If the location application is using enhanced data format, then the latitude and longitude coordinates
of the repeater sites have been configured in Radio Management (RM).
Send Feedback 125

MN002731A01-A
• If the data messages are encrypted, then the encryption keys have been configured in Radio
Management (RM).
• If the data application is receiving group data, then those groups have been configured in Radio
Management (RM)
• The MNIS data gateway is installed.
The MNIS data gateway is assigned a radio ID. This radio ID must be same as TMS Radio ID/XCMP
Server ID/ Battery Management Server ID configured in the radio. The radio uses the MNIS data
gateway’s radio ID to reach the application.
When configuring the data gateway, any non-applicable configurations pertaining to the voice gateway
are left as default. This section only references the data gateway applicable fields.
MNIS Data Gateway Site and Site Selection System Set

In the Radio Management, the MNIS data gateway must be added as a Gateway Site in the Capacity
Max System set. There must also be a Site Selection list that contains the Gateway Site. These steps
should have already been performed when the System Set was created.
The MNIS data gateway is assigned a site ID. The ID of the data gateway site must be unique across
the site IDs of repeaters or voice gateway or any other data gateway.
Adding a MNIS Data Gateway Device

Procedure:
1 In Radio Management, from the Radio View screen (radio icon), click the Add icon (star).
2 Enterthe serial number to a unique alpha numeric number (example DGW1XXXXXX). The rest of
the fields can be left empty.
3 Highlight the added data gateway device and right click to select MVO.
4 In the pop up window, select Create Infrastructure Device.
5 In the Product Family field, select Motorola Network Interface Service.
6 Select the appropriate Version of the MNIS data gateway.
Adding a MNIS Data Gateway Configuration

Procedure:
1 In the Configuration View, add a configuration.
2 In the Product Family field, select Motorola Network Interface Service.
3 Right click on the newly added MNIS Data Gateway Configuration and select Edit. Continue to
configure the fileds, as follows:
4 Select Capacity Max System, right click and select Existing Set. Select the Capacity Max System
set.
5 Select Capacity Max Site Selection. Click the Add icon (star).
126 Send Feedback

MN002731A01-A
6 In the Capacity Max Features section, perform the following:
a Click the Add icon (star).
b Select the Capacity Max System set.
c Select the Sites icon from the system that was just added.
d Click the Add icon (star) and select the Gateway site that was created earlier.
7 MNIS Security can be configured if the MNIS data gateway is receiving encrypted data from the
radios. Perform the following:
a Select MNIS Security, right click and select Copy Set From or Create New Set.
Copy Set From can be used for copying the set from another MNIS data gateway configuration,
otherwise create a new set.
b Add the Enhanced Privacy Keys and/or Symmetric Keys.
The data gateway requires all the keys which the radios are using for sending the data to the
application.
c Basic Privacy is not supported, leave to the default value.
8 Select MNIS System, right click and select Create New Set. Complete the following fields:
a Capacity Max System – select the Capacity Max System set.
b Data Gateway Radio ID – This field represents the data gateway’s radio ID. Enter the data
gateway’s radio ID. See Entity Identifier Assignments on page 29 for more details.
c MNIS Gateway UDP Port – This field represents the UDP port used by the data gateway. The
assigned UDP port, UDP Port + 1 and UDP port + 2 are used by the data gateway for
communication with the Capacity Max infrastructure. Assign a port which does not conflict with
port usage of any other application deployed on the PC.
d High Efficiency Data Enabled – This field is selected when there is a Location data application
or a XCMP data application which is using high efficiency data.
e Data Gateway Queue Size – This field represents the number of data messages from the
application that the gateway queues at a time. The data message remains in the data gateway’s
queue until it has been transmitted to the radio. The default value of the queue size is made for
normal operational condition. If the data messages from the application are getting lost, then
search the System Advisor call monitoring data to understand the reason for the loss of data
messages. If this occurs, then one solution is to increase the Data Queue Size.
f TX Privacy Type and TX Privacy Alias – This field represents the encryption algorithm and the
encryption key used by the data gateway to send data message to the radios.
g Gateway IP and Gateway Tunnel IP – This field represents the IP addresses used by the virtual
network adaptor created by the data gateway service. Typically, leave these fields to the default;
unless there is a conflict with other devices connectied to the PC that are also using this IP
address.
9 Select MNIS Advanced, right click and select Create New Set. Complete the following fields:
a Data Call Confirmed – This field sets the data gateway to use confirmed data or unconfirmed
data calls for sending data messages to the radios. This field is recommended to be set to
confirmed.
Send Feedback 127

MN002731A01-A
b Compressed UDP Data Header – This field sets the data gateway to compress the IP/UDP
header of the data message before sending the message to the radio. This field is recommended
to be set to DMR.
10 Select MNIS Network, right click and select Create New Set. Complete the following fields:
a CAI Network – This field must be the same as CAI (Comment Air Interface) Network assignment
of the radios. The radio has multiple CAI IP addresses – Internal Network Address, External
Network Address and Bluetooth Network Address. The addresses are Class A addresses using
the network IDs - CAI Network, CAI Network+1 and CAI Network+2. With the default CAI
Network setting the CAI IP addresses have Class A network IDs of 12, 13 and 14. Typically,
leave the assignment to the default unless the radio IP addresses resulting from the default
setting conflicts with IP addresses of other devices on the customer’s network. See
b CAI Group Network – This field must be the same as CAI (Comment Air Interface) Network
assignment of the talkgroup. This field must be the same as CAI Group Network assignment of
the radios. The talkgroups have Multicast IP addresses with network ID of CAI Group Network.
Similar consideration as CAI Network applies for CAI Group Network.
c TMS UDP Port – This field represents the Text Messaging (TMS) Data Application UDP port.
Since most of the MOTOTRBO Text Messaging applications use this port as default, typically one
would leave the assignment to the default. Change the port here and in the Text Messaging
application when there is a port conflict with some other application deployed on the PC.
d Telemetry UDP Port and Battery Management UDP Port – These fields represent the UDP
Port of the respective applications. Similar considerations as TMS UDP Port applies for these
ports.
e Location Server UDP Port – This field represents the Location Server Application UDP Port
when the high efficiency location data is used. Change the port when there is port conflict with
another application.
f XCMP High Efficiency Data Enable and XCMP Server UDP Port – The XCMP Enable flag is
selected when there is a XCMP data application which is using high efficiency data. The XCMP
Server UDP Port is configured to the port of the XCMP application.
g Control Interface TCP Port – This field represents the MNIS data gateway control interface
TCP Port. Applications supporting Inbound Single Strength mapping with location use this port to
request the RSSI data with radio location report. Set the application to use the Control Interface
TCP Port. Change the port when there is a port conflict with another application.
11 Select MNIS Forwarding Rules, right click and select Create New Set. Complete the following field:
a MNIS forwarding rules is not required when the data application is deployed on the data gateway
PC. When the data application is not on the data gateway PC then forwarding rules are added for
the application. The data gateway uses the configured source or destination port of the data
message (received from the radio) and sent to the forwarding IP address (of the application). For
forwarding configuration, set the RM Type field to Source/Destination port, the IP field to the IP
address of the application, and the UDP Port field to the Source/Destination port number used
by the application.
12 Select Application Override Rules, right click and select Create New Set. Complete the following
field:
a The Confirmed data and Compressed UDP Header setting configured earlier (in the MNIS
Advanced window) can be over-ridden per application. The data gateway overrides the settings
for data messages with the configured Source/Destination port. Leave all the assignments to the
defaults.
128 Send Feedback

MN002731A01-A
13 Select MNIS Sites, right click and select either Copy Set From or Create New Set. If Create New
Set is selected, complete the following fields.
a Capacity Max System – select the capacity max system set.
b MNIS Sites – This field is populated when High Efficiency Data is being used for Location Data.
For this feature, the data gateway needs the latitude and longitude of the repeater sites. Enter all
the repeater sites of the system.
Selecting the Configuration for the MNIS Data Device

1 From the Radio View screen (radio icon), highlight the newly added MNIS data gateway.
2 Select the Select Configuration item.
3 Select the newly created MNIS Data Gateway configuration.
Setting the Device ID and Redundancy Group

1 From the System View screen (antenna icon), highlight the newly added Data Gateway and enter a
unique Device ID.
Every MNIS Data Gateway in the system must be configured with a unique Device ID.
2 Set the Redundancy Group to Primary, since MNIS Data Gateways do not support redundancy.
Analyzing the MNIS Data Gateway

If there are any errors with a MNIS data gateway configuration, the configuration write fails. Every data
gateway should be analyzed before writing and all errors must be resolved.
Procedure:
1 From the Radio View screen (radio icon), highlight the newly added data gateway.
4 If there are any errors indicated, read the description and then double click on the item in the list.
succeeds.
Send Feedback 129

MN002731A01-A
Exporting MNIS Data Gateway Configurations from RM and

Importing into the Data Gateway Config Folder
Procedure:
1 From the Radio View screen (radio icon), highlight the MNIS data gateway.
2 Right click and select Export  GWCFGX. Save the file.
3 On the Data Gateway PC, perform the following:
a Launch the MOTOTRBO Network Interface Service Configuration Utility (mtrbgwgui.exe).
b Import the configuration file using the Configuration Import menu.
c Activate the configuration using the Configuration Select Active Configuration menu.
d From the menu, Stop and Start the MNIS data gateway service, so the new configuration is
applied to the MNIS data gateway.
NOTE
NOTICE:
MNIS Data Gateway does not have a modified indicator in Radio Management. Since the
MNIS data gateway configuration references the system set, changes to the system set or to
the MNIS configuration requires the data gateway configuration file to be updated.
MOTOTRBO Network Interface Service Configuration Utility

The MNIS data gateway supports multiple MOTOTRBO systems. The following table lists available
configuration methods:
Table 30: MOTOTRBO Network Interface Service Configuration Methods
MNIS
RM Configuration
System Configuration Utility Configuration
Type Supported Supported file extension Comments
Single Site N Y .GWCFG MNIS Config. Utility Import and Select

Active Configuration menu options
IPSC N Y .GWCFG are not available. For other controls
please refer to MNIS Configuration
Capacity N Y .GWCFG Guide.
Plus
LCP N Y .GWCFG
Capacity Y Limited (see .GWCFG Configuration cannot be opened from

Max comments) MNIS Config Utility. Use the Import
and Select Active Configuration
menu options. the Service menu and
Stop/Start button are available. Do not
use any other Menu options.
To apply a configuration to MNIS data gateway service requires the configuration to be selected and
then stopping/starting of the service. MNIS operation mode is based on the selected active
configuration.
130 Send Feedback

MN002731A01-A
Firewall Setting on the MNIS Data Gateway PC

The Firewall Setting must be configured to open the following ports:
• UDP Ports - MNIS LE Port, MNIS LE Port+1, MNIS LE Port+2
• MNIS Control Interface TCP Port
• UDP Ports used by the data applications
Adding a MNIS Data Gateway Radio ID to the Subscriber Access Control

The Data Gateway Radio ID must be in the Subscriber Access Control.
Procedure:
3 Select Subscriber Access Control and add a device entry.
4 Select the Data Gateway device type.
5 Enter the Device ID (data gateway’s radio ID) as per guidance provided earlier in the section.
6 Under Allowed Sites, select the Data Gateway site that was entered earlier and perform the
following:
a The call capabilities of the data gateway can be changed, if required.
b Select Group Data Call and Individual Data Call, since the device is a data gateway only.
c Short Data is not supported and the rest of the call types (Voice and Radio commands) are not
applicable to the data gateway and are to be left unchecked.
d The Queue Priority of the data gateway can be lowered to prioritize voice calls over data calls
from the application in the Trunking Controller queue.
e Telephone Gateway Site and Voice Recording Site are left as None.
7 Talkgroup Associations must be configured for the Data Gateway Site, since talkgroup affiliations
from the data gateway cannot be done dynamically. If the application is receiving or sending group
data, then the Talkgroup Site Association with Radio Management has to be updated, as follows:
a Select the data gateway site to be Allowed and Always Stream for the appropriate talkgroups.
b Do not update talkgroups which the application is not using.
Send Feedback 131

MN002731A01-A
132 Send Feedback

MN002731A01-A
Redundancy
Chapter 5
Redundancy 5
Fault Tolerance
This chapter describes the impact of hardware failures in a Capacity Max system. Understanding of
hardware failures determines if the impact is acceptable or if the available software and hardware
remedies should be considered.
Failure of a Repeater
MOTOTRBO repeaters are designed to be highly available, but hardware failures infrequently occur.
Capacity Max provides software and hardware redundancy to combat repeater failures. It is important to
understand when software redundancy is sufficient and when hardware redundancy might be
necessary.
Any repeater in the system can have hardware redundancy. Generally speaking, the system can tolerate
a failure of a single repeater if additional repeaters at the site are configured similarly. If only a few
repeaters of a particular type (Trunked, Data Revert, Control Channel) are present at a site, and
additional frequencies are not available, then it may be wise to consider repeater hardware redundancy.
This section contains more information for consideration.
Failure of a Trunked Repeater
If a trunked repeater’s hardware fails, the system detects it and stops allocating calls to the repeater.
As long as additional trunked repeaters are present at the site, the system continues to operate. The
failure reduces the available trunked resources at that site and therefore lowers the trunking grade of
service for the radio users. The radio users may experience more busies and longer wait times than
they did previously until the repeater is repaired or replaced.
A remedy for failure of a trunked repeater is to have hardware redundancy for the repeater. A
hardware redundant repeater for every trunked repeater at a site having a large number of repeaters
is unnecessary and expensive. If few trunked repeaters are present at a site, then it may be wise to
consider hardware redundancy for each repeater.
Failure of a Data Revert Repeater
If a data revert repeater’s hardware fails, the radio detects it. If the radio is configured with multiple
data revert repeaters, then it finds another data revert repeater of the same channel type (data revert
with IP data, data revert with high efficiency data, EGPS with IP data, or EGPS with high efficiency
data) to use. As long as additional data revert repeaters of the same channel type are present at the
site, the radios continue to send data. Because a data revert repeater supports the data of a large
number of radios, failure of one repeater may cause the remaining repeaters to quickly run out of
available capacity, leaving some radios without service.
If only a few data revert repeaters of the same channel type are present at a site, or if all the data
revert repeaters are highly utilized, then it may be wise to consider repeater hardware redundancy.
Send Feedback 133

MN002731A01-A
Chapter 5: Redundancy
Failure of a Control Channel Repeater
If the active control channel repeater’s hardware fails, the site selects another control channel
capable repeater as the active control channel. As long as additional control channel capable
repeaters are present at the site, the system continues to operate. The failure reduces the available
trunked resources at that site and therefore lowers the trunking grade of service for the radio
users.The radio users may experience more busies and longer wait times than they did previously
until the repeater is repaired or replaced.
If no remaining control channel capable repeaters are present at the site, the site becomes
unavailable. The radios may move to other sites if they are within their coverage. Because control
channels require exclusive use frequencies, it is recommended to have multiple dedicated
frequencies per site and to configure the repeaters to be control channel capable. If only one
exclusive use frequency is available for a site, and only one control channel capable repeater, then it
may be wise to consider repeater hardware redundancy.
Failure of a Capacity Max System Server (CMSS)

The Capacity Max System Server (CMSS) is designed to be highly available. It has redundant power
supplies, redundant fans, and redundant hard drives. Capacity Max also supports a second Capacity
Max System Server. The second CMSS does not need to be at the same physical location as the first
CMSS.
The Capacity Max System Server hosts the Trunking Controller, System Advisor Server, and the Voice
Gateway. If the hardware of a single CMSS fails, all three functions become unavailable, consider a
second Capacity Max System Server. This section contains more information on the impact of the
failures for consideration.
Failure of the Trunking Controller
If the CMSS fails, the Trunking Controller becomes unavailable. In the absence of another CMSS
with a Trunking Controller, all radio communication becomes limited to the initiating RF site. No wide
area communication is available. This condition is often referred to as Site Trunking. Voice consoles,
logging recorders, phone gateways, and data applications cannot communicate to the radios over
the air without an available Trunking Controller.
When a Trunking Controller is unavailable and all sites are in Site Trunking, radios can still have
group and individual voice calls and send text messages to other radios at their site. Because the
Trunking Controller is unavailable, subscriber access control is no longer available, therefore all
radio requests are allowed. While in Site Trunking, the radio provides a periodic audible and visual
indication to its user to inform them of their limited functionality.
If available, the redundant CMSS detects the loss of the primary CMSS and takes over as the active
Trunking Controller within a couple minutes. During failure detection, all services may not be
available and the radio sites may temporarily enter Site Trunking. After the new Trunking Controller
takes over, it requests updated registration information from the radios at each site. For a typical
number of radios per site, around 600, re-registration takes a few additional minutes. All wide area
services, including subscriber access control, are restored. Voice consoles, logging recorders,
phone gateways, and data applications are restored.
While the redundant trunking controller is active and the primary is unavailable, new radio sites that
power up (or reset) do not join the system, because newly powered up sites must register with the
primary trunking controller.
134 Send Feedback

MN002731A01-A
The trunking controller provides radio presence information to data and voice applications.
Applications can register for PN Status with a primary and a redundant trunking controller at the
same time but can subscribe for radio presence only with the active. If an application loses
connection with the primary and the status of redundant is active, the application subscribes with the
redundant trunking controller.
Failure of the System Advisor Server
If the CMSS fails, the System Advisor Server on the CMSS becomes unavailable. Without a System
Advisor Server, all System Advisor services become unavailable until the server is restored. No
device status, alarm reporting, or call activity is logged during the outage.
If available, a second CMSS hosts another System Advisor Server. Device status, alarm reporting,
and call activity are always logged to both System Advisor Servers. Therefore, access to current and
past logged information is available while the primary CMSS is unavailable. The System Advisor
Client must be connected to the available System Advisor Server to view the device status, alarm
reporting, and call activity.
Failure of the MNIS Voice and Radio Command (VRC) Gateway
If the CMSS fails, the MNIS Voice and Radio Command (VRC) Gateway becomes unavailable.
Voice consoles, logging recorders, and phone gateways cannot communicate to the radios over the
air without an available voice gateway.
If available, another CMSS can host a redundant voice gateway. The redundant voice gateway can
be hosted on the same CMSS as the redundant Trunking Controller, or can be on another CMSS by
itself. Capacity Max supports multiple primary VRC Gateways (for increased capacity), and each
primary can have a redundant VRC Gateway. When the redundant voice gateway becomes active, it
asks the voice applications to switch and start using the redundant voice gateway. The operation is
dependent on the specific voice application.
Once the primary CMSS returns back to operation, the system switches back to the primary CMSS
automatically.
Failure of a Wide Area Network Connection or an IP Network Router

If an IP network router fails, or an Internet connection drops, communication between the devices at a
site and the rest of the system is severed. The type of site that has lost communication is very important
to understanding the outcome of such failures. Although, it is assumed that the devices at the site can
still communicate with each other through the local network switch.
Failure of a Wide Area Connection to a Repeater Site
If an IP network router fails, or an Internet connection drops at a repeater site, the repeater site loses
communication with the rest of the system, and most importantly with the Trunking Controller.
While the site is out of communication with the Trunking Controller, no wide area communication is
available into or out of the repeater site. This condition is often referred to as Site Trunking. A
repeater site announces over the air that it is in Site Trunking. Radios do not prefer sites in Site
Trunking, and therefore radios attempt to roam to other sites.
Radios that are not in coverage of another site remain on the site in Site Trunking. These radios can
still make group and individual voice calls and text messages to other radios at their site. Because
the Trunking Controller is unavailable, subscriber access control is no longer available, and therefore
all radio requests are allowed. While in Site Trunking, the radio provides a periodic audible and
visual indication to its user to inform them of their limited functionality.
Send Feedback 135

MN002731A01-A
Voice consoles, logging recorders, phone gateways, and data applications cannot communicate to
the radios at the site on the trunked channels without the trunking controller, even if they are co-
located with the repeaters. However, Data revert channels do not require the trunking controller to
operate after initial registration, and therefore, if a data gateway and data application are co-located
with the data revert repeaters, reverted data is still available.
Call monitoring is streamed directly from the repeaters to the configured IP addresses. If those
addresses are located at the site, the call monitoring is still available. Because the System Advisor
Server is on the CMSS with the Trunking Controller and if the Trunking Controller is unavailable, the
System Advisor Server is likely to be unavailable as well.
When the wide area connection is restored, the repeater site communicates with the Trunking
Controller, and wide area communication and other services are restored.
Failure of a Wide Area Connection to a Capacity Max System Server
If an IP network router fails, or an Internet connection drops at the site where the primary Capacity
Max System Server (CMSS) is located, the Trunking Controller becomes unavailable to the rest of
the system. Without a Trunking Controller, all radio communication on the trunked channels
becomes limited to the initiating repeater site. All repeater sites enter Site Trunking. Data revert and
call monitoring are still available because they do not require the trunking controller. Because the
System Advisor Server is on the CMSS with the Trunking Controller and if the Trunking Controller is
unavailable, the System Advisor Server is likely to be unavailable as well.
If available, a redundant CMSS at another site detects the loss of the primary CMSS and takes over
as the active Trunking Controller. The new Trunking Controller requests updated registration
information from the radios at each site. All wide area services including subscriber access control
are restored. Voice consoles, logging recorders, phone gateways, and data applications are
restored.
Repeaters located with the primary CMSS do not enter Site Trunking.
Fragmentation of the Wide Area Network
Depending on its complexity, the wide area IP network may not simply fail at a single site, but rather
fail in a way where the system breaks into multiple subsets of sites, where some subsets may
contain multiple sites, and others only one site. If utilizing a private network, it should be designed to
avoid this scenario.
Repeater sites that can communicate with the primary CMSS do not enter Site Trunking and can
communicate across other repeater sites that can communicate with the primary CMSS. If the
redundant CMSS cannot communicate with the primary CMSS, it becomes active. Repeater sites
that can communicate with an active redundant CMSS do not enter Site Trunking and can
communicate across other repeater sites in communication with the redundant CMSS. Sites that
cannot communicate with either CMSS enter Site Trunking. Access by voice console and data
applications is also dependent on their ability to communicate with either the primary or redundant
CMSS.
If a single point of failure in the wide area network is identified, location of the primary and redundant
CMSS, as well as voice and data gateways and their applications should be located to maximize
available resources to their respective users after the bifurcation.
When either a hub router (for example, a router having a static WAN IP address and either a VPN
Address Management (VAM) server or a Next Hop Server (NHS)) or a hub router's site link fails, the
dynamic VPN tunnel network may not be able to establish the necessary connectivity between spoke
routers. If the dynamic VPN tunnels timeout due to inactivity or a temporary loss of connectivity, they
cannot be rebuilt without having connectivity to the hub router. A solution is to have a second hub router
(for example, a second router having a static WAN IP address and either a VAM server or a NHS) and to
configure the spoke routers with both hub routers' static WAN IP addresses. See Configuring the IP
Network on page 46 for more details.
136 Send Feedback

MN002731A01-A
Failure of the IP Network Switch

Capacity Max recommends utilizing reliable IP network switches, but hardware failures infrequently
occur. If an IP network switch fails, communication between the devices at a site and the rest of the
system is severed. Similar to the loss of a wide area connection, the type of site that has lost
communication with the rest of the system is very important to understanding the outcome of such
failures. See Failure of a Wide Area Network Connection or an IP Network Router on page 135 on the
effects of losing communication with a site.
In addition to losing communication with the site, the devices at the site cannot communicate with each
other.
This is particularly disruptive at a repeater site. Each repeater at the site becomes isolated. Control
channel capable repeaters all become multiple instances of a single channel trunking site (same site ID)
in Site Trunking. Although there is only one channel, queuing and call back is handled locally and allows
for organized access to the channel. All radios may not be monitoring the same control channel.
A repeater site announces over the air that it is in Site Trunking. Radios do not prefer sites in Site
Trunking, and therefore radios attempt to roam to other sites.
Radios that are not in coverage of another site remain on the site in Site Trunking. The radios can still
make group and individual voice calls and text messages to other radios at their site. Because the
Trunking Controller is unavailable, subscriber access control is no longer available, and therefore all
radio requests are allowed. Voice consoles, logging recorders, phone gateways, and data applications
cannot communicate to the radios at the site. While in Site Trunking, the radio provides a periodic
audible and visual indication to its user to inform them of their limited functionality.
Capacity Max supports hardware redundant IP network switches to mitigate these failures. See IP
Network Multiple Site Switch Configuration on page 137 for more guidance and configuration details.
Failure of the MNIS Data Gateway

If a MNIS Data Gateway fails, the data applications utilizing it cannot communicate to the radios over the
air. Capacity Max supports multiple data gateways. Data applications can integrate multiple data
gateways to create redundancy in their architecture. Loss of IP connectivity between the data gateway
and the trunking controller, the data gateway and the radio sites, or the data gateway and the data
application results in loss of data messages.
Failure of the Radio Management Server

If the Radio Management Server fails, radio and system configurations cannot be modified until
restored. But otherwise, the Capacity Max system operation is not affected. The Radio Management
Server database should be periodically backed up.
IP Network Multiple Site Switch Configuration

It may be desirable to use multiple Ethernet switches at a physical location. Reasons for doing this are
described as follows:
• Co-Located, Redundant Capacity Max System Servers (CMSS): When multiple, redundant CMSS
instances are co-located, a recommendation is to attach each CMSS to a different Ethernet switch,
which eliminates the Ethernet switch from being a single point of failure for the CMSS functions.
Send Feedback 137

MN002731A01-A
• Co-Located Data Gateways: When multiple data gateways are co-located, a recommendation is to
attach each data gateway to a different Ethernet switch.
NOTICE:
Multiple data gateways are supported by a Capacity Max system, but redundant data gateways
are not. An application may choose to support attachment to more than one than one data
gateway, which can provide a higher level of availability.
• “Critically Important” RF Site: When an RF site (that is, a repeater) is determined to be critically
important as anticipated by an end user’s usage profile, deploy multiple Ethernet switches at the
critically important site and distribute repeaters across the Ethernet switches. This deployment
improves the availability of wide area trunking at the site (with at least some of the site’s repeaters)
while reducing the likelihood of having no trunking services at the site if an Ethernet switch fails.
NOTICE:
An RF Site having a “large” number of repeaters (for example, more than eight trunked
repeaters) might be considered to be “critically important”, and to deploy multiple Ethernet
switches at such a site.
• “Large” Number of Co-Located Devices: When the number of co-located devices (for example,
CMSS, repeaters, data gateways, application servers, application clients, and so on) exceeds the
Ethernet port capacity of an available Ethernet switch, then multiple Ethernet switches can be
deployed.
Example of Standardized Switch Configuration

To simplify system deployment and minimize the number of unique Ethernet switch configurations used
in a Capacity Max system, a recommendation is to standardize an Ethernet switch configuration and
make it a building block that can be used at any type of physical location with only appropriate IP
address and VLAN customizations. For example, Table 31 describes a recommended, standardized 24-
port Ethernet switch (HP 2530 and Cisco 3650) with either one or two of these switches deployed at a
physical location.
Table 31: Example of Standardized 24-Port Ethernet Switch
HP2530 Cisco 3650

Port Port Subnet Switch 1 Switch 2
Number Number Usage Type VLAN VLAN
1-12 1-10 Repeaters Radio A A

Infrastructure
13-17 11-15 Non-Motorola Application Application B B

Servers and Clients
18-21 16-19 Capacity Max System Server Gateway C D
22 20 MNIS Data gateway Gateway E F
23 21 Technician Service Laptop Radio A A

Infrastructure
24 22 Mirror (for diagnostic packet N/A G, Port 24, G, Port 24,

capture) 1 VLAN 2 VLAN
25 23 Router (trunk) N/A N/A N/A
26 24 Co-Located Switch N/A N/A N/A
138 Send Feedback

MN002731A01-A
As shown in Figure 30 on page 139, it is recommended to attach repeater X to interface X on the

Ethernet switch. It is also recommended to attach control channel (CC) capable repeaters to the lower
numbered interfaces, immediately followed by traffic channel (TC) repeaters (which are not control
channel capable), immediately followed by revert channel (RC) repeaters, and finally immediately
followed by hardware (HW) redundant repeaters which are attached to the higher numbered interfaces.
Figure 30 on page 139 shows an example site having four CC capable repeaters, five TC repeaters, two
RC repeaters, and one HW redundant repeater connected to an HP 2530 Switch.
Figure 30: Example of Site with Multiple Repeaters Connected to an HP 2530 Switch
Send Feedback 139

MN002731A01-A
Figure 31 shows an example site having four CC capable repeaters, five TC repeaters, and one RC
repeater connected to a Cisco 3650 Switch.
Figure 31: Example of Site with Multiple Repeaters Connected to a Cisco Switch
Site Network Topology

When a physical location requires two Ethernet switches, Outfit the physical location’s router with a
small (for example, 4-port), integrated switch module that connects to the two switches as shown in
Figure 32 on page 141. Not every physical location is likely to require all of the networks shown. In fact,
many physical locations may only have one network (for example, an RF-only site has only a radio
infrastructure network).
140 Send Feedback

MN002731A01-A
Figure 32: Example of Integrated Switch Module Connected to Two Ethernet Switches
Site
IP
Site Network Site
Site with Multiple Ethernet Switches Radio Infrastructure Network (VLAN)
Rapid Spanning Tree Protocol (RSTP) Application Network (VLAN)

Root Bridge Gateway Network
CMSS 1 (VLAN )
Data Gateway 1 (VLAN )
CMSS 2 (VLAN )
Data Gateway 2 (VLAN )
Application Application Application Application Application Application Application Application

Server Client Client Client Client Client Client Server
Repeater Repeater Repeater Repeater Repeater Repeater

Technician Technician
Data CMSS CMSS Data
Laptop Laptop
Gateway Gateway
When more than one Ethernet switch is used at a physical location, Rapid Spanning Tree Protocol
(RSTP) must be used to prevent layer 2 switching loops and associated broadcast storms. Additionally,
it is highly desirable to configure the router’s switch module to serve as the RSTP root bridge, which
optimizes the flow of IP traffic to the WAN.
In the example in Figure 32:
• Redundant CMSS instances are attached to different switches and different VLANs.
• Multiple data gateways are attached to different switches and different VLANs.
• Repeaters are attached to different switches but the same VLAN.
• Non-Motorola application servers and clients are attached to different switches but the same VLAN.
When a physical location has two or more co-located RF sites, each RF site must have its own VLAN,
so in the example in Figure 32, a second radio infrastructure network VLAN must be configured to
support a second RF site.
Send Feedback 141

MN002731A01-A
Assignment of Repeaters to Ethernet Switches at a Physical Location

A recommended strategy for assigning repeaters to one of the two switches is now presented. General
guidance is to assign half of the repeaters to one switch and the remaining repeaters to the other switch.
The following sections outline a suggested strategy for assigning repeaters to Ethernet switches at a
physical location. This suggested strategy serves primarily to standardize a common approach across
all physical locations and all systems.
Assignment of Trunked Repeaters to Ethernet Switches at a Physical Location

An RF site must have one or more primary control channel capable repeaters (according to
provisioning), and the total number of such repeaters is either even or odd.
• If there is an even number of control channel capable repeaters, exactly half of those repeaters are
assigned to a first switch, and the remaining half are assigned to a second switch.
• If there is an odd number of control channel capable repeaters, a recommendation is to have the first
switch host one greater control channel capable repeater than the second switch (that is, the “extra”
control channel capable repeater is assigned to the first switch).
An RF site may have repeaters that are not control channel capable (according to provisioning), and the
total number of such repeaters will be either even (also including zero) or odd.
• If there is an even number of repeaters that are not control channel capable, exactly half of those
repeaters are assigned to a first switch, and the remaining half are assigned to a second switch.
• If there is an odd number of repeaters that are not control channel capable, a recommendation is to
have the second switch host one greater repeater that is not control channel capable than the first
switch (that is, the “extra” repeater that is not control channel capable is assigned to the second
switch).
Assignment of Revert Channel Repeaters to Ethernet Switches at a Physical

Location
An RF site may have revert channel repeaters, and the total number of such repeaters is either even
(also including zero) or odd.
• If there is an even number of revert channel repeaters, exactly half of those repeaters are assigned
to a first switch, and the remaining half are assigned to a second switch.
• If there is an odd number of revert channel repeaters and an even number of total repeaters, a
recommendation is to assign the “extra” (or odd) repeater to whichever of the two switches would
result in an equal number of total repeaters being assigned to each switch.
• If there is an odd number of revert channel repeaters and an odd number of total repeaters, a
recommendation is to arbitrarily assign the “extra” (or odd) repeater to the first Ethernet switch.
Recognizing there are two types of revert channel repeaters which may be present at a site; enhanced
GPS revert channel for IP data, and enhanced GPS revert channel for high efficiency data; a
recommendation is to balance each type of revert channel repeater across the two switches.
A further recommendation is to provision subscriber devices with at least one revert channel repeater
from each group (for example, switch 1 or switch 2).
142 Send Feedback

MN002731A01-A
The recommendations are summarized in Table 32.
Table 32: Recommendations for Assignment of Repeaters to Ethernet Switches
Number of Number of Number of

Repeaters Repeaters Revert
with CC without CC Channel
Capability Capability Repeaters Switch 1 Switch 2
Even Even Even Equal Number of CC Capable Repeaters
Equal Number of non-CC Capable Repeaters
Equal Number of Revert Channel Repeaters
Even Odd Even Equal Number of CC Capable Repeaters
“Extra” non-CC Capable

Repeater
Odd Even Even “Extra” CC Capable

Repeater
Odd Odd Even “Extra” CC Capable

Repeater

Repeater
Even Even Odd Equal Number of CC Capable Repeaters
“Extra” Revert Channel

Repeater
Even Odd Odd Equal Number of CC Capable Repeaters

Repeater

Repeater
Odd Even Odd “Extra” CC Capable

Repeater
Equal Number of non-CC Capable Repeater

Repeater
Send Feedback 143

MN002731A01-A
Table 32: Recommendations for Assignment of Repeaters to Ethernet Switches (Cont.)
Number of Number of Number of

Repeaters Repeaters Revert
with CC without CC Channel
Capability Capability Repeaters Switch 1 Switch 2
Odd Odd Odd “Extra” CC Capable

Repeater

Repeater
Repeater
Assignment of Hardware Redundant Repeaters to Ethernet Switches at a

Physical Location
Capacity Max supports an ability to have hardware redundant repeaters at an RF site. When hardware
redundant repeaters are present at an RF site, a recommendation is to assign the redundant repeater to
an Ethernet switch the same as the primary repeater. Primary repeaters transfer control to the hardware
redundant backup repeaters based upon the primary repeater’s internal fault status (that is, alarm) and
not on external faults (that is, Ethernet switch failure).
Capacity Max System Server (CMSS) Redundancy

Multiple Capacity Max System Servers (CMSS) instances can be deployed in a Capacity Max system to
support redundancy of the Trunking Controller (TC) and MNIS Voice and Radio Control (VRC) gateway.
Both physical redundancy and geographical redundancy are supported. The CMSSs communicate with
each other using standard IP messaging and do not require a hardwire General Purpose Input/output
(GPIO) connection similar to the one found between redundant repeaters. As long as IP connectivity is
available, the CMSSs may be physically located at a different geographical location to provide
redundancy to the ISP connection at the primary CMSS.
Each CMSS in the system must be assigned a unique Device ID. This is true for a CMSS hosting
redundant trunking controller or redundant MNIS VRC gateway.
The primary CMSS should be configured with a Device ID of 1, and the alternate CMSS should be
configured with a Device ID of 2. The Primary should have a Redundancy Group ID of Primary, and the
Alternate should have a Redundancy Group ID of Alternate. The Device ID and Redundancy Group ID
of the CMSS are configured in the Radio System view (antenna icon) in Radio Management.
There can only be one primary and one alternate TC in the entire Capacity Max system. For the VRC
Gateway, there can only be one primary and one alternate VRC Gateway assigned to the same VRC
Gateway Site ID; however, there can be multiple VRC Gateway Sites within a Capacity Max system,
with each VRC Gateway Site potentially having both a primary and an alternate VRC Gateway.
The primary and the alternate TCs exchange periodic messages to detect each other in the system.
Normally, the primary TC is the active TC in the system. However, when the alternate TC detects that it
has lost contact with the primary TC, the alternate TC automatically takes over as the active TC within a
couple minutes and makes announcements over the IP network to inform other entities that it has
become the active TC. Meanwhile, the alternate TC continues to attempt to re-establish communication
with the primary TC. The primary TC automatically becomes the active TC again when communication
has been re-established. The switchover from the primary to the alternate and vice versa is completely
automatic and does not require any manual intervention.
144 Send Feedback

MN002731A01-A
Radio presence and mobility information is not persistent on the TC and is not transferred whenever a
switchover between the primary and alternate TC occurs. Rather, the newly active TC attempts to
rebuild the presence and mobility database by requesting all radios to re-register with the system. This
can trigger a mass-registration scenario and temporarily affects the reliability of radio communications.
All entities in the system are configured with the IP address of only the primary TC as the Master. As a
consequence, no devices can join the system if the primary TC is not available, even if the alternate TC
is available and has already taken on the role as the active TC. For a typical number of radios per site,
around 600, re-registration takes a few additional minutes.
Capacity Max supports up to two System Advisors in the system. System Advisors are not configured
into a primary/alternate pair. Rather, both System Advisors are active and operate completely
independent of each other. Any SNMP and call monitoring messages are sent to both System Advisors.
Repeater Hardware Redundancy

MOTOTRBO repeaters are designed to be highly available, but hardware failures do infrequently occur.
Capacity Max provides software and hardware redundancy to combat repeater failures. It is important to
understand when software redundancy is sufficient and when hardware redundancy might be
necessary. This section provides considerations for determining whether hardware redundancy is
required. It also details how to configure and wire a hardware redundant repeater.
Why Utilize Hardware Redundant Repeaters

Any repeater in the system can have hardware redundancy. The system can tolerate a failure of a single
repeater if additional repeaters at the site are similarly configured. If only a few repeaters of a particular
type are present at a site, and additional frequencies are not available, then consider repeater hardware
redundancy. The following sections contain more information for consideration.
Redundancy Considerations for Trunked Repeaters

If a trunked repeater’s hardware fails, the system detects it and stops allocating calls to the repeater. As
long as additional trunked repeaters are present at the site, the system continues to operate. The failure
reduces the available trunked resources at that site and therefore lowers the trunking grade of service
for the radio users. The radio users may experience more busies and longer wait times than they did
previously until the repeater is repaired or replaced.
A remedy for failures is to have hardware redundancy for the repeater. A hardware redundant repeater
for every trunked repeater at a site having a large number of repeaters is unnecessary and expensive. If
few trunked repeaters are present at a site, then it may be wise to consider hardware redundancy for
each repeater.
Redundancy Considerations for Data Revert Repeaters

If a data revert repeater’s hardware fails, the radio detects it. If the radio is configured with multiple data
revert repeaters, then it finds another data revert repeater of the same channel type (data revert with IP
data, data revert with high efficiency data, EGPS with IP data, or EGPS with high efficiency data) to use.
As long as additional data revert repeaters of the same channel type are present at the site, the radios
continue to send data. Because a data revert repeater supports the data of a large number of radios,
failure of one may cause the remaining repeaters to quickly run out of available capacity, leaving some
radios without service.
If only a few data revert repeaters of the same channel type are present at a site, or if all the data revert
repeaters are highly utilized, then it may be wise to consider repeater hardware redundancy.
Send Feedback 145

MN002731A01-A
Redundancy Considerations for Control Channel Repeaters

If the active control channel repeater’s hardware fails, the site selects another control channel capable
repeater as the active control channel. As long as additional control channel capable repeaters are
present at the site, the system continues to operate. The failure reduces the available trunked resources
at that site and therefore lowers the trunking grade of service for the radio users. The radio users may
experience more busies and longer wait times than they did previously until the repeater is repaired or
replaced.
If no remaining control channel capable repeaters are present at the site, the site becomes unavailable.
The radios may move to other sites if they are within their coverage. Because control channels require
exclusive use frequencies, it is recommended to have multiple dedicated frequencies per site and
configure their repeaters to be control channel capable. If only one exclusive use frequency is available
for a site, therefore only one control channel capable repeater, then it may be wise to consider repeater
hardware redundancy.
Configuration and Wiring of Hardware Redundant Repeaters

Redundant repeaters are programmed identical to their primary repeaters with a few exceptions.
Their configurable device identifiers are the same, but their redundancy group identifiers are different.
The redundancy identifier of the primary should be set to Primary (0), and the redundancy group
identifier of the redundant should be set to Alternate (1). This allows their full device identifier with the
system to be unique. This information is also utilized by the System Advisor to indicate the pairing
between primary and redundant repeaters.
Another difference between the primary and redundant repeater is the programming of their General
Purpose Input/Output (GPIO) pins. To facilitate the switching, repeaters need to be wired together. A
GPIO output line of the primary repeater is connected to a GPIO input line of the redundant repeater. A
major alarm in the primary repeater triggers the redundant repeater to become enabled. See the
repeater user guide for a list of major alarms. An RF switch triggered by the major alarm switches the
transmit antenna system to the redundant repeater.
The redundant repeater is always connected to the IP Network but does not participate until enabled
through the GPIO. The disabled repeater does send information to the System Advisor if it experiences
an alarm or event while disabled.
If the primary repeater was the active control channel when it failed, another control channel capable
repeater may become the active control channel prior to the redundant repeater becoming active. If the
redundant repeater is provisioned as a preferred control channel, the redundant repeater would be
selected over any repeaters that are not identified as preferred.
Setting GPIO Physical Pins

A configurable GPIO output pin of the primary repeater is connected to a configurable GPIO input pin of
the redundant repeater. The ground pin of the primary repeater must be connected to the ground pin of
the redundant repeater.
The configurable GPIO pins of the repeater are configured within Radio Management. They can be
found in the Repeater Configuration, under Accessories and then GPIO Physical Pins.
146 Send Feedback

MN002731A01-A
Procedure:
1 On the primary repeater, set the feature of a GPIO configurable pin to Major Alarm (an output), and
set the Active Level to High.
With this configuration, the primary repeater normally sets the configurable GPIO pin to low (0 V), if
the primary repeater experiences a major alarm, it sets the configurable GPIO pin to high (5 V).
Figure 33: Primary Repeater Pin #19 Settings
2 On the redundant repeater, set the feature of the configurable GPIO pin to Disable (an input), and
set the Active Level to Low. A short debounce is fine. With this configuration, if the redundant
repeater receives a high signal (5 V) on its configurable GPIO pin, it becomes enabled. Otherwise it
is disabled.
Figure 34: Redundant Repeater Pin #19 Settings
NOTICE:
An internal pull-up resistor pulls the input line high if no external equipment is connected to that
line. If the primary repeater loses power or is not connected, the redundant repeater becomes
enabled. Keep this in mind when handling RF connections.
RF Output Configuration
RF outputs for the primary and redundant repeaters must be connected to an output antenna system
(combiner, cabling, antenna, and so on). They cannot both be connected to the same antenna system at
the same time because the output power of the primary may damage the output port of the redundant
and vice versa. The isolation can be accomplished with duplicate and independent output antenna
systems, but this can be expensive.
The isolation can also be accomplished by utilizing an RF relay (a type ‘N’ female connector relay) that
normally routes the RF from the primary repeater to the shared antenna system, and upon failure of the
primary, routes the RF from the redundant repeater to the shared antenna system.
When the antenna system is shared in this way, a failure in the antenna system above the RF relay may
eventually cause both the primary and redundant repeater to experience a major alarm (high VSWR),
resulting in neither being available. When an RF isolator or circulator is in use, the high VSWR may not
be detectable by the repeater.
RF Relays commonly require 12 V to energize; therefore the 5 V from the configurable GPIO pin is
insufficient. The switched and fused B+ pin on the repeaters offers 13 V and can be used to drive the RF
relay. A simple transistor circuit (a Darlington pair) can be utilized to energize the RF relay with the 13 V from
the B+ pin when the repeater sets the configurable GPIO pin (Major Alarm) to high (5 V).
Send Feedback 147

MN002731A01-A
If the primary repeater looses power, the redundant repeater has an internal pull-up resistor that pulls
the input line high and enables the repeater. This activates the transistor circuit, which energizes the RF
relay using the 13 V from the B+ pin of the redundant repeater. Diodes should be used to protect the B+
pin of each repeater and the RF relay.
The following table lists the physical pins that are recommended to be used for each function for each
repeater model. The configurable GPIO# used in Radio Management is shown in parenthesis.
Table 33: Recommend Pins Numbers per Repeater Model
Repeater Model
Pin Name XPR8380 XPR8400 MTR3000 SLR5700
Switched / Fused B+ (13 V) 7 7 20 20
Configurable Pins (Major 19 (GPI02) 19 (GPI02) 8 (GPI03) 8 (GPIO6)

Alarm or Disable)
GND 16 16 16 16
An example circuit for the XPR is shown in Figure 35. In this example, component model numbers are
provided only for reference. Similar components or their successors should be commonly available. See
Table 33 for pin numbers specific to the repeater model.
Figure 35: Example of XPR Repeater Hardware Redundancy Switching Circuit
RF Out RF Out
Primary Redundant
Repeater Repeater
SW B+ (13V) SW B+ (13V)
7 7
L1
RDL-SR002
8092894X02
NC
NO
C-3
R1 Q1
B-2
MPSA13RLRP
4.7K 48-13824D05
E-1
Major Alarm Repeater Disable

19 19
Active High Active Low
GND GND
16 16
* Asserting the Repeater Disabled pin triggers

the repeater to enter disabled state.
148 Send Feedback

MN002731A01-A
RF Input Configuration
The primary and redundant repeaters can share the same input antenna system (multi-coupler,
amplifier, cabling, antenna, and so on). Connecting both RF inputs to the same antenna system is
acceptable.
Recovery of Redundancy Configuration

When the primary repeater is repaired, or replaced with a new one, the circuit switches back to the
primary. It is important that configurable GPIO output pin (Major Alarm) is configured as the previous
primary repeater. Assuming the repair repeater does not have a major alarm, the configurable GPIO pin
is set low, which sets the redundant repeater disabled, and switches the RF relay back to the primary
repeater.
Power cycling the primary repeater clears any alarm state, and on power-up the primary repeater
becomes active again. If the problem that originally caused the alarm persists, the alarm occurs again,
and it re-enters the alarm state, which triggers the enabling of the redundant repeater and switching of
the RF relay.
If the configurable GPIO pins between repeaters is disconnected or is severed, both repeaters become
enabled at the same time. Because both are programmed identical, system operation may be
unpredictable.
Send Feedback 149

MN002731A01-A
150 Send Feedback

MN002731A01-A
Optimizations
Chapter 6
Optimizations 6
Data Revert Channel Optimization

This section describes configurations for Data Revert Channels that may be used to optimize the
performance of a Capacity Max system.
Data Revert Channel Configuration

Table 34 identifies programmable configuration options required to send radio to server data on an
Enhanced GPS Revert channel.
Table 34: Configurations Required to Send Radio to Server Data on an Enhanced GPS Revert Channel
Radio General
Settings DMR3 System
GPS on
Data Payload Revert Scheduled Scheduled GPS
Format GPS GNSS Channel GPS Window Size
IP Data Yes Select N/A (1) Yes 5 - 10 (2)
High Efficiency Yes Select N/A (1) Yes 1: IP Data GW

Data
2: OTA Data GW
(1) See Sending of EGPS location data at site without configured EGPS Revert Channels for impacts of this
configurable settings.
(2) Exact setting dependent upon parameters requested and clear/encrypted.
In addition to the settings in Table 34, the Enhanded GPS Revert channels on a per site basis must be
entered into the Channel Plan. Besides frequencies, time slot and color code, Channel Type = Data
Revert and for Enhanced GPS must be selected.
Different Message Sizes on EGPS Channels

There can be scenarios where some radios use EGPS with IP data while other radios use EGPS with
High Efficiency Data. Only one widow size per system is supported, and therefore all the EGPS
channels in the system are configured to support an IP data window size (5 – 10) that accommodates
the largest message size.
Transmission of EGPS Location Data at Sites Without Configured

EGPS Revert Channels
When a radio roams from a high-density site to a low-density site (one or two repeaters), the radio may
continue to send location updates at the rate specified by the location application. The following options
and constraints are available with respect to sending location updates at the low density site.
Send Feedback 151

MN002731A01-A
Chapter 6: Optimizations
When a radio is configured to send IP Data or High Efficiency Data location updates on an EGPS
Channel (Scheduled GPS selection is checked), the GPS Revert Channel selection is unchecked and
the site consists of only trunked channels (no revert channels) then IP Data would be sent on a trunked
channel but High Efficiency Data would not be sent. Assuming there is no voice activity, one trunked
channel (time slot) supports 30 IP Data location updates/minute.
When a radio is configured to send IP Data or High Efficiency Data location updates on an EGPS
Channel (Scheduled GPS selection is checked), the GPS Revert Channel selection is checked and the
site consists of only trunked channels, then neither IP Data nor High Efficiency Data would be sent.
When a radio is configured to send High Efficiency Data location updates on an EGPS Channel, it is
NOT possible to send High Efficiency Data location updates on a trunked channel. If High Efficiency
Data is required at a low density site, a EGPS Data Revert Channel must be deployed at the site.
Periodic Window Reservation (Channel Loading)

The Periodic Window Reservation field defines the maximum number of windows that are reserved for
periodic reservations on the channel. Valid options are 90%, 75%, 60% and 45%. The other windows
(10%, 25%, 40% and 65%) are used by radios to send in the data that was not sent because the radio
was involved in a voice call during its scheduled time window.
Looking at the extremes for location updates may help in understanding the impact of the Periodic
Window Reservation on data. If location enabled radios were never in voice calls, then they would
always send in the data on their reserved window, and the reliability excluding RF would be 100%. In the
other extreme, if location enabled radios were in voice calls 100% of the time, then they could never
send their data, and the reliability would be 0%. When a radio misses sending a location update
because it was in a voice call, the radio tries to send the location after the call ends. If the number of late
location updates is large relative to the windows not reserved for periodic reservations, the location
updates may time out and thus not be sent. Therefore the Periodic Window Reservation setting impacts
the data reliability of the data.
An exception to sending late location updates is for High Efficiency Data at update rates of 7.5 seconds
and 15 seconds. In these cases the radio does not attempt to send a location update when the reserved
window is missed; rather, the data is never sent. Therefore it is recommended to set the Periodic
Window Reservation to 90% in these cases.
Figure 36 on page 153 shows how the data reliability is impacted by the average duration a radio is in a
voice call (10 seconds and 20 seconds) with a window size of 7, a location update rate of 1 per minute,
and a Periodic Window Reservation of 75%. The EGPS channel would support 107 radios with 100%
reliability when none of the radios sending location updates were involved in voice calls.
152 Send Feedback

MN002731A01-A
Figure 36: Impact of Voice Call Duration on Data Reliability
Figure 36 shows the two bounding aspects discussed earlier in this section. When there are plenty of
free windows to send the late location updates, the reliability approaches 100%. When there are few
free windows, the reliability approaches the ratio of time outside a voice call to the update period. So for
the 20-second voice call with 1-minute updates, the probability approaches (40 s)/(60 s) or 66.67%.
For IP Data the following guidelines should be employed with respect to the average voice call duration
for reliability in the 90% to 95% range when the radio updating once per minute:
• 90% Periodic Window Reservation: 0  Avg. Voice Call  7.5 seconds
• 75% Periodic Window Reservation: 7.5 seconds < Avg. Voice Call  10 seconds
• 60% Periodic Window Reservation: 10 seconds < Avg. Voice Call  12.5 seconds
• 45% Periodic Window Reservation: 12.5 seconds < Avg. Voice Call  15 seconds
One of the properties of the EGPS Channels is that the number of opportunities to request sending late
location updates decreases as the window size decreases. When the window size is 1, this can quickly
move the data reliability towards the ratio of time outside a voice call to the update period. For High
Efficiency Data the following guidelines should be noted:
• 90% Periodic Window Reservation: 900 radios, 5 second Avg. Voice Call, between 90 and 95%
reliability
• 75% Periodic Window Reservation: 750 radios, 7.5 second Avg. Voice Call, between 90 and 95%
reliability
• 60% Periodic Window Reservation: 600 radios, 10 second Avg. Voice Call, just under 90% reliability
• 45% Periodic Window Reservation: 450 radios, 10 second Avg. Voice Call, just under 95% reliability
Persistent LRRP
When persistent Location Request/Response Protocol (LRRP) is enabled in Radio General Settings,
upon power-on the radio begins sending LRRP responses without receiving a new LRRP (locatioon
data) request. This reduces the traffic channel loading on the trunked channels when a large fleet of
radios are turned on during a short interval.
Send Feedback 153

MN002731A01-A
High Efficiency Data Location Update Configuration

In order to support location updates with High Efficiency Data, the GPS coordinates of the sites must be
entered into both the radio and either the OTA Data Gateway or the MNIS Data Gateway.
Multi-Site Roaming Optimization

Multi-site roaming can be optimized to achieve the following objectives: roaming to the best site,
reducing unnecessary roaming, and reducing “bounce back and forth” roaming (that is, bounced
roaming). The best site is meant to be the most favorable site as evaluated by the radio at the moment
when roaming is attempted. It is also desired that the radio roams when it is expected to roam. Bounced
roaming is not expected, because it creates frequent registrations that burden the control channel
unnecessarily. Bounced roaming also causes the radio to spent longer time away from the control
channel, which leads to missing important calls.
Optimization of multi-site roaming requires that several parameters be determined and configured into
the radio and the infrastructure. The process generally involves determining the parameters that affect
roaming, such as roamable sites, site adjacency, received signal thresholds, site preference, and
frequency reuse.
The term “roaming” is used in this document to denote automatic roaming, an activity not initiated by a
user request. Roaming that is requested by the user is explicitly called “manual roaming” or “manual site
search”.
Roamable Sites
All sites to which a radio is allowed or roam or expected to roam must be configured into the radio. In a
multi-site network, not all sites in the network are roamable site. Some sites may not be roamable for
technical reasons, such as a frequency band difference. Other reasons include an administrative or
operational arrangement that requires some radios to be inhibited or blocked from roaming to certain
sites.
For example, Figure 37 on page 155 shows a DMR3-System-1 network with four radio sites using
different frequency bands. In this example, the boundary of the site coverage is determined by the
threshold value for acceptable signal strength, which can be configured into the radio. Site-1 and Site-3
operate in VHF/UHF band, while Site-2 and Site-4 in 800 MHz / 900 MHz band. Three radios are given:
Radio-A (VHF/UHF), Radio-B (800 MHz / 900 MHz) and Radio-C (VHF/UHF).
Radio-A is configured with DMR3-System-1 containing Site-1 and Site-3 only, because this radio can
roam to only sites using the VHF/UHF band. Radio-B is configured with the same DMR3-System-1 that
contains only Site-2 and Site-4, because this radio can only roam to 800 MHz / 900 MHz sites.
Radio-C, which operates in the VHF/UHF band, is configured with DMR3-System-1 that contains only
Site-3, because this radio is used as a control station or used in a telemetry application, whose location
is fixed under the coverage of Site-3, and therefore, there is no need for roaming.
Figure 38 on page 155 summarizes the network and sites to be configured into each radio. On the
infrastructure side, however, the configured DMR3-System-1 system must contain all of these sites. A
list of sites can be created and configured into the radio. This list of sites should contain sites that are
roamable by the radio. A different list of sites can be created and configured into a different radio. Sites
that are not roamable but are configured into the radio can slow down the roaming, because the radio
then unnecessarily attempts to reach those unroamable sites during site searching.
154 Send Feedback

MN002731A01-A
Figure 37: System With Four Sites Using Different Bands
Figure 38: Roamable Sites Configured in Radio-A, Radio-B and Radio-C
Site Adjacency
Site adjacency defines which sites are adjacent to each site. This information is configured in the
infrastructure and announced over the air at every site, to help radios with roaming. The radios receive
the announcement about the sites adjacent to the home site, that is, the site where the radio is
registered at the time.
Send Feedback 155

MN002731A01-A
Information about site adjacency is meant to help the radio with roaming, and therefore adjacent sites
must be roamable sites for the radio. Also, adjacent sites should have overlapping coverage with the
home site. Sites that are configured to be adjacent but do not overlap with the home site slow the radio’s
searching of sites in the site neighborhood.
As for an example, by referring to Table 35, the following shows adjacency information that needs to be
configured in the infrastructure:
Table 35: Site Adjacency of Network Shown in Figure 37 and Figure 38
Number Site Adjacent Sites
1 Site-1 Site-3
2 Site-2 Site-4
3 Site-3 Site-1
4 Site-4 Site-2
Site adjacency should be reciprocal to support roaming in both directions between two sites. For
example, if Site-3 is configured to be adjacent to Site-1, then Site-1 should also be configured to be
adjacent to Site-3.
In a dense urban area with high traffic, co-located sites are common practice to increase the traffic that
can be served in this area. All co-located sites should be configured as adjacent to each other, to speed
roaming among these sites.
For example, if Site-1a and Site-1b, which operate in the VHF/UHF band, are added and co-located with
Site-1, the network would be similar to the network shown in Figure 39. The corresponding site
adjacency would be as described in Table 36 on page 157.
Figure 39: Network With Co-Located Sites
156 Send Feedback

MN002731A01-A
Table 36: Site Adjacency With Co-Located Sites
Number Site Adjacent Sites
1 Site-1 Site-3, Site-1a, Site-1b
2 Site-1a Site-1, Site-3, Site-1b
3 Site-1b Site-1, Site-3, Site-1a
4 Site-2 Site-4
5 Site-3 Site-1, Site-1a, Site-1b
6 Site-4 Site-2
Site Model for Roaming

For roaming, two important threshold parameters for received signal, the Acceptable RSSI Threshold
and the Roaming RSSI Threshold, can be configured into the radio. These thresholds divide the site
coverage into three concentric circular areas based on their signal strength:
• The strong signal area
• The acceptable signal area
• The poor signal area
The out of range area is defined as the area beyond the maximum site coverage determined by the
radio receiver sensitivity.
The roaming behavior of a radio differs among these areas as follows:
• In the strong signal area, the radio does not attempt roaming as the signal is regarded as strong
and there is no need for roaming. This is the no-roaming area. However, the radio still attempts to
roam when detecting the following conditions:
• Communication failure with the control channel repeater
• Request for manual site search initiated by the user
• Home site entering site-trunking mode
• In the acceptable signal area, the radio actively attempts to roam, and roams when detecting any
adjacent site with signal strength at least 6 dBm greater than the home site. This area is the
roaming-in-acceptable area. The radio also roams when detecting the following conditions:
• Communication failure with the control channel repeater
• Request for manual site search invoked by the user
• Home site entering site-trunking mode
• Any adjacent site with acceptable signal strength that has a higher preference level
Figure 40 shows the site coverage model for roaming.
• In the poor signal area, the radio actively attempts to roam and roams when detecting any adjacent
site with acceptable signal. This is the roaming-in-poor area. Any other conditions as applicable to
the roaming-in-acceptable area also may cause roaming.
Send Feedback 157

MN002731A01-A
• In the out-of-range area, the radio has no communication with the site control channel repeater,
because the received signal is less than the radio sensitivity, and therefore the radio does not
register with any site. The radio is in constant site searching. When the radio finds a site whose
signal is greater than the radio receiver sensitivity and can be validated successfully, the radio roams
to this site.
Figure 40: Site Coverage Model for Roaming
Acceptable RSSI Threshold

This threshold determines the coverage area where the radio receives a signal, whose strength is
sufficient to establish and maintain communication with the base repeater, either for a control channel or
for a trunked channel. Occasional failure that causes the radio to roam is regarded as acceptable.
Radios beyond the coverage area receive poor or weak signal, which can cause communication failure,
such as frequent loss of synchronization. This rate of failure may not be acceptable in regard to the
quality of service that the site is expected to offer. Therefore, this threshold can also be used to
determine the service coverage area where the site can provide service with acceptable quality. Upon
failure due to the weak signal, the radio should have the opportunity to roam into any configured
adjacent sites. That this acceptable signal boundary should also be used to determine the overlapping
area of site adjacency.
Acceptable RSSI Threshold can be configured on the radio to a value ranging from a minimum -120.00
dBm to a maximum -70.00 dBm, with a default of -108.00 dBm. The default value is expected to be
practical for most urban or suburban service coverage scenarios. Adjustment of this threshold is
necessary when planning the network to cover other scenarios, such as rural areas or multi-floor
buildings. Care should be taken when decreasing or increasing the Acceptable RSSI Threshold from its
default value.
A low Acceptable RSSI Threshold can cause the radio to experience imbalance coverage, a condition in
which the radio’s signal cannot reach the base repeater, while the radio still receives an acceptable
signal. It is better for the radio to roam to an adjacent site before experiencing imbalance coverage.
158 Send Feedback

MN002731A01-A
A high Acceptable RSSI Threshold can easily cause the radio to enter a poor signal area. When this
occurs, the radio may not be able to establish and maintain communication with the home site if the poor
area is not covered by any adjacent site.
In some multi-site network coverage scenarios, such as isolated sites in rural areas or multi-floor
coverage, a high or low Acceptable RSSI Threshold is set in order to obtain expected roaming behavior.
Roaming RSSI Threshold

The Roaming RSSI Threshold divides the acceptable signal coverage into no-roaming and roaming-
in-acceptable area. It also determines the strong signal area within the acceptable signal coverage.
This parameter is configurable on the radio and can have a value ranging from a minimum -120.00 dBm
to a maximum 0.00 dBm, with a default of -100.00 dBm.
When the Acceptable RSSI Threshold is set to its default value, the default value of Roaming RSSI
Threshold approximately corresponds to a no-roaming area whose range is approximately 60% of the
range of the roaming-in-acceptable area, as illustrated in Figure 41 on page 159.
Figure 41: Boundary of Strong Signal Area Determined by Default RSSI Sampling Threshold
The default value can be adjusted to affect radio roaming behavior. Increasing the Roaming RSSI
Threshold increases the roaming-in-acceptable area, and therefore increases the chance for the radio
to roam. Decreasing the Roaming RSSI Threshold decreases the roaming-in-acceptable area, which
also increases the no-roaming area.
The roaming-in-acceptable area can be increased to encourage the radio to search for another site.
On the other hand, the no-roaming area can be increased to keep the radio to stay at the home site
rather than attempt roaming.
Figure 42 shows the impact of adjustments to the Roaming RSSI Threshold on radio roaming behavior:
• Radio-A, which registers with Site-1, does not attempt to automatically roam to Site-2, because the
radio is within the no-roaming area of Site-1. Radio-A stays at Site-1 even though the radio may
receive a significantly higher signal strength from Site-2, or even if Site-2 has a higher preference
than Site-1.
• Radio-B, on the other hand, attempts to automatically roam to Site-1, and this radio roams when the
received signal from Site-1 is significantly higher than the received signal from Site-2.
Send Feedback 159

MN002731A01-A
Figure 42: Impact of Adjustments to Roaming RSSI Threshold on Automatic Roaming
Typical Multi-Site Network Coverage

In the real field application, four basic multi-site network coverage types are commonly found. They are
presented here together with recommended setting for Acceptable RSSI Threshold and Roaming RSSI
Threshold.
Dense Overlapping Coverage (Urban)

This type of coverage, as shown in Figure 43, consists of dense sites with generous overlap. This
coverage type is often found in large cities or highly populated areas. The site neighborhood contains
many sites, so that the radio may have many adjacent sites. A radio user may be within coverage of
three to four sites at a time. No overlapping sites may reuse the trunked channel frequencies.
Reuse of the control channel frequencies is recommended for the sites that do not share any adjacent
site, though they are not overlapping. Man-made facilities such as tunnels, buildings, and concrete walls
are common obstacles in the signal path. The default values of Roaming RSSI Threshold and
Acceptable RSSI Threshold are recommended. These values give sufficient roaming area for the radio
to search adjacent sites that provide better coverage.
160 Send Feedback

MN002731A01-A
Figure 43: Dense Overlapping Multi-site Coverage
Isolated No Overlapping Coverage (Rural)

This type of coverage, as shown in Figure 44 on page 162, consists of isolated sites with no overlap.
This coverage type is often configured for isolated sites in rural areas, although it also could be
configured to cover a single part of a small city. The site neighborhood contains only one site with no
adjacent sites. Because sites do not overlap each other, they may reuse frequencies for both trunked
and control channel. Care should be taken in planning, so that the maximum coverage, as determined
by the radio receiver sensitivity, does not also overlap.
A radio user can only be within coverage of one site at any time. Therefore there is no need for the radio
to attempt roaming, and the Roaming RSSI Threshold can be configured as low as the Acceptable RSSI
Threshold.
The Acceptable RSSI Threshold can also be configured as low as the radio sensitivity -120.00 dBm for
the base repeater signal to reach the maximum range. Possible risk with such a low Acceptable RSSI
Threshold is the imbalance coverage condition when the radio signal cannot reach the base repeater. It
can happen especially when using handheld portable radios.
Send Feedback 161

MN002731A01-A
Figure 44: Isolated No Overlapping Multi-site Coverage
Corridor Coverage
This type of coverage, as shown in Figure 45 on page 163, consists of in-series slightly overlapping
sites. This coverage type is often used for highways, train tracks, shorelines, or rivers. The site
neighborhood contains only two adjacent sites in most cases. No overlapping sites may reuse the
trunked channel frequencies. Sites that do not share common adjacent sites may reuse the control
channel frequencies. For example, Site-1 and Site-4 reuse the control channel frequencies.
A radio can only be within coverage of one to two sites at a time. With slightly overlapping sites, a
recommended value for Roaming RSSI Threshold is -106 dBm, to cover the thin overlapping roaming
areas, while the Acceptable RSSI Threshold is kept at the default value.
162 Send Feedback

MN002731A01-A
Figure 45: Corridor Multi-site Coverage
Multi-Floor Coverage
This type of coverage consists of dense extremely close sites with short range coverage and generous
overlap, as shown in Figure 46 on page 164. This coverage type is often used for tall buildings or deep
tunnels. This coverage type also often encounters quick signal strength reductions due to the nature of
in-building coverage. Same frequency reuse strategy as in the corridor coverage can be configured.
A radio can only be within coverage of one to two sites at a time due to signal barriers among the sites of
different floors. The site neighborhood is small because a site may overlap with only the sites above and
below it. Though there is a small neighborhood, sites have generous overlapping areas, and therefore
the Roaming RSSI Threshold is set at -96.00 dBm.
Send Feedback 163

MN002731A01-A
Figure 46: Multi-floor Multi-site Coverage
Table 37 summarizes the suggested setting for the RSSI thresholds as the guidelines. Adjusting the
thresholds to align with the actual field environment should be considered. The suggested values
assume the site coverage with a perfect circle boundary, which is not always the actual condition. The
roaming area also assumes that the radio frequency coverage is balanced between outbound and
inbound coverage. In other words, if the base repeater signal can reach the radio within the roaming
area, the radio signal can reach the base repeater too. Failure to plan a balanced coverage can lead a
radio to frequently attempt roaming to an adjacent site where the radio cannot register because the
inbound signal cannot reach the base repeater.
Table 37: Recommended Threshold Settings
Acceptable Roaming
RSSI RSSI Approx. % of
Threshold Threshold outer range
Number Network Coverage Type (dBm) (dBm) for roaming
Dense Overlapping Coverage (Urban) -108.00 -100.00 40.00%
Isolated No Overlapping Coverage -120.00 -120.00 Out of range

(Rural)
Corridor Coverage -108.00 -106.00 10.00%
Multi-Floor Coverage -108.00 -96.00 50.00%
164 Send Feedback

MN002731A01-A
Determining Site Preference Level

Setting a preference level for a site is a way to alter radio roaming behavior to speed up the radio in
finding the preferred site. A site configured in the radio can have a preference level. Four preference
levels are provided, ranging from Preference Level 1 (least preferred) to Preference Level 4 (most
preferred). By default, a configured site has a Preference Level 2, which can be changed to a higher or
lower level to suit particular user mobility.
Preference level takes effect only when the radio is attempting roaming. This means that the radio is in
the roaming-in-acceptable area, or the radio is in no-roaming area of a site that is in site trunking
mode. Preference level also takes effect when an event causes the radio to attempt roaming, such as
failure on the control channel or manual site search request.
In the example illustrated in Figure 47, Site-1 and Site-2 are configured into Radio-A and Radio-B. Both
Radio-A and Radio-B register with Site-1. The site preference level as configured into Radio-A and
Radio-B is shown in Table 38.
• Radio-A does not roam to Site-2, though the radio receives the signal from Site-2 as acceptable and
the signal may be higher than the received signal from Site-1, because Radio-A is within the no-
roaming are of Site-1.
• Radio-B, on the other hand, may roam to Site-2, though the received signal from Site-2 is lower (but
acceptable) than the received signal from Site-1, because Radio-B is within the roaming-in-
acceptable area of the Site-1.
Figure 47: Impact of Setting Preference Level
Table 38: Configured Site Preference Level in Radio-A and Radio-B for Network in Figure 47
Preference Level as Configured in Preference Level as Configured in

Number Site Radio-A Radio-B
1 Site-1 Preference Level 2 Preference Level 2
2 Site-2 Preference Level 3 Preference Level 3
Send Feedback 165

MN002731A01-A
Determining preference level for a site depends very much on the user mobility and the site strategy.
Information on the user mobility can be used to determine the sites where the radio registers most of the
time, and the sites to which the radio frequently roams, or even the sites to which the radio seldom or
never roams. Understanding the site strategy in a multi-site environment is useful in determining the site
preference level. Some sites may be configured as a micro-site or infill site, to fill small blind-spot areas
not covered by main sites. Therefore a radio is encouraged to select one site rather than the other when
the radio is within the overlapping area.
The general rule in setting the site preference level is to increase, from its default value, the preference
level of the sites where the radio prefers to be within the site, and to decrease the preference level, from
its default value, of the sites where the radio prefers not to be within the site.
The following sections present some examples of how to set the preference level for some scenarios.
Preference Level Based on User Mobility

Figure 48 illustrates an example to determine the preference level based on the user mobility. A user
with Radio-A is stationed in Site-1, with frequent roaming to the Site-2 rather than to the Site-3. This user
also seldom travels to Site-4 and thus seldom roaming to this site. The recommended preference level
as configured in the Radio-A is shown in Table 39.
Figure 48: User Mobility Used to Determine Site Preference Level
Table 39: Recommended Site Preference Level for Sites as Illustrated in Figure 48
Number Site Preference Level Configured in Radio-A
1 Site-1 Preference Level 4
166 Send Feedback

MN002731A01-A
Preference Level Based on Site Strategy (Infill Sites)

Infill sites cover blind-spot areas not covered by the main sites within the service coverage of a multi-site
network. Blind-spot areas exist commonly due to the signal from the main sites, which cannot reach the
areas because of obstacles or out of the maximum range of the main sites. An infill site has usually
fewer resources such as number of trunked channels or lower power of the base repeater.
For example, Figure 49 illustrates the use of Site-3 as an infill site to provide bridging coverage between
the main sites, Site-1 and Site-2, which cover two dense urban areas. Users may travel frequently
between Site-1 and Site-2 and want to have continuous communication without any disruptions. Site-3
may have a base repeater with low power that provides shorter range, and may have just enough
trunked channels to serve the few users who are temporarily within the Site-3 while traveling. Therefore,
the radio is not intended to stay within Site-3 for a long time. As soon as the radio can receive an
acceptable signal from Site-1 or Site-2, the radio roams to one of the main sites. Table 40 gives the
recommendation for setting the preference level.
Figure 49: Infill Site Strategy Used for Determining Site Preference Level
Table 40: Recommended Site Preference Level for Sites Shown in Figure 49
Preference Level Configured in Radio-

Number Site A
Preference Level Based on Site Strategy (Co-located Sites)

Co-located sites are sites that cover the same geographical area. Their coverage areas overlay each
other. Co-located sites are used to serve a highly dense urban area by providing more sites to cover the
same geographical area. Providing more sites means providing more network resources, such as
control channels and trunked channels for the users. This multi-site environment requires balance in
using network resources among radios. This balance can be achieved by grouping the radios and
configuring site preference levels for each group of radio.
Send Feedback 167

MN002731A01-A
Figure 50 shows Site-1, Site-2, and Site-3, which are co-located and cover the same geographical area.
Radios within this coverage can be grouped into Group A, Group B, and Group C. In order to balance
the use of network resources, Group A radios should select Site-1, Group B radios should select Site-2,
and Group C radios should select Site-3. The site preference level can be configured differently for each
group. Table 41 recommends the preference level settings for each site and radio group.
Figure 50: Co-located Sites Strategy Used to Determine Site Preference Level
Table 41: Recommended Site Preference Level for Sites Shown in Figure 50
Preference Level Preference Level Preference Level

Configured in Group Configured in Group Configured in Group
Number Site A Radios B Radios C Radios
1 Site-1 Preference Level 3 Preference Level 2 Preference Level 2
Call Priority Optimization

A Capacity Max system allows its administrator to configure the priority of a radio (or console) and the
priority of a talkgroup. The priority range for a radio or a talkgroup is 1 (highest) to 10 (lowest).
The priority of a talkgroup call is the maximum (smaller number) of the source radio’s priority and the
talkgroup’s priority. The priority of an individual call is the maximum (smaller number) of the source
radio’s priority and the target radio’s priority.
It is recommended to configure the priority of a radio or talkgroup based on the importance of the radio
or talkgroup and not based on how frequently the radio or talkgroup is used.
In a Capacity Max system the priority levels of Emergency call and All call are higher than other call
types. The Emergency or All call priority is independent of the configured radio and talkgroup priority.
Example of Call Priority

This example shows the configuration of radio and talkgroup (TG) priorities and corresponding call
priorities:
Priority of Radio 1 = 7
Priority of Radio 2 = 8
168 Send Feedback

MN002731A01-A
Priority of TG1 = 5
Priority of Console 10 = 2
• A call from Radio1 to TG1 will have a call priority = 5 (higher priority of 5, 7)
• A call from Radio1 to Radio2 will have a call priority 7 (higher priority of 7, 8)
• A call from Console10 call to Radio1 will have a call priority 2 (higher priority of 2, 7)
• A call from Console 10 call to TG1 will have a call priority 2 (higher priority of 2, 5)
Use of Call Priority in the System

During call setup, Emergency voice calls and All calls (site wide or multi-site) are given higher call
priority than any other call types. When all available trunked channels at a site are busy, emergency
calls and All calls are assigned a channel by pre-empting a busy channel at the site instead of queuing
the call.
The start of an Emergency call or All call is announced on all busy trunked channels of all the sites
associated with the call. This informs the start of an Emergency or All call to all the radios that are
receiving calls on the trunked channels. The radios that are interested in the Emergency or All call leave
the current trunked channel and move to a trunked channel where the higher priority emergency or All
call is set up. An emergency voice call has higher priority than a site or multi-site All call. A site or multi-
site All call has a higher priority than other call types.
When Call Queuing is enabled, a call is placed in the busy queue when an idle channel is not available
at any of the sites where call has to be setup (for example, affiliated sites of a talkgroup). A Capacity
Max system requires an idle channel at all the affiliated sites to set up a call (All Start).
For all the call types (excluding Emergency voice call and All call) that require a trunked channel, if an
affiliated site is busy, the call is queued according to the call priority. Higher priority calls are placed in
the busy queue ahead of lower priority calls. For calls with the same priority, earlier received calls are in
the queue ahead of later received calls. When channels become idle, they are assigned to higher priority
calls.
Send Feedback 169

MN002731A01-A
170 Send Feedback

MN002731A01-A
Capacity Max Hardware Specifications
Appendix A
Capacity Max Hardware Specifications A
An important aspect of installing a Capacity Max system is determining how and where the equipment
will fit into the customer’s sites. The relevant hardware specifications (dimensions, power consumptions,
operating temperature, and so on) are provided for the following fixed end equipment:
• Capacity Max System Server (CMSS)
• Repeaters
• IP network equipment
The RF receiving and combining equipment and antenna space on the tower should also be considered,
although this information is not provided here.
Some of the system software can be installed on PCs not provided by Motorola Solutions. The computer
specifications for the following software are provided:
• Radio Management (Server, Client, Device Programmer, Tuner)
• Battery Management (Server, Client, Proxy)
• System Advisor Client
• ESU Client
CMSS Hardware Specifications

Table 42 lists the CMSS Capacity Max System Server (CMSS) hardware specifications.
Table 42: Capacity Max System Server (CMSS) Specifications
Height 8.73 cm (3.44 in)
Width 44.54 cm (17.54 in)
Depth 73.02 cm (28.75 in)
Weight 23.5 kg (51.5 lb)
Operating Temperature 10 ° to 35 ° C (50 ° to 95 ° F) at sea level with an altitude derating of 1.0 ° C per
every 305 m (1.3 ° F per every 1000 ft) above sea level to a maximum of
3050 m (10,000 ft), no direct sustained sunlight.
Maximum rate of change is 20 ° C per hr (36 ° F per hr). The upper limit and rate of
change may be limited by the type and number of options installed.
System performance during standard operating support may be reduced if

operating with a fan fault or above 30 ° C (86 ° F).
Non-operating -30 ° C to 60 ° C (-22° F to 140 ° F)

temperature
Maximum rate of change is 20° C per hr (36 ° F per hr).
Send Feedback 171

MN002731A01-A
Appendix A: Capacity Max Hardware Specifications
Table 42: Capacity Max System Server (CMSS) Specifications (Cont.)
Operating Relative Minimum to be the higher (more moisture) of -12 ° C (10.4 ° F) dew point or 8%
Humidity relative humidity. Maximum to be the lower (less moisture) or 24 ° C (75.2 ° F) dew
point or 90% relative humidity.
Operating Altitude 3050 m (10,000 ft). This value may be limited by the type and number of options
installed. Maximum allowable altitude change rate is 457m/min (1500 ft/min).
Non-operating Altitude 9144 m (30,000 ft). Maximum altitude change rate is 457m/min (1500 ft/min).
Operating Input Voltage 100 VAC to 240 VAC

Range
AC Power 100 VAC to 240 VAC, 50-60 Hz
Power Consumption 800 W @ 120 V
800 W @ 240 V
Input Current Drain 9.4 A @ 100 VAC
4.5 A @ 200 VAC
Repeater Hardware Specifications

This section contains hardware specifications for repeaters.
MTR 3000 Repeater

Table 43 lists the hardware specifications for an MTR 3000 repeater.
Table 43: MTR 3000 Repeater Specifications
Height 5.25 in (3 RU)
Width 19 in
Depth 16.5 in
Weight 19 kg (40 lb)
Band VHF UHF 800 MHz /

900 MHz
Frequency 136-174 MHz 403-470 MHz 470-524 MHz
Tx Power 100 W 100 W 100 W 100 W
Power Consumption AC 410 W 340 W 380 W 390 W
DC 350 W 300 W 320 W 340 W
Operating Temperature -30 ° C to 60° C (-22 ° F to 140 ° F)
172 Send Feedback

MN002731A01-A
XPR 8400 Repeater

Table 44 lists the hardware specifications for an XPR 8400 repeater.
Table 44: XPR 8400 Repeater Specifications
Width 19 in
Depth 11.7 in
Band VHF UHF
Frequency 136-174 MHz 403-470 MHz 450-512 MHz
Tx Power 25 W 45 W 25 W 40 W 40 W
Power Consumption AC 300 W 400 W 300 W 400 W 400 W
DC 100 W 160 W 100 W 160 W 160 W
Operating Temperature -30 ° C to 60 ° C (-22 ° F to 140 ° F)
XPR 8380 Repeater

The following are the hardware specifications for an XPR 8380 repeater.
Table 45: XPR 8380 Repeater Specifications
Width 19 in
Depth 11.7 in
Band 800 MHz / 900 MHz
Frequency 806-870 MHz 896-941 MHz
Tx Power 35 W 30 W
Power Consumption AC 400 W 400 W
DC 130 W 130 W
SLR 5700 Repeater

The following are the hardware specifications for an SLR 5700 repeater.
Table 46: SLR 5700 Repeater Specifications
Width 19 in
Send Feedback 173

MN002731A01-A
Table 46: SLR 5700 Repeater Specifications (Cont.)
Depth 14.6 in
Weight 8.6 kg (19 lb)
Band VHF UHF
Frequency 136-174 MHz 400-470 MHz
Tx Power 50 W 50 W
Power Consumption AC 180 W 180 W
DC 130 W 130 W
Hardware Specifications for Recommended IP Network Equipment

The following sections contain hardware specifications for the recommended IP network equipment.
Specifications for IP Network Routers

This section contains hardware specifications for IP network routers.
MSR 2003 AC Router Specifications

Table 47 lists the hardware specifications for a Hewlett Packard MSR 2003 AC Router.
NOTICE:
Maximum power rating is the worst-case theoretical maximum numbers provided for planning the
infrastructure with 100% traffic, all ports plugged in, and all modules populated. Please see the
manufacturer for additional specifications.
Table 47: Hewlett Packard MSR 2003 AC Router Specifications
Width 14.17 in
Depth 11.81 in
Operating Temperature 0 ° C to 45 ° C (32 ° F to 113 ° F)
Maximum Power Rating 54W
AC Input Voltage 100VAC to 240 VAC
AC Input Frequency 50 Hz to 60 Hz
174 Send Feedback

MN002731A01-A
Cisco 2911 Router Specifications

Table 48 lists the hardware specifications for a Cisco 2911 Router.
NOTICE:
Please see the manufacturer for additional specifications.
Table 48: Cisco 2911 Router Specifications
Width 17.25 in
Depth 12 in
Weight 18 lb
Operating Temperature @ 1,800 m (5,906 ft) Altitude:

0 ° C to 40 ° C (32 ° F to 104 ° F)
Typical Power (No Modules) 50W
Maximum Power with AC Power Supply 210W
AC Input Voltage 100 VAC to 240 VAC

(Auto Ranging)
DC Input Voltage 24 VDC to 60 VDC

(Auto Ranging Positive or Negative)
DC Input Current (MAX) 8A (24V)

3.5A (60V)
Specifications for IP Network Switches

This section contains hardware specifications for IP network switches.
Procurve 2530-24 Switch Specifications

Table 49 lists the specifications for a Hewlett Packard Procurve 2530-24 Switch.
NOTICE:
Maximum power rating is the worst-case theoretical maximum numbers provided for planning the
infrastructure with fully loaded PoE (if equipped), 100% traffic, all ports plugged in, and all
modules populated. Please see the manufacturer for additional specifications.
Table 49: Hewlett Packard Procurve 2530-24 Switch Specifications
Width 17.4 in
Dept 9.7 in
Operating Temperature 0 ° C to 45 ° C (32 ° F to 113 ° F)
Send Feedback 175

MN002731A01-A
Table 49: Hewlett Packard Procurve 2530-24 Switch Specifications (Cont.)
Maximum Power Rating 14.7W

200 VAC to 240 VC
Cisco 3650 Switch Specifications

Table 50 lists the hardware specifications for a Cisco 3650 Switch.
NOTICE:
Weight includes the chassis assembly as it is shipped: three fans, two Stackwise adapters, and
one power supply blank. The weight also includes the default power supply that is shipped with
the unit. Please see the manufacturer for additional specifications for the Operating Temperature.
Table 50: Cisco 3650 Switch Specifications
Width 17.5 in
Depth 17.625 in
Weight 24T: 6.87 kg (15.15 lb)
24P: 7.26 kg (16 lb)
Operating Temperature AC: -5 ° C to +45 °C, up to 5000 ft (1500m)
DC: -5 ° C to +45 ° C, up to 6000 ft (1800m)
Power Consumption 24T: No more than 55.21W

(Weighted Average)
24P: No more than 64.18W
DC Input Voltage -36 VDC to -72 VDC
DC Input Current 21A to 10.5A
Specifications for Computer Hosting Applications

Some software for the Capacity Max system must be installed on PCs. All software listed can coexist on
the same computer and run at the same time if the computer meets the sum of their specifications.
Minimum computer specifications are provided for the following software applications:
• Radio Management (Server, Client, Device Programmer, Tuner)
• Battery Management (Server, Client, Proxy)
• System Advisor Client
• ESU Client
176 Send Feedback

MN002731A01-A
Radio Management Computer Specifications

The Radio Management software can be installed on any PC that meets the following computer
specifications.
Operating System Requirements

Standalone Radio Management Client (CPS), Standalone Radio Management Device
Programmer, or Tuner:
• Windows 10, 32-bit and 64-bit
• Windows 8, Windows 8.1, 32-bit and 64-bit
• Windows 7 Home Premium or Professional (SP1 or higher) 32-bit and 64-bit
Radio Management Client (CPS) with Radio Management Server and Radio Management Device
Programmer:
• Windows 10, 64-bit
• Windows 8, Windows 8.1, 64-bit
• Windows 7 Home Premium or Professional (SP1 or higher), 64-bit
• Windows Server 2008 R2 SP1, 64-bit
Recommended Hardware Requirements for Small Fleets

Typical hardware requirements for a small fleet size of <1000 radios are:
• Processor: 2 GHz dual core or higher Pentium grade processor
• Memory: 4 GB RAM
• Aero capable graphics card with 128 MB graphics memory
• 50 GB free hard disk space on a 5400 RPM hard disk drive
• USB Port for radio communication
• DVD-ROM for software installation
NOTICE:
Managing more than 1000 radios requires more processing power in the server than indicated in
this list. See the Radio Management Deployment Guide for details on selecting the appropriate
hardware for specific deployments and fleet sizes.
Battery Management Computer Specifications

Battery Management software can be installed on any PC that meets the following computer
specifications.

• Windows 7 x86 and x64
Send Feedback 177

MN002731A01-A
• Windows 8 x86 and x64
• Windows Server 2003 x86 and x64
• Windows Server 2008 x86 and x64
• Windows Server 2008 R2 x64
Hardware Minimum Requirements

The IMPRESTM Battery Fleet Management application can be installed on either a client/proxy computer
or a server computer. Although the installation package is the same for client and server computers, the
hardware installation requirements are different for each.
Server Hardware Minimum Requirements:
• DVD drive (not required if software downloaded from website)
• 1 GB of hard disk space
• 2 GB RAM
Client/Proxy Hardware Minimum Requirements:
• 1 USB (Universal Serial Bus) Port
• DVD drive (not required if software downloaded from website)
• 200 MB of hard disk space
• 1 GB RAM
MNIS Data Gateway Computer Specifications

The Data Gateway (MNIS) software can be installed on any PC that meets the following computer
specifications.

• Windows 8, Windows 8.1, 32-bit and 64-bit
• Windows 7 Home Premium or Professional (SP1 or higher) 32-bit and 64-bit
• Windows Server 2008 R2 SP1 32-bit and 64-bit

• 1 GB RAM
NOTICE:
Running multiple instances of MNIS on the same hardware is not supported.
178 Send Feedback

MN002731A01-A
System Advisor Client Computer Specifications

The System Advisor Client software can be installed through a web browser on any PC that meets the
following computer specifications.

• Windows 7 and above

• 2 GB RAM
Software Requirements
• Recent versions of IE, Chrome or Firefox.
• Recent versions of Oracle Java 8 32-bit (v1.8.0_66 or greater)
ESU Client Computer Specifications

The ESU Client software is accessed through a web browser on any PC that meets the following
computer specifications.
Software Requirements
• A web browser that supports HTML5:
• Internet Explorer v10
• Firefox v40
• Chrome v43
Send Feedback 179

MN002731A01-A
Chapter A: Capacity Max Hardware Specifications
180 Send Feedback

MN002731A01-A
Common System Configurations and Recommended IP Plans
Appendix B
Common System Configurations and

Recommended IP Plans B
To simplify deployment of common system configurations, several example systems and their
corresponding recommended IP plans are provided in this appendix.
The illustrated system configurations are summarized in Table 51. These configurations can be used as
a basis for creating more complex Capacity Max systems.
Table 51: Common System Configurations
Ethernet
Number CMSS Switch Description of System
of Sites Redundancy Redundancy Applications Configuration in This Appendix
1 No No No Quick Setup Reference System #1 on

page 182
1 Co-Located Yes No Quick Setup Reference System #2 on

Hardware page 186
1 No No Yes Quick Setup Reference System #3 on

page 191
2 No No Yes Quick Setup Reference System #4 on

page 195
4 Geographic Yes Yes Quick Setup Reference System #5 on

page 201
In the IP Plan descriptions in this appendix, the text colors are used as follows:
• Black – a basic configuration
• Red – items added to the basic configuration to provide redundancy
• Green – items added to the basic configuration to support applications
• Violet – items added to the basic configuration to support multi-site
Send Feedback 181

MN002731A01-A
Appendix B: Common System Configurations and Recommended IP Plans
Quick Setup Reference System #1

Figure 51: Reference System #1 for Single Site and Four Repeaters
Table 52: Reference System #1 Configuration for Single Site and Four Repeaters
Device or Location Configuration Details
System Common Trunk Controller: 172.20.36.1
SNMP Server: 172.20.36.5
Site Common Subnet Address: 172.16.1.0
Subnet Mask: 255.255.255.0
Default Gateway: 172.16.1.20
Repeater 1 (Control Channel Capable) Repeater Number: 1
Redundancy Group: 0
Repeater 2 Repeater Number: 2
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
182 Send Feedback

MN002731A01-A
Table 52: Reference System #1 Configuration for Single Site and Four Repeaters (Cont.)
Router WAN: DHCP Enabled
Loopback IP Address: 172.30.16.1
Loopback Subnet Mask: 255.255.255.255
Radio Infrastructure IP Address: 172.16.1.20
Radio Infrastructure Subnet Mask: 255.255.255.0
Gateway Network 1 IP Address: 172.20.31.20
Gateway Network 1 Mask: 255.255.255.128
Application Network IP Address: 172.20.1.148
Application Network Mask: 255.255.255.128
DHCP Pool:
172.16.1.250 through 172.16.1.254
172.20.1.192 through 172.20.1.254
172.20.31.122 through 172.20.31.126
172.20.36.122 through 172.20.36.126
Switch IP Address: 172.16.1.16
Subnet Mask: 255.255.255.0
Capacity Max System Server Subnet Address: 172.20.36.0
Subnet Mask: 255.255.255.128
Clients DHCP Enabled (for example, 172.2.1.192)
System Advisor Server: 172.20.36.5
Radio Management Server: 172.20.31.24
Send Feedback 183

MN002731A01-A
Table 52: Reference System #1 Configuration for Single Site and Four Repeaters (Cont.)
Data Gateway Server IP Address: 172.20.31.24
Data Gateway Hosts These Subnet Mask: 255.255.5.128

Applications:
• Radio Management Server
• Radio Management Job
Processor
• Radio Management Device
Programmer
Table 53: Reference System #1 IP Address for System with Single Site and Four Repeaters
Network Type Network Element IP Address
Loopback Network Router 172.30.16.1 /32
Radio Infrastructure Network Subnet Address 172.16.1.0 /24
Registrar Agent 127.16.1.1
Control Channel Manager 172.16.1.2
Ethernet Switch 172.16.1.16
Router 172.16.1.20
Repeater 1 Management 172.16.1.24
Repeater 1 Payload 172.16.1.26
DHCP Pool 172.16.1.250 through 1.2.16.1.254
IETF Subnet Directed Broadcast 172.16.1.255
184 Send Feedback

MN002731A01-A
Table 53: Reference System #1 IP Address for System with Single Site and Four Repeaters (Cont.)
Gateway Network Subnet Address 172.20.31.0 /25
Router 172.20.31.20
MNIS Data Gateway Server 172.20.31.24
Radio Management Server 172.20.31.24
DHCP Pool 172.20.31.122 through 172.20.31.126
Subnet Address 172.20.36.0 /25
Trunk Controller 172.20.36.1
ESU 172.20.36.4
Application Network Subnet Address 172.20.1.128 /25
Router 172.20.1.148
Send Feedback 185

MN002731A01-A

NOTICE:
In a system of this type, odd numbered repeaters are attached to Switch 1, and even numbered
repeaters are attached to Switch 2. The Radio Infrastructure Network VLAN spans across both
switches.
Figure 52: Reference System #2 for Single Site, Four Repeaters, Co-location CMSS Redundancy, and
Ethernet Switch Redundancy
Table 54: Reference System #2 Configuration for with Single Site, Four Repeaters, Co-location CMSS
Redundancy, and Ethernet Switch Redundancy
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
Subnet Mask: 255.255.255.0
*Repeater 1 (Control Channel Capable) Repeater Number: 1
Redundancy Group: 0
*Repeater 2 (Control Channel Capable) Repeater Number: 2
Redundancy Group: 0
186 Send Feedback

MN002731A01-A
Redundancy, and Ethernet Switch Redundancy (Cont.)
*Repeater 3 Repeater Number: 3
Redundancy Group: 0
*Repeater 4 Repeater Number: 4
Redundancy Group: 0
Gateway Network 2 IP Mask: 255.255.255.128
SNMP Server 1: 172.20.38.5
SNMP Server 2: 172.20.37.5
DHCP Pool:
172.16.1.250 through 172.16.1.254
172.20.1.192 through 172.20.1.254
172.20.31.122 through 172.20.31.126
172.20.36.222 through 172.20.36.126
172.20.37.122 through 172.20.37.126
Switch Switch 1 IP Address: 172.16.1.16
Switch 2 IP Address: 172.16.1.17
Subnet Mask: 255.255.255.0
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
Send Feedback 187

MN002731A01-A
Capacity Max System Server 1 Subnet Address: 172.20.36.0
Subnet Mask: 255.255.255.128
Subnet Mask: 255.255.255.128
Clients DHCP Enabled (for example, 172.20.1.192)
System Advisor 1 Server: 172.20.36.5
Data Gateway Server IP Address: 172.20.31.24
Data Gateway Hosts These Applications: Subnet Mask: 255.255.5.128
• MNIS Data Gateway Default Gateway: 172.20.31.20
• Radio Management Server
• Radio Management Job Processor
• Radio Management Device

Programmer
* Odd numbered repeaters are attached to switch 1 and even numbers repeaters are attached to switch 2. The
Radio Infrastructure Network VLAN spans across both switches.
188 Send Feedback

MN002731A01-A
Table 55: Reference System #2 IP Address for Single Site, Four Repeaters, Co-location CMSS
Redundancy, and Ethernet Switch Redundancy
Ethernet Switch 1 172.16.1.16
Router 172.16.1.20
Send Feedback 189

MN002731A01-A
Table 55: Reference System #2 IP Address for Single Site, Four Repeaters, Co-location CMSS
Gateway Network Subnet Address 172.20.31.0 / 25
Router 172.20.31.20
ESU 172.20.36.3
MNIS VRC Gateway 172.20.36.4
Router 172.20.36.20
ESU 172.20.37.3
Router 172.20.37.20
Router 172.20.1.148
190 Send Feedback

MN002731A01-A

Figure 53: Reference System #3 for Single Site, Four Repeaters, and Applications
Table 56: Reference System #3 Configuration for Single Site, Four Repeaters, and Applications
Subnet Mask: 255.255.255.0
Repeater 1 (Control Channel Capable) Repeater Number: 1
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Send Feedback 191

MN002731A01-A
Table 56: Reference System #3 Configuration for Single Site, Four Repeaters, and Applications (Cont.)
DHCP Pool:
172.16.1.250 through 172.16.1.254
172.20.1.192 through 172.20.1.254
172.20.31.122 through 172.20.31.126
172.20.36.122 through 172.20.36.126
Switch IP Address: 172.16.1.16
Subnet Mask: 255.255.255.0
Default Gateway: 172.16.120
Capacity Max System Server Subnet Address: 172.20.36.0
Subnet Mask: 255.25.255.128
Data Gateway Server (host for:) IP Address: 172.20.31.24
• MNIS Data Gateway Subnet Mask: 255.255.255.128
• Radio Management Server Default Gateway: 172.20.31.20
• Location Server
• Text Message Server
• Dispatch Console Server
192 Send Feedback

MN002731A01-A
Table 56: Reference System #3 Configuration for Single Site, Four Repeaters, and Applications (Cont.)
Client DHCP Enabled (for example, 172.20.1.192)
Location Server: 172.20.31.24
Text Message Server: 172.20.31.24
Console Server: 172.20.31.24
Table 57: Reference System #3 IP Address for Single Site, Four Repeaters, and Applications
Router 172.16.1.20
Send Feedback 193

MN002731A01-A
Table 57: Reference System #3 IP Address for Single Site, Four Repeaters, and Applications (Cont.)
Gateway Network Subnet Address 172.20.31.0 / 25
Router 172.20.31.20
ESU 172.20.36.3
Router 172.20.36.20
Router 172.20.1.148
194 Send Feedback

MN002731A01-A

Figure 54: Reference System #4 for Two Sites, Four Repeaters Per Site, and Applications
Table 58: Reference System #4 Configuration for Two Sites, Four Repeaters Per Site, and Applications
Site 1 Common Subnet Address: 172.16.1.0
Subnet Mask: 255.255.255.0
Site 1 Repeater 1 (Control Channel Capable) Repeater Number: 1
Redundancy Group: 0
Site 1 Repeater 2 Repeater Number: 2
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Send Feedback 195

MN002731A01-A
Site 1 Router WAN: DHCP Enabled
NBMA IP Address: 172.30.0.1
NBMA Subnet Mask: 255.255.240.0
Application Network IP Address: 172l.20.1.148
DHCP Pool:
172.16.1.250 through 172.16.1.254
172.20.1.192 through 172.20.1.254
172.20.31.122 through 172.20.31.126
172.20.36.122 through 172.20.36.126
Site 1 Switch IP Address: 172.16.1.16
Subnet Mask: 255.255.255.0
Subnet Mask: 255.255.255.128
Radio Management Server (host for): IP Address: 172.20.36.25
• Radio Management Server Subnet Mask: 255.255.255.128

196 Send Feedback

MN002731A01-A
Data Gateway Server (host for:) IP Address: 172.20.31.24
• Location Server Default Gateway: 172.20.31.20
Client DHCP Enabled (for example, 172.20.1.192)
System Advisor 1 Server: 172.20.3
Radio Management Server: 172.20.3
Location Server: 172.20.3
Text Message Server: 172.20.3
Console Server: 172.20.3
Subnet Mask: 255.255.255.0
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Send Feedback 197

MN002731A01-A
VAM Server: 172.30.0.1
DHCP Pool:
172.16.2.250 through 172.16.2.254
Site 2 Switch IP Address: 172.16.2.16
Subnet Mask: 255.255.255.0
198 Send Feedback

MN002731A01-A
Table 59: Reference System #4 IP Address for Two Sites, Four Repeaters Per Site, and Applications
Site 1 Loopback Network Router 172.30.16.1 /32
Site 1 NMBA Network Subnet Address 172.30.0.0 /20
Router 172.30.0.1
Site 1 Radio Infrastructure Subnet Address 172.16.1.0 /24

Network
Control Channel Manager 172l.16.1.2
Router 172.16.1.20
Site 1 Gateway Network Subnet Address 172.20.36.0 / 25
ESU 172.20.36.3
Router 172.20.36.20
Router 172.20.31.20
Send Feedback 199

MN002731A01-A
Table 59: Reference System #4 IP Address for Two Sites, Four Repeaters Per Site, and Applications
Site 1 Application Network Subnet Address 172.20.1.128 /25
Router 172.20.1.148
Site 2 NBMA Network Subnet Address 172.30.0.0 /20
Router 172.30.0.2

Network
Router 172.16.2.20
200 Send Feedback

MN002731A01-A

This section describes a system with four sites, four repeaters per site, geographic CMSS redundancy,
multiple site switches, and applications installed.
NOTICE:
In a system of this type, odd numbered repeaters are attached to Switch 1, and even numbered
repeaters are attached to Switch 2. The Radio Infrastructure Network VLAN spans across both
switches.
Figure 55: Reference System #5 for Four Sites, Four Repeaters Per Site, Geographic CMSS
Redundancy, Multiple Site Switches, and Applications
Table 60: Reference System #5 Configuration for System With Four Sites, Four Repeaters Per Site,
Geographic CMSS Redundancy Multiple Site Switches, and Applications
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
Send Feedback 201

MN002731A01-A
Geographic CMSS Redundancy Multiple Site Switches, and Applications (Cont.)
Subnet Mask: 255.255.255.0
Default Gateway: 172161.20
*Site 1 Repeater 1 (Control Channel Capable) Repeater Number: 1
Redundancy Group: 0
Redundancy Group: 0
*Site 1 Repeater 3 Repeater Number: 3
Redundancy Group: 0
Redundancy Group: 0
NBMA IP Address:172.30.0.1
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
DHCP Pool:
172.16.1.250 through 172.16.1.254
172.20.1.192 through 172.20.1.254\
172.20.31.122 through 172.20.31.126
172.20.36.122 through 172.20.36.126
202 Send Feedback

MN002731A01-A
Site 1 Switches Switch 1 IP Address: 172.16.1.16
Subnet Mask: 255.255.255.0
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
Site 1 Capacity Max System Server Subnet Address: 172.20.36.1
Subnet Mask: 255.255.255.128
Site 1 Radio Management Server (hosts for:) IP Address: 172.20.36.25
• Radio Management Server Subnet Mask: 255.255.255.128
• Radio Management Job Processor Default Gateway: 172.20.36.20
Site 1 Data Gateway Server (host for:) IP Address: 172.20.31.24
• Location Server Default Gateway: 172.20.31.20
Site 1 Clients DHCP Enabled (for example, 172.20.1.192)
Subnet Mask: 255.255.255.0
Redundancy Group: 0
Send Feedback 203

MN002731A01-A
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
VAM Server: 172.30.0.1
Gateway Network IP Address: 172.20.37.20
Gateway Network Mask: 255.255.255.128
SNMP Server 1: 172.20.36.5
SNMP Server 2: 12.20.37.5
DHCP Pool:
172.16.2.250 through 172.16.2.254
172.20.2.192 through 172.20.2.254
172.20.37.122 through 172.20.37.126
Subnet Mask: 255.255.255.0
SNMP Server 1: 72.20.36.5
SNMP Server 2: 172.20.37.5
204 Send Feedback

MN002731A01-A
Site 2 Capacity Max System Server Subnet Address: 172.20.37.0
Subnet Mask: 255.255.255.128
Site 2 Clients DHCP Enabled (for example, 172.20.1.192)
Subnet Mask: 255.255.255.0
*Site 3 Repeater 1 (Control Chanel Capable) Repeater Number: 1
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Send Feedback 205

MN002731A01-A
Loopback IP Adress: 172.30.16.3
VAM Server 1: 172.30.0.1
VAM Server 2: 173.30.0.2
SNMP Server 1: 172.20.36.5
SNMP Server 2; 172.2037.5
DHCP Pool: 172.16.3.250 through 172.16.3.254
Subnet Mask: 255.255.255.0
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
Subnet Mask: 255.255.255.0
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
Redundancy Group: 0
206 Send Feedback

MN002731A01-A
VAM Server 1: 172.30.0.1
VAM Server 2: 172.30.0.2
SNMP Server 1: 172.20.36.5
SNMP Server 1: 172.20.37.5
DHCP Pool: 172.16.4.250 through 172.16.4.254
Subnet Mask: 255.255.255.0
SNMP Server 1: 172.20.36.5
SNMP Server 2: 172.20.37.5
* Odd numbered repeaters are attached to switch 1 and even numbers repeaters are attached to switch 2. The
Radio Infrastructure Network VLAN spans across both switches.
Send Feedback 207

MN002731A01-A
Table 61: Reference System #5 IP Address for Four Sites, Four Repeaters Per Site, Geographic CMSS
Redundancy Multiple Site Switches, and Applications
Router 172.30.0.1

Network
Router 172.16.1.20
Repeater 4 Payload 172.161.135
208 Send Feedback

MN002731A01-A
Redundancy Multiple Site Switches, and Applications (Cont.)
Site 1 Gateway Network Subnet Address 172.20.36.0 /25
ESU 172.20.36.3
Router 172.20.36.20
Router 172.20.31.20
Router 172.20.1.148
Router 172.30.2
Send Feedback 209

MN002731A01-A

Network
Router 172.16.2.20
Repeater 2 Management 172.162.27
Site 2 Gateway Network Subnet Address 172.20.37.0 /25
ESU 172.20.37.3
Router 172.20.37.20
Router 172.20.2.148
Router 172.30.0.3
210 Send Feedback

MN002731A01-A

Network
Router 172.16.3.20
Router 172.30.0.4
Send Feedback 211

MN002731A01-A

Network
Router 172.16.4.20
212 Send Feedback

MN002731A01-A
Configuration Files
Appendix C
Configuration Files C
This appendix contains a description of the configuration information contained in the configuration text
files that were used to configure the Ethernet routers and switches during Motorola testing.
HP MSR2003 Router Configuration File Overview

There are two methods to use the HP MSR 2003 Router configuration text files provided.
• Modify the text files to customize the configurations (experienced users) and then load the text
configuration files onto the Ethernet switch or router.
NOTICE:
Caution should be taken using this method, because a syntax error in the text file may cause a
failure to load a section or the complete configuration. A text comparison tool should always be
used to confirm the correct text modifications were made.
• Load the template configuration files onto the Ethernet switch or router and then use the Command
Line Interface to modify the configuration.
Before actually loading configuration files, review the text configuration files presented here.
The selected files are from the section for ADVPN with Encryption and Secure Protocols. Router
configuration text file with annotations for Site 1. The configuration text is in a monospaced font.
#
version 7.1.059, Release 0305
#
sysname Site1Router1
Defines the name of the router
#
clock protocol ntp
Enables Network Time Protocol (NTP) on the router
#
aspf policy 1
tcp syn-check
Creates a stateful packet policy
#
ospf 1 router-id 172.30.16.1
silent-interface GigabitEthernet0/0.10
silent-interface LoopBack0
area 0.0.0.0
network 172.16.1.0 0.0.0.255
Send Feedback 213

MN002731A01-A
Appendix A: Configuration Files
network 172.20.1.128 0.0.0.127

network 172.20.31.0 0.0.0.127
network 172.20.36.0 0.0.0.127
network 172.30.0.0 0.0.15.255
network 172.30.16.1 0.0.0.0
This section configures:
• OSPF router ID on the loopback network.
• OSPF area 0.0.0.0
• The four networks for hosts on the Local Area Network (LAN)
• The network for the tunnel end points
• The loopback network
#
dhcp enable
Enables Dynamic Host Configuration Protocol (DHCP) on the router.
#
password-recovery enable
#
vlan 1
#
#
dhcp server ip-pool application-network-dhcp-pool
gateway-list 172.20.1.148
network 172.20.1.128 mask 255.255.255.128
address range 172.20.1.192 172.20.1.254
#
dhcp server ip-pool gateway1-network-dhcp-pool
network 172.20.36.0 mask 255.255.255.128
address range 172.20.36.122 172.20.36.126
#
dhcp server ip-pool radio-network-dhcp-pool
network 172.16.1.0 mask 255.255.255.0
address range 172.16.1.250 172.16.1.254
Enables DHCP pools on the router for client machines that connect to the network on the local network.
#
controller Cellular0/0
#
interface Aux0
#
interface NULL0
#
interface LoopBack0
ip address 172.30.16.1 255.255.255.255
214 Send Feedback

MN002731A01-A
Enables a loopback address for configuration simplicity.
#
interface GigabitEthernet0/0
port link-mode route
Enables routing.
#
interface GigabitEthernet0/0.10
ip address 172.16.1.20 255.255.255.0
packet-filter 3001 inbound
#
ip address 172.20.36.20 255.255.255.128
#
ip address 172.20.31.20 255.255.255.128
#
ip address 172.20.1.148 255.255.255.128
This section configures the networks that are on the physical Gigabit Ethernet 0/0 connection (port the
HP Ethernet Switch connects to). The VLANS on the router must match the VLAN IDs on the Ethernet
Switch.
The packet-filter is applying an Access Control List to restrict traffic. If the user does not want to enable
ACLs, remove these packet-filter lines.
#
description Site1-Backhaul
ip address 192.168.1.1 255.255.255.0
aspf apply policy 1 inbound
The 192.168.1.1 is the Static IP for the backhaul network for the site. The primary ADVPN site has to
have a Static IP address as well as sites that require NAT. Every instance of this IP needs to be changed
in the file.
#
nat outbound 3013 address-group 1 port-preserved
nat server protocol tcp global current-interface 9090 inside 172.20.36.5
9090
36002
36003
50111
Send Feedback 215

MN002731A01-A

51919
nat server protocol tcp global current-interface 58041 inside
172.20.31.24 58041
These are the NAT rules to access System Advisor from the Wide Area Network.
#
interface Tunnel1 mode advpn gre
description ADVPN tunnel on hub1
ip address 172.30.0.1 255.255.240.0
ospf network-type broadcast
ospf dr-priority 255
source GigabitEthernet0/1
tunnel protection ipsec profile ipsec-profile
vam client hub1
This section configures the Tunnel End Point and parameters for the ADVPN tunnel.
#
scheduler logfile size 16
#
line class aux
user-role network-admin
#
line class tty
user-role network-operator
#
line class vty
#
line aux 0
authentication-mode scheme
This section configures the access parameters for the serial port of the router.
#
line vty 0 63
authentication-mode scheme
protocol inbound ssh
This section configures the access parameters for remote access (SSH) of the router.
#
ip route-static 0.0.0.0 0 192.168.1.254
This is the default route for the traffic at the site. If the traffic does not match any route for the Capacity
Max system, the traffic is then sent directly out the WAN port and not sent through a tunnel interface.
#
snmp-agent
snmp-agent sys-info contact "Add contact here"
snmp-agent sys-info location Site1
snmp-agent sys-info version v3
snmp-agent group v3 capacity-max privacy
216 Send Feedback

MN002731A01-A
snmp-agent target-host inform address udp-domain 172.20.36.5 params

securityname param1 v3 privacy
snmp-agent target-host inform address udp-domain 172.20.37.5 params
snmp-agent target-host trap address udp-domain 172.20.36.5 params
snmp-agent target-host trap address udp-domain 172.20.37.5 params
#
This section enabled the SNMPv3 configuration of the router. Additional configuration is required. See
the procedure for completing the configuration.
ssh server enable
Enables SSH server on the router.
ntp-service enable
ntp-service source LoopBack0
ntp-service refclock-master 10
ntp-service unicast-server 24.56.178.140 source GigabitEthernet0/1
Enables NTP and if the router has Internet connectivity to connect to a time server on the Internet.
acl advanced 3001

description "ACL applied on the inbound direction of Radio subnet
interface"
rule 0 permit ip source 172.16.1.0 0.0.0.255 destination 172.16.0.0
0.0.255.255
0.0.0.255
0.0.7.255
0.0.0.255
rule 20 permit icmp source 172.16.1.0 0.0.0.255 destination 172.20.0.0
0.0.255.255
rule 25 deny ip source 172.16.1.0 0.0.0.255 destination 172.20.0.0
0.0.255.255
rule 30 permit icmp source 172.16.1.0 0.0.0.255
#
acl advanced 3002
description "ACL applied on the inbound direction of Gateway1 subnet
interface"
0.0.255.255
0.0.255.255
#
acl advanced 3003
description "ACL applied on the inbound direction of Gateway2 subnet
interface"
0.0.255.255
0.0.255.255
#
Send Feedback 217

MN002731A01-A
acl advanced 3004

description "ACL applied on the inbound direction of Application subnet
interface"
rule 0 permit icmp source 172.20.1.128 0.0.0.127 destination 172.16.0.0
0.0.255.255
rule 5 deny ip source 172.20.1.128 0.0.0.127 destination 172.16.0.0
0.0.255.255
rule 10 permit tcp source 172.20.1.128 0.0.0.127 destination 172.20.36.1
0 destination-port eq 65015
rule 35 permit udp source 172.20.1.128 0.0.0.127 destination 172.20.36.1
rule 60 deny ip source 172.20.1.128 0.0.0.127 destination 172.20.36.1 0
0.0.255.255
#
acl advanced 3013
description "Application subnet filter for NAT"
rule 0 permit ip source 172.20.1.128 0.0.0.127
218 Send Feedback

MN002731A01-A
These Access Control Lists are implemented based on Table 62:
Table 62: Conditions for Access Control Lists
Destination
Radio Gateway -
Infrastructure Gateway - TC Others Application
Radio Allowed Allowed Allowed Blocked (note 1)

Infrastructure
Source
Gateway - TC Allowed Allowed Allowed Allowed
Gateway - Allowed Allowed Allnowed (note 2) Allowed

Others
Application Blocked Blocked (note 3) Allowed Allowed (note 4)
Notes:
The following notes apply to Table 62:
1 Exception: UDP Source Ports 65008 (Repeater Slot 1) and 65009 (Repeater Slot 2) can send IP
packets from the Radio Infrastructure to the Application Network for ATIA traffic.
2 In general IP packets can be exchanged between any Gateway subnet. However, it may be
desirable to block traffic between application sites. In a system used by multiple customers, ACLS
should be applied between Gateway Networks at customer sites.
3 Exception: The Application Network can send and receive packets to and from the Trunk Controller’s
Presence service (UDP and TCP pots 65015).
4 In general, IP packets may be exchanged between any external subnets. However, it may be
desirable to block traffic between application sites. In a system used by multiple customers, ACLS
should be applied between Gateway Networks at customer sites.
#
header motd %Welcome to Capacity Max%
This is a Message of the Day Banner.
#
domain capacitymax
This is needed in all the routers to be on the same domain. In this case capacitymax was used, it has to
be the same in every router.
#
domain system
#
domain default enable system
#
role name level-0
description Predefined level-0 role
#
role name level-1
#
role name level-2
Send Feedback 219

MN002731A01-A

#
role name level-3
#
role name level-4
#
role name level-5
#
role name level-6
#
role name level-7
#
role name level-8
#
role name level-9
#
role name level-10
#
role name level-11
#
role name level-12
#
role name level-13
#
role name level-14
#
user-group system
#
local-user root class manage
service-type ssh terminal
authorization-attribute user-role network-admin
Defines root as the user login.
#
local-user capacitymax class network
password cipher $c$3$QpiHW1rcdfe3mLcy5BNewxUFaRx4cM+0lYmt
service-type advpn
220 Send Feedback

MN002731A01-A
Defines a login for the ADVPN servicec to use.
#
ipsec transform-set ipsec-transform-set
esp encryption-algorithm des-cbc
esp authentication-algorithm sha1
#
ipsec profile ipsec-profile isakmp
transform-set ipsec-transform-set
ike-profile ike-profile
Defines the ipsec parameters.
#
nat address-group 1
address 192.168.1.1 192.168.1.1
Defines the NAT pool, since there is only one static IP address the NAT pool is only one address.
#
ike profile ike-profile
keychain ike-keychain
#
ike keychain ike-keychain
pre-shared-key address 0.0.0.0 0.0.0.0 key cipher
$c$3$6igWORaddj3L2KDqeXsfZ4VWEfQ3TVQh8uJE
#
vam client name hub1
advpn-domain capacitymax
server primary ip-address 192.168.1.1
server secondary ip-address 192.168.2.1
pre-shared-key cipher $c$3$GWLwubdMu9wH2f8VieqvqjThGFyxCf1mDq2/
user capacitymax password cipher
$c$3$RNnS3yJ3GNiND8rXs7tBem9Ny4L5bZ9iHZKJ
client enable
Defines ADVPN client parameters for primary and secondary hub addresses and sets the ciphers.
Change the ciphers and make them unique per customer.
#
vam server advpn-domain capacitymax id 1
pre-shared-key cipher $c$3$bQseVUtuJELgf6G2l4h5rGVWYbCSv92z08Oa
authentication-method chap domain capacitymax
keepalive interval 15 retry 3
server enable
hub-group 1
hub private-address 172.30.0.1
hub private-address 172.30.0.2
spoke private-address range 172.30.0.0 172.30.0.255
shortcut interest all
Defines ADVPN server parameters (domain, ciphers, and so on) It is suggested to change the ciphers
and make them unique per customer. Only two routers are configured as VAM servers.
#
return
Send Feedback 221

MN002731A01-A
HP 2530 Switch Configuration File Overview

There are two methods to use the HP 2530 Switch configuration text files provided.
• Modify the text files to customize the configurations (experienced users) and then load the text
configuration files onto the Ethernet switch or router.
NOTICE:
Caution should be taken using this method, because a syntax error in the text file may cause a
failure to load a section or the complete configuration. Use of a text comparison tool should
always be used to confirm the correct text modifications were made.
• Load the template configuration files onto the Ethernet switch or router and then use the Command
Line Interface to modify the configuration.
Before actually loading configuration files, review the text configuration files presented here.
The selected files are from the section for ADVPN with Encryption and Secure Protocols. Ethernet
Switch configuration text file with annotations for Site 1. The configuration text is in a monospaced font.
; J9782A Configuration Editor; Created on release #YB.15.17.0007

; Ver #07:c3.84.9c.63.ff.37.27:50
These first two rows are always required by the Ethernet Switch to load a text configuration file.
hostname "Site1-Switch1"
User entered text to define a host name for the switch. Useful when remotely accessing the device to
change or verify configuration.
mirror-port 24
Port 24 is assigned as mirror port. The mirror port would be used to connect a laptop running Wireshark
to capture LAN traffic.
HP CLI Command to set/remove[no] mirror-port.
[no] mirror-port []
console baud-rate 9600

console idle-timeout 600
console idle-timeout serial-usb 600
Default defines the communication baud-rate for the serial port and inactivity timer to log user out.
no cdp run
Default, disables Cisco Discovery Protocol (CDP).
banner motd "Welcome to Capacity Max"
Adds a Message of the Day (motd) as a banner at the login screen.
port-security 1 learn-mode static

port-security 1 action send-alarm
222 Send Feedback

MN002731A01-A

port-security 13 address-limit 63
Send Feedback 223

MN002731A01-A
Port security is an optional configuration feature to lock a switch port to a specific MAC address. This
configuration sends a trap to the system advisor if a violation occurs. Ports 1 through 24 are assumed to
only have one host, while port 25 that connects to the router has four MAC addresses.
timesync sntp
sntp unicast
sntp 60
sntp server priority 1 172.30.16.1
Configures simple network time protocol (SNTP) to connect via unicast to the router to acquire time. In
this case the site 1 router.
no stack
Default, disables stacking.
no telnet-server
Optional command disables telnet on the Ethernet switch.
HP CLI Command to set/remove.
no telnet-server

IP authorized manager is an optional configuration feature that when enabled, requires the Ethernet
switch to ensure that any management traffic source IP is within the range of the commands. These
commands allow any host on a radio infrastructure or Gateway network to access the Ethernet switch.
ip default-gateway 172.16.1.20
The router IP address that the Ethernet switch will forward all Ethernet switch management traffic too if
the host is not on the local network. Customize to the site the switch is at?
no ip ssh cipher 3des-cbc

no ip ssh cipher rijndael-cbc@lysator.liu.se
no ip ssh mac hmac-md5
no ip ssh mac hmac-md5-96
Optional configuration to remove ciphers and macs from the IP SSH offer list.
interface 1
monitor
name "Repeater_01"
exit
interface 2
monitor
name "Repeater_02"
exit
interface 3
monitor
name "Repeater_03"
exit
interface 4
monitor
name "Repeater_04"
exit
interface 5
224 Send Feedback

MN002731A01-A
monitor
name "Repeater_05"
exit
interface 6
monitor
name "Repeater_06"
exit
interface 7
monitor
name "Repeater_07"
exit
interface 8
monitor
name "Repeater_08"
exit
interface 9
monitor
name "Repeater_09"
exit
interface 10
monitor
name "Repeater_10"
exit
interface 11
monitor
name "Repeater_11"
exit
interface 12
monitor
name "Repeater_12"
exit
interface 13
monitor
name "External-Equip"
exit
interface 14
monitor
exit
interface 15
monitor
exit
interface 16
monitor
exit
interface 17
monitor
exit
interface 18
monitor
name "CMSS-R&TC"
exit
interface 19
monitor
name "CMSS-Voice-GW"
exit
Send Feedback 225

MN002731A01-A
interface 20
monitor
name "CMSS-System-Advisor&ESU"
exit
interface 21
monitor
name "CMSS-iLO"
exit
interface 22
monitor
name "Data-Gateway"
exit
interface 23
monitor
name "Technician-port"
exit
interface 24
name "Mirror"
exit
interface 25
name "Router_01"
exit
interface 26
disable
name "Switch_02"
exit
interface 27
disable
exit
interface 28
disable
exit
Configures each port with a friendly name and if monitor is displayed the port traffic is copied to the
Mirror Port.
snmp-server community "public" unrestricted

snmpv3 enable
snmpv3 only
snmpv3 group managerpriv user "MotoMaster" sec-model ver3
snmpv3 notify "notify1" tagvalue "tag1"
snmpv3 targetaddress "system-advisor" params "param1" 172.20.1.5 filter
all taglist "tag1"
snmpv3 targetaddress "system-advisor2" params "param1" 172.20.5.5 filter
all taglist "tag1"
snmpv3 params "param1" user "MotoMaster" sec-model ver3 message-processing
ver3 priv
snmpv3 user "initial"
This section configures SNMPv3 on the Ethernet switch to work with the System Advisor.
no lldp run
226 Send Feedback

MN002731A01-A
Default, disables link layer discovery protocol (lldp).
vlan 1
name "DEFAULT_VLAN"
no untagged 1-28
ip address dhcp-bootp
exit
vlan 9
name "UNUSED"
untagged 26-28
no ip address
exit
vlan 10
name "Radio"
untagged 1-12,23
tagged 25
ip address 172.16.1.16 255.255.255.0
exit
vlan 20
name "Gateway1"
untagged 18-21
tagged 25
no ip address
exit
vlan 21
name "Gateway2"
untagged 22
tagged 25
no ip address
exit
vlan 30
name "Application"
untagged 13-17
tagged 25
no ip address
exit
vlan 40
name "Mirror"
untagged 24
no ip address
exit
This section configures the various VLANS used at the site. These VLAN IDs have to match the VLANs
on the MSR routers. Tagged refers to if the IP traffic on the port is encapsulated in VLAN tags, while
untagged means that no VLAN tag is on the port. The IP address is used for the management traffic to
and from the Ethernet Switch.
no tftp client
no tftp server
Optional configuration to disable tftp.
no dhcp config-file-update
no dhcp image-file-update
no dhcp tr69-acs-url
Optional configuration to disable some DHCP aspects to enhance security.
Send Feedback 227

MN002731A01-A
Chapter C: Configuration Files
228 Send Feedback

MN002731A01-A
MSR WAN IP Identification and Changes
Appendix D
MSR WAN IP Identification and Changes D
This appendix explains how to change the WAN IP address in the default configuration files.
Changing the WAN IP Address

The quick reference configuration templates provided use default WAN IP addresses of:
• 192.168.1.1
• 192.168.2.1
• Or dynamic
Also the Gateway addresses used for the static routes are either:
• 192.168.1.254
• 192.168.2.254
The subnet mask of 255.255.255.0 is assumed to not change. However, if a different subnet mask
needs to be applied, that change should be made at the same time the WAN IP is changed.
Procedure:
1 Identify the configuration aspects of the router that needs to be updated to apply these quick
reference configurations on your system. See Appendix B Common System Configurations and
Recommended IP Plans on page 181 for descriptions of each system type.
a Quick Reference System 1 has this instance to change:
1) interface GigabitEthernet0/1
ip address 192.168.1.1 255.255.255.0
b Quick Reference System 2 has these instances to change:
ip address 192.168.1.1 255.255.255.0
2) ip route-static 0.0.0.0 0 192.168.1.254

3) nat address-group 1
address 192.168.1.1 192.168.1.1
Send Feedback 229

MN002731A01-A
Appendix A: MSR WAN IP Identification and Changes
c Quick Reference System 3 has these instances to change:
ip address 192.168.1.1 255.255.255.0
2) ip route-static 0.0.0.0 0 192.168.1.254

3) nat address-group 1
address 192.168.1.1 192.168.1.1
d Quick Reference System 4 has these instances to change:
1) Site 1
ip address 192.168.1.1 255.255.255.0
ip route-static 0.0.0.0 0 192.168.1.254
nat address-group 1
address 192.168.1.1 192.168.1.1
2) Site 2
ip address 192.168.2.1 255.255.255.0
ip route-static 0.0.0.0 0 192.168.2.254
e Quick Reference System 5 has these instances to change:
1) Site 1
ip address 192.168.1.1 255.255.255.0
ip route-static 0.0.0.0 0 192.168.1.254
nat address-group 1
address 192.168.1.1 192.168.1.1
230 Send Feedback

MN002731A01-A
2) Site 2
ip address 192.168.2.1 255.255.255.0
ip route-static 0.0.0.0 0 192.168.2.254
3) Site 3
vam client name spoke
4) Site 4
vam client name spoke
2 Decide how to implement the changes. Perform one of the following bulleted choices:
• Edit the electronic versions of the configurations files to change the IPs to reflect the system to
be implemented. Any incorrect entry may cause the router to not load the configuration correctly,
so this should only be done by experienced users and with the help of a text comparison tool to
make sure no extraneous data is added to the file.
• Load the electronic version of the configuration files and then use the command line interface
(CLI) to change the WAN IP addresses, as follows:
a Change or configure the IP address.
When an IP address is configured on MSR2003 router, it overwrites the existing IP address.

Use the following command in the interface sub configuration mode to configure an IP
address or change the existing IP address.
ip address <IP address> <subnet mask>
Example:
[Site1Router1-GigabitEthernet0/1]ip address 192.168.1.2
255.255.255.0
[Site1Router1-GigabitEthernet0/1
Send Feedback 231

MN002731A01-A
b Configure the interface as a DHCP client
If the system requires the WAN interface IP address to be assigned dynamically from a
DHCP server in the backhaul or the internet, configure the interface with the following
command.
ip address dhcp-alloc
dhcp client identifier mac GigabitEthernet0/1
Example:
[Site1Router1-GigabitEthernet0/1]ip address dhcp-alloc
[Site1Router1-GigabitEthernet0/1] dhcp client identifier mac
c Use the CLI to change the other WAN IP instances.
Adding a NAT Entry to Access a Service from the Internet

Two kinds of NAT are configured on Capacity Max routers.
• For clients in the system to access any service in the internet – The source address of the client is
translated to the public WAN interface address on the local site router. This service is available for
clients in the Application network and CMSS network.
• For clients in the internet to access services inside the capacity max system – The client in the
internet attempts to access the public WAN interface address on the site router for the desired
service (port number). The destination IP address is translated to the private server address inside
the system.
Configuring the Static NAT Entry Under the GigabitEthernet0/1

interface
The purpose of this procedure is to configure additional static NAT entries for the second type of NAT
described above. The example below would be adding a NAT on Port 9090 to the host on the capacity
max system at the IP address of 172.20.36.5.
Static NATs can only be applied to sites that have static WAN IP addresses.
Procedure:
1 Enter the global configuration mode
2 Enter the WAN interface sub configuration mode
3 Configure the NAT entry using the following command:

nat server protocol <transport protocol> global current-interface
<port number> inside <server IP address> <port number>
NOTICE:
Transport protocol could be “tcp” or “udp”. Port number is the port number of the application that
the client in the internet is trying to access inside the system. IP address is the server’s IP
address inside the system.
232 Send Feedback

MN002731A01-A
Example:
[Site1Router1-GigabitEthernet0/1]display this
#
ip address 192.168.1.1 255.255.255.0
aspf apply policy 1 inbound
172.20.31.24 4001
172.20.31.24 4007
172.20.36.5 36002
172.20.36.5 36003
172.20.36.5 50111
172.20.36.5 51919
172.20.31.24 58041
#
return
[Site1Router1-GigabitEthernet0/1]nat server protocol tcp
global current-interface 9090 inside 172.20.36.5 9090
Send Feedback 233

MN002731A01-A
Chapter D: MSR WAN IP Identification and Changes
234 Send Feedback


LACR - Capacity Max Installation and Configuration Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LACR - Capacity Max Installation and Configuration Manual

Uploaded by

Copyright:

Available Formats

Capacity Max

Chapter 1: Configuration Overview .......................................................................1

Chapter 2: Pre-Configuration Planning ...............................................................15

Detailed Capacity Max IP Plan ..................................................................................... 23

Chapter 3: Network Configuration ...................................................................... 45

Configuring the Password for the User ‘capacitymax’ on Routers ................................72

Chapter 4: System Configuration ........................................................................75

Send Feedback iii

Configuring the Talkgroup Site Association .................................................. 98

Licensing the CMSS....................................................................................................117

Chapter 5: Redundancy ......................................................................................133

IP Network Multiple Site Switch Configuration.................................................................... 137

Chapter 6: Optimizations ................................................................................... 151

Corridor Coverage ...............................................................................................162

Chapter 7: Capacity Max Hardware Specifications ..........................................171

Send Feedback vii

Chapter 8: Common System Configurations and

Chapter 9: Configuration Files .......................................................................... 213

Chapter 10: MSR WAN IP Identification and Changes .................................... 229

viii Send Feedback

Figure 1: High Level Process of Capacity Max System Configuration. . . . . . . . . . . . . . . . . . . . . . . . 2

Figure 44: Isolated No Overlapping Multi-site Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Table 1: Classless Inter-Domain Routing (CIDR) Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 42: Capacity Max System Server (CMSS) Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 171

xii Send Feedback

Capacity Max System Confuration

Capacity Max Configuration High Level Steps

Figure 1: High Level Process of Capacity Max System Configuration

FLOOR PLAN, RACKING CONFIGURE REPEATERS

SOFTWARE INSTALL & CONFIGURE

PRE-CONFIGURATION CONFIGURE SYSTEM

CONFIGURE RADIO CONFIGURE BATTERY

IMPORT SOFTWARE CONFIGURE VOICE

CONFIGURE SYSTEM CONFIGURE DATA

Floor Plan, Racking, and Power

Software Installation and Firmware Upgrade

Site Topology Example

Figure 2: Example Site Topology

Figure 3: HP Enterprise 2530 Ethernet Switch Layout

Figure 4: Interconnect Overview

Figure 5: Connection from CMSS to Switch

Figure 6: Connection from Switch to Router

Figure 7: Connection from Switch to Repeaters

• Understanding IP Addressing on page 15

• Entity Identifier Assignments on page 29

• Radio Identifier Assignments on page 34

• Talkgroup Identifier Assignments on page 35

• Understanding the Channel Plan on page 36

Radio Management Configuration

• RM Configuration Client: Edits and Manages Configuration Data

• RM Server: Storage of Configurations

• RM Device Programmer: Programs All Managed Devices

• RM Job Processor: Processes Scheduled Jobs

The following equipment is configured within Radio Management:

• MNIS VRC Gateway

• MNIS Data Gateway

See Radio Management Configuration on page 75 for more details.

Import Software Licenses

System Parameters Configuration in Radio Management

• Capacity Max System Set

• Capacity Max Sites

• Capacity Max Channels

• Capacity Max Site Selection Set