Segment Routing Traffic Engineering Policy (SR-TE)

multi-agent routing model TOI

eos.arista.com/eos-4-23-0f/segment-routing-traffic-engineering-policy-sr-te-multi-agent-routing-model-toi

By Manoharan Sundaramoorthy

Contents [hide]

Description
Platform Compatibility
Configuration
Show Commands
Differences in show command output when compared to single agent
Syslog Messages
Troubleshooting
Collecting Information for Problem Reporting (For BGP and SrTePolicy agent)
Limitations
BGP Limitations
Platform Independent Limitations
Platform Specific Limitations
Resources

Description
Segment Routing Traffic Engineering Policy (SR-TE) aka SR Policy makes use of Segment
Routing (SR) to allow a headend to steer traffic along any path without maintaining per flow
state in every node. A headend steers traffic into an “SR Policy”.

EOS 4.21.0F added support for SR Policy for the MPLS dataplane (SR-MPLS) for Type-1 SR
Policy segments in single agent routing model. EOS 4.22.1F adds support for SR-TE in
multi-agent routing model.

For a detailed description of the functional behavior please refer to the “Description” section
of EOS 4.21.0F TOI for SR-TE in single agent routing model.

Platform Compatibility
Same as single agent routing model, ie., SR-TE is supported on Arista 7500, 7280 family of
switches

Configuration

1/4
The configuration commands are the same as those described in EOS 4.21.0F TOI for SR-
TE in single agent routing model.

Show Commands
Please refer to the SR-TE in single agent routing model TOI for a list of show commands.

Differences in show command output when compared to single agent

The following show commands are NOT supported in multi-agent model.
show <ip | ipv6> bgp neighbors update errors
show <ip | ipv6> bgp neighbors <address> update errors

In the output of “ show <ip | ipv6> bgp neighbors [neigh_addr] ” the line “ Last
treat-as-withdraw attribute error ”, in single agent routing model shows
“ Tunnel Encapsulation ” if there’s an error in the constituents of the Tunnel
Encapsulation path attribute leading to a RFC7606 treat-as-withdraw behavior. In multi-
agent model, there are more granular reasons shown. The reasons are:

Tunnel Encapsulation attribute or SR-TE TLV missing/malformed

SR-TE NLRIs missing mandatory communities
Tunnel Encapsulation attribute with multiple SR-TE TLVs
Tunnel Encapsulation attribute with multiple SR-TE SL weight
Tunnel Encapsulation attribute with SR-TE SL weight sub TLV of
invalid length
Tunnel Encapsulation attribute with SR-TE type 1 segment of invalid
length
Tunnel Encapsulation attribute with SR-TE SL sub TLV of invalid
length
Tunnel Encapsulation attribute with SR-TE SL sub TLV length of zero
Tunnel Encapsulation attribute with multiple SR-TE Binding SIDs
Tunnel Encapsulation attribute with Binding SID sub TLV of invalid
length
Tunnel Encapsulation attribute with multiple SR-TE preference
Tunnel Encapsulation attribute with SR-TE preference sub TLV of
invalid length
Tunnel Encapsulation attribute with multiple SR-TE ENLP sub TLV
Tunnel Encapsulation attribute with SR-TE ENLP sub TLV of invalid
length

The ENLP related reasons are available from EOS 4.22.2F onwards.

Syslog Messages

2/4
Please refer to the SR-TE in single agent routing model TOI for a list of syslogs

Troubleshooting
Please refer to the SR-TE in single agent routing model TOI except the sub section titled
”Collecting Information for Problem Reporting” which is revised here.

Collecting Information for Problem Reporting (For BGP and SrTePolicy

agent)
The major log files required for troubleshooting:

/var/log/agents/Bgp* and /var/log/agents/SrTePolicy* contain trace

messages that are useful for troubleshooting.
/var/log/qt/Bgp*.qt, /var/log/qt/IpRib*.qt and
/var/log/qt/SrTePolicy*.qt files contain the QuickTrace files that are useful for
troubleshooting.

Disclaimer: In some cases, running the following commands can seriously impact the
performance of the switch. Please use it cautiously and seek advice from an Arista
representative before running this in any production environments.

‘ show tech-support bgp ’ – to get a detailed state of the Bgp agent in text form.
‘ show tech-support extended srtepolicy ’ – to get a detailed state of the SR-TE
Policy agent in text form.

Limitations

BGP Limitations
Readvertisement of received SR-TE NLRIs is not supported for SR-TE SAFI.
Graceful restart for SR-TE SAFI is not supported. This means that when the Bgp agent
restarts all SR Policies learnt via BGP are deleted.
Graceful restart helper (receiving speaker) functionality for SR-TE SAFI is not
supported.
Originating the extended color community (for unicast SAFI) is not supported, however
note that the unicast prefixes received with extended color community are transitively
readvertised as per regular BGP behavior.
UCMP of IPv4/IPv6 prefixes using LinkBandwidth (LBW) extended community that
resolve over SR-TE policies is not supported as explained here.

Platform Independent Limitations

3/4
 Resolution of BGP IPv4 unicast prefix with IPv6 nexthop via SR Policy is not
supported.
A maximum of 16 SID-Lists per candidate path are installed in hardware. If more than
16 SID-Lists are present in a candidate path, a non deterministic subset is selected for
installation and a syslog is emitted.
SID-List top label resolution is supported only over
Static MPLS routes.
IS-IS SR routes. For IS-IS SR routes, SID-List top label resolution is not
supported for IS-IS SR routes protected using TI-LFA, ie., IS-IS SR routes that
have a backup path.

Platform Specific Limitations

The 7500E/7280E platforms support pushing at most 5 labels, and 7500R/7280R

support pushing at most 6 labels.
The 7500E/7280E platforms support 1K ECMP and 31K non-ECMP FECs, and the
7500R/7280R platforms support 4K ECMP and 124K non-ECMP FECs.
The 7500E/7280E platforms support 16K tunnel counters, and the 7500R/7280R
platforms support 8K tunnel counters.
The 7500E/7280E platforms share 2 counter engine resources between various
features, including MPLS LFIB counters, MPLS tunnel counters, and Nexthop group
counters. Use “ show hardware counter feature ” to see what is currently in use.
On the 7500E/7280E/7500R/7280R platforms, “ platform fap mpls-over-gre ”
must be configured (in addition to decap group configuration) to allow MPLS-over-GRE
packets to be steered using a BSID after GRE decapsulation. This option cannot be
combined with VxLAN.

Resources
1. Segment Routing Policy Architecture
2. Advertising Segment Routing Policies in BGP
3. Segment Routing Traffic Engineering Policy (SR-TE) TOI for single agent routing model

4/4