Preview Tool

Cisco Bug: CSCvt16915 - CSR Gig3 Interface not created even after ENI is attached to VM instance in AWS

Last Modified

Sep 10, 2020

Products (9)

  • Cisco Cloud Services Router 1000V Series
  • Cisco 4221 Integrated Services Router
  • Cisco 4321 Integrated Services Router
  • Cisco 4431 Integrated Services Router
  • Cisco 4331 Integrated Services Router
  • Cisco Cloud Services Router 1000V
  • Cisco 4351 Integrated Services Router
  • Cisco 4461 Integrated Services Router
  • Cisco 4451-X Integrated Services Router

Known Affected Releases

16.12.1 17.1.1

Description (partial)

An intermittent issue has been observed with CSR1k in AWS cloud that when a set of interfaces are attached to CSR using AWS APIs, one of the interfaces may not actually get attached to the CSR. While on AWS side, the API succeeds and interface is shown in attached state, on CSR IOS console, the interface is not detected and "show ip int br" does not show the interface.

This would break customer automations and affect traffic flow. Customer would need to manually login to the machine and troubleshoot which interface was not attached, try to detach/re-attach from AWS console and configure the interface.

Issue has been observed in AWS cloud when interfaces are attached using automation scripts.
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.