Cisco Crosswork Situation Manager 7.3.x Product Notices
(Powered by Moogsoft AIOps 7.3)
Table of Contents
Deprecation Notice: Google Authentication
Deprecation Notice: Logger Module
Deprecation Notice: SCOM Connector (Basic)
Deprecation Notice: Cookbook Fields
Deprecation Notice: Feedback, Prototype Release
Deprecation Notice: Template Matcher
Deprecation Notice: URL User Profile Images
End of Support Notice: Cisco Crosswork Situation Manager v5.2.0 and Prior
End of Support Notice: Cisco Crosswork Situation Manager v5.1.3 and Prior
Deprecation Notice: Legacy Dashboards
Deprecation Notice: Classic Sigaliser
End of Support Notice: Microsoft Internet Explorer 11
Deprecation Notice: JSON Filters
End of Support Notice: Cisco Crosswork Situation Manager v6.0 and Prior
End of Support Notice: Cisco Crosswork Situation Manager v6.1 and Prior
End of Support Notice: Cisco Crosswork Situation Manager v6.2 and Prior
End of Support Notice: Cisco Crosswork Situation Manager v6.3 and Prior
See Cisco Releases for information on Cisco releases, release dates, and links to version-specific documentation.
Date |
Notice |
October 4th, 2019 |
End of Support Notice: Cisco Crosswork Situation Manager v6.3 and Prior |
October 4th, 2019 |
End of Support Notice: Cisco Crosswork Situation Manager v6.2 and Prior |
October 4th, 2019 |
End of Support Notice: Cisco Crosswork Situation Manager v6.1 and Prior |
October 4th, 2019 |
End of Support Notice: Cisco Crosswork Situation Manager v6.0 and Prior |
October 4th, 2019 |
|
July 31st, 2019 |
|
May 31st, 2019 |
|
May 31st, 2019 |
|
April 30th, 2019 |
|
January 25th, 2019 |
|
October 27th, 2018 |
|
October 27th, 2018 |
|
October 27th, 2018 |
|
October 27th, 2018 |
|
October 4th, 2018 |
End of Support Notice: Cisco Crosswork Situation Manager v5.2.0 and Prior |
May 29th, 2018 |
|
May 20th, 2018 |
End of Support Notice: Cisco Crosswork Situation Manager v5.1.3 and Prior |
April 5th, 2018 |
|
March 16th, 2018 |
|
January 5th, 2018 |
Cisco offers the following types of Cisco Crosswork Situation Manager releases:
· Enterprise Stability Release (ESR) are planned once a quarter. An ESR is subject to extended internal testing in enterprise-like environments and conditions. It is intended for enterprise customers who value product stability and reliability over leading edge features.
· Occasionally we release a Beta Release. Each Beta Release is a feature-complete preview of an upcoming ESR that has not completed extended stability testing. Beta releases are not supported in production, but you can deploy one to a development or staging environment to prepare for an upcoming ESR.
For important notices about supported software deprecation and other changes see Product Notices.
Enterprise Stability Releases
ESR Releases are tested for an extended period of time and include all the features/bugfixes implemented in the incremental Edge Releases issued since the previous ESR.
· Cisco Crosswork Situation Manager /document/preview/112702#UUIDab76da819f99f5c7c29edb4549a26ebe released 4 October, 2019.v7.3.0
· Cisco Crosswork Situation Manager v7.2.0 released 30 April, 2019. Latest update: 7.2.0.6.
· Cisco Crosswork Situation Manager v7.1.0 released 25 January, 2019. Latest update: v7.1.0.7.
· Cisco Crosswork Situation Manager v7.0.0 released 4 October, 2018. Latest update: v7.0.1.9.
· Cisco Crosswork Situation Manager v6.5.0 released 20 June, 2018. Latest update: 6.5.0.10.
· Cisco Crosswork Situation Manager v6.4.0 released 16 March, 2018. Latest update 6.4.0.9.
· Cisco Crosswork Situation Manager v6.3.0 released 8 December, 2017.
· Cisco Crosswork Situation Manager v6.2.0 released 16 September, 2017.
· Cisco Crosswork Situation Manager v6.1.0 released 31 May, 2017.
· Cisco Crosswork Situation Manager v6.0.0 released 16 March, 2017.
Support for Google Authentication is deprecated beginning with Cisco Crosswork Situation Manager v7.0 and will no longer be supported in Cisco Crosswork Situation Manager v7.1.
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.1 or later.
You can enable and use Google Authentication with SAML.
Cisco is deprecating support for the Logger Module beginning with Cisco Crosswork Situation Manager v7.1.
The Logger module is replaced with Apache Log4j that allows for greater flexibility in logging configuration and the ability to dynamically change components' log levels.
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.1 or later.
Versions of Cisco Crosswork Situation Manager v7.1 or later.
Use the Apache Log4j logging utility. See Configure Logging for configuration details. Alternatively refer to the Apache Log4j documentation.Configure Logging
Cisco is deprecating support for the Nexus clustering algorithm beginning with Cisco Crosswork Situation Manager v7.3. [REVISED 8 May, 2019]
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.3 or later.
Versions of Cisco Crosswork Situation Manager up to and including v7.3.
Use the Cookbook clustering algorithm with a Vertex Entropy filter to cluster alerts based on the distance between nodes in your network topology.Cookbook
Cisco is deprecating support for Cisco Crosswork Situation Manager on Red Hat Enterprise Linux 6/CentOS 6 beginning with v6.3.1.
Support for RHEL 6/Centos 6 ends after the release of Cisco Crosswork Situation Manager v6.5.
Customers installing or upgrading to Cisco Crosswork Situation Manager v6.5.1 or later.
Versions of Cisco Crosswork Situation Manager up to and including v6.5 are supported on RHEL 6 or CentOS 6.
Install Cisco Crosswork Situation Manager on RHEL 7 or CentOS 7.
Cisco is deprecating support for the Microsoft System Center Operations Manager (SCOM) Connector (Basic) beginning with Cisco Crosswork Situation Manager v6.4.1.
Support for SCOM Connector (Basic) ends after the release of Cisco Crosswork Situation Manager v6.5.0.
Customers installing or upgrading to Cisco Crosswork Situation Manager v6.5.1 or later.
Versions of Cisco Crosswork Situation Manager up to and including v6.5 support SCOM Connector (Basic).
Use SCOM Connector (Advanced).
Cisco is deprecating support for the following fields in the Cookbook clustering algorithm beginning with Cisco Crosswork Situation Manager v7.3:
· event_id
· event_type
· event_time
Affected Users
Customers using Cookbook in Cisco Crosswork Situation Manager releases up to v7.2 or later.
Cisco is deprecating the prototype version of the Feedback clustering algorithm beginning with Cisco Crosswork Situation Manager v7.3. Cisco plans to replace the prototype Feedback with a fully-supported GA version of the Feedback clustering algorithm. Custom configurations developed for the prototype Feedback will not work in the GA version.
Affected Users
Customers who use the Feedback clustering algorithm in Cisco Crosswork Situation Manager v7.3 or later.
Cisco is deprecating support for the Template Matcher Moolet beginning with Cisco Crosswork Situation Manager v6.5. Cisco Crosswork Situation Manager v7.0 will not include the Template Matcher Moolet.
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.0 or later.
Cisco is deprecating support for user URL profile images beginning with Cisco Crosswork Situation Manager v7.0. Cisco Crosswork Situation Manager v7.1 will not support URL profile images that were added when users logged in using Google.
Cisco Crosswork Situation Manager still supports standard profile images that users can add when they create an account.
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.1 or later.
Standard support* for Cisco Crosswork Situation Manager v5.2.0 and all prior versions ended on 4th October, 2018. Cisco will no longer provide technical support services or any maintenance fixes for these versions of Cisco Crosswork Situation Manager.
* Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running versions of Cisco Crosswork Situation Manager v5.2.0 and prior.
Upgrade to the current release of Cisco Crosswork Situation Manager. See Cisco Releases for information about the most up-to-date version. Contact Cisco Crosswork Situation Manager support for assistance with your upgrade plans.
Standard support* for Cisco Crosswork Situation Manager v5.1.3 and all prior versions ends on 20 May, 2018. Cisco will no longer provide technical support services or any maintenance fixes for these versions of Cisco Crosswork Situation Manager.
*Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running versions of Cisco Crosswork Situation Manager v5.1.3 and prior.
Upgrade to the current release of Cisco Crosswork Situation Manager. See Cisco Releases for information about the most up-to-date version. Contact Cisco Crosswork Situation Manager support for assistance with your upgrade plans.
Cisco is deprecating support for the legacy built-in Dashboards beginning with Cisco Crosswork Situation Manager v6.4. For example:
The Insights feature introduced in v6.4 replaces the legacy Dashboards. Support for legacy Dashboards ends after the release of Cisco Crosswork Situation Manager v7.0. Cisco Crosswork Situation Manager v7.3 will not include legacy Dashboards. [REVISED 3 December, 2018]Insights
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.3 or later.
Versions of Cisco Crosswork Situation Manager up to and including v7.0 include the legacy Dashboards feature.
Use the Insights feature built on the Stats API. Beginning with Cisco Crosswork Situation Manager v6.4, you can get started with the default Insights Dashboard built for Grafana.Insights
Cisco is deprecating support for the Classic Sigaliser clustering algorithm beginning with Cisco Crosswork Situation Manager v7.3. [REVISED 8 May, 2019]
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.3 or later.
Versions of Cisco Crosswork Situation Manager up to and including v7.3.
Use the /document/preview/108305#UUID1bae66622a0c87fac9f147776be234a3 clustering algorithm to cluster alerts based on the time that they are created.Tempus
Cisco is deprecating support for the Speedbird clustering algorithm beginning with Cisco Crosswork Situation Manager v7.3.
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.3 or later.
Versions of Cisco Crosswork Situation Manager up to and including v7.2 include the Speedbird clustering algorithm.
Use the /document/preview/11777#UUIDf7ebeb66bd2fd4cd5be93559136d00a6 clustering algorithm to cluster alerts based on the similarity of their descriptions or other text fields.Cookbook
Standard support* for Microsoft Internet Explorer 11 (IE11), and all prior versions, ends on January 31, 2020. Cisco will no longer provide technical support services, enhancements, or any maintenance fixes related to Internet Explorer 11 in any versions of Cisco Crosswork Situation Manager.
*Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running any version of Cisco Crosswork Situation Manager who are currently using IE11.
Consider using Microsoft Edge or an alternative browser. See Microsoft Internet Explorer Lifecycle FAQs for more information.
Q: Why is Cisco ceasing support of IE11?
A: Cisco continually strives to give our customers exemplary experience and value while being mindful of delivering this in the most secure manner available. To this aim, we are constantly looking how best to deliver a state-of-the-art, contemporary, potent, performant and intuitive user experience. For this reason, we have taken the decision to discontinue support for IE11 for the following reasons:
Updates: Since Microsoft released the Edge browser in 2015, all major feature improvements have been delivered in Edge, with IE11 restricted to minor non-functional updates only. Microsoft have stated that “the latest features and platform updates will only be available in Microsoft Edge”.
Security: Since Microsoft released the Edge browser in 2015, all major security updates have been delivered in Edge only. In addition, IE11 only supports TLS 1.0 by default.
Technical Debt: Due to the antiquated architecture of IE11 and its more error-prone code base, Cisco's UI development is inhibited by a factor of approximately 50% to ensure we can deliver functional parity for IE11 in comparison to contemporary browsers. We also receive a significant number of IE11-specific bugs. This slows down our engineers from delivering further enhancements and improvements to our customers across more modern platforms.
Architecture: IE11 limits the extent of how we can take advantage of the very latest elements of CSS, HTML, and Javascript APIs. This severely restricts the capabilities we wish to deliver to our customers. This is because IE11 is unable to take advantage of these technologies to the same level, if at all, as the latest browser platforms.
Performance: Supporting IE11 has necessitated the need to bloat our code base. This has had a negative impact on performance.
Q: Will this affect my organisation?
A: If you are already using any of our supported browsers other than IE11, you will not be affected. If your organisation plans to keep using IE11 after January 31st, 2020, you will be affected. If your organisation employs a legacy HTTP client to integrate withCisco Crosswork Situation Manager, you will be affected. We recommend those customers affected start making plans to incorporate the use of one of the other supported browsers in addition to IE11 to minimise any workflow impact.
Q: What steps should my organisation take now?
A: If use of a Microsoft browser is a corporate mandate or preference, Cisco recommends migrating to the latest version of Microsoft Edge. Not only is Edge more secure and performant, it also offers greater interoperability and compatibility with other browser platforms because it has adopted the Chromium technology as its rendering engine for the future. Microsoft has already stated that Edge will be delivered and updated for all supported versions of Windows on a more frequent cadence.
Q: I have further questions. Who should I pose them to?
A: Should you have further questions beyond those answered above, feel free to contact your Cisco Technical Support, your Cisco Account Manager, or our Customer Success team.
Cisco is deprecating support for JSON in filters in inbound and outbound APIs beginning with Cisco Crosswork Situation Manager v7.4.
Customers installing or upgrading to Cisco Crosswork Situation Manager v7.4 or later.
Use SQL-like format in API filters instead of JSON format.
Standard support* for Cisco Crosswork Situation Manager v6.0 and all prior versions ended in January 2019. Cisco will no longer provide technical support services or any maintenance fixes for these versions of Cisco Crosswork Situation Manager.
*Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running versions of Cisco Crosswork Situation Manager v6.0 and prior.
Upgrade to the current release of Cisco Crosswork Situation Manager. See Cisco Releases for information about the most up-to-date version. Contact Cisco Crosswork Situation Manager support for assistance with your upgrade plans.
Standard support* for Cisco Crosswork Situation Manager v6.1 and all prior versions ended in May 2019. Cisco will no longer provide technical support services or any maintenance fixes for these versions of Cisco Crosswork Situation Manager.
*Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running versions of Cisco Crosswork Situation Manager v6.1 and prior.
Upgrade to the current release of Cisco Crosswork Situation Manager. See Cisco Releases for information about the most up-to-date version. Contact Cisco Crosswork Situation Manager support for assistance with your upgrade plans.
Standard support* for Cisco Crosswork Situation Manager v6.2 and all prior versions ends in September 2019. Cisco will no longer provide technical support services or any maintenance fixes for these versions of Cisco Crosswork Situation Manager.
*Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running versions of Cisco Crosswork Situation Manager v6.2 and prior.
Upgrade to the current release of Cisco Crosswork Situation Manager. See Cisco Releases for information about the most up-to-date version. Contact Cisco Crosswork Situation Manager support for assistance with your upgrade plans.
Standard support* for Cisco Crosswork Situation Manager v6.3 and all prior versions ends in December 2019. Cisco will no longer provide technical support services or any maintenance fixes for these versions of Cisco Crosswork Situation Manager.
*Standard support refers to Cisco's standard contract. Refer to the terms of your agreement to verify your level of support.
Customers running versions of Cisco Crosswork Situation Manager v6.3 and prior.
Upgrade to the current release of Cisco Crosswork Situation Manager. See Cisco Releases for information about the most up-to-date version. Contact Cisco Crosswork Situation Manager support for assistance with your upgrade plans.