The meter can operate in profile mode (also called color-aware mode) and non-profile mode (also called color-blind mode). On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, SAP ingress meters operate in either profile mode or non-profile mode.
To enable profile mode or color-aware mode, the user must assign the initial ingress profile explicitly using the in/out profile commands, which can be performed using the classification entries or DEI. If the use-dei command is enabled, the in/out profile value assigned by the user is ignored (DEI takes priority). Nokia recommends using the default value of ‟undefined” for the ingress profile when DEI is enabled. To enable color-blind metering, the user must not assign an initial ingress profile value (and the default undefined is used). With both color-aware and color-blind metering, the final color is assigned by the meter associated with the FC, based on the configured rates. The packet within CIR is assigned a final profile value of in-profile, and a packet that exceeds CIR and is within PIR is assigned a final profile value of out-profile. Anything above PIR is dropped.
The following functionality is implemented to support color-aware and color-blind metering:
ingress profile assignment as part of ingress classification (initial profile value)
on SAP-ingress, if the operator trusts the markings in the packet received from the customer device, the user has the following options:
DEI can be used to assign the initial profile value; use of DEI is enabled per FC.
Packet priority fields (for example, dot1p, IP DSCP, and so on) can be used for classification to an FC.
Packet priority fields (for example, dot1p, IP DSCP, and so on) can be used for classification to an FC and to assign the profile.
Profile is assigned using DEI overrides and initial profile value is assigned using explicit classification rules; however, Nokia recommends that you do not assign a profile explicitly when DEI use is enabled.
on SAP-ingress, if the packet header priority value is not trusted, the user has the following options:
Packet fields (for example, mac-criteria and ip-criteria) can be used for classification to an FC and to assign the profile.
If no classification entry matches or if the matched classification entry does not explicitly assign the profile, these packets are assigned a value of undefined.
ingress profile assignment as part of ingress policing or metering (lets call this the final profile value). The user has the following options:
If the initial profile value is assigned to a packet and if it is in-profile, it attempts to take tokens from CBS bucket. If available, its final profile value is set to in-profile. If not enough tokens are in the CBS bucket, check the MBS bucket. If sufficient tokens are available in the MBS bucket, the packet’s final profile value is set to out-profile. If there are not enough tokens available in the MBS bucket, it is dropped; this is the color-aware mode of operation for in-profile packets.
If the initial profile value is assigned to a packet and if it is out-profile, it attempts to take tokens from the MBS bucket. If available, its final profile value is set to out-profile. If there are not enough tokens in the MBS bucket, it is dropped; this is the color-aware mode of operation for out-profile packets.
If the initial profile value is assigned to a packet and if it is undefined, it attempts to take tokens from the CBS bucket. If available, its final profile value is set to in-profile. If not available, check for enough tokens in the MBS bucket and if available its final profile is set to out-profile. If there are not enough tokens in the MBS bucket, it is dropped; this is the color-blind mode of operation.