Hello,
At this time I get default routes via BGP from transit providers on two sites, running iBGP between the sites (SRX220). I use only the inet.0 routing table.
I plan to peer in one IXP on each site with two BGP sessions on each site. Each IXP has indeed two route servers. Each route server of the first IXP will send 100k IPv4 routes, each route server of the other IXP will send 50k routes.
IXP1 site1 RS1 : 100k routes
IXP1 site1 RS2 : 100k routes
IXP2 site2 RS1 : 50k routes
IXP2 site2 RS2 : 50k routes
Here are my questions :
- I think that in each IXP, the two RS send the same routes (same prefix, same next-hop, same AS path). How many routes maximum should I expect to get in the routing table on each site ? Is it 300k even if I import all the routes with the same local preference ?
At this time I get default routes via BGP from transit providers on two sites, running iBGP between the sites (SRX220). I use only the inet.0 routing table.
I plan to peer in one IXP on each site with two BGP sessions on each site. Each IXP has indeed two route servers. Each route server of the first IXP will send 100k IPv4 routes, each route server of the other IXP will send 50k routes.
IXP1 site1 RS1 : 100k routes
IXP1 site1 RS2 : 100k routes
IXP2 site2 RS1 : 50k routes
IXP2 site2 RS2 : 50k routes
Here are my questions :
- I think that in each IXP, the two RS send the same routes (same prefix, same next-hop, same AS path). How many routes maximum should I expect to get in the routing table on each site ? Is it 300k even if I import all the routes with the same local preference ?
- How many routes in the forwarding table should I expect ? Is it 150k if I get routes to totally different prefixes on each IXP ?
- I tried before not to import BGP routes received from neighbor. Back then JTAC told me that it's mandatory that the routes are stored as hidden routes. Is it mandatory that a route received from a neighbor consumes space in the routing table because of that ? No way to totally drop a route and not use memory at all ?
- I plan to use for joining the IXPs a SRX345. Does someone has an idea of the convergence time in case a session goes down then up again or a routing process restart ? Would that be a few seconds ? several minutes ?
- What would be the impact on the traffic of an IXP BGP session going down then up again ? I guess it depends on what routes are removed from the routing table / forwarding table.
- More specifically, if one or several IXP BGP sessions goes down, will the traffic continue to flow seamlessly because the default routes I receive from my transit providers will stay in the forwarding table in this case ?
Regards,
- I tried before not to import BGP routes received from neighbor. Back then JTAC told me that it's mandatory that the routes are stored as hidden routes. Is it mandatory that a route received from a neighbor consumes space in the routing table because of that ? No way to totally drop a route and not use memory at all ?
- I plan to use for joining the IXPs a SRX345. Does someone has an idea of the convergence time in case a session goes down then up again or a routing process restart ? Would that be a few seconds ? several minutes ?
- What would be the impact on the traffic of an IXP BGP session going down then up again ? I guess it depends on what routes are removed from the routing table / forwarding table.
- More specifically, if one or several IXP BGP sessions goes down, will the traffic continue to flow seamlessly because the default routes I receive from my transit providers will stay in the forwarding table in this case ?
Regards,