Configuring Peer Policy Templates Use the following tasks to create and configure a peer policy template: Configuring Basic Peer Policy Templates Perform this task to create a basic peer policy template with BGP policy configuration commands that can be applied to many neighbors using one of the next two tasks. The commands in Steps 5 through 7 are optional and could be replaced with any supported BGP policy configuration commands. Note Configuring BGP Configuring Peer Policy Templates Command or Action Purpose Device(config-router)# neighbor 172.16.0.1 remote-as 202 work. If a peering is not configured, the specified neighbor in Step 5 will not accept the session template.
Step 5 neighbor ip-address inherit peer-session session-template-name Example: Device(config-router)# neighbor 172.16.0.1 inherit peer-session CORE1 Sends a peer session template to a neighbor so that the neighbor can inherit the configuration. The example configures a device to send the peer session template named CORE1 to the 172.16.0.1 neighbor to inherit. This template can be applied to a neighbor, and if another peer session template is indirectly inherited in CORE1, the indirectly inherited configuration will also be applied. No additional peer session templates can be directly applied.
However, the directly inherited template can also inherit up to seven additional indirectly inherited peer session templates. Step 6 end Example: Device(config-router)# end Exits router configuration mode and enters privileged EXEC mode. Step 7 show ip bgp template peer-session [session-template-name] Example: Device# show ip bgp template peer-session Displays locally configured peer session templates. The output can be filtered to display a single peer policy template with the optional session-template-name argument. This command also supports all standard output modifiers. Configuring BGP 44