Specifications are subject to change without notice.
Linksys, the Cisco Systems logo, the Linksys Logo, and the Linksys One logo are registered trademarks of Cisco
Systems, Inc. All other trademarks mentioned in this document are the property of their respective owners.
Defining MAC Based ACL37
Adding Rule to MAC Based ACL38
Defining IP Based ACL38
Adding an IP Based Rule40
Defining ACL Binding40
Modifying ACL Binding41
Federal Communications Commission Interference Statement152
Industry Canada Statement152
Règlement d’Industry Canada153
EC Declaration of Conformity (Europe)153
User Information for Consumer Products Covered by EU Directive 2002/96/EC on
Waste Electric and Electronic Equipment (WEEE)153
This publication is designed for people who have some experience installing networking equipment
such as routers, hubs, servers, and switches. We assume the person installing and troubleshooting
the SFE1000P is familiar with electronic circuitry and wiring practices and has experience as an
electronic or electromechanical technician.
Purpose
This guide documents the features of the Linksys Business Series SFE1000P Gigabit Ethernet Switch
(SFE1000P). It describes the administration of the SFE1000P, explains how to install the SFE1000P,
and provides configuration information.
Organization
1
This guide is organized into the following chapters:
•Chapter 2, "Getting Started,"is an introduction to the user interface.
•Chapter 3, "Managing Device Information,"provides information for defining both basic
and advanced system information.
•Chapter 13, "Configuring Quality of Service," shows how to define Quality of Service
general settings, advanced mode settings, and basic mode settings. It also describes
configuring policy tables.
•Chapter 14, "Managing System Files," describes working with file management, logs, and
diagnostics.
•Chapter 15, "Managing System Logs," shows how to enable system logs, view device
memory logs, flash logs, and remote logs.
•Chapter 16, "Configuring System Time," provides information for configuring the system
time, and includes defining system time, SNTP settings, and SNTP authentication.
•Chapter 17, "Viewing Statistics," describes viewing and managing device statistics for
RMON, interfaces, GVRP, EAP, and Etherlike statistics.
•Chapter 18, "Managing Device Diagnostics," contains information for configuring port
mirroring, running cable tests, and viewing device operational information.
•Appendix B, "Contacts," is a listing of support resources and contact information for such.
1
•Appendix C, "Warranty Information," is the Linksys warranty.
3. Enter a user name and password. The default user name is "admin"
configured with a default password, and can be configured without entering a password.
Passwords are both case sensitive and alpha-numeric.
4. Click Login The Embedded Web System Home Page opens:
NOTE: If you have logged in automatically via the Service
Router user interface, the Tree and Device views appear
and allow you to navigate through the various areas of
the web interface. However, the following page will
appear within the frame provided by the Service Router
user interface.
. The device is not
Chapter 2: Getting Started
Starting the Application
The following table lists the interface components with their corresponding numbers:
Interface Components
Component Description
Tree ViewThe Tree View provides easy navigation through the configurable
1
device features.The main branches expand to provide the subfeatures.
2 Device ViewThe device view provides information about device ports, current
configuration and status, table information, and feature
components.The device view also displays other device information
and dialog boxes for configuring parameters.
3 Table AreaThe Table area enables navigating through the different device
features. Click the tabs to view all the components under a specific
feature.
4 EWS InformationThe EWS information tabs provide access to the online help, contains
information about the EWS.
Chapter 2: Getting Started
Understanding the Interface
4. Click the Delete button. The information is deleted, and the device is updated.
Resetting the Device
The Reset page enables the device to be reset from a remote location. Save all changes to the
Running Configuration file before resetting the device. This prevents the current device configuration
from being lost. To reset the device:
1. Click System > General > Reset. The Reset page opens.
Reset Page
2
2. Click the Reset button. The device is reset, and a prompt for a user name and password is
displayed.
3. Enter a user name and password to reconnect to the Web Interface, if the device is not part of a
full Linksys One system. If the device is part of a Linksys One system, login is automatically done
from the Service Router.
Logging Off The Device
Click . The system logs off. The Embedded Web System Home Page closes.
The System Information Page contains parameters for configuring general device information.
1. Click the System > System Management > System Information. The System Information Page
opens:
System Information Page
3
2. Enter information into the appropriate fields and press Apply.
Resetting the Device
The Reset page enables the device to be reset from a remote location. Save all changes to the
Startup Configuration file before resetting the device. This prevents the current device configuration
from being lost.
To reset the device:
1. Click System > General > Reset. The Reset page opens.
Chapter 3: Managing Device Information
Defining General System Information
3. Enter a user name and password to reconnect to the Web Interface. If the device is part of a
Linksys One system, login is automatically done from the Service Router.
Chapter 3: Managing Device Information
Resetting the Device
Power-over-Ethernet (PoE) provides power to devices over existing LAN cabling, without updating or
modifying the network infrastructure. Power-over-Ethernet removes the necessity of placing network
devices next to power sources.
Power-over-Ethernet can be used in the following applications:
•IP Phones
•Wireless Access Points
•IP Gateways
•PDAs
•Audio and video remote monitoring
Defining PoE Settings
4
Powered Devices are devices which receive power from the device power supplies, for example IP
phones. Powered Devices are connected to the device via Ethernet ports. Guard Band protects the
device from exceeding the maximum power level. For example, if 400W is maximum power level,
and the Guard Band is 20W, if the total system power consumption exceeds 380W no additional
PoE components can be added. The accumulated PoE components power consumption is rounded
down for display purposes, therefore remove value after decimal point.
NOTE: Due to hardware limitations, the power
measurement accuracy is 4%.
The PoE Settings Page contains system PoE information for enabling PoE on the device, monitoring
the current power usage, and enabling PoE traps.
1. Click Bridging > Port Management > PoE Settings. The PoE Settings Page opens:
Authentication profiles allow network administrators to assign authentication methods for user
authentication. User authentication can be performed locally or on an external server. User
authentication occurs in the order the methods are selected. If the first authentication method is not
available, the next selected method is used. For example, if the selected authentication methods are
RADIUS and Local, and the RADIUS server is not available, then the user is authenticated locally.
1. Click Security Suite > Authentication > Profiles. The Profiles Page opens:
Profiles Page
5
2. Click the Add button. The Add Authentication Profile Page opens:
Add Authentication Profile Page
3. Define the relevant fields.
4. Click Apply. The settings are modified, and the device is updated.
1. Click Security Suite > Authentication > Profiles. The Profiles Page opens:
2. Click the Edit Button. The Edit Authentication Profile Page opens:
Edit Authentication Profile Page
Chapter
5
3. Define the relevant fields.
4. Click Apply. The authentication profile is defined, and the device is updated.
Mapping Authentication Profiles
After authentication profiles are defined, they can be applied to management access methods. For
example, console users can be authenticated by one authentication profile, while Telnet users are
authenticated by another authentication profile.
Authentication methods are selected using arrows. The order in which the methods are selected is
the order by which the authentication methods are used.
The Mapping Profiles Page contains parameters for mapping authentication methods.
1. Click Security Suite > Authentication > Mapping Profiles. The Mapping Profiles Page opens:
3. Click Apply. Mapping Profiles is defined, and the device is updated.
Defining TACACS+
The devices provide Terminal Access Controller Access Control System (TACACS+) client support.
TACACS+ provides centralized security for validation of users accessing the device. TACACS+
provides a centralized user management system, while still retaining consistency with RADIUS and
other authentication processes. TACACS+ provides the following services:
•Authentication — Provides authentication during login and via user names and user-
defined passwords.
•Authorization — Performed at login. Once the authentication session is completed, an
authorization session starts using the authenticated user name. The TACACS server checks
the user privileges.
The TACACS+ protocol ensures network integrity through encrypted protocol exchanges between
the device and TACACS+ server.
The TACACS+ default parameters are user-assigned defaults. The default settings are applied to
newly defined TACACS+ servers. If default values are not defined, the system defaults are applied to
the new TACACS+ new servers. The TACACS+ Page contains fields for assigning the Default
Parameters for the TACACS+ servers.
1. Click Security Management > Security Suite > Authentication. The TACACS+ Page opens:
2. Click the Edit Button. The TACACS+ Page opens:
TACACS+ Page
5
3. Define the relevant fields.
4. Click Apply. The TACACS+ settings are modified, and the device is updated.
DefiningRADIUS
Remote Authorization Dial-In User Service (RADIUS) servers provide additional security for
networks. RADIUS servers provide a centralized authentication method for web access. The default
parameters are user-defined, and are applied to newly defined RADIUS servers. If new default
parameters are not defined, the system default values are applied to newly defined RADIUS servers.
To d ef ine RA DIU S :
1. Click Security Suite > Authentication > RADIUS. The RADIUS Page opens:
1. Click Security Suite > Authentication > RADIUS. The RADIUS Page opens:
2. Click the Edit button. The Edit RADIUS Settings Page opens:
Edit RADIUS Settings Page
Chapter
5
3. Define the relevant fields.
4. Click Apply. The RADIUS Server settings are modified, and the device is updated.
Defining Access Method
The access method section contains the following pages:
•Defining Access Profiles
•Defining Profile Rules
Defining Access Profiles
Access profiles are profiles and rules for accessing the device. Access to management functions can
be limited to user groups. User groups are defined for interfaces according to IP addresses or IP
subnets. Access profiles contain management methods for accessing and managing the device. The
device management methods include:
Management access to different management methods may differ between user groups. For
example, User Group 1 can access the switch module only via an HTTPS session, while User Group
2 can access the switch module via both HTTPS and Telnet sessions. The Access Profile Page contains
the currently configured access profiles and their activity status. Assigning an access profile to an
interface denies access via other interfaces. If an access profile is assigned to any interface, the
device can be accessed by all interfaces.
To define access profiles:
1. Click Security Suite > Access Method > Access Profiles. The Access Profiles Page opens:
Access Profiles Page
5
2. Click the Add button. The Add Access Profile Page opens:
4. Click Apply. The access profile is added, and the device is updated.
Defining ProfileRules
Access profiles can contain up to 128 rules that determine which users can manage the switch
module, and by which methods. Users can also be blocked from accessing the device. Rules are
composed of filters including:
The Traffic Control section contains the following pages:
•Defining Storm Control
•Defining Port Security
Defining Storm Control
Storm Control enables limiting the amount of Multicast and Broadcast frames accepted and
forwarded by the device. When Layer 2 frames are forwarded, Broadcast and Multicast frames are
flooded to all ports on the relevant VLAN. This occupies bandwidth, and loads all nodes connected
on all ports.
A Broadcast Storm is a result of an excessive amount of broadcast messages simultaneously
transmitted across a network by a single port. Forwarded message responses are heaped onto the
network, straining network resources or causing the network to time out.
5
Storm Control is enabled per all ports by defining the packet type and the rate the packets are
transmitted. The system measures the incoming Broadcast and Multicast frame rates separately on
each port and discards the frames when the rate exceeds a user-defined rate.
The Storm Control Page provides fields for configuring Broadcast Storm Control.
To define storm control:
1. Click Security Suite > Traf fic Control > Storm Control. The Storm Control Page opens:
Storm Control Page
2. Define the relevant fields.
3. Click Apply. Storm control is enabled, and the device is updated.
Chapter 5: Configuring Device Security
Defining Traffic Control
1. Click Security Suite > Traf fic Control > Storm Control. The Storm Control Page opens:
2. Click the Edit Button. The Edit Storm Control Page opens:
Edit Storm Control Page
3. Modify the relevant fields.
Chapter
5
4. Click Apply. Storm control is modified, and the device is updated.
Defining PortSecurity
Network security can be increased by limiting access on a specific port only to users with specific
MAC addresses. The MAC addresses can be dynamically learned or statically configured. Locked
port security monitors both received and learned packets that are received on specific ports. Access
to the locked port is limited to users with specific MAC addresses. These addresses are either
manually defined on the port, or learned on that port up to the point when it is locked. When a
packet is received on a locked port, and the packet source MAC address is not tied to that port
(either it was learned on a different port, or it is unknown to the system), the protection mechanism is
invoked, and can provide various options. Unauthorized packets arriving at a locked port are
either:
•Forwarded
•Discarded with no trap
•Discarded with a trap
•Cause the port to be shut down.
Locked port security also enables storing a list of MAC addresses in the configuration file. The MAC
address list can be restored after the device has been reset. Disabled ports are activated from the
Port Management page.
NOTE: To configure port lock, 802.1x multiple host mode
must be enabled.
Chapter 5: Configuring Device Security
Defining Traffic Control
Port based authentication enables authenticating system users on a per-port basis via a external
server. Only authenticated and approved system users can transmit and receive data. Ports are
authenticated via the RADIUS server using the Extensible Authentication Protocol (EAP). Port
Authentication includes:
•Authenticators — Specifies the port, which is authenticated before permitting system access.
•Supplicants — Specifies host connected to the authenticated port requesting to access the
system services.
•Authentication Server — Specifies the external server, for example, the RADIUS server that
performs the authentication on behalf of the authenticator, and indicates whether the
supplicant is authorized to access system services.
Port based authentication creates two access states:
•Controlled Access — Permits communication between the supplicant and the system, if the
supplicant is authorized.
5
•Uncontrolled Access — Permits uncontrolled communication regardless of the port state.
The 802.1x page configures port to use Extensible Authentication Protocol (EAP).
The 802.1x section contains the following pages:
•Defining 802.1X Properties
•Defining Port Authentication
•Defining Multiple Hosts
•Defining Authenticated Host
The 802.1x page configures port to use Extensible Authentication Protocol (EAP).
The Authenticated Host Page contains a list of authenticated users.
1. Click Security Suite > 802.1X > Authenticated Host. The Authenticated Host Page opens:
Authenticated Host Page
5
2. Define the relevant fields.
3. Click Apply. The authenticated host settings are defined, and the device is updated.
Defining Access Control
Access Control Lists (ACL) allow network managers to define classification actions and rules for
specific ingress ports. Your switch supports up to 256 ACLs. Packets entering an ingress port, with
an active ACL, are either admitted or denied entry. If they are denied entry, the user can disable the
port. ACLs are composed of access control entries (ACEs) that are made of the filters that determine
traffic classifications. The total number of ACEs that can be defined in all ACLs together is 256.
The Access Control section contains the following pages:
•Defining MAC Based ACL
•Defining IP Based ACL
•Defining ACL Binding
Chapter 5: Configuring Device Security
Defining Access Control
The MAC Based ACL Page page allows a MAC-based Access Control List (ACL) to be defined. The
table lists Access Control Elements (ACE) rules, which can be added only if the ACL is not bound to
an interface.
To d ef ine th e MAC Bas ed ACL :
1. Click Security Suite >Access Control > MAC Based ACL. The MAC Based ACL Page opens:
MAC Based ACL Page
5
2. Click the Add ACL button. The Add MAC Based ACL Page opens:
Add MAC Based ACL Page
3. Define the relevant fields.
4. Click Apply. The MAC Based ACL is defined, and the device is updated.
Chapter 5: Configuring Device Security
Defining Access Control
1. Click Security Suite > Access Control > IP Based ACL. The IP Based ACL Page opens:
2. Click the Add ACL Rule button. The Add IP Based Rule Page opens:
Add IP Based Rule Page
Chapter
5
3. Select either Match DSCP or Match IP.
4. Click Apply. The IP based rule settings are modified, and the device is updated.
Defining ACLBinding
When an ACL is bound to an interface, all the ACE rules that have been defined are applied to the
selected interface.
that do not match the ACL are matched to the default rule, which is Drop unmatched packets.
Chapter 5: Configuring Device Security
Defining Access Control
Whenever an ACL is assigned on a port or a LAG flows from that ingress interface
4. Click Apply. The Port Settings are modified, and the device is updated.
DefiningLAG Management
Link Aggregation optimizes port usage by linking a group of ports together to form a single LAG.
Aggregating ports multiplies the bandwidth between the devices, increases port flexibility, and
provides link redundancy.
The device supports both static LAGs and Link Aggregation Control Protocol (LACP) LAGs. LACP
LAGs negotiate aggregating port links with other LACP ports located on a different device. If the
other device ports are also LACP ports, the devices establish a LAG between them. Ensure the
following:
•All ports within a LAG must be the same media type.
•A VLAN is not configured on the port.
•The port is not assigned to a different LAG.
•Auto-negotiation mode is not configured on the port.
Chapter 6: Configuring Device Interfaces
Defining LAG Management
•All ports in the LAG have the same ingress filtering and tagged modes.
•All ports in the LAG have the same back pressure and flow control modes.
•All ports in the LAG have the same priority.
•All ports in the LAG have the same transceiver type.
•The device supports up to 8 LAGs, and eight ports in each LAG.
•Ports can be configured as LACP ports only if the ports are not part of a previously
configured LAG.
Ports added to a LAG lose their individual port configuration. When ports are removed from the
LAG, the original port configuration is applied to the ports.
To define LAG management:
6
1. Click Bridging > Port Management > LAG Management. The LAG Management Page opens:
LAG Management Page
2. Define the relevant fields.
3. Click Apply. LAG Management is defined, and the device is updated.
Chapter 6: Configuring Device Interfaces
Defining LAG Management
1. Click Bridging > Port Management > LAG Management. The LAG Management Page opens:
2. Click the Edit button. The Edit LAG Membership Page opens:
Edit LAG Membership Page
6
3. Define the relevant fields.
4. To assign ports to a LAG, click the port numbers in the Port List and then click the Right Arrow
button. The port number then appears in the LAG Members list.
Conversely, to remove a port from a LAG, click the port number in the LAG Members list and
then click the Left Arrow button.
5. Click Apply. The LAG membership is defined, and the device is updated.
Chapter 6: Configuring Device Interfaces
Defining LAG Management
Link Aggregated Groups optimize port usage by linking a group of ports together to form a single
aggregated group. Link aggregated groups multiply the bandwidth between the devices, increase
port flexibility, and provide link redundancy.
The LAG Settings Page contains fields for configuring parameters for configured LAGs. The device
supports up to eight ports per LAG, and eight LAGs per system.
1. Click Bridging > Port Management > LAG Settings. The LAG Settings Page opens:
LAG Settings Page
6
2.
Click the Edit button. The LAG Configuration Settings opens:
Chapter 6: Configuring Device Interfaces
Defining LAG Settings
4. Click Apply. The LAG configuration settings are modified, and the device is updated.
Configuring LACP
Aggregate ports can be linked into link-aggregation port-groups. Each group is comprised of ports
with the same speed, set to full-duplex operations.
Aggregated Links can be manually setup or automatically established by enabling Link Aggregation
Control Protocol (LACP) on the relevant links. Aggregate ports can be linked into link-aggregation
port-groups. Each group is comprised of ports with the same speed.
VLANs are logical subgroups with a Local Area Network (LAN) which combine user stations and
network devices into a single unit, regardless of the physical LAN segment to which they are
attached. VLANs allow network traffic to flow more efficiently within subgroups. VLANs use
software to reduce the amount of time it takes for network changes, additions, and moves to be
implemented.
VLANs have no minimum number of ports, and can be created per unit, per device, or through any
other logical connection combination, since they are software-based and not defined by physical
attributes.
VLANs function at Layer 2. Since VLANs isolate traffic within the VLAN, a Layer 3 router working at
a protocol level is required to allow traffic flow between VLANs. Layer 3 routers identify segments
and coordinate with VLANs. VLANs are Broadcast and Multicast domains. Broadcast and Multicast
traffic is transmitted only in the VLAN in which the traffic is generated.
VLAN tagging provides a method of transferring VLAN information between VLAN groups. VLAN
tagging attaches a 4-byte tag to packet headers. The VLAN tag indicates to which VLAN the packets
belong. VLAN tags are attached to the VLAN by either the end station or the network device. VLAN
tags also contain VLAN network priority information.
7
Combining VLANs and GARP (Generic Attribute Registration Protocol) allows network managers to
define network nodes into Broadcast domains. The VLAN Management section contains the
following pages:
4. Click Apply. The VLAN Settings are defined, and the device is updated.
Chapter
7
Defining VLAN Membership
The VLAN Membership Page contains a table that maps VLAN parameters to ports. Ports are
assigned VLAN membership by toggling through the Port Control settings.
2. Click the Edit button. The Edit VLAN Membership Page opens:
Edit VLAN Membership Page
3. Define the relevant fields.
7
4. Click Apply. VLAN Membership is modified, and the device is updated.
Defining Interface Settings
The VLAN Interface Setting Page provides parameters for managing ports that are part of a VLAN.
The port default VLAN ID (PVID) is configured on the VLAN Port Settings page. All untagged packets
arriving to the device are tagged by the ports PVID.
2. Click the Edit button. The Edit Ports Page opens:
Edit Ports Page
7
3. Define the relevant fields.
4. Click Apply. The VLAN Interface settings are modified, and the device is updated.
Configuring GVRP Settings
GARP VLAN Registration Protocol (GVRP) is specifically provided for automatic distribution of VLAN
membership information among VLAN-aware bridges. GVRP allows VLAN-aware bridges to
automatically learn VLANs to bridge ports mapping, without having to individually configure each
bridge and register VLAN membership.
NOTE: The Global System LAG information displays the
same field information as the ports, but represent the
LAG GVRP information.
The Protocol Group Page contains information defining protocol names and the VLAN Ethernet type.
Interfaces can be classified as a specific protocol based interface.
1. Click Bridging > VLAN Management > Protocol Group. The Protocol Group Page opens:
Protocol Group Page
7
2. Click the Add Button. The Add Protocol Group Page opens:
Add Protocol Group Page
3. Define the relevant fields.
4. Click Apply. The Protocol Group is added, and the device is updated.
Chapter 7: Configuring VLANs
Defining VLAN Protocol Group
This section provides information for defining device IP addresses, and includes the following topics:
•Domain Name System
•Configuring Layer 2IP Addresses
•Configuring Layer 3
Domain Name System
Domain Name System (DNS) converts user-defined domain names into IP addresses. Each time a
domain name is assigned, the DNS service translates the name into a numeric IP address. For
example, www.ipexample.com is translated into 192.87.56.2. DNS servers maintain databases of
domain names and their corresponding IP addresses. The Domain Name System contains the
following windows:
8
•Defining DNS Server
•Mapping DNS Hosts
Defining DNS Server
Domain Name System (DNS) converts user-defined domain names into IP addresses. Each time a
domain name is assigned, the DNS service translates the name into a numeric IP address. For
example, www.ipexample.com is translated into 192.87.56.2. DNS servers maintain databases of
domain names and their corresponding IP addresses.
The DNS Servers Page contains fields for enabling and activating specific DNS servers.
Chapter 8: Configuring IP Information
Domain Name System
The IP address and default gateway can be either dynamically or statically configured. In Layer 2, a
static IP address is configured on the VLAN ManagementProperties Page. The Management VLAN
is set to VLAN 100 by default, but can be modified.
This section provides information for configuring Layer 2 features, and includes the following topics:
•Configuring IP Addressing
•Defining IP Routing
Configuring IP Addressing
The IP Addressing subsection contains the following pages:
•Defining IP Interfaces
•Enabling ARP
8
Defining IP Interfaces
The IP Interface Page contains fields for assigning IP addresses. Packets are forwarded to the default
IP when frames are sent to a remote network. The configured IP address must belong to the same IP
address subnet of one of the IP interfaces.
1. Click System > System Management > IP Addressing > IP Interface. The IP Interface Page
opens:
IP Interface Page
2. Define the relevant fields.
3. Click Apply. The IP Interface settings are modified, and the device is updated.
Chapter 8: Configuring IP Information
Configuring Layer 2IP Addresses
The Address Resolution Protocol (ARP) is a TCP/IP protocol that converts IP addresses into physical
addresses. The ARP table is used to maintain a correlation between each MAC address and its
corresponding IP address. The ARP table can be filled in statically by the user. When a static ARP
entry is defined, a permanent entry is put in the table, which the system uses to translate IP
addresses to MAC addresses.
To d ef ine AR P:
1. Click System > System Management > IP Addressing > ARP. The ARP Page opens:
ARP Page
8
2.
Click on the Add ARP button. The Add ARP Page opens:
Add ARP Page
3. Define the relevant fields.
4. Click Apply. The ARP Settings are defined, and the device is updated.
Chapter 8: Configuring IP Information
Configuring Layer 2IP Addresses
MAC addresses are stored in either the Static Address or the Dynamic Address databases. A packet
addressed to a destination stored in one of the databases is forwarded immediately to the port. The
Dynamic Address Table can be sorted by interface, VLAN, and MAC Address. MAC addresses are
dynamically learned as packets from sources arrive at the device. Addresses are associated with
ports by learning the ports from the frames source address. Frames addressed to a destination MAC
address that is not associated with any port, are flooded to all ports of the relevant VLAN. Static
addresses are manually configured. In order to prevent the bridging table from overflowing,
dynamic MAC addresses, from which no traffic is seen for a certain period, are erased.
This section contains information for defining both static and dynamic Forwarding Database entries,
and includes the following topics:
•Defining Static Addresses
•Defining Dynamic Addresses
9
Defining Static Addresses
A static address can be assigned to a specific interface on this switch. Static addresses are bound to
the assigned interface and cannot be moved. When a static address is seen on another interface,
the address will be ignored and will not be written to the address table.
4. Click Apply. The Static MAC Address is added, and the device is updated.
Defining Dynamic Addresses
Chapter
9
The Dynamic Address Table contains the MAC addresses learned by monitoring the source address
for traffic entering the switch. When the destination address for inbound traffic is found in the
database, the packets intended for that address are forwarded directly to the associated port.
Otherwise, the traffic is flooded to all ports.
The Dynamic Page contains parameters for querying information in the Dynamic MAC Address
Table, including the interface type, MAC addresses, VLAN, and table storing. The Dynamic MAC
Address table contains information about the aging time before a dynamic MAC address is erased,
and includes parameters for querying and viewing the Dynamic MAC Address table. The Dynamic
MAC Address table contains address parameters by which packets are directly forwarded to the
ports. The Dynamic Address Table can be sorted by interface, VLAN, and MAC Address.
The Multicast section contains the following pages:
•IGMP Snooping
•Defining Multicast Bridging Groups
•Defining Multicast Forwarding
IGMP Snooping
When IGMP Snooping is enabled globally, all IGMP packets are forwarded to the CPU. The CPU
analyzes the incoming packets and determines:
•Which ports want to join which Multicast groups.
•Which ports have Multicast routers generating IGMP queries.
10
•Which routing protocols are forwarding packets and Multicast traffic.
Ports requesting to join a specific Multicast group issue an IGMP report, specifying that Multicast
group is accepting members. This results in the creation of the Multicast filtering database.
2. Click the Edit button. The Edit IGMP Snooping Page:
Edit IGMP Snooping Page
Chapter
10
3. Define the relevant fields.
4. Click Apply. The IGMP Global Parameters are modified, and the device is updated.
Defining Multicast Bridging Groups
The Multicast Group page displays the ports and LAGs that are members of Multicast service
groups. The Port and LAG tables also reflect the manner in which the port or LAGs joined the
Multicast group. Ports can be added either to existing groups or to new Multicast service groups.
Multicast Group Page permits new Multicast service groups to be created. The Multicast Group Page
also assigns ports to a specific Multicast service address group.
The
Chapter 10: Configuring Multicast Forwarding
Defining Multicast Bridging Groups
1. Click Bridging > Bridge Multicast> Multicast Groups. The Multicast Group Page opens:
2. Click the Edit button. The Edit Multicast Group Page opens.
Edit Multicast Group Page
3. Define the Multicast Group Port Settings.
10
4. Click Apply. The Multicast group parameters are saved, and the device is updated.
Defining Multicast Forwarding
The Multicast Forward Page contains fields for attaching ports or LAGs to a device that is attached to
a neighboring Multicast router/switch. Once IGMP Snooping is enabled, Multicast packets are
forwarded to the appropriate port or VLAN.
The Spanning Tree Protocol (STP) provides tree topography for any arrangement of bridges. STP
also provides one path between end stations on a network, eliminating loops.
Loops occur when alternate routes exist between hosts. Loops in an extended network can cause
bridges to forward traffic indefinitely, resulting in increased traffic and reducing network efficiency.
The device supports the following Spanning Tree versions:
•Classic STP — Provides a single path between end stations, avoiding and eliminating loops.
•Rapid STP — Detects and uses network topologies that provide faster convergence of the
spanning tree, without creating forwarding loops.
•Multiple STP — Provides full connectivity for packets allocated to any VLAN. Multiple STP is
based on the RSTP. In addition, Multiple STP transmits packets assigned to different VLANs
through different MST regions. MST regions act as a single bridge.
11
•The Spanning Tree section contains the following pages:
The STP Properties Page contains parameters for enabling STP on the device. The STP Properties
Page is divided into three areas, Global Settings, Bridge Settings. and Designated Root.
1. Click Bridging > Spanning Tree > Properties. The STP Properties Page opens:
STP Properties Page
11
2. Define the relevant fields.
3. Click Apply. STP is enabled, and the device is updated.
Chapter 11: Configuring Spanning Tree
Defining STP Properties
While the classic spanning tree prevents Layer 2 forwarding loops in a general network topology,
convergence can take between 30-60 seconds. This time may delay detecting possible loops, and
propagating status topology changes. Rapid Spanning Tree Protocol (RSTP) detects and uses
network topologies that allow a faster STP convergence without creating forwarding loops.
1. Click Bridging > Spanning Tree > RSTP. The RSTP Page opens:
RSTP Page
11
2. Define the relevant fields.
3. Click Apply. The Rapid Spanning Tree Settings are defined, and the device is updated.
Chapter 11: Configuring Spanning Tree
Defining Rapid Spanning Tree
1. Click Bridging > Spanning Tree > RSTP. The RSTP Page opens:
2. Click the Edit button. The Edit Rapid Spanning Tree Page opens:
Edit Rapid Spanning Tree Page
Chapter
11
3. Define the relevant fields.
4. Click Apply. The Rapid Spanning Tree Settings are modified, and the device is updated.
Defining Multiple Spanning Tree
MSTP provides differing load balancing scenarios. For example, while port A is blocked in one STP
instance, the same port is placed in the Forwarding State in another STP instance. The MSTP Properties page contains information for defining global MSTP settings, including region names,
MSTP revisions, and maximum hops.
The MSTP section contains the following pages:
•Defining MSTP Properties
•Mapping MSTP Instances to VLAN
•Defining MSTP Instance Settings
•Defining MSTP Interface Settings
Chapter 11: Configuring Spanning Tree
Defining Multiple Spanning Tree
MSTP maps VLANs into STP instances. Packets assigned to various VLANs are transmitted along
different paths within Multiple Spanning Tree Regions (MST Regions). Regions are one or more
Multiple Spanning Tree bridges by which frames can be transmitted. In configuring MSTP, the MST
region to which the device belongs is defined. A configuration consists of the name, revision, and
region to which the device belongs.
The VLAN screen enables mapping VLANs to MSTP Instances.
1. Click Bridging > Spanning Tree > MSTP > Instance to VLAN. The Instance to VLAN Page opens:
Instance to VLAN Page
11
2. .Define the relevant fields.
3. Click Apply. The local user settings are modified, and the device is updated.
Chapter 11: Configuring Spanning Tree
Defining Multiple Spanning Tree
MSTP maps VLANs into STP instances. Packets assigned to various VLANs are transmitted along
different paths within Multiple Spanning Tree Regions (MST Regions). Regions are one or more
Multiple Spanning Tree bridges by which frames can be transmitted. In configuring MSTP, the MST
region to which the device belongs is defined. A configuration consists of the name, revision, and
region to which the device belongs.
Network Administrators can define MSTP Instances settings using the MSTP Instance Settings Page.
1. Click Bridging > Spanning Tree > MSTP > Instance Settings. The MSTP Instance Settings Page
opens:
MSTP Instance Settings Page
11
2. Define the relevant fields.
3. Click Apply. The local user settings are modified, and the device is updated.
Chapter 11: Configuring Spanning Tree
Defining Multiple Spanning Tree
The Simple Network Management Protocol (SNMP) provides a method for managing network
devices. The device
SNMP v1 and v2
SNMP agents maintain a list of variables that are used to manage the device. The variables are
defined in the Management Information Base (MIB). The MIB presents the variables controlled by the
agent. The SNMP agent defines the MIB specification format, as well as the format used to access
the information over the network. Access rights to the SNMP agents are controlled by access strings.
SNMP v3
SNMP v3 also applies access control and a new traps mechanism to SNMPv1 and SNMPv2 PDUs.
In addition, User Security Model (USM) is defined for SNMPv3 and includes:
•Authentication — Provides data integrity and data origin authentication.
supports the following SNMP versions:
12
•
Privacy — Protects against disclosure message content. Cipher Bock-Chaining (CBC) is used for
encryption.
and privacy are enabled on a SNMP message. However privacy cannot be enabled without
authentication.
•
Timeliness — Protects against message delay or message redundancy. The SNMP agent compares the
incoming message to the message time information.
•
Key Management — Defines key generation, key updates, and key use. The device supports SNMP
notification filters based on Object IDs (OID). OIDs are used by the system to manage device
features. SNMP v3 supports the following features:
–Security
–Feature Access Control
–Traps
The device generates copy traps.
The SNMP section contains the following sections:
•Configuring SNMP Security
•Defining Trap Management
Either authentication is enabled on an SNMP message, or both authentication
SNMP Views provide access or block access to device features or feature aspects. For example, a
view can be defined that states that SNMP Group A has Read Only (R/O) access to Multicast
groups, while SNMP Group B has Read-Write (R/W) access to Multicast groups. Feature access is
granted via the MIB name, or MIB Object ID.
To define SNMP views:
1. Click System > SNMP > Security > Views. The SNMP Views Page opens:
SNMP Views Page
12
2. Click the Add button. The Add SNMP View Page opens:
Add SNMP View Page
3. Define the relevant fields.
4. Click Apply. The SNMP views are defined, and the device is updated.
The SNMP Users Page provides information for creating SNMP groups, and assigning SNMP access
control privileges to SNMP groups. Groups allow network managers to assign access rights to
specific device features, or feature aspects.
1. Click System > SNMP > Security > Users. The SNMP Users Page opens:
SNMP Users Page
12
2. Click the Add button. The Add SNMP Group Membership Page opens:
Add SNMP Group Membership Page
3. Define the relevant fields.
4. Click Apply. The SNMP Group Membership settings are modified, and the device is updated.
The Edit SNMP User Page provides information for assigning SNMP access control privileges to
SNMP groups. The Edit SNMP User Page contains the following fields.
1. Click System > SNMP > Security > Users to open the Edit SNMP User Page
2. Define the relevant fields.
3. Click Apply. The SNMP User is modified, and the device is updated.
Define SNMP Groups
The SNMP Groups Profile Page provides information for creating SNMP groups and assigning
SNMP access control privileges to SNMP groups. Groups allow network managers to assign access
rights to specific device features, or features aspects.
1. Click System > SNMP > Security > Groups. The SNMP Groups Profile Page opens:
SNMP Groups Profile Page
12
2. Click the Add button. The Add SNMP Group Profile Page opens:
The Access rights are managed by defining communities in the SNMP Communities Page. When the
community names are changed, access rights are also changed. SNMP communities are defined
only for SNMP v1 and SNMP v2c.
To define SNMP Communities:
1. Click System > SNMP > Security > Communities. The SNMP Communities Page opens:
SNMP Communities Page
12
2. Click the Add button. The Add SNMP Community Page opens.
Add SNMP Community Page
3. Define the relevant fields.
4. Click Apply. The SNMP settings are modified, and the device is updated.