RE: IPv6 BGP

Try to get into the habit of using the new unified syntax format for the BGP AFI/SAFIs. This way when you get into more details of IPv4 Multicast BGP, IPv6 Unicast BGP, or VPNv4 BGP you'll have a better grasp on exactly what you're trying to verify. Overall this syntax makes more sense because it uses a logical hierarchy.

Router#show bgp ipv4 unicast
Router#show bgp ipv4 unicast summary
Router#show bgp ipv4 unicast neighbors
Router#show bgp ipv4 unicast neighbors a.b.c.d advertised-routes

Router#show bgp ipv4 multicast
Router#show bgp ipv4 multicast summary
Router#show bgp ipv4 multicast neighbors
Router#show bgp ipv4 multicast neighbors a.b.c.d advertised-routes

Router#show bgp ipv6 unicast
Router#show bgp ipv6 unicast summary
Router#show bgp ipv6 unicast neighbors
Router#show bgp ipv6 unicast neighbors a:b:c::d advertised-routes

Router#show bgp vpnv4 unicast all
Router#show bgp vpnv4 unicast all summary
Router#show bgp vpnv4 unicast all neighbors
Router#show bgp vpnv4 unicast all neighbors a.b.c.d advertised-routes

HTH,

Brian McGahan, CCIE #8593 (R&S/SP/Security)
bmcgahan_at_INE.com
 
Internetwork Expert, Inc.
http://www.INE.com

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Alexei Monastyrnyi
Sent: Friday, July 15, 2011 12:19 AM
To: marc edwards
Cc: Cisco certification
Subject: Re: IPv6 BGP

no worries. :-) happy studies!
A.

On 7/15/2011 5:18 PM, marc edwards wrote:
> BGP table version is 3, local router ID is 1.1.1.1
> 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
> *> FEC0:43::/64 FEC0:124::131 0 0 4 i
> * FEC0:124::/64 FEC0:124::131 0 0 4 i
> *> :: 0 32768 i
>
> r4#sh ip bgp ipv6 unicast
> BGP table version is 25, local router ID is 4.4.4.4
> 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
> *> FEC0:43::/64 :: 0 32768 i
> * FEC0:124::/64 FEC0:124::129 0 0 1 i
> *> :: 0 32768 i
> r4#
>
>
> Although I am tired and haven't touched my lab since the post, you
> made staying up well worth it. Much thanks.
>
> Marc
>
> On Fri, Jul 15, 2011 at 12:15 AM, Alexei Monastyrnyi
> <alexeim73_at_gmail.com> wrote:
>> how about show ip bgp ipv6 unicast ?
>>
>> On 7/15/2011 3:51 PM, marc edwards wrote:
>>
>> experts:
>>
>> I have configured a pretty basic set up but having issues advertising
>> some routes. I have R1 ---FR---> R4
>>
>> R1 has many loopbacks setup on lo 1:
>>
>>
>> r1#sh run int lo1
>> Building configuration...
>>
>> Current configuration : 311 bytes
>> !
>> interface Loopback1
>> ip address 1.1.1.1 255.255.255.255
>> ipv6 address FEC0:10:10::1/64
>> ipv6 address FEC0:10:11::1/64
>> ipv6 address FEC0:10:12::1/64
>> ipv6 address FEC0:10:13::1/64
>> ipv6 address FEC0:10:14::1/64
>> ipv6 address FEC0:10:15::1/64
>> ipv6 address FEC0:10:16::1/64
>> ipv6 address FEC0:10:17::1/64
>>
>> I am trying to advertise these networks over to R4 with following
>> configuration on R1:
>>
>> router bgp 1
>> no synchronization
>> bgp log-neighbor-changes
>> neighbor FEC0:124::131 remote-as 4
>> no auto-summary
>> !
>> address-family ipv6
>> neighbor FEC0:124::131 activate
>> network FEC0:124::/64
>> no synchronization
>> exit-address-family
>>
>> I guess the problem must be on r1 because I don't see the advertised
>> network hitting it's own bgp table
>>
>> r1#sh ip bgp
>>
>> r1#
>>
>> Pretty cool that the same show commands can work for both ipv4 and
>> ipv6 in BGP. I just wish I had something to show for it (no pun
>> intended). Any suggestions? Thanks greatly in advance for help.
>>
>> Marc Edwards
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri Jul 15 2011 - 08:53:21 ART