Help attaching 2nd SAN to vSphere.
I am having trouble adding a new EMC Unity 350F SAN storage to my vSpehre 6.0. I currently have a EMC VNWe SAN running LIVE data but I am migrating over to the Unity. I have created new VMkernal ports and vSpehre switch for iSCSI storage and assigned it to an IP. That Ip is also assigned to one of the Unity array ports. I have added that VMkernal to the Port bindings on the iSCSI software adapter, in addiiton to where my othe rVMkernal adapters are to my live VNXe SAN. The port status says 'not used' on my new binding. I cannot figure out why rescanning cannot find my new Datastore on the Unity SAN.
On the Unity SAN simply went through the wizard and added mi iSCSI Interfaces to get the IQN. Then when through the VASA process of addin gthe vCenter and ESXi Host to Unisphere and it sees them. But I get a message that ther eare not initiator logged into the system.
What step am I missing?
On the Unity SAN simply went through the wizard and added mi iSCSI Interfaces to get the IQN. Then when through the VASA process of addin gthe vCenter and ESXi Host to Unisphere and it sees them. But I get a message that ther eare not initiator logged into the system.
What step am I missing?
ASKER
I agree. Back to the basics. and yes I did and confirmed....I can ping and vmkping the 173.0.0.xxx ports I setup on the SAN.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have entered the IP address for the iSCSI software adapter -> Dynamic Discovery and re scan....nothing shows in LUN. I went back and added the iqn for static discovery, re scanned, still nothing in LUN and The network config tab still shows the VMKernal as NOT ACTIVE for the new SAN IP.
Are these SANs on different networks ?
time to start looking at the VMware logs, if the SAN does not show any connection.
time to start looking at the VMware logs, if the SAN does not show any connection.
ASKER
Andrew, I just figured it out. I had my VMKernal port static IP address assigned the identical IP address as the iSCSI Port of the SAN. I just changed it and now my LUNs showed up in the scan. Thank Goodness!
Glad you find the issue, and now have LUNs!
Have a good day!
Have a good day!
>Andrew, I just figured it out. I had my VMKernal port static IP address assigned the identical IP address as the iSCSI Port of the SAN
I saw you said that in the question when you first posted it but assumed it was a typo; should have posted earlier.
I saw you said that in the question when you first posted it but assumed it was a typo; should have posted earlier.
use ping and vmkping, and remember to send packets to the new SAN via the correct VMKernel portgrpoup...
and can you vmkping the the new SAN.
First Test!