Virtualize SAN Infrastructure in Your Data Center
Today the industry spotlight is on server virtualization, the second stage of Cisco's Data Center 3.0 strategy.
As servers are virtualized, infrastructure becomes more dynamic and places new demands on SANs. Virtual machines (VMs) proliferate faster and move around the data center in ways that physical servers don't. Cisco SANs are optimized for virtual machines, allowing each machine, and each virtual host bus adapter (vHBA), to be separately:
- Identified: Each vHBA can acquire its own Fibre Channel identifier through N_Port_ID virtualization.
- Configured: Implement virtual storage area network (VSAN) membership, zoning, quality of service, and LUN mapping/masking.
- Monitored: Track login status and location, and monitor performance counters.
- Migrated: A vHBA's port world-wide name (pWWN) remains constant across VMware vMotion and port security.
- Diagnosed: Use FC Ping and FC Traceroute to troubleshoot connectivity and path choices.
But virtual machines are not the only things that move. Blade servers make it easier than ever to move physical servers around. The FlexAttach feature of NX-OS virtualizes the identity of the HBA. That allows you to assign the SAN identity of a server to whatever server logs in at that port, or it can follow the server (and its HBAs) wherever they join the fabric after a move.so you can assign the SAN identity of a server to whatever server logs in at that port, or it can follow the server (and its HBAs) wherever they join the fabric after a move.
Consolidating Fabrics
Finally, SAN fabrics themselves can be virtualized, enabling the consolidation of multiple physical fabrics into a more scalable, cost-effective infrastructure, just as virtual machines allow you to do with servers.
Cisco pioneered VSANs seven years ago when the MDS 9000 Family was introduced, and they form the basis of the industry's Virtual Fabric standard. VSANs provide isolation of traffic, fabric faults, and administrative responsibilities.
