Configuring OSPFv3 to Filter Received Routes

After receiving Link State Advertisements (LSAs), OSPFv3 determines whether to add the calculated routes to the local routing table based on a filtering policy.

Procedure

Run system-view
The system view is displayed.
Run ospfv3 [ process-id ]
The OSPFv3 view is displayed.
Run any of the following commands as required:
- Configure a basic ACL:
  1. Run quit
    Return to the system view.
  2. Run acl ipv6 { name basic-acl6-name basic | [ number ] basic-acl6-number } [ match-order { config | auto } ]
    The ACL view is displayed.
  3. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment | source { source-ipv6-address { prefix-length | source-wildcard } | source-ipv6-address/prefix-length | any } | time-range time-name | [ vpn-instance vpn-instance-name | vpn-instance-any ] ] ^*
    A rule is configured for the basic ACL.
    
    When the rule command is run to configure rules for a named ACL, only the source address range specified by source and the time period specified by time-range are valid as the rules.
    When a filtering policy of a routing protocol is used to filter routes:
    - If the action specified in an ACL rule is permit, a route that matches the rule will be received or advertised by the system.
    - If the action specified in an ACL rule is deny, a route that matches the rule will not be received or advertised by the system.
    - If a route has not matched any ACL rules, the route will not be received or advertised by the system.
    - If an ACL does not contain any rules, all routes matching the route-policy that references the ACL will not be received or advertised by the system.
    - In the configuration order, the system first matches a route with a rule that has a smaller number and then matches the route with a rule with a larger number. Routes can be filtered using a blacklist or a whitelist:
      
      Route filtering using a blacklist: Configure a rule with a smaller number and specify the action deny in this rule to filter out the unwanted routes. Then, configure another rule with a larger number in the same ACL and specify the action permit in this rule to receive or advertise the other routes.
      
      Route filtering using a whitelist: Configure a rule with a smaller number and specify the action permit in this rule to permit the routes to be received or advertised by the system. Then, configure another rule with a larger number in the same ACL and specify the action deny in this rule to filter out unwanted routes.
  4. Run ospfv3 [ process-id ]
    The OSPFv3 view is displayed.
  5. Run filter-policy { acl6-number | acl6-name acl6-name } import
    An import policy that is based on the ACL is configured to filter received routes.
- Based on an IPv6 prefix list:
  
  Run filter-policy ipv6-prefix ipv6-prefix-name import
  
  An import policy that is based on an IPv6 prefix list is configured to filter received routes.
- Based on a route-policy:
  
  Run filter-policy route-policy route-policy-name import
  
  An import policy that is based on a route-policy is configured to filter received routes.
- Based on a route-filter:
  
  Run filter-policy route-filter route-filter-name import
  
  An import policy that is based on a route-filter is configured to filter received routes.
The filter-policy import command is used to filter the routes calculated by OSPFv3. Only the routes that match the filtering rules are added to the routing table and can be advertised. Routes that do not match the filtering rules can be added to the OSPFv3 routing table but not to the routing information base (RIB) and cannot be advertised. Therefore, the LSDB is not affected regardless of whether the received routes match the filtering rules.
Run commit
The configuration is committed.