Start a Conversation

Unsolved

This post is more than 5 years old

J

1463

March 28th, 2011 15:00

cx4-120 iscsi ports - why windows iscsi initiator aim to management ip address?

why my windows server iscsi microsft software initiator aim to the cx4 management port ip address,

how could this happen, am i able to reach luns via management ports.

the register in the Clariion conectivity status window refers to the host iscsi ports ip address, why?

very strange, if i installed powerpath it hangs up,

how destroy any tracer of microsoft iscsi software initiator settings to begin again.

any idea.

thank you.

mc

1 Message

March 29th, 2011 07:00

Did you configure IP addresses for the iSCSI ports on the CLARiiON? Once you do that than you need to go into MS iSCSI Initiator and add the iSCSI IP ports and not the management ports.

295 Posts

March 29th, 2011 09:00

yes that process already was done

the strange is that in the host, from HEAT reports, device configuracion shows the following info show

Raw Device
Vendor Product Rev Serial Number SP IP Capacity World Wide Name Bus Tid Lun
\\.\PHYSICALDRIVE2 DGC RAID 5 0428 CKM000xxxxxxx A xxx.xx.xxx.210 2306867200 60060160188624000a2d06d0d28edf11 4 0 0

and that ip belongs to management ports not the the iscsi ports why, how can re configure this.

thank you

mc

March 30th, 2011 13:00

Seeing that you cleaned up the iSCSI initiator, as for the remaining items in your original post, that column in the HEAT report is correct.  It lists the mgmt IP of the SP listed in the adjacent column.  This is simply as a reminder to the user of the LUN ownership (referencing the out-of-band mgmt IP).  It is not reference to the iSCSI targets (in-band) on the SP's.

As for correcting the reference in "Connectivity Status", did you update that?  With multi-homed hosts having multiple IP's where you want to control the interface associated with the out-of-band connectivity, best solution is to create the agentID.txt file as mentioned in the following Primus (versus changing bind order of interfaces on host or instead of reverting to manual registration of intiatior records).  Otherwise, you leave it up to Navisphere/Unisphere Agent to select the first in the host's bind order.  Key points are:

emc62479: "Ensuring Navisphere Agent binds to correct NIC in multi-homed server with multiple NICs"

1) File name is case-sensitive

2) On Windows, place file in same location as the service's executable (or as mentioned in the Primus reference location in the appropriate registry key)

3) Note the order of the contents (FQDN first, then out-of-band IP of host) each on its own line

4) Each line must end with a newline; therefore, when at the end-of-the-file, cursor should not be at the end of the last line which would be the IP in this case.  Basically there should be 3 lines in your file with the last one being blank.

5) Restart service (can be done online as the out-of-band connectivity is independent of the in-band connectivity) and refresh Navisphere/Unisphere

4.5K Posts

April 6th, 2011 14:00

Take a look at Knowledgebase emc118123

glen

No Events found!

Top