Just to follow up on this on the off chance somebody runs into this in the
future...a reload of the switch fixed the issue, and the traffic for the
L3 port stopped hitting vlan 1.
Andy
On Thu, 16 Aug 2012, Andy Dills wrote:
Thanks, I appreciate those suggestions. I verified both the SDM
I've got a customer with a weird situation.
They have a pretty straightforward setup, two 7200s fronting two cisco
3550-12s, distributing to a series of 48 port 3550s. It's a bit dated, but
works very well for their needs.
They have one special network attached to (only) one of the copper
In doing further investigation, looking at traffic graphs, I see that once
they moved the network to the other switch, all of a sudden vlan1
started seeing all of the traffic that was being routed to that network.
Typically, the only traffic the switches see on vlan1 is traffic actually
Hi Andy,
One idea is different SDM templates being used. The SDM template is
not showing up in running-config, and changing it requires a reload as
well. I would compare them with 'sh sdm prefer' command. You might be
running out of IPv4 routes, which causes rest of routes to be applied
in
Thanks, I appreciate those suggestions. I verified both the SDM and VTP
configs are identical.
Did you see my followup from earlier? I identified that for some reason
unknown to me, the traffic was hitting the vlan1 interface before exiting
via the L3 interface facing that network, which was
Hi Andy,
The only thing which comes to my mind when you mention vlan 1 is that
by default it is untagged. Therefore you might have some misconfig or
miscabling or not having routing enabled, something similar which
causes traffic from or to a routed port to arrive untagged which is
interpreted as
