Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Using the flow-sync command in vRealize Network Insight (78117)

Last Updated: 4/14/2020Categories: How toTotal Views: 2506Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

As vCenter can only send flows to a single vRealize Network Insight instance, the flow-sync command can be used to copy flows from a Proxy in one vRealize Network Insight instance to a Proxy in another vRealize Network Insight  instance.

Use-case Examples:

Interest in EFT (Engineering Field Trial) for a new feature. Flows of a Production vRealize Network Insight instance can be sent to a EFT vRealize Network Insight installation.

Moving to SaaS from on-prem. The on-prem install should work as-is while the SaaS setup is configured for a period of 30 days. This will require flows to be sent to both installations.

Solution

The flow-sync command is available in vRealize Network Insight 5.2 and later.
To install the flow-sync command in vRealize Network Insight 4.2, 5.0, or 5.1, follow Add flow-sync to vRealize Network Insight 4.2 - 5.1.

To use the flow-sync command, fist identify the Sender Proxy, and the Receiver Proxy.
Sender Proxy:

This is the vRealize Network Insight Proxy which is already receiving flows from vCenter/NSX.

This Proxy can copy flows to another vRealize Network Insight Proxy.

Receiver Proxy:

vRealize Network Insight Proxy in the EFT, SaaS, or second install will become the Receiver.

Once the Proxy roles are identified, log into the Receiver Proxy as consoleuser via SSH or Console.

Run the command below to start the receiving process:

flow-sync start receiver --sender-ip=proxy_sender_IP

Note: Replace proxy_sender_IP with the IP address of the Sender Proxy.
Example: flow-sync start receiver --sender-ip=192.168.3.40

Note the secret key given by the output of the previous command.

Now, log into the Sender Proxy as consoleuser via SSH or Console.

Run the command below to start the sending process:

flow-sync start sender --secret secret_key

Note: Replace secret_key with the secret key noted in step 3.
Example: flow-sync start sender --secret secret_key

Related Information

The below flags can be given to the flow-sync command for additional options.

Flag

Description

Notes

flow-sync status

Check the status of the flow sync.

Can be run on Sender and Receiver Proxies.

flow-sync logs

Show flow sync operation logs.

Can be run on Sender and Receiver Proxies.

flow-sync stop

Stop the flow sync process.

Must be run on Sender and Receiver Proxies.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server Appliance をアップグレードするとローカル ユーザー アカウントが表示されなくなる (78148)

KB
•
在 vRealize Operations Manager 8.1 中升级过程的重新引导阶段后，节点无法访问 (78302)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Network Insight

Related Versions:

VMware vRealize Network Insight 5.x

VMware vRealize Network Insight 5.2.x

VMware vRealize Network Insight 5.1.x

VMware vRealize Network Insight 4.x

Take Our Survey

Support Assistant