To configure a 7210 and 1830 network policy
Purpose
A 7210 and 1830 network policy defines forwarding for network traffic on both ingress and egress.
For ingress traffic, the policy associates dot1p, DSCP, or LSP-EXP bits to forwarding classes and profile states. The associations are either configured directly in the network policy, or by using an assigned Dot1p, DSCP, or MPLS LSP-EXP classification policy. For packets with no dot1p, DSCP, or LSP-EXP values, a user-defined default FC and profile are assigned.
FCs are mapped to ingress meters or queues. You can configure unicast and multipoint ingress meters. One default unicast meter and one default multipoint meter are provided within the policy. The FC-to-meter mapping is user-configurable. The network policy defines rate, burst size, and algorithm mode for ingress meters.
Ingress queues (supported on the 7210 SAS-K) are configured directly within the policy. Eight queues are provided by default. You can configure the following for network ingress queues:
-
WRED slope parameters using an assigned slope policy; see To configure a 7210 and 1830 slope policy
Ingress queue-to-FC mapping is user-configurable.
For egress traffic, a network policy defines remarking behavior. Remarking is configured per FC, or a 7210 remarking policy is assigned to the network policy.
On egress, FCs are statically mapped to egress queues by default; the FC-to-queue mapping is not configurable. Rates and other parameters for egress queues are defined in a separate network queue policy; see To configure a 7210 and 1830 network queue policy .
There are two types of 7210 and 1830 network policies: port type and network interface type. Port-type network policies are assigned to network, hybrid, or L2 uplink ports; see To assign QoS policies to a 7210 SAS Ethernet port . Network interface-type policies are assigned to L3 network interfaces; see To create an L3 network interface on a routing instance and To configure L3 network interfaces . For network interface-type policies, you can select an MPLS LSP-EXP Profile. See To configure a 7210 MPLS LSP-EXP Mapping policy for information about creating an MPLS LSP-EXP Profile.
7210 and 1830 network policies are identified by both the Nw Mgr ID value and the Policy ID value. The Nw Mgr ID value is unique for all 7210 and 1830 network policies. The Policy ID value is unique for a policy type (port or network interface). It is possible to have two 7210 and 1830 network policies with the same Policy ID if one is a port-type policy and one is a network interface-type policy. However, each of these policies will have a different Nw Mgr ID.
The NFM-P provides two default 7210 and 1830 network policies. Ports use default network policy ID 1 and network interfaces use default network policy ID 2. You cannot modify or delete a default policy. A default network policy is assigned to a port or network interface unless a user-configured policy is explicitly assigned. For the 7210 SAS-K12 and 7210 SAS-K30 ETR, a default port-type policy for network ports is automatically created as Policy ID 2 when the device is discovered. An auto-assigned Nw Mgr ID value distinguishes it from the network interface default policy.
The 7210 and 1830 network policy is supported on all 7210 SAS chassis types. Support for specific parameters and features depends on the chassis type. Local definitions of the policy do not necessarily support all configurations in the global policy.
Steps
1 |
Choose Policies→QoS→SROS QoS→Network→7210 and 1830 Network from the NFM-P main menu. The 7210 and 1830 Network Policies form opens. |
2 |
Perform one of the following:
|
3 |
Configure the required parameters on the General tab. The Remarking Type parameter is configurable only when the Type parameter is set to Port and the Remarking parameter is set to true. |
4 |
In the Classification Type panel, select a Dot1p, DSCP, or MPLS LSP-EXP classification policy, as required. See To configure a 7210/7250 Dot1p classification policy, To configure a 7210/7250 DSCP classification policy or To configure a 7210 MPLS LSP-EXP Mapping policy. You can select Dot1p, DSCP, or MPLS LSP-EXP classification policies only for a port-type network policy. |
5 |
Select an MPLS LSP-EXP Profile in the Ingress panel, if required. You can select an MPLS LSP-EXP Profile only for a network interface-type policy. Note: The MPLS LSP-EXP Profile defines how LSP-EXP bits are mapped to profile states on ingress. The MPLS LSP-EXP Profile is also referred to as an MPLS LSP-EXP Map policy. See To configure a 7210 MPLS LSP-EXP Mapping policy for more information about MPLS LSP-EXP Map policies. |
6 |
Select a remarking policy in the Egress panel, if required. See To configure a 7210 remarking policy for information about creating a remarking policy. |
7 |
Associate egress forwarding classes to dot1p, DE, DSCP, or LSP-EXP values.
|
8 |
If you are configuring a network interface-type policy, associate ingress LSP EXP values with forwarding classes and profiles. Otherwise, go to Step 9 .
|
9 |
If you are configuring a port-type policy, perform one of the following:
|
10 |
Configure ingress queues.
|
11 |
Configure ingress meters.
|
12 |
Map forwarding classes to queues or meters.
|
13 |
Click OK to save the policy and close the form, or click Apply to save the policy. See To release and distribute a policy to distribute the policy to NEs. End of steps |