Overview  Containers  Contained  Inheritance  Events  Faults  FSMs  Properties Summary  Properties Detail  Naming 

Class vnic:IPv4If (CONCRETE)

Class ID:164
Encrypted: false - Exportable: true - Persistent: true
Privileges: [See Containers Hierarchies]
SNMP OID: .1.3.6.1.4.1.9.9.719.1.133.24

Represents a network end-point configured with an IPv4 Interface.

An IP interface can be provisioned using a user-specified static address, a pool of IP addresses or through DHCP.
Optionally, the IPv4 interface may be provisionned with a default gateway, static routes and DNS servers.

Naming Rules 
RN FORMAT: ipv4

    [1] PREFIX=ipv4


DN FORMAT: 

[0] fabric/lan/network-sets/fabric-network-[name]/fabric-network-def-[name]/vm-network-def-[name]/if-[name]/ipv4

[1] fabric/lanmon/eth-flow-monitoring/flow-exporter-profile-[name]/if-[name]/ipv4

[2] org-[name]/tier-[name]/ls-[name]/if-[name]/ipv4

[3] org-[name]/ls-[name]/if-[name]/ipv4

[4] org-[name]/tier-[name]/ls-[name]/ether-[name]/if-[name]/ipv4

[5] org-[name]/ls-[name]/ether-[name]/if-[name]/ipv4

[6] org-[name]/lan-conn-pol-[name]/ether-[name]/if-[name]/ipv4

[7] org-[name]/tier-[name]/ls-[name]/ipc-[name]/if-[name]/ipv4

[8] org-[name]/ls-[name]/ipc-[name]/if-[name]/ipv4

[9] org-[name]/lan-conn-templ-[name]/if-[name]/ipv4

[10] fabric/lan/profiles/vnic-[name]/if-[name]/ipv4

[11] org-[name]/tier-[name]/ls-[name]/iscsi-boot-params/boot-vnic-[name]/ipv4

[12] org-[name]/ls-[name]/iscsi-boot-params/boot-vnic-[name]/ipv4

[13] org-[name]/tier-[name]/ls-[name]/iscsi-[name]/vlan/ipv4

[14] org-[name]/ls-[name]/iscsi-[name]/vlan/ipv4

[15] org-[name]/tier-[name]/ls-[name]/iscsi-[name]/vlan/ipv4

[16] org-[name]/ls-[name]/iscsi-[name]/vlan/ipv4

[17] org-[name]/lan-conn-pol-[name]/iscsi-[name]/vlan/ipv4


Containers Hierarchies
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		fabric:Ep The root container of all fabric configuration objects.
 
 		 ├
 		fabric:LanCloud A container for logical Ethernet configuration Objects that span across the Fabric Interconnects. The contained configuration objects specify the logical Ethernet configuration, including fabric A and B, VLANs, pin groups, flow control policy, QoS policy, threshold policy, and port profiles.
 
 		 
 		 ├
 		extvmm:NetworkSets A Logical singleton container object which contains all the virtual network components.
 
 		 
 		 
 		 ├
 		extvmm:FabricNetwork NON SINGLETON NETWORK OBJECTS Fabric Network or Logical Network, contains multiple FNDs or Network Sites
 
 		 
 		 
 		 
 		 ├
 		extvmm:FabricNetworkDefinition Fabric Network Definition or Network Site, contains multiple VMNDs or Network Segments
 
 		 
 		 
 		 
 		 
 		 ├
 		extvmm:VMNetworkDefinition VM Network Definition or Network Segment each contain a single VLAN reference. The VLAN can be a regular VLAN or pVlan. If pVlan is used, every VMND under a single FND must have the same primary VLAN. A mix of regular VLANs and pVlans underneath a single FND is permitted. VMND also maintains a reference to an externally-managed IP Pool. This IP Pool is used by an...
 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-network-policy, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		fabric:Ep The root container of all fabric configuration objects.
 
 		 ├
 		fabric:LanCloud A container for logical Ethernet configuration Objects that span across the Fabric Interconnects. The contained configuration objects specify the logical Ethernet configuration, including fabric A and B, VLANs, pin groups, flow control policy, QoS policy, threshold policy, and port profiles.
 
 		 
 		 ├
 		vnic:ProfileSet A collection of vnic profile policies.
 
 		 
 		 
 		 ├
 		vnic:Profile A vnic profile is a policy applied to vnic/connectivity resources dynamically requested by a hypervisor. It defines: Connectivity rules by referring to a set of networks (VLANs) via contained {@link vnic:EtherIf} objects. Each contained {@link vnic:EtherIf} refers to a named VLAN. Qos policy binding Typically, a vn...
 
 		 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-network-policy, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		fabric:Ep The root container of all fabric configuration objects.
 
 		 ├
 		fabric:LanMonCloud A container for logical Ethernet monitoring configuration Objects that span across the Fabric Interconnects. The contained configuration objects specify the logical monitoring configuration (SPAN), including Ethernet SPAN sessions on fabric A and B.
 
 		 
 		 ├
 		fabric:EthLanFlowMonitoring
 
 		 
 		 
 		 ├
 		fabric:FlowMonExporterProfile A representation of a communication profile that can be used by one or more netflow exporters for communicating with one or more external netflow collectors. This mo contains all the network policies and properties that can be used by netflow exporters to configure the network infrastructure required for communicating with the external collector.
 
 		 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ext-lan-config, ext-lan-policy, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		vnic:EtherBase An abstract representation of a logical Ethernet interface within an ls:Server instance. The interface is realized when the ls:Server is associated with a physical server and the system can find a suitable hardware Ethernet adapter that can implement the interface specified in this MO.
 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		vnic:Ether Represents a logical Ethernet interface within a ls:Server The interface is realized when the ls:Server is associated with a physical server and the system can find a suitable hardware Ethernet adapter that can implement the interface specified in this MO. From the operating system perspective, each vnic:Ether instance will be visible as one network adapter, such as eth0, eth1, eth2.....
 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		vnic:IScsiBootParams Contains the iSCSI boot configuration of a service profile.
 
 		 
 		 
 		 ├
 		vnic:IScsiBootVnic Identifies the vnic for iscsi boot and contains settings.
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		vnic:IScsiLCP
 
 		 
 		 
 		 ├
 		vnic:Vlan
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		vnic:IScsi An IScsi vnic.
 
 		 
 		 
 		 ├
 		vnic:Vlan
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 ├
 		vnic:Ipc
 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		vnic:EtherBase An abstract representation of a logical Ethernet interface within an ls:Server instance. The interface is realized when the ls:Server is associated with a physical server and the system can find a suitable hardware Ethernet adapter that can implement the interface specified in this MO.
 
 		 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		vnic:Ether Represents a logical Ethernet interface within a ls:Server The interface is realized when the ls:Server is associated with a physical server and the system can find a suitable hardware Ethernet adapter that can implement the interface specified in this MO. From the operating system perspective, each vnic:Ether instance will be visible as one network adapter, such as eth0, eth1, eth2.....
 
 		 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		vnic:IScsiBootParams Contains the iSCSI boot configuration of a service profile.
 
 		 
 		 
 		 
 		 ├
 		vnic:IScsiBootVnic Identifies the vnic for iscsi boot and contains settings.
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		vnic:IScsiLCP
 
 		 
 		 
 		 
 		 ├
 		vnic:Vlan
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		vnic:IScsi An IScsi vnic.
 
 		 
 		 
 		 
 		 ├
 		vnic:Vlan
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		ls:Tier Tier
 
 		 
 		 ├
 		ls:Server Logical Server Definition. Holds and Regulates Specification of: identity connectivity applied to the physical compute node like compute:Blade upon association. Logical Server can serve the following purposes: associatable instance initialization template persistent ...
 
 		 
 		 
 		 ├
 		vnic:Ipc
 
 		 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		vnic:LanConnPolicy This policy describes the network configuration that can be applied to a service profile. The network configuration would include mac address pool and vnics. It can be referenced from a vnicConnPolicy.
 
 		 
 		 ├
 		vnic:Ether Represents a logical Ethernet interface within a ls:Server The interface is realized when the ls:Server is associated with a physical server and the system can find a suitable hardware Ethernet adapter that can implement the interface specified in this MO. From the operating system perspective, each vnic:Ether instance will be visible as one network adapter, such as eth0, eth1, eth2.....
 
 		 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		vnic:LanConnPolicy This policy describes the network configuration that can be applied to a service profile. The network configuration would include mac address pool and vnics. It can be referenced from a vnicConnPolicy.
 
 		 
 		 ├
 		vnic:IScsiLCP
 
 		 
 		 
 		 ├
 		vnic:Vlan
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-server, ls-storage
top:Root This class represents the root element in the object hierarchy. All managed objects in the system are descendants of the Root element.
 ├
 		org:Org
 
 		 ├
 		vnic:LanConnTempl A vNIC template is a policy that defines how a vNIC on a server connects to the LAN. You can bind a vNIC associated with a service profile to a vNIC template. When you bind the vNIC to a vNIC template, Cisco UCS Manager configures the vNIC with the values defined in the vNIC template. If the existing vNIC configuration does not match the vNIC template, Cisco UCS Manager reconfigures the vNIC. You can only chan...
 
 		 
 		 ├
 		vnic:EtherIf A logical Ethernet Interface connected to a single Layer 2 network. Multiple vnic:EtherIf instances can belong to a single network adapter. For example, to create a service profile with one network adapter configured in trunk mode, add a vnic:Ether MO, which represents the network adapter. Then add a vnic:EtherIf MO as a child of vnic:Ether for each VLAN that you want to expose to the network adapter.
 
 		 
 		 
 		 ├
 		vnic:IPv4If
Privileges: admin, ls-compute, ls-config, ls-network, ls-network-policy, ls-server, ls-storage


Contained Hierarchy
vnic:IPv4If
 ├
 		vnic:IPv4Dhcp Represents an IPv4 interface which is configured at run-time through DHCP.
 ├
 		vnic:IPv4Dns Represents the IP address of a DNS server, which is used to resolve host names to IP addresses.
 ├
 		vnic:IPv4StaticRoute Represents a statically configured IPv4 route entry. A static route is configured by specifying a destination network and next hop router.
 ├
 		vnic:IfRole An abstract base class representing the role(s) assigned to the IP interface
 ├
 		vnic:IpV4Addr An abstract base class for IP v4 addresses.
 ├
 		vnic:IpV4PooledAddr Represents the IPv4 address of an IP interface, where the IP address is obtained from a pool of IP addresses.
 
 		 ├
 		fault:Inst An abnormal condition or defect at the component, equipment, or sub-system level which may lead to a failure, as defined in ISO/CD 10303-226.
 
 		 ├
 		vnic:IpV4History A temporary object used to hold the history of ipv4 address of MOs.
 ├
 		vnic:IpV4StaticAddr Represents a statically assigned IPv4 address.
Inheritance
naming:NamedObject
 ├
 		vnic:Connection
 
 		 ├
 		vnic:If
 
 		 
 		 ├
 		vnic:L3If
 
 		 
 		 
 		 ├
 		vnic:IPIf An abstract base class for all IPv4 and IPv6 interfaces
 
 		 
 		 
 		 
 		 ├
 		vnic:IPv4If
Events


Faults


Fsms


Properties Summary
Defined in: vnic:IPv4If
address:IPv4 addr  (vnic:IPv4If:addr)
           NO COMMENTS
mo:PropAclMask
          scalar:Uint64 		propAcl  (vnic:IPv4If:propAcl)
           NO COMMENTS
Defined in: vnic:If
vnic:ConfigIssues
          scalar:Bitmask64 		configQualifier  (vnic:If:configQualifier)
           Indicates configuration issues for the vnic.
network:VnetDn
          reference:Object 		operPrimaryVnetDn  (vnic:If:operPrimaryVnetDn)
           The VLAN Dn of the resolved primary VLAN. This property is applicable for secondary PVLANs.
network:VnetName
          string:Basic 		operPrimaryVnetName  (vnic:If:operPrimaryVnetName)
           The VLAN Name of the resolved primary VLAN. This property is applicable for secondary PVLANs.
vnic:IfOperState
          scalar:Enum8 		operState  (vnic:If:operState)
           property name="nwName" type="string:Basic" refers="fabric:VnetEp" owner="management" mod="implicit" /
network:VnetDn
          reference:Object 		operVnetDn  (vnic:If:operVnetDn)
           NO COMMENTS
network:VnetName
          string:Basic 		operVnetName  (vnic:If:operVnetName)
           NO COMMENTS
scalar:Uint32 pubNwId  (vnic:If:pubNwId)
           The VLAN ID of the resolved primary VLAN. This property is applicable for secondary PVLANs.
fabric:VlanSharingType
          scalar:Enum8 		sharing  (vnic:If:sharing)
           The sharing type of this VLAN, such as standard, primary PVLAN, isolated PVLAN or community PVLAN
network:VNetId
          scalar:Uint32 		vnet  (vnic:If:vnet)
           NO COMMENTS
Defined in: vnic:Connection
naming:Name
          string:Basic 		name  (vnic:Connection:name)
           Overrides:naming:NamedObject:name
           NO COMMENTS
vnic:Owner
          scalar:Enum8 		owner  (vnic:Connection:owner)
           NO COMMENTS
network:SwitchId
          scalar:Enum8 		switchId  (vnic:Connection:switchId)
           NO COMMENTS
vnic:ConnectionType
          scalar:Enum8 		type  (vnic:Connection:type)
           NO COMMENTS
Defined in: mo:TopProps
mo:ModificationChildAction
          scalar:Bitmask32 		childAction  (mo:TopProps:childAction)
          
reference:Object dn  (mo:TopProps:dn)
           The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to the object. It is built as a sequence of relative names separated by the "/" character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />
reference:RN rn  (mo:TopProps:rn)
           The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example, the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1") within the context:
<... rn ="../" />
mo:InstSaclType
          scalar:Bitmask8 		sacl  (mo:TopProps:sacl)
           The system acl property for each Managed Object. br/> This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade

By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
mo:ModificationStatus
          scalar:Bitmask32 		status  (mo:TopProps:status)
           This property controls the life cycle of a managed object
Properties Detail

addr

Type: address:IPv4
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

childAction

Type: mo:ModificationChildAction
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelChildAction
Property Validators:

Comments:
Constants
deleteAll 16384u NO COMMENTS
ignore 4096u NO COMMENTS
deleteNonPresent 8192u NO COMMENTS
DEFAULT 0 This type is used to

configQualifier

Type: vnic:ConfigIssues
Primitive Type: scalar:Bitmask64
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
Indicates configuration issues for the vnic.
Constants
not-applicable 0ull NO COMMENTS
adaptor-protected-eth-capability 1024ull NO COMMENTS
vif-resources-overprovisioned 1048576ull NO COMMENTS
ungrouped-domain 1073741824ull NO COMMENTS
unsupported-nvgre 1099511627776ull NO COMMENTS
unsupported-adaptor-for-vnic-cdn 1125899906842624ull NO COMMENTS
misconfigured-net-san-group 1152921504606846976ull NO COMMENTS
unresolved-remote-vlan-name 128ull NO COMMENTS
invalid-wwn 131072ull NO COMMENTS
service-profile-virtualization-conflict 134217728ull NO COMMENTS
unsupported-roce-netflow 137438953472ull NO COMMENTS
unsupported-vxlan-netflow 140737488355328ull NO COMMENTS
redundancy-vnicpair-not-in-sync 144115188075855872ull NO COMMENTS
fcoe-capacity 16384ull NO COMMENTS
wwpn-derivation-virtualized-port 16777216ull NO COMMENTS
unresolved-vlan-name 16ull NO COMMENTS
vnic-virtualization-netflow-conflict 17179869184ull NO COMMENTS
unsupported-vxlan-usnic 17592186044416ull NO COMMENTS
unsupported-roce-properties 18014398509481984ull NO COMMENTS
pinning-vlan-mismatch 1ull NO COMMENTS
adaptor-requirement 2048ull NO COMMENTS
vnic-not-ha-ready 2097152ull NO COMMENTS
missing-ipv4-inband-mgmt-addr 2147483648ull NO COMMENTS
unsupported-nvgre-dynamic-vnic 2199023255552ull NO COMMENTS
duplicate-vnic-cdn-name 2251799813685248ull NO COMMENTS
overlapping-vlans 2305843009213693952ull NO COMMENTS
unresolved-remote-vsan-name 256ull NO COMMENTS
mac-derivation-virtualized-port 262144ull NO COMMENTS
vnic-virtualization-conflict 268435456ull NO COMMENTS
unsupported-roce 274877906944ull NO COMMENTS
unsupported-nvgre-netflow 281474976710656ull NO COMMENTS
unsupported-adaptor-for-vnic-oracle-rac 288230376151711744ull NO COMMENTS
vnic-vlan-assignment-error 2ull NO COMMENTS
insufficient-vhba-capacity 32768ull NO COMMENTS
inaccessible-vlan 32ull NO COMMENTS
unable-to-update-ucsm 33554432ull NO COMMENTS
soft-pinning-vlan-mismatch 34359738368ull NO COMMENTS
unsupported-roce-sriov 35184372088832ull NO COMMENTS
unsupported-nvgre-vmq 36028797018963968ull NO COMMENTS
connection-placement 4096ull NO COMMENTS
vnic-vcon-provisioning-change 4194304ull NO COMMENTS
missing-ipv6-inband-mgmt-addr 4294967296ull NO COMMENTS
unsupported-nvgre-usnic 4398046511104ull NO COMMENTS
insufficient-roce-resources 4503599627370496ull NO COMMENTS
unsupported-vm-multi-queue 4611686018427387904ull NO COMMENTS
missing-primary-vlan 4ull NO COMMENTS
adaptor-fcoe-capability 512ull NO COMMENTS
vfc-vnic-pvlan-conflict 524288ull NO COMMENTS
virtualization-not-supported 536870912ull NO COMMENTS
unsupported-vxlan 549755813888ull NO COMMENTS
unsupported-roce-nvgre 562949953421312ull NO COMMENTS
unresolved-net-san-group 576460752303423488ull NO COMMENTS
unresolved-vsan-name 64ull NO COMMENTS
insufficient-vnic-capacity 65536ull NO COMMENTS
unassociated-vlan 67108864ull NO COMMENTS
unsupported-roce-vmq 68719476736ull NO COMMENTS
unsupported-roce-vxlan 70368744177664ull NO COMMENTS
unsupported-vxlan-vmq 70368744177664ull now we support vxlan and nvgre with VMQ const name="unsupported-nvgre-vmq" value="35184372088832" help="Cannot apply NVGRE policy if VMQ is enabled"/
redundancy-vnic-not-in-pair 72057594037927936ull NO COMMENTS
dynamic-vf-vnic 8192ull NO COMMENTS
wwpn-assignment 8388608ull NO COMMENTS
missing-ipv4-addr 8589934592ull NO COMMENTS
unsupported-vxlan-dynamic-vnic 8796093022208ull NO COMMENTS
pinned-target-misconfig 8ull NO COMMENTS
unsupported-vmq-resources 9007199254740992ull NO COMMENTS
DEFAULT not-applicable(0ull) NO COMMENTS

dn

Type: reference:Object
Units: null
Encrypted: false
Access: implicit
Category: TopLevelDn
Property Validators:

Comments:
The Distinguished Name (dn) unambiguously identifies an object in the system.
The dn provides a fully qualified path from the top of the object tree, all the way to the object. It is built as a sequence of relative names separated by the "/" character.
For example:
< ... dn = "sys/chassis-5/blade-2/adaptor-1" />

name

Type: naming:Name
Primitive Type: string:Basic
Overrides:naming:NamedObject:name
Units: null
Encrypted: false
Access: admin
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "16"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

Comments:
NO COMMENTS

operPrimaryVnetDn

Type: network:VnetDn
Primitive Type: reference:Object
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
The VLAN Dn of the resolved primary VLAN. This property is applicable for secondary PVLANs.

operPrimaryVnetName

Type: network:VnetName
Primitive Type: string:Basic
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "32"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

Comments:
The VLAN Name of the resolved primary VLAN. This property is applicable for secondary PVLANs.

operState

Type: vnic:IfOperState
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
property name="nwName" type="string:Basic" refers="fabric:VnetEp" owner="management" mod="implicit" /
Constants
indeterminate 0 add fcoe
up 1 NO COMMENTS
down 2 NO COMMENTS
failed 4 NO COMMENTS
DEFAULT indeterminate(0) add fcoe

operVnetDn

Type: network:VnetDn
Primitive Type: reference:Object
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

operVnetName

Type: network:VnetName
Primitive Type: string:Basic
Units: null
Encrypted: false
Access: oper
Category: TopLevelRegular
Property Validators:
    Range:  min: "0"  max: "32"
        Allowed Chars:
            Regex: [a-zA-Z0-9_.:-]+

Comments:
NO COMMENTS

owner

Type: vnic:Owner
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
unknown 0 Unknown ownership.
physical 1 Owned by physical.
policy 2 Owned by a policy.
logical 4 Owned by logical.
initiator_policy 7 Owned by a iSCSI Initiator Autoconfig policy.
conn_policy 8 Owned by a LAN Connection policy.
DEFAULT logical(4) Owned by logical.

propAcl

Type: mo:PropAclMask
Primitive Type: scalar:Uint64
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS

pubNwId

Type: scalar:Uint32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
The VLAN ID of the resolved primary VLAN. This property is applicable for secondary PVLANs.

rn

Type: reference:RN
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRn
Property Validators:

Comments:
The Relative Name (rn) uniquely identifies an object within a given context.
Note that a dn is comprised of a sequence of relative names. For example, the context "sys/chassis-1/blade-1/adaptor-1/host-eth-2" can be thought of as the following expression:
dn = <root object>/{rn}/{rn}/{rn}/{rn}/{rn}.
The rn can then be used to identify the object (for instance, "adaptor-1") within the context:
<... rn ="../" />

sacl

Type: mo:InstSaclType
Primitive Type: scalar:Bitmask8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelSacl
Property Validators:

Comments:
The system acl property for each Managed Object. br/> This property is a 8 bit mask and supports the following values :-
a: del
b: mod
c: addchild
d: cascade

By default all Managed Objects have the following permissions
a: del
b: mod
c: addchild
This property is persisted in the db. If this property has a value none
it means, the user has read only permissions on this object.
Constants
none 0 NO COMMENTS
del 1 NO COMMENTS
mod 2 NO COMMENTS
addchild 4 NO COMMENTS
cascade 8 NO COMMENTS
DEFAULT 0 NO COMMENTS

sharing

Type: fabric:VlanSharingType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
The sharing type of this VLAN, such as standard, primary PVLAN, isolated PVLAN or community PVLAN
Constants
none 0 NO COMMENTS
primary 1 NO COMMENTS
isolated 2 NO COMMENTS
community 3 NO COMMENTS
DEFAULT 0 NO COMMENTS

status

Type: mo:ModificationStatus
Primitive Type: scalar:Bitmask32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelStatus
Property Validators:

Comments:
This property controls the life cycle of a managed object
Constants
removed 16u In a setter method: specifies that an object should be removed.
In the return value of a setter method: indicates that an object has been removed.
created 2u In a setter method: specifies that an object should be created. An error is returned if the object already exists.
In the return value of a setter method: indicates that an object has been created.
modified 4u In a setter method: specifies that an object should be modified
In the return value of a setter method: indicates that an object has been modified.
deleted 8u In a setter method: specifies that an object should be deleted.
In the return value of a setter method: indicates that an object has been deleted.
DEFAULT 0 This type controls the life cycle of objects passed in the XML API.

When used in a setter method (such as configConfMo), the ModificationStatus specifies whether an object should be created, modified, deleted or removed.
In the return value of a setter method, the ModificationStatus indicates the actual operation that was performed. For example, the ModificationStatus is set to "created" if the object was created. The ModificationStatus is not set if the object was neither created, modified, deleted or removed.

When invoking a setter method, the ModificationStatus is optional:
If a setter method such as configConfMo is invoked and the ModificationStatus is not set, the system automatically determines if the object should be created or modified.

switchId

Type: network:SwitchId
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
NONE 0 NO COMMENTS
A 1 NO COMMENTS
B 2 NO COMMENTS
DEFAULT A(1) NO COMMENTS

type

Type: vnic:ConnectionType
Primitive Type: scalar:Enum8
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:

Comments:
NO COMMENTS
Constants
unknown 0 add fcoe
ether 1 NO COMMENTS
fc 4 NO COMMENTS
scsi 8 NO COMMENTS
ipc 16 NO COMMENTS
DEFAULT 0 NO COMMENTS

vnet

Type: network:VNetId
Primitive Type: scalar:Uint32
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
    Range:  min: (long)1l  max: (long)4093l

Comments:
NO COMMENTS
Constants
defaultValue 1u const name="default" value="1"/
Overview  Containers  Contained  Inheritance  Events  Faults  FSMs  Properties Summary  Properties Detail  Naming