Users Guide

Version Description
9.10(0.1) Introduced on the S6010-ON and S4048T-ON.
9.8(1.0) Introduced on the Z9100–ON.
9.8(0.0P5) Introduced on the S4048-ON.
9.8(0.0P2) Introduced on the S3048-ON.
9.7(0.0) Introduced on the S6000–ON.
9.2(1.0) Introduced on the Z9500.
9.0.2.0 Introduced on the S6000.
8.3.19.0 Introduced on the S4820T.
8.3.11.1 Introduced on the Z9000.
8.3.7.0 Introduced on the S4810.
7.8.1.0 Introduced on the S-Series.
7.7.1.0 Introduced on the C-Series.
Usage Information If you apply a route map to a BGP peer or neighbor with the neighbor default-
originate command configured, the software does not apply the set filters in the
route map to that BGP peer or neighbor.
When you configure a route-map for a BGP peer or peer group with the neighbor
default-originate command, the command checks for the existence of the route
in BGP RIB.
Route-map configuration on a BGP peer or peer group works only when the LOC-RIB
contains at least one route.
When you apply a default route to a BGP peer or peer group using the neighbor
default-originate command, changes to the configured default route-map are
applied to the BGP peer or peer group only after a delay of 15 seconds. As a result, you
must wait for a period of 15 seconds before manually resetting BGP using the
clear
ip bgp command.
In case of eBGP, the neighbor default-originate command does not support
extended-community as a non-transtive route-map attribute.
You cannot set this configuration for a peer that is associated with a peer group.
Similarly, you cannot associate a peer to a peer group if that peer is already configured
with these settings.
In order that settings corresponding to the neighbor default-originate
command take effect, you must execute the clear ip bgp command immediately
after you execute the neighbor default-originate command.
Border Gateway Protocol 430