Dell X1018& X1052 intervlan routing issue

Hi,

Are all of the VLANs assigned to the trunk ports? Page 51 https://downloads.dell.com/manuals/common/networking-x-series-ug_en-us.pdf

Can you private message me the service tag?

Yes!

I'm testing new config on devices and still having the same issue: no way to ping from Pcs on two different VLAN.

Routes on X1018

Routes on x1052

Does the ipv4 routes table show the routes?

Okay, in that case the best option would be to get a Prosupport warranty for software support.

I know this is a very old thread, but did the OP ever get this figured out  ?
I have a x1018 and I cannot get routes to work, or even stay persistent in the UI, which is odd because the routes are present in the cmd (which is deprecated)

I have a simple config, l2 + and and am trying to route from vlan 1 ->vlan 2 I've tried a bunch of route statements and nothing works

Here is where it is now -

vlan 1 -192.168.0.0 /24 (sw ip = 192.168.0.10 /24)
vlan 2 - 192.168.2.0/24 (sw ip = 192.168.2.250 /24)

ip route 192.168.0.0 /24 192.168.2.1 metric 10

Hi @ventura007,

Can you describe what was the issue with "even stay persistent in the UI"? You mean the configuration is not saved on the switch?

Could you check if the switch firmware are up to date? https://dell.to/3D3l4vZ;

In terms vLAN configuration, would this article help you? https://dell.to/3nZprUH

Is the switchport mode on the ports set to layer 3 mode? Page 149 https://dell.to/3xAsfe0

Joey-

re: persistent in the ui - When I add a static route to the UI it doesn't reflect in the UI after I click 'OK', the number of routes doesnt change and only "directly connected" owners appear and are counted. The only way I can only see the manually added static routes is in the command line, and becuase there are no commands I can actually use on the command line I cannot edit/ delete any unless I delete the vlan IP altogether! Is this expected behavior ?

F/W = 3.0.1.9

In any case nothing is working as I'd expect. I have an IP in vlan 1 and another in vlan 2. I can ping each with hosts in the respective vlans, but cannot get routing to work and again it seems very weird that if the command line is deprecated and that the UI doesn't reflect the static routes I am adding.so there is no way to edit or delete once they are added, only to view them in a 'show run' from command.

Am i missing something ?

TIA

set to layer 2 (D'oh)

I didnt know this existed, will need to do some reading! Thank you! 

I orginally added ip addresses to the vlans and thought I could route that way. not possible, eh ?

dumb question - I have a single switch and a very small vmware lab.I have a windows RRAS vm thats basically my vlan 2 gateway. How would I implement routing from vlan 1 <-> vlan 2? Use 2 physical ports on the switch  in l3 mode, one in each vlan ? I could use a push if you are feeling charitable! 

Hi @ventura007,

The link I provided on the previous reply would be able to help you out, it's the VLAN routing. 

Here's the user guide in case you need more details for VLAN configuration on page 147: https://dell.to/3p9ZjpC

Joey-

As previously mentioned vlan routing isnt working, the routes do not stay persistent in the UI so you cannot review, edit or delete. This must be a bug, if you have a x1018 please try it. I followed the documentation - create static IP addresses for each vLAN, these do show up in the static routing table as "directly connected", but when I add routes btw these addresses the UI accepts the add but the static route table doesnt show the routes and the routing doesnt work. I have given up and am using software routing in vmware to accomplish this. I wish there was a way to escalate to suppor, the OP had a similar problem, I wonder if he ever got it working

Hi @ventura007,

I did notice what you mentioned about VLAN routing isn't working. I was answering on where you were asking how you implement routing from VLAN 1 to VLAN2 versa, and that's where I wanted to let you know that's the only way to do it. 

If the configuration is not saving, perhaps either the switch is faulty or the firmware might be corrupted. Since you are using virtual VLAN routing as a workaround, probably it would be best since it's working for you.

You can try calling the support line to submit a case for the engineers to check.