INSTALLATION AND CONFIGURATION
2-49
Document No.: COM-00-05-16 June 2006, Revised June 2014
Version: C.1
Figure 2-65. RAW Echelon Message Option
2.6.33
Route Unknown Outbound Echelon: No
Prior to release of executive software releases for the WAG, any Echelon frame that was received
from the Broadcast Medium was routed out the WAG’s Echelon interface despite the fact that the
WAG may not have seen the intended destination device on the Echelon interface.
The WAG’s usual routing behavior dictates that before the WAG can route an ATCS message to an
ATCS device, it must have heard from the destination device first. In previous releases of the
executive software, WAG would go ahead and route Echelon messages out its Echelon interface
even if the destination ATCS device wasn’t in its route table.
When this field is configured as YES, the WAG will continue to route Echelon messages for devices
it hasn’t seen yet out its Echelon interface.
When this field is configured as NO, the WAG will not route Echelon ATCS messages out its
Echelon interface unless it’s heard from the intended destination ATCS device first and thus the
device is in its route table.
When configured for NO, the internal routing of the WAG is consistent across all interfaces in that
it must hear from the device and know of its existence before attempting to route ATCS messages
to unseen devices.
The WAG defaults this configuration setting to: NO.
