Spectrum 9.3.0 release - fixes and enhancements

Document ID : KB000048433
Last Modified Date : 14/02/2018
Show Technical Document Details
ava.lang.String".
Resolution: When the action 0x10474 is sent from CLI we get the response in the String type format. Currently only OctetString and Counter as response are handled. Added support to handle when the response is of String type.
(9.3.0, 157973, 21226213-1)
  • Symptom: Alarm subscription through Spectrum Restful Web Services is not sending the updates when an alarm attribute (e.g. "Trouble TicketID" or "Assignment") is changed for an existing alarm.
    Resolution: Alarm subscription through Spectrum Restful Web Services will send the updates when an alarm attribute (e.g. "Trouble TicketID" or "Assignment") is changed for an existing alarm.
    (9.3.0, 183205, 21209377-1)
  • Fixes to SNMPv3

    • Symptom: False "SNMP V3 Duplicate Engine ID Alarm" alarms are generated.
      Resolution: False " SNMP V3 Duplicate Engine ID Alarm" alarms are no longer generated.Please refer to the Knowledge Base article for more information : https://support.ca.com/irj/portal/anonymous/redirArticles?reqPage=search&searchID=TEC590696.
      (9.3.0, 198394)

    Fixes to SS and DB Tools

    • Symptom: "Error Debugging Enabled" appears twice in log files after corba trace debugging (corbatrace=true) or SpectroSERVER debugging (debug=true).
      Resolution: "Error Debugging Enabled" now appears only once after debugging is enabled.
      (9.3.0, 189832)

    Fixes to Service Manager

    • Symptom: Changing outage type from unplanned to planned outage through Outage Editor dialog is not effecting the respective outage to be considered as maintenance outage.
      Resolution: Editing unplanned outage to planned outage through Outage Editor will make the outage to be considered as maintenance outage.
      (9.3.0, 99873, 20869330-1)

    Fixes to SpectroSERVER

    • Symptom: While running Upload task from Configuration Manager the SpectroSERVER crashes.
      Resolution: SpectroSERVER runs fine while running Upload task from Configuration Manager.
      (9.3.0, 108804, 21055710-1)
    • Symptom: When a device in Maintenance Mode is connected to a WA_Link, a situation may occur that causes a portion of the SpectroSERVER's threading to become deadlocked. It could occur when a user puts the device into Maintenance Mode or when a port connected to the WA_Link changes its status.
      Resolution: Fixed the coding flaw that led to the deadlock.
      (9.3.0, 126533, 21140394-1)
    • Symptom: The SpectroSERVER never raises an alarm when the device is taken out of maintenance and the disk monitoring threshold is still violated.
      Resolution: The SpectroSERVER raises an alarm when the device is taken out of maintenance and the disk monitoring threshold is still violated.
      (9.3.0, 142397, 21153052-1)
    • Symptom: The SpectroSERVER may crash while re-evaluating the model name and if we enable the logging by setting debug_model_naming_order=TRUE in the .vnmrc file.
      Resolution: The SpectroSERVER doesn't crash while re-evaluating the model name and if we enable the logging by setting debug_model_naming_order=TRUE in the .vnmrc file.
      (9.3.0, 147059, 21163723-1)
    • Symptom: The secondary SpectroSERVER intermittently crashes during shutdown as part of Fault-Tolerant database synchronization.
      Resolution: The fault-tolerant database synchronization process has been extended to properly handle this unusual scenario, fully recovering by successfully loading database from primary and restarting the SpectroSERVER.
      (9.3.0, 178817, 21234656-1)
      (9.3.0, 179496, 21294371-1)
    • Symptom: When SpectroSERVER database is migrated into a new Spectrum installation, statistics logging will be enabled by default leading to performance issues.
      Resolution: The statistics logging will be disabled by default in .vnmrc file. The statistics logging can be enabled if required, by setting the configuration 'stat_logging_disabled=false' in .vnmrc file.
      (9.3.0, 182635, 21151291-1)
    • Symptom: SpectroSERVER memory growth when SSLogger is used to gather multicast attributes.
      Resolution: SpectroSERVER memory will not grow when SSLogger is used to gather multicast attributes.
      (9.3.0, 183210, 20896554-1)
    • Symptom: The secondary SpectroSERVER intermittently crashes during shutdown as part of Fault-Tolerant database synchronization.
      Resolution: The fault-tolerant database synchronization process has been extended to properly handle this unusual scenario, fully recovering by successfully loading database from primary and restarting the SpectroSERVER.
      (9.3.0, 183533, 21276888-1)
    • Symptom: Application contact lost alarms are generated for polled application models when the device goes down.
      Resolution: Application contact lost alarms are not generated for polled application models when the device goes down.
      (9.3.0, 185030, 21069182-1)
    • Symptom: SpectroSERVER may crash while removing the stale interface during interface reconfiguration.
      Resolution: SpectroSERVER doesn't crash while removing the stale interface during interface reconfiguration.
      (9.3.0, 188471, 21295978-1)
    • Symptom: SpectroSERVER may continuously generate 0x10fab events(" This device is no longer managed by a chassis model") for every interface reconfiguration even if the device doesn't contain EntityMib data.
      Resolution: SpectroSERVER never generate 0x10fab events(" This device is no longer managed by a chassis model") for every interface reconfiguration if the device doesn't contain EntityMib data.
      (9.3.0, 188475, 21268750-1)
    • Symptom: SpectroSERVER crashes while processing the errors generated when enforcing certain type of policies on a model.
      Resolution: SpectroSERVER will not crash during the processing of errors generated while enforcing any type of policies.
      (9.3.0, 189653, 21238942-1)
    • Symptom: At times, state of few schedules are reflected incorrectly after SpectroSERVER restart.
      Resolution: All schedules will be displaying appropriate states after a SpectroSERVER restart.
      (9.3.0, 189655, 21202754-01)
    • Symptom: SpectroSERVER is crashing while importing SDM Configuration having duplicate SDC IP addresses.
      Resolution: Appropriate error message is displayed when we import SDM configuration having duplicate IP addresses.
      (9.3.0, 189902)
    • Symptom: SpectroSERVER crashes when a device sends unexpected or erroneous data during the processing of SysObjectId in model activation phase.
      Resolution: SpectroSERVER will not crash when a device sends unexpected or erroneous data during the processing of SysObjectId in model activation phase.
      (9.3.0, 190323, 21183501-1)
    • Symptom: SpectroSERVER may crash during VPLS discovery in DSS environment.
      Resolution: SpectroSERVER doesn't crash during VPLS discovery in DSS environment.
      (9.3.0, 193801, 21237016-1)
    • Symptom: SpectroSERVER may crash during Interface reconfiguration of devices having high port count.
      Resolution: SpectroSERVER doesn't crash during Interface reconfiguration of devices having high port count.
      (9.3.0, 196443, 21328324-1)
    • Symptom: The SpectroSERVER may crash during discovery of the connections for H3C device.
      Resolution: The SpectroSERVER doesn't crash during discovery of the connections for H3C device.
      (9.3.0, 196485, 21346502-1)
    • Symptom: SpectroSERVER unnecessarily log ICMP Server error message even if the error status is SUCCESS.
      Resolution: SpectroSERVER never log ICMP Server error message even if the error status is SUCCESS.
      (9.3.0, 198723, 21273753-1)
      (9.3.0, 178892, 21273753-1)
      (9.3.0, 184712, 21320144-1)
    • Symptom: 1. Intermittent SpectroSERVER crash when updating trap director cache due upon connection establishment.2. SpectroSERVER memory growth due to trap director forward attempts to unconnected landscapes.3. Secondary SpectroSERVER memory growth due to combination of hot-standby and trap director.
      Resolution: 1. Resolved crash when updating trap director cache.2. Resolved several reasons for memory growth when trap director is enabled.3. Disabled trap forwarding on hot-standby secondary SpectroSERVER.
      (9.3.0, 204434, 21397144-1)
      (9.3.0, 203987, 21391315-1)
    • Symptom: 1. Intermittent SpectroSERVER crash when updating trap director cache due upon connection establishment.2. SpectroSERVER memory growth due to trap director forward attempts to unconnected landscapes.3. Secondary SpectroSERVER memory growth due to combination of hot-standby and trap director.
      Resolution: 1. Resolved crash when updating trap director cache.2. Resolved several reasons for memory growth when trap director is enabled.3. Disabled trap forwarding on hot-standby secondary SpectroSERVER.
      (9.3.0, 205013, 21397144-1)
      (9.3.0, 206793, 21397144-1)
    • Symptom: Each time Spectrum connector initialize's it cause the SpectroSERVER process to leak huge chunk of memory.
      Resolution: Identified the most of memory leaks and fixing the deallocation part where ever it is applicable.
      (9.3.0, 208003, 21386187)
    • Symptom: The secondary SpectroSERVER intermittently crashes during shutdown as part of Fault-Tolerant database synchronization.
      Resolution: The fault-tolerant database synchronization process has been extended to properly handle this unusual scenario, fully recovering by successfully loading database from primary and restarting the SpectroSERVER.
      (9.3.0, 66533, 20814696-1)
    • Symptom: The SpectroSERVER may crash when changing the the server precedence from the One Click Loaded Landscapes view from the context of the Local Landscape model.
      Resolution: Corrected a flaw that could cause the SpectroSERVER to crash when its precedence is changed via the One Click Loaded Landscapes view on the Local Landscape model.
      (9.3.0, 189694)
    • Symptom: SpectroSERVER memory growth may occur over time due to a flaw in interface modeling logic.
      Resolution: Corrected SpectroSERVER memory growth issue related to interface modeling logic.
      (9.3.0, 153339)
      (9.3.0, 205795)

    Fixes to SpectroSERVER Watch Management

    • Symptom: When the SpectroSERVER is restarted, any model having watches that are marked 'Active By Default' are stuck in INITIAL state.
      Resolution: All watches are in Active state after a SpectroSERVER restart.
      (9.3.0, 82074, 20803728-1)

    Fixes to TL1 Gateway

    • Symptom: No connection can be established to TL1 devices, they stay red or blue. Debug output from the TL1 gateway show few if any connection attempts from the SpectroSERVER, and those which are made do not result in any successful login at the TL1 device.
      Resolution: The underlying problem, broken trap handling for the EPAPI protocol has been resolved. TL1 connections will be established successfully again.NOTE: if this fix is installed either as regular hotfix or patch in a distributed environment where the trap director functionality is used then ALL SpectroSERVERS in that DSS must be patched at the same time. Mixing releases will cause the trap director functionality to stop working.
      (9.3.0, 179777, 21179478-1)

    Fixes to Topology

    • Symptom: The list of landscape and SANM filters are limited to ten in the "€œLaunch Update Filter"€� dialog box in Advance Filter node under SANM->All Policy in OneClick Locator tab.
      Resolution: "€œLaunch Update Filter"€� dialog box in Advance Filter node under SANM->All Policy in OneClick Locator tab displays all the existing landscapes and SANM filters.
      (9.3.0, 204223, 21147285-1)
    • Symptom: If the user specifies a FQDN for the Main Location Server host, they would observe the following error message in either the OneClick Administration | Landscapes page or the MapUpdate command line utility output: "The parent landscape does not exist in the location server map for the local landscape.".
      Resolution: Users may now specify a FQDN for the Main Location Server host.
      (9.3.0, 205015, 21335157-1)

    Fixes to Trap Forwarding

    • Symptom: The SpectroSERVER exhibits memory growth when TrapDirector is enabled.Trap Director performance problem causes SpectroSERVER memory growth when the MLS is geographically far from.
      Resolution: Added the optional .vnmrc config option "alert_forwarding_use_relay_landscape=false", to allow TrapDirector to forward traps directly to the remote landscapes instead of via the MLS. This requires open network communication between SpectroSERVERs as the traffic is no longer routed to the MLS.
      (9.3.0, 196544, 21258291-1)