From: Bob Sinclair (bsin@cox.net)
Date: Sun Mar 27 2005 - 00:13:56 GMT-3
Null,
As a base, starting point, I would suggest putting all IP addressing on
subinterfaces. On some platforms you can get IP to work on the phsical
interface, but it goes out untagged (on the native vlan).
Note that the default native vlan on catalyst trunks is VLAN 1. On Int E0/0.1
you are tagging VLAN 1. So if the switch has the default native vlan you will
not be able to communicate.
Suggestion: Just as a proof of concept, creat two subinterfaces, one on VLAN
2 and one on VLAN 3. Create these vlans on the switch, and create an Int VLAN
for each. As below:
3640:
int e0/0.2
encap dot1q 2
ip address 2.2.2.2 255.255.255.0
int e0/0.3
encap dot1q 3
ip address 3.3.3.3 255.255.255.0
On Cat:
vlan 2
int vlan 2
ip address 2.2.2.1 255.255.255.0
vlan 3
int vlan 3
ip address 3.3.3.1 255.255.255.0
default int f0/1
int f0/1
sw trunk encap dot1q
sw mode trunk
sw nonegotiate
HTH,
Bob Sinclair
CCIE #10427, CCSI 30427, CISSP
www.netmasterclass.net
----- Original Message -----
From: Null
To: ccielab@groupstudy.com
Sent: Saturday, March 26, 2005 9:59 PM
Subject: 802.1Q trunking on Ethernet ports of Modern IOS images
I was under the impression that newer IOS images could do dot1q trunking on
regular 10 base Ethernet interfaces ? I have a bunch of 3640's running
the
following image : System image file is "flash:c3640-jk9o3s-mz.123-9.bin"
And when I use the following between an Ethernet interface on the 3640 and
a
newer image EMI 3550 the trunk comes up but there is no connectivity ???
3640:
Interface Ether 0/0
Ip address 1.1.1.1 255.255.255.0
Interface Ether 0/0.1
Encap dot1 1
Ip add 2.2.2.2 255.255.255.0
3550 Switch:
Interface f0/1
Switch trunk encap dot1
Switch mode trunk
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:52 GMT-3