ProfessionalVMware.comVCAP Brownbag, 8/17/2011Damian Karlson
VCAP Blueprint Section 2Objective 2.1: Implement & Manage Complex Virtual NetworksObjective 2.2 : Configure and Maintain VLANs, PVLANs and VLAN SettingsObjective 2.3: Deploy and Maintain Scalable Virtual NetworkingObjective 2.4: Administer vNetwork Distributed Switch Settings
SNMP & MoreIPv6: Host Configuration > Networking > PropertiesNetQueue: Host Configuration > Advanced Settings > VMkernel/Boot; also use esxcfg-advcfgSNMPvCenter: Administration > vCenter Settings > SNMPNotification traps onlyESX/ESXiESXi only has VMware embedded SNMP agent. ESX has Net-SNMP & VMware embeddedCan only be managed through vicfg-snmp (remote CLI or vMA), which opens the appropriate firewall ports.Configure communities first, then destination
Comparing vSS & vDSvSS (virtual standard switches) – same virtual switching technology we all know and loveSwitches defined on each host in a clusterPortgroup/VLAN/uplink configurations can be tediousvDS (virtual distributed switches) – introduced with vSphere 4.0Unified switch across hosts in a clusterSeparation of control and data planesExtensible through 3rd party switches (Cisco NK1v)Traffic stats available; shaping available at dvPortGroup and dvUplink portgroup levelsIngress traffic shaping
Create & Manage vSwitchesFull range of vSSconfig needs supportedSome things only available through CLI, such as MTUPartial range of vDSconfig needs supportedSome things not available through CLI, such as PVLANs or creating dvPortGroupsTools are the usual suspects: esxcfg-vswitch, esxcfg-nics, esxcfg-vswif, esxcfg-route, esxcfg-vmknic, PowerCLI, vMA
VLAN TaggingVST (virtual switch tagging)VLANs defined at vSwitch level; physical switch accepts all or rangeEST (external switch tagging)VLANs are set to 0 at vSwitch; physical switch does all taggingVGT (virtual guest tagging)VM tags thru virtual NIC propertiesvSwitch set to 4095; physical switch accepts all or range
Private VLANsPVLANs are VLANs within VLANs. Requires physical switch support.Original VLAN is the primary, additional VLANs are secondary VLANs.Secondary VLANs come in 3 flavors:Promiscuous VLANs have the same primary and secondary VLAN ID. Can talk to anyone in the same primary.Isolated VLANs can only talk to hosts in a promiscuous VLANCommunity VLANs only talk to each other, and to the promiscuous VLAN
VLAN ConfigurationVLANs on vSS are defined at the portgroup levelPVLANs are defined at the vDS level first, then can be selected at the portgroup levelDistributed switches can have VLANs defined at the dvPortGroup level and the dvUplinkPortGroup levelvDS VLAN options“None” for EST“VLAN” for VST“VLAN Trunking” for VGT or multiple VST
Uplink teamingRoute based on IP hashRequires Etherchannel or equivalent. Req’d for FTExplicit failoverCan be used to balance load & provide availability in certain situationsRoute based on source MACRoute based on virtual port ID
Network IsolationIsolate vMotion, NFS, iSCSI, FTSeparate storage from VM networksUse VLANsWhen teaming use physical NICs on different busses
vDS Port BindingsStaticPort is assigned at all times, until the VM is removed from the port groupVM can only be connected through vCenterDynamicPort is assigned when VM is on and vmnic is connected, otherwise it is disconnected.VMs with dynamic ports can only be powered on/off through vCenterEphemeraldvPorts can be assigned through ESX/ESXi or vCenterPort assigning works like dynamicUsually only reserved for emergency/recovery/vCenter down
vSS to vDS Port MigrationsCreate vDSUplinksPortgroupsVLANsBreak vSS team and assign one uplink to vDSNetworking > Migrate Virtual Machine NetworkSelect source and destination; select VMs; migrateRemove vSS portgroups and switch as needed
ResourcesSean Crookston’s guide (updated on damiankarlson.com)Ed Grigson’s guideEric Sloof’s VCAP testKendrick Coleman’s VCAP-DCA pageTrainsignal TroubleshootingPersonal experience and practice, practice, practice

ProfessionalVMware VCAP BrownBag Section 2

  • 1.
  • 2.
    VCAP Blueprint Section2Objective 2.1: Implement & Manage Complex Virtual NetworksObjective 2.2 : Configure and Maintain VLANs, PVLANs and VLAN SettingsObjective 2.3: Deploy and Maintain Scalable Virtual NetworkingObjective 2.4: Administer vNetwork Distributed Switch Settings
  • 3.
    SNMP & MoreIPv6:Host Configuration > Networking > PropertiesNetQueue: Host Configuration > Advanced Settings > VMkernel/Boot; also use esxcfg-advcfgSNMPvCenter: Administration > vCenter Settings > SNMPNotification traps onlyESX/ESXiESXi only has VMware embedded SNMP agent. ESX has Net-SNMP & VMware embeddedCan only be managed through vicfg-snmp (remote CLI or vMA), which opens the appropriate firewall ports.Configure communities first, then destination
  • 4.
    Comparing vSS &vDSvSS (virtual standard switches) – same virtual switching technology we all know and loveSwitches defined on each host in a clusterPortgroup/VLAN/uplink configurations can be tediousvDS (virtual distributed switches) – introduced with vSphere 4.0Unified switch across hosts in a clusterSeparation of control and data planesExtensible through 3rd party switches (Cisco NK1v)Traffic stats available; shaping available at dvPortGroup and dvUplink portgroup levelsIngress traffic shaping
  • 5.
    Create & ManagevSwitchesFull range of vSSconfig needs supportedSome things only available through CLI, such as MTUPartial range of vDSconfig needs supportedSome things not available through CLI, such as PVLANs or creating dvPortGroupsTools are the usual suspects: esxcfg-vswitch, esxcfg-nics, esxcfg-vswif, esxcfg-route, esxcfg-vmknic, PowerCLI, vMA
  • 6.
    VLAN TaggingVST (virtualswitch tagging)VLANs defined at vSwitch level; physical switch accepts all or rangeEST (external switch tagging)VLANs are set to 0 at vSwitch; physical switch does all taggingVGT (virtual guest tagging)VM tags thru virtual NIC propertiesvSwitch set to 4095; physical switch accepts all or range
  • 7.
    Private VLANsPVLANs areVLANs within VLANs. Requires physical switch support.Original VLAN is the primary, additional VLANs are secondary VLANs.Secondary VLANs come in 3 flavors:Promiscuous VLANs have the same primary and secondary VLAN ID. Can talk to anyone in the same primary.Isolated VLANs can only talk to hosts in a promiscuous VLANCommunity VLANs only talk to each other, and to the promiscuous VLAN
  • 8.
    VLAN ConfigurationVLANs onvSS are defined at the portgroup levelPVLANs are defined at the vDS level first, then can be selected at the portgroup levelDistributed switches can have VLANs defined at the dvPortGroup level and the dvUplinkPortGroup levelvDS VLAN options“None” for EST“VLAN” for VST“VLAN Trunking” for VGT or multiple VST
  • 9.
    Uplink teamingRoute basedon IP hashRequires Etherchannel or equivalent. Req’d for FTExplicit failoverCan be used to balance load & provide availability in certain situationsRoute based on source MACRoute based on virtual port ID
  • 10.
    Network IsolationIsolate vMotion,NFS, iSCSI, FTSeparate storage from VM networksUse VLANsWhen teaming use physical NICs on different busses
  • 11.
    vDS Port BindingsStaticPortis assigned at all times, until the VM is removed from the port groupVM can only be connected through vCenterDynamicPort is assigned when VM is on and vmnic is connected, otherwise it is disconnected.VMs with dynamic ports can only be powered on/off through vCenterEphemeraldvPorts can be assigned through ESX/ESXi or vCenterPort assigning works like dynamicUsually only reserved for emergency/recovery/vCenter down
  • 12.
    vSS to vDSPort MigrationsCreate vDSUplinksPortgroupsVLANsBreak vSS team and assign one uplink to vDSNetworking > Migrate Virtual Machine NetworkSelect source and destination; select VMs; migrateRemove vSS portgroups and switch as needed
  • 13.
    ResourcesSean Crookston’s guide(updated on damiankarlson.com)Ed Grigson’s guideEric Sloof’s VCAP testKendrick Coleman’s VCAP-DCA pageTrainsignal TroubleshootingPersonal experience and practice, practice, practice

Editor's Notes

  • #3 Objective 2.1: IPv6, NetQueue, SNMP,VMware Direct Path I/O, Migrate from vSS to a full or hybrid vDS, Configure vSS & vDS using CLI, Identify Virtual Switch DetailsObjective 2.2: VLAN trunking, config PVLANs, identify VLAN configsObjective 2.3: NIC teaming to phy switch config, failover settings, explicit failover, port groups for network isolationObjective 2.4: CLI to configvDS, port bindings, port migration, troubleshoot configurations
  • #4 For ESX, use the VMware embedded SNMP agent. Net-SNMP doesn’t contain VMware-specific information. See the Basic System Administration guide for MIB load orders, and MIB descriptions.Vicfg-snmp -- There is no esxcfg equivalent, and no GUI functionality. If using both embedded and net-snmp, change the port on one of them, otherwise they’ll both attempt to use 161vicfg-snmp.pl --server <hostname> --username <username> --password <password> -c <com1,com2vicfg-snmp.pl --server host.example.com --username user --password password –t target.example.com@162/publicvicfg-snmp.pl --server <hostname> --username <username> --password <password> --enablevicfg-snmp.pl --server <hostname> --username <username> --password <password> --test
  • #5 VCAP lab based on 4.0, so no LBT or NIOCvSS tediousness – managing overrides, failover options, etchttp://vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf
  • #7 Avoid VLAN 1, that’s the default Cisco VLAN
  • #8 http://kb.vmware.com/kb/1010691
  • #10 Fault Tolerance will always send from the same virtual port ID and source MAC on the same host. Use IP Hash to distribute across multiple links.No physical switch config: use source MAC, source port or explicitWith physical switch config: use IP hash
  • #12 http://kb.vmware.com/kb/1022312
  • #13 Connectivity is only preserved if there are multiple uplinks, otherwise there will be a break in VM networkinghttp://kb.vmware.com/kb/1010612