Licensing Requirements and Limitations for Traffic Statistics Collection

Involved Network Elements

Other network elements are not required.

Licensing Requirements

The traffic statistics collection function is a basic feature of a switch and is not under license control.

Version Requirements

For details about the mapping between software versions and switch models, see the Hardware Query Tool.

Software version evolution: V100R001C00 -> V100R002C00 -> V100R003C00 -> V100R003C10 -> V100R005C00 -> V100R005C10 -> V100R006C00 -> V200R001C00 -> V200R002C50 -> V200R003C00 -> V200R005C00 -> V200R005C10 -> V200R019C00 -> V200R019C10

Feature Limitations

• The following constraints apply to the CE12800 equipped with EA, EC, EC1, ED, EF, EG, or BA series cards, if a traffic policy containing traffic statistics collection is applied to the outbound direction:

  • The traffic policy can be applied only in the VLAN view, physical interface view, Eth-Trunk interface view, and Layer 3 sub-interface view.
  • If the traffic policy is applied in the interface view: In V100R006C00 and earlier versions, the traffic policy can be configured only on a physical interface or Layer 3 sub-interface. In V200R001C00 and later versions, the traffic policy can be configured only on a physical interface, Eth-Trunk interface, or Layer 3 sub-interface.
  • If the traffic policy is applied in the VLAN view: The interface that joins a VLAN must be located on the CE-L48GT or CE-L48GS card, and the VS to which interfaces on the CE-L48GT or CE-L48GS card belong must work in group mode. In this situation, the switch only collects statistics on packets in the VLAN on the CE-L48GT or CE-L48GS card.

• By default, the device does not calculate the inter-frame gap and preamble of Ethernet frames during traffic statistics collection. After the qos statistics ifg enable command is used, the device calculates the inter-frame gap and preamble of Ethernet frames during traffic statistics collection in V100R005C00 and later versions.

• 48GE cards do not support traffic statistics collection for double-tagged packets that match Layer 3/4 fields in the outbound direction.

• On cards except CE-L48GT and CE-L48GS series cards, when the traffic policy defining traffic statistics collection is applied in the outbound direction, the following situations may occur:

  • If all physical interfaces to which the traffic policy is applied belong to the same forwarding chip, the maximum bandwidth is 100 Gbit/s.

    On the CE-L24LQ-EA card, interfaces 0 to 5 belong to chip 0, interfaces 6 to 11 belong to chip 1, interfaces 12 to 17 belong to chip 2, and interfaces 18 to 23 belong to chip 3. When the traffic policy defining traffic statistics collection is applied to four interfaces (for example, interfaces 0, 6, 12, and 18) in different chips in the outbound direction, the maximum bandwidth is 160 Gbit/s (4x40 Gbit/s). When the traffic policy defining traffic statistics collection is applied to four interfaces (for example, interfaces 0 to 3) in the same chip in the outbound direction, the maximum bandwidth is 100 Gbit/s.

  • The card forwarding performance is reduced. The reduced performance depends on the number of interfaces to which the traffic policy is applied. More interfaces to which the traffic policy is applied indicate more reduced performance.

    Assuming that the number of 10GE ports on a card is M and a traffic policy containing CAR or traffic statistics collection is applied to N interfaces in the outbound direction, the performance is reduced to (10 Gbit/s x M) x M/(M + N). For example, when a traffic policy containing CAR is applied to an interface on the 24*10GE card, the forwarding performance is reduced from 240 Gbit/s to 230.4 Gbit/s that is calculated according to the following formula: (10 Gbit/s x 24) x 24/(24 + 1). When a traffic policy containing CAR is applied to 24 interfaces, the forwarding performance is reduced to 100 Gbit/s.

• If the traffic policy contains a lot of rules and traffic statistics collection have been cleared, wait for a period before querying traffic statistics. Otherwise, only some or no statistics are displayed.
• For the CE12800: Outbound traffic statistics collection cannot be used with outbound interface-based rate limiting, queue-based traffic shaping, ETS, or PFC.
• For the CE12800: If the traffic statistics collection function is configured in the outbound direction and traffic exceeds the bandwidth of the outbound interface, the actual volume of forwarded traffic is lower than the interface bandwidth. In this case, ensure that the traffic volume is within the interface bandwidth.
• On all switch models running versions earlier than V100R006C00, the following traffic statistics collection functions are listed in descending order of priority: Traffic statistics collection in a VLAN, MQC-based traffic statistics collection, and traffic statistics collection on a VLANIF interface. When the three functions are all configured, only the traffic statistics collection function with a higher priority takes effect. The following table lists the traffic statistics collection functions in descending order of priority in V100R006C00 and later versions.

  Table 10-3 Priorities of traffic statistics collection functions

  Card	Priorities of Traffic Statistics Collection Functions
  CE12800E equipped with the ED-E, EG-E, or EGA-E series cards	Inbound and outbound directions: Traffic statistics collection in a VLAN > Traffic statistics collection on a VLANIF interface Traffic statistics collection based on 5-tuple information of IP packets and MQC-based traffic statistics collection are compatible with the two statistics collection functions.
  CE12800 series switches	In the inbound direction of the EA, EC, EC1, ED, EF, EG, and BA series cards: Traffic statistics collection based on 5-tuple information of IP packets > Traffic statistics collection in a VLAN > MQC-based traffic statistics collection > Traffic statistics collection on a VLANIF interface In the outbound direction of the EA, EC, EC1, ED, EF, EG, and BA series cards: Traffic statistics collection based on 5-tuple information of IP packets > MQC-based traffic statistics collection > Traffic statistics collection on a VLANIF interface On the FD, FDA, FD1, FG, FG1, and SD series cards: Traffic statistics collection based on 5-tuple information of IP packets > MQC-based traffic statistics collection > Traffic statistics collection on a VLANIF interface
  CE12800E equipped with FD-X series cards	Inbound direction: The four collection methods are compatible with each other. Outbound direction: Traffic statistics collection based on 5-tuple information of IP packets > Traffic statistics collection on a VLANIF interface; Traffic statistics collection based on 5-tuple information of IP packets > MQC-based traffic statistics collection Traffic statistics collection in a VLAN can be used together with traffic statistics collection based on 5-tuple information of IP packets, based on MQC, and on a VLANIF interface.

• For the CE12800: The traffic statistics collection functions are listed in descending order of priority as follows: traffic statistics collection based on the 5-tuple > traffic statistics collection in a BD > MQC-based traffic statistics collection > traffic statistics collection in a VXLAN tunnel. If two or more of the traffic statistics collection functions are configured, only the traffic statistics collection function with the highest priority takes effect.
• For a model equipped with SD, FD, FD1, FDA, FG, or FG1 series cards: If the MQC-based traffic statistics collection function is configured on an Eth-Trunk in the outbound direction, multicast packets of member interfaces in Up state may be counted repeatedly. When the MQC-based traffic statistics collection function is configured in the system in the outbound direction and the outbound interface is an Eth-Trunk, multicast packets of member interfaces in Up state are also counted repeatedly.
• When a traffic policy containing many rules and the traffic statistics collection action is configured and the statistics are being queried based on instances or traffic classifiers, command line execution is interrupted and MIB-based query expires. By default, the timeout interval of MIB-based query is 5s and only statistics on packets matching the traffic policy within 1024 rules can be queried. When a traffic policy defines more than 1024 rules, the timeout interval of MIB-based query needs to be changed based on the data volume, and statistics are collected from the cached data.
• On a CE12800 with the following configurations, packets discarded on interfaces or denied by ACLs are mirrored but not included in traffic statistics:
  • Port mirroring or MQC-based traffic mirroring
  • MQC-based traffic statistics collection