Symptom:
Isolated ports on the same private VLAN are not isolated from each other. Data can switch between these ports.
The workaround on other 6500's in the site for the above listed bug was to migrate to 12.2(18)SXD5. This fixed the above bug along with the 'span' port limitations we faced in 12.1. However, in 12.2 a "24-port restriction" for certain modules was introduced that seems pretty wasteful from a port perspective:
24-Port Restriction:
In all releases, this “24-port restriction” applies to the WS-X6548-GE-TX and WS-X6148-GE-TX 10/100/1000 Mb Ethernet switching modules. Within groups of 24 ports (1–24, 25–48), do not configure ports as isolated ports or community VLAN ports when one port within the group of 24 ports is any of these:
– A trunk port
– A SPAN destination port
– A promiscuous private VLAN port
Based on the above in 12.2, we have to reserve a 24-port range for promiscuous ports and regular vlan ports. This seems like a waste of ports if the majority of your hosts are p-vlan host ports?
So, the question is - Is there a version where we can get the best of both worlds? In 12.1 there was a 12-port restriction which seems much more reasonable, but not for our WS-X6148-GE-TX module.
Any help would be appreciated.
