Configuring OSPF Local MT

Procedure

1. Run system-view

   The system view is displayed.

2. Run ospf [ process-id ]

   The OSPF process view is displayed.

3. Run local-mt enable

   Local MT is enabled.

   

   • Local MT takes effect only to the OSPF process of a public network instance.
   • Local MT does not support Forwarding Adjacency (FA).

4. (Optional) Run any of the following commands as required:
   • Based on the basic ACL:

     1. Run local-mt filter-policy acl { acl-number | acl-name }

        A routing policy is configured for local MT.

     2. Run quit

        Return to the system view.

     3. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } | [ number ] basic-acl-number } [ match-order { config | auto } ]

        The basic ACL view is displayed.

     4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-name | vpn-instance vpn-instance-name ] ^*

        The rule for the basic ACL is configured.

        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.

   • Based on the IP prefix:

     Run local-mt filter-policy ip-prefix ip-prefix-name

     A routing policy is configured for local MT.

   • Based on the Route-Policy:

     Run local-mt filter-policy route-policy route-policy-name

     A routing policy is configured for local MT.

   • Based on the XPL Route-Policy:

     Run local-mt filter-policy route-filter route-filter-name

     A routing policy is configured for local MT.

   After an MIGP routing table is created, OSPF performs route calculation. If the outbound interface of the calculated route is an IGP Shortcut-enabled TE tunnel interface, the router saves the physical interface on which the tunnel interface is configured as the outbound interface in the MIGP routing table. Multicast packets are then forwarded along this route.

   After the routing policy is configured, only the matching routes to the multicast source address are added to the MIGP routing table, which controls the number of entries in the MIGP routing table and speeds up MIGP routing table lookup.

   Configure a routing policy before you enable local MT, because if an excessive number of routes to a non-multicast source address exist in an MIGP routing table, the number of entries may exceed the upper limit.

5. Run commit

   The configuration is committed.