Konfigurasi Switch Linksys
Konfigurasi Switch Linksys
Konfigurasi Switch Linksys
LGS326, LGS326P, and LGS326MP) offers a quick and easy solution to extend your office
network. The switch features gigabit speed ports, a web-based setup page for easy configuration
and management, and PoE+ support for networking devices to be located anywhere without the
need for alternating current (AC) outlets.
This article will provide you the instructions on how to access the switch’s web-based setup page.
Step 1:
Open a web browser and enter "http://192.168.1.251" in the Address bar and then press Enter .
Step 2:
Enter the Username and Password in the login page.
Step 3:
Click Log In.
You have now accessed the web-based setup page of the switch.
Setting up a VLAN on the Linksys Smart Gigabit Switch
When using factory default settings, the device automatically creates VLAN1 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.
It cannot be deleted.
It cannot be used for any special role, such as unauthenticated VLAN or voice VLAN. This is only
relevant for telephony 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.
When the VLAN ID (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 Port VLAN Identifier (PVID) of the ports to the VID of the new default VLAN.
The original default VID is removed from the device. It must be recreated to use it again.
Adds the ports as untagged VLAN members of the new default VLAN.
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 switch 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.
NOTE: Some of the subtabs may vary depending of the model number of your switch.
Step 1:
Access the switch’s web-based setup page. To learn how, click here.
Step 2:
Click Add to add one or more new VLANs. You can create either a single VLAN or a range of VLANs.
Step 4:
o 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 of VLANs, the maximum number of VLANs you can create at one time is 100.
Step 1:
Step 2:
Select an Interface Type (Port or LAG) and click Search. The Ports or LAGs and their VLAN membership
will be displayed.
Step 3:
Interface VLAN Mode - Select the interface mode for the VLAN. The options are:
o Access - The interface is an untagged member of a single VLAN. A port configured in this mode
is known as an Access Port.
o 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.
o 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 PVID of the VLAN to which incoming untagged and priority tagged frames are
classified. The possible values are 1 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. The possible values are:
o Admit All - The interface accepts all types of frames: untagged frames, tagged frames, and
priority tagged frames.
o 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 4:
Click Apply. The parameters are now written to the Running Configuration file.
Joining a VLAN
When a port has a 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 connected 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.
Step 1:
Step 2:
Step 3:
To add a Port or LAG to a VLAN, select it and click Join VLAN.
VLAN Mode
o 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.
o 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
o Forbidden - The interface is not allowed to join the VLAN. 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).
o 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.
o Untagged - The interface is an untagged member of the VLAN. Frames of the VLAN are
sent untagged to the interface VLAN.
o PVID - 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 4:
Click Apply. The port is now 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 has a 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 connected 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.
Use the VLAN Memberships page to display and configure the ports within a specific VLAN.
Step 1:
Select VLAN ID and Interface Type (Port or LAG) and click Search.
PVID - 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 the VLAN membership.
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. 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 now modified and written to the Running Configuration file.
VLAN groups
VLAN groups classify packets into VLANs based on their MAC addresses. 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.
MAC-based group
MAC-based VLAN classification enables 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
groups, with each group containing different MAC addresses.
These MAC-based groups can be assigned to specific Ports or LAGs. MAC-based groups cannot contain
overlapping ranges of MAC addresses on the same port.
The following table describes the availability of MAC-based groups in various SKUs:
Layer 3 No
Layer 3 No
Follow these steps to define a MAC-based group to assign a MAC address to a VLAN group ID
Step 1:
Step 2:
Assign the VLAN group to a VLAN (using the MAC-based VLAN page). The interfaces must be in
General Mode.
If the interface does not belong to the VLAN, manually assign it to the VLAN using the VLAN
Memberships page.
Step 3:
Click Apply. The MAC address is now assigned to a VLAN group ID.
Step 1:
Click Add.
Step 3:
NOTE: This MAC address cannot be assigned to any other VLAN group.
Step 4:
Your Ports or LAGs must be in General Mode. Follow these steps to assign a MAC-based VLAN group to
a VLAN on an interface:
Step 1:
Step 2:
Click Add.
Step 3:
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 to as the voice VLAN. If the voice devices are in different voice VLANs, IP
(Layer 3) routers are needed to provide communication.
The switch supports the Telephony (organizationally unique identifier) OUI mode and Auto 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 3 bytes of an ethernet
MAC address.
Voice endpoints
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.
A phone/endpoint may obtain the voice VLAN in the boot file it downloads from an TFTP
server. A DHCP server may specify the boot file and the TFTP server when it assigns an IP
address to the phone.
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 configured with Auto voice VLAN by Telephony OUI, voice VLAN
untagged packets are possible.
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 your 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 (QoS) based
on the CoS/802.1p value found in the voice stream. For telephony OUI voice streams, you can override
the Class of Service (CoS) 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 voice VLAN QoS decision has priority over any other QoS decision, except for the Policy
decision.
A new VLAN ID can be configured for the voice VLAN only if the current voice VLAN does not
have candidate ports.
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.
Step 1:
Click Configuration > VLAN Management > Voice VLAN > Feature Configuration.
Step 2:
CoS/802.1p - Select the CoS/802.1p value to be used by the LLDP-MED as a voice network
policy.
Step 3:
Telephony OUI Voice VLAN - Check this box to enable automatic adding of ports to voice VLAN
when OUI packets are received.
Remark CoS/802.1p - Check this box to enable remarking of packets with the CoS/802.1p value.
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:
NOTE: Go to Configuration> Discovery - LLDP > LLDP MED Network Policy to enable automatic
generation of network policy for voice.
Step 1:
Click Configuration > VLAN Management > Voice VLAN > Feature Configuration.
Step 2:
To delete all the OUIs, select the top checkbox. All the OUIs will be selected and can be deleted by
clicking Delete. If you then click Restore, the system recovers the known OUIs.
Step 3:
Telephony OUI - First six digits of the MAC address that are reserved for OUIs.
Quality of Service (QoS) attributes can be assigned per port to the voice packets in one of two modes:
All 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 Interfaces 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.
Step 1:
Click Configuration > VLAN Management > Voice VLAN > Telephony OUI Interfaces.
Step 2:
To configure an interface to be a candidate port of the Telephony OUI-based voice VLAN, click Edit.
Step 3:
Telephony OUI - If enabled, the interface is a candidate port of the Telephony OUI based voice
VLAN. When packets that match one of the configured Telephony OUIs are received, the port is
added to the voice VLAN.
o All - QoS attributes are applied on all packets that are classified to the voice VLAN.
o Telephony Source MAC Address - QoS attributes are applied only on packets from IP
phones.
Step 4:
Click Apply.
Backing up the Configuration File and saving configuration changes on the
Linksys Smart Gigabit Switch
Step 1:
Access the Linksys smart switch’s web-based setup page. To know how, click here.
Step 2:
On the web-based setup page, click Maintenance > File Management > Configuration File Copy.
Step 3:
On the Configuration File Copy screen, select Running Configuration File for Source File, and Startup
Configuration File for Destination File.
Step 4:
Click Apply to save the changes.
NOTE: Unless the Running Configuration File is copied to the Startup Configuration File, rebooting the
device will remove all changes made since the last time the file was saved. Save the Running
Configuration File to the Startup Configuration File before logging off to preserve any changes you
made during this session.
Step 1:
On the web-based setup page, click Maintenance > File Management > Configuration & Log.
Step 2:
On the Configuration & Log screen, select HTTP/HTTPS for File Transfer
Protocol, Backup for Command, and Running Configuration File for Source File.
Step 3:
Click Apply.
Step 4:
Step 1:
On the web-based setup page, click Maintenance > File Management > Configuration & Log.
Step 2:
Command: Backup
IP Version: IPv4
Click Apply.
The running config.txt will be saved to the device of the TFTP server.
Accessing the Menu CLI on the Linksys Smart Gigabit Switch
This article will give you instructions on how to access Menu CLI on the switch.
Step 1:
Open the Terminal tool and select Telnet.
Step 2:
Click to proceed.
Step 3:
Enter “admin” as the default User Name and Password.
You have now accessed the Menu CLI mode.
Restarting the Linksys Smart Gigabit Switch
Manual restart
Step 1:
Using a pin, press and hold the reset button for less than 10 seconds.
Step 2:
Release the button.
NOTE: The SYSTEM light will blink fast and the system will reboot.
Step 1:
Access the switch’s web-based setup page. To learn how, click here.
Step 2:
On the web-based setup page, click the Maintenance tab.
Step 3:
Click Reboot in the left panel, then click the Reboot button on the page.
Step 4:
When the confirmation prompt appears, click OK to continue.
Setting the Linksys Smart Gigabit Switch to factory defaults
Manual reset
Step 1:
Using a pin, press and hold the reset button for more than 10 seconds.
NOTE: The SYSTEM light will blink fast when the switch is ready to reset to factory defaults.
Step 2:
Release the button.
The switch will restore its configuration to factory defaults and restart itself.
Step 1:
Access the switch’s web-based setup page. To learn how, click here.
Step 2:
On the web-based setup page, click the Maintenance tab.
Step 3:
Click Reboot in the left panel.
Step 4:
Select Yes on the Restore to Factory Defaults option, then click Reboot to reset the switch to its default
settings.
Step 5:
When the confirmation prompt appears, click OK to continue.
Configuring QoS on the Linksys Smart Gigabit Switch
Feature Configuration
The Feature Configuration page contains fields for setting the QoS mode for the system (Basic or
Disabled, as described in the QoS Mode section). You can also define the default Class of Service (CoS)
priority for each interface in this section.
NOTE: Some of the subtabs may vary depending on the model number of your switch.
Step 1:
Step 2:
Step 3:
Select the Interface Type (Port or LAG) and click Search to display or modify all Ports or LAGs on the
device and their CoS information.
Default CoS - Default VPT value for incoming packets that do not have a VLAN Tag. The Default
CoS is 0. The default is only relevant for untagged frames and only if the system is in Basic
mode and Trust CoS is selected in the Basic QoS page.
Step 4:
Click Apply. The Running Configuration file is updated.
Step 1:
Step 3:
Step 4:
Click Apply. The interface default CoS value is saved to the Running Configuration file.
Queue Scheduling
The device supports four queues for each interface. Queue 4 is the highest priority queue. Queue 1 is
the lowest priority queue.
There are two ways to determine how traffic in queues are handled:
Strict Priority - Egress traffic from the highest-priority queue is transmitted first. Traffic from
the lower queues is processed only after the highest queue has been transmitted, thus
providing the highest level of priority of traffic to the highest numbered queue.
Weighted Round Robin (WRR) - In WRR mode, the number of packets sent from the queue is
proportional to the weight of the queue (the higher the weight, the more frames are sent). For
example, if there are a maximum of four queues possible and all four queues are WRR and the
default weights are used, Queue 1 receives 1 / 15 of the bandwidth (assuming all queues are
saturated and there is congestion), Queue 2 receives 2 / 15, Queue 3 receives 4 / 15 and Queue
4 receives 8 / 15 of the bandwidth. The type of WRR algorithm used in the device is not the
standard Deficit WRR (DWRR), but rather Shaped Deficit WRR (SDWRR).
The queuing modes can be selected in the Queue Scheduling page. When the queuing mode is by strict
priority, the priority sets the order in which queues are serviced, starting with Queue 4 (the highest
priority queue) and going to the next lower queue when each queue is completed.
When the queuing mode is Weighted Round Robin, queues are serviced until their quota has been used
up and then another queue is serviced.
It is also possible to assign some of the lower queues to WRR, while keeping some of the higher queues
in strict priority. In this case, traffic for the strict priority queues is always sent before traffic from the
WRR queues. Only after the strict priority queues have been emptied is traffic from the WRR queues
forwarded. (The relative portion from each WRR queue depends on its weight).
Step 2:
o Strict Priority - Traffic scheduling for the selected queue and all higher queues is based
strictly on the queue priority.
o WRR - Traffic scheduling for the selected queue is based on WRR. The period time is
divided between the WRR queues that are not empty, meaning they have descriptors to
egress. This happens only if strict priority queues are empty.
o WRR Weight - If WRR is selected, enter the WRR weight assigned to the queue.
o % of WRR Bandwidth - Displays the amount of bandwidth assigned to the queue. These
values represent the percent of the WRR weight.
Step 3:
Click Apply. The queues are now configured, and the Running Configuration file is updated.
CoS/8022.1p to Queue
The CoS/802.1p to Queue page maps 802.1p priorities to egress queues. The CoS/ 802.1p to Queue
Table determines the egress queues of the incoming packets based on the 802.1p priority in their VLAN
Tags. For incoming untagged packets, the 802.1p priority is the default CoS/802.1p priority assigned to
the ingress ports.
0 1 Background
1 1 Best Effort
2 2 Excellent Effort
4 3 Video
7 4 Network Control
By changing the CoS/802.1p to Queue mapping (CoS /802.1p to Queue page), the Queue schedule
method (Queue Scheduling page), and bandwidth allocation (Bandwidth page) it is possible to achieve
the desired quality of service in a network.
The CoS/802.1p to Queue mapping is applicable only if one of the following exists:
Queue 1 has the lowest priority; queue 4 has the highest priority.
Step 1:
Click Configuration> Quality of Service > Basic QoS> CoS/802.1p to Queue.
Step 2:
Output Queue - Select the egress queue to which the 802.1p priority is mapped. Either four or
eight egress queues are supported, where Queue 4 is the highest priority egress queue and
Queue 1 is the lowest priority.
Step 3:
For each 802.1p priority, select the Output Queue to which it is mapped.
Step 4:
Click Apply. The 801.1p priority values to queues are now mapped, and the Running Configuration file
is updated.
DSCP to Queue
The IP Differentiated Services Code Point (DSCP) to Queue page maps DSCP values to egress
queues. The DSCP to Queue Table determines the egress queues of the incoming IP packets based on
their DSCP values. The original VLAN Priority Tag (VPT) of the packet is unchanged.
By simply changing the DSCP to Queue mapping and the Queue schedule method and bandwidth
allocation, it is possible to achieve the desired quality of service in a network.
The DSCP to Queue mapping is applicable to IP packets if the device is in QoS Basic mode and DSCP is
the trusted mode. Non-IP packets are always classified to the best-effort queue.
DSCP 63 55 47 39 31 23 15 7
Queue 3 3 4 3 3 2 1 1
DSCP 62 54 46 (EF) 38 (AF3) 30 22 14 6
(AF33) (AF23)
Queue 3 3 4 3 3 2 1 1
DSCP 61 53 45 37 29 21 13 5
Queue 3 3 4 3 3 2 1 1
DSCP 60 52 44 36 28 20 12 4
(AF42) (AF32) (AF22) (AF12)
Queue 3 3 4 3 3 2 1 1
DSCP 59 51 43 35 27 19 11 3
Queue 3 3 4 3 3 2 1 1
DSCP 58 50 42 34 26 18 10 2
(AF41) (AF31) (AF21) (AF11)
Queue 3 3 4 3 3 2 1 1
DSCP 57 49 41 33 25 17 9 1
Queue 3 3 4 3 3 2 1 1
Queue 3 3 4 3 3 2 1 1
The Queue 4 is the highest queue and the default classes in the parentheses are defined by IETF.
Step 1:
Step 2:
Select the Output Queue (traffic forwarding queue) to which the DSCP value is mapped.
Step 3:
Bandwidth Control
The Bandwidth Control page enables you to define two values, Ingress Rate Limit and Egress Shaping
Rate, which determine how much traffic the system can receive and send.
The Ingress Rate Limit is the number of bits per second that can be received from the ingress
interface. Excess bandwidth above this limit is discarded.
The following values are entered for Egress Shaping:
Committed Information Rate (CIR) sets the average maximum amount of data allowed to be
sent on the egress interface, measured in bits per second.
Committed Burst Size (CBS) is the burst of data that is allowed to be sent, even though it is
above the CIR. This is defined in number of bytes of data.
Step 1:
Click Configuration > Quality of Service > Bandwidth Control. The Bandwidth page displays bandwidth
information for each interface.
Step 2:
Step 4:
Ingress Rate Limit - Enter the maximum amount of bandwidth allowed on the interface.
Ingress Committed Burst Size - Enter the maximum burst size of data for the ingress interface in
bytes of data. This amount can be sent even if it temporarily increases the bandwidth beyond
the allowed limit. This field is only available if the interface is a port.
NOTE: The above Ingress Rate Limit fields do not appear when the interface type is LAG.
Egress Committed Information Rate - Enter the maximum bandwidth for the egress interface.
Egress Committed Burst Size (CBS) - Enter the maximum burst size of data for the egress
interface in bytes of data. This amount can be sent even if it temporarily increases the
bandwidth beyond the allowed limit.
Step 5:
Click Apply. The bandwidth settings are now written to the Running Configuration file.
Egress Shaping
In addition to limiting transmission rate per port, which is done in the Bandwidth page, the device can
limit the transmission rate of selected egressing frames on a per queue basis. Egress rate limiting is
performed by shaping the output load.
The device limits all frames except for management frames. Any frames that are not limited are
ignored in the rate calculations, meaning that their size is not included in the limit total. Per-queue
Egress rate shaping can be disabled.
Click Configuration > Quality of Service > Egress Shaping. The Egress Shaping page displays the rate
limit and burst size for each queue.
Step 2:
Step 3:
Select a Port / LAG, and click Edit. This page enables shaping the egress for up to four queues on each
interface.
Step 4:
Step 5:
Committed Information Rate - Enter the maximum rate (CIR) in kilobits per second (Kbps). CIR
is the average maximum amount of data that can be sent.
Committed Burst Size - Enter the maximum burst size (CBS) in bytes. CBS is the maximum burst
of data allowed to be sent even if a burst exceeds CIR.
Step 6:
Click Apply. The bandwidth settings are written to the Running Configuration file.
Basic QoS
In Basic QoS mode, a specific domain in the network can be defined as trusted. Within that domain,
packets are marked with 802.1p priority and / or DSCP to signal the type of service they require. Nodes
within the domain use these fields to assign the packet to a specific output queue. The initial packet
classification and marking of these fields is done in the ingress of the trusted domain.
Step 1:
Step 2:
Select the trust-behavior using the Basic QoS page. The device supports CoS/802.1p trusted mode and
DSCP trusted mode. The CoS/802.1p trusted mode uses the 802.1p priority in the VLAN tag. DSCP
trusted mode use the DSCP value in the IP header.
In Basic QoS Mode, it is recommended that you disable the trusted mode at the ports where the
CoS/802.1p and/or DSCP values of the incoming packets are not trustworthy. Otherwise, it might
negatively affect the performance of your network. Incoming packets from ports that are disabled
without trust mode are forwarded in best effort.
The Basic QoS page contains information for enabling Trust on the device. This configuration is only
active when the QoS mode is in Basic mode. Packets entering a QoS domain are classified at the edge
of the QoS domain. Follow these steps to define the Trust configuration.
Step 1:
Select the Trusted Mode while the device is in Basic mode. The Trusted mode determines the queue to
which the packet is assigned:
CoS/802.1p - Traffic is mapped to queues based on the VPT field in the VLAN tag, or based on
the per-port default CoS/802.1p value (if there is no VLAN tag on the incoming packet), the
actual mapping of the VPT to queue can be configured in the mapping CoS / 802.1p to Queue
page.
DSCP - All IP traffic is mapped to queues based on the DSCP field in the IP header. The actual
mapping of the DSCP to queue can be configured in the DSCP to Queue page. If traffic is not IP
traffic, it is mapped to the best effort queue.
CoS / 802.1p-DSCP - All IP traffic is mapped to queues based on the values in their DSCP
field. All non IP traffic is mapped to queues based on their CoS/802.1p value.
Step 3:
To disable QoS on a port, click Edit, select a Port or LAG, uncheck the QoS State box.
Step 4:
Click Apply. The Running Configuration file is now updated with the new settings.
Queues Statistics
The Queues Statistics page displays queue statistics, including statistics of forwarded and dropped
packets, based on interface, queue, and drop precedence.
Step 1:
Click Configuration > Quality of Service > QoS Statistics > Queues Statistics.
Refresh Rate - Select the time period that passes before the interface ethernet statistics are
refreshed.
Counter Set
o Set 1 - Displays the statistics for Set 1 that contains all interfaces and queues with a high DP
(Drop Precedence).
o Set 2 - Displays the statistics for Set 2 that contains all interfaces and queues with a low DP.
Drop Precedence - Lowest drop precedence has the lowest probability of being dropped.
Step 2:
Click Add.
Step 3:
Enter these parameters.
o Set 1 - Displays the statistics for Set 1 that contains all interfaces and queues with a high
DP (Drop Precedence).
o Set 2 - Displays the statistics for Set 2 that contains all interfaces and queues with a low
DP.
o Port - Selects the port on the selected unit number for which statistics are displayed.
o All Ports - Specifies that statistics are displayed for all ports.
Drop Precedence - Enter drop precedence that indicates the probability of being dropped.
Step 4:
Click Apply. The Queue Statistics counter is now added and the Running Configuration file is updated.
You should now have successfully configured the QoS of your Linksys Smart Gigabit Switch.