[c-nsp] Cisco and BGP MED

[Brandon Ewing]

Is there a knob in Cisco IOS to enable sending the MED learned from an iBGP
peer to an eBGP peer?  Currently, it appears that if an iBGP route is
learned from a local network/aggregate statement, the MED is sent to an eBGP
peer, but if the iBGP route is learned from an iBGP peer, no MED is set on
the update to the eBGP peer. 

Confirmed this in my 7206VXR lab, appears to be so in production on my
Sup720s, but my Foundry MLX series appear to send the learned MED
regardless.

Lab output (Route sourced by netowrk statement on R21, advertised to R2 in
same AS, who advertises it to R1 in different AS):

R21#show ip bgp 192.168.40.0
BGP routing table entry for 192.168.40.0/24, version 2
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  Advertised to update-groups:
        1
  Local
    0.0.0.0 from 0.0.0.0 (2.2.2.21)
      Origin IGP, metric 10000, localpref 100, weight 32768, valid, sourced, local, best

R2#show ip bgp 192.168.40.0 
BGP routing table entry for 192.168.40.0/24, version 2 
Paths: (1 available, best #1, table Default-IP-Routing-Table) 
  Advertised to update-groups: 
        2 
  Local 
    2.2.2.21 (metric 65) from 2.2.2.21 (2.2.2.21) 
      Origin IGP, metric 10000, localpref 100, valid, internal, best 


R1#show ip bgp 192.168.40.0 
BGP routing table entry for 192.168.40.0/24, version 3 
Paths: (1 available, best #1, table Default-IP-Routing-Table) 
  Not advertised to any peer 
  65002 
    1.1.2.2 from 1.1.2.2 (2.2.2.2) 
      Origin IGP, localpref 100, valid, external, best 

-- 
Brandon Ewing                                        (nicotine at warningg.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130329/df48d1c3/attachment.sig>