UCSM 2.1(1a) zoning?

[DON PETERSON]

I just completed my upgrade to 2.1(1a) and need some help.  I have a NAS server attached to the FI's and configured as an FCoE storage port.  I also have a Compellent SAN directly attached to the FI's.  We do not have any upstream switches for zoning or anything.  Before the upgrade I had zoning disabled on my VSAN and everything worked fine; I just did LUN masking on the SAN side to secure access to the LUNs.  Since the upgrade and having zoning now enabled on the VSAN my NAS cannot see the SAN anymore.  I know it's because there is no zone created for it like there are for my blades.  My question is how can I create a zone for the NAS so it can access it's LUNs on the SAN again?  I've looked all through the CLI and the funtionality is not in the NXOS.  Any assistance would be greatly appreciated.

Thanks,

Don

[kg6itcraig]

Make your FCoE vLAN ID one off and that usually gets around stuff like this.

My UCS Blog http://realworlducs.com

[DON PETERSON]

Craig, thanks for the response.  I tried creating another VSAN with zoning disabled and assigned that VSAN to the ports the NAS is connected to.  It still could not see the SAN.

[Robert Burns]

Don,

Did you review the configuration guide?  It's all documented there.

http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.1/b_UCSM_GUI_Configuration_Guide_2_1_chapter_011011.html

Highly suggest you review, it's not as simple as you might assume.

The overall process involves three steps:

1.Enable FC Zoning for the desired VSAN

2.Create a Storage Connection Policy

3.Create a vHBA Initiator group

a).in Servic Profile

b).in SAN Connectivity Policy and apply it to Servie Profile

Regards,

Robert

[DON PETERSON]

Robert, thanks for the reply but this is an "external" server not a UCS blade so there is no service profile or vHBA.  I have a Dell server acting as a NAS that is connected to a port on each FI.  Those ports are configurted as storage ports.  Before the upgrade the server could see the SAN which is connected to the FI's as well.  I did go through the document you referenced before making this post.  I had hoped there was a command to manually create a zone and add the initiators from the server and SAN to it.  I do have a SAN and storage connectivity policy created, but again there is no service profile involved for the NAS.

[Robert Burns · Accepted solution]

Expecting a direct attach NAS to see a direct attach array is not supported.   You were probably leveraging default zoning which allows "everything to see everything".  As you said you were relying on masking for security. 

We purposely removed this functionality (default zoning) due to problems we were seeing.  The fc zoning features is intended for blade <-> target communicaiton only, not NAS or other direct attach device <-> target zoning.

Regards,

Robert

[DON PETERSON]

Thanks for clearing that up Robert; it's understandable but disappointing that a feature like that would be removed. Regards,

Don