Info |
---|
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. |
Table of Contents |
---|
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:
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.
Note |
---|
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.
Anchor | ||||
---|---|---|---|---|
|
Field | Description | Mandatory / Optional |
---|---|---|
Username | Enter Username to be used with VSM | Mandatory |
Password | Enter Password | Mandatory |
Confirm Password | Enter Password again | Mandatory |
First Name | Enter User First Name | Optional |
Last Name | Enter User Last Name | Optional |
Enter User Email Address | Optional | |
Description | Enter Description for the user | Optional |
Role Assignment
Navigate to Administration >> Global Permissions
Click on the 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:
- 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.
- 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.
SNMP Configuration
Configure SNMP V1/V2
Configure SNMP Community String
This step can be skipped if you have Community String Configured
Access the appliance shell and log in as a user who has the administrator or super administrator role
The default user with super administrator role is root.
Run the snmp.set --communities command to configure an SNMP community
For example, to configure public, VSM communities, run the following command:
snmp.set --communities public,VSM |
Note |
---|
Each time you specify a community with this command, the settings you specify overwrite the previous configuration. |
Additional details can be found here
Configure the SNMP Agent to Send v1 or v2c Notifications
Access the appliance shell and log in as a user who has the administrator or super administrator role
The default user with super administrator role is root.
Make sure SNMP agent is enabled,if not enable it by running snmp.enable command
Run the snmp.set --targets target_address@port/community command to send SNMP Notifications to VSM.
Use the following for SNMP target Parameters
Field | Description |
---|---|
target_address | Enter VSM Probe IP Address |
Port | Enter the SNMP Port , if no value is specified then the default port 161 will be used |
community | Enter the Community String to be used |
For example, run the following command for configuring the targets 192.0.2.1 with community VSM
snmp.set --targets 192.0.2.1/VSM |
Note |
---|
Each time you specify a target with this command, the settings you specify overwrite all previously specified settings. To specify multiple targets, separate them with a comma. |
Run snmp.test command to send a test trap to VSM.
The agent sends a warmStart trap to the configured Agent
vCenter SNMP Configuration
SNMP configuration is required as part of CUCM Monitoring. SNMP can be configured as V1, V2, or V3 based on customer requirements.
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:
Field | Value | Mandatory / Optional |
---|---|---|
Enable reciever | Turn it on for the receiver that is going to be used by VSM | Mandatory |
Receiver (Number) URL | Enter IP Address of VSM Probe | Mandatory |
Receiver Port | 162 | Mandatory |
Community String | Enter the Community String that is going to be used by VSM | Mandatory |
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
Field | Setting |
---|---|
Vendor | VMware |
Product | vCenter |
Equipment Name | Friendly name |
Username | SSH Username |
Password | SSH Password |
IP Address / Host Name | IP Address or Hostname of the vCenter server |
Site | Friendly name for the site (where this server is located) |
SNMP
Network Connectivity
Network Connectivity ????? CP and VS to create standard Network conn statement.