Unsolved
This post is more than 5 years old
5 Posts
0
1626
August 30th, 2011 05:00
MirrorView/A iSCSI networking requirements
We are having great problems getting MirrorView/A working reliably again following a site move of one of the arrays (CX480 and CX120) and a complete change in the networking environment. At present the Management IPs and iSCSI ports are using the same VLAN. Is this a possible cause of the issues?
No Events found!
tkjoffs
159 Posts
0
August 30th, 2011 20:00
Having them in the same VLAN should not be an issue, but it would not be a best practice just from a possible network and QoS management issue.
christopher_ime
6 Operator
•
2K Posts
0
August 31st, 2011 21:00
We have a new KB article that is still "Pending" review and eventual release, but will be accessible by our clients once finalized. Curiously, this has been pending for 3 months now, but yes, there are issues with the iSCSI interfaces being on the same subnet as the SPA and SPB management ports. Specifically, when they are on the subnet, when attempting to enable the MirrorView paths it will fail with "Cannot access device". Fix is to place on separate subnets which arguably is best practice anyways for iSCSI traffic.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
September 1st, 2011 04:00
Christopher,
is that KB for general iSCSI best practices or for that particular issue only ?
kelleg
6 Operator
•
4.5K Posts
0
September 1st, 2011 15:00
For using the same subnet for the iSCSI and Mangement ports see emc235739. For all iSCSI Knowledgebase articles see emc245445.
glen