2.56. RFO

Home Prev	cOS Core 14.00.17 Log Reference Guide	Next

2.56. RFO

These log messages refer to the RFO (Route fail over events) category.

2.56.1. has_ping (ID: 04100001)

Default Severity: NOTICE
Log Message: Interface <iface>, Table <table>, Net <net>: Route enabled, got PING reply from GW <gateway>
Explanation: Route is available. Received PING reply from the gateway.
Firewall Action: None
Recommended Action: None
Revision: 2
Parameters: iface
table
net
gateway

2.56.2. no_ping (ID: 04100002)

Default Severity: WARNING
Log Message: Interface <iface>, Table <table>, Net <net>: Unable to open conn for PING trying again later
Explanation: Unable to open a connection to verify the status of the route. Will try again later.
Firewall Action: try_again_later
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.3. no_ping (ID: 04100003)

Default Severity: ERROR
Log Message: Interface <iface>, Table <table>, Net <net>: Route disabled, no PING reply from Gateway <gateway>
Explanation: Route is not available and has been disabled. Did not receive a PING reply from the gateway.
Firewall Action: route_disabled
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.4. unable_to_register_pingmon (ID: 04100004)

Default Severity: WARNING
Log Message: Interface <iface>, Table <table>, Net <net>: Route no longer monitored, unable to register PING monitor
Explanation: Internal Error: The route is no longer monitored. Failed to register PING Route Monitor.
Firewall Action: route_not_monitored
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.5. unable_to_register_pingmon (ID: 04100005)

Default Severity: ERROR
Log Message: Interface <iface>, Table <table>, Net <net>: Route no longer monitored via PING, unable to register PING monitor
Explanation: Internal Error: The route is no longer monitored. Failed to register PING Route Monitor.
Firewall Action: disabled_monitor
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.6. has_arp (ID: 04100006)

Default Severity: NOTICE
Log Message: Interface <iface>, Table <table>, Net <net>: Route enabled, got ARP reply from Gateway <gateway>
Explanation: Route is available. Received ARP reply from the gateway.
Firewall Action: route_enabled
Recommended Action: None
Revision: 2
Parameters: iface
table
net
gateway

2.56.7. no_arp (ID: 04100007)

Default Severity: ERROR
Log Message: Interface <iface>, Table <table>, Net <net>: Route disabled, no ARP reply from Gateway <gateway>
Explanation: Route is not available and has been disabled. Did not receive a ARP reply from the gateway.
Firewall Action: route_disabled
Recommended Action: None
Revision: 2
Parameters: iface
table
net
gateway

2.56.8. unable_to_register_arp_monitor (ID: 04100008)

Default Severity: ERROR
Log Message: Interface <iface>, Table <table>, Net <net>: Route no longer monitored, unable to register ARP monitor
Explanation: Internal Error: The route is no longer monitored. Failed to register ARP Route Monitor.
Firewall Action: no_monitoring
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.9. unable_to_register_arp_monitor (ID: 04100009)

Default Severity: WARNING
Log Message: Interface <iface>, Table <table>, Net <net>: Route no longer monitored via ARP, unable to register ARP monitor
Explanation: Internal Error: The route is no longer monitored. Failed to register ARP Route Monitor.
Firewall Action: disabled_monitor
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.10. no_link (ID: 04100010)

Default Severity: ERROR
Log Message: Interface <iface> has no link (reason: <reason>), all associated routes disabled.
Explanation: The interface has no link and all associated routes has been disabled.
Firewall Action: associated_routes_disabled
Recommended Action: None
Revision: 2
Parameters: iface
reason

2.56.11. has_link (ID: 04100011)

Default Severity: NOTICE
Log Message: Interface <iface> has link. Some associated routes may require ARP to be enabled
Explanation: The interface has a link. Some associated routes may require ARP to be enabled.
Firewall Action: None
Recommended Action: None
Revision: 2
Parameters: iface

2.56.12. unable_to_register_interface_monitor (ID: 04100012)

Default Severity: ERROR
Log Message: Interface <iface>, Table <table>, Net <net>: Route no longer monitored, unable to register interface monitor
Explanation: Internal Error: Route is no longer monitored. Unable to register Interface Monitor.
Firewall Action: no_monitoring
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.13. unable_to_register_interface_monitor (ID: 04100013)

Default Severity: ERROR
Log Message: Interface <iface>, Table <table>, Net <net>: Route no longer monitored, unable to register interface monitor
Explanation: Internal Error: Route is no longer monitored. Unable to register Interface Monitor.
Firewall Action: disabled_monitor
Recommended Action: None
Revision: 1
Parameters: iface
table
net
gateway

2.56.14. hostmon_failed (ID: 04100014)

Default Severity: NOTICE
Log Message: Interface <iface>, Table <table>, Net <net>: Route disabled, host monitoring failed
Explanation: Route is disabled. Host monitoring failed.
Firewall Action: route_disabled
Recommended Action: None
Revision: 1
Parameters: iface
table
net

2.56.15. hostmon_successful (ID: 04100015)

Default Severity: NOTICE
Log Message: Interface <iface>, Table <table>, Net <net>: Route enabled, host monitoring successful
Explanation: Route is available. Host monitoring successful.
Firewall Action: route_enabled
Recommended Action: None
Revision: 1
Parameters: iface
table
net

2.56.16. hostmon_failed (ID: 04100016)

Default Severity: NOTICE
Log Message: Server <server> not reachable. Server monitors Interface <iface>, Table <table>, Net <net>
Explanation: Server [server] monitoring route [table]:[net] is not any longer reachable.
Firewall Action: None
Recommended Action: None
Revision: 1
Parameters: iface
table
net
server

Home Prev