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 IS-IS Local MT

Configuring IS-IS Local MT

With IS-IS local multicast topology (MT), multicast traffic can be transmitted over a traffic engineering (TE) tunnel, and the NE through which the tunnel passes can generate multicast forwarding entries.

Usage Scenario

When multicast and a Multiprotocol Label Switching (MPLS) TE tunnel are configured on a network, the TE tunnel may send multicast packets which are transparent to the NE through which the tunnel passes. As a result, the NE cannot generate multicast forwarding entries. To resolve this problem, enable IS-IS local MT and Interior Gateway Protocol (IGP) Shortcut. If the outbound interface of a calculated route is an IGP Shortcut-enabled TE tunnel interface, the routing management (RM) module creates an independent Multicast IGP (MIGP) routing table. Multicast packets are then forwarded along the routes in the MIGP routing table.

NOTE:

IS-IS local MT takes effect only in public network IS-IS instances.

Pre-configuration Tasks

Before configuring IS-IS local MT, complete the following tasks:

  • Configure IP addresses for interfaces to ensure network connectivity between neighboring nodes.

Configuration Procedures

Figure 9-12 IS-IS local MT networking

Enabling Local MT

After local MT is enabled, routers through which a TE tunnel passes can generate multicast forwarding entries.

Context

Enable local MT in the IS-IS system view before configuring IS-IS MT. To enable the NE through which an IGP Shortcut-enabled TE tunnel passes to generate multicast forwarding entries, perform the following operations on the NE.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run isis [ process-id ]

    The IS-IS view is displayed.

  3. Run cost-style { compatible [ relax-spf-limit ] | wide | wide-compatible }

    The cost style is configured.

    NOTE:

    MPLS TE features take effect only when the cost style is compatible, wide, or wide-compatible.

  4. Run traffic-eng [ level-1 | level-2 | level-1-2 ]

    TE is configured for the process.

  5. Run local-mt enable

    Local MT is enabled.

  6. Run commit

    The configuration is committed.

(Optional) Controlling the Size of the MIGP Routing Table

You can configure a filtering policy based on the multicast source address so that the router adds only the routes destined to the specified multicast source address to the independent Multicast IGP (MIGP) routing table, which controls the size of the MIGP routing table.

Context

After IS-IS local MT is enabled, if the outbound interface of a calculated route is an IGP Shortcut-enabled TE tunnel interface, the routing management (RM) module creates an MIGP routing table, calculates a physical outbound interface for the route, and adds the route to the MIGP routing table. To control the number of entries in the MIGP routing table, speed up the MIGP routing table lookup, and reduce memory resource consumption, configure a filtering policy to enable a device to add only the matching routes to the multicast source address to the MIGP routing table.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run isis [ process-id ]

    The IS-IS view is displayed.

  3. Configure a local MT routing policy.

    Run any of the following commands as required:

    • Based on the basic ACL:
      1. Run local-mt filter-policy acl { acl-number | acl-name }

      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

    After you configure the routing policy, the device adds only the matching routes to the multicast source address to the MIGP routing table.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of IS-IS Local MT

After configuring local MT, check the MIGP routing table, routing information, SPF tree, and IS-IS statistics.

Prerequisites

Local MT has been configured.

Procedure

  • Run the display isis [ process-id ] migp-routing [ ip-address [ mask | mask-length ] | [ level-1 | level-2 ] | verbose ] command to check the IS-IS MIGP routing table.

Example

Configure the device to add only the routes to 192.168.3.0/24 to the MIGP routing table.

<HUAWEI> display isis migp-routing
                       MIGP Route information for ISIS(1)
                       ----------------------------------
                        ISIS(1) Level-2 Forwarding Table
                        --------------------------------
 IPV4 Destination     IntCost    ExtCost ExitInterface   NextHop          Flags
--------------------------------------------------------------------------------
 192.168.3.0/24       40         NULL    GE0/2/0         10.0.1.1         A/-
            Flags: A-Added to MIGP, U-Up/Down Bit Set
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 38092

Downloads: 57

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