Falcon
M-Class
| User Guide
453
8.2
Alphabetical Glossary of Terms
ACE
A
ccess
C
ontrol
E
ntry. It describes access
permission associated with a particular ACE ID.
There are three ACE frame types (
, and IPv4) and two ACE
actions (permit and deny). The ACE also contains many detailed, different parameter
options that are available for individual application.
ACL
A
ccess
C
ontrol
L
containing access control entries that specify individual users or groups
permitted or denied to specific traffic objects, such as a process or a
program.
Each accessible traffic object contains an identifier to its ACL. The privileges determine
whether there are specific traffic object access rights.
ACL implementations can be quite complex, for example, when the ACEs are prioritized
for the various situation. In networking, the ACL refers to a list of service ports or
network services that are available on a host or server, each with a list of hosts or
servers permitted or denied to use the service. ACL can generally be configured to control
inbound traffic, and in this context, they are similar to firewalls.
There are 3 web-pages associated with the manual ACL configuration:
ACL|Access Control List
: The web page shows the ACEs in a
prioritized way, highest (top) to lowest (bottom). Default the table is
empty. An ingress frame will only get a hit on one ACE even though
there are more matching ACEs. The first matching ACE will take action
(permit/deny) on that frame and a counter associated with that ACE is
incremented. An ACE can be associated with a Policy, 1 ingress port, or
any ingress port (the whole switch). If an ACE Policy is created then that
Policy can be associated with a group of ports under the "Ports" web-
page. There are number of Parameters that can be configured with an
ACE. Read the Web page help text to get further information for each of
them. The maximum number of ACEs is 64.
ACL|Ports
: The ACL Ports configuration is used to assign a Policy ID to
an ingress port. This is useful to group ports to obey the same traffic
rules. Traffic Policy is created under the "Access Control List" - page. You
can you also set up specific traffic properties (Action / Rate Limiter / Port
copy, etc) for each ingress port. They will though only apply if the frame
gets past the ACE matching without getting matched. In that case a
counter associated with that port is incremented. See the Web page help
text for each specific port property.
ACL|Rate Limiters
: Under this page you can configure the rate limiters.
Содержание Falcon Gen-3 M-Class
Страница 1: ...Falcon Gen 3 M Class User Guide nFalcon M Falcon MX Falcon MX Software version 7 4 0 www fibrolan com...
Страница 16: ...Falcon M Class User Guide 16 2 System Description 2 1 Block Diagram Figure 1 7 M Class functional block diagram...
Страница 90: ...Falcon M Class User Guide 90...
Страница 107: ...Falcon M Class User Guide 107 Figure 4 57 DSCP Translation...
Страница 139: ...Falcon M Class User Guide 139...
Страница 187: ...Falcon M Class User Guide 187 Figure 4 99 RADIUS Statistics for Server...
Страница 197: ...Falcon M Class User Guide 197 4 11 6 SyncCenter Status Figure 4 104 Sync Center Status...
Страница 214: ...Falcon M Class User Guide 214...
Страница 227: ...Falcon M Class User Guide 227...
Страница 234: ...Falcon M Class User Guide 234...
Страница 328: ...Falcon M Class User Guide 328 Figure 4 189 Connectivity check to a MIP and MEP using Loopback function...
Страница 358: ...Falcon M Class User Guide 358 Figure 4 216 sFlow Configuration displays...
Страница 376: ...Falcon M Class User Guide 376...
Страница 403: ...Falcon M Class User Guide 403...
