Reference
Top 20 Incidents
Reference KB0011985
How-To-Troubleshooting Procedures
Check a TRAK_ALARM
Trak 9100 Known Alarms
Check Trak 9100 events/alarms in UEM.
Image not available
When TRAK9100 fails, a field tech would have to check the status LEDs to verify if the issue is a hardware failure. FSU cards, Power Supplies, and GPS antennas are known to fail.
Determine NTP Servers
Use this table to determine what would be the NTP server address for different network devices we use:
Note that the selected name of the server needs to be converted into IP Address prior setting the value to device.
- Network Time Protocol (NTP) provides a clock synchronization mechanism to the RDMs and other NTP clients at the site. In a high-availability configuration, the NTP clients must use the TRAK 9100 Simulcast Site Reference (SSR), at the prime site, as the primary time source; and an ntp02.zoneNdevice at a zone core as the secondary time source. The RDMs at the site also act as an NTP time source. The base radios use RDM A as the primary NTP time source, and use RDM B as the secondary NTP time source.
- NTP provides a clock synchronization mechanism to the NTP clients at the site. All NTP clients use the TRAK 9100 SSR at the prime site (ntp01.site#.zone#) as the primary time source and the Virtual Management Server (ntp02.zone#) at the zone core as the secondary time source. This configuration applies even for subsites equipped with a TRAK SSR.
- NTP source “ntp02.zone#” resides on a Generic Application Server if the system deployment/release does not include Virtual Management Servers.
Network Device |
Non-DSR Primary NTP Source |
Non-DSR Backup NTP Source |
DSR Primary NTP Source |
DSR Backup NTP Source |
Conventional Site Controller |
ntp02.zone# |
ntp03.zone# |
ntp02.zone# |
ntp05.zone# |
Multi-Site Controller |
ntp01.site#.zone# |
ntp02.zone# |
ntp01.site#.zone# |
ntp02.zone# |
Repeater Site Controller |
ntp02.zone# |
ntp03.zone# |
ntp02.zone# |
ntp05.zone# |
HPD Site Controller |
N/A |
N/A |
N/A |
N/A |
RDM in IP Simulcast High Availability Subsite |
ntp01.site#.zone# |
ntp02.zone# |
ntp01.site#.zone# |
ntp02.zone# |
RDM in Trunked 3600 IntelliRepeater Site |
See Procedure |
See Procedure |
Does not support DSR |
Does not support DSR |
Conventional Base Radio |
ntp02.zone# |
ntp03.zone# |
ntp02.zone# |
ntp03.zone# |
Multisite Base Radio |
ntp01.site#.zone# |
ntp02.zone# |
ntp01.site#.zone# |
ntp02.zone# |
Repeater Site Base Radio |
sc1.site#.zone# |
sc2.site#.zone# |
sc1.site#.zone# |
sc2.site#.zone# |
Trunked 3600 Base Radio in a Simulcast Site |
ntp01.site#.zone# |
Does not support second NTP source |
Does not support DSR |
Does not support DSR |
Trunked 3600 Base Radio in IntelliRepeater Site |
sc1.site#.zone# |
sc2.site#.zone# |
Does not support DSR |
Does not support DSR |
HPD Base Radio 2. |
dsc1.site#.zone# |
dsc2.site#.zone# |
dsc1.site#.zone# |
dsc2.site#.zone# |
HPD Base Radio in Repeater Site 3. |
sc1.site#.zone# |
sc2.site#.zone# |
sc1.site#.zone# |
sc2.site#.zone# |
Trunked or Conventional Comparator |
ntp01.site#.zone# |
ntp02.zone# |
ntp01.site#.zone# |
ntp02.zone# |
SmartX Site Converter |
ntp02.zone# |
ntp03.zone# |
Does not support DSR |
Does not support DSR |
Telephone Media Gateway |
ntp02.zone# |
ntp03.zone# |
Does not support DSR |
Does not support DSR |
Vortex VPM |
ntp02.zone# |
ntp03.zone# |
ntp02.zone# |
ntp05.zone# |
Shutting OFF an RF Site/Bringing an RF site back into Wide Trunking
A Customer may call us requesting for temporary disabling of an RF site.
A typical example is Putting an RF site OFF for maintenance due to antenna replacement.
IMPORTANT: Only a specific list of people should have the ability to request a Site-OFF. Please refer to customer specific CSP or any similar document for permission validation
Shutting OFF an RF Site Procedure:
1. From the left pane, under “Network Database”, select “Site” and find the site name:
2. Look for the “Repeater Site” type of object. Locate the appropriate site, Right-click on it and
select “Issue Command”:
3. In the Command Window, select “Site” on the left, then “Site Off” and “Apply”:
Result: The site will go in Site-OFF Mode, which will stop any transmission.
Look for a positive message in the Status Bar.
Site equipments are still powered-on and accessible via network management applications. Site is OFF, no transmitter keyed and not accessible for subscriber traffic.
You can see the Site-OFF state in UEM and Zonewatch.
Restore the service when instructed to by proceeding with “Requesting a Wide-Trunking state from UEM”.
Bringing an RF site back into Wide Trunking:
1. Follow the steps 1 and 2 from the "Shutting OFF an RF Site" procedure.
2. In the Command Window, select “Site” on the left, then “Wide Trunking” and “Apply”:
Result: The site will go in Wide trunking Mode, which will restore trunking operation including an Active Control Channel.
Look for a positive message in the Status Bar
Site is Wide Trunking, a control channel is on-air and the site is accessible for subscriber traffic.