Trying to connect a Catalyst 3560 to a Foundry SX1600.
If I put port Fa 0/1 in VLAN 10 (Cisco) and unttag eth 1/1 to VLAN 101 (Foundry we get VLAN 101 blocked with inconsistent port type errors on the 3560. This setup puts both ports as access ports.
We got around that blocking issue by trunking Fa 0/1 with a trunk native VLAN 10 and allowed VLANs of 1 & 10. On the Foundry side eth 1/1 is tagged in VLAN 101. STP is not blocking anything.
The problem is that we can not ping the VLAN 10 interfaces on the 3560.
this is clearly a mismatch of native vlan in cisco terms. the cisco device is expecting untagged packets to be packets destined to vlan 10 and sending out untagged packets that came from vlan 10 and when the Foundry rx'd this untagged packet it will not send those packet out to vlan 10 thus vlan 10 is not working. If you are only interested in making this work, make the natvie vlan in 3550 to be anything else otehr than vlan 10, preferrably a non-working vlan or dummy vlan, for example vlan 99. Try it let me know if you are able to ping in vlan 10 between the foundry and the cisco.
In that case, cisco switch won't tag packet in vlan 10 since it's native vlan. If Foundry does tag packet in vlan 10, it could be a issue. Could you please try this:
1. make sure both sides permit the same vlan set.
2. Change the native vlan on cisco side to the vlan other than vlan 10 so that Cisco will tag the packet in vlan10.