Configuring Status Logging

 

syslog (Event logging)  

Configuring SNMP

Configuring SNMP traps

 

syslog (Event logging)

The quantity of operational information logged by the access server and the location used to store this information is configurable.

  1. On the IOCOMM Main menu page, select Global configuration then Event logging.

    Minimum level to log to console

    [debug ]

    Displays on console on port A.

    Minimum level to log to buffer

    [debug ]

    Stores log in internal buffer.

    Minimum level to log to remote host

    [No logging ]

    Logs events in syslog on remote host.


    These allow you to select where the event logging is stored or displayed and the level of event log you wish to capture (this sets the quantity of information).
  2. Select the level of event logging for each destination.

    To view the event log level for each destination, select the down arrow. If you select No logging, no event logs will be stored to this destination. If you select any other level, all levels including the one you have selected and above will be logged. For example, if you select notice, all events from emergency down to notice will be logged. Repeat this selection for the three destinations. If you wish, you can direct event logs to all three destinations, i.e. console, buffer and remote host.

    Note: The IOCOMM internal buffer holds only the last 100 event logs, so it may also be wise to write logs to the console or remote host (or both).

    The event logs saved to buffer or console will only display the correct date and time if a remote host has also been specified (even if No logging has been set for the remote host).

    The event logs written to the IOCOMM buffer can be viewed by using either the CLI command syslog display [number] in CLI mode or by using the IOCOMM Web browser pages (from the Main menu, select Status and statistics display, then Event logging, then System log).

    Note: If the IOCOMM is switched off or re-booted, all event logs held in the internal buffer will be lost.

    Remote syslog host

    [ ]

    Remote host facility to map to

    [NONE ]

  3. To write logs to a remote host, enter either the host name or IP address for the host in the Remote syslog host box. Event logs can be viewed on the selected remote host using the standard syslog command.

    Note: For this option to function correctly with a host name, DNS must be correctly configured. If DNS is not correctly configured, only the IP address entry can be used.

  4. You are also able to set up a special facility on the remote host to capture event logs to specific locations. For example, you could select local 3 as the facility for capturing event logs from the IOCOMM in a particular department or office. Or, you could set up a log facility for each individual IOCOMM.
  5. Select Submit. You are returned to the IOCOMM Global configuration page.
  6. Select Return to the main menu.

Configuring SNMP

  1. On the IOCOMM Main menu page, select Global configuration.
  2. Select SNMP.
  3. If you wish to use an SNMP manager, select Enable SNMP access.
  4. You have the option of entering general system information in the following fields; for example:

    Support contact

    [John_Brown]

    System description

    [Access_Server_03]

    System location

    [Accounts_Department]


    This information may be useful from a general network administration point of view. The information you enter in these fields will appear on the IOCOMM Administration page each time the web browser for the IOCOMM is opened.

    The Support contact line can also be used to create an e-mail shortcut, enabling e-mail messages to be sent directly to the relevant support person (either internally or externally). To use this facility, complete the box using the same form as the following example:

    Support contact

    [mailto:john.brown@anycompany.co.uk]


    The email shortcut can then be used by clicking on the mail address line shown on the IOCOMM Administration page. The email address can be changed at any time.

  5. If you require SNMP traps, select Enable SNMP traps.

    IP address

    [ ]

    Community name

    [ ]

  6. Enter the Community name and IP Address for up to three trap settings as required.

    Note: The Community name (password) required for SNMP write access is the admin password.

    Selecting the Expert option allows you to specify a Port number for the SNMP traps (the factory default is 162).

  7. Select Submit. Your changes will be saved and you will be returned to the Global configuration page.
  8. Select Return to the main menu.

Configuring SNMP traps

  1. On the IOCOMM Main menu page, select Global configuration.
  2. Select SNMP.
  3. To set SNMP traps, select Enable SNMP traps.

    IP address

    [ ]

    Community name

    [ ]

  4. Enter the Community name and IP Address for up to three trap settings as required.

    Selecting the Expert option provides a further administration setting and enables you to specify a Port number for the SNMP traps (the default SNMP port number is 162).

  5. Select Submit. You will be returned to the Global configuration page.
  6. Select Return to the main menu.

000127


Links to Configuration Tasks

Getting Started | Web Access | First Time Configuration Tour | Configuring DNS on IOCOMM | Changing Serial Line Configuration | Resetting a Serial Port | Using a Modem for Dial-in Operation | Outgoing Services | Disable Access | Adding a Terminal | Configuring the Synchronous Port (B) | Printing | Configuring RADIUS | Local Authentication | Dynamic Routing (RIP) | Enabling TCP Security | Global Messages | Configuring Status Logging | Telnet Service (telnetd) | Monitoring Status | Making Changes to IOCOMM