Linksys LGS318 User Manual
User Guide
SMART SWITCH
LGS3XX
1
Contents
Chapter 1 – Getting Started ............................................................................... 5
Chapter 2 – System Status ................................................................................. 9
System Summary .................................................................................................................................... 9
RMON ........................................................................................................................................................ 10
Interface Statistics .............................................................................................................................. 17
Chapter 3 – Quick Start ..................................................................................... 19
Chapter 4 – System Management ................................................................. 20
System Information ............................................................................................................................. 20
Management Session Timeout ........................................................................................................ 21
Time ........................................................................................................................................................... 21
SNMP ........................................................................................................................................................ 27
Logs ........................................................................................................................................................... 44
Chapter 5 – Port Management ........................................................................ 50
Ports .......................................................................................................................................................... 50
Link Aggregation ................................................................................................................................... 52
Green Ethernet ...................................................................................................................................... 56
PoE ............................................................................................................................................................. 59
Discovery - LLDP .................................................................................................................................. 65
Chapter 6 – VLAN Management ..................................................................... 77
VLANs ....................................................................................................................................................... 77
Interfaces ................................................................................................................................................ 81
VLAN Memberships ............................................................................................................................. 84
VLAN Groups.......................................................................................................................................... 85
Voice VLAN ............................................................................................................................................. 88
Chapter 7 - Spanning Tree Management .................................................... 93
Spanning Tree ........................................................................................................................................ 94
STP Interfaces ....................................................................................................................................... 96
RSTP Interfaces .................................................................................................................................... 97
2
MSTP Properties ................................................................................................................................... 99
MSTP Instance Status ..................................................................................................................... 102
MSTP Instance Interface ................................................................................................................ 103
Chapter 8 - MAC Address Management .................................................. 106
Dynamic MAC Addresses ............................................................................................................... 106
Static MAC Addresses .................................................................................................................... 107
Reserved MAC Addresses ............................................................................................................. 108
Chapter 9 – Multicast ...................................................................................... 110
Feature Configuration ..................................................................................................................... 112
IGMP Snooping ................................................................................................................................... 114
MLD Snooping .................................................................................................................................... 115
Multicast Router Ports .................................................................................................................... 116
Forward All ........................................................................................................................................... 117
Unregistered Multicast ................................................................................................................... 118
IGMP/MLD IP Group Addresses ................................................................................................... 120
MAC Group Address FDB ............................................................................................................... 121
IP Group Address FDB ..................................................................................................................... 123
Chapter 10 - IP Interface ............................................................................... 125
IPv4 ......................................................................................................................................................... 125
IPv6 ......................................................................................................................................................... 128
Chapter 11 - IP Network Operations .......................................................... 135
Domain Name System ...................................................................................................................... 135
DHCP ...................................................................................................................................................... 136
DHCP Snooping Binding Database ............................................................................................. 141
Interface Settings ............................................................................................................................. 143
Chapter 12 – Security ..................................................................................... 144
Management Security ..................................................................................................................... 144
RADIUS ................................................................................................................................................. 152
Network Access Control ................................................................................................................. 155
Port Security ....................................................................................................................................... 165
Storm Control ..................................................................................................................................... 167
3
Chapter 13 - Access Control List ............................................................... 169
MAC-Based ACL ................................................................................................................................ 170
MAC-Based ACE ................................................................................................................................ 171
IPv4-Based ACL ................................................................................................................................. 173
IPv4-Based ACE................................................................................................................................. 174
IPv6-Based ACL ................................................................................................................................. 176
IPv6-Based ACE................................................................................................................................. 176
ACL Binding ......................................................................................................................................... 178
Chapter 14 - Quality of Service ................................................................... 180
Feature Configuration ..................................................................................................................... 182
Queue Scheduling ............................................................................................................................. 183
CoS/802.1p to Queue ..................................................................................................................... 184
DSCP to Queue ................................................................................................................................... 186
Bandwidth Control ............................................................................................................................ 187
Egress Shaping .................................................................................................................................. 188
Basic QoS ............................................................................................................................................. 189
QoS Statistics .................................................................................................................................... 191
Chapter 15 - Maintenance ............................................................................ 193
Reboot ................................................................................................................................................... 193
File Management ............................................................................................................................... 193
Diagnostics .......................................................................................................................................... 201
Chapter - 16 Support ...................................................................................... 208
4
Chapter 1 – Getting Started
There are two ways to configure the device: through the graphical user interface and through the
menu command line interface.
Starting the Web-based Configuration Utility
This section describes how to navigate the Web-based switch configuration utility. If you are
using a pop-up blocker, make sure it is disabled. The following browsers are supported:
• Firefox (versions 16 and latest)
• IE version (versions 10 and latest)
• Chrome (versions 35 and latest)
Browser Restrictions
If you are using IPv6 interfaces on your management station, use the IPv6 global address and not
the IPv6 link local address to access the device from your browser.
Launching the Configuration Utility
To open the Web-based configuration utility, do the following:
1. Open a Web browser.
2. Enter the IP address of the device you are configuring in the address bar on the browser,
and then press Enter.
NOTE—When the device is using the factory default IP address of 192.168.1.251, its
power LED flashes continuously. When the device is using a DHCP assigned IP address or
an administrator-configured static IP address, the power LED is on solid.
3. On the login page, enter the username/password.
ASCII characters. The default username is “admin” and the default password is “admin”.
The password can contain up to 64
5
Logging Out
By default, the application logs out after ten minutes of inactivity.
CAUTION
Unless the Running Configuration is copied to the Startup Configuration, rebooting the
device will remove all changes made since the last time the file was saved. Save the
Running Configuration to the Startup Configuration before logging off to preserve any
changes you made during this session.
When you click Quick Start > Save Your Configurations, the Configuration File Copy page
appears. Save the Running Configuration file by copying it to the Startup Configuration
file.
To log out, click Logout in the top right corner of any page. The system logs out of the device.
NOTE—When a timeout occurs or you intentionally log out of the system, a message appears,
and the login page appears with a message indicating the logged-out state.
Interface Naming Conventions
Within the GUI, interfaces are denoted by linking the following elements:
•
Type of interface: The following types of interfaces are found on the switch:
o
Gigabit Ethernet ports (displayed as GE).
o
LAG (Port Channel) (displayed as LAG).
o
VLAN
•
Interface Number: Port, LAG or VLAN ID
Window Navigation
This section describes the features of the Web-based switch configuration utility.
Application Header
The Application Header appears on every page. It provides the following application links:
Application Link Name Description
Logout Click to log out of the Web-based switch configuration utility.
Firmware Version Display the device version number.
Help Click for the link to this administration guide.
6
Management Buttons
The following table describes the commonly used buttons that appear on various pages in the
system.
Button Name Description
Add
Apply
Close
Clear All
Clear
Click to display the related Add page and add an entry to a table.
Enter the information and click Apply to save it to the Running
Configuration. Click Close to return to the main page. Click
Save to display the Configuration File Copy page and save the
Running Configuration to the Startup Configuration file type
on the device.
Click to apply changes to the Running Configuration on the
device. If the device is rebooted, the Running Configuration is
lost unless it is saved to the Startup Configuration file type or
another file type. Click Save to display the Configuration File
Copy page and save the Running Configuration to the Startup
Configuration file type on the device.
Click to return to the previous page. Any changes not applied
are cleared.
Click to clear the statistic counters for all interfaces.
Click to clear information, such a counters of an interface, all
interface, or log files.
Delete
Edit
Search
Refresh
Test or Start
View or View All
After selecting an entry in the table, click Delete to remove.
Select the entry and click Edit.
1. Click Apply to save the changes to the Running
Configuration.
2. Click Close to return to the main page.
Enter the query filtering criteria and click Search.
Click Refresh to refresh the counter values.
Click Test/Start to perform the related tests.
Click View to display details associated with the entry
selected or for all entries (respectively).
7
Configuring with Menu Command Line Interface
To configure with the device through the menu CLI:
1. Log on to the device through telnet.
2. Configure the device.
3. Click Logout.
8
Chapter 2 – System Status
System Summary
The System Summary page provides a graphic view of the device, and displays device status,
hardware information, firmware version information, general PoE status, and other items.
To view system information, click System Status > System Summary.
contains system and hardware information.
•
System Mode—Specifies whether the system is operating in Layer 2 system mode.
•
System Description—A description of the system.
•
System Location—Physical location of the device.
System Management > System Information.
•
System Contact—Name of a contact person.
System Management > System Information.
•
Host Name—Name of the device.
word “switch” followed by the three least significant bytes of the device base MAC address
(the six furthest right hexadecimal digits).
•
Base MAC Address—Device MAC address.
•
SNMP Object ID—Unique vendor identification of the network management subsystem.
By default, the device host name is composed of the
To edit this field, go to Configuration >
To edit this field, go to Configuration >
The System Summary page
9
•
Firmware Version—Firmware version number.
•
Boot Code Version—Boot version number.
•
Hardware Version —Hardware version number of the device.
•
Serial Number—Serial number. Device Status
•
Fan Status—Applicable only to models that have fans. The following values are possible:
o
OK—Fan is operating normally.
o
Fail—Fan is not operating correctly.
•
Date & Time—System date and time.
•
System Uptime—Length of time since last reboot.
RMON
RMON Statistics
The Statistics page displays detailed information regarding packet sizes and information
regarding physical layer errors. The information displayed is according to the RMON (Remote
Network Monitoring) standard. An oversized packet is defined as an ethernet frame with the
following criteria:
•
Packet length is greater than MRU byte size.
•
Collision event has not been detected.
•
Late collision event has not been detected.
•
Received (Rx) error event has not been detected.
•
Packet has a valid CRC.
10
To view RMON statistics and/or set the refresh rate:
1. Click System Status > RMON > Statistics.
2. Select the Interface for which statistics are to be displayed.
3. Select the Refresh Rate, the time period that passes before the interface statistics are
refreshed.
The statistics are displayed for the selected interface.
•
Bytes Received—Number of octets received, including bad packets and FCS octets, but
excluding framing bits.
•
Drop Events—Number of packets dropped.
•
Packets Received—Number of good packets received, including Multicast and Broadcast
packets.
•
Broadcast Packets Received—Number of good Broadcast packets received. This number
does not include Multicast packets.
•
Multicast Packets Received—Number of good Multicast packets received.
•
CRC & Align Errors—Number of CRC and Align errors that have occurred.
•
Undersize Packets—Number of undersized packets (less than 64 octets) received.
•
Oversize Packets—Number of oversized packets (over 2000 octets) received.
•
Fragments—Number of fragments (packets with less than 64 octets, excluding framing
bits, but including Frame Check Sequence octets) received.
•
Jabbers—Total number received packets that were longer than 1632 octets. This number
excludes frame bits, but includes FCS octets that had either a bad FCS with an integral
number of octets (FCS Error) or a bad FCS with a non-integral octet (Alignment Error)
number. A jabber packet is defined as an Ethernet frame that satisfies the following
criteria:
•
Packet data length is greater than MRU.
•
Packet has an invalid CRC.
•
Received (Rx) Error Event has not been detected.
•
Collisions—Number of collisions received. If Jumbo Frames are enabled, the threshold of
Jabber Frames is raised to the maximum size of Jumbo Frames.
•
Frames of 64 Bytes—Number of frames, containing 64 bytes that were received.
•
Frames of 65 to 127 Bytes—Number of frames, containing 65-127 bytes that were
received.
•
Frames of 128 to 255 Bytes—Number of frames, containing 128-255 bytes that were
received.
•
Frames of 256 to 511 Bytes—Number of frames, containing 256-511 bytes that were
received.
11
•
Frames of 512 to 1023 Bytes—Number of frames, containing 512-1023 bytes that
were received.
•
Packets of 1024 and More Bytes—Number of frames, containing 1024- 2000 bytes,
and Jumbo Frames, that were received.
To clear or view statistics counters:
•
Click Refresh to refresh the counters on the page.
•
Click Clear to clear the selected interfaces counters.
•
Click View All to see all ports on a single page.
RMON History
The RMON feature enables monitoring statistics per interface.
The History Control Table page defines the sampling frequency, amount of samples to store and
the port from which to gather the data.
After the data is sampled and stored, it appears in the History Table page that can be viewed by
clicking the History button.
To enter RMON control information:
1. Click System Status > RMON > History.
2. Click Add.
3. Enter the parameters.
•
New History Control Entry Index—Displays the number of the new History table
entry.
•
Source Interface—Select the type of interface from which the history samples are
to be taken.
•
Maximum Samples—Enter the number of samples to store.
•
Samples Collected—RMON is allowed by the standard to not grant all requested
samples, but rather to limit the number of samples per request. Therefore, this
field represents the sample number actually granted to the request that is equal or
less than the requested maximum sample.
•
Sampling Interval—Enter the time in seconds that samples are collected from the
ports. The field range is 1-3600.
•
Owner—Enter the RMON station or user that requested the RMON information.
12
4. Click Apply. The entry is added to the History Control Table page, and the Running
Configuration file is updated.
5. Click the History button (described below) to view the actual statistics.
RMON History Table
The History Table page displays interface-specific statistical network samplings. The samples
were configured in the History Control table described above.
To view RMON history statistics:
1. Click System Status > RMON > History.
2. Click History.
3. From the History Entry Index drop down menu, optionally select the entry number of the
sample to display.
The fields are displayed for the selected sample.
•
Owner—History table entry owner.
•
Sample No.—Statistics were taken from this sample.
•
Drop Events—Dropped packets due to lack of network resources during the
sampling interval. This may not represent the exact number of dropped packets,
but rather the number of times dropped packets were detected.
•
Bytes Received—Octets received including bad packets and FCS octets, but
excluding framing bits.
•
Packets Received—Packets received, including bad packets, Multicast, and
Broadcast packets.
•
Broadcast Packets—Good Broadcast packets excluding Multicast packets.
•
Multicast Packets—Good Multicast packets received.
•
CRC Align Errors—CRC and Align errors that have occurred.
•
Undersize Packets—Undersized packets (less than 64 octets) received.
•
Oversize Packets—Oversized packets (over 2000 octets) received.
•
Fragments—Fragments (packets with less than 64 octets) received, excluding
framing bits, but including FCS octets.
13
•
Jabbers—Total number of received packets that were longer than 2000 octets.
This number excludes frame bits, but includes FCS octets that had either a bad
FCS (Frame Check Sequence) with an integral number of octets (FCS Error) or a
bad FCS with a non-integral octet (Alignment Error) number.
•
Collisions—Collisions received.
•
Utilization—Percentage of current interface traffic compared to maximum traffic
that the interface can handle.
RMON Events
You can control the occurrences that trigger an alarm and the type of notification that occurs.
•
Events Page—Configures what happens when an alarm is triggered. This can be any
combination of logs and traps.
•
Alarms Page—Configures the occurrences that trigger an alarm.
To define RMON events:
1. Click System Status > RMON > Events.
This page displays previously defined events.
2. Click Add.
3. Enter the parameters.
•
Event Entry Index —Displays the event entry index number for the new entry.
•
Community—Enter the SNMP community string to be included when traps are sent
(optional). Note that the community must be defined using the Defining SNMPv1
and v2 Notification Recipients or Defining SNMPv3 Notification Recipients pages
for the trap to reach the Network Management Station
•
Description—Enter a name for the event. This name is used in the Add RMON
Alarm page to attach an alarm to an event.
•
Notification Type—Select the type of action that results from this event.
o
None—No action occurs when the alarm goes off.
o
Log (Event Log Table)—Add a log entry to the Event Log table when the
alarm is triggered.
14
o
Trap (SNMP Manager and SYSLOG Server)—Send a trap to the remote log
server when the alarm goes off.
o
Log and Trap—Add a log entry to the Event Log table and send a trap to the
remote log server when the alarm goes off.
•
Last Event Time—Displays the time of the event. (This is a read-only table in the
parent window and cannot be defined).
•
Owner—Enter the device or user that defined the event.
4. Click Apply. The RMON event is saved to the Running Configuration file.
5. Click Event Log to display the log of alarms that have occurred and that have been logged
(see description below).
RMON Events Logs
The Event Log Table page displays the log of events (actions) that occurred. Two types of events
can be logged: Log or Log and Trap. The action in the event is performed when the event is bound
to an alarm (see RMON Alarms
•
Click System Status > RMON > Events.
•
Click Event Log.
) and the conditions of the alarm have occurred.
o
Event Index—Event’s log entry number.
o
Log Index.—Log number (within the event).
o
Log Time—Time that the log entry was entered.
o
Description—Description of event that triggered the alarm.
15
RMON Alarms
RMON alarms provide a mechanism for setting thresholds and sampling intervals to generate
exception events on counters or any other SNMP object counter maintained by the agent. Both
the rising and falling thresholds must be configured in the alarm. After a rising threshold is
crossed, no rising events are generated until the companion falling threshold is crossed. After a
falling alarm is issued, the next alarm is issued when a rising threshold is crossed.
One or more alarms are bound to an event, which indicates the action to be taken when the alarm
occurs.
Alarm counters can be monitored by either absolute values or changes (delta) in the counter
values.
To enter RMON alarms:
1. Click System Status > RMON > Alarms. All previously-defined alarms are displayed. The
fields are described in the Add RMON Alarm page below.
•
Counter Value—Displays the value of the statistic during the last sampling period.
2. Click Add.
3. Enter the parameters.
•
Alarm Entry Index—Displays the alarm entry number.
•
Interface—Select the type of interface for which RMON statistics are displayed.
•
Counter Name—Select the MIB variable that indicates the type of occurrence
measured.
•
Sample Type—Select the sampling method to generate an alarm. The options are:
o
Absolute—If the threshold is crossed, an alarm is generated.
o
Delta—Subtracts the last sampled value from the current value. The
difference in the values is compared to the threshold. If the threshold was
crossed, an alarm is generated.
o
Interval—Enter the alarm interval time in seconds.
•
Rising Event—Select an event to be performed when a rising event is triggered.
Events are created in the Events page.
•
Rising Threshold—Enter the value that triggers the rising threshold alarm
•
Falling Event—Select an event to be performed when a falling event is triggered.
16
•
Falling Threshold—Enter the value that triggers the falling threshold alarm.
•
Startup Alarm—Select the first event from which to start generation of alarms.
Rising is defined by crossing the threshold from a low-value threshold to a highervalue threshold.
o
Rising Alarm—A rising value triggers the rising threshold alarm.
o
Falling Alarm—A falling value triggers the falling threshold alarm.
o
Rising and Falling—Both rising and falling values trigger the alarm.
•
Owner—Enter the name of the user or network management system that receives
the alarm.
4. Click Apply. The RMON alarm is saved to the Running Configuration file.
Interface Statistics
The Interface Statistics page displays traffic statistics per port. The refresh rate of the
information can be selected.
This page is useful for analyzing the amount of traffic that is both sent and received and its
dispersion (Unicast, Multicast, and Broadcast).
17
To display Ethernet statistics and/or set the refresh rate:
1. Click System Status > Interface Statistics.
2. Enter the parameters.
o
Interface—Select the specific interface for which Ethernet statistics are to be
displayed.
o
Refresh Rate—Select the time period that passes before the interface Ethernet
statistics are refreshed. The available options are as follows:
-
No Refresh—Statistics are not refreshed.
-
15 Sec—Statistics are refreshed every 15 seconds.
-
30 Sec—Statistics are refreshed every 30 seconds.
-
60 Sec—Statistics are refreshed every 60 seconds.
o
Total Octets—Octets received, including bad packets and FCS octets, but excluding
framing bits.
o
Unicast Packets—Good Unicast packets received.
o
Multicast Packets—Good Multicast packets received.
o
Broadcast Packets—Good Broadcast packets received.
o
Error Packets—Packets with errors received.
o
Total Octets—Octets transmitted, including bad packets and FCS octets, but
excluding framing bits.
o
Unicast Packets—Good Unicast packets transmitted.
o
Multicast Packets—Good Multicast packets transmitted.
o
Broadcast Packets—Good Broadcast packets transmitted.
To clear or view statistics counters:
•
Click Refresh to refresh the counters on the page.
•
Click Clear to clear the selected interfaces counters.
•
Click View All to see all ports on a single page.
18
Chapter 3 – Quick Start
To simplify device configuration through quick navigation, the Quick Start page provides links to
the most commonly used pages.
Link Name (on the Page) Linked Page
Configure User Accounts and
Management Access
Configure Device IP Address IPv4 Interface
Create VLANs VLANs
Configure VLAN Memberships VLAN Memberships
Save Your Configuration Configuration File Copy
Clicking on the Support link takes you to the device product support page.
User Access & Accounts
19
Chapter 4 – System Management
System Information
To enter system information:
1. Click Configuration > System Management > System Information.
2. View or modify the system settings.
•
System Description—Displays a description of the device.
•
System Location—Enter the location where the device is physically located.
•
System Contact—Enter the name of a contact person.
•
System Host Name—Select the host name of this device.
o
Default—The default host name (System Name) of these switches is
switch123456, where 123456 represents the last three bytes of the
device MAC address in hex format.
o
User Defined—Enter the host name. Use only letters, digits, and hyphens.
Host names cannot begin or end with a hyphen. No other symbols,
punctuation characters, or blank spaces are permitted (as specified in
RFC1033, 1034, 1035).
3. Click Apply to save the values in the Running Configuration file.
20
Management Session Timeout
The Management Session Timeout configures the time intervals that the management sessions
can remain idle before they timeout and you must log in again to reestablish the session.
To set the idle session timeout for various types of sessions:
1. Click Configuration > System Management > Management Session Timeout.
2. Select the timeout for the following sessions from the corresponding list. The default
timeout value is 10 minutes.
•
Telnet Session Timeout—Select the timeout for a Telnet session.
•
HTTP Session Timeout—Select the timeout for an HTTP session.
•
HTTPs Session Timeout—Select the timeout for an HTTPS session.
3. Click Apply to set the configuration settings on the device.
Time
Network time synchronization is critical because every aspect of managing, securing, planning,
and debugging a network involves determining when events occur. Without synchronized clocks,
accurately correlating log files between devices when tracking security breaches or network
usage is impossible.
Synchronized time also reduces confusion in shared file systems, as it is important for the
modification times to be consistent, regardless of the machine on which the file systems reside.
For these reasons, it is important that the time configured on all of the devices on the network is
accurate.
Note—The device supports Simple Network Time Protocol (SNTP) and when enabled, the device
dynamically synchronizes the device time with time from an SNTP server. The device operates
only as an SNTP client, and cannot provide time services to other devices.
21
Clock Source
System time can be set manually by the user, or dynamically from an SNTP server. If an SNTP
server is chosen, the manual time settings are overwritten when communications with the server
are established.
As part of the boot process, the device always configures the time, time zone, and DST. These
parameters are obtained from SNTP, values set manually, or if all else fails, from the factory
defaults.
•
Manual—User must manually set the time.
•
SNTP—Time can be received from SNTP time servers. SNTP ensures accurate network
time synchronization of the device up to the millisecond by using an SNTP server for the
clock source. When specifying an SNTP server, if choosing to identify it by hostname,
three suggestions are given in the GUI:
o
time-a.timefreq.bldrdoc.gov
o
time-b.timefreq.bldrdoc.gov
o
time-c.timefreq.bldrdoc.gov
Note—SNTP is the recommended method for time setting.
SNTP Modes
The device can receive system time from an SNTP server in one of the following ways:
•
Client Broadcast Reception (passive mode)—SNTP servers broadcast the time,
and the device listens to these broadcasts. When the device is in this mode, there
is no need to define a Unicast SNTP server.
•
Client Broadcast Transmission (active mode)—The device, as an SNTP client,
periodically requests SNTP time updates. This mode works in either of the
following ways:
o
SNTP Anycast Client Mode—The device broadcasts time request packets
to all SNTP servers in the subnet, and waits for a response.
o
Unicast SNTP Server Mode—The device sends Unicast queries to a list of
manually-configured SNTP servers, and waits for a response.
The device supports having all of the above modes active at the same time and selects the
best system time received from an SNTP server, according to an algorithm based on the
closest stratum (distance from the reference clock).
Time Zone and Daylight Savings Time (DST)
The Time Zone and DST can be set on the device in the following ways:
•
Dynamic configuration of the device through a DHCP server, where:
•
Dynamic DST, when enabled and available, always takes precedence over the manual
configuration of DST.
22
•
If the server supplying the source parameters fails, or dynamic configuration is disabled
by the user, the manual settings are used.
•
Dynamic configuration of the time zone and DST continues after the IP address lease time
has expired.
•
Manual configuration of the time zone and DST becomes the Operational time zone and
DST, only if the dynamic configuration is disabled or fails.
Note—The DHCP server must supply DHCP option 100 in order for dynamic time zone
configuration to take place.
System Time
Use the System Time page to select the system time source. If the source is manual, you can
enter the time here.
Caution—If the system time is set manually and the device is rebooted, the manual time settings
must be reentered.
To define system time:
1. Click Configuration > System Management > Time > System Time.
The current time is displayed. This shows the DHCP time zone or the acronym for the userdefined time zone if these were defined.
23
2. Enter these parameters:
Clock Source
•
SNTP-If you enable this, the system time is obtained from an SNTP server.
To use this feature, you must also configure a connection to an SNTP server in the
SNTP Unicast Server page.
•
SNTP Client Unicast-Select to enable client Unicast mode.
•
SNTP IPv4 Multicast Rx-Select to receive SNTP IPv4 Multicast synchronization
packets requesting system time information. The packets are transmitted to all
SNTP servers on the subnet.
•
SNTP IPv4 Anycast Tx-Select to transmit SNTP IPv4 Anycast synchronization
packets requesting system time information. The packets are transmitted from
any SNTP servers on the subnet.
•
SNTP IPv6 Multicast Rx-Select to receive SNTP IPv6 Multicast synchronization
packets requesting system time information. The packets are transmitted to all
SNTP servers on the subnet.
•
SNTP IPv6 Anycast Tx-Select to transmit SNTP IPv6 Anycast synchronization
packets requesting system time information. The packets are transmitted from
any SNTP servers on the subnet.
•
Manual Date/Time-Set the date and time manually. The local time is used when
there is no alternate source of time, such as an SNTP server.
Time Zone
•
Time Zone from DHCP-Select to enable dynamic configuration of the time zone
and the DST from the DHCP server. Whether one or both of these parameters can
be configured depends on the information found in the DHCP packet. If this option
is enabled, you must also enable DHCP client on the device. The DHCP Client
supports Option 100 providing dynamic time zone setting.
•
DHCP Time Zone-Displays the acronym of the time zone configured from the
DHCP server. This acronym appears in the Actual Time field.
•
Time Zone Offset-Select the difference in hours between Greenwich Mean Time
(GMT) and the local time. For example, the Time Zone Offset for Paris is GMT +1,
while the Time Zone Offset for New York is GMT - 5.
•
Time Zone Acronym-Enter a user-defined name that represents the time zone you
have configured. This acronym appears in the Actual Time field.
Daylight Savings Time
Select to enable Daylight Saving Time.
•
Time Set Offset-Enter the number of minutes offset from GMT ranging from1-
1440. The default is 60.
24
•
Daylight Savings Type
o
USA - DST is set according to the dates used in the USA.
o
European - DST is set according to the dates used by the European Union
and other countries that use this standard.
o
By Dates - DST is set manually, typically for a country other than the USA
or a European country. This allows customization of the start and stop of
DST.
-
From - Date and time that DST starts.
-
To - Date and time that DST ends.
o
Recurring From / Recurring To) - DST occurs on the same date every year.
This allows customization of the start and stop of DST
-
Day - Day of the week on which DST begins every year.
-
Week - Week within the month from which DST begins every year.
-
Month - Month of the year in which DST begins every year.
-
Time - The time at which DST begins every year.
3. Click Apply. The system time values are written to the Running Configuration file.
SNTP Unicast Server
Up to 16 Unicast SNTP servers can be configured.
Note—To specify a Unicast SNTP server by name, you must first configure DNS server(s) on the
device (see
enabled (in the System Time page).
Domain Name System
). To add a Unicast SNTP server, SNTP Client Unicast must be
25
To add a Unicast SNTP server:
1. Click Configuration > System Management > Time > SNTP Unicast Server.
This page displays the following information for each Unicast SNTP server:
•
SNTP Server—SNTP server IP address. The preferred server, or hostname, is
chosen according to its stratum level.
•
SNTP Server Status—SNTP server status. The possible values are:
-
Up—SNTP server is currently operating normally.
-
Down—SNTP server is currently not available.
-
Unknown—SNTP server is currently being searched for by the device.
-
In Process—Occurs when the SNTP server does not fully trust its own time
server (i.e. when first booting up the SNTP server).
•
Stratum Level—Distance from the reference clock expressed as a numerical value.
An SNTP server cannot be the primary server (stratum level 1) unless polling
interval is enabled.
•
Offset—Estimated offset of the server's clock relative to the local clock, in
milliseconds. The host determines the value of this offset using the algorithm
described in RFC 2030.
•
Delay—Estimated round-trip delay of the server's clock relative to the local clock
over the network path between them, in milliseconds. The host determines the
value of this delay using the algorithm described in RFC 2030.
•
Poll Interval—Displays whether polling is enabled or disabled.
•
Authentication Key ID—Key Identification used to communicate between the
SNTP server and device.
•
Last Response Time—Last date and time a response was received from this SNTP
server.
2. To add a Unicast SNTP server, enable SNTP Client Unicast.
3. Click Add.
4. Enter the following parameters:
•
SNTP Server—Select if the SNTP server is going to be identified by its IP address
or if you are going to select a well-known SNTP server by name from the list.
Note—To specify a well-known SNTP server, the device must be connected to the
internet and configured with a DNS server or configured so that a DNS server is
identified by using DHCP. (See
•
IP Version—Select the version of the IP address: Version 6 or Version 4.
•
IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The options are
Domain Name System
in Chapter 11.)
26
•
Link Local—The IPv6 address uniquely identifies hosts on a single network link. A
link local address has a prefix of FE80, is not routable, and can be used for
communication only on the local network. Only one link local address is supported.
If a link local address exists on the interface, this entry replaces the address in the
configuration.
•
Link Local Interface—Select the link local interface (if IPv6 AddressType Link
Local is selected) from the list.
•
Global—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
•
SNTP Server IP Address—Enter the SNTP server IP address. The format depends
on which address type was selected.
•
SNTP Server Name—Select the name of the SNTP server from a list of well-known
NTP servers. If other is chosen, enter the name of an SNTP server in the adjacent
field.
•
Poll Interval—Select to enable polling of the SNTP server for system time
information. All NTP servers that are registered for polling are polled, and the clock
is selected from the server with the lowest stratum level (distance from the
reference clock) that is reachable. The server with the lowest stratum is
considered to be the primary server. The server with the next lowest stratum is a
secondary server, and so forth. If the primary server is down, the device polls all
servers with the polling setting enabled, and selects a new primary server with the
lowest stratum.
5. Click Apply. The STNP server is added, and you are returned to the main page.
SNMP
This section describes the Simple Network Management Protocol (SNMP) feature that provides a
method for managing network devices.
SNMP Versions
The device functions as an SNMP agent and supports SNMPv1, v2, and v3. It also reports system
events to trap receivers using the traps defined in the supported MIBs (Management Information
Base).
•
SNMPv1 and v2
To control access to the system, a list of community entries is defined. Each community
entry consists of a community string and its access privilege. The system responds only to
SNMP messages specifying the community which has the correct permissions and correct
operation.
SNMP agents maintain a list of variables that are used to manage the device. These
variables are defined in the Management Information Base (MIB).
27
Note—Due to the security vulnerabilities of other versions, it is recommended to use
SNMPv3.
•
SNMPv3
In addition to the functionality provided by SNMPv1 and v2, SNMPv3 applies access
control and new trap mechanisms to SNMPv1 and SNMPv2 PDUs. SNMPv3 also defines a
User Security Model (USM) that includes:
o
Authentication—Provides data integrity and data origin authentication.
o
Privacy—Protects against disclosure message content. Cipher Block- Chaining
(CBC-DES) is used for encryption. Either authentication alone can be enabled on an
SNMP message, or both authentication and privacy can be enabled on an SNMP
message. However, privacy cannot be enabled without authentication.
o
Timeliness—Protects against message delay or playback attacks. The SNMP
agent compares the incoming message time stamp to the message arrival time.
SNMP Workflow
Note—For security reasons, SNMP is disabled by default. Before you can manage the device via
SNMP, you must turn on SNMP in the SNMP > Feature Configuration page.
If you decide to use SNMPv1 or v2:
1. Navigate to the SNMP -> Communities page and click Add. The community can be
associated with access rights and a view in Basic mode or with a group in Advanced mode.
There are two ways to define access rights of a community:
•
Basic mode—The access rights of a community can configure with Read Only,
Read Write, or SNMP Admin. In addition, you can restrict the access to the
community to only certain MIB objects by selecting a view (defined in the Views
page).
•
Advanced Mode—The access rights of a community are defined by a group
(defined in the Groups page). You can configure the group with a specific security
model. The access rights of a group are Read, Write, and Notify.
2. Choose whether to restrict the SNMP management station to one address or allow SNMP
management from all addresses. If you choose to restrict SNMP management to one
address, then input the address of your SNMP Management PC in the IP Address field.
3. Input the unique community string in the Community String field.
4. Optionally, enable traps by using the Trap Settings page.
5. Optionally, define a notification filter(s) by using the Notification Filter page.
6. Configure the notification recipients on the Notification Recipients SNMPv1, v2 page.
28
If you decide to use SNMPv3:
1. Define the SNMP engine by using the Engine ID page. Either create a unique Engine ID or
use the default Engine ID. Applying an Engine ID configuration clears the SNMP database.
2. Optionally, define SNMP view(s) by using the Views page. This limits the range of Object
IDs available to a community or group.
3. Define groups by using the Groups page.
4. Define users by using the SNMP Users page, where they can be associated with a group. If
the SNMP Engine ID is not set, then users may not be created.
5. Optionally, enable or disable traps by using the Trap Settings page.
29
6. Optionally, define a notification filter(s) by using the Notification Filter page.
7. Define a notification recipient(s) by using the Notification Recipients SNMPv3 page.
Device Model Object IDs (OIDs):
Mode Name Description Object ID
LGS308
LGS318
LGS326
LGS308P
LGS318P
LGS326P
Private OIDs are placed under: enterprises(1).linksys(3955).smb(1000).switch01(201).
8-Port Smart Gigabit Switch enterprises(1) . linksys(3955) .
smb(1000).3.8.1
18-Port Smart Gigabit Switch
26-Port Smart Gigabit Switch
8-Port Smart Gigabit PoE+ Switch
18-Port Smart Gigabit PoE+ Switch
26-Port Smart Gigabit PoE+ Switch
enterprises(1) . linksys(3955) .
smb(1000).3.18.1
enterprises(1) . linksys(3955) .
smb(1000).3.26.1
enterprises(1) . linksys(3955) .
smb(1000).3.8.2
enterprises(1) . linksys(3955) .
smb(1000).3.18.2
enterprises(1) . linksys(3955) .
smb(1000).3.26.
30
Loading...