![]()
The quantity of operational information logged by the access server and the location used to store this information is configurable.
|
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. |
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 ] |
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.
|
Support contact |
[John_Brown] |
|
System description |
[Access_Server_03] |
|
System location |
[Accounts_Department] |
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] |
|
IP address |
[ ] |
|
Community name |
[ ] |
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).
|
IP address |
[ ] |
|
Community name |
[ ] |
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).
000127
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