Hi Habibalby,

The communication between the VNXe and VCenter/ESX goes through the data ports ie the interfaces created on data ports using shared fodler server or iSCSI server.

You can keep mgmt network and data network of VNXe on seperate VLANs just as in VMware.

Regards

Shivanand

Thanks Shiv,

That's what I thought of, will move the mgmt of VNX to the same vLAN as

center.

On 31 Jan 2013 16:52, "Shivanand Xavarad"

Hi,

The current EMC AX4-5i in production that gonna replaced with VNXe is detecting the Management Network "Service Console" of the esx is through the iSCSI VMKernel portgroup that connected to the Switch where the SAN Storage is connected too. Will this be applicable with the VNXe, by creating an IP Subnet same with the one that is currently configured in the ESX iSCSI Portgroups? and the ESX will get connected to the Storage targets?

Or its a must to put the VNXe Management network beside the ESX Management Network/Service Console vLAN? in order to get connected to the Storage Target.

Thanks,

Hi Habibalby,

Configuring the VNXe for ESX involves in 2 steps,

1) Add respective ESX hosts (its recommended to add the hosts using VCenter). You are entering VCenter IP address or the Mgmt IP address of ESX host. You need to navigate to Unisphere ==> Hosts ==> VMware to add hosts to VNXe.

2) Once the hosts is added to VNXe while creating the datastores you choose respective hosts to provide them access.

Configuring ESX to access the VNXe storage involves, adding iSCSI IP address which are created on the VNXe here we are not using the VNXe mgmt IP address at all.

The iSCSI VMkernal portgroup on ESX and the iSCSI servers IP address needs to be in same subnet.

W.r.t to 2nd query there is no need to to put VNXe mgmt n/t beside the ESX mgmt network.

You can refer to the document https://support.emc.com/docu31486_VNXe-Series-Using-a-VNXe-System-with-VMware.pdf?language=en_US for assistance.

Regards

Shivanand

Hi,

I believe I have done everything correctly, but still I can't see the datastore being provisioned to the ESX host.

The VNXe3150 is connected in the same subnet where the ESX management IP is configured.

The ESX has got 4 pNICs that are dedicated for iSCSI traffic only and connected to the iSCSI pSwitches.

The VNXe3150 SPA & SPB ports are connected to the iSCSI pSwitches.

In VNXe --> Settings --> Servers -->iSCSI Servers Settings i have added two IP Address one for SPA and one for SPB they are 10.90.8.1 and 10.90.8.2

In the ESX host, I have configured an iSCSI portgroup "VMKernel" and assigned an IP 10.90.8.100

ESX host can reach both VNXe iSCSI Server IPs using vmkping command.

ESX host can reach the management IP Address of the VNXe SAN.

With regards to all of the above settings, I'm still can't provision VMFS DataStore to the ESX Server.

I have deleted the manual Datastore as well as the ESX host. And I added the ESX host again using the Find Wizard, and prompt me to create a Datastore and created, but cannot provision the LUN to the ESX Host.

Execution Errors: The storage resource was created successfully on VNXe but the remote datastore creation failed on one or more VMware ESX servers. You need to create the datastores for those VMware ESX servers manually through vCenter or ESX servers. If you are using both IPv4 and IPv6 addresses, the NFS/iSCSI server on the VNXe system and the ESX host may have incompatible IPv4 or IPv6 addresses. Ensure that the ESX host is not in maintenance mode and the datastore name is valid. (Error Code:0x5c00005)

Any help?

Thanks,

I'm attaching the screen shots from the VNXe3150 system;

Host Access;

VMWare Hosts

iSCSI Servers Settings

Hosts Subnet;

Error: Create iSCSI DataStore

I have create subnet for all; iSCSI Network and Subnet for the Management IP, but still I can't provision the DataStore to the ESX Host.

Can you try creating the datastore in vSphere manually? If that does not work there could be some network issues.

The ESX server software you are using, is it a evaluation or a limited edition? We've seen similar issues in such cases.

Hi,

Well actually, found that the iSCSI adapter has a binding with other iSCSI

VMKernel PortGroup, after removing that, I was able to present the LUN.

Surprised, when I configured MPIO and presented another LUN, I wasn't able

to format the LUN and presented with an error Ds.datastore failed to mount,

when I put Back the MTU to 1500, I'm able to format the LUN.

I'm still in the fail over test phase, by disconnecting SPA Ctrl and SPB,

found two minutes of disconnection and lost access to data store and VM

while copying files using the vSPhere console and after LUN shifted to SPB,

connection resumed slower speed but completed. Followings, I'm testing this

fail over on SQL/Exchange/DC and will see what will happen to the

application during the LUN fail over to the other SP.

Will update you further.

This is the issue I'm facing now

https://henriwithani.wordpress.com/2012/01/09/changing-mtu-on-vnxe-disconnects-datastores-from-esxi/#comment-426

changing the MTU causes the ESXi (5.1.0, 799733) to loose all iSCSI datastores and even changing the settings back the datastores are still not visible on ESXi.

Also found that if two iSCSI PortGroups configured, one without uplink and the second one with two uplinks, I will not be able to reach the iSCSI target ip address unless I remove the iSCSI portrgoup "the one with no uplinks".

It seems VNXe 3150 is not matured enough when it comes to complex setup along with Jumbo Frames. Many documents from EMC says Jumbo Frame configured correctly, I wonder how they have configured if changing MTU size from default 1500 to 9000 will cause loose of datastore and connectivity issues, how come the Jumbo Frame/MPIO would be configured?

Thanks,

Hello,

For the testing purpose I have managed to connect an ESXi host to the VNXe which it's management in the same as the VNXe.

Now I want to add my production hosts to the VNXe, but the VNXe cannot connect to them, nor by vCenter IP or individual ESX host.

VNXe Management ip address on 192.168.40.x/24

vSphere/vCenter Management Network is 172.16.40.x/24

Each ESX host can reach to the iSCSI Servers/Target in the VNXe3150

Any help?

Thanks,

The connection could not be established to the remote server. Either the credentials are incorrect or there is a network issue.