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

System in SIG illegal routing monitoring function can’t inquire BGP routing

Publication Date:  2012-11-02 Views:  32 Downloads:  0
Issue Description
Although configured USG3000 or MSUA and synchronous with SIG BGP routing, but after the system implemented for a period of time, in BGP routing information query without results.
Alarm Information
None.
Handling Process
  1. Login USG3000 or MSUA, execute command “display ip routing-table statistics” to check system’s BGP routing data.
USG3000 or MSUA establishes BGP peer with the border router of the monitoring network, USG3000 or MSUA synchronous routing data should be consistent with border router, otherwise the synchronous may have abnormal.
A, When using USG3000 synchronous routing, if routing number anomaly, please refer to the relevant manuals of USG3000 to check.
B, When using MSUA synchronous routing, if routing number anomaly, please contact technical support engineer.
  2. Check the synchronous parameters configured by system.
A. login USG3000 or MSUA.
B. executive command “system-view”, enter system view.
C. executive command “display this”, check whether the port, user name and password which used to SIG synchronous with BGP synchronous are correct.
When using USG3000 synchronous routing, if it is not correct, please execute command “sig user username password { simple | cipher } password”, configure the authentication user name and password.
When using MSUA synchronous routing, if it is not correct, please execute command “bgp-sync user username password { simple | cipher } password”, configure the authentication user name and password.
D. enable routing sending function.
 Executive command “firewall send-route [ port port-number ] enable”, open routing sending function.
 When using USG3000 synchronous routing, executive command “firewall send-route [ port port-number ] enable”, enable routing sending function.
When using MSUA synchronous routing, please perform the following operation.
1. Executive command “bgp-sync port port-number”, configure the BGP routing synchronization port.
2. Executive command “bgp-sync enable”, enable routing sending function.
The default TCP port is 1808, value range is 1024 to 50000.

In the navigation tree expand "area and equipment management > BGP routing configuration". Click "synchronization configuration," view "effective synchronous threshold".
Login USG3000 or MSUA, check BGP routing data, if effective synchronous threshold is bigger than the USG3000 or MSUA BGP routing number, system do every time synchronization will think the acquired routing tables are missing, synchronous results won't become effective. If found this is a problem, modify the synchronization effective threshold into smaller than USG3000 or MSUA routing amount, waiting for the next time synchronization and import the result into the BGP data table can query.
Root Cause
The possible reasons leading to the failure are as follows:
• reason 1: USG3000 or MSUA didn’t synchronous to the BGP routing.
• reason 2: The parameters on the SIG configured to connect the USG3000 or MSUA error.
• reason 3: effective synchronous threshold value is set too big.
Suggestions
None.

END