Configuring Syslog Logging in AOS

Version 2

    Configuring Syslog Logging in AOS

     

    AdTran Operating System (AOS) supports logging via Syslog. This guide explains how to configure and troubleshoot the Syslog agent in AOS.

     

    This guide does not cover configuring a Syslog server. You should consult the Syslog server’s documentation or technical support for configuring and establishing a Syslog server.

     

    Requirements

     

    Each of the following requirements must be met, before logging can be accomplished.

     

    • AOS Device with configured and establish connections
    • Correctly configured Syslog Server
    • IP Address of Syslog Server

    For configuring via the Web Interface:

    • AOS 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 Logging:

     

    1)      Click Logging under Utilities in the left menu.

     

    2)      Check the Event History check box.

     

    Enabling Syslog:

     

    3)      Click the Syslog Forwarding tab.

     

    4)      Check the Syslog Forwarding checkbox.

     

    Configuring Syslog Options:

     

    5)      Choose a Syslog Forwarding 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)’.

     

    6)      Enter the Syslog Receiver IP Address. This is the IP Address of the computer hosting your Syslog server software.

     

    7)       Choose a Logging Facility between ‘Local 0’ and ‘Local 9’. The logging facility level is an arbitrary value that can be used in the Syslog Server software for filtering.

     

    8)      Click Apply.

     

    Saving the Configuration:

     

    9)      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: Your AOS device will now send syslog messages to your syslog server.

     

    Configuring via the Command Line Interface

     

    Syslog logging can be configured via the Command Line Interface in all versions of AOS. For more information about access 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 Exec 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 Syslog:

     

    4)      Type logging forwarding on to enable syslog logging.

     

    Configuring Syslog Options:

     

    5)      Type logging facility local0 to set the logging facility. The logging facility option is used by the Syslog server for filtering.

     

    6)      Type logging forwarding receiver-ip  <ip-address> to set the IP Address to which Syslog entries should be forwarded.

    (Example: logging forwarding receiver-ip 192.168.1.1)

     

    7)      Type logging forwarding priority-level <priority-level> to set the priority level. The priority level options are ‘error’, ‘fatal’, ‘warning’, ‘notice’ and  ‘info’ in ascending order of verbosity (‘error’ being the least verbose and ‘info’ being the most verbose).

    (Example: logging forwarding priority-level notice)

     

     

    Note: Your AOS device will now begin forwarding syslog entries to your Syslog Server.

     

     

     

    Example Configuration

     

    !

    event-history on

    logging forwarding on

    logging facility local0

    logging forwarding priority-level info

    logging forwarding receiver-ip 192.168.1.1

    !

     

     

    Trouble Shooting

     

    There is no method to log ‘debug’ messages with syslog in AOS.

     

    Before beginning to troubleshoot a Syslog connection, it is important to understand that the interface over-which the Syslog message will be transported must be “UP.” There is no method to use Syslog to monitor an interface over which the syslog message must be transported. For Example, if the Syslog server exists across a T1 connection, the syslog server will not receive messages about that T1 interface going down.

     

     

    Set the Priority Level:

     

    To begin, set the priority level to ‘info’. This will ensure that all event messages are transmitted to the Syslog server. If after setting the priority-level to ‘info’ you find the sought after message in your syslog server, configure a more verbose priority-level and try again.

     

    Cause a logged event:

     

    Syslog can be most easily troubleshot by causing a logged event. An easy way to do this is to disconnect the cable from an interface on the AOS device. This will generate a Syslog message to indicate the interface has gone down.

     

     

    Connectivity:

     

    If after setting the priority-level to ‘info’ you find that the Syslog Server is still not receiving entries, be sure that the AOS device and your Syslog server have IP connectivity. An acceptable test is to ping one device from the other. From the Command Line Interface of the NetVanta type the command “ping <ip-address>” to ping the IP Address of the Syslog server. If there is no response, the server and the AOS device do not have connectivity. You should evaluate the network connection, and return to this guide when connectivity exists.