Unsolved

This post is more than 5 years old

11 Posts

1520

March 14th, 2012 13:00

vnxe 3100 shared folder server issue

Hello all,

I am experiencing an issue where I have 2 shared folder servers setup (one for SPA and one for SPB).  Both are on the same subnet.  The issue is that I cannot ping or access the Shared Folder Server on SPB, therefore I cannot add any datastore on to that NFS datastore.  On SPA it works fine, I have created an NFS datastore and even provisioned a VM onto it.

My setup:

Server side:  2 pNICS active on one vSwitch, one vmkernel group (same subnet as shared folder servers).  vSwitch using IP Hash.  Switch has a etherchannel group for that pair of connections.  Follwed the VM sample Cisco configuration for this.

SAN side:  aggregated the 4 IO ports aka eth 10,11,12 and 13 together.  Currently only eth 10 and 11 from both SPs have cables plugged into switch.  On the switch have created a LACP channel group.  I have both Eth 10 and 11 from both SPs plugged into this second channel group.

Lets say the vmkernel is 10.0.0.1

Shared Folder Svr SPA is 10.0.0.2

Shared Folder Svr SPB is 10.0.0.3

Again from the esxi host I can vmkping the 10.0.0.2 but not 10.0.0.3.  From unisphere for 10.0.0.2 I can ping 10.0.0.1 but cannot do the same for 10.0.0.3

I am going to venture a guess that maybe the Channel Group on the switch created for the SAN may not have been confirgured properly??

This is just a test enviroment for now which is things are setup like this.  But perhaps maybe thats the reason as well??

Let me know of any suggestions or recommendations.

Thanks!

6 Operator

 • 

8.6K Posts

March 14th, 2012 16:00

Double check IP's, netmasks and routing

11 Posts

March 15th, 2012 13:00

Ranier,

IPs and everything is correct from the SAN side and the Host side.  Any other suggestions/recommendations?

Thanks

6 Operator

 • 

8.6K Posts

March 16th, 2012 06:00

Investigate and troubleshoot all components

You can try enabling the service ssh login and ping from there and look at svc_diag –state=network

The problem could very well be on the switch or client side though

70 Posts

April 3rd, 2012 12:00

Please ensure if the configuration for SPB shared folder server is same as in SPA where you are currently able to access the datastore..... if so you should be able to access the datastore and as recommended earlier remove LACP and verify if you still able to access the datastore. If still unable to access the datastore I would recommend you to open a service request with support for them to have a look into it. (I suspect the issue is with LACP configuration on the switch end).

Regards

Shivanand

No Events found!

Top