The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
A Log is a set of messages that describe system events. These logs can be very useful during troubleshooting. The logs are saved on the local memory of the device and also can be forwarded over the network to a remote log server. Logs on the remote log server serve as a backup and are useful during log merging and log analysis. This article explains how to add and configure the remote log server on the ESW2-350G switch.
Step 1. Log in to the switch configuration utility and choose Administration > System Log > Remote Log Servers. The Remote Log Servers page opens:
The Remote Log Server Table displays the following information.
• Log Server — The IP address of the SNTP server.
• UDP Port — The UDP port number through which the log messages are sent.
• Facility — The facility number assigned to the remote log server.
• Description — The description of the remote log server.
• Minimum Severity — The severity level of the log message.
Step 2. Click Add. The Add Remote Log Server window appears.
Step 3. Click the radio button according to the desired method by which the server is identified in the Server Definition field.
• By IP address — Indicates that the remote log server is identified by its IP address.
• By name — Indicates that the remote log server is identified by name.
Note: IP version 6 , IPv6 Address Type ad Link Local Interface in the above case cannot be configured as the switch has no interface configured with an IPv6 address.
Step 4. Click the desired IP version radio button.
• Version 6 — Denotes the IPv6 address type.
• Version 4 — Denotes the IPv4 address type.
Step 5. (Optional) If the Version 6 IP address type is chosen, click the desired IPv6 address type.
• Link Local — The IPv6 address uniquely identifies hosts on a single network link.
• Global — The IPv6 address is a global unicast that is visible and reachable from other networks.
Step 6. (Optional) If the Link Local IPv6 address type is chosen, choose the link local interface from the Link Local Interface drop-down list.
Step 7. According to the Server Definition, enter either the IP address or the name of the remote log server in the Log Server IP Address/Name field.
Step 8. Enter the UDP port number in the UPD Port field to which the log messages are sent. The default is 514.
Step 9. Choose the desired facility value which describes the log messages from that facility to the server. Local 0 to Local 7 are available in the Facility drop-down list. Only one facility value can be assigned to a server.
Step 10. Enter the description of the server in the Description field.
Step 11. Choose the minimum severity level of the log messages that are to be sent to the remote server. The Minimum Severity drop-down list has the following event severity levels which are listed from the highest severity to the lowest severity.
• Emergency — System is not usable and system would need immediate attention.
• Alert — Action is needed.
• Critical — System is in a critical condition.
• Error — System is in error condition.
• Warning — System warning has occurred.
• Notice — System is functioning properly, but a system notice has occurred.
• Informational — Device Information.
• Debug — Detailed information about an event is given out.
Step 12. Click Apply. The Remote Log Servers page opens again and displays the new server.