BGP Peer Prefix Policy

Location in GUI: Tenant Template » Tenant Policies » BGP Peer Prefix Policy

Diagram

Classes

tenant_policies (ndo.tenant_templates)

Name	Type	Constraint	Mandatory	Default Value
bgp_peer_prefix_policies	List	[bgp_peer_prefix_policies]	No

bgp_peer_prefix_policies (ndo.tenant_templates.tenant_policies)

Name	Type	Constraint	Mandatory	Default Value
name	String	Regex: ^[a-zA-Z0-9_.:-]{1,64}$	Yes
description	String	Regex: ^[a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]{1,128}$	No
action	Choice	log, reject, restart, shutdown	No	reject
max_prefixes	Integer	min: 1, max: 300000	No	20000
threshold	Integer	min: 1, max: 100	No	75
restart_time	Integer	min: 1, max: 65535	No	65534

Examples

Example-1: The example below shows a tenant policy template called TP1 that is created under the tenant NDO1 and the site APIC1. The BGP peer prefix policy PPP1 is configured with a maximum of 5000 prefixes, a threshold of 75%, and a restart time of 300 seconds with action restart.

ndo:
  tenant_templates:
    tenant_policies:
      - name: TP1
        tenant: NDO1
        sites:
          - APIC1
        bgp_peer_prefix_policies:
          - name: PPP1
            description: BGP Peer Prefix Policy 1
            action: restart
            max_prefixes: 5000
            threshold: 75
            restart_time: 300

Example-2: The example below shows a minimal BGP peer prefix policy PPP2 with only the required name and a log action.

ndo:
  tenant_templates:
    tenant_policies:
      - name: TP1
        tenant: NDO1
        sites:
          - APIC1
        bgp_peer_prefix_policies:
          - name: PPP2
            action: log