David Ring

Virtualization & Storage

CISCO MDS – Verifying VNX &VMAX Connectivity

February 11, 2014September 15, 2014 Cisco, VMAX, VNX CISCO MDS, EMCVNX, FCID, FCNS, PORT, VMAXSomtimes you may have encountered an issue where a VNX/VMAX front-end port gets cabled tothe wrong MDS Switch Port that you had designed for and in fact the port description that wasapplied to the MDS Port is incorrect. In this case it is invaluable to have a command to verify theVNX/VMAX port connected to the MDS. There are many situations where this command wouldbe useful; for example you may not have the ability to do a physical check as the DC is remote andyou need to ensure the interface description that you are assigning the MDS FC Port is correct andresulting zoning configurations are accurate. Confirming these connections remotely through acommand on the MDS is very benneficial during these types of situations. Else you may end upzoning to ports you did not design for.

VMAX Example

So lets take an example: the design and expectation here is to have the VMAX Port 9G:1 connectedto MDS FC Interface 2/37 and the interface was given the relevant description:

(http://davering.files.wordpress.com/2014/02/1.jpg)

From this result we can see that the port was labeled as per design as VMAX 9G:1. Now we needto confirm this is the actual port connected to FC2/37.

To analyse the connectivity of a specific interface we first need to retrieve the FCID for this port:show interface fc2/37

(http://davering.files.wordpress.com/2014/02/21.jpg)

Now that we know the FCID is 0x010440, we can run our magic cmd to verify what VMAX Port isconnected to FC2/37 :

show fcns database fcid 0x010440 detail vsan 10

(http://davering.files.wordpress.com/2014/02/3.jpg)

From the output we can confirm that there is a problem; the expected VMAX Port was 9G1 but infact 7G1 is the VMAX port patched to FC2/37 (SYMMETRIX::000195701570::SAF-7gB::FC::5876_229). Thus either we update the description of the interface or have the correctVMAX Port patched.

To modify the description:interface fc2/37Switchport description VMAX20K-7g1no shutdown

VNX Example

Interface FC1/25 as per design is connected to Service Processor ‘A2′ front-end port 2:

(http://davering.files.wordpress.com/2014/02/vnx1.jpg)

Running show interface fc1/25 in order to confirm port description and retrieve the FCID:

(http://davering.files.wordpress.com/2014/02/vnx3.jpg)

Now that we know the FCID is 0x010500, we can query the FCNS database for details of what isconnected at the other end of FC1/25:show fcns database fcid 0x010500 detail vsan 10

(http://davering.files.wordpress.com/2014/02/vnx4.jpg)From the output we can confirm the correct port is connected from the VNX.

Another method of confirming the correct port is connected, is by gathering the WWPN from theVNX/VMAX port and then running the show flogi database interface fc 1/25 command on the MDS:

(http://davering.files.wordpress.com/2014/02/vnx2.jpg)

(http://davering.files.wordpress.com/2014/02/vnx5.jpg)

Reverse LookupFrom the VNX we can run a “naviseccli -h SP_IP port -list”:

(http://davering.files.wordpress.com/2014/02/vnx6.jpg)

From the output we can see that SPA_6(Logical Port) is connected to the MDS interface WWN20:19:54:7f:ee:e2:9e:f8.Given this information we can lookup the Interface Port number by issuing: show fcs database |include 20:19:54:7f:ee:e2:9e:f8

(http://davering.files.wordpress.com/2014/02/vnx7.jpg)Thus we can conclude from this output that the VNX Physcial Port SPA:2_2 is connected to MDSPort FC1/25.

Note: If we want to look up the details of all the switch ports on the MDS this is the command:show fcns database detail

One thought on “CISCO MDS – Verifying VNX &VMAX Connectivity”

1. bilunov77 says:

Reblogged this on 49514262200010 (http://495142622com.wordpress.com/2014/02/26/cisco-mds-verifying-vnx-vmax-connectivity/).

Reply (/2014/02/11/cisco-mds-verifying-vnx-vmax-connectivity/?replytocom=312#respond)

Blog at WordPress.com (https://wordpress.com/?ref=footer_blog). The Big Brother Theme(https://wordpress.com/themes/big-brother/).

Follow

Follow “David Ring”

February 26, 2014 at 9:09 pm