2.38. ROUTE

Home Prev	cOS Stream 4.10.01 Log Reference Guide	Next

Log Categories: ROUTE
Log Message: Monitored host treated as reachable due to low latency.
Default Log Severity: Notice
Parameters: hostip, table, network, gwip, metric, iface
Explanation: A monitored host on the route is now considered unreachable due to high latency.
Gateway Action: None
Action Description: None
Proposed Action: Find and resolve the source of the high latency by checking the connection to the host.

Log Categories: ROUTE
Log Message: Monitored host treated as unreachable due to high latency.
Default Log Severity: Notice
Parameters: hostip, table, network, gwip, metric, iface
Explanation: A monitored host on the route is now considered reachable due to lowered latency.
Gateway Action: None
Action Description: None
Proposed Action: None

Log Categories: ROUTE
Log Message: Monitored host reachable.
Default Log Severity: Notice
Parameters: hostip, table, network, gwip, metric, iface
Explanation: A monitored host on the route is now reachable (after being unreachable).
Gateway Action: None
Action Description: None
Proposed Action: None

Log Categories: ROUTE
Log Message: Monitored host unreachable.
Default Log Severity: Notice
Parameters: hostip, table, network, gwip, metric, iface
Explanation: A monitored host on the route is now unreachable.
Gateway Action: None
Action Description: None
Proposed Action: Find and resolve the source of the host being unreachable by checking the connection to the host.

Log Categories: ROUTE
Log Message: Monitored route disabled.
Default Log Severity: Error
Parameters: table, network, gwip, metric, method, iface
Explanation: The monitoring method (method) triggered a monitored route to be disabled.
Gateway Action: Disable
Action Description: None
Proposed Action: Unless the link of the monitored route is actually malfunctioning, check for connectivity problems with the interface and/or monitored hosts.

Log Categories: ROUTE
Log Message: Monitored route enabled.
Default Log Severity: Notice
Parameters: table, network, gwip, metric, method, iface
Explanation: The monitoring method (method) triggered a monitored route to be enabled.
Gateway Action: Enable
Action Description: None
Proposed Action: None

Log Categories: ROUTE
Log Message: Random sticky state replacement.
Default Log Severity: Warning
Parameters: state, profile, table, network
Explanation: The maximum number of sticky states for the Route Load Balance Profile profile was exceeded, while making a lookup for network in table table. Therefore one instance of sticky state has been randomly selected and discarded; in this case state.
Gateway Action: None
Action Description: None
Proposed Action: Review how the Route Load Balance Profile is being used. Note that the maximum number of sticky states is per profile (not system-wide). Random state replacement will only take place between routes using the same profile, allowing overflow to be handled locally within logical network segments. Also consider keeping sticky state for entire network segments rather than individual IPs, and changing the keepalive condition to be less conservative with regards to remembering old choices.

Log Categories: ROUTE
Log Message: Dynamic route shadowed by configured route.
Default Log Severity: Warning
Parameters: id, table, network, gwip, metric, originator, iface
Explanation: A dynamic route has been added to routing table, but it is being shadowed by one or more statically configured routes. The static routes have been explicitly configured with a RLB profile different from the one used by the dynamic route. Dynamic routes will always use the default RLB profile.
Gateway Action: None
Action Description: The dynamic route will not be used
Proposed Action: Resolve the conflict either by changing the default RLB profile itself, update the conflicting route(s) to use the default RLB profile instead of an explicitly configured profile, or adjust the metric of the routes so that the end result is well defined.