NetOps Spectrum 10.3.1 Patch List
search cancel

NetOps Spectrum 10.3.1 Patch List


Article ID: 192836


Updated On:


CA Spectrum DX NetOps


Below is a current list of Spectrum 10.3.1 patches. This list is updated bi-weekly to include any new patches released for this GA product release.


NetOps Spectrum 10.3.1



Symptom: Username is shown incorrectly for added and removed Global Collections.
Resolution: Username is shown properly for added and removed Global Collections.


Symptom: Performance issues such as high memory utilization with VNA integration. 
Resolution: Changes for the VNA 3.6.4 integration are now incorporated to resolve performance issues.


Symptom: Overlapping IP addresses of ESX Hosts in different VNA User Domains are incorrectly reconciled. 
Resolution: When ESX Hosts are created we now consider it's IP address and SDC name as parameters. This is also now considered during reconciliation.


Symptom: Empty trunk port models are causing vLan port list to grow at a high rate.
Resolution: vLAN port list will longer grow due to empty trunk port models.


Symptom: CAPM Events will not sync to Spectrum. The Spectrum tomcat log will display an ArrayIndexOutOfBoundsException. 
Resolution: CAPM Events will be synced to Spectrum properly.


Symptom: SpectroSERVER does not start with owner under Suse Linux due to linux capabilities. 
Resolution: SpectroSERVER will now start without capabilities in Suse Linux.


Symptom: After a device reconfiguration, duplicate stale modules still exist in the Interface Tab even after PortAgeOutTime expires. 
Resolution: Duplicate stale modules will be removed once the PortAgeOutTime expires.


Symptom: Jar files signed with expired certificates will not run after expiration. 
Resolution: All jar files will be signed with new certificate and they will run as expected.


Symptom: Jasper Spectrum Overview Dashboard does not populate data when LDAP is enabled with OneClick Server.
Resolution: Jasper Spectrum Overview Dashboard will populate data when LDAP is enabled with OneClick Server.


Symptom: Tomcat log is filling up with the following debug statement: "ERROR: Attribute 0x10024 does not exist in the attrColumnMap."
Resolution: Tomcat log will no longer show "ERROR: Attribute 0x10024 does not exist in the attrColumnMap."


Symptom: Spectrum and CAPM Full Sync takes hours to complete.
Resolution: Spectrum and CAPM Full Sync performance improvements.


Symptom: Threading issue with the SpectroSERVER causes a SpectroSERVER crash.
Resolution: Code change has been made so the SpectroSERVER will no longer crash.

Additional Information

If you would like to request any of the above patches, please open an issue with Spectrum support and upload the contents of your <SPECROOT>/Install-Tools/.history file from both the SpectroSERVER and OneClick Server. Support will review this information to ensure that the patch you are requesting will not conflict with any patches you have already installed.