- VMXNET 3
— The VMXNET 3 adapter is the next generation of a paravirtualized NIC
designed for performance, and is not related to VMXNET or VMXNET 2. It
offers all the features available in VMXNET 2, and adds several new
features like multiqueue support (also known as Receive Side Scaling in
Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.
VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems:
- 32- and 64-bit versions of Microsoft Windows XP,7, 2003, 2003 R2, 2008, and 2008 R2
- 32- and 64-bit versions of Red Hat Enterprise Linux 5.0 and later
- 32- and 64-bit versions of SUSE Linux Enterprise Server 10 and later
- 32- and 64-bit versions of Asianux 3 and later
- 32- and 64-bit versions of Debian 4
- 32- and 64-bit versions of Ubuntu 7.04 and later
- 32- and 64-bit versions of Sun Solaris 10 U4 and later
Notes:- Jumbo frames are not supported in Solaris Guest OS with VMXNET 2 or VMXNET 3.
- Fault Tolerance is not supported on a virtual machine configured with a VMXNET 3 vNIC in vSphere 4.0, but is fully supported on vSphere 4.1.
12 diciembre 2011
Que sistemas operativos soportan VMXNET ? ...no todos
08 diciembre 2011
Nuevo TR: NetApp Storage Best Practices for VMware vSphere 5
Nuevo documento de December 2011 actualizado tambien a la version vSphere 5 (ESXi)
Lo podeis descargar del siguiente enlace: http://media.netapp.com/documents/tr-3749.pdf
Del documento destacaria la referencia al "Storage DRS" con los "Datastore Cluster" de la nueva version vSphere 5, y las recomendaciones sobre su configuracion:
Following are the key recommendations when configuring storage DRS and datastore cluster:
- Set SDRS to manual mode and to review the recommendations before accepting them.
- All datastores in the cluster should use the same type of storage (SAS, SATA, and so on) and have the same replication and protection settings.
- SDRS will move VMDKs between datastores, and any space savings from NetApp cloning or deduplication will be lost when the VMDK is moved. You can rerun deduplication to regain these savings.
- After SDRS moves VMDKs, it is recommended to recreate the Snapshot copies at the destination datastore.
- Do not use SDRS on thinly provisioned VMFS datastores due to the risk of reaching an out-of-space situation.
- Do not mix replicated and nonreplicated datastores in a datastore cluster.
- All datastores in an SDRS cluster must either be all VMFS or all NFS datastores.
- Datastores cannot be shared between different sites.
- All datastore hosts within the datastore cluster must be ESXi 5 hosts.
Lo podeis descargar del siguiente enlace: http://media.netapp.com/documents/tr-3749.pdf
Del documento destacaria la referencia al "Storage DRS" con los "Datastore Cluster" de la nueva version vSphere 5, y las recomendaciones sobre su configuracion:
Following are the key recommendations when configuring storage DRS and datastore cluster:
- Set SDRS to manual mode and to review the recommendations before accepting them.
- All datastores in the cluster should use the same type of storage (SAS, SATA, and so on) and have the same replication and protection settings.
- SDRS will move VMDKs between datastores, and any space savings from NetApp cloning or deduplication will be lost when the VMDK is moved. You can rerun deduplication to regain these savings.
- After SDRS moves VMDKs, it is recommended to recreate the Snapshot copies at the destination datastore.
- Do not use SDRS on thinly provisioned VMFS datastores due to the risk of reaching an out-of-space situation.
- Do not mix replicated and nonreplicated datastores in a datastore cluster.
- All datastores in an SDRS cluster must either be all VMFS or all NFS datastores.
- Datastores cannot be shared between different sites.
- All datastore hosts within the datastore cluster must be ESXi 5 hosts.
Publicado por
Pablo Cruces - vExpert 2020-2014, VCP-NV (NSX), VCP-DT, VCP-Cloud, VCP-DCV, VCP5, VCP3, MAP2013, VSP, VTSP, MCSE
-
11:36
Enviar por correo electrónicoEscribe un blogCompartir en XCompartir con FacebookCompartir en Pinterest
No hay comentarios:
Etiquetas:
Best Practices,
DRS,
NetApp,
vSphere 5
07 diciembre 2011
Emular entorno WAN con "WANem"
Para poder realizar pruebas de software como podria ser Site Recovery Manager de VMware en entornos WAN diponemos de esta util herramienta opensource: WANem, que podemos descargar incluso en una MV a modo de appliance y hacerla correr con VMplayer o VMware Server desde cualquier equipo portatil.
Enlace de la web ofcial: http://wanem.sourceforge.net/
Enlace de descarga: http://sourceforge.net/projects/wanem/files/WANem%20Virtual%20Appliance/WANem%20Virtual%20Appliance%20v2.1/WANemv2.1.zip/download
Mark Zuckerberg sufre los errores de privacidad de Facebook
Blanco y en botella.....
"Muchos son los usuarios de Facebook que se han quejado de los fallos se seguridad de la red social y..."
http://www.elpais.com/articulo/tecnologia/Mark/Zuckerberg/sufre/errores/privacidad/Facebook/elpeputec/20111207elpeputec_1/Tes
PABLO CRUCES
http://virtualshocks.blogspot.com
Enviado desde mi BlackBerry® de Vodafone
"Muchos son los usuarios de Facebook que se han quejado de los fallos se seguridad de la red social y..."
http://www.elpais.com/articulo/tecnologia/Mark/Zuckerberg/sufre/errores/privacidad/Facebook/elpeputec/20111207elpeputec_1/Tes
PABLO CRUCES
http://virtualshocks.blogspot.com
Enviado desde mi BlackBerry® de Vodafone
01 diciembre 2011
Nace YaCy, un buscador basado en P2P
Activistas del software libre han lanzado un buscador, YaCy Networks, que quiere ser una alternativa...
http://www.elpais.com/articulo/tecnologia/Nace/YaCy/buscador/basado/P2P/elpeputec/20111129elpeputec_4/Tes
PABLO CRUCES
http://virtualshocks.blogspot.com
Enviado desde mi BlackBerry® de Vodafone
http://www.elpais.com/articulo/tecnologia/Nace/YaCy/buscador/basado/P2P/elpeputec/20111129elpeputec_4/Tes
PABLO CRUCES
http://virtualshocks.blogspot.com
Enviado desde mi BlackBerry® de Vodafone
Suscribirse a:
Entradas (Atom)