Skip to content
Virtual Storage Zone
Virtual Storage Zone

Primary Navigation Menu

Menu
  • Home
  • About Me
  • Business
  • Infrastructure
  • Podcast

Zone

Mapping Cisco SAN Switch Ports to Zone Names

This morning I found myself needing to know what server was attached to each and every port on a large Cisco SAN Fabric. This can be quite the effort if you don’t have excellent documentation.  You can query the fabric login (flogi) database, but that will map a fiber channel port to a wwn.  That’s a start, but unless you have a map of wwn to server, it’s largely ineffective at proving human consumable information.   mds9513# show flogi database ——————————————————————————– INTERFACE VSAN FCID PORT NAME NODE NAME ——————————————————————————– fc1/1 301 0x8a00b0 50:00:09:72:08:3a:81:a7 50:00:09:72:06:3a:80:02 fc1/2 301 0x8a00cb 50:00:14:31:90:6a:79:12 50:00:14:40:45:32:6a:75 fc1/3 301 0x8a00ca 50:00:14:31:90:6a:54:12 50:00:14:40:45:32:6a:54 fc1/6 301 0x8a00cd 50:00:14:31:80:6a:54:02 50:00:14:40:45:22:6a:54 fc1/12 501 0xa50001 50:00:09:72:08:3a:61:e4 50:00:09:72:06:3a:82:00 If you want to see which zones map to the wwpn, you can use the “show zone member <wwn>” command to see a list of all zones associated with the specified wwn: mds9513# show zone member pwwn 10:00:00:00:c7:ca:3b:b8 pwwn 10:00:00:00:c7:ca:3b:b8 vsan 95 zoneRead More →

2014-04-14
By: Mark May
On: April 14, 2014
In: Networking

Cisco Smart Zoning Concepts

For as long as most of us in the Fiber Channel space can recall SAN Zoning has been the base method of controlling access amongst SAN attached devices. A lot of us do this the classic Single Initiator / Single Target zoning – where one Host talks to one Array port.  In a Cisco SAN Fabric we have an easier way.  But first we need to understand why we do single initiator zoning. When a zone is created and an initiator/target pair added permissions are converted to an Access Control Lists (ACL) of Access Control Entities (ACE). The switch doesn’t care if the WWNs added are initiators or targets, its simply going to allow every WWN to talk to every other WWN in the zone. In our example 2 ACLs are created – one to allow the initiator to receive data from the target and another to allow the target to receive data from the initiator.  ThisRead More →

2014-04-09
By: Mark May
On: April 9, 2014
In: Networking

Recent Posts

  • Remote Offices shouldn’t be second class citizens
  • vBrownBag tackling VMworld (CTO Advisor #57)
  • Talking Intel Optane with James Myers (CTO Advisor #056)
  • Cloudified Snapshots done two ways
  • What the heck is tail latency anyways?

Copyright 2012-2016 Mark May. All Rights Reserved.