Skip to main content

vicfg-mpath35 - configure multipath settings for Fibre Channel or iSCSI LUNs


 vicfg-mpath35 [OPTIONS]


vicfg-mpath35 provides an interface to configure multipath settings for Fibre Channel or iSCSI LUNs on ESX/ESXi version 3.5 hosts. Use vicfg-mpath for ESX/ESXi 4.0 and later hosts.


Prints a help message for each command-specific and each connection option. Calling the command with no arguments or with --help has the same effect.
--list | -l
Lists all LUNs and the paths to these LUNs through adapters on the system. For each LUN, the command displays the type, internal name, console name, size, and paths, and the policy used for path selection.
--policy | -p
Sets the policy for a given LUN to one of "mru", "rr", or "fixed". Most Recently Used (mru) selects the path most recently used to send I/O to a device. Round Robin (rr) rotates through all available paths. Fixed (fixed) uses only the active path. This option requires that you also specify the --lun option.
--state | -s
Sets the state of a given LUN path to either "on" or "off". This option requires that you also specify the --lun and --path options.
--preferred | -f
Sets the given path to be the "preferred" path for a given LUN. This option requires that you also specify the --lun and --path options.
--query | -q
Queries a specific LUN for its information and print it. This option requires that you also specify the --lun option.
--path | -P
Specifies the path to use in other operations. You cannot use this option by itself.
--lun | -L
Specifies the LUN to use in other operations. You cannot use this option by itself.
--detailed | -d
Displays all information about a LUN and its paths including the vml name of the LUN.
--bulk | -b
Shows all LUNs and paths in a format easily parsed by scripts.
--hbas | -a
Prints the list of HBAs that can be identified by a unique ID. This option lists Fibre Channel and iSCSI devices. Parallel and Block devices do not appear in the list.
--vihost | -h
When you execute this command with --server pointing to a vCenter Server system, you can use --vihost to specify the ESX/ESXi host to run the command against.


List all LUNs and the paths to these LUNs through adapters on the system:
 vicfg-mpath35 --server <servername> --username <user name> 
    --password <password> -l
Set the policy for a specific LUN. Requires --lun is also specified to indicate the LUN to operate on:
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> --policy mru --lun vmhba0:8:0
Set the state for a specific LUN path. Requires both --lun and --path are specified. This operation may appear to fail if there is active I/O on a path that is set to "off":
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> --state <on|off> --path <path flag> --lun <lunname>
Set the given path to be the preferred path for the given LUN. Requires both --path and --lun are specified:
 vicfg-mpath35 --server <server name> --username <user name> 
    --password <password> --preferred --path vmhba0:8:0 --lun vmhba0:8:0
Query the information on a specific LUN:
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> --query --lun vmhba0:8:0
Indicate which LUN to operate on. You can specify the LUN either with its internal VMkernel vmhba name (vmhbaX:X:X) or with its vml name as found in /vmfs/devices/disks:
 vicfg-mpath35 --server <server name> --username <user name> 
    --password <pasword> --policy mru --lun vmhba0:8:0
Return a bulk path listing suitable for parsing:
 vicfg-mpath35 --server <server name> --username <user name>
    --password <password> -b

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N