|
|
|
Route Asserted, Route Selected, and Link Status event packets contain numerical reason codes which are translated into text that is displayed in the Reason column of the Event Log.
State Transition event packets contain the actual text, not a numerical code.
Numerical reason codes are divided by code category. An event packet may contain codes from more than one category, but never more than one code from any single category.
In the web interface Control Panel, explanatory messages for these reasons will be displayed in the Event Log under the Reason column heading and on the Event Details tab under the heading Details. Multiple reasons will be combined into a single comma-separated list.
Reason codes are divided into the following categories:
If the current winner is not in the winner set before evaluation of load (see Chapter 2: WAN Cost and Load Optimization in the CNA Adaptive Path Controller Guide) and the winner set is not empty, the reason code will be 202.
If the current link is in the winner set but is removed because of load evaluation, the reason code will be 205.
Explanatory messages for these codes are as follows:
| Code |
Display Text (Web UI Control Panel) |
Reason Decision Maker Event was Generated |
|---|---|---|
A link formerly declared down because of results of SNMP poll (see code 101) has been restored |
||
Link status has been declared down because of results of SNMP poll. See Link Outage Control in Chapter 3: Adaptive Path Control of the CNA Adaptive Path Controller Guide. |
||
A measurement has been received over a link that had previously timed out (see code 103) |
||
No measurements have been received for the interval specified by the link-measurement-timeout command |
||
A previously detected outage to a prefix across the link has been restored (see code 201) |
||
The prefix has generated sufficient measurements through the link. |
||
Decision maker does not have sufficient measurements for prefix |
There are insufficient measurements through the link for the prefix. |
|
| Code |
Display Text (Web UI Control Panel) |
Reason Decision Maker Event was Generated |
|---|---|---|
No longer able to accept data for the prefix (BGP has withdrawn the route to it, or a user-defined prefix has been removed from the configuration) |
||
A BGP route contains an unknown next hop (could be a route through a service provider not optimized by the CNA system) |
||
Sufficient-data threshold has been crossed (see min-required-measurements command) |
||
Cannot assert a route because of the CNA command require-routes-from-all-routers |
||
Route was withdrawn after the CNA system has spoken to the router, and the CNA command require-routes-from-all-routers has not been enabled |
||
| Code |
Display Text (Web UI Control Panel) |
Reason Decision Maker Event was Generated |
|---|---|---|
| Code |
Display Text (Web UI Control Panel) |
Reason Decision Maker Event was Generated |
|---|---|---|
Link declared winner because of winner-set-priority ranking |
||
| Code |
Display Text (Web UI Control Panel) |
Reason Decision Maker Event was Generated |
|---|---|---|
Decision was made but no action taken because of excessive route-flapping |
||
Decision was made but no action taken because of require-routes-from-all-routers command |
||
Decision was made but no action taken because of unknown next hop |
||
Decision was made but no action taken because of route-assert-filter command |
||
|
|
|