From: ying c (bf5tgh1@yahoo.com)
Date: Sat Oct 05 2002 - 20:32:02 GMT-3
Barry,
Thanks for the help. Is there a fix for this known
bug? It's what I got:
r4#sh arp
Protocol  Address          Age (min)  Hardware Addr  
Type   Interface
Internet  148.24.5.10           151   0010.0010.0010 
ARPA   Ethernet0
Internet  148.24.5.5            150   0005.0005.0005 
ARPA   Ethernet0
Internet  148.24.5.4              -   0004.0004.0004 
ARPA   Ethernet0
Internet  148.24.5.100          122   0009.e8fa.9d80 
ARPA   Ethernet0
r5#sh arp
Protocol  Address          Age (min)  Hardware Addr  
Type   Interface
Internet  148.24.5.10           153   0010.0010.0010 
ARPA   Ethernet0
Internet  148.24.5.5              -   0005.0005.0005 
ARPA   Ethernet0
Internet  148.24.5.4            151   0004.0004.0004 
ARPA   Ethernet0
Internet  148.24.5.100          123   0009.e8fa.9d80 
ARPA   Ethernet0
Cat3550#sh arp
Protocol  Address          Age (min)  Hardware Addr  
Type   Interface
Internet  148.24.5.10           124   0010.0010.0010 
ARPA   Vlan100
Internet  148.24.5.100            -   0009.e8fa.9d80 
ARPA   Vlan100
Thanks,
Chang
--- Barry Rowland <reachbarry@bigfoot.com> wrote:
> Check your arp tables on R4, R5, and the cat after
> you ping the cat from
> either
> router. If you see an arp entry that maps the cats
> ip to a mac in the
> routers, but
> do not see an ip to mac map for the routers on the
> switch, then you have a
> known
> bug for the cat3550 ios image. For some unknown
> reason the cat replies to
> the
> routers with it's ip address, proof of this is in
> the routers arp table, but
> does not
> enter a map entry for the router that it replied to.
> 
> Then again, if there is no ip to mac entry for the
> cat in the either of the
> routers arp tables, then you have other issues.
> 
> HTH
> 
> Barry
> 
> 
> ----- Original Message -----
> From: "ying c" <bf5tgh1@yahoo.com>
> To: <swm@emanon.com>; <ccielab@groupstudy.com>
> Sent: Saturday, October 05, 2002 5:34 PM
> Subject: RE: Mgmt Interface 3550 in separate vlan
> REVISITED + clarification
> on Native VLAN
> 
> 
> > Hi Scott,
> >
> > Tried it, but it did not work. I also checked
> Cds42715
> > that Chris mentioned, but the bug is for dot1q
> native
> > mode problem, which is not applied to the isl I'm
> > doing here.
> >
> > Below is my topology, config and sample output,
> > hopefully someone can point out what's wrong:
> >
> >       R4         R5
> >        |          |
> >        |----------|
> >       vlan4 | vlan 5
> >             |
> >             |-----vlan100--cat 3550
> >             |
> >            R10 (router-on-the-stick, vlan 4, 5,
> 100)
> >
> > ip addresses:
> >    r4 e0: 148.24.5.4/24 in vlan 4
> >    r5 e0: 148.24.5.5/24 in vlan 5
> >    r10 BVI 1: 148.24.5.10/24
> >    Cat3550 vlan 100: 148.24.5.100/24 in vlan 100
> >    The goal is to bridge vlan 4, vlan 5 and vlan
> 100.
> >
> > Cat3550 (no ip routing was applied, but not shown
> in
> > sh run):
> >
> > version 12.1
> > !
> > hostname Cat3550
> > !
> > !
> > !
> > interface FastEthernet0/4
> >  switchport access vlan 4
> >  switchport mode access
> >  no ip address
> >  spanning-tree portfast
> > !
> > interface FastEthernet0/5
> >  switchport access vlan 5
> >  switchport mode access
> >  no ip address
> >  spanning-tree portfast
> > !
> > interface FastEthernet0/10
> >  switchport trunk encapsulation isl
> >  switchport trunk allowed vlan 1,4,5,100,1002-1005
> >  switchport mode trunk
> >  no ip address
> > !
> > interface Vlan1
> >  no ip address
> >  shutdown
> > !
> > interface Vlan100
> >  ip address 148.24.5.100 255.255.255.0
> > !
> > ip default-gateway 148.24.5.10
> > --------------------------------------
> > R4:
> >
> > interface Ethernet0
> >  ip address 148.24.5.4 255.255.255.0
> >
> > R5:
> >
> > interface Ethernet0
> >  ip address 148.24.5.5 255.255.255.0
> >
> > R10:
> >
> > !
> > version 12.2
> > !
> > hostname r10
> > !
> > !
> > bridge irb
> > !
> > !
> > interface FastEthernet0/0
> >  mac-address 0010.0010.0010
> >  no ip address
> >  no ip route-cache
> >  no ip mroute-cache
> >  duplex auto
> >  speed auto
> > !
> > interface FastEthernet0/0.4
> >  encapsulation isl 4
> >  no ip redirects
> >  no ip route-cache
> >  no ip mroute-cache
> >  bridge-group 1
> > !
> > interface FastEthernet0/0.5
> >  encapsulation isl 5
> >  no ip redirects
> >  no ip route-cache
> >  no ip mroute-cache
> >  bridge-group 1
> > !
> > interface FastEthernet0/0.100
> >  encapsulation isl 100
> >  no ip redirects
> >  no ip route-cache
> >  no ip mroute-cache
> >  bridge-group 1
> > !
> > interface BVI1
> >  ip address 148.24.5.10 255.255.255.0
> > !
> > bridge 1 protocol ieee
> > bridge 1 route ip
> > !
> > ------------------------------------
> > ping from r4, failed to 3550's mgmt interface:
> >
> > r4#ping 148.24.5.5
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 148.24.5.5,
> timeout
> > is 2 seconds:
> > !!!!!
> > Success rate is 100 percent (5/5), round-trip
> > min/avg/max = 16/18/20 ms
> > r4#ping 148.24.5.10
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 148.24.5.10,
> timeout
> > is 2 seconds:
> > !!!!!
> > Success rate is 100 percent (5/5), round-trip
> > min/avg/max = 1/3/4 ms
> > r4#ping 148.24.5.100
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 148.24.5.100,
> > timeout is 2 seconds:
> > .....
> > Success rate is 0 percent (0/5)
> > r4#
> > -------------------------------------
> > ping from r5, failed to 3550's mgmt interface:
> >
> > r5#ping 148.24.5.4
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 148.24.5.4,
> timeout
> > is 2 seconds:
> > !!!!!
> > Success rate is 100 percent (5/5), round-trip
> > min/avg/max = 4/4/8 ms
> > r5#ping 148.24.5.10
> >
> 
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:40 GMT-3