| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
├
|
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:DynamicConPolicyRef Privileges: admin, ls-config, ls-network, ls-server |
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
├
|
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:DynamicConPolicyRef Privileges: admin, ls-config, ls-network, ls-server |
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
├
|
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:DynamicConPolicyRef Privileges: admin, ls-config, ls-network, ls-server |
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
├
|
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:DynamicConPolicyRef Privileges: admin, ls-config, ls-network, ls-network-policy, ls-server |
|