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

Watch4net : What Is The Procedure For Implementing Multi-Tenancy with Traffic Flows in Watch4net 6.7u1? (526540)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

In order to implement multi-tenancy with Traffic Flow reports you need to add additional properties to identify the source of the traffic in the Traffic Flow SP.
The following steps can be followed to implement a new property called ROUTER_SRC_TEMP.

1.   Add a new property to the Flow Events in the Event-Property-Tagger instance of Traffic Flow SP. To illustrate, we add a new property in the Event-Property-Tagger named ROUTER_SRC_TEMP in the flow-global-enrichment.xml file in the EPT. (feel free to copy and paste)

<text-file path="conf/exporters.csv">
<accessor accessor-class="PropertyAccessor">
<parameter name="url">http://localhost:58080/APG-WS/wsapi/db</parameter>
<parameter name="user">ws-user</parameter>
<parameter name="password">{BB08ED04BE45F67A36D4BF31BFFC94CF251BA11539F250A0C00826C23A92E032183BDAFE231797B7BF5ACA5C0E60888C}</parameter>
<parameter name="properties">ifaceip device</parameter>
<parameter name="filter">devtype='Router' &amp; #APG:ALL</parameter>
</accessor>
<accessor accessor-class="com.watch4net.apg.v2.collector.plugins.propertytaggingfilter.accessor.StaticAccessor">
<parameter name="line">**,NOSNMP</parameter>
</accessor>
<field-separator>,</field-separator>
<field-quoting>"</field-quoting>
<default-symbol>**</default-symbol>
<property-insertion start="[" end="]"/>
<key-properties>
<key-property delete-after-use="false" string-type="string" decoder="IP">ROUTER_SRC</key-property>
</key-properties>
<new-properties>
<new-property>ROUTER_SRC_NAME_TEMP</new-property>
</new-properties>
</text-file>

2)    We also need to add a reference in the AGGREGATOR to make sure the property is picked up during the aggregation phase. In this case I am trying to push the variable to SRCADDR table so it has to come through the FLOW-SRCADDR-TOPN. So, we will have to add the reference in the FLOW-AGGR-SRCADDR-TOPN.xml. The new property will look something like:

<constant-property-list>
<mapper>StringMapper</mapper>
<mapping-key-list property-name="ROUTER_SRC_NAME">ROUTER_SRC_NAME</mapping-key-list>
<mapping-key-list property-name="ROUTER_SRC_NAME_TEMP">ROUTER_SRC_NAME_TEMP</mapping-key-list>
<mapping-key-list property-name="SNMP_NAME">SNMP_NAME</mapping-key-list>
<mapping-key-list property-name="HOST_NAME">HOST_NAME</mapping-key-list>
<mapping-key-list property-name="APPLICATION_NAME">APPLICATION_NAME</mapping-key-list>
<mapping-key-list property-name="APPLICATION_DESC">APPLICATION_DESC</mapping-key-list>
<mapping-key-list property-name="APPLICATION_ID">APPLICATION_ID</mapping-key-list>
</constant-property-list>

3)    Since the new property exists in the event coming out of FLOW-AGGR-SRCADDR-TOPN, we will have to add a mapping in the datastore writer of FLOW_SRCADDR_TOPN table to make sure this is pushed to the DB.
For this we will have to edit the  DW-FLOW-SRCADDR-TOPN.xml file and make a reference to the newly added field so that it is picked up by Writer and pushed to the DB.

<field field="ROUTER_SRC_NAME_TEMP" name="ROUTER_SRC_NAME_TEMP" data-type="STRING" xsi:type="DefaultFieldMapping" />

4)    At this point, we need to make sure that the event is pushed to the DB, we will need to add a new column to the DB, in this case to the
FLOW_SRCADDR_TOPN table. This can be done by entering the following command.

ALTER TABLE FLOW_SRCADDR_TOPN__SEQ_0_4__ ADD COLUMN ROUTER_SRC_NAME_TEMP VARCHAR(120);

5)    Finally restart the Event Processing Manager of generic-traffic-flow sp and wait for the aggregation to complete, and the new column populated in the DB should be visible.
From APG/bin
execute: ./manage-modules.sh service restart event-processing-manager generic-traffic-flow

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