Common VCO KBs checklist
search cancel

Common VCO KBs checklist

book

Article ID: 385341

calendar_today

Updated On:

Products

VMware VeloCloud SD-WAN VMware SD-WAN by VeloCloud

Issue/Introduction

This list covers VCO issues with guiding L1/L2 cases quickly. It is based on VMware VeloCloud SD-WAN documents and explains some errors on VCO.

 

Resolution

  1. lastContact discrepency in some API responses
  2. Customer clone remains disabled for some customers from VCO version 5.2.3
  3. Edge status is showing online on VCO even the edge is physically disconnected
  4. VCO DR setup failing due to "Failure Background Import" error
  5. API execution is failing while trying to delete Clickhouse Backup
  6. VCO unable to send email notifications due to error "Client does not have permissions to send as this sender
  7. VCO Firewall logs screen shows "Failed to load data"
  8. Authentication tab not loading on VCO New UI due to error "Failed To Load Data"
  9. Unable to view content in Non SD-WAN Destinations via Gateway tab under Monitor ---> Network Services
  10. VCO language translation issues due to i18n-service not running or missing from docker list
  11. VCO SSO login not working due to error "invalid_client...: The provided client keys...are expired. Visit the Azure portal to create new keys for your app.."
  12. VCO Report generation fails due to Internal Error
  13. VCO UI login via radius authentication fails due to error "Cannot read property 'username' of null "
  14. VCO unable to display graphs like Links, Applications, QOE under Monitor Edge screen
  15. VCO reporting screen doesn't load properly due to error "Unknown error occurred"
  16. Radius user throwing "invalid username or password" while logging into VCO UI
  17. Error "A valid PSK is required" is seen while saving any config change in edge from VCO UI
  18. Remote Diagnostics page not opening for a edge
  19. Unable to save changes in Configure Edge ---> Overview page due to error "Cannot save changes. There is one or more errors within your configuration."
  20. VMware VeloCloud SD-WAN Orchestrator upgrade steps from any version starting from 4.x to 5.x.
  21. VCO Disk Expansion Issue - 'resize2fs: Permission denied to resize filesystem'
  22. VCO upgrade steps to upgrade VCO from from any version starting from 5.x to 6.x.
  23. Asymmetric routing for the unrecognized application may cause the discrepancy between the Applications tab and the Links tab
  24. A workaround for "Invalid key gateway xxx at index 0"
  25. VMware SD-WAN Orchestrator monitor Edges keep in "No data available as per selected filter criteria" or "Live Mode" could not turn on in Links Tab.
  26. VMware SD-WAN Edge Heartbeat connect VMware SD-WAN Orchestrator interval
  27. Failure Background Import" error is seen while doing VCO DR replication
  28. VMware SDWAN Edge Activation (RMA Reactivation) email is not received by the recipient
  29. VCO services not getting auto-restarted after reboot
  30.  VCO unable to retrieve enterprise mapping from GSM
  31. WAN Links shown as down in VCO
  32. When logging in VCO as a user with customer privileges, the Edge's diagnostics can not be downloaded.
  33. Edge status is showing online on VCO even the edge is physically disconnected
  34. Standby Edge interface displayed speed as 0 mbps and duplex half on VCO Remote diagnostic page
  35. Static route added via API call on the VCO without netmask will not be added to the edge routing table
  36. New UI VCO cannot display and configure the some applications in the per-profile settings
  37. Link down events on the active edge (HA pair) will not be displayed in VCO events in edge versions less than 5.2.x
  38. SD-WAN Edge 510 showing events in the VCO for MGD_DEVICE_CONFIG_WARNING Unknown interface CELL1 in routedInterfaces - ignoring
  39. MGD_DEVICE_CONFIG_ERROR in VCO events
  40. VCO path monitoring tab reports path status as DEAD; however, the path is UP as per remote diagnostics
  41. VeloCloud - Incorrect path status seen in VCO UI paths page
  42. How to distinguish between a physical port down and a link down on the VCO event logs
  43. SDWAN-Unable to access Orchestrator (VCO) due to client secret keys being expired
  44.  Missing QoE data and slow access to the VCO through the GUI
  45. Edge is showing status “unable to resolve” under the ‘Sources’ tab in VCO
  46. links and recentLinks outputs in API response of get/getEdge
  47. Rebalancing GWs (Gateways) from VCO
  48. NetworkView Tab on VCO showing Link status of down and up in delay
Powered by Wolken Software