In ESX 3.5
1.Determine the available and active paths using the esxcfg-mpath program. The following output will provide the host initiator WWPN to storage controller WWPN mapping.
2.From the storage controller that is hosting the LUN, the command fcp show adapters may be used to display WWPNs of the FCP target ports. This output may be used to determine if the Active path is using one of the FCP target ports of the storage controller.
3.From the ESX host, use the command, excfg-hbadevs, to list the HBA devices. Note that the HBA name includes everything up to the first ":".
4.Rescan all of the HBAs using the esxcfg-rescan command. This will need to be done for each HBA attached to the ESX host.
5.Use the esxcfg-mpath command to change the host to use a primary path for the LUN. [root@esx-rtp]# esxcfg-mpath -p fixed --preferred -L vmhba2:0:1 --path=vmhba1:1:1
vSphere has changed the command structure, use esxcli command to list and manage the path or use vCenter manage path interface.
Subscribe to:
Post Comments (Atom)
Labels
15.2
(1)
Active Directory
(1)
agents
(1)
ai
(8)
AlwaysOn Group
(1)
Attributes
(1)
automation
(1)
Azure
(3)
Azure Log Analytics
(1)
Azure Logical App
(1)
Azure WVD
(1)
business-integration
(1)
Cisco
(3)
Citrix
(2)
database
(1)
developer-experience
(1)
Direct Server Return
(1)
enterprise
(1)
enterprise-agents
(6)
future-of-work
(1)
governance
(2)
Hybrid Cloud
(1)
integration
(1)
Junos Space
(2)
Kubernetes
(1)
Load Balancer
(2)
Microsoft
(1)
Migration
(2)
MS CRM
(2)
MS Exchange
(5)
MS Office
(2)
MS SQL
(2)
MTV
(1)
NetApp
(1)
Network
(1)
NPS
(1)
observability
(1)
OpenShift
(2)
operating-model
(1)
orchestration
(1)
Others
(6)
Polymorphic
(1)
PostgreSQL
(1)
product-management
(1)
Project Management
(3)
RADIUS
(1)
RedHat
(1)
reliability
(1)
Rollback
(1)
RSA
(1)
security
(1)
Sharepoint
(8)
software-business
(1)
SQL
(1)
strategy
(1)
talent-strategy
(1)
TechTips
(1)
Troubleshooting
(1)
trust
(1)
UCS
(1)
Virtualization
(2)
VMWARE
(14)
No comments:
Post a Comment