On 27/10/11 09:10, Matti Saarinen wrote:
I was brave (or stupid?) enough to try 15.0(1)SY on sup2t. It appears to
work otherwise ok with our simple setup except IPv6 BGP. The neighbours
remain in the idle state. When enabling debug bgp ipv6 unicast I see the
algo following line in the logs:
nbr global [...] Active open failed - route to peer is invalid
Hmm. I just tried it with an iBGP neighbor on our test sup2T running
15.0(1)SY (talking to a sup720 running 12.2(33)SXJ1)
Seems to work:
sh ip bgp ipv6 uni nei 2001:630:12::1 | inc BGP|family|essio
BGP neighbor is 2001:630:12::1, remote AS 64580, internal link
BGP version 4, remote router ID 194.82.152.1
BGP state = Established, up for 00:02:11
Neighbor sessions:
1 active, is not multisession capable (disabled)
Session: 2001:630:12::1
Address family IPv6 Unicast: advertised and received
Multisession Capability:
For address family: IPv6 Unicast
Session: 2001:630:12::1
BGP table version 362, neighbor version 362/0
Bestpath from iBGP peer: 256 n/a
Config at the SY side was:
router bgp 64580
neighbor 2001:630:12::1 remote-as 64580
address-family ipv6
neighbor 2001:630:12::1 activate
Config at the SXJ side was:
router bgp 64580
address-family ipv6 unicast
neighbor 2001:630:12::B remote-as 64580
neighbor 2001:630:12::B route-map DENYALL in
neighbor 2001:630:12::B route-map DENYALL out
neighbor 2001:630:12::B update-source Loopback1
I can ping the neighbour address from the router. Route and CEF tables
agree on where the peer is. What am I missing here? Is there some
specific parameter I need to enable so that IPv6 BGP would work on the
15.0(1)SY? The same config worked on 12.2SX (sup32) and also on
12.2(50)SY (sup2t).
Which IOS image are you running? What IGP?
What's the output for "sh ipv6 route <neigh>"
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
