Add a New vLan to a Distributed Switch NOUTG

-

 This article talks about creating a new Port Group and assigning a new vLAN to it.

Steps to follows: 

1) Login to vCenter, Go to Networking > Datacenter > Networks > Distributed Switches > Right click on dvSwitch -> Action-dvSwitch_Datacenter_Name (Example:dvSwitch_DAL) -> New Distributed Port group

2) Specify the name of the dvLAN

Naming convention-

For the dvSwitch VLAN name make sure that "dv" is in lowercase and that "LAN" is in upper case followed by the vLAN number.

Example - dvLAN150

Note :- All hosts attached to the distributed switch need to have the new vLAN trunked to them before this change is made. Also, the new vLAN should be present in the OneView.

3) Configure the below settings

a) In the vSphere Web Client, navigate to the distributed switch.

b) Right-click the distributed switch and select Distributed port group > New distributed port group.

c) On the Select name and location page, enter the name of the new distributed port group, or accept the generated name, and click Next.

d) On the Configure settings page, set the general properties for the new distributed port group and click Next.

i. Port Binding :- Static Binding (Leave default)

ii. Port allocation :- Elastic (Leave default)

iii. Number of ports :- 8 (Leave default)

iv. Network resource pool :- default (Leave default)

v. VLAN :- Mention the desired VLAN you intend to create.

e) On the Ready to complete page, review your settings and click Finish.

Comments

Post a Comment

Popular posts from this blog

VMware:- Esxi Log File Locations

-
Enable SSH and connect the host through CLI tool-  *Authentication- /var/log/auth.log *ESXi host agent log - /var/log/hostd.log *Shell log - /var/log/shell.log *System messages - /var/log/syslog.log *vCenter Server agent log - /var/log/vpxa.log *Virtual machines - The same directory as the affected virtual machine's configuration files, named vmware.log and vmware*.log. For example, /vmfs/volumes/datastore/virtual machine/vmware.log *VMkernel - /var/log/vmkernel.log *VMkernel summary - /var/log/vmksummary.log *VMkernel warnings - /var/log/vmkwarning.log *Quick Boot - /var/log/loadESX.log *Trusted infrastructure agent - /var/run/log/kmxa.log *Key Provider Service - /var/run/log/kmxd.log *Attestation Service - /var/run/log/attestd.log *ESX Token Service - /var/run/log/esxtokend.log *ESX API Forwarder - /var/run/log/esxapiadapter.log
Read more

ESX and vCenter Alarms

-
Image
  Definition An  Alarms  is a   notification  that are activated in response to an event, a set of conditions, or the state of an inventory object. An alarm definition consists of the following elements in the vSphere Client: ·  Name and description - Provides an identifying label and description. ·  Targets - Defines the type of object that is  monitored. -  VM\  DataSore \N\W  etc. ·  Alarm Rules - Defines the event, condition, or state that triggers the alarm and defines the notification severity. It also defines operations that occur in response to triggered alarms. ·  Last modified - The last modified date and time of the defined alarm.   Alarm categories – Alarms have the following severity levels: ·  Normal –  green  -   Status is Good. The health of the object is Normal ·  Warning – yellow  -  Status is Warning – The Object experiencing Some Problem ·  Ale...
Read more

Convert VMware Snapshot into Memory Dump

-
Image
  Convert VMware Snapshot into Memory Dump Background   This document explains about generating a memory dump for a VMWare Virtual Machine when the machine becomes unresponsive. VM becomes unresponsive for various reasons, you may not be able to get into any OS related settings or access any application. Even users may get not be able to access any shares or resources of this machine.   In this type of situation Memory dump would be required to  analyze  the cause. Even if the OS is configured to generate a Memory Dump for System Crashes, it would not be able to generate a Memory Dump for System Unresponsiveness most of the  times. But  with a VMWare VM, you can take a snapshot of the machine when it is unresponsive and then use vmss2core.exe tool to convert the snapshot to a Memory Dump. The target audience for this information is any technician that is responsible for creating and deleting snapshot in the Levi virtualization environment.   Note ...
Read more