tenant.logical_device.concrete_device

The individual service device is used to define a concrete l4-l7 service device.

ACI class	vnsCDev
RN	cDev-{name}
Cursor	ConcreteDeviceCursor
Parent	tenant.logical_device
Atomic	—

Attributes

Accepted as keyword arguments of .concrete_device(name) and of .set(**attrs) on this cursor. Enum parameters also accept the plain string.

parameter	wire	type	values	default	description
name (positional)	name	str	—	—	The name of the service device in the L4-L7 device cluster. The service device is uniquely identified by its name.
clone_count	cloneCount	int	—	0	—
context_label	devCtxLbl	str	—	—	—
management_address	host	str	—	—	The hostname or IP for export destination. Call Home sends email messages to either the IP address or hostname, and the associated port number.
is_clone_operation	isCloneOperation	bool	—	False	Tell whether Template or not
is_template	isTemplate	bool	—	False	Tell whether Template or not
vcenter_name	vcenterName	str	—	—	The virtual center name on which the device is hosted in the L4-L7 device cluster. The virtual center name uniquely identifies the center.
vm_name	vmName	str	—	—	The virtual center VM name on which the device is hosted in the L4-L7 device cluster. The virtual center VM name uniquely identifies the VM.

Children

maker	creates	position
.concrete_interface(name, **attrs)	vnsCIf	tenant.logical_device.concrete_device.concrete_interface
.device_param(name, key, **attrs)	vnsDevParam	tenant.logical_device.concrete_device.device_param

APIC diagnostics

States the APIC can flag on this class — it accepts the configuration and reports the inconsistency afterwards.

Config issues

code	meaning
arp-flood-enabled	ARP flood is enabled on the management end point group
cdev-missing-cif	No interface defined. It must have at least one interface defined
cdev-missing-mgmt-ip	no mgmt ip found for cdev
cdev-missing-path-for-interface	Missing path for interface.
cdev-missing-virtual-info	Virtual Object Info like Vcenter name and VM name is missing in CDev
cif-missing-virtual-info	Virtual Object like vnic name is missing in CIf
context-cardinality-violation-failure	invalid cluster context cardinality
devfolder-validation-failed	DevFolder has key, that is not found in MFolder
devparam-validation-failed	DevParam has key and/or value, that are not found in MParam
epp-download-failure	epp download failure
folderinst-validation-failed	FolderInst has key, that is not found in MFolder
function-type-mismatch-failure	invalid function type
gothrough-routing-enabled-both	Both the legs of go through node has routing enabled
gothru-same-bd	Both the legs of go through node are attached to same BD
graph-loop-detected	Service graph template configuration is invalid. It has a loop
id-allocation-failure	id allocation failure
inappropriate-devfolder	Illegal folder in configuration.
insufficient-devctx	Folder must have one value for each associated CDev.
internal-error	internal error occured during graph processing.`
invalid-absfunc-profile	Service graph template function profile config is invalid.
invalid-abstract-graph-config	invalid abstract graph config
invalid-abstract-graph-config-param	invalid abstract graph config param
invalid-config	Configuration of this device contains errors
invalid-conn-for-configparam	Config param is using an invalid graph connector.
invalid-connection	AbsGraph Connection is invalid.
invalid-devcfg-folder	DevCfg folder has invalid configuration parameters.
invalid-devctx	Device context is not valid for this folder.
invalid-filter-referred-by-rsconntoflt	AbsGraph connector is pointing to an invalid filter.
invalid-graphinst	Graphinst config is invalid
invalid-ldev	Invalid cluster
invalid-mfolder	FolderInst points to an invalid MFolder
invalid-namespace-allocation-mode	VlanInstP has invalid allocation mode: static. Allocation mode should be dynamic.
invalid-param-config	invalid param config
invalid-param-scope	invalid parameter scope
invalid-relation-target	Relation target parameter could not be resolved.
invalid-rsmconnatt	Invalid RsMConnAtt MO which points to connector
invalid-terminal-nodes	Service graph template must have two or more terminal nodes
ldevvip-missing-mgmt-ip	No Mgmt ip found for LDevVip
lif-has-invalid-interface-label	LIf has an invalid MifLbl
lif-invalid-CIf	LIf has an invalid CIf
missing-abs-function	no abstract function definition found
missing-abs-graph	no abs graph found
missing-bd	no bd found
missing-cdev	No device found in cluster.
missing-cif	Device interfaces does not match cluster.
missing-config-params	GraphInst does not have any configuration parameters. It should have at least one valid configuration parameter.
missing-function-in-device-package	No function found in device package
missing-function-node	Service graph template missing function node.
missing-interface	no interface found
missing-l3ctx	No L3 Context found for the graph connection
missing-l3instp	no L3InstP found
missing-ldev	No cluster found
missing-ldev-ctx	No device context found for LDev
missing-lif	no cluster interface found
missing-mandatory-param	mandatory param not found
missing-mdev	No device type found. LDevVip must be associated with an MDev.
missing-mparam	No parameter definition found
missing-namespace	no vlan/vxlan namespace found
missing-terminal	Terminal node is missing a terminal
param-cardinality-error	invalid param cardinality
param-validation-failed	param value is invalid
paraminst-validation-failed	ParamInst has key and/or value, that are not found in MParam
relinst-validation-failed	CfgRelInst has key and/or value, that are not found in MParam
resource-allocation-failure	resource could not be allocated during graph processing

Faults

code	condition
F0765	fltVnsCDevConfMismatch
F3235	fltVnsCDevVmOp