No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - IP Routing
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring OSPF Local MT

Configuring OSPF Local MT

By configuring local multicast topology (MT), you can create a routing table for multicast traffic when multicast and a Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnel are configured on a network.

Usage Scenario

When multicast and an Interior Gateway Protocol (IGP) Shortcut-enabled MPLS TE tunnel are configured on a network, the outbound interface of the route calculated by an IGP may not be a physical interface but a TE tunnel interface. The TE tunnel interface on the NE sends multicast Join packets over a unicast route to the multicast source address. The multicast Join packets are transparent to the NE through which the TE tunnel passes. As a result, the NE through which the TE tunnel passes cannot generate multicast forwarding entries.

To resolve this problem, enable OSPF local MT. After local MT is enabled, if the outbound interface of a calculated route is an IGP Shortcut-enabled TE tunnel interface, the route management (RM) module creates an independent Multicast IGP (MIGP) routing table for the multicast protocol, calculates a physical outbound interface for the route, and adds the route to the MIGP routing table. Multicast packets are then forwarded along this route.

You can configure a routing policy for local MT to control the number of routing entries in an MIGP routing table and speed up MIGP routing table lookup.

Pre-configuration Tasks

Before configuring local MT, complete the following tasks:

  • Configure IP addresses for interfaces to ensure that neighboring Devices are reachable at the network layer.
  • Configure basic OSPF functions.
  • Configure the IGP Shortcut.

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.

    NOTE:
    • 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.

        • If the ACL referenced by the route-policy does not exist, all routes matching the route-policy will 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 NE 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.

Checking the Configurations

  • Run the display ospf [ process-id ] migp-routing [ ip-address [ mask | mask-length ] ] [ interface interface-type interface-number ] [ nexthop nexthop-address ] command to check MIGP routing table information.
  • Run the display ospf [ process-id ] routing command to check OSPF routing table information.
  • Run the display ospf [ process-id ] brief command to check brief OSPF information.

Run the following command to view MIGP routing table information.

<HUAWEI> display ospf migp-routing
          OSPF Process 1 with Router ID 2.2.2.2
                   MIGP Routing Tables

 Routing for Network
 Destination        Cost  Type       NextHop         AdvRouter       Area
 192.168.3.0/24     4     Stub       10.0.1.1        5.5.5.5         0.0.0.0
 4.4.4.4/32         3     Stub       10.0.1.1        4.4.4.4         0.0.0.0
 5.5.5.5/32         4     Stub       10.0.1.1        5.5.5.5         0.0.0.0
 10.0.3.0/24        3     Transit    10.0.1.1        5.5.5.5         0.0.0.0

 Total Nets: 4
 Intra Area: 4  Inter Area: 0  ASE: 0  NSSA: 0
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 37424

Downloads: 57

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next