Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

EMC M&R | How to upgrade Traffic Flow SolutionPack and migrate data to ElasticSearch Database (517393)

Last Updated: 5/29/2020Categories: How toTotal Views: 2800Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

Pre-requisites for v4.0 of Traffic Flow SP

EMC M&R core must be updated to v6.8u2 by copying the packages to be upgraded into the module-repository and running the following commands:

/opt/APG/bin/manage-modules.sh update module-manager

/opt/APG/bin/manage-modules.sh service update all

/opt/APG/Tools/Module-Manager/1.13u1/bin/launch-update.sh

For more details on how to do this please refer to the EMC MnR 6.8u2 Installation and Configuration guide

The Elasticsearch cluster package must be installed and running prior to upgrade to this SP version. (Knowledgebase article #516878 covers the steps to complete this)

Checking Upgrade Availability

Once the pre-requisites have been met, you can upgrade the Traffic Flows SolutionPack block

Beginning the Upgrade

Within Centralised Management, Navigate to SolutionPacks and search for  traffic  to display the Traffic Flows SolutionPack. You will see the SolutionPack can be upgraded

Click the upgrade icon to begin the upgrade process

Follow the on-screen prompts, filling in details where appropriate

Confirm that the correct installation path,  IP address or hostname is entered for the location of the ElasticSearch database

Post upgrade steps

Once the update is complete it is necessary to create new resources to direct the frontend to the ElasticSearch Database.

From the command prompt, run the provided commands from the /opt/APG/bin directory to create the resources. Example:

./manage-resources.sh create "dba/ES-TF-CONV" '{ "type": "elasticsearch", "datasource": { "hosts": ["http://HOSTNAME:9200"], "prefix": "/es-dw-flow-conv-topn*" }, "settings": {"mapping": "ES-TF-CONV.xml"}, "disabled": false }'

Then restart the Tomcat service

Migrating Data to the ElasticSearch Database

When Tomcat service has restarted. Stop the Event Processing Manager service for traffic flow

Log into the UI and navigate to Centralised Management > Scheduled Tasks > Event Processing > event-database-migration-generic-traffic-flow. Click the Run Now button to start the task

Confirming data migration

When the database migration task has completed, it is possible to confirm that data has been migrated to the ElasticSearch Database by checking the following URL in your browser:

http://<Host_IP_of_ElasticSearch>:9200/_cat/indices

http://<Host_IP_of_ElasticSearch>:9200/_template?pretty

http://<Host_IP_of_ElasticSearch>:9200/es*/_search?pretty

Example output of http://<Host_IP_of_ElasticSearch>:9200/_cat/indices

Yellow   open    es-dw-flow-applications-topn-1517443200000    0znSJtYoRoqg-ULesEF6Kg 5 1    68509    0 15.6mb    15.6mb
Yellow   open    es-dw-flow-srcaddr-topn-1517443200000    n2seMvhgR1Oe12Toae2kPA 5 1    110751    0 21.5mb    21.5mb
Yellow   open    es-dw-flow-hosts-1517443200000        3IvgjwB6T-yhyqaWORqXiw 5 1    20359    0 4.7mb    4.7mb
Yellow   open    es-dw-flow-dstaddr-topn-1517443200000    H1npPNfjSL-hUnnAQAddLg 5 1    110766    0 21.5mb    21.5mb
Yellow   open    es-dw-flow-conv-topn-1517443200000    RdXKyLbKRGqAPutZOl986g 5 1    87452    0 25.6mb    25.6mb
Yellow   open    es-dw-flow-protocols-1517443200000    UvxjWqeoRcKGPITYPFhhjw 5 1    23252    0 5.3mb    5.3mb
Yellow   open    es-dw-flow-topint-topn-1517443200000    Fv2Evf52TKO_L3OQOm7V8w 5 1    3048    0 1mb    1mb

Related Information

Elasticsearch is used for storing events data by default in SAS 9.5 for TrafficFlow SolutionPack

The Elasticsearch Database replaces the x100 datastore found in previous versions of EMC M&R (6.3   6.7)

In SAS 9.5 there is built-in functionality to allow Event Data Migration of pre SAS 9.5 events data from the depreciated datastore to the Elasticsearch database.

Please note that this covers the steps for an upgrade from 6.7u1 to 6.8u2 of M&R. For upgrades to 6.8u2 from earlier versions, i.e. 6.6u1, please see the SolutionPack Articles installation guide

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant