Data Plan
The data provided in this section is used as an example, which may vary depending on the network scale and topology.
NE Role |
Value |
Remarks |
|---|---|---|
Site1_UPE1 |
interface XGigabitEthernet1/0/4.200: 172.18.200.66/26 |
- |
Site1_UPE2 |
interface XGigabitEthernet1/0/4.200: 172.18.200.67/26 |
- |
Site2_UPE3 |
interface XGigabitEthernet0/0/2.150: 172.18.150.2/26 |
- |
Site2_UPE4 |
interface XGigabitEthernet0/0/2.150: 172.18.150.3/26 |
- |
Site3_UPE5 |
interface XGigabitEthernet0/0/2.100: 172.18.100.2/26 |
- |
Site3_UPE6 |
interface XGigabitEthernet0/0/2.100: 172.18.100.3/26 |
- |
Parameter |
Value |
Remarks |
|---|---|---|
VPN instance name |
vpna |
- |
RD value |
UPE: 1:1 Core_SPE1: 5:1 Core_SPE2: 3:1 Core_SPE3: 4:1 |
It is recommended that the same RD value be set on UPEs and SPEs. If different RD values are set, to make VPN FRR take effect, you need to run the vpn-route cross multipath command to add multiple VPNv4 routes to a VPN instance with a different RD value from these routes' RD values. |
RT |
0:1 |
Plan the same RT on the entire network. |
Parameter |
Core_SPE1 |
Core_SPE2 |
Core_SPE3 |
Site1_UPE1 |
Site1_UPE2 |
Site2_UPE3 |
Site2_UPE4 |
Site3_UPE5 |
Site3_UPE6 |
|---|---|---|---|---|---|---|---|---|---|
BGP process ID |
65000 |
65000 |
65000 |
65000 |
65000 |
65000 |
65000 |
65000 |
65000 |
Router ID |
172.16.0.5 |
172.16.0.3 |
172.16.0.4 |
172.16.2.51 |
172.16.2.50 |
172.16.2.75 |
172.16.2.76 |
172.16.2.87 |
172.16.2.86 |
Peer group |
devCore: 172.16.0.3, 172.16.0.4 devHost: 172.16.2.50, 172.16.2.51, 172.16.2.86, 172.16.2.87 |
devCore: 172.16.0.4, 172.16.0.5 devHost: 172.16.2.50, 172.16.2.51, 172.16.2.75, 172.16.2.76 |
devCore: 172.16.0.3, 172.16.0.5 devHost: 172.16.2.75, 172.16.2.76, 172.16.2.86, 172.16.2.87 |
devCore: 172.16.0.3, 172.16.0.5 devHost: 172.16.2.50 |
devCore: 172.16.0.3, 172.16.0.5 devHost: 172.16.2.51 |
devCore: 172.16.0.3, 172.16.0.4 devHost: 172.16.2.76 |
devCore: 172.16.0.3, 172.16.0.4 devHost: 172.16.2.75 |
devCore: 172.16.0.4, 172.16.0.5 devHost: 172.16.2.86 |
devCore: 172.16.0.4, 172.16.0.5 devHost: 172.16.2.87 |
policy vpn-target |
Enable |
Enable |
Enable |
Enable |
Enable |
Enable |
Enable |
Enable |
Enable |
Tunnel policy selector |
Deploy |
Deploy |
Deploy |
- |
- |
- |
- |
- |
- |
Peer priority |
- |
- |
- |
Improve the peer priority of Core_SPE1 so that UPEs preferentially select routes advertised from Core_SPE1. |
Improve the peer priority of Core_SPE2 so that UPEs preferentially select routes advertised from Core_SPE2. |
Improve the peer priority of Core_SPE2 so that UPEs preferentially select routes advertised from Core_SPE2. |
Improve the peer priority of Core_SPE3 so that UPEs preferentially select routes advertised from Core_SPE3. |
Improve the peer priority of Core_SPE3 so that UPEs preferentially select routes advertised from Core_SPE3. |
Improve the peer priority of Core_SPE1 so that UPEs preferentially select routes advertised from Core_SPE1. |