adding new SAN Storage connecting to UCS

jalmishal · ‎06-05-2018

Hello everyone,
I am trying to adding new SAN Storage since the EMC VNX 5500 SAN have issue with low Disk Space .

We have the following equipment:

3 x Cisco UCS 5108 Blade Server Chassis configured in HA
With full UCS B200 M4 / B230 M1 Blades Servers. all are boot from SAN
2 x Cisco UCS 6296 Fabric Interconnects
2x MDS 9148 San Switch

1 x EMC VNX 5500 SAN

And The goal of the project is adding New SAN Storage server either ( Netapp or IBM or EMC on (FC) and attached to UCS. and without conflict with the current Storage.

this is short what I want to do.

The New SAN Storage Server Have one HBA card with to ports and already connected to (MDS 1 and 2) on port 11 with same VSAN.#2

I've been post before about if need to create new VSAN with add more Uplink as advice I’ve received also the utilization show no need since we have more than enough uplink ports (FC0=6ports FC1=6ports) = total 12Ports for uplink.

Now some of Blades are already shutdown and I need to configure it with New storage either boot from San or just attached
I've tried following several guides via Google but with no luck.always stuck on MDS configuration

so, I'm not really sure what the requirements are.
If anyone can offer some insight or suggestions with little guide or steps into this it would be greatly appreciated. As I'm not experienced with with San..

Niko Nikas · ‎06-07-2018

Hello,

If you have the new storage connected to the MDS already (and the ports come up fine), then the next step I would take is to zone the storage so that the servers can access it.

Since you are using VSAN 2 you'll likely want to see what the active zoneset for that looks like.

show zoneset active vsan 2

This will show you the zoneset, split up by the zones within it (assuming there are zones present)

You can determine which zones are for which server by looking at the WWNN/WWPN values in each zone and then comparing these to what you have assigned to each server.

Once you've isolated which zones you want to modify you will want to add the new end storage device's WWPN/WWNN to the appropriate zones. Once these are added and the zoneset is activated (no changes will actually become 'active' until it is activated) then the servers should be able to communicate with the end storage.

The below MDS guide walks through the CLI commands for how to perform these changes.

https://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/san-os/quick/guide/qcg_zones.html

--

Niko

jalmishal · ‎06-19-2018

sorry for late replay you , thank you very much for your efforts.

Currently, I've take one pwwn from one test blade and tried to add it to to the new zone on MDS1 as below

switch# config t

switch(config)# zone name ZOpenE vsan 2

switch(config-zone)# member pwwn 20:01:00:25:B5:1A:00:01

switch(config-zone)# zoneset name test_zoneset vsan 2

switch(config-zoneset)# member ZOpenE

switch(config-zoneset)# zoneset activate name test_zoneset vsan 2

then i got this warning

WARNING: You are trying to activate zoneset test_zoneset, which is different from current active zoneset MDS-01-Main. Do you want to continue? (y/n) [n]

still I'm not sure is I'm in right way or no ? shall I press Y :)

due I read that the MDS can only have one zoneset active at a time per switch per vsan. so in this case I'll lose the current zoneset ?

and here some info

show zoneset active vsan 2 on our MDS 1 / 2

zone name Hyper-V-03-P1-EMC vsan 2
fcid 0xb10000 [pwwn 50:06:01:64:3e:b0:13:6c]
fcid 0xb10100 [pwwn 50:06:01:6c:3e:b0:13:6c]
fcid 0xb10a00 [pwwn 50:06:01:65:3e:b0:13:6c]
fcid 0xb10b00 [pwwn 50:06:01:6d:3e:b0:13:6c]
fcid 0xb10301 [pwwn 20:01:00:25:b5:3a:00:00]

zone name LSMD-EMC vsan 2
fcid 0xb10000 [pwwn 50:06:01:64:3e:b0:13:6c]
fcid 0xb10100 [pwwn 50:06:01:6c:3e:b0:13:6c]
fcid 0xb10a00 [pwwn 50:06:01:65:3e:b0:13:6c]
fcid 0xb10b00 [pwwn 50:06:01:6d:3e:b0:13:6c]
fcid 0xb10202 [pwwn 20:01:00:25:b5:3a:00:01]

show vsan

vsan 1 information
name:VSAN0001  state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid  
operational state:down

vsan 2 information
name:MDS-01  state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid  
operational state:up

show int brief

Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
              Mode   Trunk                          Mode  Speed  Channel
                     Mode                                 (Gbps)
-------------------------------------------------------------------------------
fc1/1      2      auto   on      up               swl    F       8    --
fc1/2      2      auto   on      up               swl    F       8    --
fc1/3      2      auto   on      up               swl    F       8    --
fc1/4      2      auto   on      up               swl    F       8    --
fc1/5      2      auto   on      up               swl    F       8    --
fc1/6      2      auto   on      up               swl    F       8    --
fc1/7      2      auto   on      up               swl    F       8    --
fc1/8      2      auto   on      up               swl    F       8    --
fc1/9      2      auto   on      up               swl    F       8    --
fc1/10     2      auto   on      up               swl    F       8    --
fc1/11     2      auto   on      errDisabled      swl    --           --

please help