From: Radu Pavaloiu (Radu.Pavaloiu@connex.ro)
Date: Wed Feb 16 2005 - 11:30:36 GMT-3
I've tested. You can test during the lab using routers with trunks
configured on eth interfaces.
Kindest Regards,
I die. I fracture into thousands of fragments of flushed embarrassment.
My body parts fly, connectionless, over a badly constructed spanning
tree that isn't quite loop free.
I fall screaming into 127.0.0.1.
Radu
CCNP, CCDP
#2658
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Wednesday, February 16, 2005 4:09 PM
To: Patrick Lynchehaun
Cc: Group Study
Subject: Re: dot1q tunneling
Thanks Patrick.
I was hoping that wasn't the case since that means there's not a good
way of verifying the config during the lab.
Have you tested this and know for sure this is true?
Tim
----- Original Message -----
From: "Patrick Lynchehaun" <plynch@servecentric.com>
To: "ccie2be" <ccie2be@nyc.rr.com>; "Group Study"
<ccielab@groupstudy.com>
Sent: Wednesday, February 16, 2005 9:04 AM
Subject: RE: dot1q tunneling
ccie2be,
The port has to be connected.
Patrick.
-----Original Message-----
From: ccie2be [mailto:ccie2be@nyc.rr.com]
Sent: 16 February 2005 13:29
To: Group Study
Subject: dot1q tunneling
Hi guys,
I just configured dot1q tunneling but the switch doesn't acknowledge
this.
sw2#r int fa0/20
Building configuration...
Current configuration : 93 bytes
!
interface FastEthernet0/20
switchport access vlan 1000
switchport mode dot1q-tunnel
end
sw2#sh vlan dot1q tag nat
dot1q native vlan tagging is enabled
sw2#sh dot1q int fa0/20
dot1q-tunnel mode LAN Port(s)
-----------------------------
sw2#
As you can see from the output, no ports are shown as dot1q-tunnel mode
ports. Why is this?
Do I need to reload the switch? Does this port have to be actually
connected to another switch?
Any insight would be greatly appreciated.
TIA, Tim
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:21 GMT-3