Unsolved
This post is more than 5 years old
38 Posts
0
2005
VNX initiator issue
Hello, can someone help me with this issue:?
I´m trying to enable a mirrorview connection between a CX3-10c & a VNX-5500 using naviseccli.
I did the right zonning, also ugrade the flare to the latest patch: cx3-10c = 3.26.010.5.032 & vnx = 5.31.000.5.008. Mirrorview/S is installed in both arrays as well.
The issue is I can see cx3-10c initiators in the VNX conectivity status window, but can NOT see the VNX initiators in the cx3-10c connectivity status windows.
I already drop the zonning and recreated again and still the same problem. I also installed SanCopy and tryed to configure but the same problem with de SANcopy initiators for the VNX box.
best regards
omar
Rainer_EMC
8.6K Posts
0
May 15th, 2011 13:00
Hi Omar,
Since the VNX currently cannot share storage domain you need to do the MV setup using the CLI
Just search the knowledgebase (Primus) - there is an article there with the exact steps.
Rainer
Omar2008
38 Posts
0
May 15th, 2011 14:00
Thank you for your answer Rainer!!
I already try to connect using the cli I think is the same primus..... It doesnt find the port!
Can I share the domain by CLI??
Omar
Sent from my iPhone
galak1
4 Posts
0
May 19th, 2011 02:00
Hi,
I have exactly the same issue, and when I enter the CLI command to configure the mirror connection on CX:
naviseccli –h 1.2.3.4 -user … -password … -scope … mirror –enablepath -connectiontype fibre
The response is
Cannot acces device
Best regards
Kumar_A
727 Posts
0
May 19th, 2011 08:00
You can use Primus case emc262013 to set up the MV connections. From there, basically anytime you need to call to an object outside of the VNX "domain of 1" you need to use the CLI. From the RNs:
EMC Navisphere Secure CLI must be used in this release to configure MirrorView and create mirrors. Specifically, the following operations require the use of CLI
Enable and disable MV connections
Add secondary image
Remove secondary image
Omar2008
38 Posts
0
May 19th, 2011 08:00
Hello Galak,
In VNX family the MV port is the lowest port so use Port 0 in the zoning config
Omar
Sent from my iPhone
galak1
4 Posts
0
May 19th, 2011 10:00
Omar,
you right , know we must used the SPA0 and SPB0.
After a couple of hours, I have tried again but successfully the CLI enablepath, now all is good on mirror connection both side.
Now I can't add a secondary image because the VNX is not on CX domain
I m looking for a CLI command to add a secondary but at the moment I don t find anything
Omar2008
38 Posts
0
May 19th, 2011 10:00
Hello Galak,
You have to use the CLI to add the secondary image, the command is:
To add the destination LUN (image) to the mirror, type:
$ /nas/opt/Navisphere/bin/naviseccli -h
Example (to add destination LUN 17 as a secondary image to the
remote mirror aviator_m0, which has the source dos control LUN):
$ /nas/opt/Navisphere/bin/naviseccli -h aviator-spa -user
nasadmin -password nasadmin -scope 0 mirror -sync
-addimage -name aviator_m0 -arrayhost 10.6.1.112 -lun 17
Best regards
Omar
De: galak
Enviado el: jueves, 19 de mayo de 2011 11:21 a.m.
Para: Omar Garcia
Asunto: New message: "VNX initiator issue"
EMC Community Network
VNX initiator issue
reply from galak in VNX Family - View the full discussion
1 Attachment
VNX & Mirrorview.pdf
galak1
4 Posts
0
May 20th, 2011 01:00
Many thanks Omar2008, all working fine !!! it s perfect