Support Center > Search Results > SecureKnowledge Details
Virtual System becomes unresponsive after adding a route and pushing VSX configuration
Symptoms
  • Virtual System becomes unresponsive after adding a route and pushing VSX configuration in SmartDashboard.

  • In VSX Cluster, output of "cphaprob state" command shows that the state of Virtual System is "Active!/Down"

  • In VSX Cluster, output of "cphaprob list" command shows that the state of Critical Device "routed" is "problem".

  • /var/log/messages file shows the following line from RouteD daemon:
    Next hop for static route NET/MASK can not be an address assigned to a local interface

Cause

The route added has a VSX Gateway IP address that is assigned to an interface on that Virtual System.

Such configuration is not supported - next gateway hop for VSX route can not be the an IP address that belongs to one of the VSX Gateway's interfaces.

Once VSX Gateway receives a packet and decides where to forward it, it will find that the destination IP address belongs to one of the VSX Gateway's interfaces and will drop the packet even when it is intended to the next hop gateway (the route address).


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