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

Typical Configuration Examples

SD-WAN V100R018C00

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).
Changing Single-CPE Single-Link (MPLS) Networking to Dual-CPE Dual-Link (MPLS and Internet) Networking

Changing Single-CPE Single-Link (MPLS) Networking to Dual-CPE Dual-Link (MPLS and Internet) Networking

Related Products

Agile Controller-Campus: V300R003C00

AR: V300R003C00

Networking Requirements

One CPE is deployed at the branch site, Site1, of an enterprise as the gateway and it connects to the WAN through an MPLS link, as shown in Figure 4-4. The enterprise wants to add one CPE and one Internet link to change the single-CPE single-link (MPLS) networking to dual-CPE dual-link (MPLS and Internet) networking. Figure 4-5 shows the networking diagram after the change.

Figure 4-4 Networking before the change
Figure 4-5 Networking after the change

Solution Design

The configuration roadmap is as follows:

  1. On the Agile Controller-Campus, create a new branch site according to the networking requirements and complete the service configuration for the new branch site based on the services configured at the old branch site. Unbind the service configuration from the old site, delete the old site, and change the name of the new site to that of the old site.
  2. At the new branch site, re-deploy the CPEs, connect them to the WAN, and complete the CPE deployment.
  3. After the CPEs are deployed, they automatically obtain the modified configuration from the Agile Controller-Campus.

Figure 4-6 shows the operation flowchart.

Figure 4-6 Operation flowchart

Data Plan

One CPE and one Internet link need to be added. In this example, static routes are used as the underlay network routes for interworking with the WAN-side networks. The following tables list required data. The configuration of other services is the same as that of the old branch site, and is not mentioned here.

Table 4-7 Site template for new branch sites

Item

Value

Template name

Site1_new

Description

-

Gateway

Dual Gateways

WAN Link

Name

MPLS

Internet

Device

Device1

Device2

Interface

GE0/0/1

GE0/0/1

Transport Network

MPLS

Internet

Role

Active

Active

Inter-CPE Link

Reuse LAN-side L2 interface

OFF

Device1 Interface

GE0/0/2

Device2 Interface

GE0/0/2

Table 4-8 ZTP configuration for new branch sites

Item

Value

Link name

MPLS

Internet

Interface protocol

IPoE

IPoE

IP address access mode

Static

Static

IP address/Subnet mask

172.16.1.1/24

10.100.13.1/24

Default gateway

172.16.1.254

10.100.13.254

Negotiation mode

Auto

Auto

Uplink bandwidth (Mbps)

100

100

Downlink bandwidth (Mbps)

100

100

Table 4-9 Static route information about the underlay network

Item

Value

Device

Device1

Device2

Priority

60

60

WAN link

MPLS

Internet

Destination address/mask

0.0.0.0/0

0.0.0.0/0

Next-hop type

IP address

IP address

IP address

172.16.1.254

10.100.13.254

Track

OFF

OFF

Table 4-10 Information about devices

Device ESN

Device Name

Device Model

Description

2102351BTJ10H1000015

Site1_1

AR161EW

CPE used at Site1.

2102351BTJ10H1000013

Site1_1_temp

AR161EW

CPE that uses a virtual ESN. It is used to delete the CPE from the old site so that the CPE that is in use can be successfully registered with the new site.

Procedure

  1. Log in to the Agile Controller-Campus as a tenant administrator.
  2. (Optional) Create transport networks.

    The system provides two default transport networks, Internet and Internet1, for which Routing Domain is set to Internet. This configuration case uses the default transport networks.

  3. Create a site template to be used for branch site creation.

    1. Choose Configuration > Site > Template. On the Site Template page that is displayed, click Create.
    2. Enter the template information and click OK.

  4. Add a device based on the device model and use it as the CPE gateway for the new branch site.

    1. Choose Device Management > Device List. The Device List page is displayed.
    2. Click Add Device and set Addition method to Manually create.
    3. Set Mode to Device Model, and click Add.
    4. On the page that is displayed, set Type, Device Model, and Quantity.
    5. Click Edit, change the value of Device Name, and click Submit.
    6. Click OK.

  5. Create a branch site.

    1. Choose Configuration > Site.
    2. On the Site page that is displayed, click Create. Set Creation mode to Single.
    3. Enter the site information, and select the site template configured in the previous step. For a branch site, you need to select the hub site to which it connects.
    4. Under Add Device, select the device added in the previous step.
    5. Click OK.

  6. Complete the ZTP configuration for the new branch site and send a deployment email.

    1. Change the WAN link IP address of the old branch site.
      1. Choose Configuration > Site > ZTP Configuration. The ZTP Configuration page is displayed.
      2. In the site list on the left, click the old branch site. The WAN Link page displays link information.
      3. Click next to the WAN link that will use the IP address of the new site in the Operation column in the right pane.
      4. In the Set WAN Link dialog box that is displayed, set the IP address to a value that does not conflict with those of the other sites.

      5. Click Apply Changes.
    2. Configure the WAN link of the new branch site.
      1. Choose Configuration > Site > ZTP Configuration. The ZTP Configuration page is displayed.
      2. In the Not Activated list, click the new branch site. The WAN Link page displays link information.
      3. Click in the Operation column in the right pane.
      4. In the Set WAN Link dialog box that is displayed, set WAN link parameters.
      5. Click Apply Changes.

    3. Complete the NTP configuration.

      Select the time zone used by the old branch site, and click Apply Changes.

    4. After completing the ZTP configuration, click Send Email.
    5. In the displayed Send Email dialog box, select the site to deploy and click .
    6. Enter the recipient email address and CC email address, select the created email template, modify the email content, and click OK.

  7. Configure WAN routes for the underlay network of the new branch site. The following describes how to configure static routes.

    1. Choose Configuration > Site > Underlay Configuration.
    1. Select the new branch site with ZTP settings completed from the list on the left.
    1. On the WAN Route page that is displayed, click Click Here to Add Routing Protocol and select Static.
    2. On the Static page, click Create and configure static routes for WAN link access. Then, click Apply Changes.

  8. Complete the site configuration for the overlay network of the new branch site, including the interface connecting to the LAN, LAN-side routes, and WAN routing policies. The following describes how to configure VLANs.

    1. Choose Configuration > Overlay Network > Site Configuration.
    2. On the Site Configuration page, select the VPN to which the site to be configured belongs.
    3. Select the new branch site and click VLAN in the right pane.
    4. Click Create and enter VLAN information. On the main page, click Apply Changes.
    5. (Optional) If multiple VPNs are configured for the old branch site, repeat the preceding steps to configure all VPN services for the new branch site.

  9. (Optional) If a custom VPN is configured for the old branch site, add the new branch site to this custom VPN.

    1. Choose Configuration > Overlay Network > VPN.
    2. On the VPN page, click in the Operation column of the VPN to be modified. On the page that is displayed, select the new branch site and click to add it to the VPN.
    3. Click OK.

  10. (Optional) If a traffic distribution policy is configured for the old branch site, unbind this policy from the old branch site and bind it to the new branch site.

    1. Choose Configuration > Overlay Network > Traffic Distribution.
    2. On the Traffic Distribution page, click in the Operation column next to a traffic distribution policy and click Next. On the page that is displayed, select the new branch site and click to associate the policy with it. Then, select the old branch site and click to unbind the policy from it.
    3. Click OK.

  11. (Optional) If a traffic policy is bound to the old branch site, unbind the policy from the old site and bind it to the new branch site. The following uses a QoS policy as an example. The operations are the same for an ACL policy or an intelligent traffic steering policy.

    1. Choose Configuration > Traffic Policy.
    2. On the Overlay page, select the VPN to which the sites to be configured belong.
    3. Click QoS. On the QoS page that is displayed, click Site View.
    4. Select the branch site from which you want to unbind policies, select all policies in the policy list, and click Unbind. In the Confirm dialog box that is displayed, click OK.

    5. Select the new branch site to which you want to bind policies and click Bind New Policy. In the Bind New Policy dialog box that is displayed, select all the required policies and click OK.

    6. Click Commit All. In the Commit dialog box that is displayed, set Effective time and click OK.

  12. (Optional) If a security policy is bound to the old branch site, unbind the policy from the old site and bind it to the new branch site.

    1. Choose Configuration > Security Policy.
    2. On the Security Policy page, select the VPN to which the site to be configured belongs.
    3. On the Security Policy page, click in the Operation column of the policy. In the Attach Sites dialog box that is displayed, select the new branch site and click to bind the policy to it. Select the old branch site and click to unbind the policy from it. Then, click OK.
    4. Select the policy to be submitted, click Commit, and select Commit Selected. In the Commit dialog box that is displayed, set Effective time and click OK.

  13. Add a new CPE using a virtual ESN. The virtual ESN is used to remove the existing CPE from the old branch site, so that the existing CPE can register with the new branch site after deployment.

    When setting the virtual ESN, change the last six digits in the ESN of the CPE at the old site to random digits to ensure that the new ESN does not exist in the system.

    1. Choose Device Management > Device List. The Device List page is displayed.
    2. Click Add Device and set Addition method to Manually create.
    3. Set Mode to ESN and click Add.
    4. Set ESN, Device Name, and Description and click Submit.
    5. Click OK.

  14. Replace the CPE.

    1. Choose Device Management > Device List. The Device List page is displayed.
    2. In the device list, find the CPE of the old branch site. Click in the Operation column of the CPE record. The Device Replacement page is displayed.
    3. In the new device list that is displayed, select the device with the virtual ESN added in the previous step and click OK.

  15. Delete the replaced CPE.

    1. Choose Device Management > Device List. The Device List page is displayed.
    2. In the device list, find the replaced CPE and click in the Operation column of this CPE. In the High Risk dialog box that is displayed, click Yes to delete the device information.

  16. Change the name of the new site to that of the old site.

    1. Choose Configuration > Site.
    2. On the Site page, click in the Operation column next to the old site, change the site name to any value, and click OK.
    3. On the Site page, click in the Operation column next to the new site, change the site name to that of the old site, and click OK.

  17. Install the CPE at the new branch site based on the site networking requirements and connect the WAN port of the CPE to the WAN.
  18. Deploy the CPE at the branch site using email-based deployment.

    1. Press and hold the Reset button on the CPE for 5 seconds or longer to restore the factory settings of the CPE.
    2. Wait for a moment until the SYS indicator on the CPE is blinking green slowly, indicating that the CPE has started successfully.
    3. Perform email-based deployment according to section Email-based Deployment.

  19. After the deployment is successful, verify that the CPE registers with the Agile Controller-Campus again to obtain the configuration of the new branch site.
  20. After the successful change operation, observe the site running status for a period of time. If the site runs properly, go to the next step. Otherwise, refer to Rolling Back from Single-CPE Single-Link (Internet) Networking to Dual-CPE Dual-Link (MPLS and Internet) Networking to roll back the change operation.
  21. (Optional) Delete the old site.

    1. Choose Configuration > Site.
    2. On the Site page, select the old branch site to be deleted and click Delete. In the Warning dialog box that is displayed, enable Forcible deletion, enter yes and click OK.

Translation
Download
Updated: 2019-03-04

Document ID: EDOC1100036696

Views: 18191

Downloads: 116

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