09-26-2011 08:52 PM - edited 03-07-2019 02:27 AM
we are unable to get any user traffic between sub nets on the same physical interface. The rtr and sw have a trunk that passes all VLANs and that seems to work. The rtr and switch can see every device. We also can’t communicate between any two sub nets that are on the same physical interface. no ACL to block traffic in either direction
Even a device on the same subnet can’t ping or see other device on the subnet. However everyone can see the rtr and sw and vice versa.
the trunk i/f have this to ensure traffic can flow in both directions
no ip split-horizon
Theses two files are from our unclass tested. We use this environment to test out solutions before deployment. ERR is the rtr and ERS is the switch. The link between this rtr and the others is done right now, but that does not affect the current issue
Any tips or recommendations would be most helpful
09-26-2011 11:09 PM
are the devices taking the right ip addressing via DHCP service from the router ?
i can see you have multiple subnets while only one
ip dhcp pool f2f-SB-VoIP
import all
network 20.1.100.128 255.255.255.248
default-router 20.1.100.129
option 150 ip 20.1.100.252
lease 0 4
and each pool for each subnet has to have the default gateway as the router IP of that subnet/subinterface
by the way you do not need the helper address as the request will go direct over the trunk to the relevalnt subInterface of each Vlan
and this is got nothing to do with Siplit Horizon here
Hope this Help
09-27-2011 04:05 AM
hi
i have limited dhcp pools as most systems are on fixed IP, vs. DHCP.
The fixed ones use the correct mask gateway etc. I will add the help for the dhcp pool though.
Any idea why the fixed users have issues, but ping etc from eother rtr or switch can get frorm /to any vlan?
09-28-2011 02:37 PM
I have removed these from the rtr on all I/F and van
No ip unreachable
As well as
No redirect
Also, I remove the ip route on the switch
Same problem (;
My vlan pc can ping 192.168.0.1 and all other i/f but not 192.168.0.192
My router and switch can ping 192.168.0.1 and 192.168.0.192
When I run tracert on the pC, I only get one from 20.10.100.1after that reply just * * *
Let me know if you know anything else that I can try
09-30-2011 06:50 AM
Hello
I think i found the glitch
i removed
no ip proxy arp
on the main trunk I/F as well as the subnet I/F. now it reads
ip proxy arp
Voila, i can now do inter vlan trunking on the same physical IF
cheers all, any comment on why that now works
i have no proxy server
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