Tuesday, December 10, 2013

UCS Director : How to provision VM using UCS Director?



Introduction

UCS director provides comprehensive virtual infrastructure control, management and monitoring via single pane of glass. However, the entire set of documentation may be a bit overwhelming for a beginner to set up some test lab or test their own learning. 

So the intent of this document is to provide some assistance to build your knowledge or understand some basic pre-requisite tasks for VM provision process and later hope you can set up your own VM provisioning task or somewhat advance task using the UCS director (AKA Cloupia or CUIC). 


Pre-requisite
Virtual Account
- Make sure you have already associated with Virtual Account. This is vCenter association. 
pre-requisite-vcenter.png

Note : 
- When you create a Catalog, you will be asked to specify the "Cloud Name"
- Verify vCenter connection is good with "Test connectivity" from Administration > Virtual accounts

Network policy
- IP address range for VM provisioning . This required when you define Network policy.  


Procedure
In order to complete VM provisioning process, I have created 5 major steps and under each step I put other minor steps with  screen capture and a small explanation.One thing I should emphasis is some small steps can be very important. All the steps I described here is minimum requirement to complete the VM provisioning. 

Step1. Administration menu

The administrator can add groups and users to provide the access to CUIC. The administrator can assign different roles to users in the organisation. In here you will define self service portal user name and user group. This particular user will allow to create a service request for VM provisioning task via the service portal.

User Group tab
     + Add user group : Make sure to add contact email
0.user_group.png

Note : This "user group" will be called at Catalog creation.

User tab
     + Add user : Service type should be Service End-User
0.1.add_user.png

Note : This self portal user should be added into the user group.


Step2. Policies menu

UCS director provides a self-service portal where virtual machines are provisioned from a pool of assigned resources using predefined policies set by admin. So in the Policies menu you can define four policies in order to provision VMs later from the self service portal. These include Computing, Storage, Network and System Policies.


1- Catalog
Users can self-provision virtual machines (VMs) using predefined catalog items created by the system administrator. A Catalog item is created by the system administrator, defining certain parameters like Cloud Name, Policies, Cost Model and Group Name etc., to which the VM will be bound.

• Select Policies > Catalogs
• Click on Add.

     + catalog name, catalog type, Group, Cloud name, Image
     + Application detail such as OS type
     + user credential
     + customisation including cost 

Note : image template must be available in vCenter beforehand. Otherwise, you will not see the Image when you create the Catalog.
1.1.catalog.png


Specify OS but I did not specify any application here.
1.3.catalog_custom.png

You can specify the cost computation or other customisation action here 
1.3.catalog_custom.png


Verify Catalog name, Cloud, Image, User Group.
1.4.catalog_summary.png


2- Computing Policy : VMware Computing Policy
 + In here we define policy name, cloud name, host node, ESX type, Min condition, resizing option (vCPUs, memory). Fairly self explanatory.
     • Select Policies > Computing > VMware Computing Policy
     • Click Add
    
Note : We will associate "Cloud Name" from the pre-requisite task.
2.1.compute_pol.png



3- Network Policy
The Network Policy defines resources like network settings like DHCP or Static IP and option to add multiple vNICs for VMs provisioned using this policy.
     • Select Policies > Network > VMware Network Policy tab
     • Click Add.

Note :
- remember IP address range in the pre-requisite task. 
- If you decide to use "Static IP Pool", this IP address pool will be assigned to VM when the VM provision is performed. 
3.1.network_pol.png


4- Service Delivery policy (aka System Policy)
This is somewhat confusing. It is because in the configuration guide, it is often referred as System Policy and sometimes referred as Service delivery policy. They are basically the same thing.

The System Policy defines the system specific information like Template to be used, Time Zone, OS specific information etc. So if you browse some other menu, this might shows as "System policy". They are basically the same thing.
• Select Policies > Service Delivery > VMware System Policy tab
• Click Add.
     +  In here we define VM template name, Hostname policy, timezone, fns suffix, vm image type
4.1.service_delivery_pol.png


5- Storage policy
In this exercise we will skip this storage policy.
     • Select Policies > Storage > VMware Storage Policy tab
     • Click Add.



Step 3. VDC 
A Virtual Data Center is an environment that combines virtual resources, operational details, rules and policies to manage specific group requirements. So this task will be found under the Policies menu.
One important configuration task is in here you will define "Approval User" which is specific to a vDC. So later this user will access to the self service portal to do the approval task while doing the VM provisioning process.

• Select Policies > Virtual Data Centers.
• define a following : 
     + Group, cloud name
     + approval user name and contact detail (Make sure to note down the username for the approval. This user will be used when you access to the service portal for the approval process)
     + policies : system policy (service delivery policy), compute policy, network policy, storage policy + cost model
     + End user self-service options (VM power mgmt, resizing, deletion, etc)
5.1vdc.png


During VDC creation you will associate all the policies you created in earlier steps.
5.2.add_vdc.png

Note : later you can do the test and see if the self service portal user can perform the End user self-service options.


Step 4. Organization

1. Create Service Request

Either admin user or self portal user can perform this task. 

1.1. Self Portal User
Login as Service End-User 
Service tab > Create Request 
6.1.1.self_portal_user.png

1.2. Catalog selection (make sure to select a right catalog. If not, you cannot see the SR for approval later)
6.1.2.select_Catalog.png

1.3. Select VDC and provision type
6.1.3.select_vdc.png
 

1.4. Custom specification such as CPU core and memory
6.1.4.custom_specification.png

1.5. Verify summary
6.1.5.custom_workflow_summary.png



2. Login to Admin GUI as Admin user

2.1. Verify Service Request Submitted
6.1.6.SR_submit.png

2.2. Service Request Status 
6.1.7.SR_status.png


Step 5. Self Service Portal

1. Service Request approval
Go back to Self Service Portal to perform the approval process. You should login as user having approval responsibility
Note : We define this user in Administration and associate this responsibility when we create the VDC. 

     + Organization > Service Request tab
7.0.approval.png

     + My approval : check the SR and click Approval button.
7.1.approval.png

7.2.approval.png

7.3.approval_Status.png
 
   + Provision
7.4.provision.png


2. Check your email to see if you get the provisioning email.
7.5.email_notification.png

3. Go back to Service portal and check the log to understand how this is proceeding.
7.6.SR_log.png


4. Looks good. Go back to the Service request and verify the request status.
7.7.SR_complete.png

5. You will be also notified when it completes as below :
7.8.email_provision_complte.png



Result
Verify from vCenter and UCS director Admin GUI

1. Login to the vCenter and verify VM is provisioned properly as per the policy definition.
 
- We can see the VM creation completed successfully at vCenter.
8.0.vCenter.png

2. at CUIC we can see VM status is power on
8.1.cuic_vm_status.png

Wednesday, December 4, 2013

UCS and VMware : How to determine fnic and enic version?

Question


How do I determine if fnic driver and enic I installed are compatible with the OS and platform?

Answer

In order to use Cisco UCS compatibility matrix, you need to prepare a following information first :

Step 1 UCSM manager 

UCS release : 
Server model : 
Adapter :

Step 2 ESXi host

ssh to the ESXi host and run "vmware -vl" cmd to check the ESXi version.
Next check fnic and enid version.

vmkload_mod -s fnic
fnic.png

ethtool -i vmnic1
enic.png


Step3. Compatibility Matrix 

Once we have above, we are good to go to the compatibility matrix below and verify if we are using supported firmware.

http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

compatibility_matrix.png

In above example, the fnic driver version we checked with "vmkload_mod -s fnic" is 1.5.0.8 and this is in the supported matrix.

Friday, November 15, 2013

UCS Director : How to avoid VNC connection failure on 64 bit UCSD via HTTPS connection

Symptom


VNC may fail with 64 bit UCSD 4.0.1.1. It exhibits the Server Disconnected (1006) error when ssl secure connection is being used between web browser and 64 bit UCSD.

Conditions

VNC client connection failure only occurs with 64 bit UCSD 4.0.1.1 when ssl connection is made. It always works with http connection.


Workaround

This should be addressed via CSCul23446 . In brief,  64 bit UCSD 4.0.1.1 is delivering 32 bit SSL module for 64 bit environment for web_proxy. So a tempoary workaround before the patch 4.0.1.2 is available as follow :

- Contact BU to get 64 bit SSL library (i.e. __init__.py, __init__.pyc and _ssl2.so).
- Copy these to the following location: /usr/lib64/python2.4/site-packages/ssl/_ssl2.so
- After coping these, run web_proxy service from "/opt/infra/web_cloudmgr/apache-tomcat/webapps/cloupia/cloudmgr/vnc/utils/

[root@localhost utils]# ./startwebsock.sh
[root@localhost utils]# ./statuswebsock.sh
 websock                 RUNNING       32332
[root@localhost utils]#

Note : The file for web_proxy service is "startwebsock.sh"

Friday, July 5, 2013

UCS Director : How to apply CUIC patch?


1. Download CUIC patch from CCO. The file name is cuic_patch_3_4_1_3.zip

Note : Do not unzip the file. CUIC will automatically unzip and apply the patch.

cco_download_1.png
cco_download_2.png


2. Place the downloaded patch to FTP server.

3. ssh or VM Console to CUIC

3.1 Stop the CUIC services using the shelladmin option "3"

3.2 Verify the CUIC services are stopped using the shelladmin option "2"

3.3 Apply the patch by using the shelladmin option 19 as below screen shot

Note :
point to the URL or FTP : http://ip:port/<patchfile> or ftp://username:password@<IPorhostname>/<patchfile>

option_19.png

3.4 Verify the patch is completely applied to the CUIC as below

option_19_complete.png

3.5 Restart the CUIC services using the shelladmin option "4" and verify with option "2"

option_2.png

4. Login into CUIC GUI again and verify the version from "About"

version.png

Friday, May 3, 2013

UCS Director : Basic Performane Troubleshooting Steps

Summary


Poor performance is mostly visible from the lack of response in the website.  The initial login page would display fine however the loading of subsequent pages and navigation through the site is not appropriate. It would be several minutes for a new page to load once it was clicked on at the worst times.  Whilst this was occurring, it was noticed that the CPU on CUIC VM would often hit 100%


Basic Troubleshooting Steps

1. VM resource reservation
Try to reserve the resources for CUIC Virtual Machine via vSphere :

CPU --> 2000 Mhz
Memory --> 3GB
cuic_vm_resource.png

2. Infrastructure Polling interval

Increase "Infrastructure Polling interval" from default value to 60 min. This setting can be configured at Administration > Physical Accounts > Infrastructure System parameters
cuci_infrastructure.png

3. Monitoring property

Only enable property absolutely needed. Some customer has enabled all the properties in "Advance Configuration", it can significantly contribute the slowness on the system. You can adjust this setting at Administration > System Administration > Advanced Configuration
Note :  As a course of troubleshooting, untick "Performance monitoring" or untick everything and monitor if the problem goes away.

cuic_monitoring.png

4. Map Report

Review the map report to see if there is any VM in orverload status.
cuic_map_report.png

5. Collect all logs and system info (Adv)

If step1 to 4 does not help, collect "All logs" and "System Information (Advance)" and escalate to BU. To collect the logs, you need to click "System Information and Logs Link Page" as shown below :
cuic_supportinfo.png

Tuesday, April 30, 2013

UCS Director : How to collect logs from shelladmin with Root access

Background


If the webserver is not working (Tomcat has an issue or something else), it is not possible to collect logs via GUI


Steps

1. ssh shelladmin@<UCS director>

2. select menu 23) Login as Root

3. you can browse to /opt/infra directory and type "ls"
ucsd_opt_infra.png

3. You can find a following 3 scripts :
collectBasicSystemInfo.sh
collectSystemInfo.sh
createLogZip.sh

cloudCare_CLI.png

4. collectSystemInfo.sh is associated with "System Information (Advanced)
UCSD_collectsysteminfo.png

5. createLogZip.sh is associated with "Download All Logs" but before you run, you need to create a target diretory to save the logs.

In my test I have crated tpm/alllog directory and here is result :

ucsd_createlogzip copy.png

ucsd_new_logall.png