Byte As Numbers - Dell Force10 C150 Configuration Manual

• If the
does have
• If the
metric)
metric configured in the redistribute command as MED.
• If BGP peer out-bound route-map has
Note: When redistributing static, connected or OSPF routes, there is no metric option. Simply assign the
appropriate route-map to the redistributed route.
Table 10-1gives some examples of these rules.
Table 10-1. Example MED advertisement
Command Settings
redistribute
(IGP cost = 20)
redistribute
route-map set metric 50
redistribute
Ignore Router-ID for some best-path calculations
FTOS 8.3.1.0 and later allow you to avoid unnecessary BGP best-path transitions between external paths
under certain conditions. The
by routing and forwarding plane changes and allows for faster convergence.

4-Byte AS Numbers

FTOS Version 7.7.1 and later support 4-Byte (32-bit) format when configuring Autonomous System
Numbers (ASNs). The 4-Byte support is advertised as a new BGP capability (4-BYTE-AS) in the OPEN
message. If a 4-Byte BGP speaker has sent and received this capability from another speaker, all the
messages will be 4-octet. The behavior of a 4-Byte BGP speaker will be different with the peer depending
on whether the peer is 4-Byte or 2-Byte BGP speaker.
218 | Border Gateway Protocol IPv4 (BGPv4)
redistribute
command does not have any
metric-type internal
configured, BGP advertises the IGP cost as MED.
redistribute
command has
and the BGP Peer out-bound route-map has
isis
isis
isis metric 100
bgp bestpath router-id ignore
metric
configured and BGP Peer out-bound route-map
metric route-map set metric
configured (
metric-type internal
metric
configured, then all other metrics are overwritten by this.
BGP Local Routing
Information Base
WITH route-map
metric-type internal
MED: IGP cost 20 MED = 20
MED: IGP cost 50 MED: 50
MED: IGP cost 100 MED: 100
command reduces network disruption caused
redistribute route-type
or
configured, BGP advertises the
MED Advertised to Peer
WITHOUT route-map
metric-type internal
MED = 0
MED: 50
MED: 100