• Author : Emil Maric


FEC Implicit References

Description In order for forwarding equivalence classes (FECs) to get programmed in the ASIC, they must have some form of a reference. This can be in the form of a route pointing to the FEC, another FEC pointing to the FEC, as well as several other possibilities. FECs with no references will not get programmed in the ASIC. Enabling this feature will add an implicit reference to all FECs on the switch. This allows every FEC existing in software to get programmed in the ASIC. Users that have their own controller agents writing FECs directly to software FEC sources (ex....
Continue reading →

Resilient ECMP deduping

Description Routes covered by a resilient equal-cost multi-path (RECMP) prefix are types of routes that make use of hardware tables dedicated for equal-cost multi-path (ECMP) routing. Resilient ECMP deduping is a new feature wherein the switch will reactively attempt to reduce the number of ECMP hardware table entries allocated by forcing routes that share the same set of next hops but point to different hardware table entries to point to the same hardware table entry when hardware resource utilization is high. Forcing RECMP routes to change the hardware table entry that they point to may potentially cause a traffic flow...
Continue reading →

SR-TE Aggregate Policy Counters

Description The existing show traffic-engineering segment-routing policy … command supports showing the counters per segment-list of a policy, where the counters display the number of packets and bytes traversing the tunnel associated with the segment-list. However, the functionality of these counters is limited under the following scenarios: When the segment-list becomes unresolvable When the segment-list is deleted from the candidate path When the candidate path is removed The SR-TE aggregate policy counters aim to resolve the limitations of the segment-list counters in the above listed scenarios. These counters aggregate the segment-list counters per policy, and will preserve the history of...
Continue reading →

Discontiguous IPv4 Mask Algomatch 7160 Series ACL Support

Description On Algomatch platforms, expansions and encoding transformations on IP prefixes are performed before attempting to fit the transformed set of rules into the ACL hash tables. However, previously Algomatch would only accept IP prefixes (both IPv4 and IPv6 variants) with masks that could be represented in integer format (ex. /16, /24,etc. ) and skip any rules that contained invalid IP prefixes with a trace message stating that the rule was unsupported. This limit meant that IP rules that contained discontiguous masks could not be accepted. Discontiguous masks are IP masks that cannot be represented in integer format, such as...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: