Support Center > Search Results > SecureKnowledge Details
New routes configured in Virtual System object are not shown as "Hidden" on Virtual System, which causes VSX internal IP addresses to be published to Dynamic Routing protocols
Symptoms
  • New routes configured in SmartDashboard in Virtual System object are not shown as "Hidden" on Virtual System until RouteD daemon is restarted on VSX Cluster members:

    1. In SmartDashboard, open Virtual System object that runs a Dynamic Routing protocol (e.g., OSPF, BGP)
    2. Go to Topology pane
    3. Add route(s) / interface(s)
    4. Click on OK and install policy
    5. Connect to command line on VSX Cluster members
    6. Run "show route all" command in Clish
    7. The newly added routes appear without the flag "H" (i.e., it is not hidden)
      Example:
      C 198.18.0.64/28 is directly connected, eth2.3201
      C 198.18.0.80/28 is directly connected, eth2.3200
    8. As a result, VSX internal communication IP addresses are published to Dynamic Routing protocols (e.g., OSPF, BGP)
    9. After killing all the RouteD processes, the newly added routes appear correctly with the flag "H" (and the flag "i")
      Example:
      C H i 198.18.0.64/28 is directly connected, eth2.3201
      C H i 198.18.0.80/28 is directly connected, eth2.3200
Cause

By the current design, when adding new interfaces in VSX Cluster object, their VSX Internal IP addresses will appear as a valid direct route until policy is installed on VSX Cluster and RouteD daemon is restarted.


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