From: Ron Trunk (rtrunk@xxxxxxxxxxxxx)
Date: Tue May 25 1999 - 14:35:32 GMT-3
I reloaded the router, but took out fa0/0.1 and left the others.
(note: I've also changed the ip address of the sub ints since my original
message)
r3#sh vlan
Virtual LAN ID: 1 (Inter Switch Link Encapsulation)
vLAN Trunk Interface: FastEthernet0/0.1
Protocols Configured: Address: Received:
Transmitted:
IP 192.168.252.2 0
0
Virtual LAN ID: 2 (Inter Switch Link Encapsulation)
vLAN Trunk Interface: FastEthernet0/0.2
Protocols Configured: Address: Received:
Transmitted:
IP 192.168.153.2 0
7
Virtual LAN ID: 3 (Inter Switch Link Encapsulation)
vLAN Trunk Interface: FastEthernet0/0.3
Protocols Configured: Address: Received:
Transmitted:
IP 192.168.154.2 0
7
Virtual LAN ID: 4 (Inter Switch Link Encapsulation)
vLAN Trunk Interface: FastEthernet0/0.4
Protocols Configured: Address: Received:
Transmitted:
IP 192.168.151.2 0
8
Next I turn on vlan debugging:
r3#debug vlan packet
Virtual LAN packet information debugging is on
r3#
00:02:48: vLAN: ISL packet received bearing colour ID 1 on FastEthernet0/0
which has no subinterface configured to route or bridge ID 1.
00:02:48: vLAN: Received ISL encapsulated UNKNOWN packet bearing colour ID 2
on interface FastEthernet0/0.2 which is not configured to
route or bridge this packet type.
00:02:49: vLAN: Received ISL encapsulated UNKNOWN packet bearing colour ID 3
on interface FastEthernet0/0.3 which is not configured to
route or bridge this packet type.
00:02:49: vLAN: Received ISL encapsulated UNKNOWN packet bearing colour ID 4
on interface FastEthernet0/0.4 which is not configured to
route or bridge this packet type.
This seems to me to say the router is receiving the trunking info, but is
not sure what to do with it.
r3#debug ip packet
IP packet debugging is on
r3#ping 192.168.153.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.153.1, timeout is 2 seconds:
00:01:56: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, sending
00:01:56: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, encapsulation failed.
00:01:58: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, sending
00:01:58: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, encapsulation failed.
00:02:00: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, sending
00:02:00: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, encapsulation failed.
00:02:02: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, sending
00:02:02: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, encapsulation f.ailed
00:02:04: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, sending
00:02:04: IP: s=192.168.153.2 (local), d=192.168.153.1 (FastEthernet0/0.2),
len 100, encapsulation failed.
Success rate is 0 percent (0/5)
Since the encap is failing, that implies the router can't map the ip address
to a port. Does this mean the router doesn't know to use ethernet?
Other than this obvious info, I'm stumped!
-----Original Message-----
From: Scott Morris <SMorris@tele-tech.com>
To: 'Ron Trunk' <rtrunk@xatlantic.com>
Date: Tuesday, May 25, 1999 1:14 PM
Subject: RE: vlan routing
>Hmm.... If you take out everything but fa0/0.1, reload the router, see if
>you still get those messages (ie. try it one vlan at a time). Otherwise
>perhaps 'debug vlan' on the router and see what information you get. I'm
>also assuming that your connection speed really is 100mb. I just remember
>hearing something that a trunk required that speed, but don't have much
>additional info beyond that...
>
>Like I said. The router config looks good. When I set it up once before
>(only once, unfortunately), it worked like that, and really wasn't a
>difficult thing. That's why I'm not too sure on troubleshooting steps.
>Another thing you may try is limiting the trunk port to only trunk vlan 1
in
>the beginning, then add vlans from there as things work. *shrug*
>
>Scott
>smorris@tele-tech.com
>
>-----Original Message-----
>From: Ron Trunk [mailto:rtrunk@xatlantic.com]
>Sent: Tuesday, May 25, 1999 12:53 PM
>To: Scott Morris
>Subject: Re: vlan routing
>
>
>Scott,
>
>The cat5 is trunking:
>
>kittycat> (enable) sh trunk
>Port Mode Status
>-------- ----------- ------------
> 1/1 on trunking
>
>Port Vlans allowed on trunk
>-------- -----------------------------------------------------------------
-
>---
> 1/1 1-1000
>
>Port Vlans allowed and active in management domain
>-------- -----------------------------------------------------------------
-
>---
> 1/1 1-4
>
>Port Vlans in spanning tree forwarding state and not pruned
>-------- -----------------------------------------------------------------
-
>---
> 1/1 1-4
>kittycat> (enable)
>
>I think the problem is on the router. When I try to ping a host on one of
>the vlans, I get a encapsulation failed error.
>
>
>-----Original Message-----
>From: Scott Morris <SMorris@tele-tech.com>
>To: 'Ron Trunk' <rtrunk@xatlantic.com>
>Date: Tuesday, May 25, 1999 12:35 PM
>Subject: RE: vlan routing
>
>
>>I'm not sure if your cat is trunking as it should... Here's what I've
>>pulled from notes, I haven't configured one in quite a while, so couldn't
>>tell you much other than notes at the moment. ;) Your router config looks
>>good however...
>>
>>On Catalyst:
>>
>>The ports on a Supervisor module are trunk ports. An ISL connection is a
>>trunk connection.
>>
>>Plug router's Fast Ethernet port into Trunk port on Catalyst.
>>
>>Set trunk (card/port) on [vlans=(vlan number range)] All VLANs on by
>>default
>>Clear trunk (card/port) (vlan number range) Clears vlans
>>out of range above
>>Set port duplex (card/port) full Set port to
>>full duplex operation
>>Set port enable (card/port) Enables
>>trunking port
>>
>>On Router:
>>
>>Sub interface numbers must match vlan numbers being configured. Each vlan
>>must have a sub interface.
>>
>>Interface f#/#.vlan Interface fa3/0.1 is module 3, port
>>0, vlan 1
>>Encapsulation isl Sets trunk configuration
>>Ip address (ip#) (mask) IP must be in subnet range of that
>>vlan
>>
>>Repeat this procedure for each vlan where routing is necessary as
>configured
>>per that trunking port.
>>
>>Note: If sub-interface/vlan is removed, the router must be reloaded, or
>>interfaces will remain in a "deleted" state within the interface database.
>>
>>Scott Morris MCSE, CNE(3.x), CCDA, CCIE #4713
>>smorris@tele-tech.com
>>
>>
>>-----Original Message-----
>>From: Ron Trunk [mailto:rtrunk@xatlantic.com]
>>Sent: Tuesday, May 25, 1999 12:07 PM
>>To: ccielab@groupstudy.com
>>Subject: vlan routing
>>
>>
>>I know I've overlooked someting simple (I hope!), but I'm stuck on this
>>problem:
>>
>>I'm routing between vlans using a fastethernet interface and ISL
>>encapsulation. I've set up my vlans on my switch, set up trunking on port
>>1/1 (connected to my router), and set the router's configuration so that
>>each vlan is on a subinterface.
>>
>>But I'm getting this error:
>>
>>02:03:12: vLAN: Received ISL encapsulated UNKNOWN packet bearing colour ID
>1
>> on interface FastEthernet0/0.1 which is not configured to
>> route or bridge this packet type.
>>
>>Here is the router config:
>>
>>!
>>interface FastEthernet0/0
>>no ip address
>>no ip directed-broadcast
>>!
>>interface FastEthernet0/0.1
>>encapsulation isl 1
>>ip address 192.168.252.2 255.255.255.0
>>no ip redirects
>>no ip directed-broadcast
>>!
>>interface FastEthernet0/0.2
>>encapsulation isl 2
>>ip address 192.168.253.2 255.255.255.0
>>no ip redirects
>>no ip directed-broadcast
>>!
>>interface FastEthernet0/0.3
>>encapsulation isl 3
>>ip address 192.168.254.2 255.255.255.0
>>no ip redirects
>>no ip directed-broadcast
>>!
>>interface FastEthernet0/0.4
>>encapsulation isl 4
>>ip address 192.168.251.2 255.255.255.0
>>no ip redirects
>>no ip directed-broadcast
>>!
>>
>>Here is the switch config
>>
>>!
>>#vtp
>>set vtp mode transparent
>>set vtp pruneeligible 2-1000
>>set vlan 1 name default type ethernet mtu 1500 said 100001 state active
>>set vlan 2 name vlan2 type ethernet mtu 1500 said 100002 state active
>>set vlan 3 name vlan3 type ethernet mtu 1500 said 100003 state active
>>set vlan 4 name vlan4 type ethernet mtu 1500 said 100004 state active
>>set vlan 1002 name fddi-default type fddi mtu 1500 said 101002 state
active
>>parent 0 ring 0
>>set vlan 1003 name token-ring-default type token_ring mtu 1500 said 101003
>>state active parent 0 ring 0
>>set vlan 1004 name fddinet-default type fddi_net mtu 1500 said 101004
state
>>active bridge 0 stp ieee
>>set vlan 1005 name trnet-default type tr_net mtu 1500 said 101005 state
>>active bridge 0 stp ieee
>>!
>>(...)
>>#module 1 : 2-port 100BaseTX Supervisor
>>set module name 1
>>set vlan 1 1/1-2
>>set port enable 1/1-2
>>set port level 1/1-2 normal
>>set port duplex 1/1-2 half
>>set port trap 1/1-2 disable
>>set port name 1/1-2
>>set port security 1/1-2 disable
>>set port membership 1/1-2 static
>>set cdp enable 1/1-2
>>set cdp interval 1/1-2 60
>>set trunk 1/1 desirable 1-1000
>>set trunk 1/2 auto 1-1000
>>set spantree portfast 1/1-2 disable
>>set spantree portcost 1/1-2 10
>>set spantree portpri 1/1-2 32
>>set spantree portvlanpri 1/1 0
>>set spantree portvlanpri 1/2 0
>>!
>>
>>
>>Thanks in advance for your help
>>
>>Ron
>>
>>
>>
>>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:37 GMT-3