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 Commissioning Guide

This is NE40E V800R010C10SPC500 Commissioning Guide
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).
Example for Commissioning an IP Bearer Network

Example for Commissioning an IP Bearer Network

Prerequisites

The NE40Es are installed, cabled, and loaded with configuration scripts.

Networking

Figure 7-1 shows an IP core bearer network that provides multiple services such as 3G, Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), and Internet services. This network consists of two layers, the core layer and the access layer.

  • Core layer

    • This layer has two planes with each plane having four nodes that are fully meshed and located in four cities. The nodes on different planes are connected to each other through 10 Gbit/s or 2.5 Gbit/s links, and backup paths are provided.

    • Intermediate System-to-Intermediate System (IS-IS) is used as an Interior Gateway Protocol (IGP) on the layer, and Traffic Engineering (TE) tunnels are established between Ps on the same plane.

  • Access layer

    • Each NGW is dual-homed to two switches. Each switch is separately connected to a PE. The Virtual Router Redundancy Protocol (VRRP) runs between the PEs and switches, ensuring high availability of the link between the two switches.

    • IBGP peer relationships are established between the PEs and RRs at the core layer.

    • Remote LDP sessions are established between the PEs at different sites (LDP over TE).

    • The PEs at the same site are connected to each other, switches, and core nodes by GE links. On each PE, the interface connected to a switch is called the user-side interface, and the interface connected to the backbone network is called the network-side interface. The user-side interface contains multiple sub-interfaces with each sub-interface being bound to a VPN instance and serving as the gateway for the corresponding CE. BFD runs on the main interface.

Figure 7-1 IP core network topology

Procedure

  1. 1. Commission the hardware of each device.
    1. Logging In to the NE40E by Using the Console Interface
    2. Checking the Software Version
    3. Checking the Health Status of the NE40E
    4. Checking the Board Registration Status
    5. Checking the Power Status
    6. Checking System Time
    7. Checking the Interface Status
    8. Checking Alarm Information
    9. Checking the Voltage of Each Board
    10. Checking the Temperature of Each Board
  2. Commission the link layer.

    NOTE:

    Commission the link layer after the hardware of each device is commissioned and the devices at the two ends of every link are normally started. The links between PEs and Ps need to be commissioned.

    1. Checking Ethernet Interfaces
    2. Checking the Optical Power of Interfaces
  3. Commission services and protocols.

    NOTE:

    After ensuring that all links work properly, commission routing protocols and services such as VPN services.

    1. Commissioning IS-IS Routes

      Commission IS-IS between IS-IS-capable Ps and PEs.

      IS-IS is enabled on the following interfaces:

      • All interfaces on Ps, including Loopback 0 interfaces
      • All interfaces on RRs, including Loopback 0 interfaces
      • Network-side interfaces on PEs, which connect the PEs to the MPLS backbone network
      • Loopback 0 interfaces on PEs
      • Interfaces connecting PEs and Ps
      Figure 7-2 IS-IS interfaces

    2. Commissioning IBGP Routes

      Figure 7-3 shows BGP connections at two sites as an example. At each of the two sites, two PEs are deployed to provide access services. In fact, there are 14 sites in the network, and each RR sets up MP-IBGP connections with 28 PEs.

      Figure 7-3 BGP connections

    3. Commissioning MPLS TE

      Commission the following tunnels.

      • Tunnel paths

        Not more than four primary tunnels exist between each P and the other Ps. Figure 7-4 shows the primary tunnels between Ps on the same plane. All tunnel paths are defined based on the tunnel planning.

        Figure 7-4 Primary tunnels

        In the figure, P1, P2, P5, and P6 each serves as the ingress of three primary tunnels; P3, P4, P7, and P8 each serves as the ingress of two primary tunnels. In all, there are 20 primary tunnels.

        Based on the general tunnel design principle, all tunnels (including primary tunnels and backup tunnels) use strict explicit paths.

        Each primary tunnel has another tunnel as its backup. The primary and backup tunnels do not share the direct links between cities. Figure 7-5 shows the deployment of backup tunnels.

        Figure 7-5 Backup tunnels

        Backup tunnels cannot use the direct links that have been used by the corresponding primary tunnels between cities. For example, the primary tunnel P1->P5 cannot have P1->P2->P6->P5 as its backup tunnel. Its backup tunnel can be P1->P2->P8->P6->P5 or P1->P2->P4->P6->P5.

        Table 7-1 Backup tunnel paths on the upper plane

        Primary Tunnel Path

        Backup Tunnel Path

        P1-P3

        P1-P2-P6-P4-P3

        P1-P5

        P1-P2-P8-P6-P5

        P1-P7

        P1-P2-P6-P8-P7

        P7-P1

        P7-P8-P6-P2-P1

        P7-P5

        P7-P8-P2-P6-P5

        P5-P7

        P5-P6-P2-P8-P7

        P5-P1

        P5-P6-P8-P2-P1

        P5-P3

        P5-P6-P2-P4-P3

        P3-P5

        P3-P4-P2-P6-P5

        P3-P1

        P3-P4-P6-P2-P1

        Table 7-2 Backup tunnel paths on the lower plane

        Primary Tunnel Path

        Backup Tunnel Path

        P2-P4

        P2-P1-P5-P3-P4

        P2-P6

        P2-P1-P3-P5-P6

        P2-P8

        P2-P1-P5-P7-P8

        P8-P2

        P8-P7-P5-P1-P2

        P8-P6

        P8-P7-P1-P5-P6

        P6-P8

        P6-P5-P1-P7-P8

        P6-P2

        P6-P5-P3-P1-P2

        P6-P4

        P6-P5-P1-P3-P4

        P4-P6

        P4-P3-P1-P5-P6

        P4-P2

        P4-P3-P5-P1-P2

        There is no direct link between P7 and P3. The path for the primary tunnel from P7 to P3 is shown in Figure 7-6. Hot backup and best-effort paths are configured to protect each link along the path.

        The design on the primary tunnel between P8 and P4 is similar to that on the primary tunnel between P7 and P3, and is not provided here.

        Figure 7-6 Primary tunnel path from P7 to P3

    4. Commissioning BGP/MPLS IP VPN

      Commission VPN instances on all PEs and user-side interfaces on PEs.

      Table 7-3 VPN parameters

      Parameter

      Value

      VPN name

      • NGN_Media
      • NGN_Signal
      • NGN_Other

      VPN label allocation mode

      Each VPN instance is assigned a label, and all the routes of a VPN instance use the same label.

      VPN tunnel

      LDP LSP

      RD

      The value is in the format of AAAAA:BBBBCCCDE.

      • AAAAA: indicates the BGP AS number (65000).
      • BBBB: indicates the VPN type. If the VPN is an enterprise VPN, the first two Bs identify the enterprise and the last two Bs identify the department.
      • CCC: indicates the site.
      • D: indicates the number of a PE on a plane at a site
      • E: indicates the site. The value 1 indicates plane A; the value 2 indicates plane B.

      RT

      See Table 4.

      Table 7-4 RDs and RTs

      VPN

      Import RT

      Export RT

      Media stream

      65000:0100

      65000:0200

      65000:0300

      65000:0100

      Signaling stream

      65000:0100

      65000:0200

      65000:0300

      65000:0200

      Others

      65000:0100

      65000:0200

      65000:0300

      65000:0300

    5. Commissioning BFD

      BFD configurations consist of the following items:

      • BFD for TE hot-standby
      • BFD for VRRP

      Commission BFD for TE hot-standby on all Ps.

      Commission BFD for VRRP on all PEs.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055014

Views: 4652

Downloads: 63

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