Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello everyone,I have an issue with an 4255 IPS using an inline VLAN pair. Here's the rough sketch of the topology:SW1port 1 access vlan 10 - PC (10.20.30.2/24)port 48 trunk to SW2 - all vlans allowed and forwardingSW2port 48 trunk to SW1 - all vlans...
I've seen the tutorials where the devices are connected to the same switch, but what about adding another switch into the mix.Diagram:http://imgur.com/idZuVdLIs there any extra configuration required in order for PC to ping its default gateway (SVI o...
Yes the topology is PC-----ACCESSPORT----SW1----TRUNK----SW2 PC is on SW1 - vlan 10SVI/Default gateway for PC is on SW2.- vlan 20IPS is on SW2 - trunk vlans allowed 10,20I thought since the VLANs must be bridged in order for PC to reach SVI, this wou...
Unfortunately no, the MAP and the RAP were set as infrastructure only and did not serve wireless clients. I don't see how this would cause much of a performance hit since the backhaul link is over the 5Ghz radio.
It is possible that when I tried it, the new setting didnt stick. I've gotten the warning, went back and it was still normal. I didn't get the warning when changing e0 on the MAP though. I believe cisco documentation says the backhaul of the RAP wil...
Justin - thanks for the notes. I also ran into the PVID mismatches on the trunks, so it does seem like a glitch in the mesh code or a combination of a certain switch IOS and the mesh bridges.Currently I have both bridges up and trunking about 5 VLAN...
