From: Bob Sinclair (bsin@cox.net)
Date: Sat May 15 2004 - 08:36:13 GMT-3
Dan,
The vlan assigned to port f0/1 becomes the metro tag. Remember, port f0/1
is configured as an access port. This seems a strange, considering that the
customer's connected port is a dot1q trunk port. Each customer is assigned
to a different ISP vlan.
You need to make sure that none of the customer vlans are also native,
untagged vlans in the ISP network, otherwise traffic can get misdirected.
Best practice to make sure all vlans on ISP trunks are tagged using the
global command: vlan dot1q tag native. Note that the tunnel changes the
system mtu to 1504. Yo may want to return it to 1500 when done.
Here is a link to the topic in the docs:
HTH,
Bob Sinclair
CCIE #10427, CISSP, MCSE
www.netmasterclass.net
----- Original Message -----
From: "Dan" <dans@danbsd.a.la>
To: <ccielab@groupstudy.com>
Sent: Saturday, May 15, 2004 4:39 AM
Subject: Dot1Q Tunnel on 3550
> Hello,
>
> I searched the archive and found no answer.
>
> Could you point me to the relevant doc?
> my question is: When configuring dot1q tunnel over f0/1, which is the port
> connected to the "costumer" trunk, all I have to do is:
>
>
> interface fastEthernet0/1
> switchport mode dot1q-tunnel
>
>
> 1. How the switch knows what metro tag to apply to the taged frames
> comming from the "costumer"?
> 2. Do i need to configure anthing else on diffrent ports on the smae
> switch or other "core" switches?
>
>
> Thanks,
> Dan
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:12 GMT-3