Software Advisory Notice
Dear Cisco Customer,
Cisco has identified software issues with the release that you have selected that may affect your use of this software. Review this Software Advisory notice to determine if the issues apply to your environment. If these issues are applicable, upgrade or apply the patch release specified in the "Software solution – Fixed software version" column in the table below.
For more comprehensive information about what is included in this software, refer to the Cisco software Release Notes, available from the Product Selector tool. From this page, choose the product in which you are interested. The Release Notes are under "General Information" on the product page.
| Affected Software and Replacement Solution for CSCvj03179, CSCvn37738, CSCvn46417, CSCvn54430, and CSCvn56472 |
||
| Bug ID |
Software Affected Versions |
Software Solution Fixed Software versions |
| CSCvn30664
|
2.3.1, 3.1.1.53 |
Patch release 3.1.1.54 |
| CSCvn37738, CSCvn54430, CSCvn56472 |
3.1.1.53, 3.1.1.54 |
Patch release 3.1.1.55 |
| CSCvn46417 |
2.0, 2.1, 2.2, 2.3.1, 3.1.1.53, 3.1.1.54 |
Patch releases 2.3.1.53 and 3.1.1.55 |
Reason for Advisory:
This software advisory addresses five software issues.
Affected Software:
Cisco Tetration Software Release version mentioned in the above table.
Bug CSCvn30664
| Issue Description |
The sensor ID for a given Cisco Tetration agent is generated by the Cisco Tetration backend service using a combination of the hostname and system UUID. A recent change in the dmidecode command [1], which was called by the agent to get the system UUID, now causes the system UUID to get returned in lowercase (the UUID was previously returned in uppercase). This change results in a different sensor ID for the same running agent.
If you have a Cisco Tetration agent and you upgraded the dmidecode command, you will see duplicate agent entries in the Cisco Tetration UI for a given host.
This issue has been observed with an upgrade from the RHEL 7.5 release to the 7.6 release, but can be seen with any distribution that contains this dmidecode command being upgraded from an older version to version 3.1 or later. |
| Conditions |
You can observe this issue if you upgrade the Linux host to a version that contains the updated dmidecode (version 3.1 or later) package and restart the existing agent or reboot the host.
Alternately, upgraded dmidecode to version 3.1 or newer from an older version without upgrading the system OS. |
| Workaround |
Do not upgrade the dmidecode package to 3.1 or later and do not upgrade the system to the new Linux version that contains the dmidecode package 3.1 or later until Cisco Tetration contains a fix.
Support for the 3.1 or later dmidecode package is available in the Cisco Tetration 3.1.1.54 patch release. Disable the Cisco Tetration agent auto-upgrade until you update your Cisco Tetration cluster to the 3.1.1.54 release. |
Bug CSCvn37738
| Issue Description |
The Cisco Tetration agent MSI installer uses Microsoft Windows Installer services to perform installations during upgrades. If the installer encounters a file from a previous agent installation that it cannot overwrite or remove, the installer will queue this file and request a reboot from the OS.
In the 3.1.1.53 release, this issue will trigger a reboot immediately. With the 3.1.1.54 release, this issue will prevent the reboot, but the files will still be pending and waiting for a manual reboot.
With the 3.1.1.54 release, this pending reboot can lead to mixed code running in the environment if the files queued for replacement by the Microsoft Windows Installer are executables. If the system is manually rebooted, the installation will finish, the pending files will be copied, and the agent will be fully running on the updated code. |
| Conditions |
You can observe this issue if a file in the Cisco Tetration installation folder is locked as read-only by third party software, such as an anti-virus software. In this situation, the file cannot be replaced or removed during an upgrade from an older sensor release to the 3.1.1.53 or 3.1.1.54 sensor release when you use the Cisco Tetration GUI. |
| Workaround |
Disable the Microsoft Windows agent auto-upgrade while upgrading to the 3.1.1.53 release, and only upgrade after the fix is available in the 3.1.1.55 release.
For 3.1.1.54 release sensor installations, you should search the "Cisco Tetration" folder for the existence of *.tmp files. If a .tmp file exists, the sensor might not be fully installed and a server reboot is pending. You can verify this in the Event Viewer as well by looking under Windows Logs > Application and searching for event 1029 from the "Msiinstaller" source. The event message is as follows:
Product: Cisco Tetration Agent. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. |
Bug CSCvn46417
| Issue Description |
Cisco Tetration is impacted with a Hadoop bug in which inodes and blocks are leaked with certain APIs. These leaked inodes and blocks accumulate over time and cause slowness in the cluster. |
| Conditions |
You can observe this issue on clusters that have been running longer than 3 months and the total blocks count is higher than the total files count by more than 10 million in the HDFS monitoring dashboard. Use the following procedure to check the total blocks count and total files count in Hawkeye:
1. Under the main GUI, choose Monitoring. 2. Click on Hawkeye [Charts]. 3. Choose the "HDFS monitoring" dashboard. |
| Workaround |
If you are using the 3.1.1.53 or 3.1.1.54 release, upgrade to the 3.1.1.55 patch release.
If you are on a 2.3.1 release, upgrade to the 2.3.1.53 patch release. |
Bug CSCvn54430
| Issue Description |
The Cisco Tetration agent MSI installer uses the Microsoft Windows Installer services to perform installations during upgrades. If WinPcap already exists in the system, the installer cancels the installation and prints the following error:
MSI (s) (E4:5C) [02:53:50:004]: Product: Cisco Tetration Agent -- WinPcap found, please uninstall WinPcap first before continue
In the Cisco Tetration 2.3.1 releases, the installation does not abort when detecting WinPcap. Instead, Npcap will be installed regardless. |
| Conditions |
You can observe this issue if WinPcap is already installed on the system when you install the Cisco Tetration agent MSI. |
| Workaround |
If WinPcap is not required by any applications, you can manually uninstall WinPcap and retry the Cisco Tetration agent installation.
Otherwise, if WinPcap is required, then Cisco recommends that you wait for the fix that will be in the Cisco Tetration 3.1.1.55 release. The fix installs Npcap in WinPcap compatible mode, which enables the installation to succeed. |
Bug CSCvn56472
| Issue Description |
In the Microsoft Windows installer script (in powershell), the Out-File cmdlet writes to the user.cfg file in Unicode encoding by default. This could prevent some scripts, such as fetch_sensor_id.cmd, from being able to read the user.cfg file. This issue prevents the agent from registering with the Cisco Tetration cluster. |
| Conditions |
You can observed this issue you install the agent with the PowerShell installer script for Microsoft Windows from the Software Agent Download page and the agent has not registered with the cluster. |
| Workaround |
Open the user.cfg file in the "C:\Program Files\Cisco Tetration" folder with notepad.exe and Save-As ANSI format with the same filename to overwrite the Unicode version. Re-run the fetch_sensor_id.cmd batch file as an administrator to register the sensor.
This issue will be fixed in the 3.1.1.55 patch release. Until the patch is available, disable the Microsoft Windows Cisco Tetration agent auto upgrade or follow the above workaround. |