Skip to content
Virtual Storage Zone
Virtual Storage Zone

Primary Navigation Menu

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

automation

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

Quickly finding what port a WWN is associated with on a Cisco SAN

If you are like pretty much everyone I know who lives in the Storage World you seldom know what port on your SAN Fabric a WWN is connected with.  With Cisco you end up using device manager or fabric manager to try and find it – it works but I’m a command line kind of guy… So I end up logging into each switch in my fabric and doing the ole “show flogi database” routine..   If you’ve got a switch or two it’s not that painful, but when you grow beyond that it’s just plain annoying. I’m tired of doing that.  I’m tired of logging in to countless switches until I come across the correct switch.  I finally got annoyed enough to do something about it.  I decided to write a simple Perl script to automate the whole process. Check out the results below:   [box] cincystorage@symcliserver pub $ ./flogi_search.pl 51 192.168.1.50,fc3/21,50:00:09:72:08:3b:81:51 192.168.1.50,fc4/25,20:11:00:11:0a:00:4a:51 192.168.1.50,fc4/26,20:12:00:11:0a:00:4a:51 192.168.1.50,fc4/19,10:00:00:00:c9:88:7b:51 [/box]  Read More →

2013-10-23
By: Mark May
On: October 23, 2013
In: Networking

Creating Virtually Provisioned Thin Devices using Perl on the EMC VMAX

As a storage administrator one of most boring tasks I have to do is making and allocating new storages to hosts.  To me it’s the equivalent of creating a user.  Easy to do, but very boring.  If you know me at all, which you probably don’t, you know I hate boring.  For a lot of people it’s just a few right clicks in SMC/Unisphere and you’ve got yourself a new LUN.   For me it’s a quick SSH into a server with SYMCLI, a few edits to files, a few commands, and bam. I’d rather spend my time working on future planning, new architecture, or almost anything else. I finally had enough free time to write some Perl code which parses a simple text file to create new Meta devices on an EMC VMAX array. Actually creating a new Meta device is a fairly simple thing: First you create the thin devices, then you combine them all togetherRead More →

2013-01-29
By: Mark May
On: January 29, 2013
In: Storage

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.