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

OSN 9800 V100 Configuration Guide 03

This document introduces service configuration process for OSN 9800.
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).
Dependency and Limitation

Dependency and Limitation

This topic describes the dependencies and limitations of MPLS Tunnel in the network design phase.

Network Design Principles

Object

Planning Principle

LSR (Label Switching Router) ID

Plan label switching router (LSR) IDs (LSR ID also known as Node IDs) for NEs, because you need to configure LSR IDs before creating a packet service.

  • An LSR ID can be an IP address of standard class A, B, or C, that is, an IP address within the range from 1.0.0.1 to 223.255.255.254. An LSR ID cannot be a broadcast address (*.*.*.255), multicast address (224.0.0.0 to 239.255.255.255), reserved address (240.0.0.0 to 255.255.255.255), network address (*.*.*.0), zero address (0.*.*.*), loopback address (127.*.*.*), or subnet address (192.168.*.*, 192.169.*.*).
  • Each NE must have an independent and globally unique LSR ID on a network.
  • The LSR ID and IP address of an NE must be different from each other and must belong to different network segments.
  • The LSR ID of an NE and the IP addresses of service ports on the NE must belong to different network segments.

Port

  • Plan IP addresses and subnet masks for ports that will be bound with tunnels.
  • Ensure that the IP addresses of two ports at both ends of a link are in the same network segment.

Tunnel name

Ensure that tunnel names are easy to identify. It is recommended to name a tunnel as follows:
  • Forward tunnel: Service type:RNC site name---Access site name:Working/Protection:Forward
  • Reverse tunnel: Service type:Access site name---RNC site name:Working/Protection:Reverse

Tunnel label

  • Ensure that tunnel labels and PW labels differ, each tunnel label is unique network-wide.
  • The outgoing label of an upstream node is the same as the incoming label of its downstream node on an end-to-end network.

MPLS Tunnel

  • A tunnel can carry co-sourced and co-sinked services. If these services have different reliability requirements, plan different tunnels and protections scheme for these services.
  • If service paths are fixed and the physical connections between ports will not be changed, configure static ARP to enhance network reliability.
Translation
Download
Updated: 2019-09-05

Document ID: EDOC1100033663

Views: 19137

Downloads: 669

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