Skip to main content

Clariion CX, CX3, CX4 – How to add Storage Capacity to Attached Host






Microsoft Windows



1. If needed, add new drives to the storage system.


2. If needed, create a hot spare using Navisphere Manager.


3. If needed, create an additional RAID group on the drives using Navisphere Manager.


4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.


5. Assign the new LUNs to the server using Navisphere Manager.


6. Verify that the new LUNs were assigned to the server using Navisphere Manager.


7. On the server, verify that the server has access to the LUNs:


a. On the Windows desktop, right-click My Computer and click Manage.


b. In the left pane of the Computer Management dialog box, double-click on the storage icon.


c. Click Disk Management.


d. Verify that the LUNs that you added are listed in the right pane.


8. Start or restart the Navisphere Host Agent to push the server’s LUN mapping and operating system information to the storage system.


9. On the server, start PowerPath and verify that PowerPath sees all of the paths to the LUN.



Linux


1. If needed, add new drives to the storage system.


2. If needed, create a hot spare using Navisphere Manager.


3. If needed, create an additional RAID group on the drives using Navisphere Manager.


4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.





5. Assign the new LUNs to the server using Navisphere Manager.


6. Verify that the LUNs were assigned to the server using Navisphere Manager.


7. On the server, verify that all LUNS have entries in the /proc/scsi/scsi/ directory.


8. On the server, verify that each LUN has an entry in the appropriate HBA file:


· For QLogic HBAs, the entry is in proc/scsi/qlaxxx/hba_number


· For Emulex HBAs, the entry is in /proc/scsi/lpfc/hba_number


9. On the server, verify that the failover software recognizes all of the paths to the LUNs.


For example, for PowerPath, verify that PowerPath recognizes all of the paths to the LUNs using the powermt command: powermt display dev=all class=clariion


10. Partition the LUN and then create and mount a file system to make the LUN available to the operating system.


11. Run the Navisphere Host Agent to push the server’s LUN mapping and operating system information to the storage system.


12. Save the failover configuration.


For example, for PowerPath, save the PowerPath configuration using the powermt savecommand.





13. On the server, verify that the server and failover software sees all of the paths to the LUN.V


For example, for PowerPath, verify the configuration using the powermt display command.

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