Configure Redistribution Policies in Concerto

For supported software information, click here.

Concerto implicitly creates redistribution policies and terms based on the personality of a device (hub, spoke, Controller) and on which protocols are enabled on the LAN side, and then uses these redistribution policies in the appropriate routing protocols. These implicitly created policies do not display in the Concerto user interface.

You can also create custom redistribution policies, and you can then apply them when you create a VPN instance. For more information about creating a VPN instance, see Configure Profiles.

After you attach custom redistribution policies to a VPN instance and publish them, the custom redistribution policies replace the default redistribution policies. To return to default redistribution policies, delete all the custom redistribution policies used in the VPN instance and then republish them.

To configure redistribution policies:

1. Go to Configure > Profile Elements > Policies > Routing > Redistribution Policy.
   1. If you have not previously configured a redistribution policy, the following screen displays. Click Create Redistribution Policy.
      
      
   2. If you had previously configured one or more redistribution policies, the following screen displays.
      
      
       
2. Click the Select Columns field to select which columns to display. The options are Version and Terms.
3. Click the Add icon to create a new redistribution policy. The Add Redistribution Policy screen displays, and Step 1, Terms, is selected.
   
   
    
4. Click the Select Columns field to select which columns to display.
   
   
   
   The options are:

• Order
• Protocol
• Details
• IPv4 Prefix
• IPv6 Prefix
• Enforcement
• Set Group of Fields
• Additional Information

3. Click the Add icon. The Add Redistribution Policy Term screen displays, and Step 1, Match, is selected. Enter information for the following fields.
   
   
    

   Field	Description
   Protocol	Select a protocol: BGP DHCP Direct RIP OSPF SDWAN Static
   Routing Type	If you select the BGP protocol, select a routing type: EBGP IBGP If you select the OSPF protocol, select a routing type: Intra Area Inter Area Type 1 External Type 2 External
   Community	If you select the BGP protocol, enter the BGP community string to match. A BGP community is a group of destinations with a common property. This path attribute in BGP update messages identifies community members and performs actions at a group level instead of to an individual level. BGP communities help identify and segregate BGP routes, enabling a smooth traffic flow.
   Extended Community	If you select the BGP protocol, enter the extended BGP community string to match. In an extended community, you can group a larger number of destinations than in a community. Note that the formats of extended communities used in the match and set sections are different. Valid values are similar to the following: Match—target:222L:222 Set—0000000000000011
   OSPF Area	If you select the OSPF protocol, enter the OSPF area to match.
   OSPF Tag	If you select the OSPF protocol, enter the OSPF tag to match.
   Static Tag	If you select the Static protocol, enter a tag for the static route.
   Monitor	Select a monitor.
   Monitor State	Select a monitor state: Down Up
   IPv4 Prefix (Group of Fields)
   IPv4 Subnet (Required)	Enter a valid IPv4 subnet, for example, 10.1.1.0/24.
   Minimum Length	Enter the minimum length. Range: 0 through 32 Default: None
   Maximum Length	Enter the maximum length. Range: 0 through 32 Default: None
   Action	Select the action to take: Accept Reject
   Add icon	Click the Add icon to add the IPv4 subnet. You can add multiple subnets.
   IPv6 Prefix (Group of Fields)
   IPv6 Subnet (Required)	Enter a valid IPv6 subnet.
   Min Length	Enter the minimum length. Range: 0 through 32 Default: None
   Max Length	Enter the maximum length. Range: 0 through 32 Default: None
   Action	Select the action to take: Accept Reject
   Add icon	Click the Add icon to add the IPv6 subnet. You can add multiple subnets.

4. Click Next to go to Step 2, Action, and then enter information for the following fields.
   
   
    

   Field	Description
   Action	Select the action to take: Accept Reject
   Set Group of Fields
   Community	Enter the BGP community string to match. A BGP community is a group of destinations with a common property. This path attribute in BGP update messages identifies community members and performs actions at a group level instead of to an individual level. BGP communities help identify and segregate BGP routes, enabling a smooth traffic flow. If you configure a community string, you cannot also select a community in the Well-Known Community field.
   Extended Community	Enter the extended BGP community string to match. In an extended community, you can group a larger number of destinations than in a community. Note that the formats of extended communities used in the match and set sections are different. Valid values are similar to the following: Match—target:222L:222 Set—0000000000000011
   Origin	Select the source of the route: Local EGP Remote IGP Unknown Heritage
   OSPF External Type	Select the OSPF external type to use when distributing a route to OSPF: E1 E2
   OSPF Tag	Enter the OSPF tag to add to the route.
   OSPF Metric to BGP Local Preference	For routes being redistributed from OSPF to BGP, click to set the local preference of BGP route to a mapped value from OSPF metric (4294967295 minus the OSPF metric).
   Metric	Enter the BGP multiple exit discriminator (MED) value to match.
   Metric Conversion	Select the conversion factor for the metric value: Set Inverse Scale up Scale down Truncate
   Route Preference	Enter a value for the route preference.
   Local Preference	Enter the local preference to use during the route redistribution.

5. Click Next to go to Step 3, Review & Submit.
   
   
    
6. Enter a name for the redistribution policy under General.
7. Review your configurations. Click Edit next to any section to make changes.
8. Click Save.