![Alcatel-Lucent 7950 SR Скачать руководство пользователя страница 35](http://html1.mh-extra.com/html/alcatel-lucent/7950-sr/7950-sr_system-management-manual_2892148035.webp)
Security
7950 SR OS System Management Guide
Page 35
CPU Protection Extensions ETH-CFM
CPU protection has been extended to provide the ability to explicitly limit the amount of
ETH-CFM traffic that arrives at the CPU for processing. ETH-CFM packets that are
redirected to the CPU by either a Management Endpoint (MEP) or a Management
Intermediate Point (MIP) will be subject to the configured limit of the associated policy. Up to
four CPU protection policies may include up to ten individual eth-cfm specific entries. The
eth-cfm entries allow the operator to apply a packet per second rate limit to the matching
combination of level and opcode, for eth-cfm packet that are redirected to the CPU. Any eth-
cfm traffic that is redirected to the CPU by a Management Point (MP) that does not match any
entries of the applied policy is still subject to the overall rate limit of the policy itself. Any eth-
cfm packets that are not redirected to the CPU are not subject to this function and are treated
as transit data, subject to the applicable QoS policy.
The operator first creates a CPU Policy and includes the required eth-cfm entries. Overlap is
allowed for the entries within a policy, first match logic is applied. This means ordering the
entries in the proper sequence is important to ensure the proper behavior is achieved. Even
thought the number of eth-cfm entries is limited to ten, the entry numbers have a valid range
from 1-100 to allow for ample space to insert policies between one and other.
Ranges are allowed when configuring the Level and the OpCode. Ranges provide the operator
a simplified method for configuring multiple combinations. When more than one Level or
OpCode is configured in this manner the configured rate limit is applied separately to each
combination of level and OpCode match criteria. For example, if the Levels are configured
with using a range of 5-7 and the OpCode is configured for 3,5 with a rate of 1. That restricts
all possible combinations on that single entry to a rate of 1 packet per second. In this example
six different match conditions are programmed behind the scene.
Once the policy is created it must be applied to a SAP/Binding within a service for these rates
to take affect. This means the rate is on a per SAP/Binding basis. Only a single policy may be
applied to a SAP/Binding. The “eth-cfm-monitoring” option must be configured in order for
the eth-cfm entries to be applied when the policy is applied to the SAP/Binding. If this option
Table 4: Ranges versus Levels and OpCodes
Level
OpCode
Rate
5
3
1
5
5
1
6
3
1
6
5
1
7
3
1
7
5
1
Содержание 7950 SR
Страница 10: ...Page 10 7950 SR OS System Management Guide List of Figures...
Страница 14: ...About This Guide Page 14 7950 SR OS System Management Guide...
Страница 16: ...Alcatel Lucent 7950 SR Router Configuration Process Page 16 7950 SR OS System Management Guide...
Страница 56: ...Configuration Notes Page 56 7950 SR OS System Management Guide...
Страница 88: ...Configuring Login Controls Page 88 7950 SR OS System Management Guide...
Страница 106: ...Security Command Reference Page 106 7950 SR OS System Management Guide...
Страница 206: ...Distributed CPU Protection Commands Page 206 7950 SR OS System Management Guide...
Страница 244: ...Debug Commands Page 244 7950 SR OS System Management Guide...
Страница 254: ...Configuration Notes Page 254 7950 SR OS System Management Guide...
Страница 276: ...SNMP Security Commands Page 276 7950 SR OS System Management Guide...
Страница 296: ...Show Commands Page 296 7950 SR OS System Management Guide...
Страница 322: ...Configuration Notes Page 322 7950 SR OS System Management Guide...
Страница 358: ...Log Management Tasks Page 358 7950 SR OS System Management Guide...
Страница 454: ...Facility Alarm List Page 454 7950 SR OS System Management Guide...
Страница 460: ...Standards and Protocols Page 460 Standards and Protocols...