08-08-2022 05:24 AM - last edited on 08-09-2022 10:22 PM by Translator
Hi,
this is my very simple topology in VIRL:
IOSvL2 (running IP routing) <-----trunk with VLANs allowed + Native VLAN----> IOSvL2 (NO IP routing) <----> 2 hosts on different VLANs
The interfaces connecting the hosts are standard issue access ports with the relevant VLANs. The hosts are what i get with VIRL, i.e. ubuntu/coreOS.
I can ping from the ubuntu host to the default gateway which is the SVI on the IOSvL2 switch in the same vlan, and same in opposite direction
I can ping SVI in VLAN X source VLAN Y within the IOSvL2 switch.
What I can't do is ping the host from a different VLAN, i.e. ping Ubuntu host in vlan X from source VLAN Y. Same issue in opposite direction, i.e. host to another host in another VLAN (and also to SVI in another VLAN).
For troubleshooting, I replaced the Ubuntu host with an IOSv router and configured an IP on an interface, just in case the issue was with the Linux config but got the exact same issue.
The issue is pointing to IOSvL2 switch running IP routing.
This is basic beginner CCNA lab and I really want to get this working so I can test some more advanced features before putting into business critical production network.
I found this thread with a very similar issue and tried the solution proposed there, and just like the fellow member this is also driving me mad. This really isn't a spectacular setup, am just trying to achieve inter-VLAN routing
https://community.cisco.com/t5/routing/virl-routing-issue/m-p/4064748#M332513
Is this some kind of bug with with the IOSvL2 image in VIRL, or have I just missed something really obvious? as I'm fresh out of ideas?
I have attached the running config of both the L2 and l3 switches
Happy to provide more details/configs if required
Solved! Go to Solution.
08-08-2022 10:24 AM - last edited on 08-09-2022 10:28 PM by Translator
Hi @hassan4917 ,
You do not have a default gateway configured on either host. If you did, you would see something like this:
default via 10.0.151.254 dev ens2
you need to add the GW using the following command:
sudo ip route add default via 10.0.51.254
sudo ip route add default via 10.0.151.254
Regards,
08-08-2022 06:36 AM - last edited on 08-09-2022 10:25 PM by Translator
On the both the switches ? have you created the VLANs ?(especially Layer2 switch)
can you post below information :
show vlan
show ip routing
show ip arp
show spann brief
08-08-2022 07:23 AM
I have attached the output for both switches for these.
08-08-2022 08:38 AM
Thank you for the information, now tell me what VLAN end device not working to what VLAN
what is the source VLAN and destinatio vlan you try to reach.
Please confirm, from L3 switch are you able to ping end device ?
08-08-2022 06:45 AM - last edited on 08-09-2022 10:26 PM by Translator
Hello
Just to confirm both hosts are attached to the same L2 switch , so did you manauly create the vlans on the both switchs and enable ip routing on the L3 switch?
conf t
vlan 2,32,40,51,151
exit
08-08-2022 07:30 AM
hi @paul driver
yes both hosts are attached to the same L2 switch and I did configure the VLANs manually.
the actual topology is bigger and am satisfied that the OSPF is working fine between all the router devices across the whole topology.
However, I need to have communication between the simulated end host devices working as the next phase of the simulation is to run ACLs and route-maps - but can't due to this issue.
08-08-2022 08:32 AM
Hi @hassan4917 ,
Did you configure a default gateway on the two hosts pointing at 10.0.51.254 and 10.0.151.254 respectively?
Regards,
08-08-2022 09:17 AM
08-08-2022 10:24 AM - last edited on 08-09-2022 10:28 PM by Translator
Hi @hassan4917 ,
You do not have a default gateway configured on either host. If you did, you would see something like this:
default via 10.0.151.254 dev ens2
you need to add the GW using the following command:
sudo ip route add default via 10.0.51.254
sudo ip route add default via 10.0.151.254
Regards,
08-09-2022 01:41 AM - last edited on 08-09-2022 10:29 PM by Translator
I see... so I used the command
sudo ip route add 10.0.151.254 dev ens2
to set the DG. Just entered your command and that worked straight away.
slightly embarrassed but at least have learned something.
Thanks @Harold Ritter
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide