Cisco Bug: CSCvu81603 - ETSI: VNFM in-band created VIM connector may not be in-service before instantiate is sent
Oct 09, 2020
- Cisco Elastic Services Controller
Known Affected Releases
5.0 5.1 5.2
Symptom: The ESC ETSI VNFM will automatically create a new VIM connector when an instantiate request is received containing unknown vimConnectionInfo. The VNFM proceeds to create the VIM connector in advance of processing the instantiate, but is ultimately unable to confirm that VIM connection has been established before proceeding with the instantiate. As a result deployments can fail. Internally the VNFM does not receive the critical callback that determines VIM connector viability (VIM_CONNECTION_STATE 200). Instead the VNFM supports a delay (sleep) between VIM connector creation and instantiate deployment side effects on the VIM. This delay can be configured using etsi.properties configuration file "connector.vimuser.delay" property. Example: connector.vimuser.delay = 10 (value in seconds) Conditions: The incidence of instantiate failure is dependent on the connector.vimuser.delay value set and the underlying VIM connection setup responsiveness. However as the VNFM receives no hard confirmation of connection state, in-band connector setup is inherently flawed and unreliable. Higher incidence of failure will be observed on an ESC AA configuration as each in-band connector creation will trigger three connector setups (one per AA node).
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