vDCA550 Scenarios

1-Configure Datastore Alarms Scenarios

Scenario 1:

Create an alarm for datastore which will tell us and email when datastore will overcommit. Alarm will trigger and show you warning, when Storage provisioned of a datastore on the vSphere reached up to his 100% capacity and show you critical red error alarm when datastore is overcommitted up to 150%.This alarm is very helpful for NFS Datastores which have the ability to overcommit the storage.

Solution Scenario 1

Scenario 2:

Create an alarm for datastore which will email us when specific datastore capacity increased and datastore name would be” ISCSI1_datastore”.

Solution Scenario 2

2-Configure and Manage VSS Components

Scenario 1:

How to create and remove a Virtual Switch “vSwitch1” from GUI and CLI

Solution Scenario 1

3-Migrate a vSS network to a hybrid or full vDS solution

Scenario 1:

Create a Hybrid Virtual Network Solution. In which leave vMotion and Management Traffic are on vSS and migrated all IP Storage, VMs traffic on the vDS.

Solution Scenario 1

4-Configure vSS and vDS settings using command line

Scenario 1:

Create a new vSS named “vSwitch1” having “200” ports with support for jumbo frames ( MTU = 9000 ). Attach “vmnic2” as uplinks. Create a port group named “IP-Storage”. Set its VLAN property to “101”, and set its “NIC Teaming to  iphash” . “Enable traffic shaping” with “average” and “peak” bandwidth set to 50 Mbps. Before beginning, ensure that no vSS named “vSwitch1” already exist.

Solution Scenario 1

Scenario 2:

Use the “example 1” vSwitch1 and PG “IP-Storage” to create a vKernel PortGroup which we will use for ISCSI/NFS and vMotion. Set the vKernel Interface name “vmk3” and static IP Address “192.168.150.16/24”.

Solution Scenario 2

5-Determine appropriate discovery protocol

Scenario 1:

To disable CDP on vSwitch0

Solution Scenario 1

6-Use command line tools to troubleshoot and identify VLAN configurations

Scenario 1:

Check the VLAN Configuration on “vSwitch1” Portgroup “VM-3”. Very his uplink should be “vmnic2”and configure the VLAN ID 100. 

Solution Scenario 1

Scenario 2:

Verif the existing VLAN Configuration on “vSwitch1” PortGroup “VM-3” and Disable the “VLAN”.

Solution Scenario 2

7-Understand the NIC Teaming failover types and related physical network settings

Scenario 1:

Change the load balancing policy of “vSwitch0” into “IP based Hashing”

Solution Scenario 1

8-Configure explicit failover to conform with VMware best practices

Scenario 1:

Configure Active and Passive NICS for a Standard Virtual Switch On a vSS named vSwitch3 that has a team of NICs (vmnic1, vmnic2, and vmnic3), configure the “Production” port group to direct its I/O to “vmnic1” only, under normal conditions. Likewise, configure the “RND” port group to direct its I/O to “vminic2” under normal conditions. Configure both port groups such that they can failover to “vmnic3”, if necessary. 

Solution Scenario 1

Scenario 2:

Configure a port group named “Production” on a vDS named “dvSwitch1” to use uplink to “Uplink-3” with the “Route based on physical NIC load” teaming policy. Set “Failback” to “No”. On the same switch, configure the “VM-01” Portgroup to use “Uplink-1” with the “Use Explicit Failover Order” teaming policy, but permit it to “failover to “Uplink-2” if necessary. Ensure that each port group is configured to “notify switches” in the event of a failover

Solution Scenario 2

9-Configure port groups to properly isolate network traffic

Scenario 1:

Network administrator configured the physical Switch Ports as a trunked for VLAN 10-15. vSphere administration tasks is to create isolated infrastructure for “IP-Storage, vMotion and VM” traffic on “vSS” named “vSwitch1” with following configuration.

  1. Create Portgroup named “IP-Storage” for Management traffic and isolated with “VLAN10” on uplinks “vmnic2 active/vmnic3 standby”.
  2. Create Portgroup named “vMotion” for vMotion traffic and isolate with “VLAN11” on uplink “vmnic1”
  3. Create Portgroup named “VM-3” for VM traffic and isolate with “VLAN12” on uplink “vmnic3 active/vmnic2 standby”

Solution Scenario 1

Scenario 2:

Network administrator configured the physical Switch Ports as a trunked for VLAN 16-20. vSphere administration tasks is to create isolated infrastructure for “vMotion, IPStorage and VM” traffic on “vDS” named “vDSwitch1” with following configurations.

  1. Create Portgroup named “IPStorage” for ISCSI/NFS traffic and isolated with “VLAN16” on uplinks “vmnic1 (uplink1) active/vmnic2 (uplink2) standby”.
  2. Create Portgroup named “vMotion1” for vMotion traffic and isolate with “VLAN18” on uplink “vmnic3 (uplink3)”
  3. Create Portgroup named “VM-3” for VM traffic and isolate with “VLAN20” on uplink “vmnic2 (uplink2) active/vmnic1(uplink1) standby”

Solution Scenario 2

10-Configure and administer vSphere Network I/O Control

Scenario 1:

Configure a Network I/O Control to provide High shares for all “Production VMs”, normal to Dev VMs and Low shares for all RND VMs. One portgroup are used for Production VMs, Dev and RND VMs each with named “PG-VM-Prod”, “PG-VM-Dev” and PG-VM-RND respectively. The VLAN ID of each is uniquely assigned from 10 to 15.

Solution Scenario 1

 

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s