astro 25 7.14 release notes - semnrrb.comsemnrrb.com/documents/motorola/7.14 customer release notes...

ASTRO 25 7.14 Release Notes

. . . . . . . . . .

ASTRO® 25 7.14 Release Notes

14-Nov-13

© Copyright 2013 Motorola Solutions, Inc. US

1


Contents System Level Information ................................................................................................................. 3 Centralized System Logging ............................................................................................................. 8 Configuration / Service Software (CSS) ........................................................................................... 8 FSA4000 Fire Station Alerting ........................................................................................................... 8 GCM 8000 Comparator ...................................................................................................................... 9 GCP 8000 Site Controller (SC) .......................................................................................................... 9 GTR 8000 Base Radio (BR) ............................................................................................................. 10 HP Switches ..................................................................................................................................... 11 InfoVista ............................................................................................................................................ 11 Install and Backup Services ............................................................................................................ 11 Intersystem Gateway (ISGW) .......................................................................................................... 12 Key Management Facility (KMF) ..................................................................................................... 12 MCC 7100 IP Console ...................................................................................................................... 13 MCC 7500 Dispatch Position Software .......................................................................................... 15 MCC 7500 IP Digital Logging Recorder .......................................................................................... 18 MKM 7000 Console Alias Manager (CAM) ...................................................................................... 18 MLC 8000 Comparator ..................................................................................................................... 18 MZC 5000 Zone Controller (ZC) ...................................................................................................... 20 Provisioning Manager (PM) ............................................................................................................. 20 Routers and Gateways .................................................................................................................... 21 System Traffic Monitor Applications .............................................................................................. 23 Unified Network Configurator (UNC) .............................................................................................. 24 Virtual Management Server (VMS) .................................................................................................. 25

2


System Level Information

New Features RN_CCMPD-00002208 Abstract: Enhanced Data System Platforms Affected: ASTRO 25 7.14 Special Configurations: Enhanced Data functionality is provided on APX subscriber radios only. Description: Enhanced Data increases inbound data efficiency without requiring the user to add new hardware to an ASTRO 25 system that is enabled for Integrated Data. This feature provides the following capabilities: • Support for 150 data users per channel at a 30-second cadence • Dynamically-assigned channels (by site) • Option to protect data channel pre-emption from voice at a site or system • Capability for agencies to share Enhanced Data channels

RN_CCMPD-00002209 Abstract: Geographically Redundant Prime Site System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: The Geographically Redundant Prime Sites feature splits the current prime site into two redundant and geographically separate IP simulcast prime sites connected by extended LAN links. This allows simulcast subsystems to maintain wide area simulcast trunking operation with wireline dispatch, even after a catastrophic prime site failure (for example, if one prime site is destroyed by a natural disaster or act of terrorism).

RN_CCMPD-00002210 Abstract: Dynamic System Resilience (DSR) Enhancements System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: The existing DSR feature provides continuity of operations in case of disaster, ensuring that communication between end users is maintained if the primary master site experiences a catastrophic event. DSR supports redundancy for voice, system management, integrated data, High Performance Data (HPD) and information assurance services. If remote sites cannot connect with their currently active core, the sites switch to their standby core. The ASTRO 25 7.14 system release introduces the following enhancements: • DSR can now be implemented on an M1 system core. • DSR can now be implemented on a zone-by zone basis in multizone systems.

RN_CCMPD-00002211 Abstract: Site Selectable Alerts for Trunking System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: This feature enables users to pre-configure alerts for affiliated subscribers at selected sites. The alerts are generated as either voice announcements or tones and are displayed on appropriately equipped subscriber radios. Site Selectable Alerts command the attention of radio users, regardless of what activity they are currently performing, so the radio users can mass notify and evacuate a site in the event of an emergency.

RN_CCMPD-00002212 Abstract: Inter SubSystem Interface (ISSI) and Console Subsystem (CSSI) on M1 Core System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to systems with M1 zone core configurations. Description: ISSI 8000 and CSSI 8000 are now available for M1 core configurations. ISSI 8000 is an interoperability solution, based on Association of Public Safety Communication Officials (APCO) Project 25 (P25) standards, that enables users to connect to other P25 systems regardless of their RF bands, manufacturer types, and release versions.

3

ASTRO 25 7.14 Release Notes CSSI 8000 is an interoperability solution, based on Telecommunication Industry Association 102-BACA standards, that enables users to connect a third-party P25-capable console to an ASTRO 25 system. The features provided by ISSI 8000 and CSSI 8000 include: • Group call, emergency call, and individual call • Console priority • Console takeover • Display of transmission source type • Support for acoustic cross mute • Notification when console is receiving duplicate audio

RN_CCMPD-00002213 Abstract: High Availability Simulcast Time and Frequency Reference Extended Holdover System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to simulcast systems. Description: The High Availability Simulcast Time and Frequency feature was introduced for simulcast systems in the ASTRO 25 7.9 system release. It provides a redundant time and frequency solution at remote RF sites, as well as a holdover window that enables simulcast operation to remain available for four hours after Global Positioning System (GPS) signals are lost. The Extended Holdover solution introduced in the ASTRO 25 7.14 release provides the option to add a TRAK 9100 or TRAK 8835-3M unit at a high availability remote simulcast RF site to extend the holdover to 72 hours. The extended holdover provides time for maintenance personnel to reach a site and address any issues before functionality is impacted.

RN_CCMPD-00002214 Abstract: Conventional IP to Circuit Link Converter System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to systems that contain some CENTRACOM Gold Elite or MCC 5500 dispatch consoles. Description: The GGM 8000 gateway now supports IP Link Converter (IPLC) functionality, which enables the GGM 8000 to interface a GCM 8000 IP comparator to a digital interface unit (DIU). This feature allows users with fielded CENTRACOM Gold Elite and MCC 5500 consoles to replace or expand their simulcast or voting channels with solutions using GCM 8000 comparators, GCP site controllers, GTR 8000 base radios, and related products. As a result, users can replace circuit connectivity with IP connectivity and can transition legacy digital or mixed-mode RF channels to "G series" RF channels. This enables users to begin system migration at the RF channel level and upgrade consoles at a later date. Users can also retain existing circuit backhaul networks (T1s/E1s). In addition to leveraging the IP transport capabilities of the GGM 8000 to position users to migrate to ASTRO 25 IP-based systems, the IPLC feature leverages the following conventional channel gateway (CCGW) functionality supported on the GGM 8000: • V.24/AIS (ASTRO infrastructure signaling) protocols plus four-wire interface to the DIU • AIS/XIS (X-Zone infrastructure signaling) conversion • Support for IP and IP/XIS transport • Conversion from four-wire analog to G.728 packets to transport audio over IP • Support for IP and analog comparators in a mixed mode configuration • Integrated voice and data (IV&D) to support AIS/XIS data applications

RN_CCMPD-00002215 Abstract: MCC 7100 Instant Recall Recording (IRR) System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to systems that contain MCC 7100 IP dispatch consoles. Description: This feature provides the user with instant access to recently recorded conversations, which is consistent with the functionality provided by the MCC 7500 dispatch console solution. The feature is implemented by storing audio on the hard drive of the computer on which the MCC 7100 IP console software resides. MCC 7100 IRR provides the following functionality: • Transmit (TX) and receive (RX) recording with the capability for dispatchers to replay to their own words. • Configurable audio storage on the hard drive (up to 4 GB) • Instant record retrieval

4

ASTRO 25 7.14 Release Notes • Variable speed replay • Automatic purging of aging audio records • IRR Control graphical user interface that can be added, removed, and configured by the user

RN_CCMPD-00002216 Abstract: Audio Interface Module (AIM) for MCC 7100 IP Console System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to systems that contain MCC 7100 IP dispatch consoles. Description: AIM is a peripheral hub that enables users to connect the Motorola microphone footswitch and headset jack to the computer on which the MCC 7100 IP console software resides, enabling that computer to support the same Motorola accessories as the MCC 7500 dispatch console. These accessories include: • An external phone interface that allows the user to manage telephone and radio conversations on a single headset • Local auxiliary inputs and outputs (AUX I/Os) • A second supervisor headset • An external paging encoder

RN_CCMPD-00002217 Abstract: Trunked GPW 8000 Receiver System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: The trunked GPW 8000 receiver integrates a receive-only base radio into ASTRO 25 7.14 trunked systems that support simulcast and single transmitter/multiple receiver voting operation. It expands talk-in coverage area by providing additional receive-only stations in areas where it would otherwise be difficult to receive a signal from a portable or mobile subscriber. The dual-slot chassis of the GPW 8000 trunked receiver optimizes space efficiency by accommodating two receive-only modules in a single three-rack unit (3RU) chassis. The GPW 8000 trunked receiver also supports Time Division Multiple Access (TDMA) audio on dual receive-only modules, which allows users to increase their frequency capacity by almost four times on a single hardware base module without adding more frequencies.

RN_CCMPD-00002218 Abstract: Conventional GPW 8000 Receiver Enhancements System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: The conventional GPW 8000 receiver has been enhanced with a dual-slot chassis to optimize space efficiency by accommodating two receive-only modules in a single three-rack unit (3RU) chassis. In previous releases, conventional GPW 8000 receivers supported only one receiver module in the 3RU chassis.

RN_CCMPD-00002219 Abstract: Emergency Calls Handled as Normal Push-to-Talk (PTT) Calls System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: Dispatchers can simplify their environment with this feature, which enables dispatch positions to be configured to suppress emergency indications from talkgroups or conventional channels that are of lower priority. The dispatcher observes the following changes for the talkgroups or channels for which this feature is implemented: • For emergency calls, the console displays the PTT ID of the radio and plays the radio’s audio in the speaker or headset, but the console does not generate any visual or audible emergency indications. • For emergency alarms, the dispatch position does not display any PTT IDs or provide any visual or audible indications.

RN_CCMPD-00002220 Abstract: Enhanced Select Interaction with Patch System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: Patch operation on the MCC 7100 IP console and the MCC 7500 dispatch console has been enhanced to allow users to configure the console to automatically open a Multi-Select (MSEL) group on top of a patch group when the dispatcher sets up the patch. This capability allows the audio from the patch group to remain in the dispatcher’s headset or select speaker.

5

ASTRO 25 7.14 Release Notes This feature addresses the following issues: • When an emergency occurs on an unselected talkgroup that is part of a patch on the console, the audio from that talkgroup no longer moves from the dispatcher’s headset or select speaker to the unselect speaker. • When a dispatcher wants to hear all members of a patch group in the headset or select speaker, the dispatcher is no longer required to manually open an MSEL group that mirrors the patch group.

RN_CCMPD-00002221 Abstract: Enhanced Alert Tones System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to systems that contain MCC 7100 IP dispatch consoles. Description: Dispatchers can now access up to 15 customizable alert tones on the MCC 7100 IP console or the MCC 7500 dispatch console. This capability allows different dispatch centers (or different dispatchers within a single dispatch center) to use different sets of alert tones. The flexibility to support unique alerting needs is useful both in large regional or statewide systems shared by many agencies and in single-agency systems shared by many dispatchers.

RN_CCMPD-00002222 Abstract: 150 Trunked RF Sites for M3 Zone Cores System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to systems with M3 zone core configurations. Description: M3 zone cores now support up to 150 trunked RF sites. In previous releases, M3 zone cores supported only 100 trunked RF sites.

RN_CCMPD-00002223 Abstract: Provisioning Manager Auditing System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: The Provisioning Manager now enables stricter enforcement of system policies by providing audits that include information about the objects that are managed and configured in the Provisioning Manager application. The audit information includes: • What operation was performed on the object (create, modify, or delete) • When the operation was performed on the object • Who performed the operation on the object • The type of object on which the operation was performed • The record ID corresponding to the object Operators can use the audit information to troubleshoot issues that may arise when subscriber capabilities are configured incorrectly in subscriber profiles.

RN_CCMPD-00002224 Abstract: Hybrid Site Links System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: This feature provides a flexible method for connecting a redundant zone core to redundant remote sites in an ASTRO 25 system. In previous releases, primary and redundant site links had to be the same connection type: either T1/E1 or Ethernet. With the implementation of Hybrid Site Links, connection types can now be mixed: If the primary link is a T1/E1 link, the redundant link can be an Ethernet link, and vice versa. This flexibility increases availability and is useful during site transitions.

RN_CCMPD-00002225 Abstract: Lifecycle Upgrade Automation System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A Description: The ASTRO 25 7.14 system release introduces upgrade automation to maximize the value of an ASTRO 25 system during its lifecycle. Lifecycle Upgrade Automation: • Reduces the duration of most upgrades

6

ASTRO 25 7.14 Release Notes • Simplifies the upgrade process • Leverages modern IT technology and tools • Facilitates regular upgrades to ensure access to the latest capabilities and features introduced with each ASTRO 25 system release after the release that was first installed

RN_CCMPD-00002226 Abstract: Support for System Upgrades from ASTRO 25 7.11 or ASTRO 25 7.13 System Platforms Affected: ASTRO 25 7.14 Special Configurations: This feature applies to ASTRO 25 systems operating on System Release 7.11 or 7.13. Description: The ASTRO 25 7.14 system release supports upgrades from the ASTRO 25 7.11 or ASTRO 25 7.13 system releases. As part of this system upgrade support, users can purchase System Upgrade Agreement (SUA) and SUA II lifecycle subscriptions. These subscriptions cover the implementation costs associated with a system upgrade and provide complete upgrade coverage, including Motorola release software, third-party software and security updates, and certified hardware.

RN_CCMPD-00002490 Abstract: Carrier Operated Relay (COR) capability and Channel Active indication (CAI) for MLC 8000 Comparator System Platforms Affected: ASTRO 25 7.14 Special Configurations: Certified for MCC 7500 Dispatch Console and MCC 7100 IP Console via Conventional Channel Gateway (CCGW) link, Centracom Gold Elite consoles, and MC2500 consoles only Description: COR functionality (known as CAI) has been added to the MLC 8000 comparator to enable an alternative solution for the console to detect inbound audio from the comparator in addition to the VOX (Voice on transmit) capability that it currently provides. Please note that external hardware from a third party is required to implement this functionality.

Issue Updates RN_CCMPD-00001823 Abstract: Consoles may not accept deletion of channel and creation of new channel with different channel type but same channel ID. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue only applies to systems with conventional channels User Symptoms: When a user deletes a digital, mixed mode, or ASTRO Console Interface Module (ACIM) channel, replaces that channel with an analog channel, and the user does not distribute the deletion before adding the new channel, some console capabilities (for example, emergency calls) do not work for the new analog channel. However, when a user replaces an analog channel with a digital, mixed mode, or ACIM channel, the console accepts the channel change successfully. Description: Consoles now accept deletion of a channel and creation of a new channel with a different channel type but the same channel ID.

RN_CCMPD-00001846 Abstract: GTR 8000 Base Radio (BR) may not transmit after recovery from failure of integrated references. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: This issue affects GTR 8000 and GTR 8000 High Performance Data (HPD) BRs configured for Integrated Reference. User Symptoms: A status LED on the BR may indicate that the BR is not transmitting, and the power metering screen in Configuration/Service Software (CSS) may show that the forward power level is zero. When this occurs, both references are failed and need to be recovered. In addition, users may observe the following symptoms: • If the BR is on a control channel, subscribers may report out of range after roaming to a site. • If the BR is on a voice channel, calls may be assigned to the BR, but the radio on the assigned call may not synchronize with the BR and may bounce back and forth between voice channel and control channel for the duration of the call. When this issue occurs, inbound audio on the affected channel is still sent to the infrastructure properly. The original reference failures and recoveries are reported to the Unified Event Manager (UEM), but after the BR stops transmitting, the UEM receives no notifications that the BR is not transmitting. This issue occurs only if reference failure and recovery occurs in a particular order (AB-BA or BA-AB). Description: The BR now transmits as expected after recovering from failures of integrated references.

7


Centralized System Logging

Known Problem RN_CCMPD-00002422 Abstract: Extraneous words are interspersed between valid syslog client host names in Syslog Client list on Centralized Event Logging server. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user requests a list of syslog clients from the Centralized Event Logging server, using the “Application Administration->Application Specific Management and Operations->View Syslog Clients” menu path, the resulting list contains the host names from which syslog messages are successfully received. However, the list also contains extra words that are not host names. Functionality is not impaired, but the presence of the extra words in the list may be confusing to the user. Work Around: None. The user should ignore any words in the list that are not valid host names.

Configuration / Service Software (CSS)

Known Problems RN_CCMPD-00002461 Abstract: Rarely, CSS may freeze during exit. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: Rarely, during an exit operation, the CSS application may become unresponsive while creating a zip archive of its internal log file. When this occurs, no data is lost, but the unresponsiveness of the application may be confusing to the user. Work Around: None. To recover, the user should open the Windows Task Manager and perform an "End Task" operation on the CSS application.

RN_CCMPD-00002503 Abstract: Software Download (SWDL) installation may fail. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects multisite system configurations that contain more than 150 base radios. User Symptoms: When a user attempts a multi-channel installation for more than 150 devices at the same time, the SWDL installation may fail. When this issue occurs, the SWDL application stops performing operations on the sites where the devices reside for an extended period of time, and the following message appears in the Message Box: "Transaction failed. Vlan API failed". Work Around: None. To avoid this problem, users should set the "Simultaneous Channel Install" option in the SWDL Manager in such a way that the number of subsites in a site multiplied by the number in the "Simultaneous Channel Install" parameter does not exceed 150.

FSA4000 Fire Station Alerting

Known Problem RN_CCMPD-00001849 Abstract: FSA4000 Dispatch Application may send some alerts to location not intended by user. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue affects systems configured with eight (8) possible sequences for dispatching alerts to fire stations. User Symptoms: When a user selects eight sequences for dispatching alerts to fire stations, the FSA Disptach Application may display both sequence 8 and the previously selected default sequence as being selected for dispatching. When this occurs, alerts are sent to the selected station on the default sequence, rather than to sequence 8.

8

ASTRO 25 7.14 Release Notes Work Around: None. • To prevent this issue, users should not use eight sequences for dispatching. • To recover, users should unselect sequence 8 if it is selected.

GCM 8000 Comparator

Known Problem RN_CCMPD-00002493 Abstract: Subscribers may not hear console audio after comparator reset during V.52 test. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects conventional IP simulcast systems. User Symptoms: When a user starts a V.52 test on a given channel but does not properly stop the test (because the comparator resets and interrupts the test), subscribers may not hear audio originated by dispatch consoles on that channel. When this occurs, the Unified Event Manager (UEM) and other network management (NM) servers report the state of the comparator as "Enabled", as if the comparator were fully operational, when in fact the comparator is inactive. When the user verifies the state of the comparator using Configuration/Service Software (CSS), the "Local Status Screen" in CSS displays the state of the comparator correctly. Work Around: None. To recover, the user should manually take the comparator out of V.52 test mode using the "Stop V.52 Test Pattern" button on the "Local Status Screen" in CSS.

GCP 8000 Site Controller (SC)

Known Problems RN_CCMPD-00002426 Abstract: Status Panel screen in Configuration/Service Software (CSS) may not refresh display when SC goes to standby status. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When an SC changes its status from active to standby, the SC resets as expected. However, if the Status Panel screen in CSS is open during the reset, the screen may continue to display field values that were retrieved when the SC was active, instead of replacing those values with "N/A" as expected when an SC is on standby. The screen correctly displays the standby status of the SC, but the display of values in other fields that are not applicable to a standby SC may be confusing to the user. Work Around: None. To recover, close and reopen the Status Panel screen in CSS after the reset.

RN_CCMPD-00002437 Abstract: Site enters failsoft during field replacement of SC. System Platforms Affected: ASTRO 25 7.5, ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user performs the Field Replaceable Unit (FRU) procedure for an SC, the site where the SC is located enters site failsoft for approximately seven (7) minutes during the procedure. Work Around: To avoid this probllem when replacing an SC at a simulcast prime site, users should refer to the “Replacing the GCP 8000 Site Controller Module” procedure in the “GCP 8000 Site Controller” manual. When performing the procedure, users should skip step 14 (“Reconnect all the cabling to correct ports as previously labeled”) and instead proceed to step 17 (“Set the IP Address and the Box Number for the new device”). After the user assigns an IP address and device number to the SC, it is safe to reconnect all cabling. This workaround ensures that each SC has a unique device number assigned before network communication is restored between units. No workaround is available for FRU replacement of an SC in a GTR 8000 Expandable Site Subsystem (ESS).

9

ASTRO 25 7.14 Release Notes To recover a site from failsoft, users must follow the entire FRU procedure as described in the “GCP 8000 Site Controller” manual. Wide area trunking is restored after execution of step 29 (“Reload the configuration into the replacement site controller module”). After completing the procedure, users must ensure that both SCs are in enabled state. If either SC is in critical malfunction state, users should reset the SC to return it to enabled state.

RN_CCMPD-00002492 Abstract: Channel faults may be reported inconsistently during reset of active SC. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a channel fault occurs during a reset of an active SC, the fault may be reported inconsistently between devices in the ASTRO 25 system. For example: • The ZoneWatch (ZW) application may report the state of the channel as "Enabled" (displayed in green in ZW). • The Unified Event Manager (UEM) may report the state of the same channel as "Entity has been removed". • The Zone Controller (ZC) and Configuration/Service Software (CSS) may report the same channel as present and in some non-enabled state (for example, "Faulted" or "User Disabled". In addition, a channel that ZW reports as "Enabled" may not be assigned to any calls. When this issue occurs, users can determine the actual state of a channel element by doing any of the following: • Viewing the fault state reported directly by the channel in the UEM. • Viewing the fault state reported for the channel by the ZC in the UEM. • Connecting to the active SC using CSS. Work Around: None. To recover, users should perform a full synchronization of the active SC, using the "Synchronizing Network Elements" procedure in the "Unified Event Manager" manual.

GTR 8000 Base Radio (BR)

Issue Update RN_CCMPD-00001829 Abstract: BR may continue to report transmitter (Tx) fault after fault clears. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a BR fault shuts down the transmitter, and a user performs "Tx Inhibit" and "Tx Uninhibit" operations to clear the fault, the fault clears as expected, and the BR can transmit, but the BR continues to report transmitter failure. Functionality is not impaired, but the incorrect fault report may be misleading to the user. "Tx Inhibit" and "Tx Uninhibit" operations can be performed in the following ways: • Through network management interfaces, including Configuration/Service Software (CSS) and Motorola Supervisory Control And Data acquisition (MOSCAD) Network Fault Management (NFM). • Through a short press of the service port button on the front panel of the BR. In addition, "Tx Inhibit" and "Tx Uninhibit" can occur automatically on a conventional BR configured through WildCard. Description: The BR no longer reports a Tx fault after the fault clears.

Known Problem RN_CCMPD-00002450 Abstract: Rarely, BR may experience second reset during initialization. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: Rarely, during BR initialization, users may observe an extended startup time, and the BR may reset a second time before becoming operational. When fully initialized, the BR operates normally. When this issue occurs, no additional failures are reported to the Unified Event Manager (UEM). Work Around: None.

10


HP Switches

Issue Update RN_CCMPD-00001832 Abstract: HP 3800 switch cannot be rebooted or reloaded after operating system (OS) download from console menu interface. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When the user downloads OS software to the HP 3800 switch using the "copy" command from the console menu interface, the download is successful, but later attempts to reboot or reload the switch result in error messages. • When attempting to reboot the switch, the user sees the following message: “Cannot reload right now, the image file is currently being updated” • When attempting to reload the switch, the user sees the following message: “Download is in progress, you cannot reboot now!” Description: The HP 3800 switch can now be successfully rebooted or reloaded after an OS download from the console menu interface. NOTE: The console menu interface no longer provides a progress bar for the software download operation. As a result, the operation may not appear to be executing; however, the transfer eventually completes, and the operator is notified of the completion.

InfoVista

Issue Update RN_CCMPD-00002085 Abstract: InfoVista server reports "Communication Failure" in Unified Event Manager (UEM). System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: If the InfoVista server is restarted more than once after initial installation and configuration, the UEM reports "Communication Failure" for the server after the second and all subsequent restarts. This occurs because of incorrect entries in the configuration files for the server. Description: The InfoVista server no longer reports "Communication Failure" in the UEM if the InfoVista server is restarted more than once after initial installation and configuration.

Install and Backup Services

Issue Update RN_CCMPD-00002084 Abstract: Backup And Restore (BAR) Server displays misleading error message. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user performs a database restoration from CD-ROM or DVD-ROM discs on the BAR Server, the following message appears: "find: /media/cdrom0: No such file or directory". This occurs because ISO files from the "/export/ftp" directory are used for the restore operation. The restoration completes successfully, but the erroneous message may be confusing to the user. Description: The BAR Server no longer displays a misleading error message during database restoration.

11


Intersystem Gateway (ISGW)

Issue Update RN_CCMPD-00001855 Abstract: Intersystem Gateway (ISGW) may fail to reboot during Service Automation installation or upon operating system reboot. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue affects systems equipped for the Inter SubSystem Interface (ISSI) 8000 and Console Subsystem Interface (CSSI) 8000 interoperability solutions. User Symptoms: During installation of Service Automation or after a user issues the "Reboot Server" command, the ISGW may not fully reboot. When this occurs, the user may observe any of the following symptoms: • Service Automation indicates a failure. • The user's Secure Shell protocol (SSH) session is not terminated. • The vSphere client console for the Virtual Management Server becomes unresponsive. Description: During installation of Service Automation or after a user issues the "Reboot Server" command, the ISGW now reboots correctly, and the user no longer observes the symptoms described in this note.

Key Management Facility (KMF)

Issue Updates RN_CCMPD-00002349 Abstract: KMF displays erroneous error message. System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user places the KMF CryptR encryption device into Key Variable Loader (KVL) programming mode, the KMF displays the following message: "An unexpected error has occurred: null". The programming operation completes successfully, but the erroneous error message displayed by the KMF may be confusing to the user. Description: When a user places the KMF CryptR encryption device into KVL programming mode, the programming operation completes successfully, and the KMF no longer displays the erroneous error message.

RN_CCMPD-00002402 Abstract: KMF Client may display outdated status information for System Currency and may stop receiving operation events. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When the network where the KMF operates operates slowly because of a high volume of traffic on the network, the following conditions may occur: • The KMF stops updating the System Currency status, and the KMF Client displays outdated and possibly incorrect status information for System Currency. • The KMF Client stops receiving operation events. These conditions occur because of a loss of synchronization of operating system times between the KMF Client and the KMF Server, but the user is not notified of the loss of synchronization and is not aware of the need for any corrective action. When users actively maintain the same operating system time on the KMF Client and the KMF Server, this issue does not occur. Description: When the network where the KMF operates slowly because of a high volume of traffic on the network, the Operation Events tab in the KMF Client now displays an informational event at startup to notify the user of the loss of synchronization of operating system time between the KMF Client and the KMF Server, so that the user can manually synchronize the operating system times.

12

ASTRO 25 7.14 Release Notes RN_CCMPD-00002403 Visibility: Customer Visible SR ID: CCMPD01815423 SR Severity: C-Minor Abstract: Request for encryption keys from KMF fails afer manual deletion of keys from subscriber radios. System Platforms Affected: ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: This issue affects ASTRO 3.1 Conventional IV&D systems. User Symptoms: When a subscriber radio requests encryption keys from the KMF after keys have been deleted locally, the processing of the Retry Opportunity (ROP) request fails, and no new keys are issued to the radio. Description: When a subscriber radio requests encryption keys from the KMF after keys have been deleted locally, the processing of the ROP request now completes successfully, and new keys are now issued to the radio.

Known Problem RN_CCMPD-00002460 Abstract: Rarely, KMF Client window may freeze. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: In rare instances, the KMF Client application window may become unresponsive until the user minimizes and then restores the window. KMF functionality is not impaired, but the freezing of the application window may be confusing to the user. Work Around: None. To recover, minimize and then restore the application window.

MCC 7100 IP Console

Issue Updates RN_CCMPD-00001836 Abstract: Rarely, CRYPTR Micro encryption module not detected after ejection and reinsertion with MCC 7100 dispatch console software running. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user ejects the CRYPTR Micro from a running MCC 7100 dispatch console and then reinserts the CRYPTR Micro into the console, on rare occasions the reinsertion is not detected. When this occurs, the “Device Connect” and “Device Disconnect” sounds that accompany insertion and removal of the CRYPTR Micro are not heard. In addition, no applications that use the CRYPTR Micro can communicate with it. • When the MCC 7100 console is run, secure calls fail. • The Console Status application reports the CRYPTR Micro as “Not Present”. • The CRYPTR Micro Management Application returns “None” for requests for software version information, and for all other operations, the following message appears: “Link Down Error. Crypto module is not present”. All non-secure functions of the MCC 7100 console remain operational while this condition persists. When this condition occurs, the "CRYPTR Micro SDIO Device" node remains present in the "Memory Technology" Folder of the Windows Device Manager after the CRYPTR Micro is ejected. Description: When the user follows the instructions in section 2.10.7.5 of the "MCC 7100 IP Dispatch Console Setup and User Guide" (6871023P62-A), the potential failure conditions described in the User Symptom no longer occur.

RN_CCMPD-00001837 Abstract: User action to acknowledge installation of driver for CRYPTR Micro encryption module is required during installation of MCC 7100 dispatch console software. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When installing software for the MCC 7100 dispatch console, the user sees a warning message indicating that the CRYPTR Micro driver is from an unknown publisher, and the user is prompted to allow or disallow the install.

13

ASTRO 25 7.14 Release Notes • If the user does not actively allow installation of the driver, the installation of the console software cannot continue. • The warning message prevents unattended installation of the console software. Description: When installing software for the MCC 7100 dispatch console, the user no longer sees a warning message about the CRYPTR Micro driver, and unattended installation of the console software is now allowed.

RN_CCMPD-00001838 Abstract: Upon startup, console software may not detect CRYPTR Micro encryption module. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue affects only specific laptop computers, which are listed in section 2.10.7.5 of the "MCC 7100 IP Dispatch Console Setup and User Guide" (6871023P62-A). User Symptoms: When a user inserts the CRYPTR Micro into a computer where the console software is installed before starting that computer, the computer may not detect the CRYPTR Micro upon startup. When this occurs, no applications that use the CRYPTR Micro can communicate with it. • When the console software is run, secure calls fail. • The Console Status application reports the CRYPTR Micro as “Not Present”. • The CRYPTR Micro Management Application returns “None” for requests for software version information, and for all other operations, the following message appears: “Link Down Error. Crypto module is not present”. All non-secure functions of the console software remain operational while this condition persists. When this condition occurs, the “CRYPTR Micro SDIO Device” node remains absent from the “Memory Technology” Folder of the Windows Device Manager, even when the CRYPTR Micro has been inserted before computer startup. Description: When a technician who is using the specific laptops that exhibit this behavior follows the instructions in the document named in Special Configurations, the potential failure conditions described in the User Symptom no longer occur.

Known Problems RN_CCMPD-00002433 Abstract: Elite Dispatch transmissions may fail, and receive audio may be missing in headsets. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: After initial installation of an MCC 7100 IP Console, the Universal Serial Bus (USB) Archiving Interface Module (AIM) may not initialize completely. When this occurs, transmissions in the Elite Dispatch application may fail, and the user may see the following error message: "Insufficient Audio Peripherals". In addition, receive audio may not be present in headsets connected to the USB AIM. Work Around: Perform the following procedure: 1. Power cycle the USB AIM. 2. Open the Peripheral Configuration Tool, selected the desired non-default profile, and verify that USB AIM peripherals are correctly mapped. 3. When the mappings are correct, save the profile again. After 30 to 60 seconds, USB AIM peripherals should be available for use with Elite Dispatch.

RN_CCMPD-00002438 Abstract: Extra “Audio Only” call records appear in Instant Recall Recorder (IRR) call list. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When recording a call on an MCC 7100 IP console that is located outside the ASTRO 25 Radio Network Interface (RNI), the IRR application may create an “Audio Only” call record in addition to the expected call record for each call being recorded. These extra call records are more likely to appear when the IRR is recording a parallel console call, especially if that parallel console is also located around the RNI. Console and IRR functionality are not impaired, but the extra call records may be confusing to the user. Work Around: None. However, the call list can be filtered to show only call records matching a certain criteria, such as "Unit ID" greater than zero.

14

ASTRO 25 7.14 Release Notes RN_CCMPD-00002463 Abstract: Elite Dispatch application restarts when Message Monitoring is enabled in Debug Viewer. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user enables Message Monitoring in the WinQuicc query (under embedded queries in the Debug Viewer), the Elite Dispatch application may restart spontaneously. Enablement of Message Monitoring is not necessary to the operation of the Elite Dispatch application. Work Around: To avoid this issue, users should not enable Message Montoring in the WinQuicc query in the Debug Viewer. To recover, users should disable Message Monitoring in the WinQuicc query in the Debug Viewer.

RN_CCMPD-00002499 Abstract: Peripheral Configuration Tool may become unresponsive. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user upgrades firmware on the universal serial bus (USB) Archiving Interface Module (AIM) using the Peripheral Configuration Tool in the MCC 7100 IP console, the tool may become unresponsive, and the user may be unable to close the tool window. This condition is more likely to occur while the Elite Dispatch application is running. Work Around: To avoid this condition, users should exit the Elite Dispatch application before upgrading the AIM. To recover, users should manually terminate the upgrade process using the Windows Task Manager and then restart the Peripheral Configuration Tool. If subsequent attempts to read the firmware version fail, users should disconnect the AIM, power cycle the AIM, and connect the AIM to another available USB port.

RN_CCMPD-00002500 Abstract: Instant Recall Recorder (IRR) may become stuck in initializing state. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user opens the IRR application while the Elite Dispatch application is closing, the IRR may become stuck in initializing state and may remain stuck after Elite Dispatch is fully closed. Work Around: To avoid encountering this problem, users should not open the IRR application while the Elite Dispatch application is closing. To recover, users should reopen the Elite Dispatch application and wait for IRR to initialize.

MCC 7500 Dispatch Position Software

Issue Updates RN_CCMPD-00001834 Abstract: MCC 7500 dispatch console truncates go-ahead tones on patched telephony resource. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue affects systems equipped for the Enhanced Console Telephony feature. User Symptoms: When a talkgroup and a telephony resource are patched together on an MCC 7500 dispatch console and the radio de-keys, a "go-ahead" tone (a quick series of beeps) is generated to the phone line to indicate that the phone user can begin speaking. When this issue occurs, the "go-ahead" tones are partially truncated, and the phone user hears only one or two beeps instead of the entire series. No other audio is impacted. Description: The MCC 7500 dispatch console no longer truncates go-ahead tones on a patched telephony resource.

RN_CCMPD-00001850 Abstract: Transfer indication on console telephony resource may persist after transfer of call from Public Switched Telephone Network (PSTN). System Platforms Affected: ASTRO 25 7.13

15

ASTRO 25 7.14 Release Notes Special Configurations: This issue affects systems equipped for the Console Telephony feature. User Symptoms: When a console operator inadvertently transfers a PSTN call to a number outside the system's dialing plan, the unattended transfer takes place as expected. However, the indication of a call needing a transfer may remain on the telephony resource until the operator selects the resource again or a new call comes in on that resource. • If the phone caller hangs up, the indication goes to idle. • If the call times out (after about three minutes), the indication goes to idle. • In all cases the phone call is torn down as expected. Console functionality is not impaired, but the persisting indicator may be confusing to the user. Description: The transfer indication on a console telephony resource no longer persists after transfer of a call from the PSTN.

Known Problems RN_CCMPD-00002439 Abstract: Dispatch consoles may lose audio from some subscriber calls after takeover. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/.A User Symptoms: Dispatch consoles may lose audio from some subscriber calls after a takeover. This may occur in the following scenario: 1. One operator position (Console 1) has Talkgroups 1 and 2 in a patch group. 2. A parallel operator position (Console 2) has the same Talkgroups 1 and 2 in an open Multi-Select (MSEL) group. 3. When Talkgroup 1 receives an incoming subscriber call, the Console 1 audio patch is transmitted on Talkgroup 2. 4. When Console 2 receives two audio streams from the same source (one directly from the subscriber and another from the Console 1 audio patch transmitting on Talkgroup 2), Console 2 stops transmitting subscriber audio on Talkgroup 1. 5. When Console 1 performs a takeover of the audio patch call by keying Talkgroup 2 with "General Transmit", Console 1 cannot hear the subscriber call during and after the takeover on Talkgroup 1. Work Around: There are two workarounds for this issue: • Remove Talkgroup 1 with subscriber audio from the MSEL group and then add Talkgroup 1 again. • Change the volume on Talkgroup 1.

RN_CCMPD-00002440 Abstract: Archiving Interface Server (AIS) logs duration of secure Voice Selective Call (VSC) recordings incorrectly. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a secure VSC is made on a system where the MCC 7500 IP Logging is registered for "control ONLY" messages (no encryption), the AIS logs the duration of the VSC as 15 seconds, regardless of the actual duration of the VSC. No audio loss occurs, but the erroneous duration records may be confusing to the user. Work Around: None.

RN_CCMPD-00002441 Abstract: “Broken Link” Icon is not displayed for telephony resource in Multi-Select (MSEL) linked patch group. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a telephony resource is added to an MSEL linked patch group, no "Broken Link" icon is displayed to notify the user that the resource is not added to the MSEL group. The resource should not be added to the MSEL group, but the lack of notification may be confusing to the user. Work Around: None.

RN_CCMPD-00002442 Abstract: Audio for general transmit may be routed incorrectly during "alert tone talk extend". System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A

16

ASTRO 25 7.14 Release Notes User Symptoms: When a user performs a general transmit on a channel in a Multi-Select (MSEL) group while the "alert tone talk extend" option is active, the audio for parallel consoles with that channel selected may be routed to all speakers and headsets, instead of being routed only to select speakers or headsets as expected. This issue occurs when an MSEL group, set up with Channel 1 as its first member, is opened; an alert tone is transmitted then released using Channel 1; and a general transmit on Channel 1 is performed during the configured "talk extend" time of the alert tone. This issue is less likely to occur when the user reduces the "talk extend time" of the alert tone. Work Around: None.

RN_CCMPD-00002462 Abstract: Dispatch console may display acknowledgements of emergency calls inconsistently. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user sets the folder resource size in the Elite Dispatch application to a value greater than the default value of 1, the dispatch console may display acknowledgments of emergency calls inconsistently. For example, when an emergency call is received and acknowledged, and then another emergency call is received an acknowledged, the call stack in the dispatch console may display the green check mark symbol (indicating acknowledgment) for only the first of the two calls. When the folder resource size in Elite Dispatch is set to 1, this issue does not occur. Emergency call functionality is not impaired, but the inconsistent display of acknowledgments may be confusing to the user. Work Around: None. To recover, users should set the "Resource Size" value to 1 in Elite Dispatch by selecting "x1" from the dropdown list for the "Size" setting on the "Edit Folder Resources" screen.

RN_CCMPD-00002489 Abstract: After takeover of Multi-Select (MSEL) group or patch group, channel may transmit at wrong priority. System Platforms Affected: ASTRO 25 7.14 Special Configurations: This issue affects patch channels in an open MSEL group on a patching console. User Symptoms: When the dispatcher at a patching console performs a "general transmit" operation on an open MSEL or patch group, and subsequently one of the transmitting channels is taken over by an "instant transmit" operation on a different console and then dekeyed, the affected channel is rekeyed at "patch transmit" priority rather than at "general transmit" priority as expected. When this occurs, the affected channel is subject to takeover by a "general transmit" operation on a parallel console until the patching consoles finishes its transmissions on that channel. Work Around: None.

RN_CCMPD-00002501 Abstract: Changes to push-to-talk (PTT) configuration for speakers may not take effect after first restart of Elite Dispatch. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user changes the "Mute on PTT" setting for a speaker on the dispatch console, using the Provisioning Manager (PM) application, the changes may not take effect after the user restarts the Elite Dispatch application. However, when the user restarts Elite Dispatch again, the changes take effect as expected. Work Around: None. To recover, users should restart Elite Dispatch twice to apply the configuration changes.

RN_CCMPD-00002507 Abstract: Private call audio from subscriber to console operator is routed to unselect speaker. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a subscriber initiates a private call to a console operator on an unselected resource, private call audio from that subscriber is routed to the unselect speaker under the following conditions: • The operator responds to the call before selecting the resource. • The operator subsequently selects the resource and then keys again. All subsequent private call audio from the subscriber is routed to the select speaker as expected.

17

ASTRO 25 7.14 Release Notes Work Around: None. To avoid this problem, console operators should select a resource before responding to a private call from a subscriber.

MCC 7500 IP Digital Logging Recorder

Known Problem RN_CCMPD-00002427 Abstract: Scroll bar in Archiving Interface Server (AIS) Administrator application may not move smoothly. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: On the Resources tab of the AIS Administrator application, the vertical scroll bar used for browsing through the records listed may not move up and down smoothly when the AIS database contains a large number of records. Access to the records listed on the Resources tab is not impaired, but the movement of the scroll bar may be inconvenient to the user. Work Around: To avoid this issue, users who wish to browse the records on the Resources tab should use the up or down arrow (marked by a thumbtack icon) instead of the scroll bar.

MKM 7000 Console Alias Manager (CAM)

Known Problem RN_CCMPD-00002445 Abstract: CAM Server service startup fails. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user attempts to launch the CAM Server service using the Control Panel in the CAM Configuration Utility, the startup fails. When this occurs, one of the following warning messages may appear: ”The MKM 7000 Console Alias Manager failed to start, please contact Motorola Solution Support Center for further assistance.” “Operation failed to complete due to a timeout.” Work Around: Users should perform one of the following procedures: • For K-core systems, install local configuration appropriate for the CAM Server from the Windows Supplemental Configuration CD. • For L-core or M-core systems, while logged in as a current user, refresh the Group Policy Objects (GPO) from the Domain Controller (DC) and apply all necessary privileges to the CAMService account: Perform the following procedure: 1. From the Windows Start menu, run the command line tool (cmd.exe). 2. Type "gpupdate /force" in the command line and press the Enter key. 3. Wait 30 to 60 seconds and confirm that command has been successfully finished and there are no errors in command output. 4. Type "gpupdate /force" in the command line and press the Enter key to close the command line tool.

MLC 8000 Comparator

Issue Updates RN_CCMPD-00001536 Abstract: Windows applications may open behind MLC 8000 Configuration Tool (CT) window. System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A

18

ASTRO 25 7.14 Release Notes User Symptoms: When a user opens a Windows software application on a service laptop while the CT is running, the newly opened window may appear behind the CT window. Functionality is not impaired, but the display may be confusing or inconvenient to the user. Description: Windows applications no longer open behind the CT window.

RN_CCMPD-00001537 Abstract: Previous version of MLC 8000 Configuration Tool (CT) may persist in Windows list of installed programs. System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: After installation of a new version of the CT, the previous version and the newly installed version may both appear in the Windows operating system's list of currently installed programs (for example, in the "Add or Remove Programs" window launched from the Windows Control Panel). The installation of the new version successfully replaces the previous version, but the display of both versions as being currently installed may be confusing to the user. Description: After installation of a new version of the CT, only the newly installed version now appears in the Windows list of currently installed programs.

RN_CCMPD-00001612 Abstract: Voter Gateway Unit (VGU) may not report transmissions by ASTRO Gateway Unit (AGU) to Dispatch Application (DA) of MLC 8000 Configuration Tool (CT). System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: After a connection loss and reconnection of the Simulcast Site Reference (SSR) to the AGU, the DA software may not indicate that the AGU is transmitting. Description: After a connection loss and reconnection of the SSR to the AGU, the VGU now reports transmissions by the AGU to the DA, and the DA software now correctly indicates when the AGU is transmitting.

RN_CCMPD-00001827 Abstract: ASTRO Gateway Unit (AGU) port may be deassigned from Voter Gateway Unit (VGU). System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: This issue applies to analog systems only. User Symptoms: On analog systems, the AGU port may be deassigned from the VGU and placed in the "unassigned" category in the Configuration Tool (CT) main window system tree. When the AGU port is unassigned, no voice can be transmitted through the port. This occurs when a user changes the link type for the AGU port from "4W - External PTT(Circuit)" to "4W - TRC" or from "4W - TRC" to "4W - External PTT(Circuit)". Description: On analog systems, the AGU port is no longer deassigned from the VGU and placed in the "unassigned" category in the CT main window system tree.

RN_CCMPD-00001828 Abstract: MLC 8000 Configuration Tool (CT) may record data entries incorrectly for some parameters. System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user enters a configuration parameter value in the CT with more than one digit after the decimal point and clicks "Write to device" to save the value, the CT may save an incorrect value for that parameter. This occurs because the CT allows only one digit after the decimal point for any parameter for which entry of non-integer values is allowed (for example, Output Level, Input Level Differential, Activity Threshold, Console Hangtime, Repeat Hangtime, and Voting Hysteresis). • When the user enters the second digit after the decimal point, the CT deletes that number, and the cursor jumps to the beginning of the line for the entry of the next digit. For example, an entry of “1.234” becomes “41.2” in the CT. • If the resulting number is not within the valid range for the parameter, a popup error message is displayed when the user clicks “Write to device;” otherwise, the incorrect value is saved. Description: When a user enters a configuration parameter value in the CT with more than one digit after the decimal point and clicks "Write to device" to save the value, the cursor now remains positioned after the first digit following the decimal point, and the CT ignores any subsequent digits. The issues described in the User Symptom no longer occur.

19


MZC 5000 Zone Controller (ZC)

Issue Update RN_CCMPD-00002444 Abstract: Control channel for SmartX site is displayed in ZoneWatch (ZW) after site is turned off in Unified Event Manager (UEM). System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: Systems with 3600 sites and MZC5000 (SmartX systems). User Symptoms: A few minutes after a SmartX 3600 site is turned off in the UEM, the control channel for this site is still displayed in the ZW application. However, the site is correctly turned off, and the displayed channel is not functional. Functionality of sites and channels is not impaired, but the erroneous display may be confusing to the user. Description: The ZW application no longer displays control channel information for sites that were turned off in the UEM.

Provisioning Manager (PM)

Issue Updates RN_CCMPD-00002092 Abstract: PM application may fail to distribute configuration changes to Zone Database Server (ZDS). System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: In rare instances, the PM application may not distribute configuration changes to the ZDS. When this occurs, users may observe one of the following conditions: • No ZDS is listed on the "Device List" page in the Provisioning Manager. • When a user initiates a "Force Initialize Configuration" or "Distribute Configuration Changes" operation that includes a ZDS, the Provisioning Manager displays the following error message: "<ZDS DNS name>, Operation Failed. Internal data access error. Please contact Motorola Solutions Support Services." Description: The PM application now distributes configuration changes to the ZDS successfully, and the conditions described in the User Symptom are no longer observed.

RN_CCMPD-00002093 Abstract: "Force Initialization" may fail. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue affects systems equipped for the Dynamic System Resilience (DSR) feature. User Symptoms: In rare instances, a "Force Initialization" operation to the Zone Database Server (ZDS) may fail. This occurs when the user attempts a DSR switchover from the active User Configuation Server (UCS) to the standby UCS on a system where the active and standby UCS were never synchronized. Description: A "Force Initialization" operation to the ZDS now completes successfully when the user performs a DSR switchover from the active UCS to the standby UCS on a system where the active and standby UCS were never synchronized. NOTE: The applicable procedure in the "Provisioning Manager" manual should be executed after a DSR switchover from the active UCS to the standby UCS on a system where the active and standby UCS were never synchronized.

RN_CCMPD-00002094 Abstract: Provisioning Manager (PM) application may erroneously display blank list of available records during bulk delete operations. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: In rare instances, PM application users may see a blank record list view page, even though the requested records exist. This occurs when a user selects and deletes more than 4000 records in a single (bulk) delete operation and executes additional bulk delete operations in succession. Functionality is not impaired, but the erroneous display of a blank list may be confusing to the user. Description: The PM application no longer displays a blank list of available records during bulk delete operations.

20

ASTRO 25 7.14 Release Notes RN_CCMPD-00002095 Abstract: Provisioning Manager (PM) application users cannot enter Unified Network Configurator (UNC) passwords containing "@" character. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: Users cannot enter UNC credentials in the "Password" and "Confirm Password" fields in the User record in the PM application when the password string contains the "@" character. Description: Users can now enter UNC passwords containing the "@" character in the PM application.

Routers and Gateways

Issue Updates RN_CCMPD-00001825 Abstract: Conventional Channel Gateway (CCGW) channel configuration changes may not take effect when distributed. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue affects only channels that are configured with the “Method to Key the Transmitter” parameter set to “Tone” or “ToneAndRelay.” User Symptoms: When a user changes the setting of a CCGW conventional channel configuration parameter from the Provisioning Manager or the Configuration Manager and distributes the change, the change may not take effect until the channel is disabled and re-enabled from the Unified Event Manager (UEM). When the distributed change does not take effect, the user has no way to determine whether the change has taken effect. Description: CCGW channel configuration changes now take effect when distributed from the Provisioning Manager or the Configuration Manager, and the user no longer needs to disable and re-enable the channel.

RN_CCMPD-00001826 Abstract: Crosstalk may be observed on a conventional channel when the alignment tone level is set to its maximum value. System Platforms Affected: ASTRO 25 7.13 Special Configurations: This issue affects only GGM 8000 conventional channel gateways (CCGWs) equipped with Enhanced Conventional Gateway modules. User Symptoms: Crosstalk may be observed on a conventional channel when the “Outbound Alignment Tone Level” parameter is set to the maximum allowed value (+5 dBm) from the Provisioning Manager or the Configuration Manager. Description: Crosstalk is no longer observed on a conventional channel when the “Outbound Alignment Tone Level” parameter is set to the maximum allowed value (+5 dBm) from the Provisioning Manager or the Configuration Manager.

RN_CCMPD-00002170 Abstract: Commands sent to Conventional Channel Gateway (CCGW) may not display data-related information for configured IP mixed mode channels. System Platforms Affected: ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user issues the “SHow -CCGW DataCapable” command from the CCGW command line interface (CLI), the resulting display does not include information for any IP mixed mode channels that are configured on the device. When a user issues the “SHow -CCGW CONFiguration” command from the CCGW CLI, the resulting display does not include data-related information for any IP mixed mode channels that are configured on the device. When these conditions occur, the user must use the Provisioning Manager to view data-related information about the IP mixed mode channels configured on the CCGW. The configured channels are operational, and functionality is not affected, but the absence of data-related information in the CLI displays may be confusing to the user. Description: The display returned by the CCGW “SHow -CCGW DataCapable” command now includes information for configured IP mixed mode channels, and the display returned by the “SHow -CCGW CONFiguration” command now includes data-related information for configured IP mixed mode channels.

21

ASTRO 25 7.14 Release Notes Known Problems RN_CCMPD-00002502 Abstract: Conventional channel gateway (CCGW) may not apply conventional channel reconfigurations from Provisioning Manager (PM) successfully. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue affects GGM 8000 CCGWs equipped with an Enhanced Conventional Gateway module only. GGM 8000 CCGWs equipped with an analog/V.24 interface kit and MNR S2500 CCGWs are not affected. User Symptoms: When the user creates and configures a conventional channel on the CCGW from the PM, then performs a reconfiguration using the PM (for example, by reassigning the channel to a different port or by creating a second channel with an identical configuration on a different port), the CCGW may not apply the configuration changes. For example, in the case of a channel that is reassigned to a different port, the CCGW may keep the channel on the original port, and in the case of a second channel that is created with an identical configuration on a different port, the CCGW may create the second channel but make the first channel unavailable (missing in the CCGW configuration or assigned to an unknown (“??”) port). Work Around: None. To avoid this issue when reconfiguring conventional channels on the CCGW from the PM, users should distribute the changes to the CCGW after making modifications on each panel in the PM, rather than waiting to distribute the changes until after making all necessary modifications in the PM. For example, when reassigning the channel to a different port, users should perform the following actions: 1. Delete the original port in the PM. 2. Distribute the change from the PM to the CCGW. 3. Add the channel on the new port in the PM. 4. Distribute the change from the PM to the CCGW. Similarly, when creating a second channel with an identical configuration on a different port, users should perform the following actions: 1. Add the new channel on the different port. 2. Distribute the change from the PM to the CCGW. For detailed instructions for these operations, users should refer to the "Provisioning Manager" manual. To recover when this issue has occurred (for example, if PM operations have already been performed that have not produced the expected results on the CCGW), users should perform a “full sync” by disabling and re-enabling the CCGW service on the site using the Unified Event Manager (UEM). IMPORTANT: Because the following activity disrupts the entire site, it should be scheduled for either pre-install windows or an upgrade window where it is acceptable to disrupt the operation of the site. To disable and re-enable the CCGW service on the site using the UEM, users should follow these steps: 1. Navigate to the “Network Database” node in the UEM Navigation View. 2. Select the row corresponding to the CCGW you are managing. CCGWs are listed with “Motorola Network Resource – CCGW – Conventional” in the “Type” field. The specific CCGW can be identified by the values in the “Managed Resource Name” and the “IP Address” fields. 3. Right-click the appropriate row and select “Issue Command” from the “Managed Resource Properties” panel. A dialog box pops up. 4. In the popup dialog, perform the following actions: a. Under “Available Commands”, select “Disable”. b. Click “Apply”. c. Under “Available Commands”, select “Up”. d. Click “Apply”. e. Click “Close” to close the dialog.

22


System Traffic Monitor Applications

Issue Update RN_CCMPD-00002076 Abstract: ZoneWatch application (ZW) may fail to start. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: Occasionally, when a user attempts to start ZW, the starting process becomes stuck, and the application becomes unresponsive. Description: The ZW startup process now functions correctly.

Known Problems RN_CCMPD-00002432 Abstract: Reports exported to Excel from STM Historical Reports application my contain misaligned headers or data. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user exports a report from the Historical Reports application to the Excel file format, some columns in the exported file may contain headers or data that are not aligned correctly. The incorrect alignment should have only minor impact on the readability of the report but may be inconvenient to the user. Work Around: If the misalignment in the Excel reports in inconvenient, users can export the reports to other file formats, such as comma separated values (CSV) or portable document format (PDF).

RN_CCMPD-00002458 Abstract: "System Voice and Data Detail" report displays less detail than requested in "Counts" and "Duration" graphs. System Platforms Affected: ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user requests a "System Voice and Data Detail" report from the Historical Reports application with 15-minute intervals in the "Counts" and "Duration" graphs, the application generates reports with one-hour intervals in both graphs. The information displayed in the graphs is accurate, but the inability to retrieve the requested level of detail may be confusing to the user. Work Around: None.

RN_CCMPD-00002497 Abstract: Time Division Multiple Access (TDMA) calls involving more than 32 sites may not appear in grid window in ZoneWatch (ZW) application. System Platforms Affected: ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a TDMA group call is performed on more than 32 sites, the call is not displayed in the grid window in ZW as expected. The call is displayed in the raw ZW window and in the Air Traffic Information Access (ATIA) Log Viewer, but neither of those windows displays the additional information about channel slots that is displayed in the grid window. When this issue occurs, the Zone Controller (ZC) sends the correct information through ATIA to third-party applications. However, the inability to view the expected details in the grid window may be confusing to the user. Work Around: None.

RN_CCMPD-00002504 Abstract: ZoneWatch (ZW) application may not fully refresh display in channel grid. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A

23

ASTRO 25 7.14 Release Notes User Symptoms: When a user adjusts the width of the channel grid in the ZW window, ZW may apply the change only to the first visible site row, rather than applying the change to the entire grid as expected. When the user presses the F5 key to refresh the ZW display, the width of the channel grid is adjusted for all sites displayed. Work Around: None. To recover, press the F5 key to refresh the ZW display.

Unified Network Configurator (UNC)

Issue Updates RN_CCMPD-00002111 Abstract: Deletion of large site from large system may fail. System Platforms Affected: ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13 Special Configurations: As used in this note, the terms "large site" and "large system" are influenced by various factors, including (but not limited to): the number of devices discovered in the system; the number of events in the Event Manager; the activity in the Schedule Manager; the presence of a backup or some other processor or database-impacting task; and whether discoveries are occurring. User Symptoms: When a UNC user attempts to delete a large site from a large system, the "Policy Enforcement" job may not be scheduled. When this occurs, the UNC fails to remove any sites and channels associated with the deleted site from any zone controllers (ZCs), packet data routers (PDRs) or air traffic routers (ATRs) in the system, and any site adjacency updates fail. The ZCs, PDRs, and ATRs remain non-compliant, and no remedy jobs are generated until they are pulled or until the user performs an "Enforce Policy" operation for those devices. Description: Deletion of a large site from a large system now completes successfully.

RN_CCMPD-00002112 Abstract: Discovery jobs may generate misleading error messages for devices in "Lost and Found" folder. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user attempts to discover a device from the UNC, processing issues may cause the device to be put in the "Lost and Found" folder. When this occurs, the user sees the following text in the result tab for the discovery job (where <nnnn> may be any number with up to four digits): "chmod 770 /tftpboot/ZCCM/config/<nnnn> resulted in: chmod: changing permissions of `/tftpboot/ZCCM/config/<nnnn>': Operation not permitted" This occurs because the UNC cannot detect the device, which is actually present but has no configuration. Functionality is not impaired, but the error message may be confusing to the user. Description: Discovery jobs no longer generate misleading error messages for devices that are put in the "Lost and Found" folder.

Known Problems RN_CCMPD-00002409 Abstract: EMC Smarts Network Configuration Management application displays confusing message for login errors. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user attempts to log into the EMC Smarts Network Configuration Management application and enters an invalid user name or an invalid password, the user sees the following message in a popup window: "An unexpected problem has occurred." When the user clicks "OK" in the popup window and enters a valid user name and password, the login completes successfully. Login should be blocked when incorrect credentials are entered, but the message displayed provides no guidance about corrective action and may be confusing to the user. Work Around: None. To avoid this issue, users should enter only valid user names and valid passwords when logging into the EMC Smarts Network Configuration Management application.

24

ASTRO 25 7.14 Release Notes RN_CCMPD-00002424 Abstract: Report Advisor in EMC Network Configuration Manager may not generate reports. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user attempts to generate a report using the Report Advisor application in the EMC Network Configuration Manager, the attempt may fail. When this occurs, the "in-progress" icon in the application spins continuously and persistently, instead of stopping as expected, and no report appears. Work Around: To avoid this issue, users should navigate the EMC Network Configuration interface to look up device functionality directly rather than using the Report Advisor application. To recover, users should close the Report Advisor web page to clear the spinning “in-progress” icon, then disable and re-enable the UNC.

RN_CCMPD-00002430 Abstract: User may be unable to log in to UNC server. System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: User may be unable to log in to the UNC server. When this occurs, the Unified Event Manager (UEM) may display a malfunction event for the UNC server and may instruct users to re-enable the server. In addition, the Voyence service may restart without the user instructing it to do so. Disabling and then re-enabling the UNC server clears the stalled connections. Work Around: None. To recover, users should re-enable the UNC server or restart the Voyence service.

RN_CCMPD-00002434 Abstract: Users cannot roll Simple Network Management Protocol version 3 (SNMPv3) passphrase using Unified Network Configurator (UNC). System Platforms Affected: ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When users attempt to roll the SNMPv3 passphrase using the UNC, the operation is marked as failed, and an error message appears. Work Around: User should roll the SNMPv3 passphrase using Configuration/Service Software (CSS), as described in section 8.8.1 of the "SNMPv3" manual that is provided with the ASTRO 25 system.

RN_CCMPD-00002498 Abstract: UNC fails to distribute update for "SubSite Alias" field. System Platforms Affected: ASTRO 25 7.5, ASTRO 25 7.6, ASTRO 25 7.7, ASTRO 25 7.8, ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.12, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: This issue affects systems with simulcast or multisite configurations. User Symptoms: When a user attempts to distribute an update for the "SubSite Alias" field from the UNC, the distribution fails, and the user is notified that the "SubSite Alias" string exceeds the maximum allowed number of characters. This issue occurs because the UNC erroneously allows users to enter up to 20 characters in the "SubSite Alias" field, but the actual maximum allowed number of characters is 16. Work Around: None. To recover, users should edit the "SubSite Alias" field to a string of no more than 16 characters and retry the update.

Virtual Management Server (VMS)

Issue Updates RN_CCMPD-00002086 Abstract: VMS fails to display centralized logging status in response to request from non-root user. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a non-root user executes the "Display Centralized Logging Status" operation on the VMS, the user sees an error message indicating that the syslog configuration is not readable.

25

ASTRO 25 7.14 Release Notes Description: When a non-root user executes the "Display Centralized Logging Status" operation on the VMS, the VMS now displays the status as expected.

RN_CCMPD-00002087 Abstract: Troubleshooting interface for Direct Attached Storage (DAS) may display blank screen instead of login prompt. System Platforms Affected: PS LTE R6.0, ASTRO 25 7.13 Special Configurations: N/A User Symptoms: When a user attempts to connect to the DAS interface via a web browser to troubleshoot a component failure, the browser may display a blank screen instead of the login prompt. When this occurs, users cannot log into the interface to perform the desired troubleshooting. Description: When a user attempts to connect to the DAS interface via a web browser to troubleshoot a component failure, the browser now displays the login prompt as expected.

RN_CCMPD-00002088 Abstract: Unified Event Manager (UEM) may falsely report critical alarms for Hewlett-Packard (HP) DL380 Gen8 server. System Platforms Affected: ASTRO 25 7.13 Special Configurations: N/A User Symptoms: The UEM may report critical alarms for fans, power supplies, temperature, and central processing units (CPUs) for the HP DL380 Gen8 server, which is the hardware platform for the Virtual Management Server software, when no hardware faults are actually occurring on the server. Functionality is not impaired, but the erroneous alarms may be confusing to the user. Description: The UEM now reports critical alarms for fans, power supplies, temperature, and central processing units (CPUs) for the HP DL380 Gen8 server only when an actual hardware fault exists.

Known Problems RN_CCMPD-00002452 Abstract: Zip archive created during "getlogs" operation contains incorrect timestamp in filename. System Platforms Affected: ASTRO 25 7.9, ASTRO 25 7.11, ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: When a user initiates a "getlogs" operation, the operation archives the desired logs to a zip file, with a timestamp embedded in the zip file name as expected, but the month value in the timestamp is one less than expected. For example, a log file collected in October includes 09 instead of 10 as the month value in the timestamp. The user can see the actual creation date of the zip file by performing the "ls -l" command in the log file directory. Logging functionality is not impaired, but the incorrect timestamp may be confusing to the user. Work Around: None. To recover, a user can manually rename a log file with the correct month value in the timestamp.

RN_CCMPD-00002453 Abstract: Unified Event Manager (UEM) or Unified Network Configuration (UNC) may display erroneous error message. System Platforms Affected: ASTRO 25 7.13, ASTRO 25 7.14 Special Configurations: N/A User Symptoms: The UEM or UNC console may report a lockup of the central processing unit (CPU) when no actual lockup behavior has been observed. When this occurs, an error message similar to the following example appears: "08:59:15 DUMP [UCS1] kernel:BUG: soft lockup - CPU#2 stuck for 64s! [vmmemctl:703]" Functionality is not impaired, but the erroneous error message may be confusing to the user. Work Around: None. To recover, users should verify that the system is operating correctly by examining the UEM logs for alarms. If no unexplained alarms are present in the UEM logs, then the error message can be ignored.

26

astro 25 7.14 release notes - semnrrb.comsemnrrb.com/documents/motorola/7.14 customer release notes...

Documents