User Manual

24-Port Gigabit (Hi-Power) PoE+ Ethernet Smart Managed Pro Switch with 2 SFP Ports
Configuration Examples User Manual408
• Source IP Address. 192.168.187.0
• Source IP Mask. 0.0.0.255
For additional information about IP ACL rules, see
Configure rules for a basic IPv4 ACL
on page 319.
3. Click the Add
button.
4. On the IP Rules page, create a second rule for IP ACL 1 with the following settings:
•
Sequence Number. 2
• Action. Permit
• Match Every. T
rue
5. Click the Add
button.
6. On the IP Binding Configuration page, assign ACL ID 1 to the interface Gigabit ports 2, 3,
and
4, and assign a sequence number of 1. (See
Configure IP ACL interface bindings on
page 341.)
By default, this IP ACL is bound on the inbound direction, so it examines traffic as it
enters the switch.
7. Click the Apply
button.
8. On IP Binding Table page, view the interfaces and IP ACL binding information. (See
View or
delete IP ACL bindings in the IP ACL binding table on page 343)
The IP ACL in this example matches all packets with the source IP address
and subnet mask
of the Finance department’s network and deny it on the Ethernet interfaces 2, 3, and 4 of the
switch. The second rule permits all non-Finance traffic on the ports. The second rule is
required because an explicit deny all rule exists as the lowest priority rule.
Differentiated Services (DiffServ)
Standard IP-based networks are designed to provide best effort data delivery service. Best
effort service implies that the network delivers the data in a timely fashion, although there is
no guarantee that it does. During times of congestion, packets might be delayed, sent
sporadically, or dropped. For typical Internet applications, such as email and file transfer, a
slight degradation in service is acceptable and in many cases unnoticeable. However, any
degradation of service can negatively affect applications with strict timing requirements, such
as voice or multimedia.
Quality of Service (QoS) can provide consistent, predictable data delivery by distinguishing
between packets with strict timing requirements from those that are more tolerant of delay
.
Packets with strict timing requirements are given special treat
ment in a QoS-capable
network. With this in mind, all elements of the network must be QoS capable. If one node
cannot meet the necessary timing requirements, this creates a deficiency in the network path
and the performance of the entire packet flow is compromised.