• Data Plan
  
• Configuring Device Information
  
• Configuring Interfaces
  
• Enabling BFD
  

Data Plan

Network Topology

Construct a network based on the topology shown in Figure 1-19, name network devices, and configure IP addresses for network devices, service interfaces, and user interfaces on the devices.

Figure 1-19  Network topology 

Interface data plan

Table 1-17 and Table 1-18 list Eth-Trunks, local interfaces, and IP addresses of local interfaces on devices.

Table 1-17  Eth-Trunks

Table 1-18  Local Interfaces and IP Addresses

Configuring Device Information

Data Plan

 NOTE:

The data provided in this section is used as an example, which may vary depending on the network scale and topology.

Configure device information on all devices based on the network topology.

Device information includes the site name, device role, and device number. Each device is named in the format of AA_BBX.

• AA: indicates the site name, such as Core and Site1.
• BB: indicates the device role, such as SPE, UPE, and CE.
• X: indicates the device number, starting from 1.

For example, Site1_UPE1 indicates a UPE numbered 1 at site 1. The following table describes the data plan.

Procedure

• Configure the device name.

  The following uses the configuration of Site1_UPE1 as an example. The configurations of other devices are similar to the configuration of Site1_UPE1, and are not mentioned here.

  sysname Site1_UPE1

Configuring Interfaces

Procedure

1. Add physical interfaces to Eth-Trunks.

   The following uses the configuration of Core_SPE1 as an example. The configurations of other devices are similar to the configuration of Core_SPE1, and are not mentioned here.

   # interface XGigabitEthernet1/0/0  eth-trunk 5 # interface XGigabitEthernet1/0/1  eth-trunk 5 # interface XGigabitEthernet1/0/2  eth-trunk 5 # interface XGigabitEthernet1/0/3  eth-trunk 5 # interface XGigabitEthernet5/0/4  eth-trunk 4 # interface XGigabitEthernet5/0/5  eth-trunk 4 # interface XGigabitEthernet5/0/6  eth-trunk 4 # interface XGigabitEthernet5/0/7  eth-trunk 4 # interface XGigabitEthernet6/0/0  eth-trunk 17 # interface XGigabitEthernet6/0/1  eth-trunk 17 # interface XGigabitEthernet6/0/2  eth-trunk 17 # interface XGigabitEthernet6/0/3  eth-trunk 17 #

2. Configure descriptions and IP addresses for interfaces.

   The following uses the configuration of Core_SPE1 as an example. The configurations of other devices are similar to the configuration of Core_SPE1, and are not mentioned here.

   # interface Eth-Trunk4  undo portswitch  description Core_SPE1 to Core_SPE2  ip address 172.17.4.8 255.255.255.254 # interface Eth-Trunk5  undo portswitch  description Core_SPE1 to Core_SPE3  ip address 172.17.4.2 255.255.255.254 # interface Eth-Trunk17  undo portswitch  description Core_SPE1 to Site1_UPE1  ip address 172.17.4.10 255.255.255.254 # interface XGigabitEthernet6/0/4  undo portswitch  description Core_SPE1 to Site3_UPE6  ip address 172.17.10.2 255.255.255.254 # interface LoopBack1  description ** GRT Management Loopback **  ip address 172.16.0.5 255.255.255.255 #

3. Configure Eth-Trunks to function as 40GE interfaces.

   Run the least active-linknumber 4 command on Eth-Trunks of all S9700 switches to configure the Eth-Trunks to function as 40GE interfaces. If a member interface of an Eth-Trunk goes Down, the Eth-Trunk goes Down. The following uses the configuration of Core_SPE1 as an example. The configurations of other devices are similar to the configuration of Core_SPE1, and are not mentioned here.

   # interface Eth-Trunk4  least active-linknumber 4 # interface Eth-Trunk5  least active-linknumber 4 # interface Eth-Trunk17  least active-linknumber 4 #

4. Create Eth-Trunk load balancing profiles and apply the profiles to Eth-Trunks.

   Configure load balancing based on the source and destination port numbers. The following uses the configuration of Core_SPE1 as an example. The configurations of other devices are similar to the configuration of Core_SPE1, and are not mentioned here.

   # load-balance-profile CUSTOM  ipv6 field l4-sport l4-dport  ipv4 field l4-sport l4-dport # interface Eth-Trunk4  load-balance enhanced profile CUSTOM # interface Eth-Trunk5  load-balance enhanced profile CUSTOM # interface Eth-Trunk17  load-balance enhanced profile CUSTOM #

5. Disable STP globally.

   All devices on the entire network are connected through Layer 3 interfaces, and Layer 2 loop prevention protocols are not required. Therefore, disable STP globally. The following uses the configuration of Core_SPE1 as an example. The configurations of other devices are similar to the configuration of Core_SPE1, and are not mentioned here.

   # stp disable #

Enabling BFD

Context

To implement protection switching within 50 ms, set the minimum interval at which BFD packets are sent and received to 3.3 ms. The restraints on switches are as follows:

• For the S12700, the MPU must be an ET1D2MPUA000/ET1D2MPUDC00 card.
• For the S9700, the MPU must be an EH1D2SRUDC00/EH1D2SRUDC01 card.
• For the S7700, the MPU must have an ES0D00FSUA00 card installed or be an EH1D2SRUDC00/EH1D2SRUDC01 card.
• For the S7706/S7706 PoE or S7712, the assign system-resource-mode static command must be run to set the resource allocation mode to static so that the BFD detection duration can be controlled within 50 ms.
• For the S5720HI, S5730HI or S6720HI, the set service-mode enhanced command must be run to configure the switch to work in enhanced mode.

Procedure

• Configure SPEs.

  The following uses the configuration of Core_SPE1 on the core ring as an example. The configurations of Core_SPE2 and Core_SPE3 are similar to the configuration of Core_SPE1, and are not mentioned here.

  # bfd #

• Configure UPEs.

  The following uses the configuration of Site1_UPE1 as an example. The configurations of Site1_UPE2, Site2_UPE3, Site2_UPE4, Site3_UPE5, and Site3_UPE6 are similar to the configuration of Site1_UPE1, and are not mentioned here.

  # bfd #

See more please click 

https://support.huawei.com/enterprise/en/doc/EDOC1000069520/9aadccc0/comprehensive-configuration-examples