Dear Lazuardi: The following may be the case you have met: The Q-in-Q customers are connected to FESX. You have to configure the following command in FESX and MLX. For FESX jumbo aggregated-vlan tag-type 9100 ethernet 13 to 24(the ports to connect Q-in-Q customers) vlan 100 tag e 1 (Uplink port to MLX) untag e 13(the ports to connect Q-in-Q customers) For MLX default-max-frame-size 9216 Notice: 1. Jumbo and "default-max-frame-size 9216" are to make sure FESX and MLX can support frame up to 9K bytes. The FESX and MLX need to reload to enable this feature. 2. Aggregated-vlan is to make FESX to support frame upto 1536bytes. 3. For fesx, Tag-type 9100 will change all the 12 ports in the same port group(Port 1 to 12, Port 13 to 24, Port 25 to 36, Port 37 to 48) to tag-type 9100. You can't change only 1 port to tag-type 9100. 4. You can't put the non Q-in-Q cutomer(Normal 8100 tagging or 8100 untag) in the Q-in-Q port group(9100 untag). 5. The vlan 100 is the outter vlan id and the Q-in-Q port has to be untagged. Vlan 100 is the example, you may choose any vlan id as the outter vlan id. 6. The Q-in-Q port will ignore customer (inner) vlan id since the FESX will look customer vlan is as payload'This is because that the Q-in-Q port is tag-type 9100 untagged port.. 7. All the Q-in-Q customer's original valn priorities will be substituted by the priority of outter vlan id. This means that customer will loss the QoS assignment if cutomer have assign different priority to different vlan id. 8. The Q-in-Q customer will need to use 8100 tag-type tagging port to connect FESX 9100 tag-type untagged port. You have to change to other tag-type if Q-in-Q customer use 9100 tag-type tagging port to connect FESX. Regards, Spenser.
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
