To configure FC mapping policies for ingress classification on the 7250 IXR

Purpose

7250 SROS FC mapping policies for ingress classification associate Dot1p, DSCP, and LSP EXP CoS values with forwarding classes and profiles. A separate policy is configured for each classification type (Dot1p, DSCP, or LSP-EXP). For each policy, a default FC and profile action is configurable for ingress traffic that does not have a CoS value.

The policies are assigned to a 7250 SROS Ingress Classification policy; see To configure a 7250 SROS Ingress Classification policy.

7250 SROS FC mapping policies are identified by the policy name; policy ID numbers are not used.

The NFM-P provides a default 7250 SROS Dot1p FC mapping policy. The default policy is not configurable, and cannot be deleted. The default policy is assigned to a 7250 SROS Ingress Classification policy when no user-configured policy is explicitly assigned.

7250 SROS FC mapping policies are not supported on all 7250 IXR chassis types and releases. For information about FC mapping policy support on the 7250 IXR, see the NE documentation.

For more information about QoS policy support on the 7250 IXR, see 7250 IXR QoS policies.

Steps
 
1 

If required, configure a 7250 SROS Dot1p FC Mapping policy. Perform the following:

  1. Choose Policies→QoS→SROS QoS→Ingress Classification→7250 SROS Dot1p FC Mapping from the NFM-P main menu. The 7250 SROS Dot1p FC Mapping form opens.

  2. Click Create or choose an existing policy and click Properties. The 7250 SROS Dot1p FC Mapping (Create|Edit) form opens.

  3. Configure the required parameters on the General tab.

    The default values are applied to ingress packets that do not have a CoS value.

  4. Click on the Dot1p tab.

  5. Click Create, or choose a mapping in the list. The Dot1p FC form opens.

  6. Configure the mapping of Dot1p values, forwarding classes, and profiles.

  7. Save your changes and close the form.

  8. Repeat substep 5 to substep 7 to configure additional mappings, as required.

  9. 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.

2 

If required, configure a 7250 SROS DSCP FC Mapping policy. Perform the following:

  1. Choose Policies→QoS→SROS QoS→Ingress Classification→7250 SROS DSCP FC Mapping from the NFM-P main menu. The 7250 SROS DSCP FC Mapping form opens.

  2. Click Create or choose an existing policy and click Properties. The 7250 SROS DSCP FC Mapping (Create|Edit) form opens.

  3. Configure the required parameters on the General tab.

    The default values are applied to ingress packets that do not have a CoS value.

  4. Click on the DSCP tab.

  5. Click Create, or choose a mapping in the list. The DSCP FC form opens.

  6. Configure the mapping of DSCP values, forwarding classes, and profiles.

  7. Save your changes and close the form.

  8. Repeat substep 5 to substep 7 to configure additional mappings, as required.

  9. 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.

3 

If required, configure a 7250 SROS LSP EXP FC Mapping policy. Perform the following:

  1. Choose Policies→QoS→SROS QoS→Ingress Classification→7250 SROS LSP EXP FC Mapping from the NFM-P main menu. The 7250 SROS LSP EXP FC Mapping form opens.

  2. Click Create or choose an existing policy and click Properties. The 7250 SROS LSP EXP FC Mapping (Create|Edit) form opens.

  3. Configure the required parameters on the General tab.

    The default values are applied to ingress packets that do not have a CoS value.

  4. Click on the LSP-EXP tab.

  5. Click Create, or choose a mapping in the list. The LSP-EXP FC form opens.

  6. Configure the mapping of LSP-EXP values, forwarding classes, and profiles.

  7. Save your changes and close the form.

  8. Repeat substep 5 to substep 7 to configure additional mappings, as required.

  9. 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