Why 'show ip bgp' shows nothing ?

[news2010a]

On RouterB, I do 'show ip bgp' and no info is displayed. I expected that after issuing 'show i bgp', I would see Network '1.0.0.0' advertised. Can someone clarify what am I missing ? PLease find output from 'show run' and 'show ip bgp neigh' as an attachment.

C2610 RouterA is on AS 100, s0/0=192.1.1.1/24 (DCE)

Loopback0=1.1.1.1/24

Connected via V.35 serial cable to

RouterB, AS 200,

s0/0=192.1.1.2/24

Loopback:2.2.2.2/24

[dwyerr]

Hello,

Router B will not see this route as a BGP route because it is directly connected and because Router B is the source of the route.

To confirm that Router B is advertising the route you want to issue "show ip bgp neighbors x.x.x.x advertised-routes" from Router B.

If the route is being advertised then it should show up under "show ip bgp" on Router A.

HTH.

-Rob

[Edison Ortiz]

Marlon,

On Router A, you need to issue the following

network command.

network 1.1.1.0

instead of

network 1.0.0.0

Also, I recommend disabling synchronization on routerB since I see you are doing iBGP there.

With synchronization enabled, routes learned via iBGP peers won't be installed in the routing table. They have to be learned via IGP.

Please rate helpful posts.

Thanks

[jackyoung]

In additional to Edison's post. You can simply add "redist connected" under BGP in router A. Then you can find the route of 1.1.1.0/24 and the LB address in BGP table.

Hope this helps.

[news2010a]

In reality, the network is 1.0.0.0, therefore I did

router bgp 100

network 1.0.0.0

redist connected

and that did it.

I certainly read what the 'redistribute connected' command means but I am not sure if I understand correctly; is this supposed to advertise all routes to external AS ?

RouterB#show ip bgp

BGP table version is 14, local router ID is 2.2.2.2

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

*> 1.1.1.0/24 192.1.1.1 0 0 100 ?

r> 192.1.1.0 192.1.1.1 0 0 100 ?

[sundar.palaniappan]

Hi,

You don't need to configure both - 'network' & 'redistribute connected'. These are two different options to advertise routes via BGP.

The only reason why the route wasn't being advertised earlier with the network command is because your subnet mask for network 1.1.1.0/24 was incorrect. You were using a /8 bit mask instead of /24 bit mask. BGP wouldn't advertise a route if the mask used with the 'network' command isn't consistent with the actual route itself.

The 'redistributed connected' would redistributed all connected interfaces (networks). You can configure 'redistribute connected' with a route-map and specify which networks need to be redistributed.

Hence, you can safely remove the redistribute connected command and configure the 'network' command with the /24 bit mask. After any config change issue the command clear ip bgp soft * for the config change to take effect.

router bgp 100

network 1.1.1.0 mask 255.255.255.0

no redistribute connected

If you prefer you can use the redistribute connected command and in that case you don't need the 'network' statement under the BGP process.

Hope that helps!

Sundar

[news2010a]

True. I did 'no redist connected' and specified network 1.1.1.0 mask 255.255.255.0 and it works fine.

Thanks all for your help. You are rocking.

[jackyoung]

Yes, it will advertise all Connected / local interface to the BGP. I suggest it because of the simple config or you don't want to use mask for the subnet.

So if you only want to advertise 1.1.1.0/24 then you can use network 1.1.1.0 255.255.255.0 command. If you want to advertise all local active interface, then you can use redistribute connected to simplify the config. If you only want to advertise the network of such interface but not want to enable BGP for that interface, you can use passive-interface command to prevent that interface to enable BGP and advertise route from it.

Hope this clarify.

[Harold Ritter]

You would actually need to configure network 1.1.1.0 mask 255.255.255.0. Without the configuration of an explicit mask, the default mask of 255.0.0.0 would be used.

Hope this helps,