catalyst 3560 ipv6 bgp: route received, but not added to routing table

[jperz]

hi community,

I have a really weird issue with my cisco catalyst 3560G. After having researched back and forth, I'm running out of ideas ... maybe someone in here is guru enough to help me out!

device: cisco catalyst 3560g

ios: 12.2-53(SE) IP SERVICES

scenario: configured IPv6 iBGP link between this switch and a router. the router is announcing 1 (test) route. the switch sees the route properly, but doesn't add it to routing table (the route never gets to be "best path", although it should be).

here's a config snippet:

!

ipv6 unicast-routing

!

interface Vlan311

ip address 10.0.0.1 255.255.255.224

ip access-group 311-out out

no ip redirects

no ip unreachables

no ip proxy-arp

ipv6 address 2001:65F:E1:311::1/64

ipv6 enable

!

router bgp 12345

bgp router-id 10.9.1.1

bgp log-neighbor-changes

neighbor 2001:65F:E1:311::2 remote-as 12345

!

address-family ipv4

  no neighbor 2001:65F:E1:311::2 activate

exit-address-family

!

address-family ipv6

  neighbor 2001:65F:E1:311::2 activate

  network 2001:65F:E1::/48

  no synchronization

exit-address-family

!

the session comes up fine, but note that the path is missing the ">" marker for "best path":

sw01#show bgp ipv6 unicast neighbors 2001:65F:E1:311::2 routes

Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,

              r RIB-failure, S Stale

Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path

* i2001:1638::/32   2001:65F:E1:311::2

                                                  100      0 6939 51058 i

and finally, here's what "debug" has to add to this:

Jan 16 19:15:27: IPv6RT[FFFF] RIB lookup failed

Jan 16 19:15:27: BGP(1): no valid path for 2001:1638::/32

The peer (2001:65F:E1:311::2) as well as its link-local ip is pingable.

Any hints?

thanks,

jakob

[inikolova]

Hi,

I've had exactly the same issue to what you describe (with a 3560E) and the TAC team pointed me to bug CSCsy32000 (Although the description doesn't seem to be so much similar to the case here the affected verions and the versions it has been fixed it match

It seem that this has been fixed in 12.2(55)SE (That's why the last test here succeeds.)

It seems we have to upgrade

cheers,

Irena