Preview Tool

Cisco Bug: CSCup45387 - ASR9K L2VPN Hashing not checking IP e-type only checking layer 3 offset

Last Modified

Sep 10, 2019

Products (8)

  • Cisco ASR 9000 Series Aggregation Services Routers
  • Cisco ASR 9922 Router
  • Cisco IOS XR Software
  • Cisco ASR 9010 Router
  • Cisco ASR 9904 Router
  • Cisco ASR 9006 Router
  • Cisco ASR 9001 Router
  • Cisco ASR 9912 Router

Known Affected Releases


Description (partial)

When MPLS traffic is received on a L2 interface, L2VPN service will tunnel the whole L2+L3 frame and forward it to remote PE. If the path to remote PE is via ECMP or link bundle, load balance hashing should be done using the MAC address of the MPLS traffic or the PW VC label use to tunnel the mpls traffic. When the MPLS traffic's top label happens to start with 4 or 6, load balance hashing will not be done properly. This causes same flow traffic hashing to wrong ECMP path or wrong bundle member link. Same flow mpls traffic will be tunneled through the L2VPN service and arrives at destination Out Of Order.

MPLS traffic's top label starts with 4 or 6.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.