| ID |
Details |
Customer Case |
| 15487 |
Problem: In BMC Atrium Discovery, versions 8.2, 8.2.01, 8.2.02, 8.2.03, 8.2.04, 8.3, and 8.3 SP1, the OS string for some versions of Oracle Enterprise Linux operating system (OS) are not displayed completely. For example, the OS string might be displayed as Enterprise Linux Enterprise.
Workaround: To resolve this problem, you must perform the following actions:
- In the getDeviceInfo Shell scripts for the Linux platform, copy the following section of the script:
- Paste the copied script below the os="" string as follows:
- Delete the section of the script from its previous location and save the updated getDeviceInfo Shell script.
- Install the January, 2012 TKU and Extended Data Pack or later.
- Run BMC Atrium Discovery again.
The OS version along with the complete OS String is discovered.
|
ISS03859019, ISS03863834 |
| 15400 |
Problem: A failure during Dynamic Dip database discovery results in an IntegrationResult with a node as an attribute. The following error is displayed on the scanning appliance: "Unexpected exception while sending data to the consolidation appliance". Workaround: For versions earlier than 8.3.1, contact Customer Support for a workaround to the problem with how BMC Atrium Discovery sends data created by the pattern to the consolidator. A pattern that sets the value of an attribute to be a node can cause this error. For example:
|
|
| 15302 |
Problem: The OS classifier identifies all variants (Novell SUSE Linux Enterprise Server (9.0 - 11.0), SUSE Linux Enterprise Server (v11 onwards), and OpenSUSE) of SUSE Linux as 'SUSE Linux'.
Workaround: None. |
|
| 15254 |
Problem: In the Collaborative Application Mapping (CAM) user interface, using a named value that has a list in the results results in a traceback.
Workaround: None. |
|
| 15247 |
Problem: The query builder "show all/show fewer" links are not always visible in Internet Explorer 6.
Workaround: None. |
|
| 15231 |
Problem: The wiki markup in the CAM text editor does not render correctly in the PDFs.
Workaround: None. |
|
| 15218 |
Problem: If you have viewed a chart from results obtained using the query builder, using the back button does not work correctly.
Workaround: None. |
|
| 15213 |
Problem: The query builder does not show any attributes if nodekind instances are not present in the datastore.
Workaround: None. |
|
| 15208 |
Problem: AD Proxy shows the confusing log reference of <no username> in logs. *Workaround:* None. |
QM001720259 |
| 15207 |
Problem: TRANSIENT_CallTimedOut errors occur when SNMP discovery attempts to scan some very complex network devices. *Workaround:* None. |
|
| 15169 |
Problem: Attempting to discover a host server running version 2.5 of the optional MainView for WebSphere Application Server product results in the script failure "message View 49Z not available", and no WebSphere Discovered Application Components are created, preventing extended discovery. Workaround: None. |
|
| 15158 |
Problem: Instrument the scanning appliance to capture unexpected exceptions while sending data to the consolidator. *Workaround:* None. |
QM001718958 |
| 15106 |
Problem: When the IP list for a host changed dramatically, on the consolidator no Endpoint Identity was created. Workaround: None. |
|
| 15077 |
Problem: The user interface displays a "The appliance is having technical difficulties with this page" error if you add a login credential that includes a control character ASCII 0-31.
Workaround: None. |
|
| 15003 |
Problem: Processor sync mapping to CMDB (CMDB.Host_processor) does not support PowerPC 6 and 7 for BMC_Processor.ProcessorFamily. Workaround: None. |
ISS03780851 |
| 14968 |
Problem: In the query builder, a condition that matches a string containing a tab character results in messages such as Unknown string qualifier at 'u' on line 1. The same is true for defining functional components.
Workaround: None. |
|
| 14951 |
Problem: On high speed interfaces such as 10Gb/s, ifHighSpeed is not read, instead the value for raw_speed is shown in PortInterfaces. This is usually 4294.967295 Mb/s or similar.
Workaround: None. |
|
| 14939 |
Problem: The visualization and PDF report fail when a host with a Japanese name is included.
Workaround: None. |
|
| 14925 |
Problem: The vendor of a Fujitsu machine is erroneously reported as "Sun Microsystems". Workaround: None. |
|
| 14681 |
Problem: Cannot move proxy pools with spaces in their names using actions menu.
Workaround: None. |
|
| 14570 |
Problem: Person nodes do not have a key. As a result you get incorrect results updating Person in TPL. Workaround: Specify an explicit key in your pattern. |
ISS03643235 |
| 14555 |
Problem: "ksh[n]: tw_report: not found" appended to the output of many Discovered results for Solaris 10. Workaround: Set force subshell = True for that login credential. |
ISS03729494 |
| 14377 |
Problem: Sometimes, an error message "page cannot be displayed" is displayed in the UI when trying to restore a snapshot. Workaround: Retry the operation. |
ISS03678094 |
| 14376 |
Problem: When taking a snapshot, a popup error message may be displayed: "The feature is locked by your session at ..." Workaround: Retry the operation. |
ISS03678094 |
| 14365 |
Problem: Discovery Starttime shown on consolidation server shows UTC time when discovery and consolidation servers are localized. Workaround: None. |
ISS03708973 |
| 14245 |
Problem: CMDB sync error on service start after tw_model_init. Workaround: Restart the services. |
|
| 14227 |
Problem: When millions of DAs nodes are generated from darkspaces scan, the VA can become so slow you cannot login. Workaround: Run the tw_remove_darkspace script. |
ISS03704879 |
| 13963 |
Problem: TCPvcon cannot be pushed to Windows 2000 hosts. Workaround: Deploy the utility manually. |
|
| 13950 |
Problem: Only the maximum speed is discovered for multiple processor hosts. Workaround: None. |
ISS03603147 |
| 13881 |
Problem: When saving queries in the Reports Builder, if you specify a name that already exists, the save button is disabled, though no reason for this is shown in the user interface.
Workaround: None. |
|
| 13801 |
Problem: Cannot generate a bar graph for a scan whose name contains an apostrophe. Workaround: None. |
ISS03668576 |
| 13736 |
Problem: Misleading error when incorrect Microsoft SQL Server JDBC Driver is used. Workaround: None. |
ISS03589069 |
| 13583 |
Problem: On the Discovery Home page the Recent Runs tab does not show any discovery runs resulting from topology runs. These discovery runs are however shown in the Discovery Status panel on the Home page. BMC Atrium Discovery version 8.3 introduces Edge Connectivity discovery as a replacement for the network topology feature that was introduced in BMC Atrium Discovery 8.2.
Workaround: None. |
|
| 12827 |
Problem: Visualizations only print in hierarchical view. Workaround: None. |
23334 |
| 12700 |
Problem: The PROCESSWITH ordering in the search and reporting service is unreliable.
Workaround: None. |
|
| 12647 |
Problem: Consolidation stopped. Workaround: None. |
22943 |
| 12590 |
Problem: Upgrades from BMC Atrium Discovery 7.3 to 7.3.1 produce errors about discovery running. Workaround: None. |
22622 |
| 12534 |
Problem: Serial number not obtained on some Solaris/SPARC machines. Workaround: None. |
22536 |
| 12458 |
Problem: Wrong RAM reported by WMI against Windows 2008 Server VMs on Hyper-V. Workaround: None. |
ISS03812417 |
| 12445 |
Problem: Upgrade highlights changes to Windows discovery scripts when the content is unchanged. Workaround: None. |
22254 |
| 12405 |
Problem: Errors appear in ECA logs "Errors not related to a node". Workaround: None. |
ISS03752142 |
| 12403 |
Problem: Log rolling failure in Windows Proxy results in traceback. Workaround: None. |
21992 |
| 12385 * |
Problem: The datastore can crash when compacting the datastore using the new online compaction tool. Workaround: Although the crash does not corrupt data and the online compaction can be re-run and it will continue where it left off, it is recommended that you continue to use the offline compaction utility. |
|
| 12330 * |
Problem: When you have edited the graph-definition.txt file, you must restart the Tideway services to apply the changes. Workaround: None. |
|
| 12297 * |
Problem: If the "Only show working set in visualizations" menu option is used while viewing a visualization, the visualization does not always redraw correctly to honor the new option state. Workaround: Manually refresh the browser page. |
|
| 12296 * |
Problem: Hiding nodes in a visualization such that no nodes remain in the visualization can cause IE 6 to crash with the message "R6025 - pure virtual function call". Workaround: Do not hide all nodes in a visualization. |
|
| 12153 |
Problem: TRANSIENT_CallTimedout should be modified slightly for user display. Workaround: None. |
21758 |
| 12025 |
Problem: Discovery runs older than the ten most recent are not displayed well. Workaround: None. |
ISS03625937 |
| 11488 |
Problem: Discovery of a service processor results in creation of a host node. Workaround: None. |
16159 |
| 10738 |
Problem: Search cannot match non-UK characters, for example an umlaut ä. Workaround: None. |
13640 |
| 10737 |
Problem: TPL activation doesn't handle special characters well, for example a back tick. Workaround: None. |
13639 |
| 10521 |
Problem: When connecting to BMC Atrium Discovery via HTTPS using an alias hostname, you are prompted for verification. Workaround: None. |
|
| 10277 |
Problem: History comparison is unusable with more than a small number of entries. Workaround: None. |
8444 |
| 9317 |
Problem: Plain HTML shown after snapshot creation timeout. Workaround: None. |
ISS03690829 |
| 9179 * |
Problem: When doing an snmpGet in a pattern, it is possible that some SNMP agents for certain OIDs will return data for a different OID than the one requested. Because the OID for the data retrieved doesn't match the OID that the request was for, the corresponding attribute will not be set. Workaround: The mapping can be set to include the requested OID and the OID that will actually be returned. For example:
|
|
| 7848 * |
Problem: On Windows hosts there is overlap between what is returned as packages and what is returned as patches. The WMI getPackageList code retrieves everything that is uninstallable which will include all the patches. The pstools version does the same, but filters out hot fixes. • The data returned by getPackageList will be different depending on the access method used. • Duplicate Patch and Package nodes will be created, with potential impact on performance and disk usage. • Queries for patch/package information will have to be more complex or may return duplicate results. Workaround: None. |
|
| 3534 * |
Problem: An Appscan Auto test revealed several XSS vulnerabilities in the RelationshipSearch and ReleationshipMultisearch widgets. Workaround: None, though these have now been identified as false positives. |
|
| 3151, 4456. * |
Problem: When discovering Windows NT hosts with a Credential Windows proxy platform minimum specification, this Discovery fails although a valid credential is defined. The credential should be localhost\username. Workaround: Ensure that the credentials for these hosts are entered as localhost\username. This is not required for Credential Slaves released with BMC Atrium Discovery 8.2 and later as the Credential Slave adds "localhost\" to any unqualified username. In these examples, replace user name with the correct user name for Discovery. Customer Case Number: C5293. |
|