Collector nodes missing from GUI after deployment in VCF Operations for Networks
search cancel

Collector nodes missing from GUI after deployment in VCF Operations for Networks

book

Article ID: 439249

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

  • After deploying one or more new Collector nodes they do not appear under Settings > Infrastructure and Updates.
  • The VMs are powered on in vCenter, but the Platform cluster does not acknowledge their registration.
  • From CLI (i.e. SSH to Collector node as consoluser) command:

    show-connectivity-status

    which shows the "Platform VM Pairing status: Failed" as shown in below example:
    (cli) show-conectivity-status
    Proxy VM

    Customer ID: #####
    Deployment UUID: ########-####-####-####-########
    Deployment ID: #########
    Instance ID: ####################
    Created On: ()
    IP Address: ##.#.###.###
    Netmask: 255.255.255.0
    Gateway: ##.#.###.#
    DNS nameservers: ##.##.###.##
    NTP servers: ##.##.###.##
    NTP status: InSync
    Gateway ping status: Success
    Upgrade connectivity status (suc.ni.vmware.com:443): Failed
    Support connectivity status (support2. ni.vmware.com:443): Disabled
    Performance Telemetry connectivity status (svc.ni. vmware.com:443): Disabled
    Registration connectivity status (reg.ni.vmware.com:443): Failed
    Registration status: Not Registered
    Platform VM IP/URL: ##.##.###.##
    Platform VM network connectivity status: Failed (All services may not be running.)
    Platform VM Pairing status: Failed
    (cli)

 

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

Environment

VCF Operations for Networks 6.14.x

Cause

The newly deployed collector was not paired with the Platform using the required Shared Secret.

Resolution

  1. Log into the GUI and navigate to the Infrastructure and Support page.

  2. Click on the "Add a new Operations for Networks Data Collector virtual appliance" button and copy the Shared Secret.

  3. Log into each Collector node that is not paired via SSH using the consoleuser account.

  4. Execute the set-proxy-shared-secret command on each Collector that is not paired.

  5. Paste the copied Shared Secret when prompted to complete the pairing sequence.

Additional Information

Installation and Configuration

Deploy Additional Collector to an Existing Setup