This online help
is based on the structure of the switch's web interface tab bar and
links. For each web interface screen, a summary of information is provided
for each feature. For detailed information on switch features, refer
to the User Guide.
To locate help information
for a particular web interface tab, click on the appropriate link below.
Displays or configures
basic parameters for the switch system.
Displays basic switch identification parameters. This information
can be used to precisely identify the system by configuring a device
name, location and contact information.
Setting: The IP Configuration tab enables you to configure
the switch's IP address for management access over the network. The
default IP address for the switch is 192.168.1.254 with a netmask
255.255.255.0. You may need to change these default settings to values
that are compatible with your network. You may also need to a establish
a default gateway between the switch and management stations that
exist on another network segment. You can manually configure a static
IP address, or direct the switch to obtain an address from a Boot
Protocol (BOOTP) or Dynamic Host Configuration Protocol (DHCP) server.
If DHCPor BOOTP is enabled, IP will not function until a reply has
been received from the server.
Management Interface is the ID (1-4094) of the configured VLAN through
which you can gain management access to the switch. By default,
all ports on the switch are members of VLAN 1, so a management station
can be connected to any port on the switch. However, if other VLANs
are configured and you change the Management VLAN, you may lose
management access to the switch. In this case, you should reconnect
the management station to a port that is a member of the Management
Enables the switch's SNTP client or sets the system clock manually.
Maintaining an accurate time on the switch enables the system log
to record meaningful dates and times for event entries.
VLAN, trunking, and rate limiting for the switch system.
You can use the Port Setting screen to enable or disable an interface,
set auto-negotiation and the interface capabilities to advertise,
or manually fix the speed, duplex mode, and flow control. Note that
auto-negotiation must be disabled before you can configure or force
an interface to use the Speed/Duplex Mode or Flow Control options.
You can create multiple links between switches that work as one
virtual, aggregate link. An aggregate link offers a dramatic increase
in bandwidth for network segments where bottlenecks exist, as well
as providing a fault-tolerant link between two switches. You can
create up to four aggregate links on the switch. Each aggregate
link can contain up to 8 ports. The switch's two Gigabit ports can
also be configured as an aggregate link. The ports at both ends
of an aggregate link must be configured in an identical manner,
including speed, full-duplex mode, flow control, VLAN assignments,
and CoS settings.
The switch supports both static trunking and dynamic Link Aggregation
Control Protocol (LACP). Static trunks have to be manually configured
at both ends of the link, and the switches must be compatible with
the Cisco EtherChannel standard. LACP configured ports can automatically
negotiate a trunked link with LACP-configured ports on another device.
You can configure any number of ports on the switch as LACP, as long
as they are not already configured as part of a static trunk. If ports
on another device are also configured as LACP, the switch and the
other device will negotiate a trunk link between them. If an LACP
trunk consists of more than eight ports, all other ports will be placed
in a standby mode. Should one link in the trunk fail, one of the standby
ports will automatically be activated to replace it.
- Set Port
Actor: Sets the local switch side of an aggregate link. Ports
must be configured with the same System Priority to join the same
link group. The LACP administration key must be set to the same
value for ports that belong to the same link group. If a link
goes down, the Port Priority is used to select a backup link.
- Set Port
Partner: Sets the remote side of an aggregate link; that is,
the ports on the attached device. The command attributes have
the same meaning as those used for the Port Actor. However, configuring
LACP settings for the partner only applies to its administrative
state, not its operational state, and will only take effect the
next time an aggregate link is established with the partner.
- PoE Power
Setting: The switch can provide DC power to a wide range
of connected devices based on the IEEE 802.3af (802.3af) Power-over-Ethernet
(PoE) standard. Once configured to supply power, an automatic detection
process is initialized by the switch that is authenticated by a PoE
signature from the connected device. Detection and authentication
prevent damage to non-802.3af compliant devices.
The switch supports
up to 128 VLANs based on the IEEE 802.1Q standard. Before enabling VLANs
for the switch, you must first assign each port to the VLAN group(s)
in which it will participate. By default all ports are assigned to VLAN
1 as untagged ports. Add a port as a tagged port if you want it to carry
traffic for one or more VLANs, and any intermediate network devices
or the host at the other end of the connection supports VLANs. Then
assign ports on the other VLAN-aware network devices along the path
that will carry this traffic to the same VLAN(s). However, if you want
a port on this switch to participate in one or more VLANs, but none
of the intermediate network devices nor the host at the other end of
the connection supports VLANs, then you should add the port to the VLAN
as an untagged port.
You can configure
VLAN behavior for specific interfaces, including the default VLAN identifier
(PVID), accepted frame types, ingress filtering. and VLAN membership
VLAN: Enables you to create a single VLAN or a range of
VLANs. To create a VLAN, enter the VLAN ID and VLAN name, up to
32 characters long. Mark the Enable checkbox to activate the VLAN,
and click Add. To edit or remove a VLAN, select it from the VLAN
list, then click Update or Remove.
Setting: Enables you to configure VLAN behavior for specific
interfaces, including the mode, accepted frame type, VLAN identifier
(PVID), and ingress filtering.
to VLAN: Configures VLAN port members for the selected
VLAN index. Assign ports as tagged if they are connected to 802.1Q
VLAN compliant devices, or untagged they are not connected to any
to Port: Assigns VLAN groups to selected interfaces.
You can display
standard statistics on network traffic from the Interfaces Group and
Ethernet-like MIBs, as well as a detailed breakdown of traffic based
on the RMON MIB. Interfaces and Ethernet-like statistics display errors
on the traffic passing through each port. This information can be used
to identify potential problems with the switch (such as a faulty port
or unusually heavy loading). RMON statistics provide access to a broad
range of statistics, including a total count of different frame types
and sizes passing through each port.
Statistics: To view the interface statistics for a port,
select the required interface from the drop-down menu and click
Query. To set a refresh rate, to update the interface statistics,
select a time interval from the Refresh Rate drop-down menu.
History: The RMON History Group allows you to monitor your
network for common errors and overall traffic rates. The History
Control Table allows you to add, edit and delete collection entries,
or to select a specific index entry and then view the historical
data in table form.
Alarms: The RMON Alarm Group allows you to record important
events and critical network problems. The RMON Alarm and Event Control
Tables are used together to define specific criteria that will generate
response events. Alarms can be set to test data over any specified
time interval and can monitor absolute or changing values, such
as a statistical counter reaching a specific value, or a statistic
changing by a certain amount over a set interval. Alarms can be
set to respond to either rising or falling thresholds. The Alarm
Control Table allows you to add, edit and delete specific index
Events: An RMON Event determines the action to take when
an alarm is triggered. The response to an alarm can include logging
the alarm or sending an SNMP trap message. If the response corresponding
to an alarm has not yet been defined, use the RMON Event screen
to configure the Event Setting table. To display each time an event
was triggered by an alarm, first highlight an entry in the Event
Control Table and then click on the View Log Table button. The Log
Table shows the log index number, the time of an event, and the
description of the event that activated the entry.
Utilization: Displays the percentage of bandwidth currently
utilized on each port of the Switch.
Statisitcs: The Switch can display statistics for 802.1X
protocol exchanges for any port. To view the statistics for a port,
select the required interface from the drop-down menu and click
Query. To set a refresh rate for updating the 802.1X statistics,
select a time interval from the Refresh Rate drop-down menu.
An ACL is a sequential
list of permit or deny conditions that apply to IP addresses, MAC addresses,
or other more specific criteria. The switch tests ingress packets against
the conditions in an ACL one by one. A packet will be accepted as soon
as it matches a permit rule, or dropped as soon as it matches a deny
rule. If no rules match for a list of all permit rules, the packet is
dropped; and if no rules match for a list of all deny rules, the packet
is accepted. Each ACL can have up to 32 rules and the maximum number
of ACLs is 32. To filter incoming packets, first create an ACL, add
the required rules and then bind the ACL to specific ports.
The Security tab
provides configuration for ACL port binding, authentication servers,
IEEE 802.1X, port security, HTTPS, and management IP filtering.
Binding: After configuring ACLs, you can bind them to the ports
that need to filter traffic. The switch only supports ACLs for ingress
filtering. You can only bind one IP ACL to any port, and one MAC
ACL globally, for ingress filtering.
Setting : Remote Authentication Dial-in User Service (RADIUS)
and Terminal Access Controller Access Control System Plus (TACACS+)
are logon authentication protocols that use software running on a
central server to control access to RADIUS-aware or TACACS-aware devices
on the network. An authentication server contains a database of multiple
user name/password pairs with associated privilege levels for each
user that requires management access to the switch. By default, management
access is always checked against the authentication database stored
on the local switch. If a remote authentication server is used, you
must specify the authentication sequence and the corresponding parameters
for the remote authentication protocol. Local and remote logon authentication
control management access via the console port, web browser, or Telnet.
Settings: Up to five RADIUS servers can be configured. The
switch attempts authentication using the listed sequence of servers.
The process ends when a server either approves or denies access
to a user.
Settings: Connection details for only one TACACS server can
- 802.1X Setting:
The IEEE 802.1X (802.1X) standard defines a port-based access control
procedure that prevents unauthorized access to a network by requiring
users to first submit credentials for authentication. Access to all
switch ports in a network can be centrally controlled from a RADIUS
server, which means that authorized users can use the same credentials
for authentication from any point within the network. Each client
that needs to be authenticated must have 802.1X client software installed
and properly configured. The RADIUS server and 802.1X client also
have to support the same Extensible Authentication Protocol (EAP)
authentication type – MD5. Note that the 802.1X protocol must first
be enabled globally for the switch system before port settings are
802.1X is enabled, you need to configure the parameters for the authentication
process that runs between the client and the switch (the authenticator),
as well as the client identity lookup process that runs between the
switch and authentication server.
Mode: Allows single or multiple hosts (clients) to connect
to an 802.1X-authorized port. When Multi-Host operation is selected
for a port, the maximum number of hosts (1-1024) that can be authenticated
on the port can be set.
Sets the port authentication mode to one of the following options.
Auto - Requires an 802.1X-aware client to be authorized
by the authentication server. Clients that are not 802.1X-aware
are denied access. Force-Authorized - Forces the port to
grant access to all clients, either 802.1X-aware or otherwise.
Force-Unauthorized - Forces the port to deny access to
all clients, either 802.1X-aware or otherwise.
Sets the 802.1X client to be re-authenticated after the interval
specified by the Re-authen Period. Re-authentication can
be used to detect if a new device is plugged into a switch port.
Port security is a feature that allows you to configure a switch
port with one or more device MAC addresses that are authorized to
access the network through that port. When port security is enabled
on a port, the switch stops learning new MAC addresses on the specified
port when it has reached a configured maximum number. Only incoming
traffic with source addresses already stored in the dynamic or static
address table will be accepted as authorized to access the network
through that port. If a device with an unauthorized MAC address
attempts to use the switch port, the intrusion will be detected
and the switch can automatically take action by disabling the port
and sending a trap message. Note that when a port is disabled (shut
down) due to a security violation, it must be manually re-enabled
from the Port Configuration screen.
- HTTPS Settings:
You can configure the switch to enable the Secure Hypertext Transfer
Protocol (HTTPS) over the Secure Socket Layer (SSL), providing secure
access (that is, an encrypted connection) to the switch’s web interface.
Both the HTTP and HTTPS service can be enabled independently on the
switch. However, you cannot configure both services to use the same
UDP port. If you change the default HTTPS port number, clients attempting
to connect to the HTTPS server must specify the port number in the
URL in this format: https://device:port_number
ACL : You create a list of up to 16 IP addresses or IP address
groups that are allowed management access to the switch through
the web interface, SNMP, or Telnet. The management interfaces are
open to all IP addresses by default. Once you add an entry to a
filter list, access to that interface is restricted to the specified
addresses. IP address can be configured for SNMP, web and Telnet
access respectively. Each of these groups can include up to five
different sets of addresses, either individual addresses or address
Settings: The Secure Shell (SSH) includes server/client
applications that can provide remote management access to the Switch
and act as a secure replacement for Telnet. When the client contacts
the Switch through the SSH protocol, the Switch generates a public-key
that the client uses along with a local user name and password for
access authentication. SSH also encrypts all data transfers passing
between the Switch and SSH-enabled management station clients, and
ensures that data traveling over the network arrives unaltered.
Note that you need to install an SSH client on the management station
to access the Switch for management through the SSH protocol. The
Switch supports both SSH Version 1.5 and 2.0.
Host-key Settings: A host public/private key pair is used
to provide secure communications between an SSH client and the Switch.
After generating this key pair, you must provide the host public
key to SSH clients and import the client’s public key to the
Quality of Service
(QoS) allows you to specify which data packets have greater precedence
when traffic is buffered in the switch due to congestion. The switch
supports Class of Service (CoS) with four priority queues for each port.
Data packets in a port’s high-priority queue will be transmitted before
those in the lower-priority queues. You can set the default priority
for each interface and configure the mapping of frame priority tags
to the switch’s priority queues.
- CoS Setting:
The switch processes CoS priority tagged traffic by using the four
priority queues for each port, with service schedules based on strict
or Weighted Round Robin (WRR). Up to eight separate traffic priorities
are defined in the IEEE 802.1p CoS standard. The default priority
levels are assigned according to recommendations in IEEE 802.1p, however
you can map the priority levels to the switch’s output queues in any
way that benefits application traffic for your own network.
- Port to
CoS: You can specify the default port priority for each interface
on the switch. All untagged packets entering the switch are tagged
with the specified default port priority and then sorted into
the appropriate priority queue at the output port. The default
priority does not apply to IEEE 802.1Q VLAN tagged frames. If
the incoming frame is an IEEE 802.1Q VLAN tagged frame, the IEEE
802.1Q priority bits are used.
- Queue Setting:
You can set the switch to service the queues based on a strict rule
that requires all traffic in a higher priority queue to be transmitted
before lower priority queues are serviced, or use Weighted Round-Robin
(WRR) queuing that specifies a relative weight of each queue. WRR
uses a predefined relative weight for each queue that determines the
percentage of service time the switch services each queue before moving
on to the next queue. Note that the queue weighting is fixed for the
Switch and cannot be configured.
- IP DSCP:
The Switch supports a common method of prioritizing layer 3/4 traffic
to meet application requirements. Traffic priorities can be specified
in the IP header of a frame using the priority bits in the Type of
Service (ToS) octet. The ToS octet contains six bits that define the
Differentiated Services Code Point (DSCP) service. When these services
are enabled, the priorities are mapped to a Class of Service value
by the Switch and the traffic then sent to the corresponding output
queue. Because different priority information may be contained in
the traffic, the Switch maps priority values to the output queues
using first IP DSCP Priority and then Default Port Priority.
Setting: Differentiated Services (DiffServ) provides policy-based
management mechanisms used for prioritizing network resources to meet
the requirements of specific traffic types on a per hop basis. Each
packet is classified upon entry into the network based on access lists,
IP Precedence, DSCP values, or VLAN lists. Using access lists allows
you select traffic based on Layer 2, Layer 3, or Layer 4 information
contained in each packet. Based on configured network policies, different
kinds of traffic can be marked for different kinds of forwarding.
Switches and routers along a network path can use class information
to prioritize the resources allocated to different traffic classes.
The manner in which an individual device handles traffic in the DiffServ
architecture is called per-hop behavior. All devices along a path
should be configured in a consistent manner to construct a consistent
end-to-end QoS solution.
Class Map: A class map is used for matching packets to a specified
class. A traffic class can be based on an ACL, a DSCP or IP Precedence
value, or a VLAN. You can only specify one item to match when
assigning ingress traffic to a class map. A class map is used
with a policy map to create a service policy for a specific interface.
Note that one or more class maps can be assigned to a policy map.
Policy Map: A policy map defines a quality of service for
traffic that matches a defined class. You can set the quality
of service that a packet will receive (in the Action field) by
defining the maximum throughput and burst rate (in the Meter field),
and the action that results from a policy violation (in the Exceed
field). After using the policy map to define packet classification,
service tagging, and bandwidth policing, it must be assigned to
a specific interface by a service policy to take effect.
- DiffServ Port
Binding: Binds a policy map to the ingress queue of a particular
interface. You can only bind one policy map to an interface. The switch
only allows you to bind a policy map to an ingress queue.
- Rate Limit:
This function allows the network manager to control the maximum rate
for traffic transmitted or received on a port. Rate limiting is configured
on ports at the edge of a network to limit traffic coming into or
out of the network. Traffic that falls within the rate limit is transmitted,
while packets that exceed the acceptable amount of traffic are dropped.
Rate limiting can be applied to individual ports or LAGs.
The Spanning Tree
Algorithm (STA) can be used to detect and disable network loops, and
to provide backup links between switches, bridges or routers. This allows
the switch to interact with other bridging devices (that is, an STA-compliant
switch, bridge or router) in your network to ensure that only one route
exists between any two stations on the network, and provide backup links
which automatically take over when a primary link goes down. The spanning
tree algorithms supported by the switch include: IEEE 802.1D Spanning
Tree Protocol (STP) and IEEE 802.1w Rapid Spanning Tree Protocol (RSTP).
Displays a summary of the current bridge STA information that applies
to the entire switch.
Configures STA settings that apply to the entire switch. Note that
RSTP supports connections to either STP or RSTP nodes by monitoring
the incoming protocol messages and dynamically adjusting the type
of protocol messages the switch transmits.
- STP Port Setting:
You can configure RSTP attributes for specific interfaces, including
port priority, path cost, link type, and edge port. You may use a
different priority or path cost for ports of the same media type to
indicate the preferred path, link type to indicate a point-to-point
connection or shared-media connection, and edge port to indicate if
the attached device can support fast forwarding.
The Internet Group
Management Protocol (IGMP) runs between hosts and their immediately
adjacent multicast router/switch. IGMP is a multicast host registration
protocol that allows any host to inform its local router that it wants
to receive transmissions addressed to a specific multicast group. A
router, or multicast-enabled switch, can periodically ask their hosts
if they want to receive multicast traffic. If there is more than one
router/switch on the LAN performing IP multicasting, one of these devices
is elected “querier” and assumes the role of querying the
LAN for group members. It then propagates the service requests on to
any adjacent multicast switch/router to ensure that it will continue
to receive the multicast service. Based on the group membership information
learned from IGMP, a router/switch can determine which (if any) multicast
traffic needs to be forwarded to each of its ports. At Layer 3, multicast
routers use this information, along with a multicast routing protocol
such as DVMRP or PIM, to support IP multicasting across the Internet.
Note that IGMP neither alters nor routes IP multicast packets. A multicast
routing protocol must be used to deliver IP multicast packets across
You can configure the switch to forward multicast traffic intelligently.
Based on the IGMP query and report messages, the switch forwards
traffic only to the ports that request multicast traffic. A router,
or multicast-enabled switch, can periodically ask their hosts if
they want to receive multicast traffic. If there is more than one
router/switch on the LAN performing IP multicasting, one of these
devices is elected “querier”
nd assumes the role of querying the
LAN for group members. It then propagates the service requests on
to any upstream multicast switch/router to ensure that it will continue
to receive the multicast service.
Port: Multicast filtering can be dynamically configured using
IGMP, but for certain applications that require tighter control,
you can statically configure a multicast service on the switch.
First add all the ports attached to participating hosts to a common
VLAN, then assign the multicast service to that VLAN group. Note
that static multicast addresses are never aged out from the switch.
Port: Depending on your network connections, the switch may
not always be able to locate the IGMP querier. Therefore, if the
IGMP querier is a known multicast router/ switch connected over
the network to an interface (port or trunk) on the switch, you can
manually configure the interface (and a specified VLAN) to join
all the current multicast groups supported by the attached router.
This can ensure that multicast traffic is passed to all the appropriate
interfaces within the switch.
Query: Displays the ports on the Switch attached to a neighboring
multicast router/switch for each VLAN and multicast IP address.
Select a VLAN ID and the IP address for a multicast service from
the drop-down menus. The Switch will display all the interfaces
that are propagating this multicast service.
Port Query: Multicast routers that are attached to ports
on the Switch use information obtained from IGMP to support IP multicasting
across the Internet. These routers may be dynamically discovered
by the Switch or statically assigned to an interface on the Switch.
You can use the Router Port Query screen to display the ports on
the Switch attached to a neighboring multicast router/switch for
each VLAN ID.
This tab provides
user account, file management, system reset, SNMP, logging, jumbo frame,
cable testing, and other functions for the switch system.
The Switch supports up to 5 user names and passwords for management
access (console and web interfaces). The default user name is “admin”
with no password. You should therefore assign a new password for
the “admin” user account and store it in a safe place.
The default "admin" account cannot be deleted from the
system. As well as the default “admin” account, up to
five other user-defined accounts can be created on the Switch. To
create a new user account, enter a user name and password - up to
eight characters long - confirm the password, and then click Add.
To change the password for a specific user, select the user name
from the list, enter the new password, confirm the password by entering
it again, and then click Update.
Upgrade : Downloads or uploads switch firmware files from a
TFTP server. The Switch allows the runtime software and diagnostic
boot files to be upgraded. You must specify “Upgrade”
to download a new firmware file or “Backup” to save
a firmware file to the server. Select the Upgrade or Backup radio
button, then the file type from the drop-down menu, either Software
Image or Boot Code. Enter the IP address of the TFTP server, specify
the file name of the software on the server, and then click Save
Downloads or uploads switch configuration files from a TFTP server.
The Switch allows the start-up configuration to be saved or restored
from a TFTP server. You must specify “Upgrade” to download
a new configuration file or “Backup” to save a configuration
file to the server. Select the Upgrade or Backup radio button. Enter
the IP address of the TFTP server, specify the name of the configuration
file on the server, and then click Save Settings.
Upgrade: Downloads new switch runtime software from the
local web management PC. Enter the file name of the software or
use the Browse button to locate the file on the PC, then click Save
Default: Restores the Switch’s factory default settings.
Click the Reset to Factory Default Configuration button, then click
OK to confirm and restart the Switch.
Restarts the Switch retaining the current configuration settings.
Click the Reboot button, then click OK to confirm.
Simple Network Management Protocol (SNMP) is a communication protocol
designed specifically for managing devices on a network. Equipment
commonly managed with SNMP includes switches, routers and host computers.
SNMP is typically used to configure these devices for proper operation
in a network environment, as well as to monitor them to evaluate performance
or detect potential problems.
- SNMP Community:
A community string that acts like a password and permits access
to the SNMP protocol. You may configure up to five community strings
authorized for management access. The default strings are “public”
(read-only) and “private” (read/write). For security reasons,
you should consider removing the default strings.
- Trap Manager:
Traps indicating status changes are issued by the Switch to specified
trap managers. You must specify trap managers so that key events
are reported by the Switch to your management station (a computer
using network management software). You can specify up to five
management stations that will receive authentication failure messages
and other notification messages from the Switch.
The switch allows you to control the logging of error messages, including
the type of
events that are recorded in switch memory, logging to a remote System
server, and displays a list of recent event messages.
Logging: The system allows you to enable or disable event
logging, and specify which levels are logged to RAM or flash memory.
Severe error messages that are logged to flash memory are permanently
stored in the switch to assist in troubleshooting network problems.
Up to 4096 log entries can be stored in the flash memory, with
the oldest entries being overwritten first when the available
log memory (256 kilobytes) has been exceeded. The System Logs
page allows you to configure and limit system messages that are
logged to flash or RAM memory. The default is for event levels
0 to 3 to be logged to flash and levels 0 to 7 to be logged to
Allows you to configure the logging of messages that are sent
to syslog servers. You can also limit the event messages sent
to only those messages at or above a specified level.
Setting: To alert system administrators of problems,
the switch can use SMTP (Simple Mail Transfer Protocol) to send
email messages when triggered by logging events of a specified
level. The messages are sent to specified SMTP servers on the
network and can be retrieved using POP or IMAP clients.
Sends ICMP echo request packets to another node on the network to
see if it can be reached. Enter the IP address or host name of the
device you want to ping, then click Go. The ping results are displayed
in the Ping Status text box.
To test the connection quality of an attached cable, click on the
test button for the port (ports 1-48 only). Note that the cable
needs to be connected at both ends, otherwise the test will fail.
The cable test results for each port are displayed in the table.
Frame: The Switch provides more efficient throughput for
large sequential data transfers by supporting jumbo frames up to
9216 bytes on the Gigabit ports and mini jumbo frames on the 10/100Mbps
ports. Compared to standard Ethernet frames that run only up to
1.5 KB, using jumbo frames significantly reduces the per-packet
overhead required to process protocol encapsulation fields.
You can mirror traffic from any source port to a target port for
real-time analysis. You can then attach a logic analyzer or RMON
probe to the target port and study the traffic crossing the source
port in a completely unobtrusive manner. The switch supports only
a single mirror session from the source port to target port. Note
that the target port speed should match or exceed source port speed,
otherwise traffic may be dropped.
Database: Switches store the addresses for all known devices in
a forwarding database. This information is used to forward traffic
directly between the inbound and outbound ports. All the addresses
learned by monitoring traffic are stored in the dynamic address table.
You can also manually configure static addresses that are bound to
a specific port.
Aging: Sets the aging time for entries in the forwarding
database. The aging time is used to age out dynamically learned
Addresses: Dynamic addresses in the MAC addresses table are
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.
Addresses: A static address can be assigned to a specific
interface on the switch. Static addresses are bound to the assigned
interface and are not moved. When a static address is seen on
another interface, the address is ignored and is not written to
the address table.
Closes the web interface