Re: Help with Native Vlan

From: gladston@br.ibm.com
Date: Wed May 25 2005 - 21:14:49 GMT-3


Hi Ed,

Sorry. Wrong diagram. It is R4 instead of R1.

I am working on native between R4 and CAT1.
R4 is connected to CAT1, fa0/4, configured as trunk, nonegotiate; if
native vlan is 1, it works just fine; if native vlan is 4 on CAT1 and R4,
it does not work. Show vlan on R4 shows it sends traffic on Vlan 4, but do
not receive.
I could not find a debug on CAT1 that could show helpful information on
what is going on.
 
R7 is just for testing purposes. It is connected on CAT1, fa0/7, vlan4.

Cordially,
------------------------------------------------------------------
 Gladston

Ed Lui <edwlui@gmail.com>
25/05/2005 19:24
Please respond to
Ed Lui

To
Alaerte Gladston Vidali/Brazil/IBM@IBMBR
cc
Troy Levin <troylevin@hotmail.com>, ccielab@groupstudy.com
Subject
Re: Help with Native Vlan

Gladston,

Not sure if the host name corresponds to the router ? Looks like you
were working on router 4(Rack2R4) vs router 1(as shown on your
diagram)

R1----trunk----CAT1---vlan4--R7

HTH,
Ed Lui

On 5/25/05, gladston@br.ibm.com <gladston@br.ibm.com> wrote:
> Yes, R7 is configured to be on Vlan4 on CAT1, port fa0/7.
>
> Everything works fine until I try to test native vlan.
>
> Native vlan is the same on both sides, R4 e0/0.4 and CAT1 fa0/4.
>
> Cordially
> ------------------------------------------------------------------
> Gladston
>
>
>
> "Troy Levin" <troylevin@hotmail.com>
> 25/05/2005 17:34
>
> To
> Alaerte Gladston Vidali/Brazil/IBM@IBMBR, <ccielab@groupstudy.com>
> cc
>
> Subject
> Re: Help with Native Vlan
>
>
>
>
>
>
> Gladston.
>
> Is your CAT1 port connected to R7 configured for vlan4? If so then your
> traffic from R1 fa0/0.4 will be received by CAT1 as untagged and will be
> processed according to tables of SPT instance 4 which includes the port
to
> R7.
>
> HTH,
>
> Troy
> ----- Original Message -----
> From: <gladston@br.ibm.com>
> To: <ccielab@groupstudy.com>
> Sent: Wednesday, May 25, 2005 1:25 PM
> Subject: Help with Native Vlan
>
>
> > If configuring native vlan other than 1, connectivity is lost.
> >
> > Any idea?
> > version is 12.2(15)T5 for router 2600 and 12.1(20)EA1a for 3550
> >
> > As it is an unexpected behavior I tested on another router and 3550.
> (but
> > the IOS is the same).
> >
> > R1----trunk----CAT1---vlan4--R7
> >
> > Rack2R4#sh run int e 0/0.4
> > Building configuration...
> >
> > Current configuration : 650 bytes
> > !
> > interface Ethernet0/0.4
> > encapsulation dot1Q 4 native
> > ip address 142.20.44.4 255.255.255.0
> > ip access-group 150 in
> > ip directed-broadcast
> > ip multicast helper-map broadcast 229.1.1.1 110
> > rate-limit input access-group 121 512000 64000 96000 conform-action
> > continue exceed-action
> > drop
> > rate-limit input access-group 122 64000 8000 12000 conform-action
> transmit
> > exceed-action dr
> > op
> > rate-limit input access-group 123 32000 4000 6000 conform-action
> transmit
> > exceed-action dro
> > p
> > no ip mroute-cache
> > ip policy route-map Local-traffic
> > ntp multicast 229.2.2.2
> > ipv6 address 2001:1:1:4::4/64
> > ipv6 address FEC0:2E3D:5B7C:4::4/64
> > ipv6 nd suppress-ra
> > end
> >
> > Rack2R4#
> > Rack2R4#sh vlan
> >
> > Virtual LAN ID: 1 (IEEE 802.1Q Encapsulation)
> >
> > vLAN Trunk Interface: Ethernet0/0
> >
> > Protocols Configured: Address: Received:
> > Transmitted:
> >
> > Virtual LAN ID: 4 (IEEE 802.1Q Encapsulation)
> >
> > vLAN Trunk Interface: Ethernet0/0.4
> >
> > This is configured as native Vlan for the following interface(s) :
> > Ethernet0/0
> >
> > Protocols Configured: Address: Received:
> > Transmitted:
> > IP 142.20.44.4 37
> > 90
> >
> > Rack2R4#
> >
> >
> > Rack2CAT1#sh run int fa 0/4
> > Building configuration...
> >
> > Current configuration : 203 bytes
> > !
> > interface FastEthernet0/4
> > switchport trunk encapsulation dot1q
> > switchport trunk native vlan 4
> > switchport mode trunk
> > switchport nonegotiate
> > mls qos trust ip-precedence
> > spanning-tree portfast
> > end
> >
> > Rack2CAT1#sh int fa 0/4 sw
> > Name: Fa0/4
> > Switchport: Enabled
> > Administrative Mode: trunk
> > Operational Mode: trunk
> > Administrative Trunking Encapsulation: dot1q
> > Operational Trunking Encapsulation: dot1q
> > Negotiation of Trunking: Off
> > Access Mode VLAN: 1 (default)
> > Trunking Native Mode VLAN: 4 (VLAN0004)
> > Voice VLAN: none
> > Administrative private-vlan host-association: none
> > Administrative private-vlan mapping: none
> > Administrative private-vlan trunk native VLAN: none
> > Administrative private-vlan trunk encapsulation: dot1q
> > Administrative private-vlan trunk normal VLANs: none
> > Administrative private-vlan trunk private VLANs: none
> > Operational private-vlan: none
> > Trunking VLANs Enabled: ALL
> > Pruning VLANs Enabled: 2-1001
> > Capture Mode Disabled
> > Capture VLANs Allowed: ALL
> > Protected: false
> > Unknown unicast blocked: disabled
> > Unknown multicast blocked: disabled
> > Appliance trust: none
> >
> > Rack2R4(config-subif)#do pi 142.20.44.7
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 142.20.44.7, timeout is 2 seconds:
> > ..
> >
> >
> > If native vlan is default, works fine:
> >
> > Rack2R4(config-subif)# encapsulation dot1Q 4
> >
> > Rack2CAT1(config-if)#sw tr na v 1
> >
> > Rack2R4(config-subif)#do pi 142.20.44.7
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 142.20.44.7, timeout is 2 seconds:
> > !!!!!
> >
> > This is the network:
> >
> > R1----trunk----CAT1---vlan4--R7
> >
> >



This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:12:02 GMT-3