1 / 9

Troubleshooting 101 Something is not working, where problems could be….

Troubleshooting 101 Something is not working, where problems could be…. Infrastructure, “Tower Sites, Consoles, Servers, Connectivity ”. Subscriber Equipment, “Tuning, Broken” Programming, “System, Console, Radio” External, “Coverage, Buildings, RF Noise”

odelia
Download Presentation

Troubleshooting 101 Something is not working, where problems could be….

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Troubleshooting 101 • Something is not working, where problems could be…. Infrastructure, “Tower Sites, Consoles, Servers, Connectivity”. Subscriber Equipment, “Tuning, Broken” Programming, “System, Console, Radio” External, “Coverage, Buildings, RF Noise” Situation, “Portable on Site 1, Mobile on Site 2, etc.” User Training

  2. Scope of the issue • Is it bad audio, missing audio, wrong audio? • Is it scanning, or involve the selected talkgroup. • Is the problem specific to a geographic area? • Is it specific to an agency, or everyone in the area? • Is it specific talkgroup(s)? • Is it intermittent? • Is it involve a zone or multiple zones? “regions” • Is it subscriber - subscriber, or console – subscriber? • Is there a difference between Talk-In and Talk-Out.

  3. What Changed ?? • If something used to work, and now it doesn’t, something changed. • Is / was there any changes just done with the equipment involved? • ARMER-Sys-Notify distribution list. • The SysTech talkgroup(s). • Any programming changes?

  4. Intermittent Events • Subscriber activity data is kept in an ATIA log in the system, but additional information is needed to identify the event in the data, the Motorola captured ATIA data is kept for 30 days. • Description of what the issue is. • Date and Time, accuracy is important. • Radio Alias(s) or ID(s) involved. • Talkgroup Alias(s) or ID(s) involved • Location

  5. Resources • ARMER-Sys-Notify & Admin Distribution lists. • SysTechTalkgroupsfor support personnel. • Radio Operations Center for State issues. 651-234-7950 • Motorola Case Ticket Process. • Service Shops. • Other agencies on ARMER. • PRNM Applications. • Monthly Reports. • Software distribution share at \\10.111.111.111

  6. Whose Issue is it ?? • Agencies are responsible for equipment they own, and how it’s configured. “Radios, Consoles, Towers, Microwave etc.” • Issues that fall under MnDOT’s responsibility…. Security Access to Resources, “Consoles, Buttons, Admin”. Active Directory Domain accounts, “Admin, Dispatch, Service”. Items involving Voyance / UNC. Network configuration “Routers, Switches, Firewalls” Software & Config Files in the distribution share. Equipment owned by MnDOT.

  7. Problems we typically see • Radios that haven’t been Tuned lately, or ever. • Radios programmed to prefer a site, instead of least preferred. • Issues with new software & equipment. • Radios not programmed with CQPSK modulation. • Intermittent T1 issues in early mornings on humid summer days. • Tower site in site trunking, due to either maintenance or unplanned. • In Building coverage. • Doing operations by scanning talkgroups. • Console issues.

  8. Memorable Examples • Our Radios work terribly in this area…. • Can’t login to a Dispatch Computer…. • My Radio won’t affiliate to that site…. • You have a system repeating repeating audio problem….

More Related