You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

This section makes frequent use of data contained in the Technical Requirements.

All relevant sections of the Technical Requirements Data collection should be completed or known before commencing with the steps in this section.

Create vCenter User

VSM requires a user account to be created on vCenter, in order to run API commands which collect the status of the virtual machines running on vCenter.

vCenter users can be created via one of two options:

  1. Local User Option
  2. Active Directory Option

Local User Option

Login to the vSphere web client. You will need administrative privileges to complete these operations.

From the home menu, click on Administration.


In "Administration", click on "Users and Groups".


Choose the correct domain from the domain list.

You can not use 'localos' Domain to Add user.


Click the "ADD USER" link.


Fill in the required user details as per the table below.

FieldDescriptionMandatory / Optional
UsernameEnter Username to be used with VSMMandatory
PasswordEnter PasswordMandatory
Confirm PasswordEnter Password againMandatory
First NameEnter User First NameOptional
Last NameEnter User Last NameOptional
EmailEnter User Email AddressOptional
DescriptionEnter Description for the userOptional

Role Assignment

Navigate to Administration >> Global Permissions


Click on the (plus) icon.


Enter the username created earlier in User/Group field and select 'Read-Only' from the Role dropdown list, then click ok.


Check that what you have entered is correct, if it is then click 'OK'.


Make sure the user appears under User/Group with Role the "Read-only".

Active Directory Option

There are two scenarios for Active Directory:

  1. The client uses Active Directory to create a user and assign permissions via group policy to vCenter Users.
    • If so, ask the Client to create a vCenter account with Read-Only access.
  2. The client uses Active Directory for vCenter user creation only, and not assigning permissions.
    • If so, ask the Client to create a vCenter account via Active Directory, then follow the steps detailed in the Role Assignment section to assign Read-Only permission to the User.


vCenter SNMP Configuration

You can configure up to four receivers to receive SNMP traps from vCenter Server. For each receiver, specify a host name, port, and community.

From vSphere Client, navigate to the vCenter Server instance.


Select Configure tab


Under Settings, select General

Click Edit


Select SNMP receivers

Choose the Receiver Number that is going to be used for VSM,and enable it , In the example shown receiver 2 has been enabled





Fill in the data as the below:

FieldValueMandatory / Optional
Enable reciever Turn it on for the receiver that is going to be used by VSMMandatory
Receiver (Number) URLEnter IP Address of VSM ProbeMandatory
Receiver Port162Mandatory
Community StringEnter the Community String that is going to be used by VSMMandatory




Web Portal Configuration

Add vCenter

Log in to the VSM web portal using your credentials and password.

For the particular customer, select Service Desk > Equipment Locations. Right-click on the Equipment Location that will serve this vCenter and select 'Manage Equipment':

At the bottom of the 'Manage Equipment' page, click on the 'Add Equipment' button.

Select the Vendor 'VMWare' and the Product 'vCenter '.

If you are adding more than one piece of the same equipment type, check the 'Add another' box at the bottom of the form and the bulk of the configuration will be carried over for the next item.


Web Portal - Add vCenter Field Description

FieldSetting
VendorVMware
ProductvCenter
Equipment Name

Friendly name

UsernameSSH Username
PasswordSSH Password
IP Address / Host NameIP Address or Hostname of the vCenter server
SiteFriendly name for the site (where this server is located)

SNMP

Network Connectivity

Network Connectivity ????? CP and VS to create standard Network conn statement.


  • No labels