This post is more than 5 years old

1 Rookie

 • 

54 Posts

3334

September 3rd, 2008 10:00

Connectivity Status "inactive"

I have an AX4, and attached a host to it via iSCSI a few months back. I am attaching a new host to it now, and it's coming up under connectivity status as "inactive." I recall the setup of the host a few months back as being pretty quick and simple to do, but seeing I don't do these regularly at all, I'm guessing I'm missing a relatively simple step to activate this. The LAN port has a static IP address as well do the 2 iSCSI ports, and they all seem to be communicating with each other. Any suggestions as to what I need to do to "activate" this connecton?

Thanks,
Jon

6 Operator

 • 

4.5K Posts

September 8th, 2008 14:00

You might want to look at the AX4 series web site:

http://www.emc.com/ax4support

Look under the Install section - you find a configuration that matches your configuration. If you're using Windows 200x, you need to setup the Microsoft iSCSI Initiator. Selecting a Host will lead you to a Installation guide.

glen

1 Rookie

 • 

54 Posts

September 10th, 2008 09:00

Thanks Glen. I'm printing out a PDF now.

Here's an oddball one for you:
I have the iSCSI initiator installed, and at one time successfully logged into a port and even presented a 100 GB virtual disk onto my host server. However, I noticed in Navisphere Express that when it listed my server as a connection, the IP address associated with the connection was an IP address I had assigned to the iSCSI ports versus the IP address of my LAN adapter. At this point I knew it was a binding order issue, so I checked it, and sure enough it was binding my 2 iSCSI adapters and then my LAN adapter 3rd. I then adjusted the binding order of the 3 NICs, as 1 attaches to my LAN, and the other 2 to the AX-4 SCSI ports. Once I changed the binding order, I am now unable to log onto my "inactive" ports. Any thoughts/ suggestions?

Thanks,
Jon

1 Rookie

 • 

54 Posts

September 10th, 2008 11:00

THANK YOU GLEN!

I customized my PDF unique to my environment, and now I am all set. Both SPs are connected and active, and the appropriate IP LAN address is listed in Navisphere Express (opposed to the iSCSI port IP addresses...which like I said was a binding order issue).

I am so thankful for pointing out that link to me!

-Jon

6 Operator

 • 

4.5K Posts

September 10th, 2008 11:00

Once you get the guide printed, see the section for setting up the iSCSI initiator. If you originally logged in the iscsi initiators using the "default" source NIC, then the initiator will use any NIC on the host to connect to the array.

Look in the Persistent Targets tab in the initiator control panel, select a connection and click on Details - look at the Source IP address - if it's "default" you'll need to delete the Persistent Target, Log Off the connection in the Targets tab, the log back in following the steps in the installation guide (you need to specifically select the source NIC in the Advanced section of the logon screen). You may also need to deregister the connections (paths) on the array in Connectivity Status (you'll need to move the host out of the Storage Group first).

glen
No Events found!

Top