Cisco Bug: CSCvu55266 - vEdge running 20.1 does not come up as spoke in per-tunnel QoS due to bandwidth "not set"
Sep 04, 2020
- Cisco vEdge Router
Known Affected Releases
Symptom: vEdge device (running version 20.1) configured as a spoke role in per-tunnel QoS is never recognized as spoke (it does not show It listed under the show platform software sdwan qos target command) by the hub. Analyzing the OMP TLOCS sent by the spoke and received by the hub, the bandwidth attribute appears as not set. Conditions: vEdge device configured as spoke running 20.1.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases