Support Center > Search Results > SecureKnowledge Details
BGP routemaps stop working correctly after upgrade
Symptoms
  • BGP routemaps stop working correctly after Security Gateway upgrade.

  • Comparing the BGP settings in Gaia Database from the original machine and from the upgrade machine shows that BGP "aspath-regex" settings are saved in different ways:

    Example:

    • Taken from original R76:

      set routemap Import_Map_1 id 30 match aspath-regex "65002 | 65002 64513 64513 | 65002 64513" origin any
      set routemap Import_Map_2 id 20 match aspath-regex "64513 64513 65002 | 64513 64513 | 64513" origin any
      
    • Taken after the upgrade to R77.30:

      set routemap Import_Map_1 id 30 match aspath-regex "65002\\|\\65002\\64513\\64513\\|\\65002\\64513" origin any
      set routemap Import_Map_2 id 20 match aspath-regex "64513\\64513\\65002\\|\\64513\\64513\\|\\64513" origin any
      
  • "RTGRTG0019 compile_regex: Regex ... is not a valid GNU regex" error when trying to remove the involved BGP routemap in Clish.

    Example:
    HostName> set routemap Import_Map_2 id 20 off
    RTGRTG0019 compile_regex: Regex "64513\\64513\\65002\\|\\64513\\64513\\|\\64513" is not a valid GNU regex
    
Cause

Format of BGP "aspath-regex" settings in Gaia Database changed in R77.10 and later versions.

During the upgrade from R77 and lower versions, BGP "aspath-regex" settings are not translated correctly to the new format.


Solution
Note: To view this solution you need to Sign In .