Configuring Console Logging in AOS
AdTran Operating System (AOS) supports event logging via the Console Port. This guide explains how to configure and troubleshoot logging via the Console Port.
Console logging should be used when network logging, such as Syslog or Email logging is not a viable option. Console logging ensures events will always be captured, because the logs will not be transported via a possibly faulty network connection.
This guide does not cover configuring a serial logging server. You should consult the documentation and technical support for third party devices with the appropriate vendor.
Requirements
- AOS device with configured and establish connections
- A 9-pin male to 9-pin female straight through serial cable
- Computer with a 9-pin serial port
For configuring via the Web Interface:
- AOS revision 12 or Higher
- 1st Generation NetVanta 3200/3205 (1200860Lx and 1200870Lx) and NetVanta 2000 Series routers do not support firmware revision 12 or higher
- Modern web-browser with Javascript support
- Internet Explorer 5 or Higher; Firefox 1.5 or Higher
Configuring via the Web Interface
Configuring logging via the Web Interface is supported in AOS firmware revisions 12 and higher. If your AOS device does not support AOS firmware revision 12, you should use the section titled “Configuring via the Command Line Interface”. For more information about accessing the web interface, consult the guide titled “Accessing the Web Interface in AOS”.
Enabling Event Logging:
1) Click Logging under Utilities in the left menu.
2) Check the Event History check box.
Enabling Console Logging:
3) Check the Console Logging check box to enable console port logging.
Configuring Console Logging Options:
4) Choose a Event History Priority Level. ‘Info (0)’ is the most verbose and ‘fatal (5)’ is the least verbose. For general information about interface state changes and firewall messages, choose ‘Notice (3)’.
Saving the Configuration:
5) Click the Save button in the upper-right corner. Not clicking the ‘save’ button will cause the router to loose the changes you have made upon the next reboot.
Note: You may now connect any logging device via the console port of your AOS device to record logging messages.
Configuring via the Command Line Interface
Console logging can be configured via the Command Line Interface in all versions of AOS. For more information about accessing the Command Line Interface, consult the guide titled “Accessing the Command Line Interface in AOS”
Accessing Global Configuration Mode:
1) Type enable to enter Privileged mode. You may be prompted for a password. If you do not know this password, consult the guide “Password Recovery in AOS”.
2) Type configure terminal to access Global Configuration Mode.
Enabling Event Logging:
3) Type event-history on to enable event history logging.
Enabling Console Logging:
4) Type logging console to enable console port logging. This option is enabled by default and therefore will not appear in “show run”.
Configuring Console Logging Options:
5) Type event-history priority <priority-level> to set the priority level. The priority level options are ‘error’, ‘fatal’, ‘warning’, ‘notice’ and ‘info’ in order of verbosity; ‘error’ being the least and ‘info’ being the most verbose.
(Example: logging forwarding priority-level notice)
Saving the Configuration:
6) Type do write to save the current configuration. Skipping this step will cause the router to loose the changes you have made upon the next reboot.
Note: You may now connect any logging device via the console port of your AOS device to record logging messages.
Example Configuration
!
event-history on
logging console
event-history priority notice
!
Troubleshooting
The best method to troubleshoot Console Port logging in AOS, is to access to the Command Line Interface via the Console Port. Consult the guide “Accessing the Command Line Interface” for more information. After accessing the command line interface, and completing this guide, the logged events should be shown in the command-line interface.
Set the Priority Level:
First, set the priority level to ‘info’. This will ensure that all event messages are transmitted out the console port. If after setting the priority-level to ‘info’ you find the sought after message in your logging records, set a more verbose priority-level and try again.
Cause a logged event:
Logging can be most easily troubleshot by causing a logged event; such as causing an interface to go ‘UP’ or ‘DOWN’. Choose an interface that is currently “UP” and disconnect the cable. You should see a message from the console port that indicates the interface changed state to “DOWN”.
