Translate

Total Pageviews

My YouTube Channel

My YouTube Channel

Thursday, 23 January 2014

Configure Auto-Refresh in vSphere Web Client Server 5.5

A common piece of feedback that I have heard regarding the vSphere Web Client experience is that it does not automatically refresh the screen. This is a change from the vSphere C# Client where it will automatically refresh the inventory, but of course there is some overhead associated with this refresh as it needs to pull the latest data from the vCenter Server. However, with the latest vSphere Web Client 5.5, you can now enable auto-refresh using an advanced configuration (by default it is disabled). Before you enable this, do note that this can alter the performance of your environment and be aware this will prevent the session from automatically logging out if you have configured an idle session timeout.

To enable auto-refresh, you will need to locate the following configuration file /var/lib/vmware/vsphere-client/webclient.properties on the VCSA (there should also be an equivlent on Windows version of vSphere Web Client Server)

By default the auto-refresh is disabled, to enable it, you will need to un-comment the following configuration parameter and set the number of seconds to auto-refresh:

refresh.rate = # of seconds
Posted by at No comments:

vSphere Options and Requirements


This table summarizes the available options and requirements:

Storage vMotion (SvMotion)VirtualCenter 2.5vCenter Server 4.x/5.xRDM virtual compatibility modeRDM physical compatibility modeThe virtual machine can  change hostsVirtual machine Snapshots
ESXi/ESX 3.5Supported using the remote CLI script:
svmotion.pl		YesYesYesNoVirtual machine must not have snapshots while performing SvMotion.
ESXi/ESX 4.xNot supported: VirtualCenter 2.5 cannot manage ESXi/ESX 4.x hosts.YesYesYesYesVirtual machine must not have snapshots while performing SvMotion.
ESXi 5.0 and higherNot supported: VirtualCenter 2.5 cannot manage ESXi 5.0 and higher hosts.Only vCenter 5.xYesYesYesYes
Posted by at No comments:

Editing virtual machine and host custom attributes, notes and annotations (1005720)

Symptoms

This article provides steps to edit the custom attributes and annotations of a virtual machine or host.

Resolution


You can use custom attributes to associate your own information with the resources in VirtualCenter. After you create the attributes, set their values on each virtual machine or managed host, as appropriate. The values are stored with VirtualCenter. You can then use the new attributes to filter information about your virtual machines and managed hosts. If you no longer need the custom attribute, remove it. A custom attribute is always a string.
You can also add annotations to a virtual machine to add a description or other comments about the virtual machine or host.
You can set custom attributes for a virtual machine or host from the object's Summary tab. You can also define Global attributes, which are not specific to a particular type of managed object. For more information on defining Global attributes, see Using Custom Attributes in theBasic Administration Guide.
Custom attributes have these conditions:
  • VMware Infrastructure (VI) Client must be connected to VirtualCenter or the ESX host.
    Note: You can add annotations when connected to either VirtualCenter Server or to any host, but you can only define attributes when connected to VirtualCenter Server.
     
  • Minimum required privileges:
    • Global > Manage Custom Attributes
    • Global > Set Custom Attributes
    • Virtual machine > Configuration > Rename
To edit custom attributes and annotations for a virtual machine or host:
  1. Select the virtual machine or host in the inventory.
  2. Click the Summary tab for the virtual machine or host.
  3. In the Annotations box, click the Edit link.
  4. To add an attribute:
    1. Click Add.
    2. In the Name text box, enter the name of the attribute.
    3. In the Type drop-down list, select the attribute type.
    4. In the Value text box, enter the value to give to the attribute for the selected object.
    5. Click OK.After you define an attribute on a single virtual machine or host, it is available to all objects of that type in the inventory. However, the value you specify is applied only to the selected object.
       
  6. To edit the value of an attribute that is already defined, double-click the Value field for that attribute and enter the new value.
  7. To add annotations, enter text in the Notes text box.
  8. Click OK to save your changes.
How to Configure Annotations in vSphere Web Client


Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005720
Posted by at No comments:

Wednesday, 22 January 2014

Virtual Disk 'X' is a mapped direct access LUN that is not accessible (1016210)

Symptoms

  • Powering on or migrating (vMotion) a virtual machine with a raw device mapping (RDM) may fail with the error:

    Virtual Disk 'X' is a mapped direct access LUN that is not accessible
  • When checking the VML identifier for a RDM on two or more ESX hosts, you see they are not referring to the same VML ID (this is known as a VML mismatch).

Purpose

This is an informational event which indicates that the host attempting to start or receive the virtual machine cannot access the device (LUN) backing the raw disk mapping.

For more information on raw device mappings, see the Raw Device Mapping section of the ESX/ESXi Server Configuration Guide for your version.

Resolution

A raw device mapping file contains metadata, specifically SCSI vital product data (VPD) page 0x83, for uniquely identifying a device. A host attempting to access the physical LUN reads the mapping file metadata, and searches the devices known to the host for a LUN with the same VPD page 0x83 information.
The contents of SCSI VPD page 0x83 should match when requested by all hosts in a vSphere cluster, and the RDM should be accessible by all hosts in the cluster. However, discrepancies in device presentation between hosts in a cluster may lead to different hosts receiving different contents for VPD page 0x83 for the same device. In this case, hosts which did not create the RDM mapping file may be unable to locate the raw device mapping LUN when powering on or migrating a virtual machine.
Note: Cold migrations of powered off virtual machines do not require access to the raw device mapping. Symptoms may be noticed after cold migration, when the virtual machine is powered on.

Identifying mis-presented devices using VML identifiers

The VPD page 0x83 information, when available, forms the basis of the unique VML identifier which the ESX/ESXi host assigns to each storage device. This VML identifier should be consistent for a given device across each host in a vSphere cluster.
Identify the device being used for a raw device mapping by its VML identifier, such as by reviewing the contents of /vmfs/devices/disks/, on each host in a cluster. Compare the VML identifier obtained for the device on each host. For more information, see Identifying disks when working with VMware ESX (1014953).
The highlighted sections of the VML identifiers in this example do not match between the hosts, indicating a LUN with different presentation to each host:
  • Host 1:

    vml.02000500006006048000019010406353303035344553594d4d4554 -> naa.60060480000190104063533030353445
  • Host 2:

    vml.02004d00006006048000019010406353303035344553594d4d4554 -> naa.60060480000190104063533030353445
Note: In the above example, the highlighted value equates to the device's LUN number represented in hexidecimal. On host 1, the LUN has been presented as LUN 5, and on Host 2, it has been presented as LUN 77.

Resolution

This issue is resolved in vCenter Server 5.5. You can download the latest vCenter Server release from the VMware Download Center.
 
To resolve this issue in earlier vCenter Server releases, LUN presentation (including LUN numbering) should be made consistent for every host participating in a cluster that could run the virtual machine. The raw device mapping metadata file should be consistent with that presentation, and vCenter Server's cache of this information should be accurate.

Segmented cluster:

If one segment of a vSphere Cluster has correct presentation of the LUN being used for a raw device mapping, but other segments do not, the virtual machine will operate correctly only within the segment with correct presentation. Correct the presentation in the nonworking segment(s):
  1. Unpresent the LUNs from the hosts with incorrect presentation. For more information, see Removing a LUN containing a datastore from VMware ESXi/ESX 4.x (1029786) and Unmounting a LUN or detaching a datastore/storage device from multiple ESXi 5.x hosts (2004605).
  2. Represent the LUNs in the same manner as the working hosts. For more information, engage your storage array vendor.
  3. Rescan to pick up storage changes. For more information, see Performing a rescan of the storage (1003988).
  4. Verify that the host LUN ID matches on all the hosts in the cluster that have access to that LUN.
  5. Verify that the VML ID for the device matches on all the hosts in the cluster.
  6. If the host LUN ID matches and the VML ID does not match:

    1. Unpresent the LUN on the host where the VML ID does not reflect the correct host LUN ID. For more information, seeRemoving a LUN containing a datastore from VMware ESXi/ESX 4.x (1029786) or Unmounting a LUN or Detaching a Datastore/Storage Device from multiple ESXi 5.x hosts (2004605).
    2. Perform a rescan, then represent the LUN. Verify that the VML ID matches.
  7. Attempt migration of the virtual machine from the working segment to the corrected hosts.

Whole cluster:

If a virtual machine cannot be started on any host in a vSphere Cluster, the presentation to each host may differ from the VPD Page 0x83 information stored within the raw device mapping file. Recreate the mapping file:
  1. Power down the virtual machine.
  2. Right-click the virtual machine and click Edit Settings.
  3. Make note of the raw device mapped disks which are attached to the virtual machine.
  4. Remove the raw device mapped disks from the virtual machine.
  5. Click OK.
  6. Right-click the virtual machine and click Edit Settings.
  7. Click Add to re-add the previously removed raw device(s).
  8. Click OK.
  9. Power on the virtual machine and re-attempt the operation which previously failed.

vCenter Server cache:

The vCenter Server maintains a cache of storage topology information for virtual machines. If this information has become out of sync with the presentation, power operations or migrations initiated from vCenter Server may fail. Remove the affected virtual machine from inventory and re-register it to clear the cached information:
  1. Power down the virtual machine.
  2. Right-click the virtual machine and remove it from the inventory.
  3. Re-register the virtual machine to the inventory. For more information, see Registering or adding a virtual machine to the inventory (1006160).
  4. Power on the virtual machine and retry the operation which previously failed.
Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016210
Posted by at No comments:

Two Available VCP5-DCV Exams

      
On January 22, we released a new exam to qualify candidates for the VMware Certified Professional 5 - Data Center Virtualization (VCP5-DCV) Certification.
This new exam (exam code VCP550) is based on vSphere v5.5, where the existing exam (exam code VCP510) is based on vSphere 5.0/5.1.
Passing either of these exams will earn VCP5-DCV certification if you have also taken an approved qualifying course.

vSphere 5.5 Based Exam – Exam Code VCP550

vSphere 5.0/5.1 Based Exam – Exam Code VCP510



Approved Courses
Attendance at one of these courses, in combination with passing either the VCP510 or VCP550 exam, is required to earn VCP5-DCV certification.
The following courses are appropriate for general candidates.
The following courses are only recommended for candidates who have significant experience with VMware vSphere 5.x technology and a high level of comfort with the exam objectives.
The following courses fulfill the course requirement only for candidates who have already achieved the VCP4-DCV certification or have attended a VCP4-DCV qualifying class.
Source:-
http://mylearn.vmware.com/mgrReg/plan.cfm?plan=45082&ui=www_cert
Posted by at No comments:

Tuesday, 21 January 2014

vCenter Server Appliance 5.5 root account locked out after password expiration (2069041)

Symptoms

  • You are unable to log into the root account for the vCenter Server Appliance (vCSA).
  • The root account for the vCSA is locked.

Purpose

This article provides instructions on preventing the forced lockout of the root account and on unlocking a locked root account.

Cause

The 5.5 release of the vCenter Server Appliance (vCSA) enforces local account password expiration after 90 days by default. This policy locks out the root account when the password expiration date is reached.

Resolution

This behavior affects vCenter Server Appliance 5.5.

Prevent forced lockout when the root account is still active

If the root account is still accessible through the vCSA console or via the secure shell (SSH), you can prevent this issue from occurring by modifying the /etc/cron.daily/pass-expiration script.

To prevent the forced lockout when the root account is still active:

  1. Log in to the vCSA as the root user.
  2. Open the /etc/cron.daily/pass-expiration script in a text editor.
  3. Replace the commands at the bottom of the script to replace the forced lockout with a forced password change:

    1. Delete these commands:

      # disable the password if it's time and not already done.
      # don't rely on the pam account facility. prepend an x in the shadow file.
      if [ $TODAY -ge $DEADLINE ] && ! grep -q 'root:x' $SHADOW; then
         sed -e 's/^root:\(.*\)/root:x\1/' $SHADOW -i
      fi
    2. Enter these commands:

      # force a password change for root if we've reached the password expiration date.
      # pam.unix2 doesn't do this the way we would like, so we do this instead.
      if [ $TODAY -ge $DEADLINE ]; then
         chage –d 0 root
      fi
  4. Save and close the file.

Unlocking a locked out root account

If the root account is not accessible via the console, the secure shell, and the Virtual Appliance Management Interface (VAMI), the root account has been inactivated due to password expiration. To reactivate the root account, the vCSA must be rebooted and the kernel option modified in the GRUB bootloader to obtain a root shell.

To reactivate the root account:

  1. Reboot the vCSA using the vSphere Client.
  2. When the GRUB bootloader appears, press the spacebar to disable autoboot.



    Note: If the time between when you power on the virtual machine and when it exits the BIOS or EFI and launches the guest operating system is too short, you can adjust the delay. For more information, see Delay the Boot Sequence in the vSphere Client in thevSphere Single Host Management guide.
  3. Type p to access the appliance boot options.
  4. Enter the GRUB password.

    Note:
    • If the vCSA was deployed without editing the root password in the Virtual Appliance Management Interface (VAMI), the default GRUB password is vmware.
    • If the vCSA root password was reset using the VAMI, then the GRUB password is the password last set in the VAMI for the root account.
  5. Use the arrow keys to highlight VMware vCenter Server Appliance and type e to edit the boot commands.


  6. Scroll to the second line displaying the kernel boot parameters.


  7. Type e to edit the boot command.
  8. Append init=/bin/bash to the kernel boot options.


  9. Press Enter. The GRUB menu reappears.
  10. Type b to start the boot process. The system boots to a shell.
  11. Reset the root password by running the passwd root command.
  12. Restart the appliance by running the reboot command.
  13. Important: Follow the instructions in the Prevent forced lockout when the root account is still active section of this article to prevent future root account lock out and retain password expiration functionality.

Additional Information

The vCSA allows you to establish your own password expiration and warning email policies by using the Admin tab of the Virtual Appliance Management Interface (VAMI).



By default, the password expiration on the local root account in the vCSA is set to 90 days after the password has been changed. This typically occurs at first boot. If the password is not changed on installation, there is a 90-day period before expiration.

Email addresses configured in the Admin tab in the VAMI (https://IP_address:5480 or https://VAMI_host_name:5480) receive email notifications each day for seven days prior to password expiration. The email settings, such as relay SMTP server, are configured through the vSphere Client in the vCenter Server mail settings.
Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2069041
Posted by at No comments:

Sunday, 19 January 2014

Devices deprecated and unsupported in ESXi 5.5 (2056935)

Purpose

This article describes the devices that were deprecated in ESXi 5.5 and the implications for support.

Resolution

Support for some devices are deprecated in ESXi 5.5. During an upgrade, these device drivers may still be installed on the ESXi 5.5 host, and may continue to function, but the device is no longer officially supported on ESXi 5.5.

If you are upgrading ESXi using the ISO or VMware Update Manager, you may see a warning indicating that you are attempting to upgrade a server with a deprecated device. If you are upgrading using esxcli, you do not see a warning. If the you proceed with the upgrade, in all cases, the deprecated drivers are carried over as part of the ESXi 5.5 upgrade, but the device is not supported in ESXi 5.5.

Note: While creating an image that includes driver VIBs supporting deprecated device IDs, you do not see any warnings during the installation or auto deployment. However, during a fresh installation, you see a warning about the deprecated device. You can ignore the warning and complete the installation.
 
This table lists the devices that are deprecated and no longer supported in ESXi 5.5:
PartnerDriver NameDevice IDsDevice Name
satasata-promise
Version:
2.12-3vmw		105a:3371PDC20371 (FastTrak S150 TX2plus)
105a:357020771 (FastTrak TX2300)
105a:3571PDC20571 (FastTrak TX2200)
105a:3373PDC20378 (FastTrak 378/SATA 378)
105a:3375PDC20375 (SATA150 TX2plus)
105a:3376PDC20376 (FastTrak 376)
105a:3574PDC20579 SATAII 150 IDE Controller
105a:3d75PDC20575 (SATAII150 TX2plus)
105a:3d73PDC40775 (SATA 300 TX2plus)
105a:3318PDC20318 (SATA150 TX4)
105a:3319PDC20319 (FastTrak S150 TX4)
105a:3515PDC40719 [FastTrak TX4300/TX4310]
105a:3519PDC40519 (FastTrak TX4200)
105a:3d17PDC40718 (SATA 300 TX4)
105a:3d18PDC20518/PDC40518 (SATAII 150 TX4)
105a:6629PDC20619 (FastTrak TX4000)
105a:3577PDC40779 (FastTrak TX2300)
sata-sil
Version:
2.3-4vmw		1095:3112SiI 3112 [SATALink/SATARaid] Serial ATA Controller
1095:0240Adaptec AAR-1210SA SATA HostRAID Controller
1095:3512SiI 3512 [SATALink/SATARaid] Serial ATA Controller
1095:3114SiI 3114 [SATALink/SATARaid] Serial ATA Controller
sata-sil24
Version:
1.1-1vmw		1095:3124SiI 3124 [SATALink/SATARaid] Serial ATA Controller
1095:3132SiI 3132 [SATALink/SATARaid] Serial ATA Controller
1095:3531SiI 3531 [SATALink/SATARaid] Serial ATA Controller
sata-svw
Version:
2.3-3vmw		1166:0240K2 SATA
1166:0241RAIDCore RC4000
1166:0242RAIDCore RC4000
1166:024aBCM5785 [HT1000] SATA (Native SATA Mode)
1166:024bBCM5785 [HT1000] SATA (PATA/IDE Mode)
patapata-amd
Version:
0.3.10-3vmw		1022:7401AMD Cobra 7401 IDE/PATA Controller
1022:7409AMD Viper 7409 IDE/PATA Controller
1022:7411AMD Viper 7411 IDE/PATA Controller
1022:7441AMD 7441 OPUS IDE/PATA Controller
1022:7469AMD 8111 IDE/PATA Controller
1022:209aAMD CS5536 IDE/PATA Controller
10de:01bcNVidia NForce IDE/PATA Controller
10de:0065NVidia NForce2 IDE/PATA Controller
10de:0085NVidia NForce2S IDE/PATA Controller
10de:00d5NVidia NForce3 IDE/PATA Controller
10de:00e5NVidia NForce3S IDE/PATA Controller
10de:0053NVidia NForce CK804 IDE/PATA Controller
10de:0035NVidia NForce MCP04 IDE/PATA Controller
10de:0265NVidia NForce MCP51 IDE/PATA Controller
10de:036eNVidia NForce MCP55 IDE/PATA Controller
10de:03ecNVidia NForce MCP61 IDE/PATA Controller
10de:0448NVidia NForce MCP65 IDE/PATA Controller
10de:0560NVidia NForce MCP67 IDE/PATA Controller
10de:056cNVidia NForce MCP73 IDE/PATA Controller
10de:0759NVidia NForce MCP77 IDE/PATA Controller
pata-cmd64x
Version:
0.2.5-3vmw		1095:0643CMD643 IDE/PATA Controller
1095:0646CMD646 IDE/PATA Controller
1095:0648CMD648 IDE/PATA Controller
1095:0649CMD649 IDE/PATA Controller
pata-hpt3x2n
Version:
0.3.4-3vmw		1103:0004HPT 366 (rev 06) IDE/PATA Controller
1103:0007HPT 371/371N (rev 02) IDE/PATA Controller
1103:0005HPT 372 (rev 02) IDE/PATA Controller
1103:0006HPT 302/302N (rev 02) IDE/PATA Controller
1103:0009HPT 372N IDE/PATA Controller
pata-pdc2027x
Version:
1.0-3vmw		105a:4d68PDC20268 Ultra ATA/100 IDE/PATA Controller
105a:4d69PDC20269 (Ultra133 TX2) IDE/PATA Controller
105a:6268PDC20270 Ultra ATA/100 IDE/PATA Controller
105a:6269PDC20271 Ultra ATA/133 IDE/PATA Controller
105a:1275PDC20275 Ultra ATA/133 IDE/PATA Controller
105a:5275PDC20276 Ultra ATA/133 IDE/PATA Controller
105a:7275PDC20277 Ultra ATA/133 IDE/PATA Controller
pata-serverworks
Version:
0.4.3-3vmw
1166:0211Serverworks OSB4 IDE/PATA Controller
1166:0212Serverworks CSB5 IDE/PATA Controller
1166:0213Serverworks CSB6 IDE/PATA Controller
1166:0214Serverworks HT1000 IDE/PATA Controller
1166:0215Serverworks HT1100 IDE/PATA Controller
1166:0217Serverworks CSB6IDE2 IDE/PATA Controller
pata-sil680
Version:
0.4.8-3vm		1095:0680Sil0680A - PCI to 2 Port IDE/PATA Controller
pata-via
Version:
0.3.3-2vmw		1106:5324VX800 SATA/EIDE Controller
Adaptecadp94xx
Version:
1.0.8.12-6vmw		9005:0410AIC-9410
9005:0411AIC-9410
9005:0412AIC-9410
9005:041eAIC-9410
9005:041fAIC-9410
Adaptecaic79xx
Version:
3.1-5vmw		9005:8000ASC-29320A U320
9005:800fAIC-7901 U320
9005:8010ASC-39320 U320
9005:801139320D Ultra320 SCSI
9005:8011:0e11:00acASC-32320D U320
9005:8011:9005:0041ASC-39320D U320
9005:8012ASC-29320 U320
9005:8013ASC-29320B U320
9005:8014ASC-29320LP U320
9005:8015AHA-39320B
9005:8016AHA-39320A
9005:8017AHA-29320ALP
9005:801cAHA-39320DB / AHA-39320DB-HP
9005:801dAIC-7902B U320 OEM
9005:801eAIC-7901A U320
9005:801fAIC-7902 U320
9005:8094ASC-29320LP U320 w/HostRAID
9005:809eAIC-7901A U320 w/HostRAID
9005:809fAIC-7902 U320 w/HostRAID
Adaptecips
Version:
7.12.05-4vmw		1014:002eSCSI RAID Adapter [ServeRAID] 4Lx
1014:01bdServeRAID Controller 5i
9005:0250ServeRAID Controller
LSImegaraid2
Version:
2.00.4-9vmw		1000:0407LSI MegaRAID 320-2x
1000:0408:1028:0002Dell PERC 4e/DC Adapter
1000:0408LSI Logic MegaRAID
1000:1960:1028:0518Dell PERC 4/DC
1000:1960LSI Logic MegaRAID
1000:9010LSI Logic MegaRAID
1000:9060LSI Logic MegaRAID
101e:1960MegaRAID
101e:9010MegaRAID 428 Ultra RAID Controller
101e:9060MegaRAID 434 Ultra GT RAID Controller
1028:000eDell PowerEdge Expandable RAID Controller
1028:000fDell PERC 4
1028:0013Dell PERC 4E/Si/Di
8086:1960:101e:0438MegaRAID 438 Ultra2 LVD RAID Controller
8086:1960:101e:0466MegaRAID 466 Express Plus RAID Controller
8086:1960:101e:0467MegaRAID 467 Enterprise 1500 RAID Controller
8086:1960:101e:09a0PowerEdge Expandable RAID Controller 2/SC
8086:1960:1028:0467PowerEdge Expandable RAID Controller 2/DC
8086:1960:1028:1111PowerEdge Expandable RAID Controller 2/SC
8086:1960:103c:03a2MegaRAID
8086:1960:103c:10c6MegaRAID 438, HP NetRAID-3Si
8086:1960:103c:10c7MegaRAID T5, Integrated HP NetRAID
8086:1960:103c:10ccMegaRAID, Integrated HP NetRAID
Neterions2io
Version:
2.1.4.13427-3vmw		17d5:5831Xframe I 10 GbE Server/Storage adapter
17d5:5832Xframe II 10 GbE Server/Storage adapter
Marvell Techsky2
Version:
1.20-2vmw		11ab:435488E8040 PCI-E Fast Ethernet Controller
11ab:436288E8053 PCI-E Gigabit Ethernet Controller
RealTekr8168
Version:
8.013.00-3vmw		10ec:8168Realtek 8168 Gigabit Ethernet
r8169
Version:
011.00-2vmw		10ec:8169Realtek 8169 Gigabit Ethernet
10ec:8167Realtek 8169 Gigabit Ethernet
nVidiaforcedeth
Version:
0.61-2vmw		10de:0373nVidia NForce Network Controller
10de:0372NVIDIA nForce Pro 3600 Network Controller
10de:0269nVidia NForce Network Controller
10de:0268nVidia NForce Network Controller
10de:0056NVIDIA nForce Pro 2200 Network Controller
10de:0057NVIDIA nForce Pro 2200 Network Controller
10de:054cMCP55 SATA Controller
10de:054dnVidia NForce Network Controller
10de:054enVidia NForce Network Controller
10de:054fnVidia NForce Network Controller
10de:07dcnVidia NForce Network Controller
10de:07ddnVidia NForce Network Controller
10de:07denVidia NForce Network Controller
10de:07dfnVidia NForce Network Controller
10de:0760nVidia NForce Network Controller
10de:0761nVidia NForce Network Controller
10de:0762nVidia NForce Network Controller
10de:0763nVidia NForce Network Controller
10de:0ab0nVidia NForce Network Controller
10de:0ab1nVidia NForce Network Controller
10de:0ab2nVidia NForce Network Controller
10de:0ab3nVidia NForce Network Controller
Intele1000
Version:
8.0.3.1-3vmw		8086:100082542 Gigabit Ethernet Controller
8086:100182543GC Gigabit Ethernet Controller (Fiber)
8086:100482543GC Gigabit Ethernet Controller (Copper)
8086:100882544EI Gigabit Ethernet Controller (Copper)
8086:100982544EI Gigabit Ethernet Controller (Fiber)
8086:100c82544GC Gigabit Ethernet Controller (Copper)
8086:100d82544GC Gigabit Ethernet Controller (LOM)
8086:100e82540EM Gigabit Ethernet Controller
8086:100f82545EM Gigabit Ethernet Controller (Copper)
8086:101082546EM Gigabit Ethernet Controller (Copper)
8086:101182545EM Gigabit Ethernet Controller (Fiber)
8086:101282546EM Gigabit Ethernet Controller (Fiber)
8086:101382541EI Gigabit Ethernet Controller
8086:101482541ER Gigabit Ethernet Controller
8086:101582540EM Gigabit Ethernet Controller (LOM)
8086:101682540EP Gigabit Ethernet Controller
8086:101782540EP Gigabit Ethernet Controller
8086:101882541EI Gigabit Ethernet Controller
8086:101982547EI Gigabit Ethernet Controller
8086:101a82547EI Gigabit Ethernet Controller
8086:101d82546EB Gigabit Ethernet Controller
8086:101e82540EP Gigabit Ethernet Controller
8086:102682545GM Gigabit Ethernet Controller
8086:102782545GM Gigabit Ethernet Controller
8086:102882545GM Gigabit Ethernet Controller
8086:107582547GI Gigabit Ethernet Controller
8086:107682541GI Gigabit Ethernet Controller
8086:107782541GI Gigabit Ethernet Controller
8086:107882541ER Gigabit Ethernet Controller
8086:107982546EB Gigabit Ethernet Controller
8086:107a82546GB Gigabit Ethernet Controller
8086:107b82546GB Gigabit Ethernet Controller
8086:107c82541PI Gigabit Ethernet Controller
8086:108a82546GB Gigabit Ethernet Controller
8086:109982546GB Gigabit Ethernet Controller (Copper)
8086:10b582546GB Gigabit Ethernet Controller (Copper)
e1000e
Version:
1.1.2-4vmw		8086:106082571EB Gigabit Ethernet Controller
8086:10a482571EB Gigabit Ethernet Controller
8086:10a582571EB Gigabit Ethernet Controller (Fiber)
8086:10d582571PT Gigabit PT Quad Port Server ExpressModule
8086:10d982571EB Dual Port Gigabit Mezzanine Adapter
8086:10da82571EB Quad Port Gigabit Mezzanine Adapter
8086:107d82572EI Gigabit Ethernet Controller
8086:107f82572EI Gigabit Ethernet Controller
8086:10b982572EI Gigabit Ethernet Controller
8086:108b82573V Gigabit Ethernet Controller
8086:108c82573E Gigabit Ethernet Controller
8086:109a82573L Gigabit Ethernet Controller
Inteligb
Version:
2.1.11.1-4vmw		8086:10d6Intel 82575GB Gigabit Network Connection
ixgbe
Version:
3.7.13.7.14iov-11vmw		8086:10b6Intel 82598 10GbE PCI-Express Ethernet Controller
8086:10c8Intel 82598EB 10-Gigabit AT Network Connection
8086:10dbIntel 82598EB 10 Gigabit Dual Port Network Connection
8086:10ddIntel 82598EB 10 Gigabit AT CX4 Network Connection
8086:10e1Intel 82598EB 10-Gigabit AF Dual Port Network Connection
8086:10ecIntel 82598EB 10-Gigabit AF CX4 Network connection
8086:10f1Intel 82598EB 10-Gigabit AF Dual Port Network Connection
8086:10f4Intel 82598EB 10-Gigabit AF Network Connection
8086:1508Intel 82598EB 10 Gigabit BX Network Connection
8086:150bIntel 82598EB 10-Gigabit AT2 Server Adapter
Emulexlpfc10DF:f095LP952 Fibre Channel Adapter
10DF:f0a5LP1050 2Gb Fibre Channel Host Adapter
10DF:f0d5LP1150 4Gb Fibre Channel Host Adapter
10DF:f800LP8000 Fibre Channel Host Adapter
10DF:fc10:10DF fc11LP11000-S 4Gb Fibre Channel Host Adapter
10DF:fc10:10DF fc12LP11002-S 4Gb Fibre Channel Host Adapter
10DF:fd00LP11000 4Gb Fibre Channel Host Adapter
10DF:fe05Emulex LP21000 10GbE PCIe FCoE CNA
10DF:fe12Cisco UCS CNA M71KR-Emulex
10DF:f098LP982 Fibre Channel Adapter
10DF:f0a1LP101 2Gb Fibre Channel Host Adapter
10DF:f900:10DF:0026LP9002 2Gb Fibre Channel Host Adapter
10DF:f900:10DF:0028Cisco UCS CNA M71KR-Emulex
10DF:f900LP9000 Fibre Channel Host Adapter
10DF:f980LP9802 Fibre Channel Adapter
10DF:fa00LP10000 2Gb Fibre Channel Host Adapter
10DF:fc00LP10000-S 2Gb Fibre Channel Host Adapter
Qlogicnx_nic
Version:
5.0.620-3vmw		4040:0100:4040:0124QLE3044 (NX3-4GBT) Quad Port PCIe 2.0 Gigabit Ethernet Adapter
4040:0100:4040:0126QLE3142 (NX3-20GxX) Dual Port PCIe 2.0 10GbE SFP+ Adapter
Qlogicqla2xxx1077:5432SP232-based 4Gb Fibre Channel to PCI Express HBA
1077:2300QLA2300 64-bit Fibre Channel Adapter
1077:2312ISP2312-based 2Gb Fibre Channel to PCI-X HBA
1077:2322ISP2322-based 2Gb Fibre Channel to PCI-X HBA
1077:6312SP202-based 2Gb Fibre Channel to PCI-X HBA
1077:6322SP212-based 2Gb Fibre Channel to PCI-X HBA
Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2056935
Posted by at No comments:
Subscribe to: Posts (Atom)