Spectrum Hotfix patch H01 for 9.3 - fixes and enhancements - Part 1

Document ID : KB000018980
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This knowledge document only lists the fixes and enhancements to pre-existing functionality that Spectrum hotfix patch H01 for 9.3 will deliver. The full and final Software Release Notice (SRN) contains requirements, special considerations and installation instructions. Please read the full SRN which can be download along with H01 when it becomes Generally Available (GA).

Links to the H01 download will be included in the H01 GA Announcement which will be posted on the Spectrum home product page; https://support.ca.com/irj/portal/anonymous/prddtlshome?prdhmpgform=p&productID=7832.

Solution:

DETAILS OF H01 CONTENTS

New Functionality

     CAPKI Upgrade (H01, 265780)
          CAPKI has been upgraded to 4.3.3.

     MySQL Upgrade (H01, 285024)
          MySQL has been upgraded to 5.5.35.

     Java Upgrade (H01, 285439)
          Java has been upgraded to 1.7.0_51.

     Tomcat Upgrade (H01, 280138)
          Tomcat has been upgraded to 7.0.42.

     Enhancements to NCM Device Capture functionality (H01, 110529)
          Spectrum NCM has been enhanced to capture the devices with large configurations having more than 20,000 lines.
          This functionality can be enabled by adding the following entry in $SPECROOT/NCM/config.xml file:
          <diff-largefile type = "java.lang.String" >on</diff-largefile>

     Availability Reports (H01, 193112)
          Availability Reports have been updated for IMB and MS cluster.

     Fortinet Certifications (H01, 275631)
          Fortinet devices support has been enhanced with the addition of 19 new devices
          under FortinetFortiOS, FortinetFortiAnalyzer and FortinetFortiManager model types.

     Enhancements to AutoDiscovery (H01, 260174)
          Spectrum AutoDiscovery has been enhanced for range discovery to optionally ignore checking for the discovered IP address in the device's IP address table.
          This can be achieved by deselecting the "Require discovered IP entry in device's IP Address Table" checkbox in the Advanced Options section of the Discovery Configuration.

Fixes to Alarm Management

Symptom: Alarms can take a long time to appear in the OneClick alarm console due to the computation of the Internal_Port_Link_Status attribute.
Resolution: Resolved locking/threading issues due to the computation of Internal Port Link Status.
(H01, 214105, 21315615-1)

Symptom: When a logMonMatch trap is received with the loopback address in the syslog message, the SysEDGE model unnecessarily forwards the events on to the models that have the loopback address configured.
Resolution: A loopback address check is now done before forwarding the events on to the models. The SysEDGE model will not forward the events to the models if the address is the loopback address.
(H01, 224715, 21401266-1)

Symptom: V3 traps are not processed for SHA and AES protocols.
Resolution: V3 traps are now processed for SHA and AES protocols.
(H01, 225941, 21459432-1)

Symptom: Port down alarms are not generated for some devices for which the PollPortStatus attribute on device model is reset.
Resolution: Port down alarms are generated even if the PollPortStatus attribute on device model is reset.
(H01, 263633, 21330721-1)

Symptom: Spectrum OneClick Console is displaying an inaccurate status in the Interfaces tab of BigIP 6400 (Device Type) (Model Type Name: F5BigIPDev) when the ports are disabled. Spectrum is showing as down instead of disabled in the Status column. As a result, when the PollPortStatus (0x1280a) attribute is enabled on the port model, and then the port is disabled, Spectrum is asserting BAD LINK DETECTED alarm.
Resolution: To differentiate between a disabled interface and a down interface, use the sysInterfaceStatus MIB in conjunction with the sysInterfaceEnabled. If an interface is reported down and enabled, the interface is down; if an interface is reported down and disabled, the interface is disabled.
(H01, 274767, 21482647-1)

Fixes to Alarm Notifier and SANM

Symptom: Alarms are not cleared on the secondary SpectroSERVER when the primary SpectroSERVER is down.
Resolution: A retry count has been added; it will try 3 times to connect to the secondary SpectroSERVER and clear the alarms.
(H01, 213499, 21310981-1)

Symptom: SANM moves ALL landscapes to the exclude side when saving the policy filter.
Resolution: SANM will not move ALL landscapes to the exclude side when saving the policy filter.
(H01, 224713, 21302329-1)

Symptom: AlarmNotifier sends repeated SET alarm notifications and incorrect alarm CLEAR notifications in a Fault Tolerant environment.
Resolution: AlarmNotifier will not send repeated SET alarm notifications or incorrect alarm CLEAR notifications in a Fault Tolerant environment.
(H01, 261638, 21400880-1)

Symptom: Alarm Notifier attributes are returned with leading blank spaces thereby impacting any third party integrations that rely on the exact values of Notifier attributes.
Resolution: Alarm Notifier attributes are returned without any leading blank spaces.
(H01, 272425, 21601660-1)

Fixes to AutoDiscovery

Symptom: Unable to import hostnames/IP addresses from a text file when the file contains an unresolved hostname or IP address.
Resolution: Able to import the hostnames/IP addresses from a text file that contains an unresolved hostname or IP address. The unresolved hostnames or IP addresses are written to OneClick debug console output.
(H01, 212868, 21318483-1)

Symptom: The DRC of the Cisco ACE device was set to "Router".
Resolution: The DRC of the Cisco ACE device has been set to "None" in place of "Router".
(H01, 213478, 21303300-1)

Symptom: Unable to discover Pingable devices with the Discovery Console in OneClick.
Resolution: Pingable devices can now be discovered with the Discovery Console in OneClick.
(H01, 213485, 21081764-1)

Symptom: The Lldp Neighbor Table OneClick view populates the wrong value under the Local Port field.
Resolution: The Lldp Neighbor Table OneClick view now populates the correct value under the Local Port field.
(H01, 219894, 21410544)

Symptom: The OneClick server and SpectroSERVER become unresponsive during very large range discoveries. Very large range discoveries progress very slowly.
Resolution: Set up dedicated thread pool to limit discovery impact on other parts of OneClick. Reduced the number of threads available for the discovery process to limit discovery impact on the SpectroSERVER. Implemented multi-threaded range discovery.4. Improved algorithm to handle de-duplication of discovered devices, significantly reducing unnecessary IP address table reads.
(H01, 222782, 20961526-1)

Symptom: Discovery and Alarm Filters may not work under certain conditions. The problem typically manifests itself when the OR logical operator is used or when the comparator is of the form "Does Not...".
Resolution: The Discovery and Alarm Filter have been fixed so that AND/OR logical operators and Not comparison filters work properly in the presence of missing data.
(H01, 263933, 21545175-1)

Fixes to CA Introscope (Wily)

Symptom: User is unable to launch the live Introscope dashboards from Spectrum OneClick console.
Resolution: User will be able to launch the live Introscope dashboards from Spectrum OneClick console.
(H01, 256842, 21532407-1)

Fixes to CA Service Desk

Symptom: Unable to launch the Service Desk ticket from the Events tab in Spectrum; Service Desk link failed with "Error determining URL for ticket" error message.
Resolution: User will be able to launch the Service Desk ticket from Events tab in Spectrum.
(H01, 256074, 21433973-1)

Symptom: When a ticket is unassigned in CA Service Desk Manager, Spectrum creates a "null" troubleshooter.
Resolution: When a ticket is unassigned in Service Desk, Spectrum will not create a "null" troubleshooter.
(H01, 258017, 21535745-1)

Fixes to CA eHealth Integration

Symptom: Initial mapping failed with the following error: "Initial mapping request failed! PreparedStatementCallback; uncategorized SQLException for SQL...".
Resolution: Initial mapping request now completes successfully.
(H01, 256072, 21317119-1)

Symptom: When a user right-clicks on a live eHealth alarm in OneClick, the "Alarm Detail Report (eHealth)" link is missing.
Resolution: The "Alarm Detail Report (eHealth)" link is now shown.
(H01, 271720, 21603462-1)

Fixes to Chassis Management

Symptom: In some devices that support the ENTITY-MIB, the interfaces do not appear under their respective chassis module because the MIB specifies container modules in between them.
Resolution: Fixed chassis modeling to show the interfaces under their respective modules even if there are containers defined between them.
(H01, 220370, 21279164-1)

Fixes to Command Line Interface (CLI)

Symptom: Clearticket is crashing during alarm clear.
Resolution: Clearticket utility does not crash when clearing the alarm.
(H01, 213497, 21340587-1)

Fixes to Event Management System

Symptom: OneClick displays garbled characters in the OneClick Events tab for event 0x2104a7.
Resolution: OneClick displays event message properly in the OneClick Events tab for event 0x2104a7.
(H01, 212865, 21331520-1)

Symptom: If using the event_disp_error parameter in the $SPECROOT/SS/.vnmrc file, the user may see an error similar the following when processing event 0x11c0004:2013/02/25 18:57:16: Warning: Event rule CA.EventCondition for model 0x123456, model name model1, for event 0x11c0004 Unable to evaluate expression - possibly due to attempted access of a non-existent trap variable.
Resolution: This error message will no longer appear for event 0x11c0004.2013/02/25 18:57:16: Warning: Event rule CA.EventCondition for model 0x123456, model name model1, for event 0x11c0004 Unable to evaluate expression - possibly due to attempted access of a non-existent trap variable.
(H01, 212866, 21331431-1)

Symptom: The return value in the description of a procedure is incorrect in " \Spectrum\SS\CsVendor\CA\Procedures\GetRegexp.xml " file.
Resolution: The description has been updated with the correct return value.
(H01, 212885, 21403769-1)

Symptom: The Event Configuration editor view shows a Single Event rule incorrectly (ResetEventCode and SingleTargetEventCode are swapped).
Resolution: The Event Configuration editor view now shows the Single Event rule properly.
(H01, 225118, 21440694-1)

Symptom: For an event code in Event Configuration, the event condition rule that contains a "default" is modified when the user clicks the Edit button and clicks Ok without making any changes. An end parenthesis is being appended at the end of the default text.2. The default Operator is changed to "Equal TO".
Resolution: The end parenthesis is removed from the criterion when the exception is caught. Also, the default operator remains unchanged.
(H01, 251193, 21519328-1)

Symptom: Under rare circumstances, false Application Contact Lost (0x10d09) alarms could be rapidly generated and cleared.
Resolution: Resolved the race condition that could cause false Application Contact Lost (0x10d09) alarms to be rapidly generated and cleared.
(H01, 251901, 21258998-1)

Symptom: The ospfIfStateChange Trap is configured incorrectly, resulting in an inaccurate event message being reported when this trap occurs.
Resolution: The ospfIfStateChange trap is mapped to the correct event type, thereby displaying the appropriate event message for this trap.
(H01, 256146, 21529182-1)

Symptom: Error message generated for 0x22002e event in event_disp_error Time value is too big: 4294967295.
Resolution: No such error message will be generated for 0x22002e event.
(H01, 266877, 21331422-1)

Symptom: Some Event format and PCause files are missing as part of Spectrum 9.3.0.0 installation corresponding to model types "Host_Device", "Host_Compaq", etc. Majority of these configuration files correspond to non-alarming Events.
Resolution: Missing Event format and PCause files related to "Host_Device", "Host_Compaq" etc. have been bundled and all the corresponding events and probable causes will be displayed in expected format.
(H01, 283975, 21657574-1)

Fixes to Events and Alarms

Symptom: OneClick shows inconsistent alarms. Alarms of other landscapes are seen.
Resolution: All the paths associated with the device will be added to a list and this list will be added against the model handle as key for the device.
(H01, 212998, 21347821-1)

Symptom: While sending email for an alarm from the OneClick alarms tab, the subject field shows the last sent email subject instead of default subject of "CA Spectrum Alarm".
Resolution: While sending email for an alarm from the OneClick alarms tab, the subject field shows the default subject of "CA Spectrum Alarm".
(H01, 225620, 21469907-2)

Fixes to Fault Isolation

Symptom: The SpectroSERVER shows green devices connected to fault domains for which all of the other models are grey when users were clearing unresolved fault alarms (0x10703).
Resolution: Unresolved fault alarms (0x10703) cannot be cleared by users.
(H01, 226718, 21511232-1)

Fixes to Global Collections

Symptom: The "Update Global Collection Membership" privilege is not respected for users who are not granted the "Manage Global Collections" privilege.
Resolution: The "Update Global Collection Membership" is respected regardless of whether or not the user has the "Manage Global Collections" privilege enabled.
(H01, 224402, 21496471-1)
(H01, 227962, 21496471-1)

Fixes to Install

Symptom: Spectrum distributed install fails when using sudo privileges.
Resolution: Spectrum distributed installation will be successful even with the sudo user.
(H01, 261069, 21554446-1)
(H01, 269258, 21589338-1)

Symptom: EULA is not shown for localized i.e. Japanese, Simplified Chinese and Traditional Chinese hot fix (H01) Spectrum installations on all 3 platforms.
Resolution: Fixed the code to ship the localized license files on to VCD, so the EULA will be shown.
(H01, 277911)

Fixes to Integrations

Symptom: Event Integration is not properly displaying raw varbind data.
Resolution: Change the way raw varbind data is passed to Event Integration so it can be displayed properly.
(H01, 256595, 21158284-1)

Fixes to Locator Search

Symptom: In the OneClick console attributes tab, the values of ifsysUptime and ifLastChange are negative when these values are very large.
Resolution: In the OneClick console attributes tab, the values of ifsysUptime and ifLastChange will be displayed appropriately even when the values are very large.
(H01, 226499, 21353088-1)

Click here to view Part 2 of the document for more information.