Linksys LGS308P Bruksanvisning

Linksys Växla LGS308P

Läs gratis den bruksanvisning för Linksys LGS308P (110 sidor) i kategorin Växla. Guiden har ansetts hjälpsam av 8 personer och har ett genomsnittsbetyg på 4.8 stjärnor baserat på 4.5 recensioner. Har du en fråga om Linksys LGS308P eller vill du ställa frågor till andra användare av produkten? Ställ en fråga

Ladda ner PDF

Sida 1/110

Smart Switch LGS3XX

User Guide

Table of ContentsLinksys

Chapter 1: Getting Started 1 . . . . . . . . . . . . . . . . . . . . .

Starting the Web-based Conﬁguration Utility . . . . . . . . . . . .1

Launching the Conﬁguration Utility . . . . . . . . . . . . . . . . .1

Interface Naming Conventions . . . . . . . . . . . . . . . . . . . . . .2

Window Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Conﬁguring with Menu Command line Interface . . . . . . . . . .3

Chapter 2: System Status . . . . . . . . . . . . . . . . . . . . . . 4

System Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

RMON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

RMON Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

RMON History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

RMON Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

RMON Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Chapter 3: Quick Start . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 4: System Management. . . . . . . . . . . . . . . . . .10

System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Management Session Timeout . . . . . . . . . . . . . . . . . . . . . 10

Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

SNTP Unicast Server . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

SNMP Versions and Workﬂow . . . . . . . . . . . . . . . . . . . . 14

Feature Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . 15

Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Communities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Notiﬁcation Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

SNMPv1/v2 Notiﬁcation Recipients. . . . . . . . . . . . . . . . . 20

SNMPv3 Notiﬁcation Recipients . . . . . . . . . . . . . . . . . . . 21

Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Log Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Remote Log Servers . . . . . . . . . . . . . . . . . . . . . . . . . . 23

RAM Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Flash Memory Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 5: Port Management . . . . . . . . . . . . . . . . . . .24

Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

LAG Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Green Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

PoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Feature Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . 31

Port Limit Power Mode . . . . . . . . . . . . . . . . . . . . . . . . 31

Class Limit Power Mode . . . . . . . . . . . . . . . . . . . . . . . . 31

LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table of Contents

Table of ContentsLinksys

Feature Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . 33

LLDP MED Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

LLDP Local Information . . . . . . . . . . . . . . . . . . . . . . . . 35

LLDP Neighbor Information . . . . . . . . . . . . . . . . . . . . . 36

LLDP MED Network Policy . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 6: VLAN Management. . . . . . . . . . . . . . . . . . .39

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

VLANs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

VLAN Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

MAC-Based Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

MAC-Based VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Voice VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Feature Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . 45

Telephony OUI Interfaces . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 7: Spanning Tree Management . . . . . . . . . . . . .47

Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

STP Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

RSTP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

MSTP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

MSTP Instance Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

MSTP Instance Interface . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 8: MAC Address Management. . . . . . . . . . . . . .53

Dynamic MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . 53

Static MAC Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Reserved MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 9: Multicast . . . . . . . . . . . . . . . . . . . . . . . . .55

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Feature Conﬁguration 56 . . . . . . . . . . . . . . . . . . . . . . . . . .

IGMP/MLD Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Multicast Router Ports . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Forward All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Unregistered Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . 59

IGMP/MLD IP Group Addresses. . . . . . . . . . . . . . . . . . . . . 59

MAC Group Address FDB. . . . . . . . . . . . . . . . . . . . . . . . . 60

IP Group Address FDB . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 10: IP Interface . . . . . . . . . . . . . . . . . . . . . . .62

IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

IPv4 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

IPv6 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

IPv6 Interface Addresses . . . . . . . . . . . . . . . . . . . . . . . 64

IPv6 Default Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 65

IPv6 Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

IPv6 Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 11: IP Network Operations. . . . . . . . . . . . . . . .67

Domain Name System . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DHCP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

DHCP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Trusted Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

DHCP Snooping Binding Database . . . . . . . . . . . . . . . . . . 70

iii

Table of ContentsLinksys

Interface Settings 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 12: Security . . . . . . . . . . . . . . . . . . . . . . . . .72

Management Security . . . . . . . . . . . . . . . . . . . . . . . . . . 72

User Access & Accounts . . . . . . . . . . . . . . . . . . . . . . . . 72

Access Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 72

Access Proﬁle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Access Proﬁle Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Network Access Control . . . . . . . . . . . . . . . . . . . . . . . . . 77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Multiple Authentication Methods . . . . . . . . . . . . . . . . . 78

Dynamic VLAN Assignment . . . . . . . . . . . . . . . . . . . . . 80

Feature Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . 80

Port Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Authenticated Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Storm Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 13: Access Control List . . . . . . . . . . . . . . . . . .86

MAC-Based ACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

MAC-Based ACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

IPv4-Based ACL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

IPv4-Based ACE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

IPv6-Based ACL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

IPv6-Based ACE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

ACL Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 14: Quality of Service . . . . . . . . . . . . . . . . . . .91

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Feature Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Queue Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

CoS/802.1p to Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

DSCP to Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Bandwidth Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Egress Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Basic QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

QoS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 15: Maintenance . . . . . . . . . . . . . . . . . . . . . .97

Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Firmware & Boot Code . . . . . . . . . . . . . . . . . . . . . . . . . 99

Active Firmware Image . . . . . . . . . . . . . . . . . . . . . . . 100

Conﬁguration & Log . . . . . . . . . . . . . . . . . . . . . . . . . 100

Conﬁguration File Copy . . . . . . . . . . . . . . . . . . . . . . . 101

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Copper Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Optical Module Status . . . . . . . . . . . . . . . . . . . . . . . . 102

Ping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 16: Support . . . . . . . . . . . . . . . . . . . . . . . . 105

Table of ContentsLinksys

CHAPTER 1 Getting Started

Getting Started

This section provides an introduction to the Web-based configuration utility,

and covers the following topics:

•Starting the Web-based Configuration Utility

•Interface Naming Conventions

•Window Navigation

•Configuring with Menu Command Line Interface

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 9, 10)

•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:

STEP 1 Open a Web browser.

STEP 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.

Logging In

The default username is and the default password is to log in to admin admin

the Web-based GUI:

STEP 1 Open the GUI. The Login page is displayed.

STEP 2 Enter the username/password. The password can contain up to 64

ASCII characters.

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.

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.

Table of ContentsLinksys

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:

•Gigabit Ethernet ports (displayed as GE).

•LAG (Port Channel) (displayed as LAG).

•VLAN (displayed as 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.

Management Buttons

The following table describes the commonly used buttons that appear on

various pages in the system.

Button Name Description

Add 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.

Apply 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.

Button Name Description

Close Click to return to the previous page. Any changes not

applied are cleared.

Clear All Click to clear the statistic counters for all interfaces.

Clear Click to clear information, such a counters of an interface

or all interface, or log files.

Delete After selecting an entry in the table, click Delete to

remove.

Edit Select the entry and click Edit. The Edit page appears, and

the entry can be modified.

1. Click Apply to save the changes to the Running

Configuration.

2. Click Close to return to the main page.

Search Enter the query filtering criteria and click Search. The

results are displayed on the page.

Refresh Click Refresh to refresh the counter values.

Test or Start Click Test/Start to perform the related tests.

View or View All Click View to display details associated with the entry

selected or for all entries (respectively).

Table of ContentsLinksys

Configuring with Menu Command Line

Interface

To configure the device through the menu CLI, do the following:

1. Log on to the device through telnet.

The following menu is displayed:

2. Enter your user name and password.

The main menu is displayed:

3. Continue configuring the device.

4. Click Logout to log out of the CLI menu.

Table of ContentsLinksys

CHAPTER 2 System Status

System Status

This section describes how to view device statistics. It covers the following

topics:

•System Summary

•RMON

•Interface Statistics

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. The

System Summary page 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. Click Edit to go the

System Information page to enter this value.

•System Contact—Name of a contact person. Click Edit to go the System

Information page to enter this value.

•Host Name—Name of the device. By default, the device host name is

composed of the 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.

•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:

•OK—Fan is operating normally.

•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.

To view RMON statistics and/or set the refresh rate, do the following:

STEP 1 Click System Status > RMON > Statistics.

STEP 2 Select the Interface for which statistics are to be displayed.

STEP 3 Select the Refresh Rate, the time period that passes before the

interface statistics are refreshed.

The statistics are displayed for the selected interface.

Table of ContentsLinksys

•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.

•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, do the following:

•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:

STEP 1 Click System Status > RMON > History.

STEP 2 Click Add.

STEP 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.

Table of ContentsLinksys

STEP 4 Click Apply. The entry is added to the History Control Table page, and

the Running Configuration file is updated.

STEP 5 Click the History button (described below) to view the actual

statistics.

RMON History

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:

STEP 1 Click System Status > RMON > History.

STEP 2 Click History.

STEP 3 From the History Control Entry Index No. 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 Index—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.

•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 Event

You can control the occurrences that trigger an alarm and the type of

notification that occurs. This is performed as follows:

•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:

STEP 1 Click System Status > RMON > Events.

This page displays previously defined events.

STEP 2 Click Add.

STEP 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,2 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.

Values are:

•None—No action occurs when the alarm goes off.

•Event Log (Event Log Table)—Add a log entry to the Event Log table

when the alarm is triggered.

•Trap (SNMP Manager and SYSLOG Server)—Send a trap to the

remote log server when the alarm goes off.

Table of ContentsLinksys

•Trap and Event Log—Add a log entry to the Event Log table and send

a trap to the remote log server when the alarm goes off.

•Owner—Enter the device or user that defined the event.

•Last Event Time—Displays the time of the event. (This is a read-only table

in the parent window and cannot be defined).

STEP 4 Click Apply. The RMON event is saved to the Running Configuration

file.

STEP 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 the Alarms

page) and the conditions of the alarm have occurred.

STEP 1 Click System Status > RMON > Events.

STEP 2 Click Event Log.

This page displays the following fields:

•Event Entry No.—Event’s log entry number.

•Log No.—Log number (within the event).

•Log Time—Time that the log entry was entered.

•Description—Description of event that triggered the alarm.

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:

STEP 1 Click System Status > RMON > Alarms. All previously-defined alarms

are displayed. The fields are described in the Add RMON Alarm page

below. In addition to those fields, the following field appears:

•Counter Value—Displays the value of the statistic during the last

sampling period.

STEP 2 Click Add.

STEP 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:

•Absolute—If the threshold is crossed, an alarm is generated.

•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.

•Interval—Enter the alarm interval time in seconds.

•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 higher-value threshold.

•Rising Alarm—A rising value triggers the rising threshold alarm.

•Falling Alarm—A falling value triggers the falling threshold alarm.

•Rising and Falling Alarm—Both rising and falling values trigger

the alarm.

•Owner—Enter the name of the user or network management system that

receives the alarm.

•Rising Threshold—Enter the value that triggers the rising threshold alarm.

•Rising Event—Select an event to be performed when a rising event is

triggered. Events are created in the Events page.

•Falling Threshold—Enter the value that triggers the falling threshold alarm.

Table of ContentsLinksys

•Falling Event—Select an event to be performed when a falling event

is triggered.

STEP 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).

To display Ethernet statistics and/or set the refresh rate, do the following:

STEP 1 Click System Status > Interface Statistics.

STEP 2 Enter the parameters.

Interface Statistics

•Interface—Select the specific interface for which Ethernet statistics are to

be displayed.

•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.

The Receive Statistics area displays information about incoming packets.

•Unicast Packets—Good Unicast packets received.

•Multicast Packets—Good Multicast packets received.

•Broadcast Packets—Good Broadcast packets received.

•Error Packets—Packets with errors received.

The Transmit Statistics area displays information about outgoing packets.

•Total Octets—Octets transmitted, including bad packets and FCS octets,

but excluding framing bits.

•Unicast Packets—Good Unicast packets transmitted.

•Multicast Packets—Good Multicast packets transmitted.

•Broadcast Packets—Good Broadcast packets transmitted.

•To clear or view statistics counters, do the following:

•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.

Table of ContentsLinksys

Chapter 3 Quick Start

Quick Start

This section describes how to view device statistics.

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

User Access & Accounts

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.

Table of ContentsLinksys

Chapter 4 System Management

This chapter describes the following topics:

•System Information

•Management Session Timeout

•Time

•SNMP

•Logs

System Information

To enter system information, do the following:

STEP 1 Click Configuration > System Management > System Information.

STEP 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.

•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.

•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).

STEP 3 Click Apply to save the values in the Running Configuration file.

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:

STEP 1 Click Configuration > System Management > Management Session

Timeout.

STEP 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.

STEP 3 Click Apply to set the configuration settings on the device.

Time

This section describes the options for configuring the system time, time zone,

and Daylight Savings Time (DST). It covers the following topics:

•Overview

•System Time

•SNTP Unicast Server

Overview

Synchronized system clocks provide a frame of reference between all devices

on the network. 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.

Table of ContentsLinksys

System Time

System time can be set manually by the user 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.

Time

The following methods are available for setting the system time on the device:

•Manual—You 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 host name, three suggestions are given

in the GUI:

•time-a.timefreq.bldrdoc.gov

•time-b.timefreq.bldrdoc.gov

•time-c.timefreq.bldrdoc.gov

NOTE:

SNTP is the recommended method for time setting.

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.

•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.

SNTP Modes

The device can receive the 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:

•SNTP Anycast Client Mode—The device broadcasts time request

packets to all SNTP servers in the subnet, and waits for a response.

•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).

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, do the following:

STEP 1 Click Configuration > System Management > Time > System Time.

The current time on the device is displayed. This shows the DHCP time zone or

the acronym for the user-defined time zone if these were defined.

STEP 2 Enter these parameters:

Table of ContentsLinksys

•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 from any 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 to all 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 from any 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 to all 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—The local time is used via the DHCP server or Time Zone offset.

Time Zone-The local time is used via the DHCP server or Time Zone offset .

•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 how DST is defined:

•Daylight Savings—Select to enable Daylight Saving Time.

•Time Set Offset—Enter the number of minutes offset from GMT ranging

from1—1440. The default is 60.

•Daylight Savings Type—Click one of the following:

•USA—DST is set according to the dates used in the USA.

•European—DST is set according to the dates used by the European

Union and other countries that use this standard.

•By Dates—DST is set manually, typically for a country other than the

USA or a European country. Enter the following parameters:

•Recurring - DST occurs on the same date every year . This allows

customization of the start and stop of DST

•For Daylight Savings Time, enter the following parameters:

•From—Day and time that DST starts.

•To—Day and time that DST ends.

•Recurring From, enter the following parameters that indicate when DST

begins each year:

•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.

•(Recurring) To - Enter the following parameters that indicate when DST

ends each year:

•Day—Day of the week on which DST ends every year.

•Week—Week within the month from which DST ends every year.

•Month—Month of the year in which DST ends every year.

•Time—The time at which DST ends every year.

STEP 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.

Table of ContentsLinksys

NOTE:

To specify a Unicast SNTP server by name, you must first configure DNS

server(s) on the device (see DNS Settings). To add a Unicast SNTP server,

SNTP Client Unicast must be enabled.

To add a Unicast SNTP server:

STEP 1 Click Configuration > Time > SNTP Unicast Server.

This page displays the following information for each configured Unicast

SNTP server:

•SNTP Server—SNTP server IP address. The preferred server, or host name,

is chosen according to its stratum level.

•SNTP Server Status—SNTP server status. The possible values are as follows:

•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 has not fully trusted 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—The 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—The 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.

•Last Response Time—Date and time of the last time a response was

received from this SNTP server.

STEP 2 To add a Unicast SNTP server, enable SNTP Client Unicast.

STEP 3 Click Add.

STEP 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 DNS Settings)

•IP Version—Select the version of the IP address: Version 4 or Version 6.

•IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The

options are

•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 Address

•Type 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 name of 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.

STEP 5 Click Apply. The STNP server is added, and you are returned to the

main page.

Table of ContentsLinksys

SNMP

This section describes the Simple Network Management Protocol (SNMP)

feature that provides a method for managing network devices.

It covers the following topics:

•SNMP Versions and Workflow

•Model OID

•Feature Configuration

•Views

•Groups

•Users

•Communities

•Notification Filters

•V1/V2 Notification Recipients

•V3 Notification Recipients

SNMP Versions and Workflow

The device functions as 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).

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:

•Authentication—Provides data integrity and data origin authentication.

•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.

•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.

The following is the recommended series of actions for configuring SNMP:

If you decide to use SNMPv1 or v2:

STEP 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.

STEP 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.

Table of ContentsLinksys

STEP 3 Input the unique community string in the Community String field.

STEP 4 Optionally, define a notification filter(s) by using the Notification

Filter page.

STEP 5 Configure the notification recipients on the Notification Recipients

SNMPv1,2 page.

If you decide to use SNMPv3:

STEP 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.

STEP 2 Optionally, define SNMP view(s) by using the Views page. This limits

the range of OIDs available to a community or group.

STEP 3 Define groups by using the Groups page.

STEP 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.

STEP 5 Optionally, define a notification filter(s) by using the Notification

Filter page.

STEP 6 Define a notification recipient(s) by using the Notification Recipients

SNMPv3 page.

Model OIDs

The following are the device model Object IDs (OIDs):

Mode Name Description Object ID

LGS308 8-Port Smart Gigabit Switch enterprises(1) .linksys(3955).

smb(1000).3.8.1

LGS318 18-PortSmartGigabit Switch enterprises(1).linksys(3955).

smb(1000).3.18.1

LGS326 24-Port Smart Gigabit Switch enterprises(1).linksys(3955).

smb(1000).3.26.1

LGS308P 8-Port Smart Gigabit PoE Switch enterprises(1).linksys(3955).

smb(1000).3.8.2

LGS318P 16-Port Smart Gigabit PoE Switch enterprises(1).linksys(3955).

smb(1000).3.18.2

LGS326P 24-Port Smart Gigabit PoE Switch enterprises(1).linksys(3955).

smb(1000).3.26.2

The private Object IDs are placed under:

enterprises(1).linksys(3955).smb(1000).switch01(201).

Feature Configuration

The Engine ID is used by SNMPv3 entities to uniquely identify them. An SNMP

agent is considered an authoritative SNMP engine. This means that the agent

responds to incoming messages (Get, GetNext, GetBulk, Set) and sends trap

messages to a manager. The agent’s local information is encapsulated in fields

in the message.

Each SNMP agent maintains local information that is used in SNMPv3 message

exchanges. The default SNMP Engine ID is comprised of the enterprise

number and the default MAC address. This engine ID must be unique for the

administrative domain, so that no two devices in a network have the same

engine ID.

Local information is stored in four MIB variables that are read-only

(snmpEngineId, snmpEngineBoots, snmpEngineTime, and

snmpEngineMaxMessageSize).

CAUTION:

When the engine ID is changed, all configured users and groups are erased.

To configure SNMP:

STEP 1 Click Configuration > System Management > Feature Configuration.

STEP 2 Enter the following fields:

•SNMP—Select to enable SNMP.

•Authentication Notification—Select to enable SNMP authentication

failure notification.

•SNMP Notification—Select to enable SNMP notifications.

•Local SNMPv3 Engine ID—Configure the engine. The options are:

•Use Default—Select to use the device-generated engine ID. The

default engine ID is based on the device MAC address, and is defined

per standard as:

Table of ContentsLinksys

•First 4 octets—First bit = 1, the rest is the IANA enterprise number.

•Fifth octet—Set to 3 to indicate the MAC address that follows.

•Last 6 octets—MAC address of the device.

•None—No engine ID is used.

•User Defined—Enter the local device engine ID. The field value is a

hexadecimal string (range: 10 - 64). Each byte in the hexadecimal

character strings is represented by two hexadecimal digits.

All remote engine IDs and their IP addresses are displayed in the Remote

Engine ID table.

STEP 3 Click Apply. The Running Configuration file is updated.

The Remote Engine ID table shows the mapping between IP addresses of the

engine and Engine ID. To add the IP address of an engine ID:

STEP 4 Click Add. Enter the following fields:

•Remote Engine Host Address—Select whether to specify the Engine ID

server by IP address or name.

•IP Version—Select the supported IP format.

•IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The

options are:

•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.

•Global—The IPv6 address is a global Unicast IPV6 type that is visible

and reachable from other networks.

•Remote Engine IP Address—Enter the IP address of the log server.

•Remote Engine IP Host—Enter the domain name of the log server.

•Engine ID—Enter the Engine ID.

STEP 5 Click Apply. The Running Configuration file is updated.

Views

A view is a user-defined label for a collection of MIB subtrees. Each subtree ID

is defined by the Object ID (OID) of the root of the relevant subtrees. Either

well- known names can be used to specify the root of the desired subtree or

an OID can be entered (see Model OIDs).

Each subtree is either included or excluded in the view being defined.

The Views page enables creating and editing SNMP views. The default views

(Default, DefaultSuper) cannot be changed.

Views can be attached to groups in the Groups page or to a community which

employs basic access mode through the Communities page.

To define SNMP views:

STEP 1 Click Configuration > System Management > SNMP > Views.

STEP 2 Click Add to define new views.

STEP 3 Enter the parameters.

•VIew Name—Enter a view name between 0-30 characters)

•View Object—Select the node in the MIB tree that is included or excluded

in the selected SNMP view. The options to select the object are as follows:

•Object ID—Enter an OID not offered in the Object ID Selection List option.

•Object ID Selection List—Enables you to navigate the MIB tree. Press the

Up arrow to go to the level of the selected node’s parent and siblings;

press the Down arrow to descend to the level of the selected node’s

children. Click nodes in the view to pass from one node to its sibling. Use

the scrollbar to bring siblings in view.

STEP 4 Include or exclude the MIB object from the view. If Include Object

is selected, the MIB objects are included in the view, otherwise they

are excluded.

STEP 5 Click Apply.

STEP 6 In order to verify your view configuration, select the user-defined views

from the Filter: View Name list. The following views exist by default:

•Default—Default SNMP view for read and read/write views.

•DefaultSuper—Default SNMP view for administrator views.

Other views can be added.

•Object ID—Displays the Object ID and its subtree to be included or

excluded in the SNMP view.

•Object View—Displays whether the defined object and its subtree are

included or excluded in the selected SNMP view.

Table of ContentsLinksys

Groups

•In SNMPv1 and SNMPv2, a community string is sent along with the SNMP

frames. The community string acts as a password to gain access to an

SNMP agent. However, neither the frames nor the community string are

encrypted. Therefore, SNMPv1 and SNMPv2 are not secure.

•In SNMPv3, the following security mechanisms can be configured.

•Authentication—The device checks that the SNMP user is an authorized

system administrator. This is done for each frame.

•Privacy—SNMP frames can carry encrypted data.

Thus, in SNMPv3, there are three levels of security:

•No security (No authentication and no privacy)

•Authentication (Authentication and no privacy)

•Authentication and privacy

SNMPv3 provides a means of controlling the content each user can read or

write and the notifications they receive. A group defines read/write privileges

and a level of security. It becomes operational when it is associated with an

SNMP user or community.

NOTE:

To associate a non-default view with a group, first create the view in the

Views page.

To create an SNMP group:

STEP 1 Click Configuration > System Management > SNMP> Groups.

•This page displays the existing SNMP groups and their security levels. The

following fields are displayed for each SNMP group (only the fields not

explained in the Add page):

•No Authentication Read View—No authentication is needed, and anyone

is able to read the view.

•No Authentication Write View—No authentication is needed, and anyone

is able to write the view.

•No Authentication Notify View—No authentication is needed, and

anyone is able to receive notification of the view.

•Authentication Read View—Only authenticated users are allowed to read

the view. By default, all users or community of a group can access all the

MIB objects. A group can be limited to specific view(s) based on the read,

write, notify, authentication and/or privacy configurations.

•Authentication Write View—Only authenticated users are able to write

the view.

•Management access is write for the selected view.

•Authentication Notify View—Only authentication users are allowed

toreceived notification.

•Privacy Read View— When reading the objects in the view, the SNMP

messages are encrypted.

•Privacy Write View—When writing the object in the view, the SNMP

messages are encrypted.

•Privacy Notify View—Notification on the objects in the view are encrypted.

STEP 2 Click Add.

STEP 3 Enter the parameters.

•Group Name—Enter a new group name.

•Security Model—Select the SNMP version attached to the group,

SNMPv1, v2, or v3.

•Three types of views with various security levels can be defined. For each

security level, select the views for Read, Write and Notify by entering the

following fields:

•Enable—Select this field to enable the Security Level.

•Security Model—Define the security level attached to the group. SNMPv1

and SNMPv2 support neither authentication nor privacy. If SNMPv3 is

selected, select to enable one of the following:

•No Authentication and No Privacy—Neither the Authentication nor the

Privacy security levels are assigned to the group.

•Authorized View—Select the Read, Write and Notify views associated with

this group and with the above security level.

•Authentication and No Privacy—Authenticates SNMP messages, and ensures

the SNMP message origin is authenticated but does not encrypt them.

•Authorized View—Select the Read, Write and Notify views associated with

this group and with the above security level.

Table of ContentsLinksys

•Authentication and Privacy—Authenticates SNMP messages, and

encrypts them.

•Authorized View—Select the Read, Write and Notify views associated with

this group and with the above security level.

STEP 4 Click Apply. The SNMP group is saved to the Running Configuration file.

Users

An SNMP user is defined by the login credentials (username, passwords, and

authentication method) and by the context and scope in which it operates by

association with a group and an Engine ID.

The configured user has the attributes of its group, having the access

privileges configured within the associated view.

Groups enable network managers to assign access rights to a group of users

instead of to a single user.

A user can only belong to a single group.

•To create an SNMPv3 user, the following must first exist:

•An engine ID must first be configured on the device. This is done in

the Engine ID page.

•An SNMPv3 group must be available. An SNMPv3 group is defined in

the Groups page.

To display SNMP users and define new ones:

STEP 1 Click Configuration > System Management > SNMP > Users.

This page contains existing users.

STEP 2 Click Add.

This page provides information for assigning SNMP access control privileges

to SNMP users.

STEP 3 Enter the parameters.

•User Name—Enter a name for the user.

•Engine ID—Select either the local or remote SNMP entity to which the

user is connected. Changing or removing the local SNMP Engine ID

deletes the SNMPv3 User Database. To receive inform messages and

request information, you must define both a local and remote user.

•Local—User is connected to the local device.

•Engine—User is connected to a different SNMP entity besides the

local device. If the remote Engine ID is defined, remote devices

receive inform messages, but cannot make requests for information.

•Select the remote engine ID.

•Group Name—Select the SNMP group to which the SNMP user belongs.

SNMP groups are defined in the Add Group page.

NOTE Users, who belong to groups which have been deleted, remain, but

they are inactive.

•Authentication Method—Select the Authentication method that varies

according to the Group Name assigned. If the group does not require

authentication, then the user cannot configure any authentication. The

options are:

•None—No user authentication is used.

•MD5—A password that is used for generating a key by the MD5

authentication method.

•SHA—A password that is used for generating a key by the SHA

(Secure Hash Algorithm) authentication method.

•Authentication Password—If authentication is accomplished by either

a MD5 or a SHA password, enter the local user password in either

Encrypted or Plaintext. Local user passwords are compared to the local

database, and can contain up to 32 ASCII characters.

•Privacy Method—Select one of the following options:

•None—Privacy password is not encrypted.

•DES—Privacy password is encrypted according to the Data Encryption

Standard (DES).

•Privacy Password—16 bytes are required (DES encryption key) if the DES

privacy method was selected. This field must be exactly 32 hexadecimal

characters. The Encrypted or Plaintext mode can be selected.

STEP 4 Click Apply to save the settings.

Communities

Access rights in SNMPv1 and SNMPv2 are managed by defining communities

in the Communities page. The community name is a type of shared password

between the SNMP management station and the device. It is used to

authenticate the SNMP management station.

Table of ContentsLinksys

Communities are only defined in SNMPv1 and v2 because SNMPv3 works with

users instead of communities. The users belong to groups that have access

rights assigned to them.

The Communities page associates communities with access rights, either

directly (Basic mode) or through groups (Advanced mode):

•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 SNMP 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.

To define SNMP communities:

STEP 1 Click Configuration > System Management > SNMP> Communities.

•This page contains a table of configured SNMP communities and their

properties.

STEP 2 Click Add.

•This page enables network managers to define and configure new

SNMP communities.

STEP 3 Enter the following fields:

•SNMP Management Station—Click User Defined to enter the

management station IP address that can access the SNMP community.

Click All to indicate that any IP device can access the SNMP community.

•IP Version—Select either IPv4 or IPv6.

•IPv6 Address Type—Select the supported IPv6 address type if IPv6 is

used. The options are:

•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.

•Global—The IPv6 address is a global Unicast IPV6 type that is visible and

reachable from other networks.

•Interface—If the IPv6 address type is Link Local, select whether it is

received through a VLAN or ISATAP.

•IP Address—Enter the SNMP management station IP address

•Community—Enter the community name used to authenticate the

management station to the device.

•Access Control—Select one of the following:

•Basic—In this mode, there is no connection to any group. You can only

choose the community access level (Read Only, Read Write, or SNMP

Admin) and, optionally, further qualify it for a specific view. By default, it

applies to the entire MIB.

•Advanced—In this mode, access is controlled by group configurations

•Access Mode—Configure the community:

•Read Only—Management access is restricted to read-only. Changes

cannot be made to the community.

•Read Write—Management access is read-write. Changes can be made to

the device configuration, but not to the community.

•SNMP Admin—User has access to all device configuration options, as well

as permissions to modify the community. SNMP Admin is equivalent to

Read Write for all MIBs except for the SNMP MIBs. SNMP Admin is required

for access to the SNMP MIBs.

•View Name—Select an SNMP view (a collection of MIB subtrees to which

access is granted).

•Group Name—Select an SNMP group that determines the access rights in

Advanced mode.

STEP 4 Click Apply. The SNMP Community is defined, and the Running

Configuration is updated.

Notification Filters

The Notification Filter page enables configuring SNMP notification filters

and Object IDs (OIDs) that are checked. After creating a notification filter, it is

possible to attach it to a notification recipient in the Notification Recipients

SNMPv1,2 page, and Notification Recipients SNMPv3 page.

The notification filter enables filtering the type of SNMP notifications that are

sent to the management station based on the OID of the notification to be sent.

To define a notification filter:

STEP 1 Click Configuration > System Management >SNMP> Notification Filter.

Table of ContentsLinksys

•The Notification Filter page contains notification information for each

filter. The table is able to filter notification entries by Filter Name.

STEP 2 Click Add.

STEP 3 Enter the parameters.

•Filter Name—Enter a name between 0-30 characters.

•Filter Object—Select the node in the MIB tree that is included or excluded

in the selected SNMP filter. The options to select the object are as follows:

•Selection List—Enables you to navigate the MIB tree. Press the Up arrow

to go to the level of the selected node’s parent and siblings; press the

Down arrow to descend to the level of the selected node’s children. Click

nodes in the view to pass from one node to its sibling. Use the scrollbar to

bring siblings in view.

•If Object ID is used, the object identifier is included in the view if the

Include in filter option is selected.

STEP 4 Include or exclude in Object Filter. If this is selected, the selected MIBs

are included in the filter, otherwise they are excluded.

STEP 5 Click Apply. The SNMP views are defined and the running

configuration is updated.

SNMP v1/v2 Notification Recipients

Trap messages are generated to report system events, as defined in RFC 1215.

The system can generate traps defined in the MIB that it supports.

Trap receivers (aka Notification Recipients) are network nodes where the trap

messages are sent by the device. A list of notification recipients are defined as

the targets of trap messages.

A trap receiver entry contains the IP address of the node and the SNMP

credentials corresponding to the version that is included in the trap message.

When an event arises that requires a trap message to be sent, it is sent to

every node listed in the Notification Recipient Table.

The Notification Recipients SNMPv1,2 page and the Notification Recipients

SNMPv3 page enable configuring the destination to which SNMP notifications

are sent, and the types of SNMP notifications that are sent to each destination

(traps or informs). The Add/Edit pop-ups enable configuring the attributes of

the notifications.

An SNMP notification is a message sent from the device to the SNMP

management station indicating that a certain event has occurred, such as a

link up/ down.

It is also possible to filter certain notifications. This can be done by

creating a filter in the Notification Filter page and attaching it to an SNMP

notification recipient. The notification filter enables filtering the type of SNMP

notifications that are sent to the management station based on the OID of the

notification that is about to be sent.

Defining SNMP Notification Recipients

•To define a recipient in SNMPv1,2:

STEP 1 Click Configuration > System Management > SNMP > V1/V2 >

Notification Recipients

•This page displays the currently-defined SNMP recipients.

STEP 2 Enter the parameters.

•Recipient—Select whether to specify the remote log server by IP address

or server name.

•IP Version—Select either IPv4 or IPv6.

•IPv6 Address Type—Select either Link Local or Global.

•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.

•Global—The IPv6 address is a global Unicast IPV6 type that is visible

and reachable from other networks.

•Interface—If the IPv6 address type is Link Local, select whether it is

received through a VLAN or ISATAP.

•Recipient IP Address—Enter the IP address of where the traps are sent.

•Recipient Name—Enter the server name of where the traps are sent.

•UDP Port—Enter the UDP port used for notifications on the recipient device.

•Notification Type—Select whether to send Traps or Informs. If both are

required, two recipients must be created.

•Notification Version—Select the trap SNMP version 1 or 2.

Table of ContentsLinksys

•Community—Select from the pull-down the community string of the trap

manager. Community String names are generated from those listed in the

Community page.

•Notification Filter—Select to enable filtering the type of SNMP

notifications sent to the management station. The filters are created in

the Notification Filter page.

•Filter Name—Select the SNMP filter that defines the information

contained in traps (defined in the Notification Filter page).

STEP 3 Click Apply. The SNMP Notification Recipient settings are written to

the Running Configuration file.

SNMP v3 Notification Recipients

•To define a recipient in SNMPv3:

STEP 1 Click Configuration > System Management > SNMP > V3 Notification

Recipients.

This page displays recipients for SNMPv3.

STEP 2 Enter the fields:

•Recipient—Select whether to specify the remote log server by IP address

or server name.

•IP Version—Select either IPv4 or IPv6.

•IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The

options are:

•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.

•Global—The IPv6 address is a global Unicast IPV6 type that is visible

and reachable from other networks.

•Link Local Interface—Select the link local interface (if IPv6 Address Type

Link Local is selected) from the pull-down list.

•Recipient IP Address/Name—Enter the IP address or server name of

where the traps are sent.

•UDP Port—Enter the UDP port used to for notifications on the

recipient device.

•Notification Type—Select whether to send traps or informs. If both are

required, two recipients must be created.

•User Name—Select from the drop-down list the user to whom SNMP

notifications are sent. In order to receive notifications, this user must be

defined on the SNMP User page, and its engine ID must be remote.

•Security Level—Select how much authentication is applied to the packet.

NOTE:

The Security Level here depends on which User Name was selected. If

this User Name was configured as No Authentication, the Security Level

is No Authentication only. However, if this User Name has assigned

Authentication and Privacy on the User page, the security level on this

screen can be either No Authentication, or Authentication Only, or

Authentication and Privacy.

The options are:

•No Authentication—Indicates the packet is neither authenticated

nor encrypted.

•Authentication—Indicates the packet is authenticated but not encrypted.

•Privacy—Indicates the packet is both authenticated and encrypted.

•Notification Filter—Select to enable filtering the type of SNMP

notifications sent to the management station. The filters are created in

the Notification Filter page.

•Filter Name—Select the SNMP filter that defines the information

contained in traps (defined in the Notification Filter page).

STEP 3 Click Apply. The SNMP Notification Recipient settings are written to

the Running Configuration file.

Logs

This section describes the Logs feature, which enables the device to generate

multiple independent logs. It covers the following topics:

•Log Management

•Remote Log Servers

•RAM Log

•Flash Memory Log

Table of ContentsLinksys

Overview

Each log is a set of messages describing system events.

The device generates the following local logs:

•Log sent to the console interface.

•Log written into a cyclical list of logged events in the RAM and erased

when the device reboots.

•Log written to a cyclical log-file saved to the Flash memory and persists

across reboots.

In addition, you can send messages to remote SYSLOG servers in the form of

SNMP traps and SYSLOG messages.

You can configure the messages that are written to each log by severity, and

amessage can go to more.

Log Management

You can enable or disable logging on the Log Management page.

You can select the events by severity level. Each log message has a severity

level marked with the first letter of the severity level separated by dashes

(-) on each side (except for Emergency that is indicated by the letter F). For

example, the log message “%INIT-I-InitCompleted: … “ has a severity level of I,

meaning Informational.

The event severity levels are listed from the highest severity to the lowest

severity, as follows:

•Emergency—System is not usable.

•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.

You can select different severity levels for RAM and Flash logs. These logs are

displayed in the RAM Log page and Flash Memory Log page, respectively.

Selecting a severity level to be stored in a log causes all of the higher severity

events to be automatically stored in the log. Lower severity events are not

stored in the log.

For example, if Warning is selected, all severity levels that are Warning and

higher are stored in the log (Emergency, Alert, Critical, Error, and Warning). No

events with severity level below Warning are stored (Notice, Informational,

and Debug).

To set global log parameters, do the following:

STEP 1 Click Configuration > System Management > Logs > Log

Management.

STEP 2 Enter the parameters.

System Log

•Logging—Select to enable message logging.

•Originator Identifier—Enables adding an origin identifier to SYSLOG

•messages. The options are as follows:

•None—Do not include the origin identifier in SYSLOG messages.

•Hostname—Include the system hostname in SYSLOG messages.

•IPv4 Address—Include the IPv4 address of the sending interface in

•SYSLOG messages.

•IPv6 Address—Include the IPv6 address of the sending interface in

•SYSLOG messages.

•User Defined—Enter a description to be included in SYSLOG messages.

Log Settings

•Severity—Select the severity levels of the messages to be logged to

the following:

•RAM Memory Logging—Severity levels of the messages to be logged to

the RAM.

•Flash Memory Logging—Severity levels of the messages to be logged to

the Flash memory.

STEP 3 Click Apply. The Running Configuration file is updated.

Table of ContentsLinksys

Remote Log Servers

The Remote Log Servers page enables defining remote SYSLOG servers where

log messages are sent (using the SYSLOG protocol). For each server, you can

configure the severity of the messages that it receives.

To define SYSLOG servers, do the following:

STEP 1 Click Configuration > System Management > Logs > Remote

Log Servers.

The list of configured remote log servers is displayed.

STEP 2 Click Add.

STEP 3 Enter the parameters.

•Remote Log Server—Select whether to identify the remote log server by

IP address or name.

•IP Version—Select the supported IP version.

•IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The

options are as follows:

•Global—The IPv6 address is a global Unicast IPV6 type that is visible

and reachable from other networks.

•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.

•Interface—Select the link local interface (if IPv6 Address Type Link

Local is selected) from the list.

•Log Server IP Address—Enter the IP address of the log server if it is to be

identified by address.

•Log Server Name—Enter the domain name of the log server if it is to be

identified by name.

Server Settings

•UDP Port—Enter the UDP port to which the log messages are sent.

•Facility—Select a facility value from which system logs are sent to the

remote server. Only one facility value can be assigned to a server. If a

second facility code is assigned, the first facility value is overridden.

•Description—Enter a server description.

•Minimum Logging Level—Select the minimum level of system log

messages to be sent to the server.

STEP 4 Click Apply. The SYSLOG server is added, and the Running

Configuration file is updated.

RAM Log

The RAM Log page displays all messages that were saved in the RAM (cache)

in chronological order. Entries are stored in the RAM log according to the

configuration in the Log Management page.

To view log entries, click Configuration > System Management > Logs > RAM Log.

This page contains the following fields:

•Log Index—Log entry number.

•Log Time—Time when message was generated.

•Severity—Event severity.

•Description—Message text describing the event.

To clear the log messages, click Clear. The messages are cleared.

Flash Memory Log

The Flash Memory Log page displays the messages that were stored in the

Flash memory, in chronological order. The minimum severity for logging is

configured in the Log Management page. Flash logs remain when the device

is rebooted. You can clear the logs manually.

To view the Flash logs, click Configuration > System Management > Logs >

Flash Memory Log.

This page contains the following fields:

•Log Index—Log entry number.

•Log Time—Time when message was generated.

•Severity—Event severity.

•Description—Message text describing the event.

To clear the messages, click Clear. The messages are cleared.

Table of ContentsLinksys

Chapter 5 Port Management

This section describes port configuration, link aggregation, and the Green

Ethernet feature.

It covers the following topics:

•Ports

•Link Aggregation

•Green Ethernet

•PoE

•LLDP

Ports

Workflow

To configure ports, perform the following actions:

1. Configure port by using the Ports page.

2. Enable/disable the Link Aggregation Control protocol, and configure the

potential member ports to the desired LAGs by using the LAGs page. By

default, all LAGs are empty.

3. Configure the Ethernet parameters, such as speed and auto-negotiation

for the LAGs by using the LAGs page.

4. Configure the LACP parameters for the ports that are members or

candidates of a dynamic LAG by using the LAGs page.

5. Configure Green Ethernet and 802.3 Energy Efficient Ethernet by using

the Green Ethernet page.

6. Configure Green Ethernet energy mode and 802.3 Energy Efficient

Ethernet per port by using the Green Ethernet page.

7. If PoE is supported and enabled for the device, configure the device as

described in PoE.

8. Configure LLDP and LLDP-MED Port feature by using Discovery LLDP.

Configure Port Settings

To configure port settings:

STEP 1 Click Configuration > Port Management > Ports.

STEP 2 Select Enable to support jumbo packets of up to 10 KB in size. If

Jumbo Frames is not enabled (default), the system supports packet

size up to 2,000 bytes. For Jumbo Frames to take effect, the device

must be rebooted after the feature is enabled.

STEP 3 To update the port settings, select the desired port, and click Edit.

STEP 4 Modify the following parameters:

•Port—Select the port number.

Port Settings

•Operational Status—Displays whether the port is currently up or down.

If the port is down because of an error, the description of the error is

displayed.

•Administrative Mode—Select to bring the port up or down.

•Suspended Port—Select to reactivate a port that has been suspended.

The reactivate operation brings the port up without regard to why the

port was suspended.

•Protected Port—Select to make this a protected port. (A protected port is

also referred to as a Private VLAN Edge (PVE).) The features of a protected

port are as follows:

•Protected Ports provide Layer 2 isolation between interfaces (Ethernet

ports and LAGs) that share the same VLAN.

•Packets received from protected ports can be forwarded only to

unprotected egress ports. Protected port filtering rules are also applied to

packets that are forwarded by software, such as snooping applications.

•Port protection is not subject to VLAN membership. Devices connected to

protected ports are not allowed to communicate with each other, even if

they are members of the same VLAN.

•Both ports and LAGs can be defined as protected or unprotected.

Protected LAGs are described in the LAGs section.

•Auto Negotiation—Select to enable auto-negotiation on the port. Auto-

negotiation enables a port to advertise its transmission speed, duplex

mode, and flow control abilities to the port link partner.

Table of ContentsLinksys

•Port Speed—Configure the speed of the port. The port type determines

the available speeds. You can designate this field only when port auto-

negotiation is disabled.

•Duplex Mode—Select the port duplex mode. This field is configurable

only when auto-negotiation is disabled, and the port speed is set to 10M

or 100M. At port speed of 1G, the mode is always full duplex. The possible

options are:

•Half—The interface supports transmission between the device and

the client in only one direction at a time.

•Full—The interface supports transmission between the device and

the client in both directions simultaneously.

•Auto Advertisement—Select the capabilities advertised by auto-negotiation

when it is enabled. The optionsare as follows:

•Max Capability—All port speeds and duplex mode settings can be accepted.

•10 Full Duplex—10 Mbps speed and Full Duplex mode.

•10 Half Duplex—10 Mbps speed and Half Duplex mode.

•100 Full Duplex—100 Mbps speed and Full Duplex mode.

•100 Half Duplex—100 Mbps speed and Half Duplex mode.

•1000 Full Duplex—1000 Mbps speed and Full Duplex mode.

•Back Pressure—Select the Back Pressure mode on the port (used with

Half Duplex mode) to slow down the packet reception speed when

the device is congested. It disables the remote port, preventing it from

sending packets by jamming the signal.

•Flow Control—Enable or disable 802.3x Flow Control, or enable the auto-

negotiation of flow control on the port (only when in Full Duplex mode).

•MDI/MDIX—the Media Dependent Interface (MDI)/Media Dependent

Interface with Crossover (MDIX) status on the port. The options are

as follows:

•MDIX—Select to swap the port’s transmit and receives pairs.

•MDI—Select to connect this device to a station by using a straight-

through cable.

•Auto—Select to configure this device to automatically detect the

correct pinouts for the connection to another device.

•Description—Enter the port description.

STEP 5 Click Apply. The port settings are written to the Running

Configuration file.

Link Aggregation

This section describes how to configure LAGs. It covers the following topics:

•Overview

•LAGs

Overview

Link Aggregation Control Protocol (LACP) is part of the IEEE specification

(802.3ad) that enables you to bundle several physical ports together to form

a single logical channel (LAG). LAGs multiply the bandwidth, increase port

flexibility, and provide link redundancy between two devices.

Two types of LAGs are supported:

•Static—A LAG is static if the LACP is disabled on it. The ports assigned to

a static LAG are always active members. After a LAG is manually created,

the LACP option cannot be added or removed, until the LAG is edited and

a member is removed (which can be added prior to applying), then the

LACP button becomes available for editing.

•Dynamic—A LAG is dynamic if LACP is enabled on it. The ports assigned

to dynamic LAG are candidate ports. LACP determines which candidate

ports are active member ports. The non-active candidate ports are

standby ports ready to replace any failing active member ports.

Load Balancing

•Traffic forwarded to a LAG is load-balanced across the active member

ports, thus achieving an effective bandwidth close to the aggregate

bandwidth of all the active member ports of the LAG.

•Traffic load balancing over the active member ports of a LAG is managed

by a hash-based distribution function that distributes Unicast and

Multicast traffic based on Layer 2 or Layer 3 packet header information.

•The device supports two modes of load balancing:

•By MAC Addresses—(Default) Based on the destination and source MAC

•addresses of all packets.

Table of ContentsLinksys

•By IP and MAC Addresses—Based on the destination and source IP

addresses for IP packets, and destination and source MAC addresses for

non-IP packets.

LAG Management

In general, a LAG is treated by the system as a single logical port. In particular,

the LAG has port attributes similar to a regular port, such as state and speed.

The device supports four LAGs.

Every LAG has the following characteristics:

•All ports in a LAG must be of the same media type.

•To add a port to the LAG, it cannot belong to any VLAN except the default

VLAN.

•Ports in a LAG must not be assigned to another LAG.

•No more than eight ports are assigned to a static LAG and no more than

16 ports can be candidates for a dynamic LAG.

•All the ports in a LAG must have auto-negotiation disabled, although the

LAG can have auto-negotiation enabled.

•When a port is added to a LAG, the configuration of the LAG is applied

to the port. When the port is removed from the LAG, its original

configuration is reapplied.

•Protocols, such as Spanning Tree, consider all the ports in the LAG to be

one port.

Default Settings and Configuration

Ports are not members of a LAG and are not candidates to become part of a LAG.

Static and Dynamic LAG Workflow

After a LAG has been manually created, LACP cannot be added or removed

until the LAG is edited and a member is removed. Only then the LACP field

is activated.

•To configure a static LAG, perform the following actions:

Disable LACP on the LAG to make it static. Assign up to eight member

ports to the static LAG in the Port List to the LAG Port Member list.

Perform these actions in the LAGs page.

Configure various aspects of the LAG, such as speed and flow control by

using the Edit LAG page.

To configure a dynamic LAG, perform the following actions:

Enable LACP on the LAG. Assign up to 16 candidates ports to the

dynamic LAG by selecting and moving the ports from the Port List to

the LAG Port Member List by using the LAGs page.

Configure various aspects of the LAG, such as speed and flow control by

using the LAGs page.

LAGs

The LAGs page displays global and per-LAG settings. The page also enables

you to configure the global settings and to select and edit the desired LAG on

the Edit LAG Membership page.

•To define the member or candidate ports in a LAG.

STEP 1 Click Configuration > Port Management > Link Aggregation > LAGs.

Information for each defined LAG is displayed.

STEP 2 Select the Load Balance Method:

•by MAC Address—(Default) Based on the destination and source MAC

addresses of all packets.

•by IP and MAC Address—Based on the destination and source IP addresses

for IP packets, and destination and source MAC addresses for non-IP

packets.

STEP 3 Select the LAG to be configured, and click Edit.

STEP 4 Enter the values for the following fields:

Operational Status—Displays the following:

•Port List—Move those ports that are to be assigned to the LAG from the

Port List to the LAG Port Member list. Up to eight ports per static LAG can

be assigned, and 16 ports can be assigned to a dynamic LAG.

•LAG Mode—Displays whether the LAG is up or down.

•Suspended LAG—Select to reactivate the LAG.

Table of ContentsLinksys

•LACP—Select to enable LACP on the selected LAG. This makes it a

dynamic LAG. This field can only be enabled after moving a port to the

LAG in the next field.

•Protected LAG—Select to make the LAG a protected port for Layer 2

isolation. See the Port Configuration description in Setting Basic Port

Configuration for details regarding protected ports and LAGs.

•Auto Negotiation—Select to enable auto-negotiation on the LAG. Auto-

negotiation is a protocol between two link partners that enables a LAG to

advertise its transmission speed and flow control to its partner (the Flow

Control default is disabled). It is recommended to keep auto-negotiation

enabled on both sides of an aggregate link, or disabled on both sides,

while ensuring that link speeds are identical.

•Port Speed—Configure the speed of the LAG. The port types determine

the available speeds. You can designate this field only when port auto-

negotiation is disabled.

•Auto Advertisement—Select the capabilities to be advertised by the LAG.

The options are as follows:

•Max Capability—All LAG speeds and both duplex modes are available.

•10 Full Duplex—The LAG advertises a 10 Mbps speed and the mode

is full duplex.

•100 Full Duplex—The LAG advertises a 100 Mbps speed and the

mode is full duplex.

•1000 Full Duplex—The LAG advertises a 1000 Mbps speed and the

mode is full duplex.

•Flow Control—Set Flow Control to either Enable or Disable or Auto-

Negotiation.

•Description—Enter the LAG name or a comment.

STEP 5 Click Apply. LAG membership is saved to the Running Configuration file.

Green Ethernet

This section describes the Green Ethernet feature that is designed to save

power on the device.

Green Ethernet is a common name for a set of features that is designed to be

environmentally friendly, and to reduce the power consumption of a device.

Green Ethernet is different from EEE in that Green Ethernet energy-detect is

enabled on all devices where only the gigabyte ports are enable with EEE.

The Green Ethernet feature can reduce overall power usage in the

following ways:

•Energy-Detect Mode—In this mode, the switch conserves power

when the operational status of a port is down. Energy-Detect Mode is

supported on all ports.

•Short-Reach Mode—This feature provides for power savings on a short

length of cable. After cable length is analyzed, the power usage is adjusted

for various cable lengths. If the cable is shorter than 50 meters, the device

uses less power to send frames over the cable, thus saving energy. This

mode is only supported on RJ45 GE ports; it does not apply to Combo ports.

This mode is globally disabled by default. It cannot be enabled if EEE mode

is enabled (see below).

802.3 Energy Efficient Ethernet (EEE)—EEE reduces power consumption

when there is no traffic on the port. See Energy Efficient Ethernet Feature

for more information.

EEE is enabled globally by default. On a given port, if EEE is enabled, short

reach mode will be disabled. If Short Reach Mode is enabled, EEE is grayed

out.

These modes are configured per port, without taking into account the LAG

membership of the ports.

Power savings, current power consumption and cumulative energy saved

can be monitored. The total amount of saved energy can be viewed as a

percentage of the power that would have been consumed by the physical

interfaces had they not been running in Green Ethernet mode.

The saved energy displayed is only related to Green Ethernet. The amount of

energy saved by EEE is not displayed.

Energy Efficient Ethernet Feature

EEE is designed to save power when there is no traffic on the link. In Green

Ethernet, power is reduced when the port is down. With EEE, power is reduced

when the port is up, but there is no traffic on it.

When using 802.3 EEE, systems on both sides of the link can disable portions

of their functionality and save power during periods of no traffic.

802.3 EEE supports IEEE 802.3 MAC operation at 100 Mbps and 1000 Mbps:

Table of ContentsLinksys

LLDP is used to select the optimal set of parameters for both devices. If LLDP

is not supported by the link partner, or is disabled, 802.3 EEE will still be

operational, but it might not be in the optimal operational mode.

The 802.3 EEE feature is implemented using a port mode called Low Power

Idle (LPI) mode. When there is no traffic and this feature is enabled on the

port, the port is placed in the LPI mode, which reduces power consumption

dramatically.

Both sides of a connection (device port and connecting device) must support

802.3 EEE for it to work. When traffic is absent, both sides send signals

indicating that power is about to be reduced. When signals f s (and not in

Down status), and power is reduced.

For ports to stay in LPI mode, the Keep Alive signal must be received

continuously from both sides.

Power Saving by Disabling Port LEDs

The Disable Port LEDs feature saves power consumed by the device’s LEDs.

When located in an unoccupied room, these LEDs are unnecessary. Use the

Green Ethernet feature to disable port LEDs (link, speed, and PoE) when they

are not needed. Enable them if needed (debugging, connecting additional

devices, etc.).

Advertise Capabilities Negotiation

802.3 EEE support is advertised during the Auto-Negotiation stage. Auto-

Negotiation provides a linked device with the capability to detect the

abilities (modes of operation) supported by the device at the other end of

the link, determine common abilities, and configure itself for joint operation.

Auto-Negotiation is performed at the time of link-up, on command from

management, or upon detection of a link error. During the link establishment

process, both link partners to exchange their 802.3 EEE capabilities. Auto-

Negotiation functions automatically without user interaction when it is

enabled on the device.

NOTE:

If Auto-Negotiation is not enabled on a port, the EEE is disabled. The only

exception is if the link speed is 1GB, then EEE will still be enabled even

though Auto-Negotiation is disabled.

Default Configuration

•By default, 802.3 EEE is enabled globally and per port.

Interactions Between Features

The following describe 802.3 EEE interactions with other features:

•If auto-negotiation is not enabled on the port, the 802.3 EEE operational

status is disabled. The exception to this rule is that if the link speed is 1

gigabit, EEE will still be enabled even though Auto-Negotiation is disabled.

•If 802.3 EEE is enabled and the port is going up, it commences to work

immediately in accordance with the maximum wake time value of the port.

•On the GUI, the EEE field for the port is not available when the Short

Reach Mode option on the port is checked.

If the port speed on the GE port is changed to 10Mbit, 802.3 EEE is disabled.

This is supported in GE models only.

802.3 EEE Configuration Workflow

This section describes how to configure the 802.3 EEE feature and view its

counters.

STEP 1 Ensure that auto-negotiation is enabled on the port by opening the

Ports page.

a. Select a port and open the Edit Ports page.

b. Select Auto Negotiation field to ensure that it is Enabled.

STEP 2 Ensure that 802.3 Energy Efficient Ethernet (EEE) is globally enabled

in the Green Ethernet page (it is enabled by default). This page also

displays how much energy has been saved.

STEP 3 Ensure that 802.3 EEE is enabled on a port by opening the Green

Ethernet page.

a. Select a port, open the Edit Ports page.

b. Check the 802.3 Energy Efficient Ethernet (EEE) mode on the port (it is

enabled by default).

Configuring Green Ethernet

To configure Green Ethernet globally and on a port, do the following:

STEP 1 Click Configuration > Port Management > Green Ethernet.

STEP 2 Choose whether to enable the following features:

•Energy Detect Mode—Select to globally enable.

Table of ContentsLinksys

•Port LEDs—Select to disable port LEDs. When disabled, ports do not

display link status, activity, etc.

•Short Reach—Select to globally enable Short Reach mode.

NOTE:

If Short Reach is enabled, EEE must be disabled.

•802.3 Energy Efficient Ethernet (EEE)—Select to globally enable EEE.

STEP 3 Click Apply to set the global settings.

•The following fields are displayed:

•Power Savings—Displays the percentage of power saved by running

Green Ethernet and Short Reach. The power savings displayed is only

relevant to the power saved by Short Reach and Energy Detect modes.

The EEE power savings is dynamic by nature since it is based on port

utilization and is therefore not taken into consideration. The power

saving calculation is performed by comparing the maximum power

consumption without power savings to the current consumption.

•Cumulative Energy Saved—Displays the amount of energy saved from

the last device reboot in watt hours. This value is updated each time there

is an event that affects power saving.

For each port the following fields are described:

•Port—The port number.

•Short Reach Mode—State of the port regarding Short Reach mode.

•Short Reach Status—Status of the port regarding Short Reach mode is

either Enabled or Disabled.

•Short Reach Reason—If Short-Reach mode is not operational, displays

the reason.

•Cable Length—Displays VCT-returned cable length in meters.

•EEE Mode—State of the port regarding the EEE feature.

•EEE Status—Whether EEE is currently operating on the local port. This is a

function of whether it has been enabled (Administrative Status), whether

it has been enabled on the local port and whether it is operational on the

local port.

NOTE:

The window displays the Short Reach, Energy Detect and EEE settings for

each port; however, they are not enabled on any port unless they are also

enabled globally.

•EEE Status—State of EEE on the device (enabled or disabled).

•Remote EEE Mode—EEE mode of the linked partner.

•Energy Detect Mode - Whether Energy Detect Mode is enabled.

•Energy Detect Status -Whether Energy Detect Mode is currently

operational. This is a function of whether it has been enabled

(Administrative Status), whether it has been enabled on the local port

and whether it is operational on the local port.

•Energy Detect Reason - If Energy Detect Mode is not operational, this

field identifies why not.

STEP 4 Select a Port and click Edit.

STEP 5 Select to enable or disable the various features.

STEP 6 Click Apply. The Green Ethernet port settings are written to the

Running Configuration file.

PoE

The Power over Ethernet (PoE) feature is only available on PoE-based devices.

For a list of PoE-based devices, refer to the Device Models section.

This section describes how to use the PoE feature. It covers the following

topics:

•Overview

•Feature Configuration

•Port Limit Power Mode

•Class Limit Power Mode

Overview

A PoE device is PSE (Power Sourcing Equipment) that delivers electrical

power to connected PD (Powered Devices) over existing copper cables

without interfering with the network traffic, updating the physical network or

modifying the network infrastructure.

Table of ContentsLinksys

See Device Models for information concerning PoE support on various

models. PoE provides the following features:

•Eliminates the need to run 110/220 V AC power to all devices on a

wired LAN.

•Removes the necessity for placing all network devices next to power

sources.

•Eliminates the need to deploy double cabling systems in an enterprise,

significantly decreasing installation costs.

Power over Ethernet can be used in any enterprise network that deploys

relatively low-powered devices connected to the Ethernet LAN:

•IP phones

•Wireless access points

•IP gateways

•Audio and video remote monitoring devices

PoE Operation

•PoE implementation stages are as follows:

•Detection—Sends special pulses on the copper cable. When a PoE device

is located at the other end, that device responds to these pulses.

•Classification—Negotiation between the Power Sourcing Equipment

PSE) and the Powered Device (PD) commences after the Detection stage.

During negotiation, the PD specifies its class, which is the amount of

maximum power that the PD consumes.

•Power Consumption—After the classification stage completes, the

PSE provides power to the PD. If the PD supports PoE, but without

classification, it is assumed to be class 0 (the maximum). If a PD tries to

consume more power than permitted by the standard, the PSE stops

supplying power to the port.

Power Modes

•Power per port can be limited depending on the Power Mode:

•Port Limit—Power is limited to a specified wattage. For these settings to be

active, the system must be in PoE Port Limit mode. That mode is configured

in the PoE Feature Configuration page. When the power consumed on the

port exceeds the port limit, the port power is turned off.

•Class Limit—Power is limited based on the class of the connected PD. For

these settings to be active, the system must be in PoE Class Limit mode.

That mode is configured in the PoE Feature Configuration page. When the

power consumed on the port exceeds the class limit, the port power is

turned off.

PoE Priority Example

A 48-port device is supplying a total of 375 watts.

The administrator configures all ports to allocate up to 30 watts each. This

results in 48 times 30 ports equaling 1440 watts, which is too much. The

device cannot provide enough power to each port, so it provides power

according to the priority.The administrator sets the priority for each port,

allocating how much power it can be given.

These priorities are entered in the PoE Port Limit Mode or Class Limit Power

Mode pages.

See Device Models for a description of the device models that support PoE

and the maximum power that can be allocated to PoE ports.

PoE Configuration Considerations

There are two factors to consider in PoE configuration:

•The amount of power that the PSE can supply

•The amount of power that the PD is attempting to consume

You can decide the following:

•Maximum power a PSE is allowed to supply to a PD

•POE mode—To change the mode from Class Power Limit to Port Limit,

and vice versa, during device operation. The power values per port that

were configured for the Port Limit mode are retained.

NOTE:

Changing the mode from Class Limit to Port limit, and vice versa, when the

device is operational forces the Powered Device to reboot.

•Maximum port limit allowed as a per-port numerical limit in mW (Port

Limit mode).

The PoE-specific hardware automatically detects the PD class and its power

limit according to the class of the device connected to each specific port

(Class Limit mode).

Table of ContentsLinksys

If at any time during the connectivity an attached PD requires more power

from the device than the configured allocation allows (no matter if the device

is in Class Limit or Port Limit mode), the device does the following:

•Maintains the up/down status of the PoE port link

•Turns off power delivery to the PoE port

•Logs the reason for turning off power

Feature Configuration

The Feature Configuration page enables selecting either the Port Limit or

Class Limit PoE mode.

These settings are entered in advance. When the PD actually connects

and is consuming power, it might consume much less than the maximum

power allowed.

Output power is disabled during power-on reboot, initialization, and system

configuration to ensure that PDs are not damaged.

To configure PoE on the device and monitor current power usage:

STEP 1 Click Configuration > Port Management > PoE > Feature Configuration.

STEP 2 Enter the values for the following fields:

•Power Mode—Select one of the following options:

•Port Limit—The maximum power limit per each port is configured by the

user.

•Class Limit—The maximum power limit per port is determined by the

class of the device, which results from the Classification stage.

NOTE:

When you change from Port Limit to Class Limit, or vice versa, you must

disable PoE ports, and enable them after changing the power configuration.

The following counters are displayed for the device:

•Nominal Power—The total amount of power in watts that the device can

supply to all the connected PDs.

•Consumed Power—Amount of power in watts that is currently being

consumed by the PoE ports.

•Available Power—Nominal power in watts minus the amount of

consumed power.

STEP 3 Click Apply to save the PoE properties.

Port Limit Power Mode

To configure port limit power mode do the following:

STEP 1 Click Configuration > Port Management > PoE > Port Limit Power

Mode. The list of fields below is for Port Limit Power Mode.

The following fields are displayed for ports on which the port limit power

mode is enabled:

•PoE Status—Enable or disable PoE on the port.

•Power Priority Level—Port priority is low, high, or critical, for use when

the power supply is low. For example, if the power supply is running at

99% usage and port 1 is prioritized as high, but port 3 is prioritized as low,

port 1 receives power and port 3 might be denied power.

•Power Allocation Limit (mW)—Power in milliwatts allocated to the port.

•Max Power Allocation (mW)—Maximum amount of power permitted on

this port.

•Power Consumption (mW)—Amount of power assigned to the powered

device connected to the selected interface.

•Class—Power class of device.

•Operational Status—Displays whether Power Limit mode is enabled or

disabled on the port.

STEP 2 Select a port and click Edit. Enter the fields as described above.

STEP 3 Click Apply. The PoE settings for the port are written to the Running

Configuration file.

Class Limit Power Mode

•To configure class limit power mode, do the following:

STEP 1 Click Configuration > Port Management > PoE > Class Limit Power

Mode.

The following fields are displayed for ports on which the port limit power

mode is enabled:

•PoE Status—Enable or disable PoE on the port.

Table of ContentsLinksys

•Power Priority Level—Port priority is low, high, or critical, for use when

the power supply is low. For example, if the power supply is running at

99% usage and port 1 is prioritized as high, but port 3 is prioritized as low,

port 1 receives power and port 3 might be denied power.

•Class—Class configured on this port. The classes are shown in the

following:

•Class •Maximum Power Delivered by Device

Port

•0 •15.4 watt

•1 •4.0 watt

•2 •7.0 watt

•3 •15.4 watt

•4 •30.0 watt

•Max Power Allocation (mW)— Maximum amount of power permitted on

this port. The switch hardware may actually supply 5-10% more power

than Max Power Allocation to accommodate the power loss over the wire.

•Power Consumption (mW)—Amount of power assigned to the powered

device connected to the selected interface.

•Operational Status—Whether the Class Limit mode is enabled or disabled

on the port.

STEP 2 Select a port and click Edit. Enter the fields as described above.

STEP 3 Click Apply. The PoE settings for the port are written to the Running

Configuration file.

LLDP

This section provides information for configuring Discovery. It covers the

following topics:

•Overview

•Feature Configuration

•LLDP MED Ports

•LLDP Local Information

•LLDP Neighbor Information

•LLDP MED Network Policy

Overview

Link Layer Discovery Protocol (LLDP) is a link layer protocol for directly-

connected LLDP-capable neighbors to advertise themselves and their

capabilities. LLDP enables network managers to troubleshoot and enhance

network management in multi-vendor environments. LLDP standardizes

methods for network devices to advertise themselves to other systems, and to

store discovered information.

By default, the device sends an LLDP advertisement periodically to all its

interfaces and processes incoming LLDP packets as required by the protocols. In

LLDP, advertisements are encoded as TLV (Type, Length, Value) in the packet.

The information learned is stored in the data in a Management Information

Base (MIB). The network management system models the topology of the

network by querying these MIB databases.

By default, the device terminates and processes all incoming LLDP packets as

required by the protocol.

The LLDP protocol has an extension called LLDP Media Endpoint Discovery

(LLDP-MED) that provides and accepts information from media endpoint

devices such as VoIP phones and video phones. For further information about

LLDP-MED, see LLDP MED Network Policy.

The following LLDP configuration notes apply:

•LLDP can be enabled or disabled globally or per port. The LLDP capability

of a port is relevant only if LLDP is globally enabled.

•If LLDP is globally enabled, the device filters out incoming LLDP packets

from ports that are LLDP-disabled.

Table of ContentsLinksys

•If LLDP is globally disabled, the device can be configured to discard,

VLAN-aware flooding, or VLAN-unaware flooding of all incoming

LLDP packets. VLAN-aware flooding floods an incoming LLDP packet

to the VLAN where the packet is received excluding the ingress

port. VLAN-unaware flooding floods an incoming LLDP packet to

all the ports excluding the ingress port. The default is to discard

LLDP packets when LLDP is globally disabled. You can configure the

discard/flooding of incoming LLDP packets from the LLDP Feature

Configuration page.

•LLDP end devices, such as IP phones, learn the voice VLAN

configuration from LLDP advertisements. By default, the device is

enabled to send out LLDP advertisement based on the voice VLAN

configured at the device. Refer to the Voice VLAN for details.

NOTE:

When yLLDP does not distinguish if a port is in a LAG. If there are multiple

ports in a LAG, LLDP transmit packets on each port without taking into

account the fact that the ports are in a LAG.

The operation of LLDP is independent of the STP status of an interface.

If 802.1x port access control is enabled at an interface, the device transmits

and receives LLDP packets to and from the interface only if the interface is

authenticated and authorized.

If a port is the target of mirroring, then LLDP considers it down.

NOTE:

LLDP are link layer protocols for directly-connected LLDP capable devices

to advertise themselves and their capabilities. In deployments where the

LLDP-capable devices are not directly connected and are separated with

LLDP- incapable devices, the LLDP-capable devices may be able to receive

the advertisement from other device(s) only if the LLDP-incapable devices

flood the LLDP packets they receive. If the LLDP-incapable devices perform

VLAN-aware flooding, then LLDPcapable devices can hear each other

only if they are in the same VLAN. An LLDPcapable device may receive

advertisements from more than one device if the LLDPincapable devices

flood the LLDP packets.

Workflows

Following are examples of actions that can be performed with the LLDP feature

and in a suggested order. You can refer to the LLDP/CDP section for additional

guidelines on LLDP configuration. LLDP configuration pages are accessible

under the Configuration > Port Management > Discovery LLDP menu.

Enter LLDP global parameters, such as LLDP Frames Handling using the

LLDP Feature Configuration page.

Configure LLDP per port by using the LLDP Feature Configuration page.

On this page, interfaces can be configured to receive/transmit LLDP

PDUs, send SNMP notifications, specify which TLVs to advertise, and

advertise the device’s management address.

Create LLDP MED network policies by using the LLDP MED Network

Policy page.

Associate LLDP MED network policies and the optional LLDP-MED TLVs

to the desired interfaces by using the LLDP MED Port Settings page.

Feature Configuration

The Feature Configuration Page enables configuration of LLDP global

parameters and entering the TLVs that are sent in the LLDP PDU.

The LLDP-MED TLVs to be advertised can be selected in the LLDP MED Port

Settings page, and the management address TLV of the device may be

configured to be advertised.

To configure the LLDP port settings:

STEP 1 Click Configuration > Port Management > Discovery LLDP >

Feature Configuration.

The following fields are displayed (only fields that do not appear in the Edit

page are described):

•Interface—The port to edit.

•LLDP MED Status—Enabled or disabled.

•Number of neighbors—Number of neighbors discovered.

•Neighbor Capability—Displays the primary functions of the neighbor; for

example: Bridge or Router.

•Local PoE—Local PoE information advertised.

•power priority—Port power priority

•power value—Port power value

•Neighbor PoE—PoE information advertised by the neighbor.

•power priority—Port power priority

Table of ContentsLinksys

•power value—Port power value

STEP 2 Enter the following fields.

•LLDP Status—Select to enable LLDP on the device (enabled by default).

•LLDP Frame Handling—If LLDP is not enabled, select the action to be

taken if a packet that matches the selected criteria is received.

•Filtering—Delete the packet.

•Flooding—Forward the packet to all VLAN members.

STEP 3 Select a port and click Edit.

This page provides the following fields:

•Port—Select the port to edit.

•LLDP Status—Select the LLDP publishing option for the port. The values

are the following:

•Tx Only—Publishes but does not discover.

•Rx Only—Discovers but does not publish.

•Tx & Rx—Publishes and discovers.

•Disable—Indicates that LLDP is disabled on the port.

•Available Optional TLVs—Information to be published by the device

•Advertise Optional TLVs—Select the information to be published by

the device by moving the TLV from the Available Optional TLVs list. The

available TLVs contain the following information:

•Port Description—Information about the port, including

manufacturer, product name and hardware/software version.

•System Name—System’s assigned name (in alpha-numeric format).

The value equals the sysName object.

•System Description—Description of the network entity (in alpha-

numeric format). This includes the system’s name and versions of the

hardware, operating system, and networking software supported by

the device. The value equals the sysDescr object.

•System Capabilities—Primary functions of the device, and whether

or not these functions are enabled on the device. The capabilities are

indicated by two octets. Bits 0 through 7 indicate Other, Repeater,

Bridge, WLAN AP, Router, Telephone, DOCSIS cable device, and

station respectively. Bits 8 through 15 are reserved.

•802.3 MAC-PHY—Duplex and bit rate capability and the current duplex

and bit rate settings of the sending device. It also indicates whether the

current settings are due to auto-negotiation or manual configuration.

•802.3 Link Aggregation—Whether the link (associated with the port

on which the LLDP PDU is transmitted) can be aggregated. It also

indicates whether the link is currently aggregated, and if so, provides

the aggregated port identifier.

•802.3 Maximum Frame—Maximum frame size capability of the MAC/

PHY Management Address TLV—Select one of the following ways to

advertise the IP management address of the device:

•Auto Advertise—Specifies that the software automatically chooses

a management address to advertise from all the IP addresses of

the device. In case of multiple IP addresses, the software chooses

the lowest IP address among the dynamic IP addresses. If there are

no dynamic addresses, the software chooses the lowest IP address

among the static IP addresses.

•None—Do not advertise the management IP address.

•Manual Advertise—Select this option and the management IP

address to be advertised.

•Management IP Address—If Manual Advertise was selected, select the

Management IP address from the addresses provided.

STEP 4 Enter the relevant information, and click Apply. The port settings are

written to the Running Configuration file.

LLDP MED Ports

The LLDP MED Ports page enables the selection of the LLDP-MED TLVs and/or

the network policies to be included in the outgoing LLDP advertisement for

the desired interfaces. Network Policies are configured using the LLDP MED

Network Policy page.

To configure LLDP MED on each port, do the following:

STEP 1 Click Configuration > Port Management > LLDP MED Ports.

This page displays the following LLDP MED settings for all ports (only fields

not described in the Edit page are listed):

•Location—Whether Location TLV is transmitted.

•PoE—Whether POE-PSE TLV is transmitted.

Table of ContentsLinksys

•Inventory—Whether Inventory TLV is transmitted.

STEP 2 The message at the top of the page indicates whether the generation

of the LLDP MED Network Policy for the voice application is

automatic or not (see LLDP Overview). Click on the link to change the

mode.

STEP 3 To associate additional LLDP MED TLV and/or one or more user-

defined LLDP MED Network Policies to a port, select it, and click Edit.

STEP 4 Enter the parameters:

•Port—Select the interface to configure.

•LLDP MED Status—Enable/disable LLDP MED on this port.

•Available Optional TLVs—Select the TLVs that can be published by the

device by moving them from the Advertise Optional TLVs list.

•Available Network Policies—Select the LLDP MED policies to be

published by LLDP by moving them from the Available Network Policies

list. These were created in the LLDP MED Network Policy page. To include

one or more userdefined network polices in the advertisement, you must

also select Network Policy from the Available Optional TLVs.

NOTE:

The following fields must be entered in hexadecimal characters in the exact

data format that is defined in the LLDP-MED standard (ANSI-TIA-1057_final_

for_publication.pdf):

•Location Coordinate—Enter the coordinate location to be published

by LLDP.

•Location Civic Address—Enter the civic address to be published

by LLDP.

•Location (ECS) ELIN—Enter the Emergency Call Service (ECS) ELIN

location to be published by LLDP.

STEP 5 Click Apply. The LLDP MED port settings are written to the Running

Configuration file.

LLDP Local Information

To view the LLDP local port status advertised on a port:

STEP 1 Click Configuration > Port Management > Discovery - LLDP > LLDP

Local Information.

STEP 2 Select the desired port from the Port list.

This page displays the following groups of fields (the actual fields displayed

depend on the optional TLVs selected to be advertised):

Global

•Chassis ID Subtype—Type of chassis ID. (For example, the MAC address.)

•Chassis ID—Identifier of chassis. Where the chassis ID subtype is a MAC

address, the MAC address of the device appears.

•System Name—Name of device.

•System Description—Description of the device (in alpha-numeric format).

•Supported System Capabilities—Primary functions of the device, such as

Bridge, WLAN AP, or Router.

•Enabled System Capabilities—Primary enabled function(s) of the device.

•Port ID Subtype—Type of the port identifier that is shown.

•Port ID—Identifier of port.

•Port Description—Information about the port, including manufacturer,

product name and hardware/software version.

Management Address

Displays the table of addresses of the local LLDP agent. Other remote

managers can use this address to obtain information related to the local

device. The address consists of the following elements:

•Address Subtype—Type of management IP address that is listed in the

Management Address field; for example, IPv4.

•Address—Returned address most appropriate for management use.

•Interface Subtype—Numbering method used for defining the

interface number.

•Interface Number—Specific interface associated with this

management address.

MED Information

•Capabilities Supported—MED capabilities supported on the port.

•Current Capabilities—MED capabilities enabled on the port.

Table of ContentsLinksys

•Device Class—LLDP-MED endpoint device class. The possible device

classes are:

•Endpoint Class 1—Generic endpoint class, offering basic LLDP services.

•Endpoint Class 2—Media endpoint class, offering media streaming

capabilities, as well as all Class 1 features.

•Endpoint Class 3—Communications device class, offering all Class 1

and Class 2 features plus location, 911, Layer 2 device support, and

device information management capabilities.

•PoE Device Type—Port PoE type; for example, powered.

•PoE Power Source—Port power source.

•PoE Power Priority—Port power priority.

•PoE Power Value—Port power value.

•Hardware Revision—Hardware version.

•Firmware Revision—Firmware version.

•Software Revision—Software version.

•Serial Number—Device serial number.

•Manufacturer Name—Device manufacturer name.

•Model Name—Device model name.

•Asset ID—Asset ID.

Location Information

•Civic—Street address.

•Coordinates—Map coordinates: latitude, longitude, and altitude.

•ECS ELIN—Emergency Call Service (ECS) Emergency Location

Identification Number (ELIN).

Network Policy

•Application Type—Network policy application type; for example, Voice.

•VLAN ID—VLAN ID for which the network policy is defined.

•VLAN Type—VLAN type for which the network policy is defined. The

possible field values are the following:

•Tagged—Indicates the network policy is defined for tagged VLANs.

•Untagged—Indicates the network policy is defined for

untagged VLANs.

•User Priority—Network policy user priority.

•DSCP—Network policy DSCP.

LLDP Neighbor Information

The LLDP Neighbor Information page contains information that was received

from neighboring devices.

After timeout (based on the value received from the neighbor Time To

Live TLV during which no LLDP PDU was received from a neighbor), the

information is deleted.

To view the LLDP neighbors information:

STEP 1 Click Configurations > Port Management > Discovery - LLDP > LLDP

Neighbor Information.

This page contains the following fields:

•Local Port—Number of the local port to which the neighbor is connected.

Global

•Local Port—Port number.

•MSAP Entry—Device Media Service Access Point (MSAP) entry number.

Basic Details

•Chassis ID Subtype—Type of chassis ID (for example, MAC address).

•Chassis ID—Identifier of the 802 LAN neighboring device chassis.

•Port ID Subtype—Type of the port identifier that is shown.

•Port ID—Identifier of port.

•Port Description—Information about the port, including manufacturer,

product name and hardware/software version.

•System Name—Name of system that is published.

•System Description—Description of the network entity (in alpha-numeric

format). This includes the system name and versions of the hardware,

operating system, and networking software supported by the device. The

value equals the sysDescr object.

Table of ContentsLinksys

•Supported System Capabilities—Primary functions of the device. The

capabilities are indicated by two octets. Bits 0 through 7 indicate Other,

Repeater, Bridge, WLAN AP, Router, Telephone, DOCSIS cable device, and

station, respectively. Bits 8 through 15 are reserved.

•Enabled System Capabilities—Primary enabled function(s) of the device.

Management Address

•Address Subtype—Managed address subtype; for example, MAC or IPv4.

•Address—Managed address.

•Interface Subtype—Port subtype.

•Interface Number—Port number.

MED Information

•Capabilities Supported—MED capabilities enabled on the port.

•Current Capabilities—MED TLVs advertised by the port.

•Device Class—LLDP-MED endpoint device class. The possible device

classes are:

•Endpoint Class 1—Indicates a generic endpoint class, offering basic

LLDP services.

•Endpoint Class 2—Indicates a media endpoint class, offering media

streaming capabilities as well as all Class 1 features.

•Endpoint Class 3—Indicates a communications device class, offering

all Class 1 and Class 2 features plus location, 911, Layer 2 switch

support and device information management capabilities.

•PoE Device Type—Port PoE type, for example, powered.

•PoE Power Source—Port’s power source.

•PoE Power Priority—Port’s power priority.

•PoE Power Value—Port’s power value.

•Hardware Revision –Hardware version.

•Firmware Revision—Firmware version.

•Software Revision—Software version.

•Serial Number—Device serial number.

•Manufacturer Name—Device manufacturer name.

•Model Name—Device model name.

•Asset ID—Asset ID.

Location Information

Enter the following data structures in hexadecimal as described in section

10.2.4 of the ANSI-TIA-1057 standard:

•Civic—Civic or street address.

•Coordinates—Location map coordinates—latitude, longitude, and altitude.

•ECS ELIN—Device’s Emergency Call Service (ECS) Emergency Location

Identification Number (ELIN).

•Unknown—Unknown location information.

Network Policy

•Application Type—Network policy application type, for example, Voice.

•VLAN ID—VLAN ID for which the network policy is defined.

•VLAN Type—VLAN type, Tagged or Untagged, for which the network

policy is defined.

•User Priority—Network policy user priority.

•DSCP—Network policy DSCP.

LLDP MED Network Policy

LLDP Media Endpoint Discovery (LLDP-MED) is an extension of LLDP

that provides the following additional capabilities to support media

endpoint devices:

•Enables the advertisement and discovery of network polices for real-time

applications such as voice and/or video.

•Enables discovery of the device location to allow creation of location

databases and, in the case of Voice over Internet Protocol (VoIP),

Emergency Call Service (E-911) by using IP Phone location information.

•Troubleshooting information. LLDP MED sends alerts to network

managers upon:

•Port speed and duplex mode conflicts

•QoS policy misconfigurations

Table of ContentsLinksys

Setting LLDP MED Network Policy

An LLDP-MED network policy is a related set of configuration settings for

a specific real-time application such as voice, or video. A network policy, if

configured, can be included in the outgoing LLDP packets to the attached

LLDP media endpoint device. The media endpoint device must send its traffic

as specified in the network policy it receives. For example, a policy can be

created for VoIP traffic that instructs VoIP phone to:

•Send voice traffic on VLAN 10 as tagged packet and with 802.1p priority 5.

•Send voice traffic with DSCP 46.

Network policies are associated with ports by using the LLDP MED Port Settings

page. An administrator can manually configure one or more network policies

and the interfaces where the policies are to be sent. It is the administrator’s

responsibility to manually create the VLANs and their port memberships

according to the network policies and their associated interfaces.

In addition, an administrator can instruct the device to automatically generate

and advertise a network policy for voice application based on the voice VLAN

maintained by the device. Refer the Auto Voice VLAN section for details on

how the device maintains its voice VLAN.

To define an LLDP MED network policy:

STEP 1 Click Configuration > Port Management > LLDP MED Network.

This page contains previously-created network policies.

STEP 2 When Network Policy for Voice Application is enabled, the device

automatically generates and advertises a network policy with the

current voice VLAN configuration. Go to Voice VLAN > Feature

Configuration page to configure the voice VLAN.

STEP 3 Click Apply to add this setting to the Running Configuration file.

STEP 4 To define a new policy, click Add.

STEP 5 Enter the values:

•Network Policy Number—Select the number of the policy to be created.

•Application—Select the type of application (type of traffic) for which the

network policy is being defined.

•VLAN ID—Enter the VLAN ID to which the traffic must be sent.

•VLAN Tag—Select whether the traffic is Tagged or Untagged.

•Layer 2 Priority—Select the traffic priority applied to traffic defined by

this network policy. This is the CoS value.

•DSCP Value—Select the DSCP value to associate with application data

sent by neighbors. This informs them how they must mark the application

traffic they send to the device.

STEP 6 Click Apply. The network policy is defined.

NOTE:

You must manually configure the interfaces to include the desired

manually-defined network policies for the outgoing LLDP packets using the

LLDP MED Port Settings.

Table of ContentsLinksys

Chapter 6 VLAN Management

VLAN Management

This section covers the following topics:

•Overview

•VLANs

•VLAN Groupss

•Voice VLAN

Overview

A VLAN is a logical group of ports that enables devices associated with it to

communicate with each other over the Ethernet MAC layer, regardless of the

physical LAN segment of the bridged network to which they are connected.

VLAN Description

Each VLAN is configured with a unique VID (VLAN ID) with a value from 1 to

4094. A port on a device in a bridged network is a member of a VLAN if it can

send data to and receive data from the VLAN. A port is an untagged member

of a VLAN if all packets destined for that port into the VLAN have no VLAN tag.

A port is a tagged member of a VLAN if all packets destined for that port into

the VLAN have a VLAN tag. A port can be a member of one untagged VLAN and

can be a member of several tagged VLANs.

A port in VLAN Access Mode can be part of only one VLAN. If it is in Trunk Mode,

the port can be part of one or more VLANs.

VLANs address security and scalability issues. Traffic from a VLAN stays

within the VLAN, and terminates at devices in the VLAN. It also eases network

configuration by logically connecting devices without physically relocating

those devices.

If a frame is VLAN-tagged, a four-byte VLAN tag is added to each Ethernet

frame. The tag contains a VLAN ID between 1 and 4094, and a VLAN Priority Tag

(VPT) between 0 and 7. See Quality of Service for details about VPT.

When a frame enters a VLAN-aware device, it is classified as belonging to a

VLAN, based on the four-byte VLAN tag in the frame.

If there is no VLAN tag in the frame or the frame is priority-tagged only,

the frame is classified to the VLAN based on the PVID (Port VLAN Identifier)

configured at the ingress port where the frame is received.

The frame is discarded at the ingress port if Ingress Filtering is enabled and the

ingress port is not a member of the VLAN to which the packet belongs. A frame

is regarded as priority-tagged only if the VID in its VLAN tag is 0.

Frames belonging to a VLAN remain within the VLAN. This is achieved by

sending or forwarding a frame only to egress ports that are members of the

target VLAN. An egress port may be a tagged or untagged member of a VLAN.

The egress port peforms the following actions:

The egress port:

•Adds a VLAN tag to the frame if the egress port is a tagged member of the

target VLAN, and the original frame does not have a VLAN tag.

•Removes the VLAN tag from the frame if the egress port is an untagged

member of the target VLAN, and the original frame has a VLAN tag.

VLAN Roles

VLANs function at Layer 2. All VLAN traffic (Unicast/Broadcast/ Multicast)

remains within its VLAN. Devices attached to different VLANs do not have direct

connectivity to each other over the Ethernet MAC layer. Devices from different

VLANs can communicate with each other only through Layer 3 routers. An IP

router, for example, is required to route IP traffic between VLANs if each VLAN

represents an IP subnet.

The IP router might be a traditional router, where each of its interfaces

connects to only one VLAN. Traffic to and from a traditional IP router must be

VLAN untagged. The IP router can be a VLAN-aware router, where each of its

interfaces can connect to one or more VLANs. Traffic to and from a VLAN-aware

IP router can be VLAN tagged or untagged.

Adjacent VLAN-aware devices exchange VLAN information with each other by

using Generic VLAN Registration Protocol (GVRP). As a result, VLAN information

is propagated through a bridged network.

Some VLANs can have additional roles, including:

•Voice VLAN—For more information refer to Voice VLAN.

Table of ContentsLinksys

•Guest VLAN—For more information refer to Security: Network Access

Control.

•Default VLAN—For more information refer to VLANs.

•Management VLAN—For more information refer to the IPv4 Interface page

VLANs

This section describes the GUI pages used to configure various types of

VLANs. This section describes the following processes:

•VLAN Configuration Workflow

•Default VLAN Settings

•VLANs - Creating VLANs

•Interface Settings

•VLAN Membership

•Join VLAN

VLAN Configuration Workflow

To configure VLANs:

If required, change the default VLAN by using the VLAN

Management section.

Create the required VLANs by using the VLANs section.

Set the desired VLAN-related configuration for portsusing the

Interfaces section.

Assign interfaces to VLANs by using the Configuring Port to VLAN section

or the Configuring VLAN Membership section.

View the current VLAN port membership for all the interfaces in the

Configuring VLAN Membership section.

If required, configure VLAN groups as described in the MAC-based

Groups and Protocol-based VLANs sections.

Default VLAN Settings

When using factory default settings, the device automatically creates VLAN 1 as

the default VLAN, the default interface status of all ports is Trunk, and all ports

are configured as untagged members of the default VLAN.

The default VLAN has the following characteristics:

•It is distinct, non-static/non-dynamic, and all ports are untagged

members by default.

•It cannot be deleted.

It cannot be given a label.

•It cannot be used for any special role, such as unauthenticated VLAN or

Voice VLAN. This is only relevant for OUI-enabled voice VLAN.

•If a port is no longer a member of any VLAN, the device automatically

configures the port as an untagged member of the default VLAN. A port

is no longer a member of a VLAN if the VLAN is deleted or the port is

removed from the VLAN.

•RADIUS servers cannot assign the default VLAN to 802.1x supplicants by

using Dynamic VLAN Assignment.

When the VID of the default VLAN is changed, the device performs the

following on all the ports in the VLAN, after saving the configuration and

rebooting the device:

•Removes VLAN membership of the ports from the original default VLAN

(takes effect after reboot).

•Changes the PVID (Port VLAN Identifier) of the ports to the VID of the new

default VLAN.

•The original default VLAN ID is removed from the device. To be used, it

must be recreated.

•Adds the ports as untagged VLAN members of the new default VLAN.

To change the default VLAN:

STEP 1 Click Configuration > VLAN Management > VLANs.

STEP 2 Enter the value for the following field:

•Current Default VLAN ID—Displays the current default VLAN ID.

•Default VLAN ID After Reboot—Enter a new VLAN ID to replace the

default VLAN ID after reboot.

STEP 3 Click Apply.

STEP 4 Click Quick Start > Save and save the Running Configuration to the

Startup Configuration.

The Default VLAN ID After Reset becomes the Current Default VLAN ID after

you reboot the device.

Table of ContentsLinksys

VLANs - Creating VLANs

You can create a VLAN, but this has no effect until the VLAN is attached to at

least one port, either manually or dynamically. Ports must always belong to

one or more VLANs.

The Smart device supports up to 128 VLANs, including the default VLAN.

Each VLAN must be configured with a unique VID with a value from 1 to 4094.

The device reserves VID 4095 as the Discard VLAN and VID 4094 for 802.1x. All

packets classified to the Discard VLAN are discarded at ingress, and are not

forwarded to a port.

The VLANs page enables you to change the default VLAN and create a new

VLAN. To change add a VLAN, do the following:

STEP 1 Click Configuration > VLAN Management > VLANs.

The currently-defined VLANs are displayed.

STEP 2 Click Add to add one or more new VLANs.

The page enables the creation of either a single VLAN or a range of VLANs.

STEP 3 Enter the following fields for the new VLANs.

•VLAN—Select one of the following options:

•Single VLAN—Select to create a single VLAN .

•Range of VLANs—Select to create a range of VLANs and specify

the range of VLANs to be created by entering the Starting VID and

Ending VID, inclusive. When using the Range function, the maximum

number of VLANs you can create at one time is 100.

•VLAN ID—Enter a VLAN ID .

•VLAN Name—Enter a VLAN name .

•VLAN ID Range—Enter a range of VLANs .

STEP 4 Click Apply to create the VLAN(s).

Interfaces

The Interface Settings page displays and enables configuration of VLAN-

related parameters for all interfaces.

To configure the VLAN settings:

STEP 1 Click Configuration > VLAN Management > Interface Settings.

STEP 2 Select an interface type (Port or LAG), and click Search. Ports or LAGs

and their VLAN Membership are displayed.

STEP 3 To configure a Port or LAG, select it and click Edit.

NOTE:

To add a port or LAG to a VLAN, click Join VLAN. The Join VLAN page

is displayed.

This page is described below.

STEP 4 Enter the values for the following fields:

•Interface—Select a Port/LAG.

•Interface VLAN Mode—Select the interface mode for the VLAN. The

options are:

•Access—The interface is an untagged member of a single VLAN. A

port configured in this mode is known as an access port.

•Trunk—The interface is an untagged member of one VLAN at most,

and is a tagged member of zero or more VLANs. A port configured in

this mode is known as a trunk port.

•General Port—The interface can support all functions as defined

in the IEEE 802.1q specification. The interface can be a tagged or

untagged member of one or more VLANs.

•PVID—Enter the Port VLAN ID (PVID) of the VLAN to which incoming

untagged and priority tagged frames are classified. The possible values

are1 to 4094.

•Acceptable Frame Type—Select the type of frame that the interface can

receive. Frames that are not of the configured frame type are discarded

at ingress. These frame types are only available in General mode. Possible

values are:

•Admit All—The interface accepts all types of frames: untagged

frames, tagged frames, and priority tagged frames.

Table of ContentsLinksys

•Admit Tagged Only—The interface accepts only tagged frames.

•Admit Untagged Only—The interface accepts only untagged and

priority frames.

•Ingress Filtering—(Available only in General mode) Select to enable ingress

filtering. When an interface is ingress filtering enabled, the interface discards

all incoming frames that are classified as VLANs of which the interface is not

a member. Ingress filtering can be disabled or enabled on general ports. It is

always enabled on access ports and trunk ports.

STEP 5 Click Apply. The parameters are written to the Running

Configuration file.

Join VLAN

When a port is forbidden default VLAN membership, that port is not allowed

membership in any other VLAN. An internal VID of 4095 is assigned to the port.

To forward packets properly, intermediate VLAN-aware devices that carry VLAN

traffic along the path between end nodes must be manually configured.

Untagged port membership between two VLAN-aware devices with no

intervening VLAN-aware devices, must be to the same VLAN. In other words,

the PVID on the ports between the two devices must be the same if the ports

are to send and receive untagged packets to and from the VLAN. Otherwise,

traffic might leak from one VLAN to another.

Frames that are VLAN-tagged can pass through other network devices that

are VLAN-aware or VLAN-unaware. If a destination end node is VLAN-unaware,

but is to receive traffic from a VLAN, then the last VLAN-aware device (if there

is one), must send frames of the destination VLAN to the end node untagged.

To add a port to a VLAN:

STEP 1 Click Configuration > VLAN Management > Interface Settings.

STEP 2 Select an interface type (Port or LAG), and click Search. Ports or LAGs

and their VLAN Membership are displayed.

STEP 3 To add a Port or LAG to a VLAN, select it and click Join VLAN.

STEP 4 Enter the following fields:

•VLAN Mode—Select the interface mode for the VLAN. The options are:

•Access—The interface is an untagged member of a single VLAN. A

port configured in this mode is known as an access port.

•Trunk—The interface is an untagged member of one VLAN at most,

and is a tagged member of zero or more VLANs. A port configured in

this mode is known as a trunk port.

•General Port—The interface can support all functions as defined

in the IEEE 802.1q specification. The interface can be a tagged or

untagged member of one or more VLANs.

•Tagging:

•Forbidden—The interface is not allowed to join the VLAN even from

GVRP registration. When a port is not a member of any other VLAN,

enabling this option on the port makes the port part of internal VLAN

4095 (a reserved VID).

•Excluded—The interface is currently not a member of the VLAN.

This is the default for all the ports and LAGs when the VLAN is newly

created.

•Tagged—The interface is a tagged member of the VLAN.

•Untagged—The interface is an untagged member of the VLAN.

Frames of the VLAN are sent untagged to the interface VLAN.

•PVID—Port PVID is set to this VLAN. If the interface is in access mode

or trunk mode, the device automatically makes the interface an

untagged member of the VLAN. If the interface is in general mode,

you must manually configure VLAN membership.

STEP 5 Click Apply. The port is added to the VLAN and the settings are

written to the Running Configuration file.

VLAN Memberships

The VLAN Memberships page displays the VLAN memberships of the ports in

various presentations. You can use them to add memberships to or remove

memberships from the VLANs.

When a port is forbidden default VLAN membership, that port is not allowed

membership in any other VLAN. An internal VID of 4095 is assigned to the port.

To forward packets properly, intermediate VLAN-aware devices that carry

VLAN traffic along the path between end nodes must be manually configured.

Untagged port membership between two VLAN-aware devices with no

intervening VLAN-aware devices, must be to the same VLAN. In other words,

the PVID on the ports between the two devices must be the same if the ports

Table of ContentsLinksys

are to send and receive untagged packets to and from the VLAN. Otherwise,

traffic might leak from one VLAN to another.

Frames that are VLAN-tagged can pass through other network devices that

are VLAN-aware or VLAN-unaware. If a destination end node is VLAN-unaware,

but is to receive traffic from a VLAN, then the last VLAN-aware device (if there

is one), must send frames of the destination VLAN to the end node untagged.

Use the VLAN Memberships page to display and configure the ports within a

specific VLAN.

To assign a port to one or more VLANs:

STEP 1 Click Configuration > VLAN Management > VLAN Memberships.

STEP 2 Select VLAN ID and interface type (Port or LAG), and click Search.

Configure the following fields for the interfaces of the selected type:

•Interface—Port/LAG ID.

•PVID—Port PVID is set to this VLAN. If the interface is in access mode or

trunk mode, the device automatically makes the interface an untagged

member of the VLAN. If the interface is in general mode, you must

manually configure VLAN membership.

•Mode—Interface VLAN mode that was selected in the Interface

Settings page.

•Access-Select to make the interface an access interface on this VLAN.

•Trunk-Select to make the interface a trunk interface on this VLAN.

•General Port—The interface can support all functions as defined

in the IEEE 802.1q specification. The interface can be a tagged or

untagged member of one or more VLANs.

•Forbidden—The interface is not allowed to join the VLAN even from GVRP

registration. When a port is not a member of any other VLAN, enabling

this option on the port makes the port part of internal VLAN 4095 (a

reserved VID).

•Excluded—The interface is currently not a member of the VLAN. This is

the default for all the ports and LAGs when the VLAN is newly created.

•Tagged—The interface is a tagged member of the VLAN. This is not

relevant for Access ports.

•Untagged—The interface is an untagged member of the VLAN. Frames of

the VLAN are sent untagged to the interface VLAN. This is not relevant for

Access ports.

STEP 3 Click Apply. The settings are modified and written to the Running

Configuration file.

VLAN Groups

This section describes how to configure MAC-based VLAN groups.

VLAN groups classify packets into VLANs based on their MAC addresses or

protocol ID.

VLAN groups can be used to separate traffic into different VLANs for security

and/or load balancing.

If several classifications schemes are defined, packets are assigned to a VLAN

in the following order:

•TAG—If the packet is tagged, the VLAN is taken from the tag.

•MAC-Based VLAN—If a MAC-based VLAN has been defined, the VLAN is

taken from the source MAC-to-VLAN mapping of the ingress interface.

•PVID—VLAN is taken from the port default VLAN ID.

MAC-based Group

MAC-based VLAN classification enable packets to be classified according to their

source MAC address. You can then define MAC-to-VLAN mapping per interface.

You can define several MAC-based VLAN groups, which each group

containing different MAC addresses.

These MAC-based groups can be assigned to specific ports/LAGs. MAC-based

VLAN groups cannot contain overlapping ranges of MAC addresses on the

same port.

The following table describes the availability of MAC-based VLAN groups in

various SKUs:

Table 1 MAC-Based VLAN Group Availability

SKU System Mode MAC-based VLAN Groups Supported

Smart Layer 2 Yes

Managed Layer 2 Yes

Layer 3 No

Table of ContentsLinksys

Workflow

To define a MAC-based VLAN group:

Assign a MAC address to a VLAN group ID (using the MAC-Based

Groups page).

For each required interface:

a. Assign the VLAN group to a VLAN (using the Mac-Based VLAN

page). The interfaces must be in General mode.

b. If the interface does not belong to the VLAN, manually assign it to

the VLAN using the VLAN Membership page.

MAC-based VLAN

See Table 1 for a description of the availability of this feature.

To assign a MAC address to a VLAN Group:

STEP 1 Click Configuration > VLAN Management > VLAN Groups > MAC-

Based Group.

STEP 2 Click Add.

STEP 3 Enter the values for the following fields:

•Group ID—Enter a user-created VLAN group ID number.

•MAC Address—Enter a MAC address to be assigned to a VLAN group.

NOTE This MAC address cannot be assigned to any other VLAN

group.

•Prefix Mask—Enter one of the following:

•Host—Source host of the MAC address

•Length—Prefix of the MAC address

STEP 4 Click Apply. The MAC address is assigned to a VLAN group.

MAC-based VLAN Per Interface

See Table 1 for a description of the availability of this feature.

Ports/LAGs must be in General mode.

To assign a MAC-based VLAN group to a VLAN on an interface:

STEP 1 Click Configuration > VLAN Management > LAN Groups > MAC-

Based VLAN.

STEP 2 Click Add.

STEP 3 Enter the values for the following fields:

•Interface—Enter a general interface (port/LAG) through which traffic is

received.

•Group ID—Select a VLAN group, defined in the MAC-Based Groups page.

•VLAN ID—Select the VLAN to which traffic from the VLAN group

is forwarded.

STEP 4 Click Apply to set the mapping of the VLAN group to the VLAN. This

mapping does not bind the interface dynamically to the VLAN; the

interface must be manually added to the VLAN.)

Voice VLAN

In a LAN, voice devices, such as IP phones, VoIP endpoints, and voice systems

are placed into the same VLAN. This VLAN is referred as the voice VLAN. If the

voice devices are in different voice VLANs, IP (Layer 3) routers are needed to

provide communication.

Overview

This section covers the following topics:

•Auto Voice VLAN

•Voice VLAN QoS

•Voice VLAN Constraints

•Voice VLAN Workflows

Auto Voice VLAN

The device supports the Telephony OUI (Organization Unique Identifier) voice

VLAN mode. The two modes affect how voice VLAN and/or voice VLAN port

memberships are configured.

In Telephony OUI mode, the voice VLAN must be a manually-configured VLAN,

and cannot be the default VLAN.

When the device is in Telephony OUI mode and a port is manually configured

as a candidate to join the voice VLAN, the device dynamically adds the port

to the voice VLAN if it receives a packet with a source MAC address matching

one of the configured telephony OUIs. An OUI is the first three bytes of an

Table of ContentsLinksys

Ethernet MAC address. For more information about Telephony OUI, see

Telephony OUI.

Voice End-Points

To have a voice VLAN work properly, the voice devices, such as IP phones

and VoIP endpoints, must be assigned to the voice VLAN where it sends and

receives its voice traffic. Some of the possible scenarios are as follows:

•A phone/endpoint may be statically configured with the voice VLAN.

•A phone/endpoint may obtain the voice VLAN in the boot file it

downloads from a TFTP server. A DHCP server may specify the boot file

and the TFTP server when it assigns an IP address to the phone.

•A phone/endpoint may obtain the voice VLAN information from LLDP-MED

advertisements it receives from their neighbor voice systems and switches.

You can create a network policy manually or enable the device to

automatically generate a network policy, based on a voice VLAN

configuration.

The device expects the attaching voice devices to send voice VLAN, tagged

packets. On ports where the voice VLAN is the native VLAN or that is

configured with auto voice VLAN by Telephony OUI, voice VLAN untagged

packets are possible.

Voice VLAN QoS

The device can advertise the CoS/802.1p and DSCP settings of the voice VLAN

by using LLDP-MED Network policies. You can create your network policy

manually or enable the device to automatically generate the network policy

based on your voice VLAN configuration. MED-supported devices must send

their voice traffic with the same CoS/802.1p and DSCP values, as received with

the LLDP- MED response.

You can disable the automatic update between Voice VLAN and LLDP-MED

and use his own network policies.

Working with the OUI mode, the device can additionally configure the

mapping and remarking (CoS/802.1p) of the voice traffic based on the OUI.

By default, all interfaces are CoS/802.1p trusted. The device applies the quality

of service based on the CoS/802.1p value found in the voice stream. In Auto

Voice VLAN, you can override the value of the voice streams using advanced

QoS. For Telephony OUI voice streams, you can override the quality of service

and optionally remark the 802.1p of the voice streams by specifying the desired

CoS/802.1p values and using the remarking option under Telephony OUI.

Voice VLAN Constraints

The following constraints exist:

•Only one Voice VLAN is supported.

•A VLAN that is defined as a Voice VLAN cannot be removed.

In addition the following constraints are applicable for Telephony OUI:

•The Voice VLAN cannot be VLAN1 (the default VLAN).

•The Voice VLAN QoS decision has priority over any other QoS decision.

•A new VLAN ID can be configured for the Voice VLAN only if the current

Voice VLAN does not have candidate ports.

•The interface VLAN of a candidate port must be in General or Trunk mode.

•The Voice VLAN QoS is applied to candidate ports that have joined the

Voice VLAN, and to static ports.

•The voice flow is accepted if the MAC address can be learned by the

Forwarding Database (FDB). (If there is no free space in FDB, no action

occurs).

Feature Configuration

To configure Auto Voice VLAN:

STEP 1 Click Configuration > VLAN Management > Voice VLAN > Feature

Configuration.

STEP 2 Enter the following to configure Voice VLAN:

•Voice VLAN ID—Enter the identifier of the current voice VLAN

•CoS/802.1p—Select the CoS/802.1p value to be used by the LLDP-MED as

a voice network policy.

STEP 3 Enter the following to configure telephone OUI voice VLAN:

•Telephone OUI Voice VLAN—Check to enable automatically adding ports

to voice VLAN when OUI packets are received.

•Remark CoS/802.1p—Select the enable remarking packets with the CoS/

802.1p value.

Table of ContentsLinksys

•Aging Time—Enter the time delay to remove a port from the voice VLAN

after all of the MAC addresses of the phones detected on the ports have

aged out.

STEP 4 Click Apply to save the settings to the Running Configuration file.

Refer to Administration > Discovery > LLDP > LLDP MED Network Policy to

enable automatic generation of network policy for voice.

To view or add a new OUI:

STEP 1 Click Configuration > VLAN Management > Voice VLAN > Feature

Configuration.

The Telephony OUI page displays the configured OUIs.

STEP 2 Click Add to add a new OUI.

Enter the fields:

•Telephony OUI—First six digits of the MAC address that are reserved for

OUIs.

•Description—User-assigned OUI description.

NOTE:

Click Restore to delete all of the user-created OUIs, and leave only the

default OUIs in the table. The OUI information may not be accurate until

the restoration is completed. This may take several seconds. After several

seconds have passed, refresh the page by exiting it and re-entering it.

To delete all the OUIs, select the top checkbox. All the OUIs are selected

and can be deleted by clicking Delete. If you then click Restore, the system

recovers the known OUIs.

STEP 3 Click Apply. The OUI is added to the Telephony OUI Table.

Telephone OUI Interfaces

QoS attributes can be assigned per port to the voice packets in one of the

following modes:

•All—Quality of Service (QoS) values configured to the Voice VLAN are

applied to all of the incoming frames that are received on the interface

and are classified to the Voice VLAN.

•Telephony Source MAC Address (SRC)—The QoS values configured for

the Voice VLAN are applied to any incoming frame that is classified to the

Voice VLAN and contains an OUI in the source MAC address that matches

a configured telephony OUI.

Use the Telephony OUI Interface page to add an interface to the voice VLAN on

the basis of the OUI identifier and to configure the OUI QoS mode of voice VLAN.

To configure Telephony OUI on an interface:

STEP 1 Click Configuration > VLAN Management > Voice VLAN > Telephony

OUI Interfaces.

Voice VLAN OUI parameters for all interfaces are displayed.

STEP 2 To configure an interface to be a candidate port of the telephony

OUI-based voice VLAN, click Edit.

STEP 3 Enter the values for the following fields:

•Interface—Select an interface.

•Telephony OUI VLAN—If enabled, the interface is a candidate port of the

telephony OUI based voice VLAN. When packets that match one of the

configured telephony OUI are received, the port is added to the voice VLAN.

•QoS Mode—Select one of the following options:

•All—QoS attributes are applied on all packets that are classified to

the Voice VLAN.

•Telephony Source MAC Address—QoS attributes are applied only on

packets from IP phones.

STEP 4 Click Apply. The OUI Interface is enabled.

Table of ContentsLinksys

Chapter 7 Spanning Tree

Management

Spanning Tree Management

This section describes the Spanning Tree Protocol (STP) (IEEE802.1D, IEEE802.1s

and IEEE802.1w) and covers the following topics:

•Overview

•Spanning Tree

•STP Interfaces

•RSTP Interfaces

•MSTP Properties

•VLAN to MSTP

•MSTP Instance Status

•MSTP Instance Interface

Overview

STP protects a Layer 2 broadcast domain from broadcast storms by selectively

setting links to standby mode to prevent loops. In standby mode, these links

temporarily stop transferring user data. After the topology changes so that

the data transfer is made possible, the links are automatically re-activated.

Loops occur when alternate routes exist between hosts. Loops in an extended

network can cause switches to forward traffic indefinitely, resulting in

increased traffic load and reduced network efficiency.

STP provides a tree topology for any arrangement of switches and

interconnecting links, by creating a unique path between end stations on a

network, and thereby eliminating loops.

The device supports the following Spanning Tree Protocol versions:

•Classic STP – Provides a single path between any two end stations,

avoiding and eliminating loops.

•Rapid STP (RSTP) – Detects network topologies to provide faster

convergence of the spanning tree. This is most effective when the

network topology is naturally tree-structured, and therefore faster

convergence might be possible. RSTP is enabled by default.

Spanning Tree

The Spanning Tree page contains parameters for enabling STP or RSTP. Use

the STP Interface page and RSTP Interface page to configure ports with these

modes, respectively.

To set the STP status and global settings, do the following:

STEP 1 Click Configuration > Spanning Tree Management > Spanning Tree.

STEP 2 Enter the parameters.

Global Settings

•Spanning Tree—Select to enable STP on the device.

•Spanning Tree Mode—Select an STP mode—Classic STP or Rapid STP.

•Path Cost Default Values—Selects the method used to assign default path

costs to the STP ports. The default path cost assigned to an interface varies

according to the selected method.

•Short—Specifies the range 1 through 65,535 for port path costs.

•Long—Specifies the range 1 through 200,000,000 for port path costs.

•BPDU Handling—Select how Bridge Protocol Data Unit (BPDU) packets are

managed when STP is disabled on the port or the device. BPDUs are used

to transmit spanning tree information.

•Filtering—Filters BPDU packets when Spanning Tree is disabled on an

interface.

•Flooding—Floods BPDU packets when Spanning Tree is disabled on an

interface.

Bridge Configuration

•Priority—Set the global priority value. The priority value influences the

port choice when a bridge has two ports connected in a loop. The priority

is a value from 0 to 240, set in increments of 16.

•Hello Time—Set the interval (in seconds) that a root bridge waits

between configuration messages.

Table of ContentsLinksys

•Maximum Age—Set the interval (in seconds) that the device can wait

without receiving a configuration message, before attempting to redefine

its own configuration.

•Forward Delay—Set the interval (in seconds) that a bridge remains in a

learning state before forwarding packets.

Status Designated Root

•Bridge ID—The combined bridge priority and the MAC address of

the device.

•Root Bridge ID—The combined root bridge priority and the MAC

•address of the root bridge.

•Root Port—The port that offers the lowest cost path from this bridge to

the root bridge. (This is significant when the bridge is not the root.)

•Root Path Cost—The cost of the path from this bridge to the root.

•Topology Changes Count—The total number of STP topology changes

that have occurred.

•Last Topology Change—The time interval that elapsed since the last

topology change occurred. The time appears in a days/hours/minutes/

seconds format.

STEP 3 Click Apply. The STP Global settings are written to the Running

Configuration file.

STP Interfaces

The STP Interface page enables you to configure STP on a per-port basis, and to

view the information learned by the protocol, such as the designated bridge.

The defined configuration entered is valid for all flavors of the STP protocol. To

configure STP on an interface, do the following:

STEP 1 Click Configuration > Spanning Tree Management > STP Interfaces.

STEP 2 Select an interface type and click Edit.

STEP 3 Enter the parameters.

•STP—Select to enable STP on the port.

•BPDU Handling—Select how BPDU packets are managed when STP is

disabled on the port or the device. BPDUs are used to transmit spanning

tree information.

•Use Global Settings—Select to use the settings defined in the

Spanning Tree page.

•Filtering—Filters BPDU packets when Spanning Tree is disabled on an

interface.

•Flooding—Floods BPDU packets when Spanning Tree is disabled on

an interface.

•Path Cost—Set the port contribution to the root path cost or use the

default cost generated by the system.

•Priority—Select the priority value of the port. The priority value

influences the port choice when a bridge has two ports connected in a

loop. The priority is a value from 0 to 240, set in increments of 16.

•Port State—Displays the current STP state of a port.

•Disabled—STP is currently disabled on the port. The port forwards

traffic while learning MAC addresses.

•Blocking—The port is currently blocked, and cannot forward traffic

(with the exception of BPDU data) or learn MAC addresses.

•Listening—The port is in Listening Mode. The port cannot forward

traffic, and cannot learn MAC addresses.

•Learning—The port is in Learning Mode. The port cannot forward

traffic, but it can learn new MAC addresses.

•Forwarding—The port is in Forwarding Mode. The port can forward

traffic and learn new MAC addresses.

•Designated Bridge ID—Displays the priority and interface of the

selected port.

•Designated Port ID—Displays the priority and interface of the selected

port.

•Designated Cost—Displays the cost of the port participating in the

STP topology. Ports with a lower cost are less likely to be blocked if

STP detects loops.

STEP 4 Click Apply. The interface settings are written to the Running

Configuration file.

Table of ContentsLinksys

RSTP Interfaces

Rapid Spanning Tree Protocol (RSTP) enables a faster STP convergence

without creating forwarding loops.

The RSTP Interfaces page enables you to configure RSTP per port. Any

configuration that is done on this page is active when the global STP mode is

set to RSTP.

To enter RSTP settings, do the following:

STEP 1 Click Configuration > Spanning Tree Management> RSTP Interfaces.

STEP 2 Select a port.

STEP 3 Select an interface, and click Edit.

STEP 4 Enter the Interface Settings.

•Point to Point Mode—Define the point-to-point link status. Ports

defined as full duplex are considered point-to-point port links.

•Enable—This port is an RSTP edge port when this feature is enabled,

and is brought to Forwarding Mode quickly (usually within 2 seconds).

•Disable—The port is not considered point-to-point for RSTP

purposes, which means that STP works on it at regular speed, as

opposed to high speed.

•Auto—Automatically determines the device status by using

RSTP BPDUs.

•Edge Port Mode—Enables or disables Fast Link on the port. If Fast Link

Mode is enabled on a port, the port is automatically set to forwarding

state when the port link is up. Fast Link optimizes the STP protocol

convergence. The options are:

•Enable—Enables Fast Link immediately.

•Disable—Disables Fast Link.

•Auto—Enables Fast Link a few seconds after the interface becomes

active. This allows STP to resolve loops before enabling Fast Link.

NOTE It is recommended to set the value to Auto so that the device sets the

port to fast link mode if a host is connected to it, or sets it as a regular

STP port if connected to another device. This helps avoid loops.

•STP Mode—Select either STP or RSTP.

•Point to Point Status—Displays the point-to-point operational status if

the Point to Point Administrative Status is set to Auto.

•Port Role—Displays the role of the port that was assigned by STP to

provide STP paths. The possible roles are as follows:

•Root—Lowest cost path to forward packets to the root bridge.

•Designated—The interface through which the bridge is connected

to the LAN, which provides the lowest cost path from the LAN to the

root bridge.

•Alternate—Provides an alternate path to the root bridge from the

root interface.

•Backup—Provides a backup path to the designated port path toward

the spanning tree leaves. This provides a configuration in which two

ports are connected in a loop by a point-to-point link. Backup ports

are also used when a LAN has two or more established connections

to a shared segment.

•Disabled—The port is not participating in spanning tree.

•Port Status—Displays the RSTP status on the specific port.

•Disabled—STP is currently disabled on the port.

•Blocking—The port is currently blocked, and it cannot forward traffic

or learn MAC addresses.

•Listening—The port is in Listening Mode. The port cannot forward

traffic, and cannot learn MAC addresses.

•Learning—The port is in Learning Mode. The port cannot forward

traffic, however it can learn new MAC addresses.

•Forwarding—The port is in Forwarding Mode. The port can forward

traffic and learn new MAC addresses.

STEP 5 Click Apply. The Running Configuration file is updated.

MSTP Properties

Multiple Spanning Tree Protocol (MSTP) is used to separate the STP port state

between various domains (on different VLANs). For example, while port A is

blocked in one STP instance due to a loop on VLAN A, the same port can be

placed in the Forwarding State in another STP instance. The MSTP Properties

page enables you to define the global MSTP settings.

To configure MSTP:

Table of ContentsLinksys

•Bridge Priority—Set the priority of this bridge for the selected

MST instance.

•Action—Select either add VLAN or remove VLAN

•VLANs—Displays the VLANs mapped to the selected instance. The default

mapping is that all VLANs are mapped to the common and internal

spanning tree (CIST) instance 0).

STEP 8 Click Apply. The MSTP properties are defined, and the Running

Configuration file is updated.

MSTP Instance Status

The MSTP Instance Status page enables you to configure and view parameters

per MST instance. This is the per-instance equivalent to the Spanning Tree page.

To enter MSTP instance settings:

STEP 1 Click Configuration > Spanning Tree Management > MSTP Instance

Status.

STEP 2 The following parameters are shown.

•Instance ID—Select an MST instance to be displayed and defined.

•Bridge Priority—Set the priority of this bridge for the selected

MST instance.

•Designated Root Bridge ID—Displays the priority and MAC address of the

Root Bridge for the MST instance.

•Root Port—Displays the root port of the selected instance.

•Root Path Cost—Displays the root path cost of the selected instance.

•Bridge ID—Displays the bridge priority and the MAC address of this

device for the selected instance.

•Remaining Hops—Displays the number of hops remaining to the next

destination.

MSTP Instance Interface

The MSTP Instance Interface page enables you to configure the port MSTP

settings for every MST instance, and to view information that has currently been

learned by the protocol, such as the designated bridge per MST instance.

To configure the ports in an MST instance:

STEP 1 Click Configuration > Spanning Tree Management > MSTP Instance

Interface .

STEP 2 Enter the parameters.

•MSTP Instance—Select the MSTP instance to be configured.

•Interface Type—Select whether to display the list of ports or LAGs.

STEP 3 Click Search. The following MSTP parameters for the interfaces on

the instance are displayed:

•Interface—Select the interface for which the MSTI settings are to be

defined. Interface Priority—Set the port priority for the specified interface

and MST instance.

•Path Cost—Enter the port contribution to the root path cost in the User

Defined textbox or select Use Default to use the default value.

•Port State—Displays the MSTP status of the specific port on a specific

MST instance. The parameters are defined as:

•Disabled—STP is currently disabled.

•Blocking—The port on this instance is currently blocked, and cannot

forward traffic (with the exception of BPDU data) or learn MAC

addresses.

•Listening—The port on this instance is in Listening mode. The port

cannot forward traffic, and cannot learn MAC addresses.

•Learning—The port on this instance is in Learning mode. The port

cannot forward traffic, but it can learn new MAC addresses.

•Forwarding—The port on this instance is in Forwarding mode. The

port can forward traffic and learn new MAC addresses.

•Boundary—The port on this instance is a boundary port. It inherits

its state from instance 0 and can be viewed on the STP Interface

Settings page.

•Port Role—Displays the port or LAG role, per port or LAG per instance,

assigned by the MSTP algorithm to provide STP paths:

•Root—Forwarding packets through this interface provides the lowest

cost path for forwarding packets to the root device.

•Designated—The interface through which the bridge is connected

to the LAN, which provides the lowest root path cost from the LAN to

the Root Bridge for the MST instance.

Table of ContentsLinksys

•Alternate—The interface provides an alternate path to the root

device from the root interface.

•Backup—The interface provides a backup path to the designated

port path toward the Spanning Tree leaves. Backup ports occur

when two ports are connected in a loop by a point-to-point link.

Backup ports also occur when a LAN has two or more established

connections to a shared segment.

•Disabled—The interface does not participate in the Spanning Tree.

•Boundary—The port on this instance is a boundary port. It inherits

its state from instance 0 and can be viewed on the STP Interface

Settings page.

•Mode—Displays the current interface Spanning Tree mode.

•If the link partner is using MSTP or RSTP, the displayed port mode

is RSTP.

•If the link partner is using STP, the displayed port mode is STP.

•Type—Displays the MST type of the port.

•Boundary—A Boundary port attaches MST bridges to a LAN in

a remote region. If the port is a boundary port, it also indicates

whether the device on the other side of the link is working in RSTP or

STP mode.

•Internal—The port is an internal port.

•Designated Bridge ID—Displays the ID number of the bridge that

connects the link or shared LAN to the root.

•Designated Port ID—Displays the Port ID number on the designated

bridge that connects the link or the shared LAN to the root.

•Designated Cost—Displays the cost of the port participating in the

STP topology. Ports with a lower cost are less likely to be blocked if STP

detects loops.

•Remain Hops—Displays the hops remaining to the next destination.

•Forward Transitions—Displays the number of times the port has changed

from the Forwarding state to the Blocking state.

STEP 4 Select an interface, and click Edit.

STEP 5 Enter the parameters.

STEP 6 Click Apply. The Running Configuration file is updated.

Table of ContentsLinksys

Chapter 8 MAC Address

Management

MAC Address Management

This section describes how to add MAC addresses to the system. It covers the

following topics:

•Dynamic MAC Addresses

•Static MAC Addresses

•Reserved MAC Addresses

There are two types of MAC addresses—static and dynamic. Depending on

their type, MAC addresses are either stored in the Static Address table or in

the Dynamic Address table, along with VLAN and port information.

Static addresses are configured by the user, and therefore, they do not expire.

A new source MAC address that appears in a frame arriving at the device

is added to the Dynamic Address table. This MAC address is retained for a

configurable period of time. If another frame with the same source MAC

address does not arrive at the device before that time period expires, the MAC

entry is aged (deleted) from the table.

When a frame arrives at the device, the device searches for a corresponding/

matching destination MAC address entry in the static or dynamic table. If a

match is found, the frame is marked for egress on the port specified in the

table. If frames are sent to a MAC address that is not found in the tables, they

are transmitted/broadcasted to all the ports on the relevant VLAN. Such

frames are referred to as unknown Unicast frames.

The device supports a maximum of 8K static and dynamic MAC addresses.

Dynamic MAC Addresses

The Dynamic Address Table (bridging table) contains the MAC addresses

acquired by monitoring the source addresses of frames entering the device.

To prevent this table from overflowing, and to make room for new MAC

addresses, an address is deleted if no corresponding traffic is received for a

certain period. This period of time is the aging interval.

Configuring Dynamic MAC Address Aging Time

To configure the aging interval for dynamic addresses, do the following:

STEP 1 Click Configuration > MAC Address Management > Dynamic

MAC Addresses.

STEP 2 Enter Aging Time. The aging time is a value between the user-

configured value and twice that value minus 1. For example, if

you entered 300 seconds, the aging time is between 300 and 599

seconds.

STEP 3 Click Apply. The aging time is updated.To query dynamic addresses,

do the following:

STEP 4 In the Dynamic MAC Address Table block, enter the query criteria:

•VLAN ID—Enter the VLAN ID for which the table is queried.

•MAC Address—Enter the MAC address for which the table is queried.

•Interface—Select the interface for which the table is queried. The query

can search for specific unit/slot, ports, or LAGs.

•Sort By—Select the field for which the table is queried.

STEP 5 Click Search. The Dynamic MAC Address Table is queried and the

results are displayed.To delete all dynamic MAC addresses click Clear.

Static MAC Addresses

Static MAC addresses are assigned to a specific physical interface and VLAN

on the device. If that address is detected on another interface, it is ignored,

and is not written to the address table.

To define a static address:

STEP 1 Click Configuration > MAC Address Management > Static MAC

Addresses.

The Static Addresses page contains the currently defined static addresses.

STEP 2 Click Add.

STEP 3 Enter the parameters.

•VLAN ID—Select the VLAN ID for the port.

Table of ContentsLinksys

•MAC Address—Enter the interface MAC address.

•Interface—Select an interface (unit/slot, port, or LAG) for the entry.

•Status—Select how the entry is treated. The options are:

•Permanent—The system never removes this MAC address. If the

static MAC address is saved in the Startup Configuration, it is retained

after rebooting.

•Delete on reset—The static MAC address is deleted when the device

is reset.

•Delete on timeout—The MAC address is deleted when aging occurs.

•Secure—The MAC address is secure when the interface is in classic

locked mode (see Configuring Port Security).

STEP 4 Click Apply. A new entry appears in the table.

Reserved MAC Addresses

When the device receives a frame with a destination MAC address that belongs

to a reserved range (per the IEEE standard), the frame can be discarded or

bridged. The entry in the Reserved MAC Address Table can either specify the

reserved MAC address or the reserved MAC address and a frame type:

To add an entry for a reserved MAC address:

STEP 1 Configuration > Click MAC Address Tables > Reserved MAC Addresses.

STEP 2 Click Add.

STEP 3 Enter the values for the following fields:

•MAC Address—Select the MAC address to be reserved.

•Frame Type—Select a frame type based on the following criteria:

•Ethernet II—Applies to Ethernet II packets with the specific MAC

address and ethertype.

•LLC—Applies to Logical Link Control (LLC) packets with the specific

MAC address and DSAP-SSAP.

•LLC-SNAP—Applies to Logical Link Control/Sub-Network Access

Protocol (LLC-SNAP) packets with the specific MAC address.

•All—Applies to all packets with the specific MAC address and protocol.

•Action—Select one of the following actions to be taken upon receiving a

packet that matches the selected criteria:

•Bridge—Forward the packet to all VLAN members.

•Discard—Drop the packet.

STEP 4 Click Apply. A new MAC address is reserved.

Table of ContentsLinksys

Chapter 9 Multicast

Multicast

This section describes the Multicast Forwarding feature and covers the

following topics:

•Overview

•Feature Configuration

•IGMP/MLD Snooping

•Multicast Router Ports

•Forward All

•Unregistered Multicast

•IGMP/MLD IP Group Addresses

•MAC Group Address FDB

•IP Group Address FDB

Overview

Multicast forwarding enables one-to-many information dissemination.

Multicast applications are useful for dissemination of information to multiple

clients, where clients do not require reception of the entire content. A typical

application is a cable-TV-like service, where clients can join a channel in the

middle of a transmission, and leave before it ends.

The data is sent only to relevant ports. Forwarding the data only to the relevant

ports conserves bandwidth and host resources on links.

For Multicast forwarding to work across IP subnets, nodes and routers must be

Multicast-capable. A Multicast-capable node must be able to do the following:

•Send and receive Multicast packets.

•Register the Multicast addresses being listened to by the node with

local routers, so that local and remote routers can route the Multicast

packet to the nodes.

Typical Multicast Setup

•While Multicast routers route Multicast packets between IP subnets,

Multicastcapable Layer 2 switches forward Multicast packets to registered

nodes within a LAN or VLAN.

A typical setup involves a router that forwards the Multicast streams between

private and/or public IP networks, a device with Internet Group Membership

Protocol (IGMP) snooping capabilities, and a Multicast client that wants

to receive a Multicast stream. In this setup, the router sends IGMP queries

periodically.

These queries reach the device, which in turn floods the queries to the VLAN,

and also learns the port where there is a Multicast router (Mrouter). When a

host receives the IGMP query message, it responds with an IGMP Join message

saying that the host wants to receive a specific Multicast stream and optionally

from a specific source. The device with IGMP snooping analyzes the Join

messages, and learns that the Multicast stream the host has requested must be

forwarded to this specific port. It then forwards the IGMP Join to the Mrouter

only. Similarly, when the Mrouter receives an IGMP Join message, it learns the

interface from which it received the Join messages that wants to receive a

specific Multicast stream. The Mrouter forwards the requested Multicast stream

to the interface.

In a Layer 2 Multicast service, a Layer 2 switch receives a single frame addressed

to a specific Multicast address. It creates copies of the frame to be transmitted

on each relevant port.

When the device is IGMP snooping-enabled and receives a frame for a Multicast

stream, it forwards the Multicast frame to all the ports that have registered to

receive the Multicast stream using IGMP Join messages.

The device can forward Multicast streams based on one of the following options:

•Multicast MAC Group Address

•IP Multicast Group Address (G)

•A combination of the source IP address (S) and the destination IP

Multicast Group Address (G) of the Multicast packet.

•One of these options can be configured per VLAN.

The system maintains lists of Multicast groups for each VLAN, and this manages

the Multicast information that each port should receive. The Multicast groups

and their receiving ports can be configured statically or learned dynamically

using IGMP snooping.

Table of ContentsLinksys

Multicast registration is the process of listening and responding to Multicast

registration protocols. The available protocols are IGMP for IPv4.

When IGMP snooping is enabled in a device on a VLAN, it analyzes the IGMP

packets it receives from the VLAN connected to the device and Multicast

routers in the network.

When a device learns that a host is using IGMP messages to register to receive

a Multicast stream, optionally from a specific source, the device adds the

registration to its Multicast Forwarding Data Base (MFDB).

•IGMP snooping can effectively reduce Multicast traffic from streaming

bandwidthintensive IP applications. A device using IGMP snooping

only forwards Multicast traffic to the hosts interested in that traffic. This

reduction of Multicast traffic reduces the packet processing at the device,

and also reduces the workload of the end hosts, since they do not have to

receive and filter all of the Multicast traffic generated in the network.

The following versions are supported: IGMP v1/v2/v3.

Multicast Address Properties

Multicast addresses have the following properties:

•Each IPv4 Multicast address is in the address range 224.0.0.0 to

239.255.255.255.

•To map an IP Multicast group address to a Layer 2 Multicast address: for

IPv4, this is mapped by taking the 23 low-order bits from the IPv4 address,

and adding them to the 01:00:5e prefix. By standard, the upper nine bits

of the IP address are ignored, and any IP addresses that only differ in the

value of these upper bits are mapped to the same Layer 2 address, since

the lower 23 bits that are used are identical. For example, 234.129.2.3 is

mapped to a MAC Multicast group address 01:00:5e:01:02:03. Up to 32 IP

Multicast group addresses can be mapped to the same Layer 2 address.

Feature Configuration

The Feature Configuration page enables you to configure the Bridge Multicast

filtering status.

By default, all Multicast frames are flooded to all ports of the VLAN. To

selectively forward only to relevant ports and filter (drop) the Multicast on

the rest of the ports, enable Bridge Multicast filtering status in the Feature

Configuration page.

If filtering is enabled, Multicast frames are forwarded to a subset of the ports in

the relevant VLAN as defined in the Multicast Forwarding Data Base. Multicast

filtering is enforced on all traffic. By default, such traffic is flooded to all relevant

ports, but you can limit forwarding to a smaller subset.

A common way of representing Multicast membership is the (S,G) notation

where S is the (single) source sending a Multicast stream of data, and G is the

IPv4 group address. If a Multicast client can receive Multicast traffic from any

source of a specific Multicast group, this is saved as (*,G).

The following are ways of forwarding Multicast frames:

•MAC Group Address—Based on the destination MAC address in the

Ethernet frame.

NOTE:

One or more IP Multicast group addresses can be mapped to a MAC group

address. Forwarding, based on the MAC group address, can result in an IP

Multicast stream being forwarded to ports that have no receiver for the stream.

•IP Group Address—Based on the destination IP address of the IP packet

(*,G).

•Source Specific IP Group Address—Based on both the destination IP

address and the source IP address of the IP packet (S,G).

By selecting the forwarding mode, you can define the method used by hardware

to identify Multicast flow by one of the following options: MAC Group Address,

IP Group Address, or Source Specific IP Group Address. (S,G) is supported by

IGMPv3, while IGMPv1/2 support only (*.G), which is just the group ID. The device

supports a maximum of 256 static and dynamic Multicast group addresses. To

enable Multicast filtering, and select the forwarding method:

STEP 1 Click Configuration > Multicast > Feature Configuration.

STEP 2 Enter the global parameter:

•Bridge Multicast Filtering—Select to enable filtering of Multicast addresses.

VLAN Settings

•VLAN ID—Select the VLAN ID to set its forwarding method.

•IPv4 Multicast Forwarding—Select one of the following options:

•By MAC Address—Select to enable the MAC address method for

forwarding Multicast packets.

Table of ContentsLinksys

•By IPv4 Group Address—Select to enable the IPv4 group address

method for forwarding Multicast packets.

•By Source Specific IPv4 Group Address—Select to enable the source-

specific IPv4 group address method for forwarding Multicast packets.

•IPv6 Multicast Forwarding—Select one of the following options:

•By MAC Address—Select to enable the MAC address method for

forwarding Multicast packets.

•By IPv6 Group Address—Select to enable the IPv4 group address

method for forwarding Multicast packets.

•By Source Specific IPv6 Group Address—Select to enable the source

specific IPv6 group address method for forwarding Multicast packets.

STEP 3 Click Apply. The Running Configuration file is updated.

IGMP/MLD Snooping

Multicast registration is the process of listening and responding to Multicast

registration protocols. The available protocols are IGMP for IPv4 and MLD

for IPv6.

When IGMP/MLD snooping is enabled in a device on a VLAN, it analyzes the

IGMP/MLD packets it receives from the VLAN connected to the device and

Multicast routers in the network.

When a device learns that a host is using IGMP/MLD messages to register to

receive a Multicast stream, optionally from a specific source, the device adds

the registration to the MFDB.

The following versions are supported:

•IGMP v1/v2/ v3

•MLD v1/v2

NOTE:

The device supports IGMP/MLD Snooping only on static VLANs. It does not

support IGMP/MLD Snooping on dynamic VLANs.

When IGMP/MLD Snooping is enabled globally or on a VLAN, all IGMP/MLD

packets are forwarded to the CPU. The CPU analyzes the incoming packets,

and determines the following:

•Which ports are asking to join which Multicast groups on what VLAN.

•Which ports are connected to Multicast routers (Mrouters) that are

generating IGMP/MLD queries.

•Which ports are receiving PIM, DVMRP, or IGMP/MLD query protocols.

These VLANs are displayed on the IGMP/MLD Snooping page.

Ports, asking to join a specific Multicast group, issue an IGMP report that

specifies which group(s) the host wants to join. This results in the creation of a

forwarding entry in the Multicast Forwarding Data Base.

To support selective IPv6 Multicast forwarding, bridge Multicast filtering must be

enabled (in the Multicast > Feature Configuration page), and MLD Snooping must

be enabled globally and for each relevant VLAN in the MLD Snooping pages.

IGMP Snooping

To enable IGMP Snooping and identify the device as an IGMP Snooping

Querier on a VLAN, do the following:

STEP 1 Click Configuration > Multicast > IGMP Snooping.

STEP 2 Enable or disable IGMP Snooping.

When IGMP Snooping is enabled globally, the device monitoring network

traffic can determine which hosts have requested to receive Multicast traffic.

The device only performs IGMP Snooping if both IGMP snooping and Bridge

Multicast filtering are enabled.

STEP 3 Select a VLAN, and click Edit. Enter the parameters:

•VLAN ID—Select the VLAN ID on which MLD snooping is defined.

•VLAN Settings

•IGMP Snooping Status—Enable or disable the monitoring of network

traffic for the selected VLAN.

•Auto Learn MRouter Ports —Select to enable auto learning of the ports

to which the Mrouter is connected.

•Immediate Leave—Select to enable Immediate Leave to decrease the

time it takes to block a Multicast stream sent to a member port when

an MLD Group Leave message is received on that port.

•IGMP Querier—Select to enable the IGMP Querier.

Table of ContentsLinksys

•IGMP Querier Version—Select the IGMP version used if the device

becomes the elected querier. Select IGMPv3 if there are switches and/or

Multicast routers in the VLAN that perform source-specific IP Multicast

forwarding.

•Querier Source IP Address—Select the source IP address of the IGMP

Querier. The following options are available:

•Auto—The system decides whether to use the IP address of the VLAN

or the management IP address.

•User Defined—This can be the IP address of the VLAN or it can be the

management IP address.

STEP 4 Click Apply. The Running Configuration file is updated.

MLD Snooping

To enable MLD Snooping and configure it on a VLAN, do the following:

STEP 1 Click Configuration > Multicast > MLD Snooping.

When MLD Snooping is globally enabled, the device monitoring network

traffic can determine which hosts have requested to receive Multicast traffic.

The device performs MLD Snooping only if both MLD snooping and Bridge

Multicast filtering are enabled.

STEP 2 Select MLD Snooping to enable the feature.

The following fields are displayed in the MLD Snooping Table:

•VLAN ID-VLAN ID on which MLD snooping is defined.

•MLD Snooping Status-Whether the monitoring of network traffic for the

selected VLAN is enabled or disabled.

•Router MLD Version-MLD version supported.

•Auto Learn MRouter Ports -Whether auto learning of the ports to which

the Mrouter is connected is enabled.

•Immediate Leave-Whether Immediate Leave to decrease the time it takes

to block a Multicast stream sent to a member port when an MLD Group

Leave message is received on that port is enabled.

STEP 3 Click Edit.

STEP 4 Enable or disable the following features for the selected VLAN:

•VLAN ID—Select a VLAN on which to configure MLD Snooping.

•MLD Snooping Status—Select to enable MLD snooping globally on all

interfaces.

•Auto-Learn MRouter Ports—Select to enable Auto Learn of the

Multicast router.

•Immediate Leave—Select to enable the switch to remove an interface

that sends a leave message from the forwarding table without first

sending out MAC-based general queries to the interface. When an MLD

Leave Group message is received from a host, the system removes the

host port from the table entry. After it relays the MLD queries from the

Multicast router, it deletes entries periodically if it does not receive any

MLD membership reports from the Multicast clients. When enabled, this

feature reduces the time it takes to block unnecessary MLD traffic sent to

a device port.

STEP 5 Click Apply. The Running Configuration file is updated.

Multicast Router Ports

A Multicast router (Mrouter) port is a port that connects to a Multicast router.

The device includes the Multicast router port(s) numbers when it forwards the

Multicast streams and IGMP/MLD registration messages. This is required so that

the Multicast routers can, in turn, forward the Multicast streams and propagate

the registration messages to other subnets.

To statically configure or see dynamically-detected ports connected to the

Multicast router, do the following:

STEP 1 Click Configuration > Multicast > Multicast Router Ports.

STEP 2 Enter some or all of following query filter criteria:

•VLAN ID—Select the VLAN ID for the router ports that are described.

•IP Version—Select whether the IP group address is an IPv4 or IPv6

address.

•Interface Type—Select whether to display ports or LAGs.

STEP 3 Click Search. The interfaces matching the query criteria are displayed.

STEP 4 For each port or LAG, select its association type. The options are as

follows:

•Static—The port is statically configured as a Multicast router port.

Table of ContentsLinksys

•Dynamic—(Display only) The port is dynamically configured as a Multicast

router port by a IGMP/MLD query. To enable the dynamic learning of

Multicast router ports, go to the IGMP Snooping page.

•Forbidden—This port is not to be configured as a Multicast router port,

even if IGMP/MLD queries are received on this port. If Forbidden is

enabled on a port, Mrouter is not learned on this port (i.e. MRouter Ports

Auto-Learn is not enabled on this port).

•None—The port is not currently a Multicast router port.

STEP 5 Click Apply to update the device.

Forward All

The Forward All page enables and displays the configuration of the ports and/

or LAGs that are to receive Multicast streams from a specific VLAN. This feature

requires that Bridge Multicast filtering in the Feature Configuration page be

enabled. If it is disabled, then all Multicast traffic is flooded to ports in the device.

You can statically (manually) configure a port to Forward All, if the devices

connecting to the port do not support IGMP/MLD.

IGMP/MLD messages are not forwarded to ports defined as Forward All.

NOTE:

The configuration affects only the ports that are members of the

selected VLAN.

To define Forward All Multicast, do the following:

STEP 1 Click Configuration > Multicast > Forward All.

STEP 2 Define the following:

•VLAN ID—The VLAN ID the ports/LAGs are to be displayed.

•Interface Type—Define whether to display ports or LAGs.

STEP 3 Click Search. The status of all ports/LAGs are displayed.

STEP 4 Select the port/LAG that is to be defined as Forward All by using the

following methods:

•Static—The port receives all Multicast streams.

•Forbidden—Ports cannot receive any Multicast streams, even if IGMP/

MLD snooping designated the port to join a Multicast group.

•None—The port is not currently a Forward All port.

STEP 5 Click Apply. The Running Configuration file is updated.

Unregistered Multicast

Multicast frames are generally forwarded to all ports in the VLAN. If IGMP/MLD

Snooping is enabled, the device learns about the existence of Multicast groups,

and monitors which ports have joined which Multicast group. Multicast groups

can also be statically configured. Multicast groups that were either dynamically

learned or statically configured are considered registered.

The device forwards Multicast frames (from a registered Multicast group) only

to ports that are registered to that Multicast group.

The Unregistered Multicast page enables handling Multicast frames that belong

to groups that are not known to the device (unregistered Multicast groups).

Unregistered Multicast frames are usually forwarded to all ports on the VLAN.

You can select a port to receive or filter unregistered Multicast streams. The

configuration is valid for any VLAN of which it is a member (or will be a member).

This feature ensures that the customer receives only the Multicast groups

requested and not others that may be transmitted in the network.

To define unregistered Multicast settings, do the following:

STEP 1 Click Configuration > Multicast > Unregistered Multicast.

STEP 2 Define the following:

•Interface Type—Define whether to display ports or LAGs.

•Interface Settings—Displays the forwarding status of the selected

interface. The possible values are as follows:

•Forwarding—Enables forwarding of unregistered Multicast frames to the

selected interface.

•Filtering—Enables filtering (rejecting) of unregistered Multicast frames to

the selected interface.

STEP 3 Click Apply. The settings are saved, and the Running Configuration

file is updated.

IGMP/MLD IP Group Addresses

The IGMP/MLD IP Group Addresses page displays the IPV4/IPV6 group address

learned from IGMP/MLD messages.

Table of ContentsLinksys

There might be a difference between information on this page and, for

example, information displayed in the MAC Group Address FDB page. Assuming

that the system is in MAC-based groups and a port that requested to join the

following Multicast groups 224.1.1.1 and 225.1.1.1, both are mapped to the same

MAC Multicast address 01:00:5e:01:01:01. In this case, there is a single entry in

the MAC Group Address FDB page, but two entries on this page.

To query for an IP Multicast group, do the following:

STEP 1 Click Configuration > Multicast > IGMP/MLD IP Group Addresses.

STEP 2 Enter some or all of following query filter criteria:

•VLAN ID—Defines the VLAN ID to query.

•Dynamic IP Group Type—Select whether the IP group address is an IPv4

or IPv6 address.

•IP Group Address—Defines the Multicast group MAC address or IP

address to query.

•Source IP Address—Defines the sender address to query.

STEP 3 Click Search. The following fields are displayed for each Multicast group:

•VLAN ID—The VLAN ID.

•IP Group Address—The Multicast group MAC address or IP address.

•Source IP Address—The sender address for all of the specified

group ports.

•Included Ports—The list of destination ports for the Multicast stream.

•Excluded Ports—The list of ports not included in the group.

•Compatibility Mode—The oldest IGMP/MLD version of registration from

the hosts the device receives on the IP group address.

MAC Group Address FDB

The device supports forwarding incoming Multicast traffic based on the

Multicast group information. This information is derived from the IGMP/MLD

packets received or as the result of manual configuration, and it is stored in the

Multicast Forwarding Database (MFDB). When a frame is received from a VLAN

that is configured to forward Multicast streams, based on MAC group addresses,

and its destination address is a Layer 2

Multicast address, the frame is forwarded to all ports that are members of the

MAC group address.

The MAC Group Address FDB page has the following functions:

•Query and view information from the MFDB, relating to a specific VLAN ID

or a specific MAC address group. This data is acquired either dynamically

through IGMP/MLD snooping or statically by manual entry.

•Add or delete static entries to the MFDB that provide static forwarding

information, based on MAC destination addresses.

•Display a list of all ports/LAGs that are a member of each VLAN ID and

MAC address group, and enter whether traffic is forwarded to it or not.

To define and view MAC Multicast groups, do the following:

STEP 1 Click Configuration > Multicast > MAC Group Address FDB.

STEP 2 Enter the parameters.

•VLAN ID —Enter the VLAN ID of the group to be displayed.

•MAC Group Address —Set the MAC address of the Multicast group to be

displayed. If no MAC Group Address is specified, the page contains all the

MAC Group Addresses from the selected VLAN.

STEP 3 Click Search, and the MAC Multicast group addresses are displayed in

the lower block.

Entries that were created both in this page and in the IP Group Address FDB

page are displayed. For those created in the IP Group Address FDB page, the IP

addresses are converted to MAC addresses.

STEP 4 Click Add to add a static MAC Group Address.

STEP 5 Enter the parameters.

•VLAN ID—Defines the VLAN ID of the new Multicast group.

•MAC Group Address—Defines the MAC address of the new Multicast group.

STEP 6 Click Apply, the MAC Multicast group is saved to the Running

Configuration file.

To configure and display the registration for the interfaces within the group,

select an address, and click Membership.

The MAC Group Address FDB page opens. Enter the following:

•VLAN ID—The VLAN ID of the Multicast group.

•MAC Group Address—The MAC address of the group.

•Interface Type—Port or LAG.

Table of ContentsLinksys

STEP 7 Click Search to display the port or LAG membership.

STEP 8 Select the way that each interface is associated with the

Multicast group:

•Static—Attaches the interface to the Multicast group as a static member.

•Dynamic—Indicates that the interface was added to the Multicast group as

a result of IGMP snooping.

•Forbidden—Specifies that this port is not allowed to join this group on

this VLAN.

•Excluded—Specifies that the port is not currently a member of this

Multicast group on this VLAN.

STEP 9 Click Apply, and the Running Configuration file is updated.

NOTE Entries that were created in the IP Group Address FDB page cannot

be deleted in this page (even if they are selected).

IP Group Address FDB

The IP Group Address FDB page enables querying and adding IP Multicast

groups contained in the IP Multicast Groups Forwarding Data Base.

To define and view IP Multicast groups, do the following:

STEP 1 Click Configuration > Multicast > IP Group Address FDB

The page contains all of the IP Multicast group addresses learned by snooping.

STEP 2 Enter the parameters required for filtering.

•VLAN ID—Enter the VLAN ID of the group to be displayed.

•IP Group Address—Define the IP address of the Multicast group to be

displayed. This is only relevant when the Forwarding Mode is (S,G).

•IP Version—Select whether the IP group address is an IPv4 or IPv6

address.

•Source IP Address—Define the source IP address of the sending device.

If mode is (S,G), enter the sender S. This together with the IP group

address is the Multicast group ID (S,G) to be displayed. If mode is

(*.G), enter an * to indicate that the Multicast group is only defined by

destination.

STEP 3 Click Search. The results are displayed in the lower block.

STEP 4 Click Add to add a static IP Multicast group address.

STEP 5 Enter the parameters.

•VLAN ID—Defines the VLAN ID of the group to be added.

•IP Group Address—Define the IP address of the new Multicast group.

Group Address Settings

•Source Specific IP Multicast—Select to indicate that the entry contains a

specific source, and adds the address in the IP Source Address field. If not,

the entry is added as a (*,G) entry, an IP group address from any IP source.

•Source IP Address—Enter the source address to be included.

STEP 6 Click Apply. The IP Multicast group is added, and the device is

updated.

STEP 7 To configure and display the registration of an IP group address,

select an address and click Membership.

The VLAN ID, IP Version, IP Multicast group address, and Source IP address

selected are displayed as read-only in the top of the window. You can select the

filter type:

•Interface Type—Select whether to display ports or LAGs.

STEP 8 For each interface, select its association type. The options are as follows:

•Static—Attaches the interface to the Multicast group as a static member.

•Dynamic—Indicates that the interface was added to the Multicast

group as a result of IGMP snooping.

•Forbidden—Specifies that this port is forbidden from joining this group

on this VLAN.

•Excluded—Indicates that the port is not currently a member of this

Multicast group on this VLAN. This is selected by default until Static or

Forbidden is selected.

STEP 9 Click Apply. The Running Configuration file is updated.

Table of ContentsLinksys

Chapter 10 IP Interface

IP Interface

This section describes IP interfaces and covers the following topics:

•IPv4

•IPv6

IPv4

This section describes IPv4 configuration. It covers the following topics:

•Overview

Overview

Layer 2 IP Addressing

The device has one IPv4 address and up to two IPv6 interfaces in the

management VLAN. This IP address and the default gateway can be

configured manually, or by DHCP. The static IP address and default gateway

are configured on the IPv4 Interface page. The device uses the default

gateway, if configured, to communicate with devices that are not in the same

IP subnet as the device. By default, VLAN 1 is the management VLAN, but this

can be modified. The device can only be reached at the configured IP address

through its management VLAN.

The factory default setting of the IPv4 address configuration is DHCPv4. This

means that the device acts as a DHCPv4 client, and sends out a DHCPv4

request during boot up.

If the device receives a DHCPv4 response from the DHCPv4 server with an

IPv4 address, it sends Address Resolution Protocol (ARP) packets to confirm

that the IP address is unique. If the ARP response shows that the IPv4 address

is in use, the device sends a DHCPDECLINE message to the offering DHCP

server, and sends another DHCPDISCOVER packet that restarts the process.

If the device does not receive a DHCPv4 response in 60 seconds, it continues

to send DHCPDISCOVER queries, and adopts the default IPv4 address:

192.168.1.251/24.

IP address collisions occur when the same IP address is used in the same IP

subnet by more than one device. Address collisions require administrative

actions on the DHCP server and/or the devices that collide with the device.

When a VLAN is configured to use dynamic IP addresses, the device issues

DHCPv4 requests until it is assigned an IPv4 address from a DHCPv4 server.

The management VLAN can be configured with a static or dynamic IP address.

The IP address assignment rules for the device are as follows:

•Unless the device is configured with a static IP address, it issues DHCPv4

requests until a response is received from the DHCP server.

•If the IP address on the device is changed, the device issues gratuitous

ARP packets to the corresponding VLAN to check IP address collisions.

This rule also applies when the device reverts to the default IP address.

•The system status LED changes to solid blue when a new unique IP

address is received from the DHCP server. If a static IP address has been

set, the system status LED also changes to solid blue. The LED flashes

when the device is acquiring an IP address and is currently using the

factory default IP address 192.168.1. 251.

•The same rules apply when a client must renew the lease, prior to its

expiration date through a DHCPREQUEST message.

•With factory default settings, when no statically defined or DHCP-

acquired IP address is available, the default IP address is used. When the

other IP addresses become available, the addresses are automatically

used. The default IP address is always on the management VLAN.

IPv4 Interface

To manage the device by using the web-based configuration utility, the

IPv4 device management IP address must be defined and known. The

device IP address can be manually configured or automatically received

from a DHCP server.

To configure the IPv4 device IP address, do the following:

STEP 1 Click Configuration > IP Interface > IPv4 > IPv4 Interface.

STEP 2 Enter values for the following fields:

•Management VLAN—Select the Management VLAN used to access

the device through telnet or the Web GUI. VLAN1 is the default

Management VLAN.

•IP Address Type—Select one of the following options:

Table of ContentsLinksys

•Dynamic (DHCP)—Discover the IP address using DHCP from the

management VLAN.

•Static IP Address—Manually define a static IP address.

NOTE:

DHCP Option 12 (Host Name option) is supported when the device is a

DHCP client. If DHCP Option 12 is received from a DHCP server, it is saved as

the server’s host name. DHCP option 12 will not be requested by the device.

The DHCP server must be configured to send option 12, regardless of what

is requested in order to make use of this feature.

•Dynamic IP Address—Select to renew the DHCP-supplied IP address.

•IP Address—Enter the IP address, and configure one of the following

Mask fields:

•IP Subnet Mask—Configure one of the following Mask fields:

•SubNet Mask—Select and enter the IP address mask.

•Prefix Length—Select and enter the length of the IPv4 address prefix.

•User Defined Default Gateway—Select User Defined and enter the

default gateway IP address.

•Default Gateway—Displays the current default gateway status.

NOTE:

If the device is not configured with a default gateway, it cannot

communicate with other devices that are not in the same IP subnet.

STEP 3 Click Apply. The IPv4 interface settings are written to the Running

Configuration file.

ARP

The device maintains an ARP (Address Resolution Protocol) table for all known

devices that reside in the IP subnets directly connected to it. A directly-

connected IP subnet is the subnet to which an IPv4 interface of the device is

connected. When the device is required to send/route a packet to a local device,

it searches the ARP table to obtain the MAC address of the device. The ARP table

contains dynamic addresses. The device creates dynamic addresses from the

ARP packets it receives. Dynamic addresses age out after a configured time.

To define the ARP tables, do the following:

STEP 1 Click Configuration > IP Interface > IPv4 > ARP.

STEP 2 Enter the parameters.

•ARP Entry Aging Time (1-40000000)—Enter the number of seconds that

dynamic addresses can remain in the ARP table. A dynamic address ages

out after the time it is in the table exceeds the ARP Entry Age Out time.

When a dynamic address ages out, it is deleted from the table, and only

returns when it is relearned.

STEP 3 Click Apply. The ARP global settings are written to the Running

Configuration file.

The ARP table displays the following fields:

•IP Interface—The IPv4 Interface of the directly-connected IP subnet where

the IP device resides.

•IP Address—The IP address of the IP device.

•MAC Address—The MAC address of the IP device.

•Status—Whether the entry was manually entered (static) or

dynamically learned.

STEP 4 Click Add.

STEP 5 Enter the parameters:

Interface—An IPv4 interface can be configured on a port, LAG or VLAN. Select

the desired interface from the list of configured IPv4 interfaces on the device.

•IP Address—Enter the IP address of the local device.

•MAC Address—Enter the MAC address of the local device.

STEP 6 Click Apply. The ARP entry is saved to the Running Configuration file

IPv6

This section describes IPv6 configuration. It covers the following topics:

•Overview

•IPv6 Interfaces

•IPv6 Interface Addresses

•IPv6 Default Routers

•IPv6 Routes

•IPv6 Neighbors

Table of ContentsLinksys

Overview

The Internet Protocol version 6 (IPv6) is a network-layer protocol for

packetswitched Internet works. IPv6 was designed to replace IPv4, the

predominantly deployed Internet protocol.

IPv6 introduces greater flexibility in assigning IP addresses because the

address size increases from 32-bit to 128-bit addresses. IPv6 addresses are

written as eight groups of four hexadecimal digits, for example FE80:0000:0

000:0000:0000:9C00:876A:130B. The abbreviated form, in which a group of

zeroes can be left out, and replaced with ‘::’, is also acceptable, for example,

::-FE80::9C00:876A:130B.

IPv6 nodes require an intermediary mapping mechanism to communicate with

other IPv6 nodes over an IPv4-only network. This mechanism, called a tunnel,

enables IPv6-only hosts to reach IPv4 services, and enables isolated IPv6 hosts

and networks to reach an IPv6 node over the IPv4 infrastructure.

The device detects IPv6 frames by the IPv6 Ethertype.

IPv6 Interface

An IPv6 interface can be configured on a port, LAG or VLAN.

To define an IPv6 interface:

STEP 1 Click Configuration > IP Interface> IPv6 > IPv6 Interface.

STEP 2 Click Add to add a new interface on which interface IPv6 is enabled.

STEP 3 Enter the fields:

•IPv6 Interface—Select a specific port, LAG, ISATAP tunnel or VLAN for the

IPv6 address.

•Number of DAD Attempts—Enter the number of consecutive neighbor

solicitation messages that are sent while Duplicate Address Detection

(DAD) is performed on the interface’s Unicast IPv6 addresses. DAD verifies

the uniqueness of a new Unicast IPv6 address before it is assigned. New

addresses remain in a tentative state during DAD verification. Entering

0 in this field disables duplicate address detection processing on the

specified interface. Entering 1 in this field indicates a single transmission

without follow-up transmissions.

•IPv6 Address Auto Configuration—Select to enable automatic address

configuration from router advertisements sent by neighbors.

NOTE:

The device does not support stateful address autoconfiguration from a

DHCPv6 server.

•Send ICMPv6 Messages—Select to enable generating unreachable

destination messages.

STEP 4 Click Apply to enable IPv6 processing on the selected interface.

Regular IPv6 interfaces have the following addresses automatically

configured address

•All link local Multicast addresses (FF02::1)

•Solicited-Node Multicast address (format FF02::1:FFXX:XXXX)

IPv6 Interface Addresses

To assign an IPv6 address to an IPv6 Interface, do the following:

STEP 1 Click Configuration > IP Interface> IPv6 > IPv6 Interface Addresses.

STEP 2 To filter the table, select an interface name, and click Search. The

interface appears in the IPv6 Address Table.

STEP 3 Click Add.

STEP 4 Enter values for the fields.

•IPv6 Interface—Displays the interface on which the IPv6 address is to be

defined. If an * is displayed, the IPv6 interface is not enabled but has been

configured.

•IPv6 Address Type—Select the type of the IPv6 address to add.

•Link Local—An IPv6 address that 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.

•Global—An IPv6 address that is a global Unicast IPV6 type that is visible

and reachable from other networks.

Produktspecifikationer

Varumärke:	Linksys
Kategori:	Växla
Modell:	LGS308P
Vikt:	1880 g
Bredd:	90 mm
Djup:	252 mm
Höjd:	43.8 mm
Hållbarhetscertifikat:	RoHS
Antal per paket:	8 stuk(s)
Inspänning:	90 - 305 V
Uteffekt:	320 W
Utström:	6.7 A
Spännande:	48 V