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>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Wrong MBGP configuration for VRR cause just one VRR is work

Publication Date:  2012-07-27 Views:  51 Downloads:  0
Issue Description
when the Primary VRR failure,some services down.
NE40E:V600R001C00SPC800
Alarm Information
none
Handling Process
1. After find some services down,try to log in backup RR and troubleshooting,login is successful,IGP and MPLS function is normal.
2. Check BGP VPNV4 peer is normal and BGP VPNV4 routing tabel is normal as well.
3. Check the BGP VPNV4 client, some of them can not receive the BGP VPNV4 routing. recheck the configuration in Backup VRR, the configuration as below:
bgp 65000
 router-id 172.29.24.4
 graceful-restart
 peer 172.29.24.9 as-number 65000
 peer 172.29.24.9 connect-interface LoopBack0
 group OCMIPBB internal
 peer OCMIPBB connect-interface LoopBack0
 peer 172.29.24.1 as-number 65000
 peer 172.29.24.1 group OCMIPBB
 peer 172.29.24.2 as-number 65000
 peer 172.29.24.2 group OCMIPBB
 peer 172.29.24.3 as-number 65000
 peer 172.29.24.3 group OCMIPBB
 peer 172.29.24.5 as-number 65000
 peer 172.29.24.5 group OCMIPBB
 peer 172.29.24.6 as-number 65000
 peer 172.29.24.6 group OCMIPBB           
 peer 172.29.24.7 as-number 65000
 peer 172.29.24.7 group OCMIPBB
 peer 172.29.24.8 as-number 65000
 peer 172.29.24.8 group OCMIPBB
 peer 172.29.24.10 as-number 65000
 peer 172.29.24.10 group OCMIPBB
 peer 172.29.24.13 as-number 65000
 peer 172.29.24.13 group OCMIPBB
 peer 172.29.24.14 as-number 65000
 peer 172.29.24.14 group OCMIPBB
 peer 172.29.24.17 as-number 65000
 peer 172.29.24.17 group OCMIPBB
 peer 172.29.24.18 as-number 65000
 peer 172.29.24.18 group OCMIPBB
 peer 172.29.24.19 as-number 65000
 peer 172.29.24.19 group OCMIPBB
 peer 172.29.24.20 as-number 65000
 peer 172.29.24.20 group OCMIPBB
 #
 ipv4-family vpnv4
  reflector cluster-id 65000
  undo policy vpn-target
  peer 172.29.24.1 enable
  peer 172.29.24.2 enable
  peer 172.29.24.3 enable
  peer 172.29.24.5 enable
  peer 172.29.24.6 enable
  peer 172.29.24.9 enable
  peer 172.29.24.10 enable
  peer 172.29.24.13 enable
  peer 172.29.24.14 enable
  peer OCMIPBB enable                     
  peer OCMIPBB reflect-client
  peer 172.29.24.7 enable
  peer 172.29.24.7 group OCMIPBB
  peer 172.29.24.8 enable
  peer 172.29.24.8 group OCMIPBB
  peer 172.29.24.17 enable
  peer 172.29.24.17 group OCMIPBB
  peer 172.29.24.18 enable
  peer 172.29.24.18 group OCMIPBB
  peer 172.29.24.19 enable
  peer 172.29.24.19 group OCMIPBB
  peer 172.29.24.20 enable
  peer 172.29.24.20 group OCMIPBB
---------------------------------------------------------------
some of them enable BGP VPV4 function,but did not belong to BGP group OCMIPBB,so did not reflect the routing information to client.
Root Cause
1. backup RR's hardware problem
2. backup RR's BGP peer is not established.
3. RR function did not configured correctly.
Suggestions
After the project  implementation, make some VRR function test if possible.at least,need to double check the configuration script by HQ expert.

END