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

Reduce Cluster expansion time when adding a Remote Collector node to a vRealize Operations Manager Cluster (70642)

Last Updated: 7/16/2020Categories: InformationalTotal Views: 3003Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

When a Remote Collector node is added to a vRealize Operations Manager cluster, the time to expand can take a while depending on the latency between the Primary node and the Remote Collector, as well as the amount of adapters installed to the vRealize Operations Manager cluster.

In the event the pre-checks for an upgrade or cluster expansion are not passed on a Remote Collector due to latency, the upgrade or cluster expansion will fail.

Impact / Risks

Best practices stipulate that a Remote Collector must have a latency consistently under 200ms to the analytics cluster.
Using the method below to work around the sub 200ms latency requirement will not guarantee a successful upgrade, cluster expansion, or fully functional Remote Collector.
VMware will not support a cluster when the minimum requirements are not met.

Resolution

Only add a Remote Collector to a vRealize Operations Manager cluster when the latency to the Analytics cluster is consistently under 200ms.

Workaround

To reduce the cluster expansion time, manually copy the adapters installed to the vRealize Operations Manager cluster to the Remote Collector node.

Deploy a Remote Collector node from vSphere.

Note: You may skip this step if you have already deployed a new Remote Collector node that as not yet been added, or is in the process of adding, to the vRealize Operations Manager cluster.

Log into the Remote Collector node as root via Console.

Note: The root password is blank by default.  Type Enter and follow the prompts to update the password.

Enable SSH:

service sshd start

Log into the Remote Collector node as root via SSH.

SCP the installed adapters from the Primary node, to the Remote Collector:

scp -C master_ip:/data/db/casa/pak/dist_pak_files/VA_LINUX/* /data/db/casa/pak/dist_pak_files/VA_LINUX/

Note: Replace master_ip with the IP address of the Primary node.

Example: scp -C 192.168.3.10:/data/db/casa/pak/dist_pak_files/VA_LINUX/* /data/db/casa/pak/dist_pak_files/VA_LINUX/

Navigate to the Remote Collector's UI in a web browser.

Click Expand An Existing Installation and follow the prompts.

Once all of the necessary PAKs are installed, click Finish adding new nodes.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
VMware Validated Design 5.0.x 用の vRealize Suite Lifecycle Manager での Cross-Region-Env 環境の修復 (70641)

KB
•
在 vRealize Suite Lifecycle Manager 中修复 VMware Validated Design 4.3 对应的 Cross-Region-Env 环境 (70640)

KB
•
Enterprise PKS クラスタ内のマスター ノードが、NCP の再起動のために障害状態になる (70632)

KB
•
Enterprise PKS のワーカー ノードとマスター ノードで CPU 使用率が高くなる (70608)

KB
•
当 ncp 过程在主节点上失败时，Enterprise PKS 群集处于故障状态 (70618)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

Take Our Survey

Support Assistant