BGP Default-Network

From: Cielieska Nathan (ncielieska@gmail.com)
Date: Fri Jan 18 2008 - 23:57:05 ARST


Guys,

I labbed up a scenario tonight involving BGP default-network for
changing some various redistributed routes.

So i have R4 (AS400) peer with R2 (AS200), set up a few contiguous
loopbacks on R4 and a static route to Null0 to test.

I'm not sure where it would matter but i'll include the ip addresses
on the loopbacks and the Null0 route:

FastEthernet0/0 10.1.1.4 YES manual
up up
Serial1/0 unassigned YES unset
administratively down down
Serial1/1 unassigned YES unset
administratively down down
Serial1/2 unassigned YES unset
administratively down down
Serial1/3 unassigned YES unset
administratively down down
Loopback0 5.5.5.5 YES manual
up up
Loopback1 5.5.1.1 YES manual
up up
Loopback2 5.5.2.1 YES manual
up up
Loopback3 5.5.3.1 YES manual
up up
Loopback4 5.5.4.1 YES manual
up up

Now the Null route

ip route 5.5.0.0 255.255.0.0 Null0

Ok i set up

redistribute static
redistribute connected
default-metric 70

here is what i got:

R4#sh ip bgp
BGP table version is 20, local router ID is 5.5.5.5
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
*> 5.5.0.0/16 0.0.0.0 70 32768 ?
*> 5.5.1.0/24 0.0.0.0 0 32768 ?
*> 5.5.2.0/24 0.0.0.0 0 32768 ?
*> 5.5.3.0/24 0.0.0.0 0 32768 ?
*> 5.5.4.0/24 0.0.0.0 0 32768 ?
*> 5.5.5.5/32 0.0.0.0 0 32768 ?
*> 10.1.1.0/24 0.0.0.0 0 32768 ?

Why is static routes (and i take it IGP routes would do the same)
come in as 70 MED but connected routes come in as 0. Not only that
but the MED gets distributed to peers the same way.

Wondering why?

Regards,
Nate



This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:00 ARST