The Well Known Group Address is the group's iSCSI IP address.
So, your group has an iSCSI IP and then each port on the controller has an IP (eth0, eth1, eth2, eth3 (depending on the model you may have 1, 2 or 4 iSCSI ports (older models could also have 3 iSCSI ports)).
Be sure to always use the group's iSCSI IP in the ASM's connectivity section and not the IP from one of the eth-ports.
If you did use this, disable all but 1 of your iSCSI NICs and try to ping the group IP and all port IPs. If you cannot reach one or more of them, you need to check your networking as it would be a segregated iSCSI setup, which won't work with an Equallogic implementation.
Thank you for your reply, I actually changed the IP address in the initiator and that's ok, I have no error in the wizzard. In the configuration of PS Group ACCESS must uncheck "verify connection to PS Group" to avoid this error.
Now I can well create a hardware snapshot with DPM server on Hyper-V hosts
I'd recommend to configure everything from the ASM and not from the initiator. Just use the initiator to do the actual connection to the volumes (logins).
Dev Mgr
4 Operator
•
9.3K Posts
1
May 22nd, 2013 11:00
The Well Known Group Address is the group's iSCSI IP address.
So, your group has an iSCSI IP and then each port on the controller has an IP (eth0, eth1, eth2, eth3 (depending on the model you may have 1, 2 or 4 iSCSI ports (older models could also have 3 iSCSI ports)).
Be sure to always use the group's iSCSI IP in the ASM's connectivity section and not the IP from one of the eth-ports.
If you did use this, disable all but 1 of your iSCSI NICs and try to ping the group IP and all port IPs. If you cannot reach one or more of them, you need to check your networking as it would be a segregated iSCSI setup, which won't work with an Equallogic implementation.
jpottier
3 Posts
0
May 23rd, 2013 07:00
Hello,
Thank you for your reply, I actually changed the IP address in the initiator and that's ok, I have no error in the wizzard.
In the configuration of PS Group ACCESS must uncheck "verify connection to PS Group" to avoid this error.
Now I can well create a hardware snapshot with DPM server on Hyper-V hosts
thank you
Dev Mgr
4 Operator
•
9.3K Posts
0
May 26th, 2013 00:00
I'd recommend to configure everything from the ASM and not from the initiator. Just use the initiator to do the actual connection to the volumes (logins).