Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

No sh ip bgp summary

Hi there,

I have already configured to PE's using iBGP.COnsider the following ascii diagram:

CE1---PE1--[MPLS-Cloud]--PE2--CE2

I suspect that it's a BGP problem:

PE1#sh ip bgp neighbors

BGP neighbor is 200.200.0.10, remote AS 100, internal link

BGP version 4, remote router ID 200.200.0.10

BGP state = Established, up for 00:19:59

Last read 00:00:59, hold time is 180, keepalive interval is 60 seconds

Neighbor capabilities:

Route refresh: advertised and received

Address family IPv4 Unicast: received

Address family VPNv4 Unicast: advertised and received

PE2#sh ip bgp summary

BGP router identifier 200.200.0.10, local AS number 100

BGP table version is 1, main routing table version 1

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

200.200.0.7 4 100 3706 3713 0 0 0 00:20:35 (NoNeg)

PE2#sh ip bgp neighbors

BGP neighbor is 200.200.0.7, remote AS 100, internal link

BGP version 4, remote router ID 200.200.0.7

BGP state = Established, up for 00:21:03

Last read 00:00:03, hold time is 180, keepalive interval is 60 seconds

Neighbor capabilities:

Route refresh: advertised and received(old & new)

Address family IPv4 Unicast: advertised

Address family VPNv4 Unicast: advertised and received

If you noticed, the is no message on PE1 when I issue command sh ip bgp summary but on the other end, it shows.What really happen actually?Perhaps due to that, the vpnv4 route already propagated but...

The reachability on the MPLS core is reachable.

Thanks in advance.

maher

1 REPLY
Cisco Employee

Re: No sh ip bgp summary

BGP address family IPv4 is configured only on PE2. Make sure that on PE1, you activate PE2 under the address-family ipv4 statement. This will only prevent ipv4 updates to be exchanged. It doesn't affect VPNv4 at all.

Hope this helps,

Harold Ritter
Sr. Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México 
Paseo de la Reforma 222 Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
152
Views
0
Helpful
1
Replies