Link to home
Start Free TrialLog in
Avatar of leblanc
leblanc

asked on

network in bgp

I have a layer 3 core and it currently has BGP running on it. I need to add another network  in BGP, 192168.1.0/24. Will it work if I just do "network 192168.1.0 mask 255.255.255.0" in the BGP process? I read somewhere that BGP will advertise if it has a route to that network. My BGP knowledge is limited so any tips will be greatly appreciated. Thanks

router bgp 65001
 no synchronization
 network 10.10.0.0 mask 255.255.0.0
 redistribute connected
 neighbor 10.10.3.1  remote-as 65010
 no auto-summary

ip route 0.0.0.0 0.0.0.0 10.10.3.1 
ip route 0.0.0.0 0.0.0.0 10.10.1.1 250

Open in new window

Avatar of Akinsd
Akinsd
Flag of United States of America image

You will need to add the neighbor first with the neighbor command

BGP works differently from other routing protocols
Avatar of leblanc
leblanc

ASKER

the existing config already has the  neighbor 10.10.3.1  remote-as 65010 command
BGP requires that you have an internal route (OSPF, EIGRP, static, connected, whatever) for the same network with the same mask before it will advertise it. You don't need to redistribute it, but it needs to verify the advertised route against the normal routing table.
Avatar of leblanc

ASKER

so what do I need to make it work.
Well, if you type "show ip route" is the route you want to advertise in BGP in your routing table?
Split Horizon and/or synchronization rules.

The BGP synchronization rule states that if an AS provides transit service to another AS, BGP should not advertise a route until all of the routers within the AS have learned about the route via an IGP. Disabling this negates the need to already have a route from an internal routing protocol.

You've disabled that already, so that leaves us with the split horizon rule

BGP split horizon rule state that : When a BGP speaker receives an UPDATE message from an internal peer, the receiving BGP speaker shall not re-distribute the routing information contained in that UPDATE message to other internal peers.."

Verify that the condition does not exist.

There's a lot to BGP and a diagram and more show commands would be necessary to diagnose the problem.

There are other things to look for also.
show ip bgp
show ip bgp summary

http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/22166-bgp-trouble-main.html
Let's start with a more basic question: Are you asking why it isn't working, or are you asking what you need to do to make it work? Because you do need to add that network statement if you want to advertise it out. And the above is correct, if you have no-summary on then you can just add the network statement. But keep in mind that if you don't actually have a route to the network you're advertising, it won't do you any good! The main benefit of no-summary is that you can keep advertising the route even if the internal path goes down.
Avatar of leblanc

ASKER

"But keep in mind that if you don't actually have a route to the network you're advertising, it won't do you any good! " That is what I am trying to understand.
My Cisco core layer 3 switch has  a SVI 192168.1.1/24. All the access switches have a default route pointed to that SVI. So where is the route that I need to have BGP advertised? Thx
If you're advertising to the internet, you can't be advertising 192.168.x.x You have to advertise whatever public addressing you own. Just saying...

Now if you are using BGP in your own network between your own routers, no problem. I asked you earlier to type "show ip route" to see if the route you want to advertise is in the routing table of the BGP router. If it's a connected LAN as you suggest, it will be in the routing table and you shouldn't have any problem.
ASKER CERTIFIED SOLUTION
Avatar of Akinsd
Akinsd
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of leblanc

ASKER

This is a MPLS circuit w/ BGP peering. My configuration is correct. I believe they screwed up in their MPLS cloud because it is working now after they made a change in their routing table. I have a question though. What does redistribute connect do? Why do you need it? Thanks
That redistributes connected routes into BGP. It's easier and cleaner compared to redistributing routes from routing protocols. Since it is not a good practice to publish internal routes into bgp, you'll have to use route maps in conjunction with BGP redistribution to filter out unwanted routes.

For more information about this, see the pdf document in the link below
http://wiki.n4c.eu/wiki/images/e/e2/Bgp-internal.pdf
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of leblanc

ASKER

mikebernhardt,
"...adds routes from physically connected interfaces" I completely agree with you. So if my internal subnets are 10.10.10.0/24 and 10.10.20.0/24 and I advertise "network 10.10.10.0 and network 10.10.20.0" under my BGP process and my SVIs are 10.10.10.1 and 10.10.20.1, I do not need to redistribute connected. Correct?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial