User Manual
Table Of Contents
- Insight Managed 8-Port Gigabit Ethernet Smart Cloud Switch with 2 SFP Fiber Ports
- Contents
- 1. Getting Started
- Switch Management Options and Default Management Mode
- Available Publications
- Web Browser Requirements and Supported Browsers
- User-Defined Fields
- Interface Naming Conventions
- Access the Switch
- Change the Management Mode of the Switch
- Register the Switch
- How to Configure Interface Settings
- Local Browser Interface Device View
- 2. Configure System Information
- View and Configure the Switch Management Settings
- View or Define System Information
- View the Switch CPU Status
- Configure the CPU Thresholds
- Configure the IPv4 Address for the Network Interface and Management VLAN
- Configure the IPv6 Address for the Network Interface
- View the IPv6 Network Neighbor
- Configure the Time Settings
- Configure Denial of Service Settings
- Configure DNS Settings
- Configure Green Ethernet Settings
- Manage the Bonjour Settings and View Bonjour Information
- Control the LEDs
- Use the Device View
- Configure Power over Ethernet
- Configure Link Layer Discovery Protocol
- Configure DHCP L2 Relay and DHCP Snooping
- Set Up PoE Timer Schedules
- View and Configure the Switch Management Settings
- 3. Configure Switching
- 4. Configuring Routing
- 5. Configure Quality of Service
- 6. Manage Device Security
- Management Security Settings
- Configure Management Access
- Configure Port Authentication
- Set Up Traffic Control
- Configure Access Control Lists
- Use the ACL Wizard to Create a Simple ACL
- Configure a Basic MAC ACL
- Configure MAC ACL Rules
- Configure MAC Bindings
- View or Delete MAC ACL Bindings in the MAC Binding Table
- Configure an IP ACL
- Configure Rules for a Basic IP ACL
- Configure Rules for an Extended IP ACL
- Configure an IPv6 ACL
- Configure Rules for an IPv6 ACL
- Configure IP ACL Interface Bindings
- View or Delete IP ACL Bindings in the IP ACL Binding Table
- Configure VLAN ACL Bindings
- 7. Perform Maintenance Tasks
- 8. Manage Power over Ethernet
- 9. Monitor the System
- A. Configuration Examples
- B. Hardware Specifications and Default Values
Monitor the System
379
Insight Managed 8-Port Gigabit Ethernet Smart Cloud Switch with 2 SFP Fiber Ports
console log. Messages logged to a collector or relay through syslog support the same
format as well.
The following example shows the standard format for a log message:
<14>2017-09-02 16:35:40 10.131.12.183-1 UNKN[2176789276]:
main_login.c(179) 3855 %% HTTP Session 19 initiated for user admin
connected from 10.27.64.122
The number contained in the angle brackets represents the message priority, which is
derived from the following values:
Priority = (facility value × 8) + severity level.
The facility value is usually 1, which means it is a user-level message. Therefore, to
determine the severity level of the message, subtract 8 from the number in the angle
brackets. The sample log message shows a severity level of 6 (informational). For more
information about the severity of a log message, see Manage the Server Log on
page 381.
The message was generated on September 2, 2017, at 5:35:40 p.m. by the switch with
an IP address of 10.131.12.183. The component that generated the message is
unknown, but it came from line 179 of the main_login.c file. This is the 3,855th
message logged since the switch was last booted. The message indicates that the
administrator logged on to the HTTP management interface from a host with an IP
address of 10.27.64.122.
10. To refresh the page with the latest information about the switch, click the Refresh button.
11. To clear the messages from the buffered log in the memory, click the Clear button.
Message Log Format
This topic applies to the format of all logged messages that are displayed for the message
log, persistent log, or console log.
Messages logged to a collector or relay through syslog use an identical format:
• <15>2017-09-02 05:34:05 0.0.0.0-1 MSTP[2110]: mspt_api.c(318)
237%% Interface 12 transitioned to root state on message age timer
expiry.
This example indicates a message with severity 7 (15 mod 8) (debug) on a switch and
generated by component MSTP running in thread ID 2110 on September 2, 2017, at
05:34:05 a.m. by line 318 of file mstp_api.c. This is the 237th message logged with
system IP 0.0.0.0 and task-ID 1.
• <15>2017-09-02 06:24:15 STK0 MSTP[2110]: mspt_api.c(318) 237%%
Interface 12 transitioned to root state on message age timer
expiry.
This example indicates a user-level message (1) with severity 7 (debug) on a system that
is not a chassis and generated by component MSTP running in thread ID 2110 on
September 2, 2017, at 06:24:15 a.m. by line 318 of file mstp_api.c. This is the 237th