6881005y52 o PDF
6881005y52 o PDF
6881005y52 o PDF
*6881005Y52*
68P81005Y52-O
November 2002
Computer Software Copyrights
The Motorola products described in this document include a copyrighted Motorola computer program. Laws in the United States and other countries, as well as
International Treaties, preserve for Motorola the exclusive rights for Motorola’s copyrighted computer programs, including the exclusive right to copy, repro-
duce, distribute, or otherwise transfer said computer program(s). Accordingly, the copyrighted Motorola computer programs contained in this document may
not be copied, decompiled, reverse engineered, or reproduced in any manner and on or within any media without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the
copyrights, patents, or patent applications of Motorola, except for the normal non-exclusive, royalty-free license to use that arises by operation of law in the
sale of a product.
Document Copyrights
© Motorola, Inc. All rights reserved.
No duplication or distribution of this document or any portion thereof shall take place without the express written permission of Motorola. No part of this
document may be reproduced, distributed, or transmitted in any form or by any means, electronic or mechanical, for any purpose without the express written
permission of Motorola.
To order additional copies of this document contact your Motorola sales representative.
Disclaimer
The information in this document is carefully examined, and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies. Further-
more, Motorola reserves the right to make changes to any products herein to improve readability, function, or design. Motorola does not assume any liability
arising out of the applications or use of any product or circuit described herein; neither does it cover any license under its patent rights nor the rights of others.
Trademark Information
The following are registered trademarks of Motorola, Inc.: ASTRO, ASTRO-TAC, EMBASSY, FLASHport, FULLVISION, INTELLIREPEATER,
MAXTRAC, Motorola, the Motorola logo, MSF 5000, PSC 9600, QUANTAR, QUANTRO, SECURENET, SMARTNET, SMARTZONE, SPECTRA, and
STARTSITE.
The following are Motorola trademarks: CENTRACOM Series, CENTRACOM Gold Series, CENTRACOM Series II, CENTRACOM Series II Plus,
Cisco, CoveragePLUS, DIGITAC, DVP, Max-Fax, MDC-600, Micor, MOSCAD, MSF 10000, MTS 2000, Private Conversation, SABER, SMARTNET
II, SmartWorks, and Wireless Network Gateway.
HP, HP-UX, and Hewlett Packard are registered trademarks of Hewlett-Packard Corporation.
UNIX is a registered trademark of The Open Group in the United States and other countries.
PICMG, CompactPCI, and the PICMG and CompactPCI logos are registered trademarks of the PCI Industrial Computers Manufacturers Group.
PowerPC is a registered trademark of IBM in the United States.
Any other brand or product names are trademarks or registered trademarks of their respective holders.
WARRANTY
Limited Software Warranty
For the first ninety (90) days following its initial shipment, Motorola warrants that when properly used, its software will be free from reproducible defects that
cause a material variance from its published specification. However, Motorola does not warrant that program operation will be uninterrupted or error- free, that
each defect will be corrected, or that any program will meet Licensee’s particular requirements.
This warranty does not cover an item of Software (i) used in other than its normal and customary manner; (ii) subjected to misuse; or (iii) subjected to modi-
fications by Licensee or by any party other than Motorola without the prior written consent of Motorola.
Limited Media Warranty
For the first ninety (90) days following its initial shipment, Motorola warrants that the media carrying the software will be free from defects that damage the
performance of the software. Motorola will replace any damaged media free of charge during the warranty period. Warranted media is limited to that which
is used to transport the software (such as floppy disks and authorization key). PROMs that may store the software in equipment are not covered under this
warranty.
Limitation of Liability
Motorola’s total liability and Licensee’s sole remedy for any warranted software shall be limited to, at Motorola’s option, software replacement or the payment
of Licensee’s actual damages, not to exceed the total licensed charge paid by Licensee to Motorola for the item of software that caused the damage.
The warranties set forth above extend only to the first licensee. Subsequent transferees accept these programs "as is" and without warranties of any kind. This
warranty is given in lieu of all other warranties, express or implied, including, without limitation, the warranties of merchantability and fitness for a
particular purpose.
In no event shall Motorola be liable for special, incidental, or consequential damages (including, without limitation, loss of use, time or data, inconvenience,
commercial loss, and lost profits or savings) to the full extent that such may be disclaimed by law even if Motorola has been advised of the possibility of such
damage against licensee by any other party.
Repair of Defects
The classification of defects in Motorola-supplied software shall be the responsibility of Motorola. Remedy of defects is at the sole discretion of Motorola. If
Motorola agrees to remedy a software defect, the new software will be warranted until the end of the original limited warranty period. Replacement of any
software defect shall constitute Motorola supplying the Licensee with the appropriate software media and authorization key. Field installation and configuration
are not included. Field software updates/upgrades and new enhancement option software will be warranted for ninety (90) days from the date of initial shipment.
All warranty service will be performed at service locations designated by Motorola. Travel and associated expenses of the Licensee or such expenses incurred
by Motorola for visits to Licensee’s location by Motorola personnel are not covered by this warranty.
Table
of
Contents
Contents
List of Figures
List of Tables
List of Procedures
List of Processes
Process 2-1: Configuring Other Band Trunking and Sub-Band Capabilities . . . . . . . . . . . . . . . . . . . 2-15
Process 2-2: Adding a New Band Plan Element (High Level Process) . . . . . . . . . . . . . . . . . . . . . . 2-34
Process 2-3: Changing a Band Plan Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Process 2-4: Entering a Configuration into the S4000 Site Router . . . . . . . . . . . . . . . . . . . . . . . . 2-70
This booklet provides high-level references and procedures for configuring the installed
ASTRO® 25 Release 6.1 IntelliSite™ Repeater hardware.
• Attended the Motorola Worldwide Learning Services (WLS) formal ASTRO 25 training
(including all multimedia presentations) to learn the operating principles of ASTRO 25.
Related Information
1
IntelliSite Repeater Site Configuration
Overview
The System Configuration Guide for your ASTRO® 25 Release 6.1 system, together with any associated
documentation, outlines the configuration and programming parameters for the devices installed at the
IntelliSite® Repeater site. These documents, taken together, list the settings for all parameters of the
Configuration/Service Software for the IntelliSite Repeater sites in your system.
Using the system documentation as your programming reference ensures that you will program
the IntelliSite Repeater Sites to a known baseline.
Do not deviate from the specified settings contained in your system documentation without
following the change procedures for your organization.
Document all changes according to your organizations change procedures. Failing to
document changes or not following proper change procedures makes troubleshooting
more difficult when a problem arises.
The Federal Communications Commission (FCC), together with your state or local frequency coordinators,
determines the frequencies your system will use and which sites get specific frequencies.
Setting the frequencies incorrectly can lead to interference within your system and other systems in your
region. There are also legal ramifications if you do not use the FCC-mandated frequencies.
The ASTRO 25 Release 6.1 IntelliSite Repeater design requires certain settings for proper operation
of your system, as described in your site documentation.
If these parameters are not set correctly, your equipment will not operate as planned.
For example, the specifications may require setting the Control Channel Capability to Enable. Setting
the Control Channel Capability to Disable would reduce the availability of potential control channels in
the event of a control channel failure (but not necessarily inhibit site operation).
This section details the specifications for the equipment, software, and documents you
need to configure the IntelliSite Repeater site.
Equipment
You must have the following equipment in order to program your IntelliSite Repeaters and the
site network transport equipment at an IntelliSite Repeater site:
• "Computer" on page 1-2
• "Cables and Connectors" on page 1-3
• "Software" on page 1-4
Computer
You will need a computer (either laptop or desktop) to perform configuration.
The computer you use must meet the minimum specifications described in Table 1-1.
• Serial cable
• 10Base-T cable for software download and connection to the PSC 9600 site controller
• CAT-5 crossover cable for connection to the S4000 for configuration download
• Serial cable female DB9 to RJ45 or female DB9
• Null modem adapter
Depending on the configuration of your workstation, you may also need appropriate
adapters for equipment interconnection.
• Quantar: Serial cable for 30-80369E31
• S4000 Router: S 413 plug-in module
Software
In order to program the IntelliSite Repeaters, you must have Configuration Service
Software (CSS) version DLN6455A or later.
In order to program Quantar® stations used for Mutual Aid, you will also need the latest version of the
Radio Service Software (RSS) version RVN5002 or later for Quantar and Quantro® stations.
If the IntelliSite Repeater site does not include Mutual Aid equipment, you do not need RSS.
CSS and Zone Controller Management (ZCM) will be sufficient to program the site.
Documentation
In order to configure the site, you must have the following documents:
• The System Configuration Guide for your system.
• For sites with Mutual Aid stations, you may need to refer to the Zhone TeNSr Manual,
Integrated Access Server, Software Release 5.3, Zhone Technologies, Inc.
• For MOSCAD Remote Terminal Unit (RTU) configuration, you will need to refer to General
Usage and Loading Instructions For The MOSCAD Toolbox and Site Builder, which is
included in your System Installation Guide documentation package.
• For Other Band Trunking (OBT) you will need a hard copy of your band plan.
2
Configuration Processes and Procedures
This chapter provides information to help you configure the IntelliSite ® Repeater equipment.
This chapter contains information on the following topics:
• "Definitions" on page 2-1
• "Making Connections to the Site or to Hardware" on page 2-2
• "IntelliSite PSC 9600 Controller Configuration" on page 2-9
• "IntelliSite Repeater Configuration" on page 2-39
• "Configuring the Quantar as a Conventional Mutual Aid Channel" on page 2-52
• "IP Address Definition" on page 2-52
• "Transport Device Configuration" on page 2-53
• "TeNSr Channel Bank " on page 2-96
• "Channelization Plan on T1 Slots" on page 2-97
• "Card Configuration for 6.1 Systems" on page 2-98
• "MOSCAD Remote Terminal Unit (RTU) Configuration" on page 2-101
• "Checking Measurements on the IntelliSite Repeater" on page 2-102
• "Metering the IntelliSite Repeater Through CSS" on page 2-130
Definitions
As used in this booklet and in Volume 10, IntelliSite Repeater Hardware Installation,
the term “IntelliSite Repeater Site” includes:
• Network Transport Equipment
• All IntelliSite Repeater stations, as well as Mutual Aid Stations
• Zhone® TeNSr Channel bank, where used
• PSC 9600® site controller
• Hewlett-Packard® Procurve® 2524 switch
MOSCAD™ equipment is optional at an ASTRO® 25 IntelliSite Repeater site. However, this configuration
booklet treats it as a standard feature to be installed with the original site.
If MOSCAD equipment is going to be installed at the site, the Motorola Fixed Data Product Group
will provide a MOSCAD site configuration file in the documentation.
There are two ways you can make the physical connection to an IntelliSite Repeater site
or to the IntelliSite Repeater hardware components:
• "Connecting Through an Ethernet Link" on page 2-2
• "Connecting Through a Serial Link" on page 2-6
1 Connect a computer (either laptop or desk top) to the IntelliSite Repeater site:
1. Connect an Ethernet cable between the Ethernet port on the computer and the Ethernet port on the device.
2. Start the computer.
2 Launch the CSS application:
1. Double click the Configuration Service Software icon.
The Configuration/Service Software window opens.
You can click on the Connect to Device icon on the toolbar instead.
2. Select the desired device type from the Device list box.
3. Enter the proper values in the Zone, Site, Subsite, and
Device ID fields.
4. Click OK.
You can use the map on the left side of the screen to view configuration information for the device.
1 Connect a serial cable between the COM1 port on the laptop or PC which has the CSS application
installed, and the serial connector on the device you want to read.
This assumes you connected the serial cable to COM1 as stated in step 1. If you used a
different COM port, select that port from the field instead.
2. Select 9600 in the Baud Rate field.
3. Click Connect.
Result: An Information window will open and display a Communication Setup message:
IF the PC and the device: THEN...
Can communicate successfully: An Information window opens and displays the
Communication Setup Verified! message
(Figure 2-3, on page 2-5).
Continue with step 4.
Cannot communicate: An Error window opens and displays the CSS cannot
establish a physical connection with this
device! message. If this happens:
1. Click the OK button to close the message.
2. Check the connections to make sure they are good.
3. Check the port IDs to verify that you have the
correct COM ports identified.
4. Repeat these steps until you get the
Communication Setup Verified message.
5 Select Read Configuration From Device from the File menu. You may also use the Read
Configuration From Device icon.
Result: The configuration for the device downloads to your computer. When the download is
complete, the CSS Main Window opens (Figure 2-4, on page 2-5).Use the map on the left side of
the screen to view configuration information for the device. Click on the icon for the Site, Zone, or
other icons to see the configuration for that entity.
Manager-Owned Parameters
The settings shown in some of the tables, such as Table 2-2, Table 2-3, or Table 2-5, and in the CSS
windows (for System, Zone, Zone IP Address and most Site window values) include parameters which are
“manager-owned.” This means that any values set using the CSS application will be overwritten by the Network
Manager settings when the IntelliSite Repeater Site establishes a connection with the Master Site, and the Master
Site downloads the channel parameters. Manager-owned parameters are marked with an asterisk (*).
When you first set up the IntelliSite Repeater site, the site is not connected to the master site. During the setup,
you enter all of the parameters, which are included in your System Configuration Guide. When the site is
configured and online, it will open in site trunking using the parameters you entered. When the site connects to
the Master site, the Network Manager program overwrites the parameters that the Network Manager owns.
If you try to write a new configuration value to any parameter marked with an asterisk, the Network Manager
will compare the new settings against the settings in the corresponding database file, determine that one or more
values have been changed, and will then overwrite those parameter values with the values from the database.
Device-Owned Parameters
Parameters not marked with asterisks are owned by the device. You may change device-owned
parameters at any time, using the CSS. The Network Manager will detect that a new configuration
file has been written to a device and will capture the new parameter values in its local database, but
will not overwrite the parameter values in the device. Changes to device-owned parameters must
be in accordance with your System Configuration Guide documentation.
1 Make a connection to the PSC 9600. Follow the instructions in Procedure 2-1
2 With the CSS open, find each parameter using the navigation pane (on the left
side of the window) as your guide.
Table 2-2 through Table 2-6 list the PSC 9600 parameters that you can read and (in
some cases) set, using the CSS application.
Table 2-5 CSS PSC 9600 Channel Hardware Configuration Settings (Continued)
CSS Field Setting Range (default) Description
DFB Capable [*] Enabled or Disabled This field allows you to enable or disable the
Dynamic Frequency Blocking capability for the
• “Enabled” means this channel
selected channel.
can have up to seven interfering
channels. Also, this channel can be
an interfering channel for another
channel. (An interfering channel
is any channel whose frequency
interferes with another channel.)
Dynamic Frequency Blocking
(DFB) prevents two interfering
channels from being used at the same
time. When a channel is in use, any
channels listed as interfering with
that channel are made unavailable
(blocked).
• “Disabled” means this channel
cannot have any interfering channels,
nor can it be an interfering channel.
(default=Disabled)
When the DFB Capable field is enabled, the Control Channel Capability, BSI
Capability, and Failsoft Capability become read-only.
If any of these three fields are enabled, the DFB Capable field becomes
read-only.
BSI Capable [*] Enabled or Disabled Shows whether this channel can serve as the
Base Station Identifier (BSI) channel.
Failsoft Capable [*] Enabled or Disabled Indicates whether the channel is Failsoft Capable
or not.“Enabled” disables the DFB Channel
field.
Control Channel Capable Enabled or Disabled (default=Disabled) Shows whether this channel can serve as the
[*] Control Channel.
Control Channel Preference 1 (highest preference) through 4 (lowest This field allows you to assign a preference level
Level [*] preference) to the channel to indicate the order in which it
(default=4) is chosen as control channel. This field is only
Only channels 1 to 4 can be assigned as available when the Control Channel Capable
control channel capable. Multiple control field is enabled. When the Control Channel
channel capable stations can have the Capable field is disabled, this field is 4.
same preference level.
Interconnect Capable [*] Enabled or Disabled (default=Disabled) This field shows whether the Controller can
perform Telephone interconnect.
Table 2-5 CSS PSC 9600 Channel Hardware Configuration Settings (Continued)
CSS Field Setting Range (default) Description
Protect Capable [*] Enabled or Disabled (default=Disabled) This field allows you to indicate if the selected
channel is protected from being assigned to
a dispatch call, unless it is the only channel
available.
• “Enabled” means this channel cannot be
assigned to dispatch calls.
• “Disabled” means this channel can be
assigned to a dispatch call.
Voice Capable [*] Enabled or Disabled Shows whether this channel can serve as a Voice
(default=Enabled) Channel.
Tx Channel Frequency Available range depends on the frequency This field lets you enter the Transmit Frequency
(MHz) band. (in MHz) for the selected station. The system
(No default) will display a warning if the value is invalid.
• For the VHF frequency band, the Tx
Frequency value must be divisible by 6.25
kHz or 2.5 kHz to be valid.
• For the UHF and 800 MHz frequency
bands, the Tx Frequency value must be
divisible by 6.25 kHz or 5.0 kHz to be
valid.
Rx Channel Frequency Available range depends on the frequency This field lets you enter the Receiver Frequency
(MHz) band. (in MHz) for the selected station. The system
(No default) will display a warning if the value is invalid.
• For the VHF frequency band, the Rx
Frequency value must be divisible by 6.25
kHz or 2.5 kHz to be valid.
• For the UHF and 800 MHz frequency
bands, the Rx Frequency value must be
divisible by 6.25 kHz or 5.0 kHz to be
valid.
Trunking systems typically use a standard 800 MHz full range of frequencies. Other band trunking uses
frequencies outside of this standard trunking range. In this release, a system can have radios and other
resources that operate on another frequency besides 800 MHz. These other frequency ranges are:
• VHF (136-174 MHz)
• UHF (380-470 MHz and 450-520 MHz)
The standardization of 800 MHz includes the arrangement of assigned channel numbers to each frequency in the
range. This means that a frequency band plan has already been created and followed for 800 MHz.
Because other frequency bands outside of the 800 MHz range use a wide variety of channel pairings for transmit
and receive frequencies, however, a prearranged channel-to-frequency standard cannot be applied. You must
create a frequency band plan specifically for the transmit and receive frequencies in your system.
The frequency band plan identifies a channel and lists the frequency information for that channel.
The radio users reference the channel and can determine all of the frequency information from
the band plan for using the channel in trunked communications.
Subscribers and resources, such as channels, that use other frequency bands need to be configured in the
system. Infrastructure devices need to have other band trunking resources identified in their database
so they can correctly assign resources when a radio trunking call requests to use other band trunking
frequencies. If the system contains resources that use sub-band frequencies, you must flag channels that
are used for Sub-band Restricted subscribers. Process 2-1 shows the high-level process for configuring
an ASTRO 25 system for other band trunking and sub-band capable resources.
Only IntelliSite Repeater sites are configured with other band trunking information. This release
does not allow Simulcast subsystems or IntelliRepeater sites to use other band trunking.
1 Create a fleetmap for the system, which includes a frequency band plan for the
use of other band trunking.
You can create a template for each type of user to make the
configuration and programming process easier.
4 Configure the Private Site Controller 9600 (PSC 9600) at each IntelliSite
Repeater site using Configuration/Service Software (CSS). You must configure
all of the System, Zone, and Site windows, including the Other Band Trunking
window. The Sub-Band window configures all sub-band resources at the site. See
"Configuring the PSC 9600 for Other Band Trunking" on page 2-16 or the PSC
9600 online help that is available with the CSS after you read from the device for
more details on how to configure this site controller.
Process 2-1 Configuring Other Band Trunking and Sub-Band Capabilities (Continued)
5 Configure the channel information in the Zone Configuration Manager (ZCM),
including the Sub-Band Restricted field.
See Volume 3, Managing Zone Infrastructure for the procedures to configure a
channel.
6 Configure all radio users, subscribers, talkgroups, and multigroups in the User
Configuration Manager (UCM) for other band trunking and sub-band restricted
capabilities.
See Volume 3, Managing Radio Users for the procedures to configure radio
users, subscribers, talkgroups, and multigroups.
See Volume 1: Understanding Your ASTRO 25 Trunking System and the online help for configuration
for background information on Other Band Trunking.
This section contains the following subsections:
• "Configuring the PSC 9600 for Other Band Trunking" on page 2-16
• "Configuring Sub-band Restricted Radios and Talkgroups in the PSC 9600" on page 2-21
• "Entering Restricted Talkgroup IDs on the Talkgroup Tab" on page 2-23
• "Configuring a Sub-Band Channel in ZCM" on page 2-25
• "Configuring Sub-band Restricted Radios and Talkgroups in the PSC 9600" on page 2-21
• "Adding a New Band Plan Element" on page 2-34
• "Changing a Band Plan Element" on page 2-36
Only IntelliSite Repeater sites are configured with other band trunking information. This release
does not allow Simulcast subsystems or IntelliRepeater sites to use the other band trunking feature.
Try to get the information from an established chart or table. Do not try to
configure the device from memory.
Procedure 2-4 How to Configure the Other Band Trunking Window
1 Connect to the PSC 9600. See Procedure 2-1, "How to Connect Through an Ethernet Link," on
page 2-2 for an example.
Result: The CSS screen for the PSC 9600 opens (Figure 2-7).
Procedure 2-4 How to Configure the Other Band Trunking Window (Continued)
2 Select Other Band Trunking from the navigation pane, which is part of the System
configuration windows.
Result: The Other Band Trunking window opens.
3 Enter a number to identify this specific band plan in the Band Plan ID field. The range of
IDs for this field is 1 to 16.
You will find all information that you need to complete the Other Band Trunking
window in the frequency band plan that is created with the fleetmap.
4 Type a name for this band plan in the Band Plan Name field.
Procedure 2-4 How to Configure the Other Band Trunking Window (Continued)
5 Select the Frequency Band Plan tab.
Result: The Frequency Band Plan tab appears.
Procedure 2-4 How to Configure the Other Band Trunking Window (Continued)
6 Using information from the frequency band plan, enter information for the following fields:
Field Name Definition and Valid Values
Identifier Enable This field indicates if this band plan entry is valid or not.
• True indicates the entry is valid.
• False indicates the entry is not valid.
Disable any band plan entries that are not currently being used.
Base Frequency This values is the lowest transmit frequency at the site. The range for this
(MHz) frequency depends on the band:
• VHF Band range is 132 - 174 MHz
• UHF Band range is 380 - 520
• MHz 800 MHz Band range is 851.00625 - 869.99375 MHz
Procedure 2-4 How to Configure the Other Band Trunking Window (Continued)
8 Do one of the following:
• Save the configuration data to an archive file. See “Saving an Archive File” in the CSS
online help.
• Write the configuration data into the PSC 9600 site controller. See “Writing the
Configuration Data to a Device” in the Core online help.
Result: If you are making changes for the first time to any information in the Other Band
Trunking window, an Information dialog box appears (Figure 2-10).
This Information dialog box only appears the first time you make a change to
parameters in the Other Band Trunking window. It does not appear after any
subsequent changes.
9 Click OK to close the dialog box and continue saving or writing the configuration data.
Parameters in the Sub-band window are Manager-owned. If you enter or change any
parameters in this window through CSS, the parameters will be overwritten with values
from the User Configuration Server (UCS) database after the PSC 9600 interfaces
with the Zone Configuration Manager (ZCM).
Procedure 2-5 explains how to configure restricted radio IDs from the frequency band
plan in the Radio tab of the Sub-band window.
Procedure 2-5 How to Configure Restricted Radio IDs
4 In the Lower Restricted Radio ID field, enter the ID of the first radio in a block of radio
IDs to be restricted.
5 In the Upper Restricted Radio ID field, enter the ID of the last radio in the block of radio
IDs to be restricted.
6 In the Subband Restricted field, select one of the following from the list:
• True — Indicates that radios in this range can operate on the full band of the frequency.
• False — Indicates that radios in this range must use only the channels assigned with
the sub-band frequency.
7 Repeat step 4 through step 6 to enter another range of restricted radios IDs.
8 Write the configuration data into the PSC 9600 site controller.
See “Writing the Configuration Data to a Device” in the CSS online help.
1 Select Sub-Band from the navigation pane, which is part of the System
configuration windows.
2 Select the Talkgroup tab.
Result: The Talkgroup tab on the Sub-Band window opens.
3 In the Lower Restricted Talkgroup ID field, enter the ID of the first talkgroup
in a range of talkgroup IDs to be restricted.
4 In the Upper Restricted Talkgroup ID field, enter the ID of the last talkgroup in
a range of radio IDs to be restricted.
5 In the Subband Restricted field, select one of the following from the list:
• True — Indicates that talkgroups in this range can operate on the full band
of the frequency.
• False — Indicates that talkgroups in this range must use only the channels
assigned with the sub-band frequency.
6 Repeat step 3 through step 5 to enter another range of restricted talkgroup IDs.
7 Write the configuration data into the PSC 9600 site controller. See “Writing the
Configuration Data to a Device” in the Core online help.
Procedure 2-7 explains how to open the Channel window and confirm if the Sub-band parameter has been set.
Procedure 2-7 How to Confirm a Channel is Configured for Sub-Band
1 Select Channel from the navigation pane for the PSC 9600
Result: The Channel window opens (Figure 2-13).
The Channel window is too large to fit in a single image. These figures show both
halves of the screen. When you are working on the actual screen you will have to
scroll to see different columns.
1 From the IntelliSite Repeater Site object, select the Channel object in the
navigation pane.
2 Right-click to open the popup menu.
The Configuration screen is too large to fit on a single screen. You need to scroll
up and down to see all the fields on the tab.
Procedure 2-9 explains how to configure restricted radio IDs from the frequency band plan.
Procedure 2-9 How to Configure Restricted Radio IDs
There is only one choice for this selection. However, you still have to select it to continue.
3. Right-click the mouse to open the popup menu and select Open.
Result: The Sub-Band Restricted window opens (Figure 2-21).
When performing step 4 and step 5, ensure that Individual and Talkgroup ID start
and end range mappings fall within the ranges specified in the Home Zone mapping
object. Improper mapping will result in inoperable subscribers.
5 In the Radio ID Mapping End field, enter the ID of the last radio in the block of radio IDs to be restricted.
6 Check the Sub-band Restricted box if you want to restrict the range of radios that can use the full band
of the frequency.
• True — Indicates that radios in this range can operate on the full band of the frequency.
• False — Indicates that radios in this range must use only the channels assigned with the sub-band
frequency.
7 Click the Apply button at the bottom of the window.
8 Choose one of the actions below:
IF you want to: THEN:
Create more records: Repeat step 2 through step 7 to enter another range of restricted
radios IDs.
Finish creating records Continue with step 9.
9 Write the configuration data into the PSC 9600 site controller.
See “Writing the Configuration Data to a Device” in the CSS online help.
Procedure 2-10 explains how to configure restricted talkgroup IDs on the Talkgroup tab.
Procedure 2-10 How to Configure Restricted Talkgroup IDs
5 In the Lower Talkgroup ID field, enter the ID of the first talkgroup in a range of
talkgroup IDs to be restricted.
6 In the Upper Talkgroup ID field, enter the ID of the last talkgroup in a range
of radio IDs to be restricted.
7 In the Sub-band Restricted Flag field, select one of the following from the list:
• True — Indicates that talkgroups in this range can operate on the full band
of the frequency.
• False — Indicates that talkgroups in this range must use only the channels
assigned with the sub-band frequency.
8 Repeat step 3 through step 7 to enter another range of restricted talkgroup IDs.
9 Write the configuration data into the PSC 9600 site controller. See “Writing the
Configuration Data to a Device” in the Core online help.
UHF and VHF bands use a random frequency pairing and most likely will
require band plan element changes.
If you need to change any elements in the band plan, see "Changing a Band
Plan Element" on page 2-36.
• Process 2-2 gives the high-level process for adding a new element to your band plan.
• Process 2-3 gives the high-level process for changing an element in your band plan.
Process 2-2 Adding a New Band Plan Element (High Level Process)
You must ensure that the start and end ranges for
all individual and talkgroup IDs fall within the ranges
specified in the Home Zone mapping object in the Zone
Configuration Manager (ZCM). Improper mapping can
result in inoperable subscribers.
4 Enter the new band element information into the appropriate subscriber templates
using the Customer Programming Software (CPS).
See the CPS specific to your subscribers
5 Enter the new band element information and channel information into the PSC
9600 site controller archive file using the Configuration/Service Software (CSS).
See the PSC 9600 online help, which is available from the application after you
read from one of the PSC 9600 at the site.
Process 2-2 Adding a New Band Plan Element (High Level Process) (Continued)
6 Program the following in any order you prefer:
• New identifier information into all subscribers on the system using the
templates updated in step 4. See the CPS specific to your subscribers.
You can bring channels into service after the sites have been prepared
to identify the new channels and the subscribers have been prepared
to read the new channel identifiers.
Making changes to the band plan for a live system will disrupt system
operations. Any affected channels will need to be removed from service for
reprogramming. All subscribers will need to be reprogrammed to include any
band plan changes. If you make changes to the band plan that move or delete
elements, subscribers could reference the wrong frequency for either a traffic
channel or a control channel. These subscribers would be unable to affiliate
and would not be able to communicate on the system.
Process 2-3 lists the high-level process to change an element in your band plan.
Process 2-3 Changing a Band Plan Element
Changing the identifier for a primary control channel that is currently in use can
cause serious system disruptions since the channel needs to be temporarily removed
from service to update the channel information.
6 Take all affected channels out of service at the sites.
It is critical that all channels requiring a change be removed from service so they
are not recognized at their site or at any adjacent sites.
7 Reprogram the following in any order that you prefer:
• New identifier information into all subscribers on the system using the templates created
in step 2.
See the CPS specific to your subscribers.
You must reprogram all subscribers, including those held as spares or reserves,
before the subscribers can use the system.
• New identifier information into the PSC 9600 site controllers at the sites using the archive
file created in step 3.
8 Configure any new channels or update any existing channels for the affected sites through the
Zone Configuration Manager (ZCM). See
See Volume 3, Managing Zone Infrastructure, for more information on entering this
information.
For Sub-band Restricted channels, be sure to set the Sub-band Restricted field
on the channel object to Yes.
You can bring channels into service after the sites have been prepared to identify
the new channels and the subscribers have been prepared to read the new channel
identifiers.
If the system uses other band trunking, you must be careful to match the transmit frequency and the receive
frequency for each channel in the Channel window and the Other Band Trunking window in the PSC 9600. If
these frequencies do not match on both windows, the Channel Mapping Validation Error dialog box appears:
If you are saving the PSC 9600 configuration data to an archive file, the Continue Saving button
appears on the dialog box and allows you to finish saving the file.
Motorola recommends that you do not program the PSC 9600 with an archive file after you receive
the Channel Mapping Validation Error dialog box. Check the file for incorrect frequencies.
Click the Close button in the upper right corner of the box to cancel the dialog box and to stop the file from saving.
If you are saving configuration data directly to the PSC 9600 and receive the Channel Mapping
Validation Error dialog box, the configuration data is not written to the device.
2 Click on each object in the navigation tree (left window pane) to view the parameters associated with that
object. Table 2-7 through Table 2-10 list the CSS application parameters for the following objects:
• System
• Zone
• Site
• Channel
"IntelliSite Repeater Configuration Parameters" on page 2-43 contains explanations of the parameters
associated with the “Configuration” object.
Fields marked with a “[*]” are controlled by the Zone Controller Manager (ZCM). You can set this
value locally through the CSS. However, the ZCM will overwrite the local values when the site
transitions to wide area trunking.
Table 2-10 CSS IntelliSite Repeater Channel Hardware Configuration Settings (Continued)
CSS Field Setting Range (default) Description
Disabled You must enter all frequency values
manually
Transmitter Frequency None (None) This read-only field displays the current transmitter band for
Band (MHz) [*] the selected station.
Tx Frequency (MHz) [*] 85100000 through This field lets you enter the Transmit Frequency (in MHz) for
86899375 the selected station. The system will display a warning if the
(default=85100000) value is invalid.
• For the VHF frequency band, the Tx Frequency value
must be divisible by 6.25 kHz or 2.5 kHz to be valid.
• For the UHF and 800 MHz frequency bands, the Tx
Frequency value must be divisible by 6.25 kHz or 5.0
kHz to be valid.
Transmitter Idle Frequency If Autocalculate The frequency that the IntelliSite Repeater tunes to if it is not
(MHz) [*] Frequencies = Enabled, transmitting (idle).
the field is read-only.
• If Autocalculate Frequencies is Enabled, this field is Read
If Autocalculate
Only.
Frequencies = Disabled, fill
in the values according to • If Autocalculate Frequencies is Disabled, you must enter
the description at the right. the Transmit Idle Frequency (in MHz) for the selected
station.
The system will display a warning if the value is invalid.
• For the VHF frequency band, the Tx Frequency value
must be divisible by 6.25 kHz or 2.5 kHz to be valid.
• For the UHF and 800 MHz frequency bands, the Tx
Frequency value must be divisible by 6.25 kHz or 5.0
kHz to be valid.
Tx Modulation Type [*] This field lets you select the modulation type that this station
• ASTRO CAI (LSM)
uses for transmission.
• ASTRO CAI (C4FM)
• ASTRO CAI (Wide
Pulse)
(default=ASTRO CAI
(C4FM))
Receiver Frequency Band Not Applicable The current receiver band for the selected station. This field is
(MHz) [*] read-only.
Rx Frequency (MHz) Not Applicable This field lets you enter the Receiver Frequency (in MHz) for
the selected station. The system will display a warning if the
value is invalid.
• For the VHF frequency band, the Rx Frequency value
must be divisible by 6.25 kHz or 2.5 kHz to be valid.
• For the UHF and 800 MHz frequency bands, the Rx
Frequency value must be divisible by 6.25 kHz or 5.0
kHz to be valid.
Table 2-10 CSS IntelliSite Repeater Channel Hardware Configuration Settings (Continued)
CSS Field Setting Range (default) Description
Rx Modulation Type This field lets you select the modulation type that this station
• ASTRO CAI (LSM)
uses for reception.
• ASTRO CAI (C4FM)
• ASTRO CAI (Wide
Pulse)
(default=ASTRO CAI
(C4FM))
Rx Bandwidth Narrow 12.5 kHz The bandwidth for the receiver channel.
Table 2-11 CSS IntelliSite Repeater Configuration Parameters: Hardware Configuration Tab
Table 2-11 CSS IntelliSite Repeater Configuration Parameters: Hardware Configuration Tab
(Continued)
CSS Field Setting Range (default) Description
Receiver Frequency Band This read-only field specifies the operating
(MHz) [*] frequency band for the IntelliSite Repeater Site
receiver
Power Amplifier Type This field specifies the type of power amplifier
• 800 MHz
at this station.
• 700 MHz
• VHF R1
• VHF R2
• UHF R0
• UHF R1
• UHF R2
• UHF R3
• UHF R4
• N/A
Power Amplifier Rating Depends on the value of the Power Specifies the output power rating for the power
[R] Amplifier Type field. amplifier at this station.
Tx Power Out Minimum This read-only field specifies the minimum
(Watts) output power for Tx Power Out (Watts) field on
the transmitter.
Tx Power Out Maximum This read-only field specifies the maximum
(Watts) output power for Tx Power Out (Watts) field on
the transmitter.
Tx Power Out (Watts) 100 (100) This field specifies the desired output power for
this IntelliSite Repeater.
TX Power Level Battery Not Applicable This field specifies the transmit output power
Backup (Watts) for this IntelliSite Repeater Site when the site is
operating from the backup battery power supply.
The station will maintain the PA output power
as defined in this field as long as the DC input
voltage is above 27 volts. When the DC power
drops below 27 volts, the output power will be
derated based on the input DC voltage level,
until the DC input voltage drops to 21 volts. At
that point, the output power will shut down to
protect the batteries.
Power Supply Type Variable; depends on the value in the Specifies the type of power supply for this
Hardware Platform Field IntelliSite Repeater site.
External Wattmeter Enabled or Disabled (default=Disabled) Specifies whether an external wattmeter is
Monitor connected to this station.
Table 2-11 CSS IntelliSite Repeater Configuration Parameters: Hardware Configuration Tab
(Continued)
CSS Field Setting Range (default) Description
Frequency Reference Internal - standard Specifies the source of the frequency reference
External - 5 MHz for the IntelliSite Repeater.
External - 10 MHz
Internal - High Stability (UHSO)
External - 5MHz/w fallback
External - 10MHz/w fallback
Internal - High Stability (UHSO)/w
fallback
Battery Type This field specifies what type of storage battery
• None
is at the site. This lets the power supplies’
• NICAD (Nickel-Cadmium) battery charging circuitry select the best
charging rate for the battery.
• LEAD ACID NON (sealed
Lead-Calcium acid)
• LEAD ACID LIN (vented
Lead-Calcium acid)
(default=None)
Table 2-12 CSS IntelliSite Repeater Configuration Parameters: Station Configuration (Continued)
CSS Field Setting Range (default) Description
Dynamic Frequency Enabled or Disabled This field enables or disables Dynamic
Blocking Capability (default=Disabled) Frequency Blocking for this IntelliSite Repeater.
• Enabled means this channel can have up
to seven interfering channels. Also, this
channel can be an interfering channel for
another channel.
DFB is incompatible with the Control
Channel Capability, the BSI Capability
and the Failsoft Capability. If DFB is
Enabled, these three configurations must
be disabled.
Table 2-12 CSS IntelliSite Repeater Configuration Parameters: Station Configuration (Continued)
CSS Field Setting Range (default) Description
Illegal Carrier Enabled or Disabled (default=Enabled) This field, together with the Malfunction Timer
Determination value(sec) [*] field, sets the station to detect an
illegal carrier for this frequency. This field also
disables the RF Threshold value (dBm) field so
you can set a value for the noise level.
• Enabled means that set IntelliSite Repeater
can detect an Illegal carrier, using the value
in the RF Threshold value (dBm) field.
• Disabled means that the IntelliSite
Repeater uses the -50 dBm value in the RF
Threshold value (dBm) field. If this field is
disabled, you cannot edit the RF Threshold
value (dBm) field.
The Illegal Carrier Determination field and the
Malfunction Timer Value field must be set to
the same value to work properly. If they are set
to different values, unpredictable behavior can
occur.
RF Threshold value (dBm) -50 dBm to -124 dBm This field sets the level (in dBm) for illegal
The default value depends on the type of carrier determination. If the IntelliSite Repeater
station and its frequency range: receives a signal above the level set in the
RF Threshold value field, and the IntelliSite
• Quantar (VHF); default=−90 dBm
Repeater is not assigned to a call, the IntelliSite
• Quantar (UHF); default=−101 dBm Repeater will consider the received signal to
be an illegal carrier. This field works with
• Quantar (800 mHz, C4FM);
the Malfunction Timer value(sec) [*] field to
default=−108 dBm
prevent an illegal carrier form disabling the
IntelliSite Repeater.
Malfunction Timer 1 through 253 seconds (default=50) This field sets the length of time a carrier
value(sec) [*] must exceed the Illegal Carrier threshold on
an unassigned channel before the IntelliSite
Repeater reports the carrier to the Zone Control
Manager (ZCM).
Table 2-13 CSS IntelliSite Repeater Configuration Parameters: Infrastructure Interface Tab
Table 2-13 CSS IntelliSite Repeater Configuration Parameters: Infrastructure Interface Tab
(Continued)
CSS Field Setting Range (default) Description
Infrastructure Transmit External (default=External) This read-only field indicates the clock source
Clock for the infrastructure interface. External
indicates that external equipment (such as a
channel bank) is providing the V.24 clock.
Digital Idle Link Check Enabled or Disabled (default=Enabled) This field allows you to determine if the station
is capable of monitoring the link continuity by
sending periodic messages to the comparator.
1 Connect a serial cable between the COM1 port on the laptop or PC which has the CSS application installed, and
the serial connector on the PSC 9600.
This assumes you connected the serial cable to COM1 as stated in step 1. If you used a different
COM port, select that port from the field instead.
5. Click Connect.
Result: An Information window will open and display a communication Setup message:
IF the PC and the PSC 9600... THEN...
Can communicate successfully: An Information window opens and displays the Communication Setup
Verified! message.
Continue with step 3.
Cannot communicate: An Error window opens and displays the CSS cannot establish a
physical connection with this device! message.
If this happens:
• Click the OK button to close the message.
• Check the connections to make sure they are good.
• Check the port IDs verify you have the correct COM ports identified.
Repeat step 2 until you get the Communication Setup Verified
message
You must establish communication between the PC and the device to continue.
Once you have downloaded the configuration data to the device, check it to make sure that it downloaded correctly.
Procedure 2-14 explains how to verify that the configuration data was copied success-
fully from the PC to the device.
Procedure 2-14 How to Verify the Configuration Data
1 Open a CSS connection to the device. Follow the steps in "Connecting Through
an Ethernet Link" on page 2-2
2 From the Versions menu, select Version.
Result: The Version screen opens.
4 Compare the software versions listed on the tab with the ones you have added. If
they are the same, you have uploaded the files successfully
The CSS IntelliSite Repeater window, Repeater Configuration, and Repeater Information tabs provide settings for
each repeater installed at the site. This is important for situations when the zone controller link is lost and the PSC
9600 must control the site. The PSC 9600 will assume the tasks of call processing and Resource Management.
The System ID (WACN ID), Site Timer and Repeater Configuration parameters are
essential to site (instead of Wide Area) operation.
Quantar stations used at the site may be configured for Mutual Aid. Mutual Aid stations are conventional
stations programmed according to your System Installation Guide documentation.
Versions of the Configuration/Service Software (CSS) supplied with ASTRO 25 do not support
configuration of conventional channels for use as Mutual Aid channels. To program stations for Mutual
Aid, use the latest version of Radio Service Software (RSS). See the latest version of the Quantar and
Quantro Radio Service Software User’s Guide (68P81085E35) for RSS references.
IP Address Definition
Windows for the Zone, Site, and IntelliSite Repeater allow the verification of the IntelliSite Repeater’s
network system, zone, and site parameters, most of which are manager-owned.
The digital voice and control data must be properly routed throughout the system. The transport devices were
programmed and their programming verified for proper routing of audio at the time of installation.
Unless there is a failure situation, do not make any changes or take actions with respect to the
transport devices, except to back up (and in the case of a failure, restore) their configuration data
as indicated in Volume 3, Managing Network Transport Equipment.
The following sections describe the devices that connect the IntelliSite Repeater to the rest of your system:
• "HP Procurve 2524 Switch" on page 2-53
• "S4000 Router" on page 2-63
You do not use CSS software to configure the HP Procurve 2524 switch. You must connect
to the switch and configure it using terminal emulation software.
This procedure is based on Software version F_02_13 of the HP Procurve 2524 switch.
Procedure 2-15 How to Connect to the HP Procurve 2524 Switch
Result: The switch IP address and the subnet mask are defined. The screen
displays the HP2524(config)# prompt.
3 Define the Switch IP default gateway:
1. Type ip default-gateway <IP ADDRESS>, where “<IP
ADDRESS>” is the actual IP address for the switch.
2. Press Enter.
Result: The Switch IP default gateway is defined. The screen displays the
HP2524(config)# prompt.
4 Define the Switch Time Server (NTP server):
1. Type ip timep manual <IP ADDRESS> interval 60, where
“60” is the polling interval.
The IP address for the NTP server will be different than the IP
address for the switch. The System Configuration Guide included
with your system will have the actual IP addresses.
2. Press Enter.
Result: The server and the polling interval are set. The screen displays the
HP2524(config)# prompt.
You cannot have any spaces in the text string. For example,
“Zone1_Site1” is a valid text string; “Zone 1 Site 1” is not.
2. Press Enter.
The prompt changes to HP2524(config)#.
Result: The System Name, System Contact, and System Location are defined.
The prompt changes to <Hostname_text_string>)#, using the system name
you created.
6 Define the switch time zone:
1. Type time timezone 0 daylight-time-rule none.
2. Press Enter.
• “ip address” is the IP addresses of the current zone and system SSC
HPOV servers.
If the current Zone HPOV server is the System HPOV, do not include
the System HPOV.
If there is no EMSC HPOV, do not include it.
2. Press Enter
Result: The switch SNMP trap receivers are set. The <Host-
name_text_string>)# prompt displays.
10 Define the Authentication Failure Trap:
1. Type snmp-server enable traps authentication
2. Press Enter.
Result: The maximum number of VLANs is set and the configuration is written
to flash memory.
12 Define the switch console inactivity timer:
1. At the command prompt, type: console inactivity-timer 10,
and press Enter.
2. At the command prompt, type: write memory, and press Enter.
Result: The switch console inactivity timer has been set and the configuration is
written to flash memory.
Result: The New Password prompt displays. Continue with the next step.
2 Type the new password and press Enter. The prompt changes to Please retype the new password.
After you have configured the switch, you must reboot it to make some of the settings, such as passwords, active.
Procedure 2-18 How to Reboot the Procurve 2524 Switch
You set the speed and duplex settings for ports 1 through 24. Ports 25 and 26
are the Gigabit ports used as trunk lines.
Procedure 2-19 How to Define Switch Port Speed and Duplex Settings
1 Make sure that the HP Procurve 2524 switch is still in “configure” mode:
IF the switch is... THEN...
In configure mode: Continue with step 2.
Not in configure mode: Repeat Procedure 2-14 to put the switch into configure mode. Then return
to step 2.
2 Configure port 1:
1. At the command prompt, type: interface ethernet 1 speed-duplex 100–full, where
• “1” is the Port number
2. Press Enter.
Result: The command prompt will return, and Port 1 will be configured.
Port 1 connects the Procurve 2524 switch to the LAN port on the site router.
Procedure 2-19 How to Define Switch Port Speed and Duplex Settings (Continued)
3 Configure the rest of the ports:
1. At the command prompt, type: interface ethernet x–xx speed-duplex 10–half where:
• “x-xx” are the ports you are configuring
An ASTRO 25 SE system does not support the redundant site link option. Ignore all
references to redundant site links or dual path diversity.
Port 1 of the second switch is reserved for connecting to the second router in a dual site link
configuration. Do not use the second port of switch 2 in a dual switch / single router configuration.
An ASTRO 25 SE system does not support the redundant site link option. Ignore all references
to redundant site links or dual path diversity.
2. Press Enter.
Result: A 2 Gigabit static trunk, using ports 25 and 26 on both switches is created.
Procedure 2-19 How to Define Switch Port Speed and Duplex Settings (Continued)
5 Define switch stacking:
1. At the command prompt, type no stack.
2. Press Enter.
An ASTRO 25 SE system does not contain the Cisco Catalyst 6509 Ethernet LAN switch (LAN
switch) or Nortel Passport 7480 WAN switch (WAN switch). Ignore all references to these switches.
1. At the command prompt, type no cdp run.
2. Press Enter.
Procedure 2-20 How to Exit the HP Procurve 2524 Switch Configuration Mode
S4000 Router
Commissioning of your ASTRO 25 system with an IntelliSite Repeater Site includes the configuration
of the site S4000 router. Depending on the system design, the site may either be configured
with a Zhone TeNSr channel bank (sites with Mutual Aid), or the site router may be connected
directly with the WAN via an S413 module installed in the router.
There are three ways to configure the S4000 router at the IntelliSite Repeater site:
• Using Router Manager to enter configuration parameters
• Downloading a configuration from a CD
• You will configure the router using a 3Com® 3C server application loaded on your workstation,
along with a terminal emulator program such as HyperTerminal or ProComm+.
• Your workstation has an IP address, Subnet Mask, and default gateway set as
defined by the system installation guides.
• You are configuring a new site, or an existing site with a replacement router.
If you use a TFTP server application other than the 3Com TFTP server application, the command
syntax and setup scenario may be slightly different than that shown in the following procedures.
3. Launch the emulator program and verify its configuration (9600, 8, N, 1),
then press Enter.
4. Type root (root is the Default account name).
Result: The following prompt is displayed:
Password:
5. Press Enter.
Result: The Enterprise OS# prompt is displayed. You are now logged on
to the router.
2 Change directories to the directory in which the desired configuration file is
to be stored by typing Router#cd a:/primary, where a:/primary is the router
directory.
Result: The system returns a Router# prompt indicating the new directory as:
Router# a:/primary
3 At the Router# prompt, enter the following command:
Router#SetD !1 —IP NETA=10.101.2.254 255.255.255.0
Result: The router IP is defined.
Procedure 2-21 How to Download a Stored Configuration File to the S4000 (Continued)
4 Select and run the 3Com TFTP Server application from the Windows Program
Menu.
Result: The 3Com 3CServer window opens.
Procedure 2-21 How to Download a Stored Configuration File to the S4000 (Continued)
6 Select the TFTP Configuration tab.
Result: The TFTP Configuration window opens.
Procedure 2-21 How to Download a Stored Configuration File to the S4000 (Continued)
7 Click the Browse Directories button to select the directory which contains the
stored configuration file. For example, assume that the desired configuration file
is stored on a floppy disk in drive a: of the workstation as “z1s001.cfg” and that
the file is on the root directory of the floppy in a: drive.
Procedure 2-21 How to Download a Stored Configuration File to the S4000 (Continued)
8 Return to the terminal program. At the Router# prompt, copy the required
router configuration file from the default directory of the TFTP server,
using the following command: copy 10.101.2.x z1s002.cfg
a:/primary/boot.cfg. For example, assume you wish to copy the Zone 1,
Site 2 configuration “z1s002.cfg” to the default directory of the TFTP server.
Manual configuration of the site router should only be performed as a last option, if no
record exists in the system of the stored site router configuration that was provided
when the system was commissioned. Good practice is to store at least one copy on
removable media of each device configuration at the site in which the device is used.
The process of manually configuring an S4000 follows the same steps, whether the router is to be
configured for use with a Zhone TeNSr Channel Bank and Mutual Aid, or for direct connection
to a T1 using an S413 module; however, some parameter values will be different.
Process 2-4 Entering a Configuration into the S4000 Site Router
1 Connect to the S4000 Site Router using Procedure 2-22, "How to Connect to the
S4000 Router," on page 2-70.
Result: Communication with the site router is established.
2 Enter System Setup parameters first, establishing prompts, welcome messages,
and related router configuration settings, using:
• Procedure 2-23, "How to Enter FlexWAN V.35 - System Setup Parameters,"
on page 2-71
• Procedure 2-29, "How to Enter T1-S413 - System Setup Parameters," on
page 2-83
Result: The overall System Setup Parameters are established for the site router.
3 Disable all site router ports.
Result: This prevents network management errors.
4 Enable routing.
Result: The site router is enabled to route packets.
5 Enter the parameters according to these procedures:
• Procedure 2-31, "How to Enter T1-S413 Frame Relay, Interface Addressing
and Static Route Setup Parameters," on page 2-87
• Procedure 2-32, "How to Enter T1-S413 - Multicast and Priority Queuing
Setup Parameters," on page 2-88
• Procedure 2-33, "How to Enter T1-S413 - SNMP and FR.12 Setup
Parameters," on page 2-91
• Procedure 2-34, "How to Enter T1-S413 - DHCP, NTP, and Port and Path
Re-Enabling Setup Parameters," on page 2-94
6 Save the configuration created in step 5 to a file on a workstation drive.
Result: A configuration file is available for downloading to the site router.
1 Connect a serial cable between the console port of the S4000 router and the
workstation PC. Also connect the workstation Ethernet port to the router, using a
CAT-5 crossover cable. (The crossover cable crosses pins 1 and 2 over to pins
3 and 6.)
Result: The workstation is connected to the S4000 site router.
2 Launch the emulator program and verify its configuration (9600, 8, N, 1) then
press Enter.
Result: The Entitling prompt is displayed.
3 Type root (root is the Default account name).
Result: The Password prompt is displayed.
4 Press Enter.
FlexWAN V.35 is only used at IntelliSite Repeater Sites that use mutual aid.
If you are configuring an S4000 at an IntelliSite Repeater site that does not have mutual aid, follow
the procedure in "Configuring the S4000 for T1-S413 " on page 2-83.
This section contains information on:
• "FlexWAN V.35 System Setup Parameters" on page 2-72
• "Routing, Port, Path, and Virtual Path Parameters" on page 2-73
• "Multicast and Priority Queuing Setup Parameters" on page 2-76
"Frame Relay, Interface Addressing, and Static Route Setup Parameters" on page 2-74
The first step in configuring the S4000 is to enter a series of System Parameters and to disable unused ports. Both
steps are shown in Procedure 2-23. Values such as system name and contact would be different for your system.
Note that, while the parameters are listed one after the other in the procedure, each must be typed
and Enter pressed, then the next parameter typed and Enter pressed again, until all parameters in
the procedure have been entered. After each parameter is entered, the Enterprise OS# reappears.
Definitions for each line of the System Setup Parameters are shown in Table 2-14.
The configuration information shown in this procedure is only an example. You must
insert actual values per your system documentation. Examples in the System Parameters
include the location of the Sys Location and the System Contact, which would be
changed to reflect your system location and contact person.
Follow Procedure 2-23 to enter the FlexWAN V.35 system setup parameters.
Procedure 2-23 How to Enter FlexWAN V.35 - System Setup Parameters
1 Set up the System Parameters for the S4000 site router. Type
SETD -SYS NMPrompt = “Z1_Site001 # “
SETD —SYS Prompt = “Z1_Site001 >”
SETD -SYS WelcomeString = “Welcome to Zone 1 Site
Router 1 “
SETD -SYS SysLOCation = “New Sit Lab”
SETD -SYS STSNAMe = “Z1_Site001”
SETD -SYS TimeZone = 0
SETD -NMPassWord = ““ ““ ““
Result: The system parameters are set.
2 Disable the unused ports. Type
SETD !4 -POrt CONTrol = Disable
SETD !4 -PAth CONTrol = Disable
Result: The unused ports are disabled.
Table 2-14 describes the system setup parameters for the S4000.
Parameter Description
NMPrompt Specifies the string (maximum of 14 characters) that the
bridge/router uses as the prompt on the local device (starting
in column 1) to indicate that the port has Network Manager
privilege. If you set the prompt for greater than 14 characters, it
is truncated to 14, and the message “String truncated” appears.
Set per your System Installation Guide.
SYSPrompt Specifies the string (maximum of 14 characters) that the
bridge/router uses as the prompt on the local device (starting
in column 1) to prompt when the user does not have Network
Manager privilege.
System WelcomeString Specifies the text string displayed when logging into the router
from the console or Telnet session. Set per your System
Installation Guide.
SysLOCation Specifies the physical location of the router. Set per your
System Installation Guide.
SysCONtact Specifies a string that identifies the name of a contact person
responsible for this managed router. You can also specify
information on how to contact the person, such as a telephone
number or address. Set per your System Installation Guide.
The next group of parameters you enter establish site router routing, port, path, and virtual path capabilities.
A description of each line in the configuration is shown in Table 2-15 on page 2-74.
Entering the FlexWAN V.35 Routing, Port, Path, and Virtual Path Parameters
In this step, the PAth Baud rate is the WAN link speed of 1024.
Result: Port, path, and virtual port settings are established.
Table 2-15 describes the routing, port, path, and virtual port setup parameters.
Table 2-15 FlexWAN V.35 - Routing, Port, Path, and Virtual Port Setup Parameters
Parameter Description
IP CONTrol Determines whether the system performs IP routing and how
the routing function is performed. The values within each pair
are mutually exclusive. The values specified apply to the global
IP routing function, not just to a particular interface.
PA BAudPAth Set port communication parameters for the router ports.
DUplexPOrt OWNer
POrt Virtual Port Maps the virtual ports to the FRAME dlci 16 and 17, which
are the redundant site control paths (SCPs) between the Zone
Controller and the site. These frame circuits 16 and 17 are
identifiers used for the WAN switch at the Master Site for
purposes of cross-connecting to the other dlci in the Core router
(Master Site) for eventual link to the Zone Controller.
The next step in configuring the S4000 is entering the frame relay, interface addressing,
and static route setup parameters.
Descriptions of the setup parameters appear in Table 2-16.
Procedure 2-25 explains how to enter the Frame Relay, Interface Addressing, and Static Route setup parameters.
Procedure 2-25 How to Enter FlexWAN V.35 - Frame Relay, Interface Addressing,
and Static Route Setup Parameters
Table 2-16 describes the Frame Relay, Interface Addressing, and Static Route setup parameters.
Table 2-16 Description of Frame Relay, Interface Addressing and Static Route Parameters
Parameter Description
CONTrol Determines whether the Line Management Interface (LMI)
Protocol works on a specified port. You must use the -POrt
OWNer parameter to enable the FR Service.
KeepAliveTimer (KAT) Specifies the amount of time (in units of 100ms) between
transmission of keep alive packets. The range is 1-300 (100ms
to 30 seconds).
CIRbothdir Specifies the throughput parameters for data coming in and
going out through the specified virtual circuit identifier and
the specified parent port.
NETaddr Assigns an IP address to the specified port and configures a
directly connected IP network or subnet on a specified port.
ADD - IP ROUTe x.x.x.x (For IntelliSite Repeater and Simulcast Prime Site Subnets.)
255.255.255.0 x.x.x.x 5 Sets static routes for the site router.
Override
The next step in programming the S4000 site router is to enter the Multicast and Priority Queuing setup parameters.
Descriptions of the setup parameters appear in Table 2-17.
Procedure 2-26 explains how to enter the Multicast and priority queuing setup parameters.
Procedure 2-26 How to Enter FlexWAN V.35 - Multicast and Priority Queuing Setup Parameters
Table 2-17 describes the Multicast and Priority Queuing setup parameters.
Parameter Description
CONTrol Enables or disables multicast routing, and displays whether multicast routing is in
service.
IgmpControl Used to control the IGMP host/router functionality, as well as administratively set the
IGMP version number.
QueryInterval Specifies how often an IGMP Query message is sent to request local group
membership. Only the designated router sends the queries onto the associated network.
The designated router is elected if it has the lowest IP address on that network (when
running the DVMRP Protocol) or the one with the highest router priority (when running
the MOSPF Protocol).
LeaveInterval Sets the leave latency. When a bridge/router receives an IGMP leave from the local
host, it sends a group-specific query to check to see if there are any other hosts
interested in receiving the traffic for that group. The group-specific queries are sent
twice at an interval which is a function of the query interval and it can take up to a few
seconds before the traffic is actually stopped.
Table 2-17 Description of Multicast and Priority Queuing Setup Parameters (Continued)
Parameter Description
CONTrol Manipulates PIM-SM version2 functionality on a per-port basis using. If PIM CONTrol
is enabled on a port and the IGMPControl parameter of the -MIP service is disabled
on the same interface, IGMPv2 behavior is automatically enabled on the interface
to ensure proper functionality
GblSPTThreshold (Global Allows the user to specify the threshold value for switching to a Shortest Path Tree
Shortest Path Tree Threshold) (SPT) for any (S,G) multicast flow. PIM-SM supports the ability to switch from a
shared tree to a shortest path tree based on data rates. If the threshold value gets
exceeded for an (S,G) multicast flow, the PIM-SM module initiates procedures to
switch the PIM routing state for the (S,G) flow to a shortest path tree from a shared
tree. If set to Infinity, PIM routing state for all sources for “applicable IP multicast
destinations” is never switched from the shared tree to the Shortest Path Tree (SPT).
MultipleJoins Used to enable or disable multiple joins on the router, depending on the reliability of
the link. If you set MultipleJoins to Enable, the router will send the number of joins
specified by the RetryCount option at the calculated interval.
JoinPruneAgg A PIM-SM Timer-related configuration parameter which controls the aggregation
PIM JoinPrune messages.
QueueMethod Applies only when RealTime priority queuing is enabled (RealTimeQueue is set to
RealTimeQueue). For remote site (edge) routers, set QueueMethod to PathBasedQueue.
RealTimeQueue Indicates the type of priority queuing to be used on the entire Frame Relay interface:
realtime priority queuing or non-realtime PQH (priority queue handler) priority
queuing.
QueueInterLeave Determines the forwarding ratio of packets in the high- to medium-priority queues and
the forwarding ratio of packets in the medium-to-low-priority queues. The values
you specify identify the number of high-priority packets that are transmitted for each
medium-priority packet and the number of medium-priority packets that are transmitted
for each low-priority packet.
TosQueue Enables assignment of IP packets to TOS-based priority queues on the outbound port.
The next step in programming the S4000 site router is to enter the Simplified Network Management
Protocol (SNMP) and Fragmentation Control (FR.12) setup parameters.
The description of each parameter is shown in Table 2-18.
Procedure 2-27 explains how to enter the SNMP and Fragmentation control parameters.
In step 2 of Procedure 2-27, the FragPktSize is a function of the number of DSOs, line speed,
and other factors. Table 2-19 shows how these factors are related.
Procedure 2-27 How to Enter FlexWAN V.35 - SNMP and FR.12 Setup Parameters
Table 2-18 describes the SNMP and Fragmentation (FR. 12) setup parameters.
Table 2-18 Description of SNMP and Fragmentation (FR. 12) Setup Parameters
Parameter Description
CONTrol Determines how the SNMP agent operates. Trap | NoTrap -
Enables or disables trap generation. Traps can be generated
even if NoManage is selected. Authentication failure traps are
not generated because all incoming requests are ignored.
Table 2-18 Description of SNMP and Fragmentation (FR. 12) Setup Parameters (Continued)
COMmunity Modifies the list of communities. A community is named by a
string of octets and is used for authenticating SNMP messages.
A request is valid only if the community name is included in
the list. A maximum of six community names is allowed in
the request list.
• ANYCOM is a reserved com.name. It allows requests
with any community name to be handled. When the
community list is checked upon the arrival of a request, the
entry under ANYCOM is checked last. If an entry under
any other community name is found, the information in
that entry is used instead of that under ANYCOM. If traps
are configured for ANYCOM, the community name field
in the trap PDU is left blank.
• TRiv specifies the authentication scheme. The Trivial
scheme is selected by default.
• RO | RW specifies the access to the management
information base (MIB). RO means read-only; RW means
read-write access. By default, RO is selected.
• ALl | NOne ALl means both general and authentication
and enterprise-specific traps as well as enterprise-specific
traps.
• NOne (the default) means no traps are generated for
managers using this community string.
RtqFragLevel Indicates the priority level at and below which packets will
be candidates for fragmentation. Long packets at and below
the specified priority level will be fragmented to reduce
delay—provided fragmentation is enabled on the specific
Virtual Circuit (VC) (FragType is not set to No) and the packet
length exceeds the MTU of the maximum fragment size
allowed (as specified by the FragPktSize parameter).
FragType Specifies the type of fragmentation control or disables
fragmentation on the specified Virtual Circuit (VC).
FragPktSize Specifies the maximum packet size for the specified <vcid>
when fragmentation is enabled for a VC [where <vcid> refers
to a DLCI (PVC)]. Packets larger than the specified maximum
are fragmented into multiple packets with MTU sizes of the
specified FragPktSize or smaller.
Table 2-19 provides a reference for the determination of Fragmentation size as a function of
DSOs, line speed, Router CIR, and ASTRO repeaters.
The next step in programming the S4000 site router is to enter the Dynamic Host Control, Network
Time Protocol and port and path re-enabling setup parameters.
Descriptions of each parameter are in Table 2-20.
DHCP, NTP, and Port and Path Re-Enabling Setup Parameter Descriptions
Table 2-20 describes the DHCP, NTP, and port and path re-enabling parameters.
Table 2-20 Description of DHCP, NTP and Port and Path Re-enabling Parameters
Parameter Description
CONTrol A per-port parameter that controls the DHCP operation on a
specific port. The DHCP server feature is performed only when
CONTrol is set to Enabled.
ADD -DHCP PRoFile Creates a new profile and copies the contents of profile P1 to
the new profile as the contents template. The default profile
(P1) is provided by the system.
AddressPool/ Designates an active address pool from either the address pool
DeftAddressPool or the default address pool. When you specify AddressPool,
DHCP uses the user-configured address pool (defined in
AddressPool) as its active address pool.
ProfDNS Specifies a list of Domain Name System name servers available
to the client.
ProfLEASE Specifies the lease time that DHCP server offers for the client
to use the IP address.
ProfReBindTimer Specifies the rebinding time (T2). Based on this timer, the
server informs the client to start its rebinding process.
ProfReNewTimer Specifies the renewal time (T1). The timer triggers the client to
start its renew processing. The T1 value must be less than the
ProfLEASE value and greater than the ProfReBindTimer value.
NTP CONTrol Enables or disables the ability of the S4000 site router to obtain
input from the NTP primary and backup servers.
NTP PrimarySrvr Specifies the IP address of the primary NTP server.
NTP BackupSrvr Specifies the IP address of the backup NTP server.
Configure the site router manually only as a last option. You may need to
configure the site manually if no record exists in the system of the site router
configuration that Motorola provided when the system was commissioned.
Good practice is to store at least one copy of each device configuration, on
removable media, at the site where the device is used.
While the parameters are listed one after the other in the procedure, you must type a parameter and
press Enter, then type the next parameter and press Enter again, until you have entered all the
parameters in the procedure. After you enter each parameter the Enterprise OS# prompt reappears.
Values such as “system name” and “contact” would be different for your system.
Procedure 2-29 How to Enter T1-S413 - System Setup Parameters
1 Set up the System Parameters for the S4000 site router. Type
SETD -SYS NMPrompt = “Z1_Site0002#“
SETD -SYS Prompt = “Z1_Site0002 > “
SETD -SYS Prompt = “Welcome to Zone 1 Site Router 2”
SETD -SYS SYSLOCation = “Your Location”
SETD -SYS SYSCONtact = “Your Contact”
SETD -SYS SYSNAMe = “Z1_Site002”
SETD -SYS TimeZone = 0
SETD -SYS NMPassWord = ““ ““ ““
Result: The system parameters are set.
2 Disable the unused ports. Type
SETD !3 -POrt CONTrol = Disable
SETD !3 -PAth CONTrol = Disable
SETD !4 -POrt CONTrol = Disable
SETD !4 -Path CONTrol = Disable
Result: The unused ports are disabled.
Table 2-21 describes the System Setup parameters for the S4000 for T1 connection using the S413 module.
Parameter Description
NMPrompt This field specifies the string (maximum of 14 characters)
that the bridge/router uses as the prompt on the local
device (starting in column 1) to indicate that the port has
Network Manager privilege. If you set the prompt for
greater than 14 characters, it is truncated to 14, and the
message “String truncated” appears. Set per your System
Installation Guide.
SYSPrompt Specifies the string (maximum of 14 characters) that
the bridge/router uses as the prompt on the local device
(starting in column 1) to prompt when the user does not
have Network Manager privilege.
System WelcomeString Specifies the text string displayed when logging into the
router from the console or Telnet session. Set per your
System Installation Guide.
SysLOCation Specifies the physical location of the router. Set per your
System Installation Guide.
SysCONtact Specifies a string that identifies the name of a contact
person responsible for this managed router. You can also
specify information on how to contact the person, such
as a telephone number or address. Set this parameter
according to your System Installation Guide.
The next group of parameters to be entered are used to establish site router routing,
port, path, and virtual port capabilities.
The description of each line in the configuration appears in Table 2-22.
Table 2-22 describes the T1-S413 routing, port, path, and virtual path parameters.
Table 2-22 T1-S413 Routing, Port, Path, and Virtual Path Parameter Descriptions
Parameter Description
FrameMode Allows you to specify the frame mode.
LineCoding Specifies the transmission encoding method for the T1
or E1 line. The coding method you specify for the line
must match the attached communication device. B8ZS
or AMI should be used for T1 connectors and HDB3 or
AMI should be used for E1 connectors
LineDistance Specifies the compensation required for line length.
Table 2-22 T1-S413 Routing, Port, Path, and Virtual Path Parameter Descriptions (Continued)
CLock Determines how the bridge/router derives its transmit
clock. This parameter applies only to serial interfaces.
For the new value to take effect on all routers, you must
re-enable the corresponding path. External indicates the
bridge/router derives the transmit clock from the send
or receive timing clock supplied by the digital service
unit/channel service unit (DSU/CSU) or by the Network
Time Server.
ChannelBaud Specifies the baud rate (56kbits/sec or 64kbits/sec) of
each time slot (such as channel) mapped to the specified
path. All time slots mapped to a given path must be
equivalent in baud rate.
ChannelMap Specifies the time slots (such as channels) associated
with the specified path. In this case, all twenty-four time
slots are deleted, and the first sixteen are then added.
IP CONTrol Determines whether the system performs IP routing and
how the routing function is performed. The values within
each pair are mutually exclusive. The values specified
apply to the global IP routing function, not just to a
particular interface.
PA BAudPAth DUplexPOrt Sets port communication parameters for the router ports.
OWNer
POrt Virtual Port Defines the identity and operation of the site router virtual
ports, which are needed to communicate with VLANS.
T1-S413 Frame Relay, Interface Addressing, and Static Route Setup Parameters
The next step in programming the S4000 site router for T1 connection using the S413 module is to
enter the Frame Relay, Interface Addressing, and Static route setup parameters.
Table 2-23 gives a description of each parameter.
T1-S413 Frame Relay, Interface, and Static Route Setup Parameter Descriptions
Table 2-23 describes the T1-S413 Frame Relay, interface, and route setup parameters.
Table 2-23 Description of T1-S413 Frame Relay, Interface, and Static Route Setup Parameters
Parameter Description
CONTrol Determines whether the Line Management Interface
(LMI) Protocol runs over a specified port. You must use
the POrt OWNer parameter to enable the FR Service.
KeepAliveTimer (KAT) Specifies the amount of time (in units of 100ms) between
transmission of keep alive packets. The set-able range is
1-300 (100 ms to 30 seconds).
Table 2-23 Description of T1-S413 Frame Relay, Interface, and Static Route Setup Parameters
(Continued)
CIRbothdir Specifies the throughput parameters for data coming
in and going out through the specified virtual circuit
identifier and the specified parent port.
NETaddr Assigns an IP address to the specified port and configures
a directly connected IP network or subnet on a specified
port.
ADD - IP ROUTe x.x.x.x (for IntelliSite Repeater and Simulcast Prime Site
255.255.255.0 x.x.x.x 5 Override Subnets) Sets static routes for the site router.
The next step in programming the S4000 site router for T1 connection using the S413 module is
to enter the Multicast and Priority Queuing setup parameters.
Table 2-24 gives descriptions of each parameter.
Table 2-24 describes the Multicast and Priority Queuing setup parameters.
Parameter Description
MIP CONTrol Enables or disables multicast routing, and displays
whether multicast routing is in service.
IgmpControl Used to control the IGMP host/router functionality as
well as administratively set the IGMP version number.
QueryInterval Specifies how often an IGMP Query message is sent to
request local group membership. Only the designated
router sends the queries onto the associated network. The
designated router is elected if it has the lowest IP address
on that network (when running the DVMRP Protocol) or
the one with the highest router priority (when running
the MOSPF Protocol).
LeaveInterval Sets the leave latency. When a bridge/router receives an
IGMP leave from the local host, it sends a group-specific
query to check to see if there are any other hosts interested
in receiving the traffic for that group. The group-specific
queries are sent twice at an interval which is a function
of the query interval and it can take up to a few seconds
before the traffic is actually stopped.
PIM CONTrol Manipulates PIM-SM version2 functionality on a per-port
basis. If PIM CONTrol is enabled on a port and the
IGMPControl parameter of the -MIP service is disabled
on the same interface, IGMPv2 behavior is automatically
enabled on the interface to ensure proper functionality.
PIM HelloOption GenID A 32-bit unsigned number used to reduce convergence
(Generation Identifier) time on PIM networks. The GenID option enables PIM
routers to quickly detect any new neighbor and thus to
synchronize RP-Set information and routing table entries
by triggering BootStrap and Join/Prune messages to
the new neighbor. When GenID is enabled on a PIM
router, each interface on the router is randomly assigned
a different GenID number when it boots up. The GenID
numbers remain the same as long as the interfaces are up.
If the router reboots or an interface is toggled on and off,
new GenID numbers are assigned. Based on the changed
GenID numbers, other PIM neighbors can immediately
detect the reboot or interface toggle and send RP-Set and
Join/Prune messages—without waiting for the periodic
messages. Thus the PIM network is able to converge
more quickly.
Table 2-24 Description of Multicast and Priority Queuing Setup Parameters (Continued)
Parameter Description
GblSPTThreshold (Global Allows the user to specify the threshold value for
Shortest Path Tree Threshold) switching to a Shortest Path Tree (SPT) for any (S,G)
multicast flow. PIM-SIM supports the ability to switch
from a shared tree to a shortest path tree based on data
rates. If the threshold value gets exceeded for an (S,G)
multicast flow, the PIM-SM module initiates procedures
to switch the PIM routing state for the (S,G) flow to a
shortest path tree from a shared tree. If set to Infinity,
PIM routing state for all sources for “applicable IP
multicast destinations” is never switched from the shared
tree to the Shortest Path Tree (SPT).
MultipleJoins Used to enable or disable multiple joins on the router,
depending on the reliability of the link. If you set
MultipleJoins to Enable, the router will send the number
of joins specified by the RetryCount option at the
calculated interval.
JoinPruneAgg A PIM-SM Timer-related configuration parameter which
controls the aggregation PIM JoinPrune messages.
QueueMethod Applies only when RealTime priority queuing is
enabled (RealTimeQueue is set to RealTimeQueue).
For remote site (edge) routers, set QueueMethod to
PathBasedQueue.
RealTimeQueue Indicates the type of priority queuing to be used on the
entire Frame Relay interface: real-time priority queuing
or non-realtime PQH (priority queue handler) priority
queuing.
QueueInterLeave Determines the forwarding ratio of packets in the high-
to medium-priority queues and the forwarding ratio
of packets in the medium-to-low-priority queues. The
values you specify identify the number of high-priority
packets that are transmitted for each medium-priority
packet and the number of medium-priority packets that
are transmitted for each low-priority packet.
TosQueue Enables assignment of IP packets to TOS-based priority
queues on the outbound port.
The next step in programming the S4000 site router for T1 connection using the S413 module is to enter the
Simplified Network Management Protocol (SNMP) and Fragmentation Control (FR.12) setup parameters.
Table 2-25 gives a description of each parameter.
In step 2 of Procedure 2-33, the FragPktSize is a function of the number of DSOs, line speed,
and other factors. Table 2-25 shows how these factors are related.
Procedure 2-33 How to Enter T1-S413 - SNMP and FR.12 Setup Parameters
Table 2-25 SNMP and Fragmentation (FR. 12) Setup Parameter Descriptions
Table 2-25 SNMP and Fragmentation (FR. 12) Setup Parameter Descriptions (Continued)
Parameter Valid Input Description
COMmunity Modifies the list of communities. A community is named by a
• ANYCOM
string of octets and is used for authenticating SNMP messages.
• TRiv A request is valid only if the community name is included in
the list. A maximum of six community names is allowed in the
• RO
request list. There is a reserved com.name called ANYCOM. It
• RW allows requests with any community name to be handled. When
the community list is checked upon the arrival of a request, the
• ALl entry under ANYCOM is checked last. If an entry under any
• NOne other community name is found, the information in that entry is
used instead of that under ANYCOM. If traps are configured
for ANYCOM, the community name field in the trap PDU
is left blank. TRiv specifies the authentication scheme. The
Trivial scheme is selected by default. RO or RW specifies the
access to the management information base (MIB).
• RO means read-only.
• RW means read-write access.
RO is the default.
ALl or NOne:
• ALl means both general and authentication and
enterprise-specific traps as well as enterprise-specific
traps.
• NOne (the default) means no traps are generated for
managers using this community string.
NOne is the default.
RtqFragLevel Indicates the priority level at and below which packets will
be candidates for fragmentation. Long packets at and below
the specified priority level will be fragmented to reduce
delay—provided fragmentation is enabled on the specific
Virtual Circuit (VC) (FragType is not set to No) and the packet
length exceeds the MTU of the maximum fragment size
allowed (as specified by the FragPktSize parameter).
FragType Specifies the type of fragmentation control or disables
fragmentation on the specified Virtual Circuit (VC).
FragPktSize The parameter specifies the maximum packet size for the
specified <vcid>, when fragmentation is enabled for a VC
[where <vcid> refers to a DLCI (PVC)]. Packets larger than the
specified maximum are fragmented into multiple packets with
MTU sizes of the specified FragPktSize or smaller.
Table 2-19, "Fragmentation Size ," on page 2-81 provides a reference for the determination of Fragmentation
size as a function of DSOs, line speed, Router CIR, and ASTRO repeaters.
The final step in programming the S4000 site router for T1 connection using the S413 module is to enter
the Dynamic Host Control, Network Time Server, and Port and Path Re-enabling setup parameters, save
the file to the appropriate workstation drive, and download the store file to the site router.
Table 2-26 describes the values for the fields.
DHCP, NTP, and Port and Path Re-Enabling Setup Parameter Descriptions
Table 2-26 describes the DHCP, NTP, and port and path re-enabling setup parameters.
Table 2-26 DHCP, NTP, and Port and Path Re-Enabling Setup Parameter Descriptions
Parameter Description
CONTrol A per-port parameter. It controls the DHCP operation on
a specific port. The DHCP server feature is performed
only when CONTrol is set to Enabled.
ADD -DHCP PRoFile Creates a new profile and copies the contents of profile
P1 to the new profile as the contents template. The
default profile (P1) is provided by the system.
AddressPool/ DeftAddressPool Designates an active address pool from either the address
pool or the default address pool. When you specify
AddressPool, DHCP uses the user-configured address
pool (defined in AddressPool) as its active address pool
ProfDNS Specifies a list of Domain Name System name servers
available to the client.
ProfLEASE Specifies the lease time that DHCP server offers for the
client to use the IP address.
ProfReBindTimer Specifies the rebinding time (T2). Based on this timer,
the server informs the client to start its rebinding process.
ProfReNewTimer Specifies the renewal time (T1). The timer triggers the
client to start its renew processing. The T1 value must
be less than the ProfLEASE value and greater than the
ProfReBindTimer value.
NTP CONTrol Enables or disables the ability of the S4000 site router to
obtain input from the NTP primary and backup servers.
NTP PrimarySrvr Specifies the IP address of the primary NTP server.
NTP BackupSrvr Specifies the IP address of the backup NTP server.
The following sections provide an overview of the configuration of the TeNSr channel bank.
For more information, see the Zhone TeNSr manual.
This is dependent on the field design and is not directed from the system level, other than to caution
against putting all the channels to a site over a single T1 or path. When possible, use multiple routes
to and from each site for redundancy to avoid a single point of failure.
Requirements
You must have the following equipment to perform this procedure:
• A PC with a terminal emulation program installed.
• A serial cable female DB9 to RJ45 or female DB9.
Additionally, the channel bank software must be at version 5.3.1 or later.
Procedure
Follow Procedure 2-35 to set up the channel bank.
Procedure 2-35 How to Set Up the Channel Bank
1 Connect the serial cable from the PC COM1 port to the TERM port on the
interface board in the channel bank.
If you use a different COM port, select that port from the field instead.
Result: The hardware is in place for a serial connection to the channel bank.
2 Open Microsoft HyperTerminal and press Enter twice.
Result: The PC establishes a serial connection to the channel bank.
3 At the login prompt, type the correct login name according to your system
documentation and press Enter. Type the correct password according to your
system documentation and press Enter.
Result: The main window opens.
4 Tab to Config and press Enter.
Result: The Configuration window appears, summarizing the current status
of the TeNSr.
5 Tab to the Config option and press Enter. Then tab to the WAN selection in the
lower select bar and press Enter again.
Result: The Configuration menu appears.
6 Tab to the WAN card option and press Enter. Then configure the TeNSr cards as
shown in Table 2-27.
Table 2-27 provides the required settings for the TeNSr channel bank cards. All parameters
not listed use default values. Some of the settings are default, but because they affect system
operation, they are listed to ensure they are set properly.
These are generic settings. For specific settings for your system as originally configured, see the
System Installation Guide that came with your system. For additional information, or if you wish to
use other cards not originally installed with your system, see the TeNSr manual.
3. Select direct.
3. Select direct.
MOSCAD configuration is generally done by the Motorola representative who configures your site
initially. When it is necessary to re-configure the MOSCAD system (the NFM RTU), this is usually
accomplished by downloading a site configuration file provided by Motorola, using Site Builder. This
site configuration file is downloaded to the MOSCAD NFM RTU (Network Fault Management Remote
Terminal Unit) using a laptop on which the Toolbox and Site Builder applications are already installed,
and on which the necessary MOSCAD site configuration file has been stored.
After installing the IntelliSite Repeater, check the RF measurements to be sure the station is operating
at the correct levels. These RF measurements include the following:
• "Generating ASTRO Test Patterns" on page 2-103
• "Measuring the Bit Error Rate" on page 2-106“
• "Measuring the Receive Signal Strength Indicator (RSSI)" on page 2-108
• "Calibrating the Reference Oscillator and UHSO" on page 2-109
• "Calibrating the RSSI" on page 2-118
• "Aligning Reference Modulation Compensation" on page 2-120
• "Aligning the Power Output " on page 2-124
• "Aligning the Transmit Deviation" on page 2-126
• "Checking Receiver Desensitivity" on page 2-127
You generate ASTRO test patterns to verify that the ASTRO signaling patterns from the station meet
the ASTRO standards. Procedure 2-36 explains how to test the signaling patterns.
Procedure 2-36 How to Generate the ASTRO Test Patterns
• Open the Test and Measurement Screen dialog box, as described in step 1.
4. When you have the Test and Measurement screen open, continue with step 4.
4 Connect the service monitor to the station using the following steps:
1. Remove the N-Type connector from transmit output.
2. Connect the N-to-N cable from the analyzer to transmit output.
Table 2-28 lists the deviation standards for each ASTRO test pattern.
The specifications in this table allow a spread of ± 10%. However, the accuracy of the service
monitor needs to be taken into account. Since the accuracy of the service monitor is only ± 5%, the
allowable spread in the measured deviation should only be ± 5% and not ± 10%.
Procedure 2-37 explains how to measure the Bit Error Rate (BER) for the station.
Procedure 2-37 How to Measure the BER
5 Click OK.
Result: The station begins a reset sequence to change modes, which takes a
few seconds. After resetting, you must read the configuration data again from
the base radio and then open the Test and Measurement Screen dialog box as
described in step 1.
6 Select V.52 from the Pattern Type field.
7 Enter the number of second you want from the Sampling Period (sec) list box.
This field allows you to determine the length of time before the report is updated.
8 Measure the BER:
1. Click the Start BER Measurement button.
Result: The Test and Measurement Screen window displays the measurements
for the BER in the Results form.
2. Click the Start Log button to create a log file for the BER measurement.
3. Click the Stop BER Measurement button to stop the test.
9 Click the Change to Normal Mode button to return the station to normal
operation.
Procedure 2-38 explains how to measure the receive signal strength indicator (RSSI) for the station.
Procedure 2-38 How to Measure the RSSI
4 Click OK.
Result: The station begins a reset sequence to change modes, which takes a
few seconds. After resetting, you must read the configuration data again from
the base radio and then open the Test and Measurement Screen dialog box as
described in step 1.
5 Select Project 25 from the Pattern Type field.
6 Enter the number of seconds you want from the Sampling Period (sec) list box.
This field allows you to select the length of time before the report is updated.
The circuit devices responsible for determining the station reference frequency exhibit slight variations
in their operating characteristics over time. Approximately 90% of the aging process occurs during
the first year, whether the equipment is in service or in storage awaiting installation. Therefore, it
is necessary to calibrate the reference oscillator at the time of optimization.
The station configuration determines which reference oscillator procedure you need to perform.
Table 2-29 lists the three possible configuration.
Table 2-29 Station Configurations Matched to Calibration Procedures
2 Click the Change to Service Mode button to put the station into service mode.
Result: A confirmation dialog box appears (Figure 2-40).
3 Click OK.
Result: The station goes through a reset sequence to change modes, which
takes a few seconds. After resetting, you must read the configuration data from
the station again, and then access the Alignment Screen window, as described
in step 1.
4 Connect the service monitor with external frequency standard to the PA Output
on the station.
2 Click the Change to Service Mode button to put the station into service mode.
Result: A confirmation dialog box appears (Figure 2-42).
3 Click OK.
Result: The station goes through a reset sequence to change modes, which takes
a few seconds. After resetting, you must read the configuration data from the
station again and then access the Alignment Screen window as described in step 1.
Procedure 2-40 How to Calibrate an Internal Reference Oscillator Using AUTO-NET (Continued)
4 Click one of the following buttons:
• AUTO-NET 5 MHZ
• AUTO-NET 10 MHZ
Result: The status area of the window indicates the status of the calibration
process. When the process is complete, a dialog box appears stating that the
calibration process was successful.
5 Click OK to close the dialog box.
6 Click the Change to Normal Mode button to restore the station to normal
operations.
2 Click the Change to Service Mode button to put the station into service mode.
Result: A confirmation dialog box appears.
3 Click OK.
Result: The station goes through a reset sequence to change modes, which takes
a few seconds. After resetting, you must read the configuration data from the
station again and then access the Alignment Screen window as described in step 1.
Result: The status area of the window indicates the status of the calibration
process. When the process is complete, a dialog box appears stating that the
calibration process was successful.
6 Click OK to close the dialog box.
7 Remove the external reference source.
8 Click the Change to Normal Mode button to restore the station to normal
operations.
Calibrating a UHSO
Procedure 2-42 explains how to calibrate an ultra high stability oscillator (UHSO).
Procedure 2-42 How to Calibrate a UHSO
2 Click the Change to Service Mode button to put the station into service mode.
Result: A confirmation dialog box appears.
3 Click OK.
Result: The station goes through a reset sequence to change modes, which takes
a few seconds. After resetting, you must read the configuration data from the
station again and then access the Alignment Screen window as described in step 1.
4 Connect the service monitor with external frequency standard to the station.
Procedure 2-43 explains how to perform to calibrate the receive signal strength indicator (RSSI).
Procedure 2-43 How to Calibrate the RSSI
3 Click the Change to Service Mode button to put the station into service mode.
Result: A confirmation dialog box appears.
If you change the output level value in this step, make sure the screen
matches the signal generator.
6 Enter -90 in the Unmodulated RF Signal Input (dBm) field.
7 Click the Start RSSI Calibration button.
Result: As the station begins the calibration process, the button changes to Stop
RSSI Calibration. After calibration is completed the button returns to Start RSSI
Calibration.
You can stop the calibration process for clicking the Stop RSSI
Calibration button at any time.
8 Click the Change to Normal Mode button to restore the station to normal
operations.
Procedure 2-44 explains how to align the reference modulation compensation for the station.
Procedure 2-44 How to Align the Reference Modulation Compensation
8 Disconnect the service monitor and reconnect the cable to the PA Output.
9 Click the Change to Normal Mode button to return the station to normal
operation.
Procedure 2-45 explains how to align the power output for the station.
Procedure 2-45 How to Align the Power Output
4 Connect the service monitor to the station using the following steps:
1. Remove the N-Type connector from PA Output.
2. Connect the cable from the service monitor to PA Output.
5 Perform the power output alignment:
1. Click the Key On Freq1 button to key the station on the first frequency.
Result: The Current Frequency Is field displays the transmit frequency.
2. Set the service monitor to the frequency shown in the Current Frequency
Is field.
3. Read the deviation on the service monitor display, which is shown as two
numbers, one for positive (+) and one for negative (-) on the screen.
4. Enter the larger number into the Deviation (kHz) field for Frequency 1.
6 Repeat step 5 for Frequency 2, 3, and 4.
Procedure 2-46 explains how to align the transmit deviation for the station.
Procedure 2-46 How to Align the Transmit Deviation
4 Click OK.
Result: The station begins a reset sequence to change modes, which takes a few seconds.
After resetting, you must read the configuration data again from the base radio and then open the Alignment
Screen window as described in step 1.
If the power amplifier fails while adjusting the power out, click
the PA INIT button to reset the PA to its initial value and start
the alignment procedure again.
9 Disconnect the service monitor and reconnect the cable to the PA Output.
10 Click the Change to Normal Mode button to return the station to normal operation.
Procedure 2-47 explains how to check the receiver desensitivity for the station.
If a tower top amplifier is used, connect the ISC-T to the service port on the amplifier. If the tower
top amplifier does not have a service port, measure the receive desensitivity using this procedure.
Procedure 2-47 How to Check the Receiver Desensitivity
• Project 25
The Configuration/Service Software (CSS) contains metering windows that take measurements
without using an external service monitor. You can use the following procedures to
monitoring components of the IntelliSite Repeater:
• "Monitoring the Exciter and Power Amplifier" on page 2-131
• "Monitoring the Receiver Module" on page 2-132
• "Monitoring the Power Supply Module" on page 2-133
• "Monitoring the UHSO Module" on page 2-134
Procedure 2-48 explains how to monitor the exciter and power amplifier (PA) modules in the station.
Procedure 2-48 How to Monitor the Exciter and PA Modules
3 Click OK.
Result: The station begins a reset sequence to change modes, which takes a few
seconds. After resetting, you must read the configuration data again from the
base radio and then open the Metering Screen window as described in step 1.
4 Click the KEYUP button.
Result: The window displays performance information on the exciter and PA.
5 Click the DEKEY button to turn off the transmitter.
Procedure 2-49 explains how to monitor the receiver module in the station.
Procedure 2-49 How to Monitor the Receiver Module
3 Click the Close button in the right hand corner of window to close it.
Procedure 2-50 explains how to monitor the power supply module in the station.
Procedure 2-50 How to Monitor the Power Supply Module
3 Click the Close button in the right hand corner of window to close it.
Procedure 2-51 explains how to monitor the ultra high stability oscillator (UHSO) module in the station.
Procedure 2-51 How to Monitor the UHSO Module
3 Click the Close button in the right hand corner of window to close it.
Index