Example for Configuring High-Speed Self Recovery on a Subway Bearer Network

Deploying OSPF

• Configuration Roadmap
  
• Deploying OSPF
  

Configuration Roadmap

Figure 1-20  OSPF neighbor relationship diagram 

Configuration Roadmap

Use OSPF as an IGP to ensure that network-wide devices can be reached through routes and set up MPLS LDP and MPLS TE over OSPF routes. The configuration roadmap is as follows:

1. Add all devices to area 0 and advertise the directly connected network segment and the address of loopback interface 1.
2. Configure all interfaces that do not run OSPF as OSPF silent interfaces to disable the interfaces from sending or receiving OSPF packets. The configuration makes the OSPF network more adaptive and saves network resources.
3. Considering the impact of 31-bit subnet masks, configure the OSPF network type to point-to-point on the main interoperation interface.
4. Configure synchronization between OSPF and LDP to prevent traffic loss caused by switchovers of the primary and backup LSPs.

Deploying OSPF

Context

Configuring OSPF ensures that user-end provider edges (UPEs) and superstratum provider edges (SPEs) can be reached through public network routes.

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.

  router id 172.16.0.5    //Configure a router ID. # interface Eth-Trunk4  ospf network-type p2p    //Set the OSPF network type to P2P on the interfaces using IP addresses with 31-bit subnet masks. # interface Eth-Trunk5  ospf network-type p2p # interface Eth-Trunk17  ospf network-type p2p # interface XGigabitEthernet6/0/4  ospf network-type p2p # ospf 1  silent-interface all    //Prohibit all interfaces from receiving and sending OSPF packets.  undo silent-interface Eth-Trunk4    //Allow interfaces to receive and send OSPF packets.  undo silent-interface Eth-Trunk5  undo silent-interface Eth-Trunk17  undo silent-interface XGigabitEthernet6/0/4  spf-schedule-interval millisecond 10    //Set the route calculation interval to 10 ms to speed up route convergence.  lsa-originate-interval 0    //Set the LSA update interval to 0.  lsa-arrival-interval 0    //Set the interval for receiving LSAs to 0 so that topology or route changes can be immediately detected to speed up route convergence.  graceful-restart period 600    //Enable OSPF GR.  flooding-control    //Enable flooding-control to stabilize neighbor relationships.  area 0.0.0.0   authentication-mode md5 1 cipher %^%#NInJJ<oF9VXb:BS~~9+JT'suROXkVHNG@8+*3FyB%^%#    //Set the authentication mode and password for the OSPF area.   network 172.16.0.5 0.0.0.0   network 172.17.4.2 0.0.0.0   network 172.17.4.8 0.0.0.0   network 172.17.4.10 0.0.0.0   network 172.17.10.2 0.0.0.0 # 

• 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.

  router id 172.16.2.51 # interface Eth-Trunk7  ospf network-type p2p # interface Eth-Trunk17  ospf network-type p2p # ospf 1  silent-interface all  undo silent-interface Eth-Trunk7  undo silent-interface Eth-Trunk17  graceful-restart period 600  bandwidth-reference 100000    //Set the bandwidth reference value used by the system to calculate the interface cost based on a formula.  flooding-control  area 0.0.0.0   authentication-mode md5 1 cipher %^%#nU!dUe#c'J!;/%*WtZxQ<gP:'zx_E2OQnML]q;s#%^%#   network 172.16.2.51 0.0.0.0   network 172.17.4.11 0.0.0.0   network 172.17.4.14 0.0.0.0 #

Checking the Configuration

• Run the display ospf peer command to check OSPF neighbor information. Using Core_SPE1 as an example, if the value of State is Full, OSPF neighbor relationships have set up successfully.

  [Core_SPE1]display  ospf peer            OSPF Process 1 with Router ID 172.16.0.5                  Neighbors   Area 0.0.0.0 interface 172.17.4.8(Eth-Trunk4)'s neighbors  Router ID: 172.16.0.3         Address: 172.17.4.9      GR State: Normal         State: Full  Mode:Nbr is  Slave  Priority: 1    DR: None   BDR: None   MTU: 0        Dead timer due in 40  sec     Retrans timer interval: 4     Neighbor is up for 00:53:42         Authentication Sequence: [ 0 ]                   Neighbors   Area 0.0.0.0 interface 172.17.4.2(Eth-Trunk5)'s neighbors  Router ID: 172.16.0.4      Address: 172.17.4.3     GR State: Normal         State: Full  Mode:Nbr is  Master  Priority: 1    DR: None   BDR: None   MTU: 0        Dead timer due in 37  sec     Retrans timer interval: 4     Neighbor is up for 00:53:22         Authentication Sequence: [ 0 ]                   Neighbors   Area 0.0.0.0 interface 172.17.4.10(Eth-Trunk17)'s neighbors  Router ID: 172.16.2.51       Address: 172.17.4.11       GR State: Normal         State: Full  Mode:Nbr is  Slave  Priority: 1    DR: None   BDR: None   MTU: 0        Dead timer due in 31  sec     Retrans timer interval: 4     Neighbor is up for 00:53:34         Authentication Sequence: [ 0 ]                   Neighbors   Area 0.0.0.0 interface 172.17.10.2(XGigabitEthernet6/0/4)'s neighbors  Router ID: 172.16.2.86      Address: 172.17.10.3      GR State: Normal         State: Full  Mode:Nbr is  Master  Priority: 1    DR: None   BDR: None   MTU: 0        Dead timer due in 32  sec     Retrans timer interval: 5     Neighbor is up for 00:53:42         Authentication Sequence: [ 0 ]

See more please click 

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