How to fix a vCenter Appliance No-Networking problem

This problem might occur with your vCenter Server Appliance. But it could also happen with other Linux-servers. It might happen when you move the virtual machine, clone it, restore it, recover it from replication or perform any other action where the MAC Address of the virtual machine changes. This is what you would see on the console of the virtual appliance:

vCenter Appliance No Networking error

vCAC and vCenter Orchestrator workflow to move Virtual Machines to a Resource Pool

This article describes how to create a workflow in vCenter Orchestrator that, when executed from vCAC, moves a provisioned Virtual Machine to a specified Resource Pool. If the Resource Pool does not exist it will be created.

Requirements:

- vCAC Plugin installed in vCO and configured (documentation and download for plugins)

Import existing virtual machines in vCloud Automation Center

Virtual machines from an existing vSphere environment can be imported into vCloud Automation Center to manage them from there. You perform this action as an Infrastructure Administrator with a tool named Infrastructure Organizer that you will find under the Infrastructure tab in your vCAC administration portal.

vCloud Automation Center Import virtual machines

Modify the Session Time Out for vCloud Automation Center 6.x

The default timeout value for the vCAC web console is 30 minutes. You might find this not long enough or too long, whatever your reasons are, if you want to change it you can.

Access the vCAC Appliance through SSH (with Putty for example) or access the virtual appliance console directly to modify this file:

for 6.0  /usr/lib/vcac/server/webapps/shell-ui-app/WEB-INF/web.xml

for 6.2  /usr/lib/vcac/server/webapps/vcac/WEB-INF/web.xml

Configure vCenter privileges for access to vCenter Operations Manager

After deployment of vCenter Operations Manager there are two users in the system that have access to the entire environment. These are the built-in admin-user of vCops and any user that is assigned to the Administrator role in vCenter. In the image below you can see that there are two privileges assigned in the Administrator role that allow anyone assigned a permission with this role to access vCenter Operations Manager as an administrative user.

How to reset vCenter Operations Manager Configuration to the default settings

It is possible to reset your vCenter Operations Manager configuration to the default settings. This applies to the default policy but also to any other policies that you may have created in your environment. Open the Configuration panel, click the Default Policy or any other policy you would like reset. Next in the Clone from field select Original Defaults and click Ok to save the settings. All configuration settings for that policy are now reset to the default vCops settings.

Follow us on LinkedIn

  

   

   

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer