Circuit-ID Tunnels—Rules and Notes
Keep in mind the following rules and notes when working with Circuit-ID tunnel encapsulation and decapsulation:
| • | A maximum of 512 circuit-IDs are supported within a cluster for encapsulation and decapsulation. |
| • | If a network port receives a double-tagged packet that is encapsulated with a circuit-ID, the five tuple hashing will not work only in the second cluster, that is the cluster in the decapsulation side over stack GigaStream or tool gigastream. Hence, traffic cannot be filtered using the IP/L4 parameters. After decapsulation, flow mapping filters the traffic based on circuit-ID. |
| • | It is not supported for inline scenarios. |
Keep in mind the following rules and notes when working with Circuit-ID tunnel encapsulation:
| • | Circuit-ID tunnel encapsulation is not supported on Pass All maps. |
| • | Port filter configured on circuit port for VLAN pass/drop will try to match the encap circuit-id instead of packet outer VLAN. |
Keep in mind the following rules and notes when working with Circuit-ID tunnel decapsulation:
| • | A maximum of 512 circuit-ID tunnels can be created for decapsulation. |
| • | Circuit-ID tunnel decapsulation is not supported on Pass All and Shared Collector maps. |
| • | A circuit-ID must be paired with a circuit port, only in one circuit-ID tunnel. |
Document INFORMATION 
