ESX NIC labelling

Similar Questions

• BIOS of ESX, NIC and HBA driver Versions

  Hi friends,

  am intermiediate POWERCLI user and shell the scritping, please you colud help launch me script below.

  more information http://www.sandfordit.com/vwiki/ESX_Script_Extracts_and_Examples

  Thanks in advance,

  Aldo.

  Get versions of driver BIOS, NIC and HBA is dependent on what is reported to the ESX provider CIM material supplier. This script has been written using different servers of HP and well can work for them.

  # ===============================================================
  # ESX Inventory Getter
  # ===============================================================
  # Simon Strutt        November 2010
  # ===============================================================
  #
  # Version 1
  # - Initial Creation
  #
  # Version 2 - Dec 2010
  # - Added BiosVer, CpuCores, CpuModel, HbaModel, NicModel
  # - Bugfix: Corrected VC connection handling
  # - Removed dependency on obsoleted properties (from upgrade to PowerCLI v4.1.1)
  #
  # Limitations
  # - Tested on HP DL380 (G7), BL465 (G7), BL495 (G6), BL685 (G5)
  # - Supports 1 distinct HBA model, 2 distinct NIC models
  #
  # ================================================================
   
  $start = Get-Date
  $OutputFile = "ESXs.csv"
  $VC_List = "ESX-Check.csv"
  $UserFile = "User.fil"
  $PassFile = "Pass.fil"                           # Encrypted file to store password in
  $Results = @()
   
  # Include library files
  . .\lib\Standard.ps1
   
  Start-Transcript -Path ESX-Inventory.log
  Log "Started script run at $start"
   
  # Function-U-like ===================================================================================
   
  Function Get-NicDriverVersion ($view, $driver) {
      # Gets the CIM provided driver version (tallies up driver name with CIM software component)
      $result = ($view.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like $driver + " driver*"} | Get-Unique).Name
      $result = ([regex]::Matches($result, "(\b\d)(.*)(?=\s)"))[0].Value         # HP regex to extract "2.102.440.0" for example
      $result
  }
   
  # =================================================================================================== 
   
  # Load list of VC's
  try {
      $VCs = Import-CSV $VC_List
  } catch {
      Log "ERROR: Failed to load list of vC's"
      Exit
  }
   
  # Load password credential from encrypted file
  $pass = Get-Content $PassFile | ConvertTo-SecureString
  $user = Get-Content $UserFile
  $cred = New-Object System.Management.Automation.PsCredential($user, $pass)
   
  foreach ($vc in $VCs) {
   
      # Connect to VC
      try {
          Log("Connecting to " + $vc.vc)
          $VCconn = Connect-VIServer -Server $vc.vc -Credential $cred -errorAction "Stop"
      } catch [VMware.VimAutomation.ViCore.Types.V1.ErrorHandling.InvalidLogin] {
          Log("Unable to connect to vCentre, invalid logon error !!")
          Log("Abandoning further script processing in order to prevent potential account lockout.")
          Break
      } catch {
          Log("Unable to connect to vCentre - " + $_)
          Continue
      }
   
      # Get ESX objects
      Log("Getting list of ESXs to check on " + ($vc.vc) + "...")
      $ESXs = Get-VMHost -Server $vc.vc | Sort -property Name
      Log("Got list of " + ($ESXs.Count) + " ESXs to check") 
   
      ForEach ($ESX in $ESXs) {
          $row = "" | Select VC, Cluster, Name, IP, Version, Make, Model, BiosVer, CpuCores, CpuModel, HbaModel, HbaDriver, HbaDriverVer, Nic1Model, Nic1Driver, Nic1DriverVer, Nic2Model, Nic2Driver, Nic2DriverVer
          Log($ESX.Name)
   
          # Store objects which get re-used for efficiency
          $ESXview = Get-View -VIObject $ESX
          $VMHostNetworkAdapter = Get-VMHostNetworkAdapter -VMHost $esx 
   
          # Get the basics
          $row.VC = $vc.vc
          $row.Cluster = $ESX.Parent
          $row.Name = $ESX.Name.Split(".")[0]
          $row.IP =  ($VMHostNetworkAdapter | Where {$_.ManagementTrafficEnabled -eq "True" -or $_.DeviceName -like "vswif*" -or $_.Name -eq "vmk0"}).IP
          $row.Version = $ESX.Version + " (" + $ESX.Build + ")"
          $row.Make = $ESX.Manufacturer
          $row.Model = $ESX.Model
   
          # Now onto the more ESX version / hardware specific stuff (new versions of hardware will require further work below)
   
          # BIOS
          if ($ESXView.Hardware.BiosInfo) {     # Works on some systems 
              $row.BiosVer = $ESXview.Hardware.BiosInfo.BiosVersion + " " + $ESXview.Hardware.BiosInfo.ReleaseDate.ToString("yyyy-MM-dd")   # Need date for HP servers as they use same version no for diff versions!
          } else {
              $row.BiosVer = ($ESXview.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like "*BIOS*"}).Name
              $row.BiosVer = ([regex]::Matches($row.BiosVer, "[A-Z]\d{2} 20\d{2}-\d{2}-\d{2}"))[0].Value           # HP regex to extract "A19 2010-09-30" for example
          }
   
          # CPU info
          $row.CpuCores = $ESXview.Hardware.CpuInfo.NumCpuCores.ToString() + " (" + $ESXview.Hardware.CpuPkg.count + "x" + $ESXview.Hardware.CpuPkg[0].ThreadId.count + ")"
          $row.CpuModel = $ESX.ExtensionData.Summary.Hardware.CpuModel
   
          # HBA info (script assumes only one HBA model in use)
          $row.HbaModel = ($ESX.ExtensionData.Config.StorageDevice.HostBusAdapter | Where {$_.Key -like "*FibreChannel*"})[0].Model
          $row.HbaDriver = ($ESX.ExtensionData.Config.StorageDevice.HostBusAdapter | Where {$_.Key -like "*FibreChannel*"})[0].Driver     # Includes version for ESX3
          $row.HbaDriverVer = ($ESXview.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like "*" + $row.HbaDriver + "*"}).Name
          $row.HbaDriverVer = ([regex]::Matches($row.HbaDriverVer, "(\b\d)(.*?)(?=\s)"))[0].Value
   
          # NIC info (script only supports two distinct NIC types)
          $nics = $ESXview.Hardware.PciDevice | Where {$_.ClassId -eq 512} | Select VendorName, DeviceName, Id | Sort-Object -Property DeviceName -Unique
          if ($nics.count) {
              $row.Nic1Model = $nics[0].VendorName + " " + $nics[0].Devicename
              $row.Nic2Model = $nics[1].VendorName + " " + $nics[1].Devicename
   
              # Use PCI ID to match up NIC hardware type with driver name
              $row.Nic1Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics[0].Id}).ExtensionData.Driver
              $row.Nic2Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics[1].Id}).ExtensionData.Driver
   
              $row.Nic1DriverVer = Get-NicDriverVersion $ESXview $row.Nic1Driver
              $row.Nic2DriverVer = Get-NicDriverVersion $ESXview $row.Nic2Driver
           } else {
              # Annoyingly, $nics is not an array if there's only one NIC type, hence seperate handling
              $row.Nic1Model = $nics.VendorName + " " + $nics.Devicename
              $row.Nic1Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics.Id}).ExtensionData.Driver
              $row.Nic1DriverVer = Get-NicDriverVersion $ESXview $row.Nic1Driver
          }
   
          $Results = $Results + $row
      }
      Disconnect-VIServer -Server $VCconn -Confirm:$false
  }
  $Results | Format-Table *
  Log("Writing results to $OutputFile...")
  $Results | Export-Csv -path $OutputFile -NoTypeInformation
   
  Log("All completed")
  Stop-Transcript
  			 
  Hi Aldo,.
  As directed by the PM, I sent you, I genericised the script a bit more, it should be easier to use (no need to the Standard.ps1 file).  Similarly the name of your Center virtual servers don't need to be put in a separate file CSV file is
  To avoid having to create credentials files, delete the following lines...
  # Load password credential from encrypted file
  $pass = Get-Content $PassFile | ConvertTo-SecureString
  $user = Get-Content $UserFile
  $cred = New-Object System.Management.Automation.PsCredential($user, $pass)
  
  .. .and replace by (the script will prompt you for the user/pass)...
  $cred = Get-Credential
  
  Hope this gets you operational.
  Note that I found to NIC and driver versions HBA is quite unreliable using this script, that there is a lot of consistency in what is returned by ICM to hardware vendors.  More on the servers I tested with firmware HBA was never available.  A more reliable, but more complex method is to use PowerShell for SSH for your ESX, which has its own problems, but is another approach (when you do audits of system I tend to use both).  See below for more info...
  http://vblog.Strutt.org.UK/2012/04/ESX-HBA-and-NIC-driverfirmware-versions/
  All the best...
  Simon
  		   

• Installation of ESX NIC support

  install ESX 3.5 u4 VMWorkstation 6.5. Has encountered an error: Setup could not find supported network devices.

  It seems that my NETWORK card is not supported.

  Can anyone recommend inexpensive NIC for a desktop PC that will support the ESX?

  I guess that you configured wrong your ESX - VM.

  Use this ESX - VM as a guide

  http://sanbarrow.com/moa24/files/esxi_35.zip

  He'll find NICs during installation

  ___________________________________

  Description of the vmx settings: http://sanbarrow.com/vmx.html

  VMware-liveCD: http://sanbarrow.com/moa.html

• ESX NIC Teaming

  People

  This is the scenario. There are 8 NIC by each vminc0 to vmnic7 ESX Server

  VSWITCH0: vmnic0 and vmnic1: Console of Service:

  VSWITCH1: vmnic2 and vmic3: VMotion

  VSWITCH2: vmnic4 and vmnic5: Virtual Machine with four-port network works addressing VLAN 22,33,44,55

  VSWITCH3:vmnic6 and vmnic7: the Virtual Machine with four-port network works addressing VLAN 161 162

  Each of the NIC report to different physical switches as vmic0 to switch A, vmnic1 from B. The other NETWORK adapter are connected in the same way. Balancing policy is on the route in native function of virtual port ID.

  Issues related to the:

  1. If there are 3 VM connected to VSWITCH 3, my understanding is that the vswitch runs its own hash that assigns a physical NETWORK adapter to the virtual machine through which data can be receivced and transmitted. Fix? If I see the graphs in real-time networking there are streams of data on both the NIC

  2. but if you take Service Console or single VMotion NETWORK map is showing the data flow.

  This does not validate #1 said... Please advice

  Concerning

  Kumar

  Yes, that's how to set up my vm traffic switches.  I'll also trunk all my VLAN on all my interfaces, so I can spread the load as needed and to have a consistent configuration of physical switches.

  -KjB

  Don't forget to leave points and mark messages useful/correct.

• Programmatically create a free label on the front

  To make the appearance of my nicer VI, I add a few free labels for a tab on the front panel control.

  Then edit the free text in the tab control and by placing a free text on the block schema works very well with the attached VI. (Note: put the two in the same folder)

  However if I am trying to add a label free control tab with Labview, the following code generates error 1060 "LabVIEW: object cannot contain (clean) specified object.»

  

  So now I'm wondering what I need to to to add text to the front with the help of scripts of VI.

  Hope you can help.

  @Yamaeda

  On your 2nd thought: I do not think I need to add the label to the table decorations or is it possible, given that the setting is "read only".

  @tst

  You got the indirect answer. First of all, I created the example below to check if I could create a color of the tab box

  

  2nd I started browsing trough style options to see if I could find something that would allow me to bring another form of decoration. And by chance I found the style of "Label (System)" (ID = 21961). So the following code generates a nice label on the tab and solved my problem.

  

• Information about the host material with information on the nic and HBA drivers

  Can someone help me complete the script below. I can't able to get information from HBA and driver for the card.

  
  Get-Datacenter | % {  
    $datacenter=$_
    Get-VMhost -Location $datacenter | Get-VMHostHBA -Type FibreChannel | where {$_.Status -eq "online"} | 
    Select @{N="Datacenter";E={$datacenter}},@{N="VMHost";E={$_.VMHost.Name}},@{N="HostName";E={$($_.VMHost | Get-VMHostNetwork).HostName}},@{N="ver";E={$_.VMhost.version}},@{N="Manf";E={$_.VMhost.Manufacturer}}, @{N="Hostmodel";E={$_.VMhost.Model}},@{Name="SerialNumber";Expression={$_.VMhost.ExtensionData.Hardware.SystemInfo.OtherIdentifyingInfo |Where-Object {$_.IdentifierType.Key -eq "Servicetag"} |Select-Object -ExpandProperty IdentifierValue}},
    @{N="Cluster";E={
          if($_.VMHost.ExtensionData.Parent.Type -ne "ClusterComputeResource"){"Stand alone host"}
          else{
              Get-view -Id $_.VMHost.ExtensionData.Parent | Select -ExpandProperty Name
          }
        }},Device,Status,@{N="WWN";E={((("{0:X}"-f $_.PortWorldWideName).ToLower()) -replace "(\w{2})",'$1:').TrimEnd(':')}},@{N="HBA Model";E={($_.VMhost | get-vmhosthba -Type FibreChannel | where {$_.Status -eq "online"} | select-object -ExpandProperty Model  ) | Get-Unique}},
        @{N="fnicdriver";E={$esxcli.software.vib.list() | ? {$_.Name -match ".*$hbadriver.*"} | Select -Expand Version}}
        @{N="Fnicvendor";E={$esxcli.software.vib.list() | ? {$_.Name -match ".*$hbadriver.*"} | Select -Expand Vendor}},
        @{N="enicdriver";E={$esxcli.system.module.get("enic").version}}
       @{N="Enicvendor";E={$esxcli.software.vib.list() | ? {$_.Name -match ".$net.*"} | Select -Expand Vendor}}
  } 
  
  

  Thank you correct me with your previous posts, I had made some changes to get information on the correct provider for FC and network cards, now it's show desired output.

  Get-Datacenter | % {
        $datacenter=$_
        foreach($esx in Get-VMhost -Location $datacenter){
          $esxcli = Get-EsxCli -VMHost $esx
          $nic = Get-VMHostNetworkAdapter -VMHost $esx | Select -First 1 | select -ExpandProperty Name
          $hba =Get-VMHostHBA -VMHost $esx -Type FibreChannel | where {$_.Status -eq "online"} |  Select -First 1 |select -ExpandProperty Name
          Get-VMHostHBA -VMHost $esx -Type FibreChannel | where {$_.Status -eq "online"} |
          Select @{N="Datacenter";E={$datacenter.Name}},
                  @{N="VMHost";E={$esx.Name}},
                  @{N="HostName";E={$($_.VMHost | Get-VMHostNetwork).HostName}},
                  @{N="version";E={$esx.version}},
                  @{N="Manufacturer";E={$esx.Manufacturer}},
                  @{N="Hostmodel";E={$esx.Model}},
                  @{Name="SerialNumber";Expression={$esx.ExtensionData.Hardware.SystemInfo.OtherIdentifyingInfo |Where-Object {$_.IdentifierType.Key -eq "Servicetag"} |Select-Object -ExpandProperty IdentifierValue}},
                  @{N="Cluster";E={
                      if($esx.ExtensionData.Parent.Type -ne "ClusterComputeResource"){"Stand alone host"}
                      else{
                          Get-view -Id $esx.ExtensionData.Parent | Select -ExpandProperty Name
                      }}},
                  Device,Model,Status,
                  @{N="WWPN";E={((("{0:X}"-f $_.NodeWorldWideName).ToLower()) -replace "(\w{2})",'$1:').TrimEnd(':')}},
                  @{N="WWN";E={((("{0:X}"-f $_.PortWorldWideName).ToLower()) -replace "(\w{2})",'$1:').TrimEnd(':')}},
                # @{N="Fnicvendor";E={$esxcli.software.vib.list() | ? {$_.Name -match ".*$($hba.hbadriver).*"} | Select -First 1 -Expand Vendor}},
                  @{N="Fnicvendor";E={$esxcli.hardware.pci.list() | where {$hba -contains $_.VMKernelName} |Select -ExpandProperty VendorName }},
                  @{N="fnicdriver";E={$esxcli.system.module.get("fnic").version}},
                  @{N="enicdriver";E={$esxcli.system.module.get("enic").version}},
                 # @{N="Enicvendor";E={$esxcli.software.vib.list() | ? {$_.Name -match ".net.*"} | Select -First 1 -Expand Vendor}}
                   @{N="Enicvendor";E={$esxcli.hardware.pci.list() | where {$nic -contains $_.VMKernelName} |Select -ExpandProperty VendorName }}
                   #@{N="Enicvendor";E={$esxcli.network.nic.list() | where {$vmnic.name -eq $_.vmnic1} | select -First 1 -ExpandProperty Description }}
          }
      } 
  

  =================

  Output:

  -------

  

• NIC & Storage Driver Version and Firmware

  Hello

  I would like to know powercli average to determine the firmware revision, version, and NETWORK/storage card driver name. I can take this info via

  esxcfg-info takes so long

  ethtool-i vmnic0

  Thank you

  The seller and the device to take a look at my post to appoint this material .

  According to the HW you use, you can try using the CIM for the information.

  Take a look at the BIOS of ESX, NIC and HBA driver Versions, which shows a way to do with HP hardware.

• Issue between Cisco and ESX switch

  It is a small deployment with an ESX Server running a Windows Small Business SERVER 2003.

  ESX server has 2 network cards, previously a NIC was connected to a small FastEthernet Switch netgear and all workstations have been working on it.

  I replaced the netgear with a Cisco WS-C2960S-24TS-S and the field still works fine, the problem is that I can't connect to the service console or the VI client from a computer connected to the switch.

  I can't ping the IP switch ESX service console and also can not ping the switch since the service console.

  Switch and ESX console can ping the Windows Virtual Machine and the virtual machine can ping both of them. Therefore, I can get to the VI client via Wirtual Machine (not the best scenario to manage one of its right VMS ESX host?)

  I don't know what the problem is, but it sounds a lot there is a problem with the configuration of port / vlan on the cisco switch.

  Can a Cisco expert help out me here?

  Here are some details of the configuration.

  Port group service Console and the port Vm group do not use no matter what config VLAN on the ESX Server.

  CONFIG NETWORK ESX

  # esxcfg - NICS - l

  Name PCI Driver link speed Duplex MAC address MTU Description

  vmnic0 0b: 00.00 bnx2 up to 1000Mbps Full 00: 1a: 64:b6:06:92 1500 Broadcom Broadcom NetXtreme II BCM5709 1000Base-T Corporation

  vmnic1 0b: 00.01 bnx2 up to 100 Mbit/s Full 00: 1a: 64:b6:06:94 1500 Broadcom Broadcom NetXtreme II BCM5709 1000Base-T Corporation

  vusb0 nickname cdc_ether Up 0Mbps 02: 1a: 64:b6:06:99 half 1500 unknown unknown

  # esxcfg - vswitch - l

  Switch name Num used Ports configured Ports MTU rising ports

  64 6 64 1500 vmnic0 vSwitch0

  Name PortGroup VLAN ID used rising Ports

  PORTS 0 1 vmnic0 VM GROUP

  0 1 vmnic0 Console service

  Switch name Num used Ports configured Ports MTU rising ports

  64 3 64 1500 vmnic1 vSwitch1

  Name PortGroup VLAN ID used rising Ports

  BIG POND ADSL 0 1 vmnic1

  # esxcfg - vswif - l

  Port Group/DVPort IP IP family name address Netmask Broadcast Enabled TYPE

  vswif0 Service Console IPv4 192.168.0.100 255.255.255.0 192.168.0.255 true STATIC

  # ifconfig

  Lo encap:Local Loopback link

  INET addr:127.0.0.1 mask: 255.0.0.0

  RACE of LOOPING 16436 Metric: 1

  Dropped packets: 1310258 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 1310258 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:0

  RX bytes: 4531037961 (4.2 GiB) TX bytes: 4531037961 (4.2 GiB)

  vmnic0 Link encap HWaddr 00: 1a: 64:B6:06:92

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 94579247 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 99834049 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 127899970453 (119.1 GiB) TX bytes: 19056702095 (17.7 GiB)

  Interruption: 209 memory: 92000000-92012100

  vmnic1 Link encap HWaddr 00: 1a: 64:B6:06:94

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 3585973 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 3018690 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 2304776001 (2.1 GiB) TX bytes: 1021855293 (974,5 MiB)

  Interruption: 217 memory: 94000000-94012100

  vswif0 Link encap HWaddr 00:50:56:45:43:6 C

  INET addr:192.168.0.100 Bcast:192.168.0.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 367248 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 126300 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 33905320 (32.3 MiB) TX bytes: 154760077 (147,5 MiB)

  vusb0 Link encap HWaddr 02: 1a: 64:B6:06:99

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 341442 errors: 0:0 overruns: 0 frame: 0

  Dropped TX packets: 0 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 26973918 (25.7 MiB) TX bytes: 0 (0.0 b)

  CISCO SWITCH CONFIGURATION

  Port on which the ESX nic is connected to:

  interface GigabitEthernet0/1

  switchport mode trunk

  switchport nonegotiate

  switchport port-security

  aging of the switchport port security 2

  security violation restrict port switchport

  inactivity of aging switchport port-security type

  macro description cisco-computer desk

  spanning tree portfast

  spanning tree enable bpduguard

  !

  ******************************************

  CONFIGURATION OF VLAN

  !

  interface Vlan1

  IP 192.168.0.253 255.255.255.0

  !

  interface Vlan2

  Description management Vlan

  no ip address

  !

  interface Vlan10

  Test description Vlan

  IP 192.168.121.253 255.255.255.0

  !

  Default IP gateway 192.168.0.1

  Any help would be appreciated.

  Thank you

  I think I've seen this before. I'm not super familiar with this switch, but I think that the problem is with cisco-computer office macro.

  Try using the macro switch cisco instead since you are addressing a vSwitch on the other end. You can always check the mac address table and see if your Mac to the vswif (service console) make their appearance. If they are not then appear this is an inconsistency in the port between the Cisco Switch and vSwitch.

  Louis

• ESX 3.5, iSCSI and Cisco 3750

  I have a pretty basic or newly created three ESX environment 3.5 servers, switches from NetApp for storage and a battery (two) of Cisco 3750.

  IM using for my data vmfs iSCSI store and will only run about 15-20 VM at best. This isn't a great environment but I want to plan for future growth and I won't get a second chance to get the stack of 3750 correct configuration.

  I have 2 GB ethernet by the host to the storage and 4 GB of my NAS ethernet ports all converge on the stack of Cisco.

  Can someone point me to a cisco config guide or the white paper which can guide me for the installation to take advantage of the cross battery etherchannel and balancing of load on the side of esx?

  Suggestions?

  Experiences?

  Advice?

  Much appreciated in advance.

  Hello.

  While it's not hardware Cisco, Scott Lowe has some excellent articles on this subject.

  http://blog.scottlowe.org/2007/06/13/Cisco-link-aggregation-and-NetApp-vifs/

  http://blog.scottlowe.org/2008/10/08/more-on-VMware-ESX-NIC-utilization/

  Good luck!

• Pane (Advanced) search for Windows 7?

  I've been using Windows 7 for a while now and love it!

  However, when I was preaching to my family and my friends, they asked me if the search pane advanced (that we had running XP) is back in Windows 7.

  Of course, with the advanced Windows search query syntax (let's call this AQS), we are able to achieve what could research advanced and much more. But then, they have made a very good point:

  Why I (they) should learn/remember a special syntax to run a research complex, when the advanced XP search pane was so much easier? And I kinda agree with them.

  For example, without looking at the documentation of AQS, how many of you can come immediately with the unique search criteria for:

  1. all files jpg and png (only)
  2. who are in e:\images and d:\images, and f:\dir\images
  3. without recursing into all subdirectories
  4. who are more than 10 KB
  5 and has been created between December 25 and January 1?

  Anyone got an answer for this?

  Or is there some kind of advanced research as in Outlook? Choose from a list of filters the search/filter field, and you get a nice label/text box to type in?

  I did some research and it seems that he has only partial (limited) support for this. For example, in the music library, you can only add filters to the Album, artist, Genre, length; Documents: Authors, Type, Date modified, size; etc.

  And when you are not in a folder on an external drive of library, for example, only filters that you can add are updated and the size.

  Are there ways to add more filters? Or are we limited either: 1) based on the filters that Windows 7 * THINK * we need, or 2) loop down and memorize the AQS?

  [Edit]
  Here's another story: I was explaining to my mother how you could build a search criteria AQS, and she pointed to (paraphrasing), "why he tries to search when you are not actually type? Why not have a search button that starts the search only when you're ready to? »

  It's just me, but how do you even get here?

  My "search" stands usually just before I can even START adding a filter. That initiate original research of a new Explorer window? Or start you looking for the start icon, and then add a filter... or...?
  For me, the search is missing... 99% of my data is on a network share, and it does not find it, even if I'm in the folder that I'm looking for

• Question of vlan SG200 (ESXi VSA config)

  Hello! I have three switches SG200-26, and I have also two hosts ESXi I want to connect exactly as shown on the attached map of 'best practices' by VMware.

  

  Even if I created the VLAN in the SG200 and I put the two VLANS (508 and 608), as authorized these ports (where my ESX NIC are connected), I can't host ping host 1 2 when the configuration of their NETWORK interface card to use 608 VLAN.

  Am I missing something? My IP is all in the 192.168. network and the only reason for which I need a VLAN is to separate the traffic of the VSA backend internally, only these two hosts will use the VLAN. So I think that I don't have to create virtual interfaces on my router because this is the case, is my understanding correct?

  Also sending my switch config screenshot below... 3 switches all have the latest firmware.

  

  Any ideas what to change to make it work on the SG200 would be appreciated!

  VMware also has that Protocol VLANS on the physical switch must be 802. 1 q, not of ISL, someone knows which one uses my SG200-26?
  In addition, the only requirements is that my two hosts:

  • Are in the same subnet.
  • Have static IP addresses.
  • Have the same default gateway configured.

  Thank you for your time!

  Alex

  Hi Alex,

  My switch supports 802. 1 q, your config switch seems ok at this point.

  Here are some of my thoughts that I see the announcement and I'm a bit confused.

  What worries me is the configuration on the wall of sound, or the router, they are not spread of VLAN between ports on the router?

  • You're not VLAN 508 multiplication and 608 via the router, so I guess you have two network interfaces on the router, one for each of the two switches as shown in the first diagram... You can expand on the description of the network configuration of the router.
  • You are using two NICs for each host and spreading with tag vlan packets for VLAN 508 and 608 of each NETWORK card?  But the pattern of reference would indicate that you have four physical network interface cards to each HOST.
  • If so, I suppose that HOST servers are connected with the GE15 and switch 3 and GE16 and GE2 GE3 switch 1

  Nope, I want to talk to you, please send us your phone coordinated with this validation URL

  dhornste at cisco.com remove the spaces next to the 'at' and replate the to by @.

  Best regards, Dave

• Need a script to create standard vSwitch with virtual and several computer port group VLAN

  I want to create standard vSwitch for all hosts in the cluster for virtual machine port group and add one or more groups of ports VLAN for the same standard vswitch.

  Kind regards

  Shan

  Try something like this

  $clusterName = "mycluster.

  $nics = "vmnic0", "vmnic1.

  $vlans = 123456789

  foreach ($esx in (Get-Cluster-name $clusterName |)) Get - VMHost)) {}

  $sw = New - VirtualSwitch - name swX - VMHost $esx - Nic $nics - confirm: $false

  $vlans | %{

  New-VirtualPortGroup-name "PG $($_)" - VLanId $_ - VirtualSwitch $sw - confirm: $false

  }

  }

• vNetwork Distributed Switch - School me please!

  Can someone give me a description as to what is happening with a configuration switch vNetwork?  My areas of interest are:

  What happens when I add an ESXi host management network interface active to a distributed switch?

  How are the hosts of ESXi with several NIC supposed to be configured on the physical network?

  Should I have several ESXi host WHAT NIC connected to VLAN separate physics?

  When and how to use groups of dvPort?

  What is the best practice to deploy a vNetwork Distributed Switch in a production environment existing?

  What IP addresses should the virtual machine which will connect to the switch vNetwork have?  Real routable IP or a private beach that lives on the only host of ESXi?

  I have ESXi setup guide and understand 'how' do these things but don't understand what happens when treating several VLAN virtual physics and ESXi hosts being not connected to all local networks.  I tried to set this up a while ago and had a lot of questions while losing connectivity to multiple hosts ESXi and all virtual machines running on the hosts on the network.  I don't want to repeat this mistake!

  You don't have to use the junction of your physical switch ports, it is usually best if you do. When you use the junction ports and assign several VLANS to that port, that means that the virtual switch (standard or distributed) can then talk to the physical switch using assigned VLANs. Which means that a single physical NETWORK card within an ESX host can talk to several VLANs, if you do not use trunking then you can only assign a VLAN by ESX NIC that is not very effective.

  Most of the vSwitches converses with several VLANs, but will have only one or two uplinks, in this scenario, it is almost always necessary to use port trunking.

  Does that answer your question?

• Circuits on the physical virtual network

  Hello

  I'm trying to implement trunking to route traffic to vlan tagged from the virtual to the physical.

  I have a cisco 2900 2 layer switch series.

  I created a virtual swtich and have only 1 portgroup for now. The portgroup must have 4 VLANS. I have configured the parameter vlan in the portgroup 4.

  On the physical switch I configured the port that connects to the esx NIC that the virtual switch uses an uplink as follows:

  conf t

  int fa0/7

  switchport mode trunk

  No tap

  When I use sh int trunk command I can see that the port is certainly the installer on the trunk and is using 802. 1 q encapsulation.

  I joined a virtual computer to the vSwtich and the portgroup which is put in place for the vlan 4

  I have setup the next physical port on vlan 4 as an access port.  and connected to a laptop

  The laptop computer and the virtual computer are in the same subnet, but they cannot ping each other.  Later, I'll add other exchanges to other VLANs to the swtich, but I want to get the connectivity on the trunk port before proceeding.

  Anyone know what I am doing wrong?

  Thanks for any help

  There are a few additional settings, you may need to configure the physical port. Take a look at http://kb.vmware.com/kb/1004074 for an example of configuration of VLAN.

  André

• Microsoft iSCSI Initiator with MPIO software

  Use the Microsoft MPIO Software iSCSI initiator installed from an OS supported by VMware guest? Can you tell me analysis that supports this or not?

  Setup would be:

  (1) FAS of NetApp with two Ethernet ports, two IP addresses and two VLANS

  (2) guest operating system (2000, 2003, 2008) with the Microsoft iSCSI initiator installed/enabled and configured for failover or MPIO load balancing

  (3) don't know how to put in place the ESX network, either:

  (i) two physical ESX NIC physical, connected to two different physical switches and two vSwitches, each physical NETWORK adapter on the VLANS separated mentioned in point (1). Guest operating system with two network cards for, each vNIC connected to the separate vSwitches - MPIO configured to load balance/failover.

  (II) active/passive team ESX physical NIC (not the choice here for active/active), connected to a unique vSwitch, both VLAN present at vSwitch. Guest operating system with two network adapters, each vNIC connected to the separate vSwitches - MPIO provisions set up two paths to the storage.

  Other ideas would be appreciated, thanks.

  Hi Tao2,

  Welcome to the forum.

  NetApp site information: "MPIO is not supported in a guest OS." ( http://now.netapp.com/NOW/knowledge/docs/snapdrive/relsnap62/html/software/admin/GUID-5341E2D6-4BFD-41E1-8AAE-0D643D2596EC.html ).

  Most of the time, we ensure the redundancy of storage iSCSI network through the VMware network design:

  • a vNic dedicated for storing the virtual machine

  • vNic attached to a vSwitch with two physical in failover mode maps

  It may be useful

  Concerning

  Franck