Unsolved
This post is more than 5 years old
89 Posts
0
1040
New interface IP question
Hello,
I'm having a hard time trying to get a new IP network to work in my existing setup so let me explain the current setup and what I'm trying to do.
Current setup is that the IP network for the data movers, iscsi, and cifs servers are 10.21.3.153, 10.21.3.154, 10.21.3.155 and this works and we have been using it for years. Now I need to add a new IP network 172.18.1.x to this so I created a new network interface with IP 172.18.1.10 subnet 255.255.255.0 and the Celerra automatically created the rest including the route for this new 172.18.1.0 network. This new 172 network is for iSCSI and I created the target and luns but I can't get it to be seem on my vmhost. Actually the vmhost can see and ping the IP 172.18.1.10 but the Celerra can not ping the vmhost IP even though they are on the same vlan and the vmhost has IP 172.18.1.27 for the iSCSI vmkernel. It would seem to be a routing issue on the Celerra side but I don't know where to look or check as this is the weird part if the vmhost can see and ping the Celerra 172 IP then it would seem routing is working but the Celerra can not ping it's own 172 IP nor any other 172 IP even though everything is on the same vlan subnet.
Any suggestion or help is appreciated.
Thanks.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 19th, 2014 17:00
server_ping is pinging from a datamover, ping is from the control station. Are you using VLAN tagging or you have dedicated devices for 172.x network ?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 19th, 2014 17:00
i assume you use server_ping ? As a test did you try to set a host static route just to one vmkernel IP address ?
fl1
89 Posts
0
June 19th, 2014 17:00
Hmm. Server_ping returns both the Celerra and vmhost 172 back as alive but the "ping" command does not. Is there a difference between the two commands?
I've tried creating a route of destination 172.18.1.27 gateway 172.18.1.10 and subnet mask 255.255.255.255. Celerra creates the route fine but the vmhost still doesn't seem to be able to discover any targets on the Celerra. I tried manually adding the iSCSI server and target name of the Celerra to the iSCSI initiator on the vmhost but it throws an error. I tried the other way where I manually create a lun mask on the Celerra side pointing to the iSCSI iqn id of the vmhost iSCSI initiator, Celerra creates it fine but I don't think it actually checks. I do a rescan for new luns and targets on the vmhost but nothing.
It shouldn't be firewall even though a 172 network is non-routable and both Celerra and vmhost on the same vlan but then again the original IP network of the Celerra is 10. and still is. There's nothing special I should need to do other than create the new interface like some route refresh command or reboot of the data movers to take effect is there?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 19th, 2014 19:00
interfaces are not tagged on Celerra , you are using the same device for 10.21 and for 172.16 ?
fl1
89 Posts
0
June 19th, 2014 19:00
There are vlan tagging on the vmhost side but not on the Celerra side. My network guys told me I should be able to add any 172.16. address as long as they are on the same vlan there should be no problem. I just want to make sure it's not something on the Celerra end before I engage my network team.
Can you explain why I can ping from the datamover but not from the control station since both on the same 10.21 subnet? I would think I should be able to ping from both.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
June 19th, 2014 19:00
i've always used VLAN tagging but my networks are routed ..maybe if it's all layer 2 it does not matter. So if server_ping can ping ESXI host and ESXi host can ping 172.16 interface on datamover then you are in business.
fl1
89 Posts
0
June 19th, 2014 19:00
Ok then. I'll engage the network guys and have them check their logs or run some packet captures because it looks like something is not making through. Thanks for you input.
fl1
89 Posts
0
June 19th, 2014 19:00
Yes I am or at least trying to. Is this not possible on the Celerra side? Because I am able to do think on the vmhost side using the same vlan tag for both 10.21 and 172.16 and it works.