Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

If you select OSPF from the Protocol drop-down list, do the following:

1. In OSPF Enabled, use the toggle switch to enable (True) or disable (False) OSPF.

2. Expand the IPV4 Prefix List section, and configure the listed fields.

When you configure an IPv4 prefix list, you filter OSPF routes by assigning the prefix list to a neighbor rather than by using an autonomous system (AS) path filter. The process for evaluating a prefix against a prefix list ends when a match is found. For example, to disallow redistribution of a route for 10.0.0.0/24 through OSPF, define an IPv4 prefix list that includes this prefix; the system will reference it from the OSPF redistribution routing map.

    • Name: Enter a name for the IPv4 prefix list. Create a name that does not exceed 64 characters in length. Use numbers, any special characters, uppercase and lowercase letters, and even spaces. Start and end a name with any character but not a space. Leading and trailing spaces will be trimmed off automatically.
    • Description: Enter the description for the IPv4 prefix list.
    • Click Add and enter the following details to add an IPv4 prefix to the list:
      • ACTION: The action to be applied to this IPv4 prefix list. Choose either DENY or PERMIT to allow or disallow traffic to the route that matches the prefix list.
      • PREFIX: Enter the IPv4 prefix. For example, to allow or disallow traffic to 10.0.0.0/8, enter 10.0.0.0/8.
      • IPV4 PREFIX LENGTH GE: The prefix length greater than or equal to the subnet value. This is the lowest value of the range of prefix length.
      • IPV4 PREFIX LENGTH LE: The prefix length less than or equal to the subnet value. This is the highest value of the range of prefix length.
      • SEQUENCE: The entry point of this IPv4 prefix list among other OSPF configurations. Enter a number from 1 to 2147483646. 

For example, if you configure ACTION = PermitIPv4 PREFIX = 10.0.0.0/8, and IPv4 PREFIX LENGTH LESS OR EQUAL = 19, then all networks that fall within the 10.0.0.0/8 range AND have a subnet mask of /19 or less will be allowed through OSPF.

To delete a selected IPv4 prefix, click Remove.  

3. Expand the Route Map drop-down section, and configure the fields listed next. 

A route map evaluates the matching conditions until a successful match occurs. After the match occurs, the route map stops evaluating and starts executing the conditions in the order they were configured. If a successful match does not occur, the route map “falls through” and evaluates the next sequence number of the route map, until all configured route map entries are evaluated or a successful match occurs. To identify the entry, each route map sequence is tagged with a sequence number. Route map entries are evaluated from the lowest sequence number to the highest sequence number. 

    • Name: Enter a name for the route map. Create a name that does not exceed 64 characters in length. Use numbers, any special characters, uppercase and lowercase letters, and even spaces. Start and end a name with any character but not a space. Leading and trailing spaces will be trimmed off automatically.
    • In the Route Map Entry section, specify the following:
      • Action: Choose DENY or PERMIT for this route map. 
      • Description: Enter a description for this route map.
      • Sequence: To determine the entry point of this route map, enter a number from 1 to 2147483646.
    • Match Condition: Click Add and do the following to add a matching condition and a condition value:
      • CONDITION: Enter a name for the matching condition.
      • CONDITION VALUE: Enter a matching value for this condition.

To delete a condition, select it and click Remove

    • Set Community: Click Add and do the following to configure the community settings for the route map. You can use the community attribute to control the routing policy in the upstream service provider’s network.
      • COMMUNITY: Enter the community value.
      • DESCRIPTION: Enter a description for this community attribute.
      • To delete a community, select it and click Remove
    • Add a route map by clicking Add in the bottom-right corner of the section.

4. Expand the OSPF Config drop-down section, and do the following:

  • Expand the Areas section and click Add to add an IP address as an area.
    • AREA: As the area ID, you can enter an integer in the range of 0 to 4294967295. An area is a collection of sub-domains, networks, or routers, and it is identified by a unique ID. In OSPF, Area 0 is created by default and is called the backbone area. In Service Edge, a router corresponds to a Service Edge instance. An area comprises multiple Service Edge instances.
    • AUTH TYPE: Choose either Simple or Message Digest
  • Auto-cost reference bandwidth
  • Expand the Default Info Originate section, and do the following:
    • Advertise Default Route: Toggle either True or False.
    • Always: Toggle either True or False. 
    • Metric
    • Metric Type: Choose either 1 or 2. 
    • Route Map
  • Expand the Global section, enter the IP address of the Service Edge instances in the Router ID field.
  • Log Adjacency Changes: Toggle either True or False. 
  • Passive All: Toggle either True or False. 
  • Expand the Passive Interfaces section, and click Add
    • PASSIVE INTERFACE
  • In PID, enter a random number as the OSPF process ID. The PID is also called the instance ID and is local to OSPF. Service Edge supports only one instance of OSPF.
  • Expand the Interfaces section. Select the area PID that you entered in the Global section, and in the Interface field, enter a name for the area interface.

5. Click Save & Close

  • No labels