Beruflich Dokumente
Kultur Dokumente
Copyright 2012 Dell Inc. All rights reserved. Dell and EqualLogic are trademarks of Dell Inc. All trademarks and registered trademarks mentioned herein are the property of their respective owners. Information in this document is subject to change without notice. Reproduction in any manner whatsoever without the written permission of Dell is strictly forbidden. January 2012 Part Number: 110-6093-EN-R3
Table of Contents
Preface 1 Overview
EqualLogic MEM Architecture EqualLogic MEM Configuration Model Related Documentation
v 1 1 2 3 5 5 6 7 8 8 10 10 11 11 11 12 13 13 13 14 14 15 15 15 17 17 17 18 18 18 19 19 19 20 21 21 21 21 22 22 23 25 25 27 29
4 Troubleshooting
Log Files ESX 5 CLI Commands for Troubleshooting Listing Statistics Listing Adapters Listing Sessions Troubleshooting Common Issues
Index
iii
Preface
PS Series arrays optimize resources by automating performance and network load balancing. Additionally, PS Series arrays offer all-inclusive array management software, host software, and free firmware updates.
Audience
The information in this guide is intended for administrators responsible for managing VMware vSphere environments attached to a PS Series group.
Related Documentation
For detailed information about PS Series arrays, groups, volumes, array software, and host software, log in to the Documentation page at the customer support site.
Contacting Dell
1. If you have an Express Service Code, have it ready. The code helps the Dell automated support telephone system direct your call more efficiently. 2. If you are a customer in the United States or Canada in need of technical support, call 1-800-945-3355. If not, go to Step 3. 3. Visit support.equallogic.com. 4. Log in, or click Create Account to request a new support account. 5. At the top right, click Contact Us, and call the phone number or select the link for the type of support you need.
1 Overview
VMware vSphere provides the Pluggable Storage Architecture (PSA), which enables you to configure multipathing for high availability and increased performance. The modular design of the architecture accepts third-party multipathing plugins that enable enhanced functionality specific to storage device models. The EqualLogic Multipathing Extension Module (MEM) provides the following enhancements to the existing VMware multipathing functionality: Increased bandwidth Reduced network latency Automatic connection management Automatic load balancing across multiple active paths
Note: Starting with Version 5.0, vSphere supports ESXi only. Previous versions of vSphere supported both ESX
and ESXi. Because this guide covers operations on both vSphere Version 4.1 and 5.0, the term ESX will be used to refer to a host running ESX or ESXi.
The PSP provides load balancing capabilities that enable you to maximize I/O throughput. The PSP uses its knowledge of the distributed nature of volumes on the PS Series group and least queue depth to route each I/O packet on the most optimal path to the volume. EHCM simplifies management by creating the appropriate number of sessions to an EqualLogic volume. The number of sessions created by EHCM depends on the topology of your iSCSI SAN and the MPIO settings on the VMware ESX host. Every volume is distributed across one or more members in the PS Series group. The portion of a volume that is located on a single member is referred to as a volume slice. The default EHCM behavior is to create two sessions per volume slice, with a maximum of six sessions per volume. However, you can alter this behavior (see EHCM Configuration File on page 17).
1 Overview
When you use the Dell EqualLogic MEM, EHCM distributes iSCSI sessions across all configured VMkernel ports and PS Series group Ethernet ports. EHCM monitors the topology of the SAN. If you change the configuration by modifying the number of Ethernet interfaces, by moving a PS Series volume, or if there is a network outage that affects some of the iSCSI sessions, EHCM automatically reconfigures the iSCSI sessions to reflect these changes.
1 Overview
1 2 3 4 5 6 7 8 9 10 11
VMware virtual machines with guest operating system Virtual machine disk format (VMDK) Raw device mapping (RDM) disk VMware file system (VMFS) CIM provider, which hosts EqualLogic Host Connection Management EqualLogic Routed PSP VMware native multipathing, hosting the PSP driver VMkernel, the ESX hypervisor, including network and storage stacks Host Bus Adapter (HBA) or software initiator Network PS Series group members
Related Documentation
It is beyond the scope of this document to provide VMware conceptual information or detailed instructions on configuring VMware vSphere. See the following related documentation.
VMware Documentation
See the VMware documentation web site: http://www.vmware.com/support/pubs/ Specifically, refer to the following documents: vSphere Installation and Setup Guide iSCSI SAN Configuration Guide Installing and Administering vSphere Update Manager
See the Dell EqualLogic Multipathing Extension Module Release Notes for installation requirements and information, including: Minimum software and firmware prerequisites Unsupported VMware environments Notes about using the EqualLogic MEM plugin with HBAs
configuration and installation script. To use this script, copy it to the vSphere Management Assistant (vMA) or install the vSphere CLI on your Linux or Windows desktop / management station. The offline bundle for ESX 4.1 containing the VMware Infrastructure Bundle (VIB) to be installed on an ESX server. This bundle should not be unzipped, as the installation tools expect it in .zip format. This bundle can be installed through vCenter Update Manager or from a vMA.
dell-eql-mem-esx4-version.zip
dell-eql-mem-esx5-version.zipThe
offline bundle for ESX 5.0 containing the VIB to be installed on an ESX server. This bundle should not be unzipped, as the installation tools expect it in .zip format. This bundle can be installed through vCenter Update Manager or from a vMA. User documentation in PDF format.
Create a vSwitch
Create a vSwitch to use for iSCSI traffic. Assign physical NICs that will be used for iSCSI traffic to this vSwitch. If you intend to use jumbo frames, you must enable them for each vSwitch and each VMkernel port (virtual network interface that is used by the VMkernel) interface. You can verify that jumbo frames are enabled on the vSwitch and VMkernel port through the vSphere client (vSphere 5.0 only) or by using the commands esxcfg-vswitch -l and esxcfg-vmknic -l.
5 6
Before enabling jumbo frames, check with your hardware vendors to ensure your physical network adapter and other network equipment support jumbo frames. Decide on VMkernel ports Each port must be mapped to a single network port. Create VMkernel ports for the iSCSI initiator to use. You should create one VMkernel port per physical NIC that will be used for Create VMkernel ports iSCSI multipathing. If you have multiple VMkernel ports sharing the same uplink, only one of them will be used by EHCM, and the excess VMkernel ports will be ignored. You can use multiple NICs per vSwitch, but each VMkernel port must be mapped to a single uplink (physical NIC). You can verify Remove extra uplinks this by using the command esxcfg-vswitch -l, and you can remove extra uplinks with the esxcfg-vswitch -N command. Enable VMware iSCSI Initiator If using the software initiator, enable VMware iSCSI Initiator. You must bind the VMkernel ports to the iSCSI daemon with one of the following commands. Bind the VMkernel ports
esxcli iscsi networkportal add esxcli swisci nic add
(ESX 5)
(ESX 4.1) You must add the PS Series group address to the iSCSI Initiator discovery list. 8 Add discovery list If using Broadcom iSCSI offload adapters, there is a separate vmhba for each adapter port. The discovery address must be entered for each vmhba.
See the VMware iSCSI SAN Configuration Guide for more information.
Note: See the PS Series documentation for group limits and pool limits on total iSCSI sessions. It may be
necessary to reduce the number of sessions created per volume in large configuration.
ESX host or vCenter server against which to run the command. Administrative user account on the system specified by --server. Password for administrative account on the host. To install on an ESX host, it must be configured with an administrative password. ESX host. This parameter is required if --server refers to a vCenter server. Administrative user account for the system specified by --vihost. Password for administrative account for the system specified by --vhhost.
Note: Dell suggests that you configure vi-fastpass on the vMA. Once vi-fastpass is configured, it is not
necessary to specify the username and password when running the setup script, though it is still necessary to identify the ESX server. See the vSphere Management Assistant Guide, available from VMware, for more details on configuring vi-fastpass authentication.
Depending on your configuration, not all of the parameters are needed. Table 4 describes the configuration parameters.
--nohwiscsi
--heartbeat
--chapuser
--chapsecret
Comma separated list of vmknics to use for multipathing. Comma separated list of IP addresses to assign to VMkernel ports used for multipathing. Name of vSwitch to create. setup.pl will use the existing vSwitch if one is found. MTU to use for VMkernel ports and vSwitch used for multipathing. Prefix to use for VMkernel ports created for multipathing. Subnet mask used for VMkernel ports created for multipathing. Enable the VMware software iSCSI initiator if not already enabled. Ignore any supported iSCSI offload network cards, and use only the VMware software iSCSI initiator. If the configuration script detects iSCSI offload network cards, it will use this capability by default unless this flag is set. Sets the specified IP address as a Send Targets discovery address for all iSCSI initiators that were configured to bind vmknics. Use a vNetwork Distributed Switch instead of a standard vSwitch. Specify a file to use to record a log of network configuration actions. IP address to use for a highly available VMkernel port on the iSCSI subnet. This VMkernel port will be configured to use all physical NICs on the vSwitch, so it will remain online in the event of a single NIC or switch failure. CHAP user name to be used for connecting volumes on the PS Series group IP. CHAP credentials are assigned to the Send Targets discovery address specified by the --groupip parameter. CHAP secret to be used for connecting volumes on the PS Series group IP.
not set
none
none none
The --configure operation can be run in an interactive mode by specifying only the server name parameter. The script then interactively asks the user a series of questions to gather the necessary information for network configuration. For example:
$ setup.pl --configure --server=192.168.XXX.XXX
Installation Considerations
Installation of the Dell EqualLogic MEM requires you to put the ESX host in maintenance mode using VMware management tools. Configuration through the setup.pl script requires communicating directly with the ESX host, therefore it is required that lockdown mode not be enabled. Because installation requires putting the ESX host in maintenance mode, it is not possible to perform the installation from a vCenter Server, vCenter Update Manager, or VMware Management Assistant that is running as a VM on the ESX host. The VMs must first be migrated to another ESX host so they can continue running during the installation. For a clean installation of MEM on ESX 5.0, you do not need to reboot ESX. However, if you are doing an upgrade install of MEM on ESX 5.0, or are installing the MEM on ESX 4.1, you must reboot the ESX host for the changes to take effect.
script
Installing the MEM Plugin Using vCenter Update Manager on page 11 Installing the MEM Plugin Using the setup.pl Script on page 11 Installing the MEM Plugin Using the vSphere CLI For ESX 5.0 on page 12 Installing the MEM Plugin Using the vSphere CLI For ESX 4.1 on page 13
vSphere CLI
Notes: When installing the Dell EqualLogic MEM, you are required to put the VMware host in maintenance
mode for both ESX 4.1 and 5.0 . ESX 4.1 requires a reboot. ESX 5.0 requires a reboot only if you are performing an update installation. When installing on ESX 5.0 with the setup.pl script, the offline bundle is first uploaded to one of the ESX hosts datastores before it is installed. This offline bundle is not deleted after the installation. The setup.pl script will choose the first datastore it finds, but you can use the optional --datastore parameter to specify a particular datastore to use.
10
For network configuration, see Configuring Your Network for the MEM Plugin on page 8. To modify the EHCM configuration, see Chapter 3, Configuring the EqualLogic MEM. For instructions on uninstallation, see Installing the MEM Plugin Using the vSphere CLI For ESX 5.0 on page 12.
11
The --bundle parameter specifies the path to the offline bundle file containing multipathing plugin (delleql-mem-esxn-version.zip). If not specified, the script will default to the offline bundle in the same directory as the setup.pl script. The --datastore optional parameter is used for ESX 5.0 only, specifies which datastore to use as a staging area to copy the bundle to before installing it. If not specified, the script will use the first datastore it finds. The optional --reboot parameter will auto-reboot ESX following a successful installation.
Installing the MEM Plugin Using the vSphere CLI For ESX 5.0
If you are using ESX 5.0, you can use the following vSphere CLI command syntax to install the Dell EqualLogic MEM plugin:
esxcli --server=hostname software vib install --depot bundle
The --depot parameter specifies the path to the offline bundle file containing multipathing plugin (dell-eqlmem-esxn-version.zip).
Note: To install the offline bundle, you must first copy it to a location that is accessible from the ESX host. The
install command can then be run from any esxcli client, giving the full path to the bundle on the host. For example, if you upload the bundle to a datastore named datastore1, it can then be installed with the following command:
$ esxcli --server 192.168.XXX.XXX software vib install --depot /vmfs/volumes/datastore1/dell-eql-mem-esx51.1.0.202245.zip Enter username: root Enter password: Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Dell_bootbank_dell-eql-host-connection-mgr_1.1.0-202245, Dell_bootbank_dell-eql-hostprofile_1.0.9-202245, Dell_bootbank_dell-eql-routed-psp_1.1.0-202245 VIBs Removed: VIBs Skipped:
Notes: This bundle should not be unzipped, as the installation tools expect it in .zip format.
Make sure that the path to the bundle you specify is relative to the ESX host. In addition to specifying a bundle that is on an ESX datastore, you can also specify a full remote URL.
12
Installing the MEM Plugin Using the vSphere CLI For ESX 4.1
If you are using ESX 4.1, you can use the vihostupdate tool to install the Dell EqualLogic MEM plugin:
vihostupdate --server=hostname --install --bundle=bundle
Note: When using vihostupdate, the bundle does not need to be first copied to the ESX host, and the location
Removing the MEM Plugin Using the vSphere CLI for ESX 5.0
On ESX 5.0, use the following vSphere CLI command syntax to remove the EqualLogic plugin VIBs:
esxcli --server=hostname software vib remove --vibname [bundle]
13
To properly remove the MEM, all three VIBs must be uninstalled. You can do this from one command line:
$ esxcli software vib remove --vibname dell-eql-host-connection-mgr --vibname dell-eql-hostprofile --vibname dell-eql-routed-psp
Enter username: root Enter password: Removal Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VIBs Removed: Dell_bootbank_dell-eql-host-connection-mgr_1.0.9-202245, Dell_bootbank_delleql-hostprofile_1.0.9-202245, Dell_bootbank_dell-eql-routed-psp_1.0.9-202245 VIBs Skipped:
14
Note: The upgrade operation when preformed on ESX 4.1 or ESX 5.0 requires a reboot prior to the new version
becoming available.
2. Add the three VIBs in the MEM to the image profile. For example:
Add-EsxSoftwarePackage -imageprofile name -SoftwarePackage dell-eql-routed-psp Add-EsxSoftwarePackage -imageprofile name -SoftwarePackage dell-eql-hostconnection-mgr Add-EsxSoftwarePackage -imageprofile name -SoftwarePackage dell-eql-hostprofile
See the vSphere Installation and Setup documentation available from VMware for more information about AutoDeploy.
15
The AutoDeploy feature is frequently used with host profiles. For details, see EqualLogic MEM Configuration Using Host Profiles for vSphere 5.0 on page 20.
16
TotalSessions
512
1024
64
VolumeSessions
12
MemberSessions
Maximum total sessions created to all EqualLogic volumes. You can lower this limit in large configurations to keep the session count within VMware ESX and PS group limits. Maximum number of sessions created to each EqualLogic volume. You can lower this limit in large configurations to keep the session count within VMware ESX and PS group limits. Maximum number of sessions created to each volume slice (portion of a volume on a single member).
When determining how many sessions to create to a volume, EHCM chooses a value that meets all constraints specified by the totalsessions, volumesessions and membersessions values. EHCM does not establish entirely redundant paths (iSCSI sessions that have identical server and array endpoints). Depending on your configuration, the actual number of sessions created may be less than you specify for the configuration. See the PS Series documentation for group limits and pool limits on total iSCSI sessions. It may be necessary to reduce the number of sessions created per volume in large configurations.
17
The preferred method of making changes is through the vSphere CLI tools on vSphere 5.0, and through the setup.pl script on vSphere 4.1. Each line in the file uses the format param=value. Table 6 shows available options and their values.
EqualLogic MEM Configuration for ESX 5.0 Using vSphere CLI Commands
On ESX 5.0, you can use the vSphere CLI to configure and inspect the Dell EqualLogic MEM. For a full description of the vSphere CLI commands, see the VMware documentation.
Note: The MEM functionality is available immediately after an installation. However, the new esxcli
commands used to control and report status of the plugin are not available until the hostd agent is restarted. This can be done without rebooting the server by connecting to the ESX console and executing the following command:
/etc/init.d/hostd restart
For example:
$ esxcli equallogic param list
18
For example:
$ esxcli equallogic param set --name=VolumeSessions --value=3
For example:
$ setup.pl --listparam --server=10.168.XXX.XXX Parameter Name -------------TotalSessions VolumeSessions MemberSessions MinAdapterSpeed Value ----512 6 2 1000 Max --1024 12 4 10000 Min --64 1 1 10 Description ----------Max number of sessions per host. Max number of sessions per volume. Max number of sessions per member per volume. Minimum adapter speed for iSCSI multipathing.
19
For example:
$ setup.pl --setparam --name=TotalSessions --value=256 --server=10.168.XXX.XXX Setting parameter totalsessions Parameter Name -------------TotalSessions VolumeSessions MemberSessions MinAdapterSpeed Value ----256 6 2 1000 Max --1024 12 4 10000 = 256 Min --64 1 1 10 Description ----------Max number of sessions per host. Max number of sessions per volume. Max number of sessions per member per volume. Minimum adapter speed for iSCSI multipathing.
See the vSphere Host Profiles Guide available from VMware for more information about using Host Profiles.
20
4 Troubleshooting
This chapter discusses topics relating to troubleshooting the Dell EqualLogic MEM.
Log Files
Table 7 shows the log file used by the Dell EqualLogic MEM. Table 7: Log Files
Log File Name /var/log/equallogic/ehcmd.log /var/log/vmkernel /var/log/messages /var/log/vmkernel.log Description
Contains EHCMD log messages for ESX Includes PSP log messages (ESX 4.1) Includes PSP log messages (ESXi 4.1) Includes PSP log messages (ESXi 5.0)
Listing Statistics
To view statistics, use the following vSphere CLI command syntax:
esxcli equallogic stat {detail | summary} [--device=device] [--path]}
The following options can be used: The detail parameter will cause detailed statistics to be reported instead of summary statistics. The device parameter allows filtering to display just statistics for one device. The path parameter will cause statistics to be reported for each path.
21
4 Troubleshooting
For example:
$ esxcli equallogic stat summary
Listing Adapters
To view adapters, use the following vSphere CLI command syntax:
esxcli equallogic adapters
For example:
$ esxcli equallogic adapters VMKernel: vmk1 Ip: 192.168.xxx.xx Status: Normal NIC: vmnic1 Speed: 1000 MAC: 00:1e:c9:b5:04:75 HBA: vmhba33 Vendor: VMware:iSCSI Software Adapter VMKernel: vmk2 Ip: 192.168.xxx.xx Status: Normal NIC: vmnic2 Speed: 1000 MAC: 00:1e:c9:b5:04:77 HBA: vmhba33 Vendor: VMware:iSCSI Software Adapter
Listing Sessions
To list sessions, use the following vSphere CLI command syntax:
esxcli equallogic sessions
22
4 Troubleshooting
For example:
$ esxcli equallogic sessions VolumeName SrcIp ------------------- -------------esx5datastore 192.168.XXX.61 esx5datastore 192.168.XXX.62 esx5datastore 192.168.XXX.62 esx5datastore 192.168.XXX.61 esx5vm1 192.168.XXX.62 esx5vm1 192.168.XXX.61 esx5vm1 192.168.XXX.61 esx5vm1 192.168.XXX.62 esx5vm2 192.168.XXX.61 esx5vm2 192.168.XXX.62 esx5vm2 192.168.XXX.61 esx5vm2 192.168.XXX.61 esx5vm3 192.168.XXX.61 esx5vm3 192.168.XXX.62 esx5vm3 192.168.XXX.61 esx5vm3 192.168.XXX.61 esx5vm4 192.168.XXX.61 esx5vm4 192.168.XXX.61 esx5vm4 192.168.XXX.62 esx5vm4 192.168.XXX.62 esx5vm5 192.168.XXX.62 esx5vm5 192.168.XXX.61 esx5vm5 192.168.XXX.61 esx5vm5 192.168.XXX.62 TgtIp ------------192.168.XX.212 192.168.XX.221 192.168.XX.211 192.168.XX.222 192.168.XX.222 192.168.XX.221 192.168.XX.212 192.168.XX.211 192.168.XX.221 192.168.XX.211 192.168.XX.222 192.168.XX.212 192.168.XX.212 192.168.XX.211 192.168.XX.222 192.168.XX.222 192.168.XX.221 192.168.XX.222 192.168.XX.212 192.168.XX.221 192.168.XX.211 192.168.XX.221 192.168.XX.212 192.168.XX.222
23
4 Troubleshooting
The VIB was not first copied to the ESX location (ESX 5.0) Did not bind vmknics to the iSCSI initiator. See iSCSI Network Configuration Requirements on page 6. Volume access is not properly set for all vmknics to login. If using IP ACLs, access must be granted to all VMkernel ports bound to the iSCSI initiator.
If using Broadcom iSCSI offload NICs and using IQN for volume access, an IQN entry is required for each Broadcom iSCSI offload NIC that is bound to the iSCSI initiator. Array limits of iSCSI sessions exceeded Session limits on ESX server need to be lowered. The Broadcom iSCSI offload does not support jumbo Logins from Broadcom NIC with iSCSI offload cannot frames. For vmknic and vswitch, MTU must be set to be seen 1500. The values for the Broadcom session limits are Do not see the expected number of sessions for documented in the vSphere 4.1 and 5.0 Configuration Broadcom NIC with iSCSI offload Maximums document. esxcli equallogic commands are not recognized (ESX The hostd agent was not restarted after the plugin 5.0 only) installation. This is expected behavior in the following cases: Your configuration is exceeding one of the three EHCM maximum settings (TotalSessions, VolumeSessions or MemberSessions). For example, if you have a single member pool, and membersessions is set to the default value of 2, you will only see 2 sessions created to each volume in the pool, regardless of the number of VMkernel ports configured for iSCSI. The MEM has determined that creating additional iSCSI sessions will not improve performance. For example, doubling up on either array or host eth ports will not improve performance in most cases. Your hosts are exceeding PS group or pool session limits, and the multipath sessions are being automatically reduced by the storage array.
24
25
Creating portgroup iSCSI3 on vSwitch vSwitchISCSI. Assigning IP address 192.168.XXX.65 to iSCSI3. Creating new bridge. Adding uplink vmnic2 to vSwitchISCSI. Adding uplink vmnic3 to vSwitchISCSI. Adding uplink vmnic4 to vSwitchISCSI. Adding uplink vmnic5 to vSwitchISCSI. Setting new uplinks for vSwitchISCSI. Setting uplink for iSCSI0 to vmnic2. Setting uplink for iSCSI1 to vmnic3. Setting uplink for iSCSI2 to vmnic4. Setting uplink for iSCSI3 to vmnic5. Bound vmk2 to vmhba33. Bound vmk3 to vmhba33. Bound vmk4 to vmhba33. Bound vmk5 to vmhba33. Refreshing host storage system. Adding discovery address 10.127.XXX.210 to storage adapter vmhba33. Rescanning all HBAs. Network configuration finished successfully.
26
Used Ports 10
MTU 9000
PortGroup Name iSCSI3 iSCSI2 iSCSI1 iSCSI0 StorageHeartbeat Switch Name vSwitch1 PortGroup Name Private Num Ports 128
VLAN ID 0 0 0 0 0
Used Ports 1 1 1 1 1
MTU 1500
Uplinks
Used Ports 0
Uplinks
27
Setting vSwitch MTU to 1500. Creating portgroup StorageHeartbeat on vSwitch vSwitchISCSI. Assigning IP address 192.168.XXX.233 to StorageHeartbeat. Creating portgroup iSCSI0 on vSwitch vSwitchISCSI. Assigning IP address 192.168.XXX.231 to iSCSI0. Creating portgroup iSCSI1 on vSwitch vSwitchISCSI. Assigning IP address 192.168.XXX.232 to iSCSI1. Creating new bridge. Adding uplink vmnic4 to vSwitchISCSI. Adding uplink vmnic5 to vSwitchISCSI. Setting new uplinks for vSwitchISCSI. Setting uplink for iSCSI0 to vmnic4. Setting uplink for iSCSI1 to vmnic5. Bound vmk2 to vmhba40. Bound vmk3 to vmhba41. Refreshing host storage system. Adding discovery address 10.127.XXX.210 to storage adapter vmhba41. Adding discovery address 10.127.XXX.210 to storage adapter vmhba40. Rescanning all HBAs. Network configuration finished successfully.
Resulting configuration:
$ esxcfg-vswitch -list --server 192.168.XXX.230 --username root --password password
Switch Name vSwitch0 PortGroup Name VM Network Management Network Switch Name vSwitchISCSI PortGroup Name iSCSI1 iSCSI0 StorageHeartbeat Num Ports 128 Num Ports 128 Used Ports 3 VLAN ID 0 0 Configured Ports 128 Used Ports 0 1 Used Ports 5 VLAN ID 0 0 0 Uplinks vmnic0 vmnic0 Configured Ports 128 Used Ports 1 1 1 Uplinks vmnic5 vmnic4 vmnic5,vmnic4 MTU 1500 Uplinks vmnic4,vmnic5 MTU 1500 Uplinks vmnic0
28
Index
N A adapters
listing
22 15
8 7
5-6, 10, 12
P plugin
enabling and disabling removing
15 13 1
configuration values
setting
configuring the EqualLogic MEM E EHCM ehcmd EqualLogic Host Connection Manager H host profiles I installation
EqualLogic MEM tasks performed upgrade using setup.pl using vCenter Update Manager using vSphere CLI commands on ESX 4.1 using vSphere CLI commands on ESX 5 verifying
PSP S
1, 17 17
sessions
listing
22 5, 7-8, 11, 15 15 21
See EHCM
20
U upgrade installation V
14
10 11 14 11 11 13 12 14 17
VMware ESX configuration VMware iSCSI Initiator VMware Management Assistant vSphere commands vSwitch vSwitch configuration vUM See vCenter Update Manager
11 5 7 7 7 6 7 8 18 7 8
29