topic Re: Vlan comunications in ExtremeSwitching (EXOS/Switch Engine)

Vlan comunications

Grud — Tue, 15 Dec 2020 00:39:27 GMT

Good afternoon everyone! I am new to working with Extreme equipment and I have a problem that I cannot identify, I create vlans following this guide (https://extremeportal.force.com/ExtrArticleDetail?an=000083610) and my vlans do not communicate with each other, I couldn't find the problem and in most places I saw teaching how to create they were similar to this example in the guide. What can this problem be about the lack of communication between vlans? I'm using Extreme X440-48t to do this configuration with the vlans, I don't have any fixed address range that I have to follow, I'm just trying to solve this problem. Thanks in advance for your attention!

Re: Vlan comunications

CThompsonEXOS — Tue, 15 Dec 2020 00:56:38 GMT

Can you provide the output of “show vlan”?

Thanks,

Chris Thompson

Re: Vlan comunications

Grud — Tue, 15 Dec 2020 01:03:52 GMT

Of course! Following is an image with "show vlan" and another with the output of "show config", but only the part of the vlan.

Re: Vlan comunications

StephanH — Tue, 15 Dec 2020 03:45:23 GMT

Hello Grud,

how do you test the routing between the vlans?

With two computer in different vlans and ping?

If yes, what is the adapter config (ip, mask, gateway)?

Can you ping the gateway of the pcs?

Can you provid an "sh ip route" frim the x440?

Re: Vlan comunications

Grud — Tue, 15 Dec 2020 10:03:01 GMT

well, the routing between the computers I test with the ping command, and the two machines get a ping response from their respective gateways, each machine is on a different vlan, even this part is ok, however, when I will ping one machine on the other does not work. Follow the exit of the "show iproute". Thanks a lot for the help.

Re: Vlan comunications

StephanH — Tue, 15 Dec 2020 13:51:11 GMT

Hmm,

can you do a ping on the switch “ping 172.16.10.1 from 192.168.100.1” and “ping 192.168.100.1 from 172.16.10.1”, please.

Re: Vlan comunications

StephanH — Tue, 15 Dec 2020 14:17:46 GMT

In addition you can ping the gateway from the other vlan from the PC = ping to 172.16.10.1 (wolf) from pc in the vlan 192.168.100.0/24 (fox)

Re: Vlan comunications

Grud — Tue, 15 Dec 2020 19:20:43 GMT

Here are some images showing the ping made by the switch, an image showing a machine on the vlan fox pinging the entire network and another image showing a machine on the vlan wolf pinging the entire network. Thank you!

Re: Vlan comunications

StephanH — Tue, 15 Dec 2020 20:47:19 GMT

Pinging on the switch without a “from” didn’t show if routing is working. Can you do the ping with “from” as descripted.

Re: Vlan comunications

Grud — Tue, 15 Dec 2020 21:24:04 GMT

I didn't know he had this, cool! Follow what you asked me to do. Thank you!

Re: Vlan comunications

StephanH — Tue, 15 Dec 2020 21:31:39 GMT

Hello,

as far as I can see you pinged not the interface of the x440. In the first pictures the interface ip is 172.16.10.1 (vlan wolf) right?

.20 is you PC.

What I want to see is if the problem exists directly on your switch or not.

Re: Vlan comunications

Stefan_K_ — Wed, 16 Dec 2020 01:29:56 GMT

Can you also provide the output of

ifconfig

route

of your linux-machines?

Re: Vlan comunications

Grud — Sat, 19 Dec 2020 00:22:57 GMT

Sorry for the delay in responding. After mentioning that ping is used with origin and destination by the switch, it is used to see if the internal routing is ok, I stopped a bit and redid the network configuration. I deleted everything, redid the vlans, set the IPs on the machines, gateways, dns and etc. And probably the problem was on the machines rather than on the switches, but I only got to see it after the explanations above. So the initial guide I saw is right, but we just needed to check the gateway and the ip of the machines on the networks. Thank you all!

Re: Vlan comunications

StephanH — Sat, 19 Dec 2020 01:37:12 GMT

Hello,

thank for the feedback.