The following is a list of defects and fixes that have been included in the 10.3.1 release:
The following is a list of defects and fixes that have been included in the 10.3.1 release:
Fixes to SpectroSERVER
Symptom: SpectroSERVER gets stuck in the model activation state because of a few UIM model types added to the global collection.
Resolution: SpectroSERVER performs as expected and the model activation is successful after modifying the UIM bidirectional search criteria.
(10.3.1, DE313290, 00823470)
Symptom: SpectroSERVER (SS) crashes when deleting large number of processes at once.
Resolution: This issue has been fixed, and SS does not crash when deleting large number of processes at once.
(10.3.1, DE357978, 00997898)
Symptom: AlertMap files in the following directory:
$SPECROOT/custom/Events/folder1/subfolderavailable in the primary SpectroSERVER (SS) do not sync over to the secondary SpectroSERVER (SS) in a fault tolerance environment.
Resolution: This issue has been fixed and the AlertMap files in the following directory:
$SPECROOT/custom/Events/folder1/subfolderavailable in the primary SpectroSERVER (SS) now sync over to the secondary SpectroSERVER (SS) in a fault tolerance environment.
(10.3.1, DE365233, 01061640)
Symptom: SpectroSERVER (SS) crashes while reading the empty physical serial number of a device.
Resolution: This issue has been fixed and the SS does not crash while reading the empty physical serial number of a device.
(10.3.1, DE368190, 01102965)
Symptom: SpectroSERVER (SS) crashes after updating and importing the SDM.config file.
Resolution: SpectroSERVER (SS) does not crash after updating and importing the SDM.config file.
(10.3.1, DE375492, 01111162)
Symptom: Duplicate RTM_TestHost models are created after SpectroSERVER (SS) restarts.
Resolution: This issue has been fixed and the duplicate RTM_TestHost models are not created after SpectroSERVER (SS) restart.
(10.3.1, DE378256, 01105046)
Symptom: Secondary SpectroSERVER crashes after an online backup.
Resolution: This issue is fixed and the secondary SpectroSERVER does not crash after an online backup.
(10.3.1, DE382107, 01007469)
Symptom: SpectroSERVER crashes when a REST call which contains an integer type attribute is used with < has-prefix > , < does-not-have-prefix > , < has-suffix > or < does-not-have-suffix > tag.
Resolution: SpectroSERVER does not crash when a REST call which contains an integer type attribute is used with < has-prefix > , < does-not-have-prefix > , < has-suffix > or < does-not-have-suffix > tag.
(10.3.1, DE383034, 01171069)
Symptom: SpectroSERVER crashes due to memory growth.
Resolution: The memory issue for SNMPv3 has been fixed.
(10.3.1, DE383903, 01181959)
Symptom: SpectroSERVER may run into a performance issue when it retrieves a huge number of alarms with Alarm filters.
Resolution: This issue has been fixed and SpectroSERVER does not run into performance issues when it retrieves huge number of alarms with Alarm filters.
(10.3.1, DE385840, 01195667)
Symptom: The SpectroSERVER may run into performance issues when a correlation condition is used.
Resolution: This issue is fixed, and the SpectroSERVER does not run into performance issues when a correlation condition is used.
(10.3.1, DE387545, 01206152)
Fixes to SNMP
Symptom:After upgrading to 10.3.1, the already existing dangling links in the container's peer linklist are not removed.
Resolution: Performed a major overhaul of SNMP subsystem, which is designed to improve efficiency and stability.
(10.3.1, DE396329, DE368279, 00992313)
Symptom: Devices with the Network_Address attribute set to 0.0.0.0 or <empty> do not raise an alarm as expected during the steady-state but raises an alarm during the start state. This causes ghost alarms to appear during an FT alarm synchronization.
Resolution: SNMP and ICMP-based models have been extended with new intelligence to pre-validate changes to Network_Address attribute, blocking changes to invalidate addresses.
(10.3.1, DE340311, 00925224)
Fixes to OneClick
Symptom: In the OneClick console, if the user tries to edit the font from the Topology preferences and cancels the changes, the updates are not canceled but saved.
Resolution: Clicking the Cancel button after editing the font, behaves as expected and discards the changes in the OneClick preferences tab.
(10.3.1, DE271939, 00643109)
Fixes to SDC
Symptom: Secure Domain Connector (SDC) creates invalid alarms when under heavy load (hundreds of requests creating hundreds of threads).
Resolution: The SDC is re-architected to efficiently manage high volumes of SNMP requests using only a few native threads.
(10.3.1, DE345502, 00788951)
Fixes to WLC
Symptom: Access Points do not migrate to the correct the WLC if there is HA that is configured.
Resolution: This issue has been fixed, and the access points migrate to the correct WLC if there is HA that is configured.
(10.3.1, DE368271, 01069297)
Fixes to Alarm and Events
Symptom: Event Export was not RFC complaint.
Resolution: Debug patch contains potential fix to make the event export text RFC compliant.
(10.3.1, DE371941, 01124676)
Symptom: Operator users are able to "Snooze Alarms for all Users" option.
Resolution: "Snooze alarms for all Users” option is enabled only for Administrator users.
(10.3.1, DE377432, 01145271)
Symptom: Link down alarms are not processed correctly on the interfaces from TrapX when the object instance ID is large.
Resolution: Link down alarm are processed correctly from the TrapX even when the object instance ID is large.
(10.3.1, DE384905, 01185223)
Symptom: When the SystemEDGE is running the Traps are not processed by Spectrum.
Resolution: Traps are processed by Spectrum when the SystemEDGE is running.
(10.3.1, DE387419, 01205174)
Symptom: Service status does not go down after a fallback to primary when the device is made to go down.
Resolution: Service status now goes down after a fallback to primary when the device is made to go down.
(10.3.1, DE371907, 01111190)
Symptom: Spectrum generates false 'module removal detected alarm on some modules.
Resolution: This issue has been fixed and Spectrum does not generate false 'module removal detected' alarm on modules.
(10.3.1, DE369146, 01105303)
Fixes to WebClient
Symptom: In the Japanese OS, Alarm details are not displayed in the WebClient.
Resolution: In the Japanese locale WebClient Alarm details are not rendered properly because WebClient is not internalized, so changing the locale by default to English, with this change Alarm Details are shown in English in the Japanese locale.
(10.3.1, DE383547, 01179675)
Symptom: The WebClient does not show the alarm filters saved in 0x12a7f attribute of the GlobalConfig model.
Resolution: As part of the fix, the alarm filters are fetched from 0x12a7f attribute of the GlobalConfig model if the alarm filters are not present in the user model.
(10.3.1, DE383824, 01176652)
Symptom: SLA threshold values for many SLAs are wrongly displayed as 10 seconds.
Resolution: SLA threshold values for SLAs are now displayed correctly.
(10.3.1, DE378901, 01154802)
Symptom: Migration of DataCenter to different landscape moves the wrong DataCenter in case of different vCenters that have data centers with the same name.
Resolution: Migration of DataCenter to different landscape moves the correct DataCenter even if different vCenters that have data centers with the same name.
(10.3.1, DE381186, 01167708)
Symptom: Archmgr memory grows over time due to an ever increasing event queue.
Resolution: Archmgr memory will not grow over time due to an ever increasing event queue.
(10.3.1, DE381213, 01169235)
Symptom: Chassis modules are not created if there is empty entAliasMappingIdentifier data.
Resolution: A new.
vnmrc flag/optionis introduced for ForceChassisModuleModel that enables the use of creating chassis modules in case the entAliasMappingIdentifier OID data is not available in the device. This functionality is disabled by default, setting the ForceChassisModuleModel=TRUE in ".vnmrc" file enables it. In this case Spectrum creates the chassis modules under the chassis manager, and not creating chassis modules under the device interface tab (entAliasMappingIdentifier data is required for creating chassis module mapping under interface tab).
(10.3.1, DE381645, 01143801)
Symptom: Policies are not added to the global collection (GC).
Resolution: This issue is fixed and now the non- MLS policy gets added to the GC in the OC view.
(10.3.1, DE381724, 01137512)
Symptom: MOT values are incorrect in the Service Manager Reports.
Resolution: MOT values are displayed and calculated properly in the Service Manager Reports.
(10.3.1, DE381967, 01173907)
Symptom: Billing executable is not included on the Spectrum Linux platform.
Resolution: Build and ship billing executable is included now for Linux.
(10.3.1, DE384817, 01177731)
Symptom: After Spectrum v.10.3 InnoDB database migration, ddm_load and ddm_save backup consumes a lot of disk space during execution.
Resolution: The ddm_save and ddm_load tools processing has been optimized to consume less disk space during execution.
(10.3.1, DE389839, 01217361)
Symptom: The Service Manager does not show the incorrect state change after installing 10.3.0 BMP01.
Resolution: The Service Manager shows the correct state change.
(10.3.1, DE395497, 01249415)
Symptom: Invalid character in "processd.pl" script does not allow running script.
Resolution: The invalid character in "processd.pl" script, allows running script.
(10.3.1, DE396463, 01254404)
Symptom: The offending value is minor while the service health is down.
Resolution: The offending value is not shown as minor when the service health is down.
(10.3.1, DE336915, 00921151)
Symptom: Spectrum is not able to render the firmware version correctly for the Fortinet device type.
Resolution: This issue has been fixed and Spectrum will correctly render the firmware version for the Fortinet device type.
(10.3.1, DE370205, 01115826)
Symptom: There is an expected email error, after upgrading to the Spectrum 10.2.1. Whenever an email is sent the following OneClick error message is displayed 'java.lang.IllegalStateException: Can't overwrite cause with com.sun.mail.smtp.SMTPSenderFailedException: 553 5.5.4 ... Domain name required for sender address'.
Resolution: This issue is fixed and the mail is being sent successfully after the changes.
(10.3.1, DE312812, 00804515)
Symptom: The NetApp Cluster is modeled to Modeltype_Name GnSNMPDev. On the Model type there is no Interface data (No IH handler) that is, identifiable data is empty in the mib tool and on clicking the Interface tab, 'The model has no Inferface' message is displayed.
Resolution: The NetApp Cluster Model type is modeled correctly as Modeltype_Name NetAppONTAPDev. The Model type Interface data reads from the property mib ie. 184.108.40.206.4.1.7220.127.116.11.2 and on clicking the Interface tab, the Interface data is displayed.