When you run a command, the Serengeti CLI or Big Data Extensions plug-in displays the following error. Internal error: REST API transport layer error.
Serengeti Management Server needs to communicate with vCenter Server Extension vService through vCenter Server's FQDN during initialization. The following 3 scenarios will prevent you from performing Serengeti operations.
- (vSphere 5.1) If the host name is not correctly set during vSphere installation, vCenter Server cannot receive the correct host name or FQDN, nor provide the correct information to the Serengeti Management Server. As a result, the Big Data Extensions plug-in cannot successfully communicate with vCenter Server.
- (vSphere 5.5) If the vCenter Server Appliance is deployed into an OVF environment that has a static IP network configuration and a blank host name, the reverse lookup from the IP address cannot be performed. Without the reverse lookup, the host name is incorrectly set for the vCenter Server Appliance.
- During the installation of Big Data Extensions vApp instance, if vCenter Server is configured a FQDN, but this vApp does not configure an appropriate DNS server that can resolve this FQDN, or this vApp does not confgure an appropriate network that can communicate with vCenter Server.
For vSphere 5.1, set the correct FQDN name.
- Use the vSphere Web Client to log in to vCenter Server.
- From the Inventories pane, click vCenter. On the left pane, click vCenter Servers.
- From the left pane, click the name of the connected vCenter Server.
- Click the Manage tab, click Settings, and from the tab's left nvigation pane, click Advanced Settings.
- Find the keys related to FQDN or fullQualifiedDomainName or evs and change the values from incorrect FQDN to the correct FQDN or IP address.
- Delete and install a new Big Data Extensions vApp instance.
For vSphere 5.5, reinstall your environment.
- Delete and reinstall the vCenter Server Appliance. During reinstallation, set the vCenter Server Appliance host name in the OVF properties.
- Delete the existing Big Data Extensions vApp instance and install a new Big Data Extensions vApp instance.
For incorrect DNS server or network issue, delete and install a new Big Data Extensions vApp instance with an appropriate DNS server and network that can resolve the vCenter Server FQDN and communicate with it.