10-02-2020 01:39 PM
Hello,
I have an issue getting inter-vlan routing working. Here's the setup:
Switch 9318 - IOS 9.2(3) - License ACI Essentials
Vlan4
192.168.1.1
no shut
Vlan5
no shut
192.168.2.1
Ethernet 1/48
Trunk to 9200
Switch 9200 - IOS 16.12.02 - License Network/DNA Essentials
Vlan 5
192.168.2.2
no shut
Ethernet 1/0/24
Trunk to 9318
I can see each switch from the other via CDP, I can pint 191.168.1.1 and 192.168.2.1 from both switches, but that's it. I have a workstation on each side (192.168.1.52 & 192.168.2.23) that cannot ping each other. I have confirmed all interfaces are up/up, assigned to the appropriate VLANs, trunking works, etc.
I've checked online and I can't issue the "ip routing" command on the 9318, I'm concerned this is due to an IOS/licensing issue.
Any help is greatly appreciated.
Solved! Go to Solution.
10-06-2020 11:43 AM
I am not sure what is the issue about 1.52. But most of it does seem to be working. If you are satisfied and want to call it solved then we can consider it finished for discussion.
10-02-2020 01:48 PM
on nexus - can you post-show features or enable the feature
config t
feature interface-vlan
still not working share the config with above show feature output
10-05-2020 08:39 AM
Hello,
I executed the command:
feature interface-vlan
There was an "ip" option but it only allowed the following:
download-on-convergence event-history multicast
There was no "ip routing" option avaiable.
10-02-2020 01:58 PM
Thanks,
I had to exit our facility, I'll post it on Monday.
10-02-2020 02:16 PM
If you can not implement the command ip routing that is concerning. Perhaps the output of these commands on 9318 might shed some light:
show ip protocol
show ip route
Can each of the workstations ping the IP of the vlan interface of its vlan on the 9318?
Can each of the workstations ping the IP of the other vlan interface on the 9318?
10-02-2020 02:21 PM
Thank you,
I'll have the results for you on Monday, our facility closed for the weekend.
10-05-2020 09:26 AM
Sir,
for show ip route
192.168.1.0/24, attached via 192.168.1.1, vlan 4, direct 192.168.1.1/32, attached via 192.168.1.1, vlan 4, local 192.168.2.0/24, attached via 192.168.2.1, vlan 5, direct 192.168.2.1/32, attached via 192.168.2.1, vlan 5, local
I decided to swap workstations (new IP - 192.168.2.25) since I was growing concerned something was wrong. I can now do the following:
192.168.1.52 ping 192.168.1.1 - success 192.168.1.52 ping 192.168.2.1 - success
192.168.1.52 ping 192.168.2.2 - fail
192.168.1.52 ping 192.168.2.25 - success
192.168.2.25 ping 192.168.2.1 - success
192.168.2.25 ping 192.168.2.2 - success
192.168.2.25 ping 192.168.1.1 - success
192.168.2.25 ping 192.168.1.52 - success
Not sure why the 1.52 workstation can't ping the 2.2 interface on the other switch.
I think this is solved?
10-06-2020 11:43 AM
I am not sure what is the issue about 1.52. But most of it does seem to be working. If you are satisfied and want to call it solved then we can consider it finished for discussion.
10-06-2020 11:53 AM
Hello,
does your 9200 switch have:
ip default-gateway 192.168.2.1
configured ?
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