Example:
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)# label mode per-ce
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)#
Configures resilient per-ce label allocation mode.
Step 6
Do one of the following:
•
end
•
commit
Example:
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)# end
or
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)# commit
Saves configuration changes.
•
When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting(yes/no/cancel)?[cancel]:
â—¦
Entering yes saves configuration changes to the running configuration file, exits the configuration session,
and returns the router to EXEC mode.
â—¦
Entering no exits the configuration session and returns the router to EXEC mode without committing the
configuration changes.
â—¦
Entering cancel leaves the router in the current configuration session without exiting or committing the
configuration changes.
•
Use the commit command to save the configuration changes to the running configuration file and remain within
the configuration session.
Configuring Resilient Per-CE Label Allocation Mode Using a Route-Policy
Perform this task to configure resilient per-ce label allocation mode using a route-policy.
Resilient per-CE 6PE label allocation is not supported on CRS-1 and CRS-3 routers, but supported only
on CRS-X routers.
Note
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.1.x
OL-30423-03 157
Implementing BGP
Configuring Resilient Per-CE Label Allocation Mode