The following conditions and interactions apply to the automatic trace-route feature:
If multiple links are lost at the same time, only a limited number of automatic trace-route commands are launched.
10 trace-route requests are held in a buffer at any given time; all other links failures that exceed the buffer size are dropped.
Only one automatic trace-route command is launched and completed at a time for each system. A new automatic trace-route cannot begin until the previous automatic trace-route completes or aborts. As soon as an automatic trace-route command is issued for a particular failed link, that entry is removed from the failed link buffer.
-
The automatic trace-route command aborts when:
Encountering failed hops, that is, all three packets for that hop are unanswered (three asterisks).
Some other process (for example, a user-initiated trace-route command) takes precedence.
Communication Manager resets (Level 2 or higher); no further automatic trace-routes are launched during a reset, and the failed link buffer is cleared.
The Linux operating system (OS) shuts down abnormally; any automatic trace-route commands in progress on the native-NIC abort, and the failed link buffer is cleared.
Note:
Aborts due to a Linux OS abnormal shut downs are not logged in the IP events log; the Linux OS logs should indicate that the OS restarted.
Duplicated servers only: the servers interchange (not logged in the IP events log); other areas of the log files should indicate the server interchange, which also includes a warm restart (reset system 1). The failed link buffer is retained through an interchange, and trace-route commands in the buffer are launched after an interchange or warm reset.
Since the log files are resident on each server, a server interchange means that the log file being written to also changes. Only the entries that occur while the given processor is active appear in that server’s log. To get a complete history you must go to each server and view the respective logs.
-
The command is not completed within predetermined time period:
Native NIC: 2 minutes
Note:
Aborted trace-route commands are not restarted for native-NIC interfaces.
Supported servers: RAM disk configuration supports server reliability by partially surviving a disk failure. In this situation, even though Communication Manager is running on the RAM disk, there is no disk to which the system can write the results of the automatic trace-route. For supported servers, see Avaya Aura® Communication Manager Hardware Description and Reference.
