|| invalid abstract graph config
|| The abstract graph configuration is invalid.
|| mandatory param not found
|| A mandatory configuration parameter could not be resolved.
Check the package for the mandatory parameter and make sure that AbsGraph has
|| invalid param cardinality
|| A configuration parameter does not meet cardinality
requirements. Check if you specified multiple instances of a parameter without
|| epp download failure
|| Graph policies failed to download to the switch.
|| duplicate param name
|| Multiple identical copies of a parameter were found with the
|| id allocation failure
|| A unique network resource (either VLAN or VXLAN) could not be
|| No cluster found
||A cluster could not be found.
|| invalid cluster context cardinality
|| The cluster does not support the required tenancy(multi-tenant
or single tenant).
|| invalid function type
|| The function type is not supported for the selected device.
Check if the AbsNode functype and resolved
LDevVip function type match.
|| invalid abstract graph config param
|| The abstract graph configuration parameter is invalid.
|| No parameter definition found
|| A required parameter definition could not be found.
|| no abs graph found
|| The abstract graph configuration is missing for the graph
|| invalid param config
||The parameter configuration is invalid.
|| invalid parameter scope
|| The parameter scope is invalid. Check the
vnsRsScopeToTerm parameter in the AbsGraph to see if
parameter is correct.
|| Invalid cluster
|| The cluster configuration is invalid. Check the status of the
LDevVip and correct the fault.
|| no tenant found
|| The tenant could not be found for the graph.
|| internal error
|| An internal error occurred during graph processing.
|| resource allocation failure
|| A required resource could not be allocated during graph
|| no abstract function found
|| The abstract function definition is missing.
|| param validation failure
|| The configuration parameter value is invalid.
|| No connector found
|| A required connector could not be found.
|| no mgmt ip found for cdev
|| The management IP address could not be found for concrete
device. Check if
vnsCMgmt is present for the resolved
|| invalid graphinst config
|| The graph instance is invalid.
|| no interface found
|| An interface could not be found.
|| no bd found
|| A bridge domain could not be found.
|| Terminal node is missing a terminal
|| Terminal node is missing a terminal. Check the terminal node
|| no vlan/vxlan namespace found
|| The namespace that is needed to allocate the VLAN or VXLAN is
missing. Verify that the resolved
vnsLDevVip has the
phyDomp parameter or the
vmmDomp parameter configured that has a relation to
|| No function found in device package
|| A required function could not be found in the device package.
Verify that all
AbsNode function types are present in the package.
|| no cluster interface found
|| A required cluster interface could not be found. Verify that
vnsLIf parameter in
vnsLDevVip is configured correctly.
|| Abstract Function Profile config is invalid
|| The abstract function profile configuration is invalid. This
fault may be due to an invalid configuration parameter that is specified in the
|| No device found
|| The concrete device could not be found in the cluster. Verify
that a valid
vnsCDev is present under the resolved
|| Illegal folder in configuration
|| No corresponding folder was found in the device package.
|| Device context is not legal for this folder
|| The device package does not allow specifying a device context
for this folder.
|| Folder must have one value for each associated CDev
|| The folder is concrete device specific. The folder must have at
least one value for each concrete device.
|| No interface defined
|| A concrete device must have at least one interface defined.
|| Missing path for interface
|| For a physical service appliance, we must know to which leaf
ports the interface is connected. Verify that the
vnsCifPathAtt parameter is present for all
vnsCIf under the resolved
|| Device interfaces does not match cluster
|| The device interfaces should match the interfaces configured
for their cluster. Verify that the
vnsCIf parameter and the
vnsLIf parameter are present under the resolved
|| No Mgmt ip found for LDevVip
|| The management IP address could not be found for
|| LIf has an invalid MifLbl
MIfLbl contained by LIf is not present in the device
|| LIf has an invalid CIf
|| The CIf contained by LIf is not present. Check the concrete
device and CIf settings.
|| Abstract graph missing function node
|| An abstract graph must have at least one function node.
|| Abstract graph config has a loop
|| The abstract graph configuration is invalid. The configuration
has a loop.
|| Both the legs of go through node has routing enabled
|| Both the legs of the go through node have routing enabled.
|| Abstract graph has invalid number of terminal nodes
|| An abstract graph must have at least two terminal nodes.
|| No device context found for LDev
|| The device context for the device could not be found. Verify
vnsLDevCtx has values that match the contract, graph
|| ARP flood is enabled on the management end point group
|| ARP flood must be disabled for the management endpoint group.
|| FolderInst has key, that is not found in MFolder
FolderInst's key and value should honor
|| ParamInst has key and/or value, that are not found in MParam
ParamInst's key and value should honor
|| FolderInst points to an invalid MFolder
FolderInst must point to a valid
|| ParamInst points to an invalid MParam
ParamInst must point to a valid
|| DevFolder has key, that is not found in MFolder
DevFolders key and value should honor
|| DevParam has key and/or value, that are not found in MParam
DevParam's key and value should honor
|| Virtual Object Info is missing in CDev
|| Virtual object information must be provided if
LDevVip is of type Virtual.
||Relationship to metaconnector is invalid
||Correct the metaconnector DN and ensure it binds to the correct