Bi-Monthly Patches (BMPs) on 10.2.3

Bi-Monthly Patch(BMP) is a bundle of PTF patches available on top of a Spectrum GA-release.
Spectrum
BMPs are released every two months on a regular basis.
Spectrum
Bi-Monthly Packs are self-extracting install files for each of the supported operating systems.
casp102
Bi-Monthly Patch(BMP) is a bundle of PTF patches available on top of a Spectrum GA-release.
Spectrum
BMPs are released every two months on a regular basis.
Spectrum
Bi-Monthly Packs are self-extracting install files for each of the supported operating systems.
The BMP must be installed on both the SpectroSERVER and OneClick server. For installation and uninstall instructions, refer to the Release Notes of the BMP.
The Spectrum 10.2.3_BMP_10.2.303 can be downloaded for Windows and for Linux machines.
The following are the list of BMPs available on top of
Spectrum
10.2.3:
10.2.3_BMP_10.2.304
The
10.2.3_BMP_10.2.304
includes the
10.2.3_BMP_10.2.303
fixes and other fixes for the following defects. The
10.2.3_BMP_10.2.304
includes the fixes for the following defects:
Defect
Symptom and Resolution
DE435371
Symptom:
While trying to create a user with a password, it is getting failed with landscape invalid exception.
Resolution:
Instead of converting the password to octet string, saving the encrypted password directing in attributes of the user.
DE429385
Symptom:
Spectrum
is generating false "module removal detected" alarm on some modules.
Resolution:
Code changes are made to not generate false "module removal detected" alarm on modules.
DE368190
Symptom:
SpectroSERVER is crashing while reading the empty physical serial number for a device.
Resolution:
Code changes are made to fix the SpectroSERVER crash issue while reading the empty physical serial number for a device.
DE419925
Symptom:
When the same attribute ID is used for the two SD attributes, values are getting shuffled between attributes.
Resolution:
Code changes are made to remove the duplicates while querying and reading from the model.
DE422876
Symptom:
Spectrum
was not syncing events from CAPC due to the ArrayIndexOutOfBoundsExceptions in tomcat logs.
Resolution:
Code changes are made to enable sync of the events successfully from CAPC without any exceptions being reported.
DE421942
Symptom:
Resolution:
DE417938
Symptom
: SpectroSERVER Crashes when a huge REST query receives from the OneClick server.
Resolution
: SpectroSERVER does not crash and shows an
Error.SearchQueryCombinationsExceedStackProcessingSize
error to OneClick server when huge REST query receives.
DE447467
Symptom
: Locator Search when using a list containing more than 250 items returns an error.
Resolution
: Locator Search is working fine after refining search criteria filtering at the OneClick server.
DE411321
Symptom:
DC Migration list and VCDCDomainList attribute of UIM Manager are empty.
Resolution:
Now
Spectrum
re-populate the DC list in the next VM sync. Additional checks stop two syncs running at the same time and overriding the dc list.
DE417925
Symptom:
After migration of the data center of a vCenter, the new data center which is received in the next sync is modeled under vCenter of the migrated landscape.
Resolution:
Spectrum
now models the migrated data center which is received in next sync in its original landscape.
DE417473
Symptom:
Connections in the Topology views between containers and devices which have no logical or physical connection.
Resolution:
Connections are properly shown in the Topology views between containers and devices.
DE446737
Symptom:
Export Preferences from Group to Group is not successful.
Resolution:
Code changes are made to fix the issue.
DE439342
Symptom:
A huge number of Management lost alarms seen on SNMP devices in the OneClick client.
Resolution:
Code changes are made to hide Management lost alarms on SNMP devices in OneClick client.
DE407743
Symptom:
The trap is not getting forwarded to remote models with RMonApp.
Resolution:
Code changes are made to forward the Trap to remote models with RMonApp.
10.2.3_BMP_10.2.303
The
10.2.3_BMP_10.2.303
includes the
10.2.3_BMP_10.2.302
fixes and other fixes for the following defects. The
10.2.3_BMP_10.2.303
includes the fixes for the following defects:
Defect
Symptom and Resolution
DE399894
Symptom:
Customizations or any changes that are made to the event in the OneClick Event Configuration editor does not get saved or updated to the EventDisp file.
Resolution:
Changes to the event is saved to the EventDisp file.
DE403882
Symptom:
Primary MLS has a high memory growth when the trap director is enabled.
Resolution:
Memory leak does not occur when the trap director is enabled, during the trap process.
DE403330
Symptom:
Jars that are signed with expired certificate do not run post certificate expiry date.
Resolution:
All jars that are signed with a new certificate run as expected.
DE396290
Symptom:
The authentication request goes to the LDAP server instead of
Spectrum
, for local
Spectrum
users.
Resolution:
Spectrum
local users are authenticated first with
Spectrum
and not the LDAP server.
DE401365
Symptom:
SpectroSERVER crashes when parsing the regular expression.
Resolution:
This issue has been fixed, and the SpectroSERVER does not crash when parsing the regular expression.
DE376099
Symptom:
NCM configuration buckets count increase and the processing are stopped with an error while parsing the event vardata.
Resolution:
All NCM configuration buckets are processed by skipping the corrupted event, having null values for the current, and previous MH.
DE404574
Symptom:
Jasper assets report displays incorrect or negative values for 'Idle Days' list.
Resolution:
Jasper assets report displays correct values for 'Idle Days' list.
DE397289
Symptom:
TopN event group reports display wrong event count and displays the correct event counts for the subreport.
Resolution:
This issue has been fixed, and the TopN event group reports display correct event count as the subreport event count.
DE404003
Symptom:
The disk space is not released for the old event table partitions on the SRM server.
Resolution:
The disk space is released for the old event table partitions on the SRM server.
DE399262
Symptom:
Jasper Spectrum Overview Dashboard does not populate data when LDAP is enabled in the OneClick Server.
Resolution:
This issue has been fixed, and the Jasper Spectrum Overview Dashboard now populates data when LDAP is enabled in the OneClick Server.
DE409228
Symptom:
Records of the 'Current Port Details - Group' Jasper report when exported to Excel, does not appear in a single line if the port available value is 'Yes'.
Resolution:
This issue has been fixed, and the records of the 'Current Port Details - Group' Jasper report when exported to Excel, appears in a single line, if port available value is 'Yes'.
DE353002
Symptom:
The Interface Tab does not reflect the information for devices and ports connected.
Resolution:
In case the required information is not updated automatically, then by selecting the refresh button on the interface tab, all the details for the device and port that is connected are updated.
DE404880
Symptom:
The secondary SpectroSERVER crashes after an online backup.
Resolution:
The secondary SpectroSERVER does not crash due to the ICMP Tests.
DE403246
Symptom:
When issuing a REST GET models request, with a list of external attribute parameters, a Null Pointer Exception is returned.
Resolution:
REST GET models request with a list of external attributes parameters returns successfully.
DE394960
Symptom:
SpectroSERVER crashes after while writing attributes with over 4MB value.
Resolution:
Handled writing of attributes with more than 4MB, preventing further crashes.
DE394306
Symptom:
Multiple datacenters cannot be migrated at same time.
Resolution:
Multiple datacenter migrations is done for
Spectrum
UIM integration via RESTful web services.
DE349697
Symptom:
Defects include: Inventory Sync with UIM takes long, the OLB hangs and the UIM Alarms are asserted on the event model instead of the device model.
Resolution:
Fixes for the defects that are mentioned above, are as follows:
1.Query for the configuration items process has changed. Now users can fetch the configuration items per vCenter instead of configuration IDs. This reduces the number of calls to NISAPI Probe, thus reducing the load on that probe.
2. From the logs, it was inferred that the ESX might be the culprit for the OLB to hang, because it is being polled. That part has been commented out, to see if this is actually the cause since this code has been there since the first iteration of this integration.
3. EventAdmin code has been changed to assert the alarms, based on the model name if the EventAdmin is unable to find the model based on IP.
DE406911
Symptom:
SpectroSERVER crashes in an SNMP packet processing area while comparing the string.
Resolution:
This issue has been fixed, and the SpectroSERVER does not crash while processing the SNMP received packet.
DE409077
Symptom:
Idle days are not populated when used as a fourth column in the Jasper report Current Port Assets.
Resolution:
This issue has been fixed and the Idle days is populated when used as a fourth column in the Jasper report Current Port Assets.
DE409025
Symptom:
Event titles are overlapped in the Jasper report 'Top-N Most Common Events-Group'.
Resolution:
This issue has been fixed and the Event titles do not overlap in the Jasper report 'Top-N Most Common Events-Group'.
DE398909
Symptom:
Jasper SSO does not work after redeploying.
Resolution:
This issue has been fixed, and Jasper SSO works after redeploying.
DE375989
Symptom:
Connections are not updated correctly in the OneClick view.
Resolution:
Changes in connections are updated in the OneClick view.
DE399117
Symptom:
There is huge thread count increase.
Resolution:
Threads are created only when the contact status is not equal to established, and threads wait to receive a message only once.
DE413196
Symptom:
Spectrum
filters VMs during V-Motion with typename 'Computer System', but VMware sends it is as 'VM', causing V-Motion to fail.
Resolution:
typenames "VirtualSystem" and "VM" were added to fix this issue and
Spectrum
now filters VMs during V-Motion with the typename "ComputerSystem" and "VirtualSystem" and "VM".
10.2.3_BMP_10.2.302
The BMP must be installed on both the SpectroSERVER and OneClick server. The Spectrum 10.2.3_BMP_10.2.302 can be downloaded here. For installation and uninstall instructions, refer to the Release Notes of the BMP.
The
10.2.3_BMP_10.2.302
includes the
10.2.3_BMP_10.2.301
fixes and other fixes for the following defects. The
10.2.3_BMP_10.2.302
includes the fixes for the following defects:
Defect
Symptom and Resolution
DE368409
Symptom:
Watch status error text is garbled.
Resolution:
Junk error messages which were returned when evaluating the watch expression, is now rectified and only the defined error messages are displayed.
DE356653
Symptom:
The sysUpTime attribute rolls over in 495 days or gives inconsistent values, and so a false reboot alarm is generated.
Resolution:
If the sysUpTime is reset and based on the snmpEngineTime it is decided whether there was an actual reboot or not.
Symptom:
An http unauthorized response is received while launching the alarm view in CAPM.
Resolution:
An http authorization is now successful when launching the alarm view in CAPM.
Symptom:
Migration of DataCenter to different landscapes moves the wrong DataCenter in case if different vCenters having data centers with the same name.
Resolution:
Migration of DataCenter to different landscapes moves the correct DataCenter even if different vCenters having data centers with the same name.
Symptom:
MOT values are incorrect in the Service manager reports.
Resolution:
MOT values are displayed and calculated appropriately.
Symptom:
Alarm Top N reports that are run by selecting cause code and not by the alarm title.
Resolution:
Two new controls to Use and Select cause code to run the Top N alarm reports.
Symptom:
Users get a sync from Spectrum after redeploying, even when LDAP is configured in JasperServer.
Resolution:
Users now only get a sync from Spectrum to JasperServer during redeployment.
Symptom:
A security string check takes time while loading the Input control parameters report.
Resolution:
This security string check has been removed.
Symptom:
JasperServer 6.4.2 dashboards do not run properly in Spectrum 10.2.3.
Resolution:
This issue has been fixed and the dashboards and reports run properly on JasperServer 6.4.2 with Spectrum 10.2.3.
Symptom:
In the Alarm Details Report, the alarm condition and the landscape names are not displayed correctly.
Resolution:
With this fix, the alarm condition and landscape names display correctly in Alarm details report.
Symptom:
There are missing IP addresses for Viptela device interfaces.
Resolution:
Viptela device IP addresses for interfaces, CPU, and memory performance graphs are populated.
Symptom:
Fix required to handle one of their use case where an alarm can be raised on the system Edge with the given format.
Resolution:
Changes have been made to
ensure that an alarm can be raised on the system Edge, once the domain name is passed, following the date and time regarding the defined format.
Symptom:
SpectroSERVER crashes while importing a specific XML file.
Resolution:
SpectroSERVER does not crash after the fix.
Symptom:
In the availability report (drill down) there is a wrong calculation on down time.
Resolution:
The down time calculation in availability(drill down) report is now corrected.
Symptom:
After integrating Jasper 6.4.3 with Spectrum 10.2.3, database connection details fail to update.
Resolution:
This issue has been fixed, after integrating Jasper 6.4.3 with spectrum 10.2.3 database connection details update correctly.
Symptom:
ModelType BrocadeNos sets attribute modelclass to SNMP.
Resolution:
Devices are modeled as a switch instead of an SNMP.
Symptom:
The Mac address of a device is not populated in Spectrum due to a database corruption.
Resolution:
An action to evaluate and populate the Mac address in Spectrum was provided.
Symptom:
Service Alarms are not generated in the Services correctly in some specific cases.
Resolution:
When a Service is down, the Service Alarms are generated correctly.
Symptom:
Creating events using REST APIs does not work for custom events with varbandids greater than 9.
Resolution:
Necessary changes are made to get the event creation REST API working.
Symptom:
While creating custom events with varbandids greater than 9, the event details using REST APIs do not show properly.
Resolution:
Necessary changes are made not to convert decimal values to hexadecimal while processing the event creation request.
Symptom:
Spectrum stops monitoring the devices once a while due to incorrect SNMPv3 boot value.
Resolution:
Spectrum updates SNMPv3 cache with the boot value from Device response, and sends the correct boot value.
The following defects have been fixed:
DE371971 - deviceType parameter should start with lowercase d in configFile of SpectrumDataPublisher.
DE371975 - SpectrumDataPublisher - java heap error when querying Elastic search (Elasticsearch dependency removal).
DE371820 - Spectrum data publisher 500 http error.
DE394767
Symptom:
Spectrum maps the extended fault correlation domain to the wrong policy.
Resolution:
Spectrum does not map the extended fault correlation domain to the wrong policy.
DE395701
Symptom:
SpectroSERVER crashes while deleting the SDC managed SNMPv3 device.
Resolution:
SpectroSERVER does not crash when deleting the SDC-managed SNMPv3 device.