7705 SAR Interfaces
122
Interface Configuration Guide
3HE 11011 AAAC TQZZA Edition: 01
3.2.14.2 Per-Service Hashing
The 7705 SAR supports load balancing based on service ID, as shown in Table 15,
The 7705 SAR uses the service ID as the input to the hash function. Per-service and
per-flow hashing are mutually exclusive features.
For IPv4 and IPv6 routed traffic under ECMP operation, the service ID is used as the
hashing input for Layer 3 traffic going to a Layer 3 spoke SDP interface. Otherwise,
per-flow load balancing is used.
For Epipe and VPLS services under LAG operation, the per-service-hashing
command and the l4-load-balancing and teid-load-balancing commands are
mutually exclusive. Load balancing via per-service hashing is configured under the
config>service> epipe>load-balancing and config>service>vpls>
load-balancing contexts.
Note:
• Prior to Release 8.0.R4 of the 7705 SAR, load balancing for an Epipe service was
implicitly defaulted to be enabled (that is, hashing was always on the service ID).
Release 8.0.R4 adds the per-service-hashing command, which is disabled by
default. The per-service-hashing command must be explicitly enabled if
pre-Release 8.0.R4 behavior is needed.
• Starting with Release 8.0.R4, unless per-service-hashing is enabled, a 4-byte hash
value will be appended to internal overhead for VPLS multicast traffic at ingress. The
egress internal hash value is discarded at egress before scheduling. Therefore,
shaping rates at access and network ingress and for fabric policies may need to be
adjusted accordingly. In addition, the 4-byte internal hash value may be included in any
affected statistics counters.
To Next Page
Loading...
