Meraki MS 250 : Inter-Vlan Routing issue

Solved
Pavan_Pawar
Getting noticed

Meraki MS 250 : Inter-Vlan Routing issue

Hello Experts,

 

I have created two L3 VLANs and each VLAN has one test PC connected, PC1 is not able to reach PC2.

below is the setup:

 

{
"interfaceId": "3705899543372500746",
"name": "NAME_VLAN_101",
"subnet": "192.168.101.0/24",
"interfaceIp": "192.168.101.1",
"multicastRouting": "disabled",
"vlanId": 101,
"defaultGateway": "192.168.101.254",
"ospfSettings": {
"area": "ospfDisabled"
}
},
{
"interfaceId": "3705899543372500747",
"name": "NAME_VLAN_201",
"subnet": "192.168.201.0/24",
"interfaceIp": "192.168.201.1",
"multicastRouting": "disabled",
"vlanId": 201,
"ospfSettings": {
"area": "ospfDisabled"
}
}
]

 

"portId": "1",
"name": "FIXIA-P5-37",
"tags": [],
"enabled": true,
"poeEnabled": true,
"type": "access",
"vlan": 101,
 
"portId": "3",
"name": "FIXIA-P5-39",
"tags": [],
"enabled": true,
"poeEnabled": true,
"type": "access",
"vlan": 201,
 
 
routing table : 
[
{
"staticRouteId": "3705899543372501715",
"name": "Default route",
"subnet": "0.0.0.0/0",
"nextHopIp": "192.168.101.254",
"advertiseViaOspfEnabled": false,
"preferOverOspfRoutesEnabled": false
}
]

 

Source -

PC1(VLAN101) - 192.168.101.10
Destination -

PC2(VLAN201) - 192.168.201.10

 

PC1 cannot ping PC2, In captures(taken on the dashboard for the switch) I can see the switch is sending an ARP request and receiving an ARP reply from PC2 but the ping fails. 

On the dashboard, the switch ARP table keeps loading and does not show anything.

 

Note - The default gateway is not reachable as this is local switch routing.

 

Do I need to toggle any settings for inter-vlan routing?

 

Regards,

Pavan

1 Accepted Solution
Pavan_Pawar
Getting noticed

The issue is resolved with the below config change :

 

"portId""1",
"name""FIXIA-P5-37",
"tags": [],
"enabled"true,
"poeEnabled"true,
"type": "trunk",
"vlan": 101,
"allowed vlans" 101
 
 
"portId""3",
"name""FIXIA-P5-39",
"tags": [],
"enabled"true,
"poeEnabled"true,
"type": "trunk",
"vlan": 201,
"allowed vlans" 201
 

 

 

 

View solution in original post

14 Replies 14
alemabrahao
Kind of a big deal
Kind of a big deal

Are they Windows machines? Have you tried disabling the Windows firewall?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Pavan_Pawar
Getting noticed

this are the Linux machine and nothing sort of blocking on this machines

alemabrahao
Kind of a big deal
Kind of a big deal

Maybe the Iptables? Just make sure that nothing is being blocked. As they are directly connected networks, routing should be ok.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
RaphaelL
Kind of a big deal
Kind of a big deal

Note - The default gateway is not reachable as this is local switch routing.

 

Do I need to toggle any settings for inter-vlan routing?

 

What ?

Pavan_Pawar
Getting noticed

Do I need to make any setting changes to enable inter-vlan routing?

alemabrahao
Kind of a big deal
Kind of a big deal

No.

 

Do you have any ACL configured?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
RaphaelL
Kind of a big deal
Kind of a big deal

Can PC1 ping his gateway ? 

Can PC2 ping his gateway ?

Pavan_Pawar
Getting noticed

yes

RaphaelL
Kind of a big deal
Kind of a big deal

When doing ifconfig on both PC1 and PC2 , it shows the IP , mask and default gateway ?

cmr
Kind of a big deal
Kind of a big deal

If you put both ports in vlan 101 and change the second PC to IP 192.168.101.11 can they ping each other?

 

If so put both PCs on VLAN 201 and 102.168.201.x IP addresses and try the same, does that also work?

If my answer solves your problem please click Accept as Solution so others can benefit from it.
GIdenJoe
Kind of a big deal
Kind of a big deal

I noticed the default route for your interface is ALSO on VLAN 101 192.168.101.254.  Are your endpoints using 192.168.101.1 or .254 as their default gateway?

 

It is bad practice to use the same subnet for clients as for routing on your switch to the next hop towards the internet because this causes asymmetric routing and possible issues with DHCP relay.

Pavan_Pawar
Getting noticed

The issue is resolved with the below config change :

 

"portId""1",
"name""FIXIA-P5-37",
"tags": [],
"enabled"true,
"poeEnabled"true,
"type": "trunk",
"vlan": 101,
"allowed vlans" 101
 
 
"portId""3",
"name""FIXIA-P5-39",
"tags": [],
"enabled"true,
"poeEnabled"true,
"type": "trunk",
"vlan": 201,
"allowed vlans" 201
 

 

 

 

JRichardson
Just browsing

What tool is being used to make these configuration changes? It looks like traditional Cisco CLI albeit different syntax, etc. I am having a similar issue in my environment but only configure through the GUI. Any advice is appreciated. 

Pavan_Pawar
Getting noticed

the output you see is taken from the API response in the Postman application.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels