VMware Smart Assurance Smarts: VeloCloud Orchestrator (VCO) is not discoverable using ICMP or SNMP

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

• Host object for VCO is not discovered in IP-AM.
• In IP AM log, you see message similar to:

VCO host IP is not pingable via ICMP

Cause

This issue is caused when Host object for VCO is not discovered in IP-AM, resulting in VCO Host Object not imported in ESM.
This would prevent ESM to discover and monitor Velocloud environment as there is no target VCO Host object in ESM topology.

Resolution

To resolve this issue, create VeloCloud Orchestrator object manually in IP-AM using the attached script.

1. Download the file add-vco-ip file attached in the KB.
2. Edit the below line in the script to specific IP address of the VCO:

 

 default vco = "<vco-ip-address>";

3. Run the command:

/smarts/bin/sm_adapter -b <broker> -s <ip-am-pm server> -D vco=<vco-ip-address> add-vco-ip.asl

Example:
/smarts/bin/sm_adapter -b localhost:2121 -s INCHARGE-AM-PM -D vco=1.1.1.11 add-vco-ip.asl