Cisco Cisco Elastic Services Controller 1.1 Release Notes

ESC 1.1 provides support to add or delete a vm_group, add or delete an ephemeral network in a 
vm_group, and add or delete an interface in a vm_group during deployment. 

For ESC Datamodel updates

ESC does not support the properties of an existing vm_group to be updated.

ESC does not support the image, the flavor, kpi and the rules section of a vm_group to be 
updated.

ESC does not support blank names for resource names (that is, vm_group, network, subnet or 
Interface)

In ESC 1.1, the ephemeral networks or subnets can only be added or deleted. ESC does not 
support updating the properties of an existing network or subnet.

For ESC Interfaces

In ESC 1.1, the interface can only be added or deleted. ESC does not support updating the 
properties of an existing interface.

ESC does not support adding or deleting interfaces through the ESC portal.

ESC supports adding or deleting interfaces from a vm_group only through NETCONF APIs. \

ESC does not support Day-0 configuration of interfaces added during service update.

In case of recovery, for Day-0 configuration, all the interfaces with Network Interface Card IDs 
will be configured. 

Common Limitations for ESC HA

The HA failover will take around two minutes and the ESC service will not be available during 
the switchover time.

When the switchover is triggered during inflight transactions, all the incomplete inflight 
transactions will be dropped. The requests should be re-sent by NB client if it does not receive 
any response from ESC.

For complete list of ESC HA limitations, see 

.

For a complete list of known and resolved bugs and enhancements for this release, use the Cisco 

 tool.

 lists the key issues resolved in the Cisco Elastic Services Controller 1.1 release:

All VNFs lost after ASR reload (netwok outage). Services don't recover

After bulk deployment, while checking the logs, ESC Portal shows signs of latency