If you look at f0/11, you will probably see a line that states "switchport trunk allowed vlan 10-15,20". If you want all vlans, allowed on the trunk, you can remove that line.
Port f0/15 is connected to a host that cannot trunk. The port's default is dynamic desirable, but the other side cannot trunk, so the port ends up in a non-trunking state. It's only allowing vlan 12 over that port. That could be because this port has a configuration of "switchport access vlan 12", but it's mode is dynamic desirable. If that's the case and dynamic fails, the port is set to an access port in the vlan specified.
To help diagnosing I phisically connected an host to a switch2 port configured in vlan 12 and it works; it can ping another host on vlan 12 connected to switch1. I think it confirms that trunking is working (even if a "sh int fa0/41 trunk" executed on switch1 get a non-trunking status, who knows why).
Actually, sorry not being probably clear, the problem is to ping the new host connected to vlan 12 from another vlan.
And I suspect that the problem is in the configuration of the trunking port that connect switch to firewall; in fact the very first host (configured from previous guy) on vlan 12 is pingable from other vlans ... the new one is not.
Also, I examined the fw configuration related to that vlan but I can't find any access-list that seems to restrict hosts.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...