Regular ESM QoS is supported in both the access and bonding contexts; however, there is no direct feedback mechanism between the two contexts. Therefore, if an access connection drops a packet, it is not reflected in bonding statistics, nor does it cause backpressure on the bonding QoS algorithm.
When traffic passes over the FPE from the bonding context to the access context or from the access context to the bonding context, the system keeps the traffic classification and the in- and out-profile markings. Although this occurs automatically, bonding subscriber policies for ingress and egress should consider the following recommendations.
Enable de-mark for access egress and map each FC to the dot1p as defined in Table: FC to dot1p mapping, therefore ensuring that the same classification is used in the access connection context.
Perform classification for access ingress based on dot1p as defined in Table: FC to dot1p mapping and enable in-profile and de-1-out-profile for each FC, therefore ensuring the same classification is used as for the access connection context. A different classification scheme can be used if required, for example, based on DSCP or IP criteria.
| FC | dot1p |
|---|---|
be |
0 |
l2 |
1 |
af |
2 |
l1 |
3 |
h2 |
4 |
ef |
5 |
h1 |
6 |
nc |
7 |
To support load-balancing in the bonding context, the configured stat-mode of any egress policer in the bonding context is ignored. Instead, an internal stat-mode is used, which uses two counters (one per access connection), which is reflected in the in- and out-of-profile statistics.