MDS9216i and EVA4k

[Sc_5]

Hello I ahve question regardin the replication over MDS9216i. I have added two EVA4k storages on two sites and formed a channel on MDS for replication. Only on one site I have managment station with CV installed. When I'm trying to manage both EVA's I got the message TIMEOUT , but on the managment server I have visible both luns from both EVA's:
The table lists path information associated with storage systems visible to this management agent.
System Node WWN Model Version Role OS SCSI Device
Port Target LUN Ping (µsec) Status
5000-1FE1-5009-EAE0 HSV200 5110 Slave Scsi2
0 0 0 149 Ready
5000-1FE1-5009-EAE0 HSV200 5110 Master Scsi2
0 1 0 152 Ready
5000-1FE1-5009-EAB0 HSV200 5110 Master Scsi2
0 2 0 1051 Ready
5000-1FE1-5009-EAB0 HSV200 5110 Slave Scsi2
0 3 0 1046 Ready

Could I manage those both EVA's over the extended SAN? What speciall setting muast be set on the MDS or for the zonning!?

[Jonathan Harris_3]

Are both switches in the same VSAN? If not, you'll have to enable Inter-VSAN Routing (IVR). Now, depending on what your 'channel' is, this could prove to be tricky.

If you're using FCIP with the gig ethernet modules, there is a restricted licence that comes with the module that permits you to use a basic form of IVR.

If your switches are connected with an ISL, then you will need an Enterprise licence to use IVR. This costs a lot of money, so it's usually best just to bring the two switches in to the same VSAN.

If you do need to use IVR, then the switches and the EVAs will need to go in to the IVR zoneset.

If your switches are both in the same VSAN and you are running an ISL between the switches then you need to make sure that zoning is set up correctly. Make sure your management appliance and both of your EVAs are in the same zone.

[Sc_5]

Hello, both EVA's are in teh same VSAN and zoning is proper because I can see LUN 0 from both EVA's on the managment station but I cant connect to the remote EVA when I start CommandView.
I just got a message: " The storage system is not responding to management command requests in a timely manner. This may be due to a prior management command request with excessively long response time, or a communication problem. CV EVA will recover automatically when the storage system is able to respond to management commands. Management command access to the storage system does not affect host I/O."

Here is the config of the MDS
zone default-zone permit vsan 1
zone name Zone1 vsan 1
member pwwn 50:00:1f:e1:50:09:ea:e9
member pwwn 50:00:1f:e1:50:09:ea:ed
member pwwn 21:00:00:e0:8b:8e:1b:10

zone name Zone2 vsan 1
member pwwn 21:00:00:e0:8b:8e:1b:10
member pwwn 50:00:1f:e1:50:09:ea:b9
member pwwn 50:00:1f:e1:50:09:ea:bd

zoneset name ZoneSet1-Bosiljevo vsan 1
member Zone1

zoneset activate name ZoneSet1-Bosiljevo vsan 1
ivr zone name IvrZone1
member pwwn 50:00:1f:e1:50:09:ea:ed vsan 1
member pwwn 50:00:1f:e1:50:09:ea:bd vsan 1
member pwwn 50:00:1f:e1:50:09:ea:b9 vsan 1
member pwwn 21:00:00:e0:8b:8e:1b:10 vsan 1
member pwwn 50:00:1f:e1:50:09:ea:e9 vsan 1
ivr zone name IvrZone2
ivr zoneset name IvrZoneSet1
member IvrZone1
ivr zoneset name IVR_ZoneSet2
ivr commit

interface fc1/1

interface fc1/2

interface fc1/3

interface fc1/4

interface fc1/5

interface fc1/6

interface fc1/7

interface fc1/8

interface fc1/9

interface fc1/10

interface fc1/11

interface fc1/12

interface fc1/13
switchport description PORT13_EVA4k_BOSILJEVO_CNT_GORNJI_FP2
channel-group auto
no shutdown

interface fc1/14
switchport description PORT14_EVA4k_BOSILJEVO_CNT_DONJI_FP2
channel-group auto
no shutdown

interface GigabitEthernet1/1
ip address 172.18.0.20 255.255.255.0
switchport description Bosiljevo GigE1/1
switchport mtu 2300
no shutdown

interface GigabitEthernet1/2
ip address 172.18.1.20 255.255.255.0
switchport description Bosiljevo GigE1/2
switchport mtu 2300
no shutdown

interface iscsi1/1

interface iscsi1/2
no shutdown

interface mgmt0
switchport speed 100
ip address 172.17.0.175 255.255.255.0

MDS9216i_BOS#