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

NE40E V800R010C10SPC500 Configuration Guide - IP Routing 01

This is NE40E V800R010C10SPC500 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 a Route Target Set

Configuring a Route Target Set

Route target sets are used to match the RTs of VPN routes.

Procedure

  • Configure a route target set using the paragraph editing mode.
    1. Run the edit xpl extcommunity-list rt rt-list-name command to enter the route target set paragraph editing interface view.
    2. Press i to enter the text editing mode.

      NOTE:

      Sets or route-filters can be configured only in the text editing mode. If you exit from the text editing mode, you can perform shortcut key operations only.

    3. Configure a start clause (xpl extcommunity-list rt rt-list-name) for the route target set.
    4. Configure elements for the route target set and separate every two neighboring elements with a comma (,). The elements can be configured in any of the following formats:

      • 2-byte AS number:4-byte user-defined number, for example, 1:3. The AS number is an integer ranging from 0 to 65535, and the user-defined number is an integer ranging from 0 to 4294967295. The AS number and user-defined number must not be both 0s. Specifically, the RT must not be 0:0.
      • IPv4 address:2-byte user-defined number, for example, 192.168.122.15:1. The IPv4 address ranges from 0.0.0.0 to 255.255.255.255, and the user-defined number is an integer ranging from 0 to 65535.
      • Integral 4-byte AS number:2-byte user-defined number, for example, 0:3 or 65537:3. The integral 4-byte AS number ranges from 65536 to 4294967295, and the user-defined number is an integer ranging from 0 to 65535.
      • 4-byte AS number in dotted notation (x.y):2-byte user-defined number, for example, 0.0:3 or 0.1:0. The x, y, and user-defined number are integers ranging from 0 to 65535. The AS number and user-defined number must not be both 0s. Specifically, the RT must not be 0.0:0.
        NOTE:

        In the preceding elements, either value around a colon (:) can be replaced by an asterisk (*) to match any value.

      • regular regular-expression: matches VPN routes with RTs in the specified regular expression. For detailed description about regular expressions, see NE40E Configuration Guide – Basic Configuration.

    5. Configure an end clause (end-list) for the route target set.
    6. Press Esc to exit from the text editing mode.
    7. Press :wq and Enter to save the configurations and exit from the global variable set paragraph editing interface view.

      NOTE:

      A message is displayed for you to confirm whether to commit the configurations when you attempt to exit from the global variable set paragraph editing interface view. To commit the configurations, press Y.

      To exit from the global variable set paragraph editing interface view without saving the configurations, press :q! and Enter.

  • Configure a route target set using the line editing mode.
    1. Run the system-view command to enter the system view.
    2. Run the xpl extcommunity-list rt rt-list-name command to enter the route target set view.
    3. Configure elements for the route target set and separate every two neighboring elements with a comma (,). The elements can be configured in any of the following formats:

      • 2-byte AS number:4-byte user-defined number, for example, 1:3. The AS number is an integer ranging from 0 to 65535, and the user-defined number is an integer ranging from 0 to 4294967295. The AS number and user-defined number must not be both 0s. Specifically, the RT must not be 0:0.
      • IPv4 address:2-byte user-defined number, for example, 192.168.122.15:1. The IPv4 address ranges from 0.0.0.0 to 255.255.255.255, and the user-defined number is an integer ranging from 0 to 65535.
      • Integral 4-byte AS number:2-byte user-defined number, for example, 0:3 or 65537:3. The integral 4-byte AS number ranges from 65536 to 4294967295, and the user-defined number is an integer ranging from 0 to 65535.
      • 4-byte AS number in dotted notation (x.y):2-byte user-defined number, for example, 0.0:3 or 0.1:0. The x, y, and user-defined number are integers ranging from 0 to 65535. The AS number and user-defined number must not be both 0s. Specifically, the RT must not be 0.0:0.
        NOTE:

        In the preceding elements, either value around a colon (:) can be replaced by an asterisk (*) to match any value.

      • regular regular-expression: matches VPN routes with RTs in the specified regular expression. For detailed description about regular expressions, see NE40E Configuration Guide – Basic Configuration.

    4. Run the end-list command to conclude the configuration of the route target set, exit the route target set view, and return to the system view.
    5. Run the commit command to commit the configuration.

Example

NOTE:

If only paragraph editing is used as an example, the corresponding line editing is similar. To use the line editing mode, perform the operations described in paragraph editing.

For detailed set and route-filter configuration steps, see Configuration Procedures of Sets and Route-Filters Using the Paragraph Editing Mode. For detailed description about XPL clauses, see XPL Paragraph Editing Clauses.

Objective Configure a route target set to match the VPN routes with the RT 100:1, 200:1, or 300:1.
Configuration Example
<HUAWEI> edit xpl extcommunity-list rt rt-list1

xpl extcommunity-list rt rt-list1
100:1,
200:1,
300:1
end-list

The route target set contains three elements and can match VPN routes carrying RT 100:1, 200:1, or 300:1.

Objective Configure a route-filter to set the next hop IP addresses of the VPN routes carrying the RTs listed in the set named rt-list1 or less RTs and the VPN routes carrying some of the RTs listed in the set named rt-list1 to 1.1.1.1 and 2.2.2.2, respectively.
Reference Example
<HUAWEI> edit xpl route-filter r1

xpl route-filter r1
if extcommunity rt matches-within rt-list1 then
apply ip next-hop 1.1.1.1
elseif extcommunity rt matches-all rt-list1 then
apply ip next-hop 2.2.2.2
endif
end-filter

The route-filter references the set named rt-list1 and sets the next hop IP addresses of the VPN routes carrying the RTs listed in the set named rt-list1 or less RTs and the VPN routes carrying some of the RTs listed in the set named rt-list1 to 1.1.1.1 and 2.2.2.2, respectively.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 49225

Downloads: 201

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