Cisco Crosswork Network Controller 7.2.x Traffic Engineering and Optimization

PDF

Cisco Crosswork Network Controller 7.2.x Traffic Engineering and Optimization

Locator counter collection coverage

Want to summarize with AI?

Log in

This section covers the effects of partial locator counter collection coverage.


For the most accurate and complete SRv6 demand matrix, Locator counter (LOC.INT.E) collection should include every device in the IGP domain. This is the recommended deployment model for DDM. With partial coverage (for example, when some devices support Locator accounting and others do not), the demand matrix may be impacted in several ways, including:

  • false demands

  • missing demands

  • double counting of traffic

In general, with partial LOC.INT.E coverage, false demands can arise at any node serving as a transit for traffic to a Locator (for example, when the node has non-zero LOC.INT.E counters for transiting traffic), if one or more neighboring nodes do not support LOC.INT.E counters and, as a result, the ingress counters from those neighbors are not considered.