Skip to main content

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

SYNOPSIS

 vicfg-mpath35 [OPTIONS]

DESCRIPTION

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.

OPTIONS

--help
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.

EXAMPLES

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

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...