Most VRC operations can occur simultaneously by different users within the VRC server. However, there are certain operations that cannot run concurrently.
VRC concurrent operations constraints include:
A single user can execute only one operation at a time.
There can only be one design session open at a time for a given scope.
Design sessions that originate with the Discovery operation are opened at the Administrative Domain (AD) level.
No two operations of the same type can be executed simultaneously (exceptions: Design Export and Save Design)
The following VRC operations cannot occur simultaneously:
Operation being executed |
Cannot execute simultaneously with |
Check network element | |
Distribution |
Persist element configuration |
Distribution within the same scope | |
Import Topology | |
Discovery |
Element activation or reactivation |
Discovery |
Design Export |
Discovery |
Commit |
Discovery |
Save Design |
Design Preview |
View generated CLI (both baseline and design views) |
Element activation or reactivation | |
Persist element configuration | |
View generated CLI (baseline view) |
Export baseline dial plan |
Because the following operations require serialized access to staging tables, they are semi-concurrent with the Commit operation:
Design Preview
View the generated CLI (both baseline and design views)
If you receive an error message that an operation cannot be executed because it cannot be initialized, wait a few moments and try again. VRC might be waiting for an operation to complete, or that operation must be in the initialized state before you can execute another operation.
If you are executing an operation for a scope that overlaps with another user, your operation request fails. If there is no scope overlap, your operation request is queued and executed when server resources become available.
Note: If you are using a Cisco IE2100 device for automating the deployment and management of network devices, your concurrent operation issues might be different.