defaultbehavior directs Cisco UCS Manager to bring the remote Ethernet interface down if the associated
borderport fails. In this scenario, any vFibreChannel interfaces that are bound to the remote Ethernet interface
arebrought down aswell.
CiscoUCS Manager, release 1.4(2) and earlier did not enforce the Action on Uplink Fail property for
thosetypes of non-VM-FEX capableconverged network adapters mentioned above. If the Action on
UplinkFail property was setto link-down,Cisco UCS Manager would ignorethis setting and instead
issuea warning. In the current version of Cisco UCS Manager this setting is enforced. Therefore, if your
implementationincludes one of those converged network adapters and the adapter is expected to handle
bothEthernet and FCoEtraffic, we recommend that you configure the Action on Uplink Fail property
witha value of warning.
Pleasenote that this configuration may result in an Ethernet teaming driver not being able to detect a link
failurewhen the borderport goes down.
Note
MAC Registration Mode
InCisco UCS Manager, releases 1.4 and earlier, MAC addresses were installed on all of the VLANs belonging
toan interface. Starting in release 2.0, MAC addresses are installed only on the native VLAN by default. In
mostimplementations this maximizesthe VLAN portcount.
Ifa trunking driver is being run on the host and the interface is in promiscuous mode, we recommend that
youset theMac RegistrationMode to AllVLANs.
Note
Power Control Policy
CiscoUCS uses the priority set in the power control policy, along with the blade type and configuration, to
calculatethe initial power allocation for each blade within a chassis. During normal operation, the active
bladeswithin a chassis can borrow powerfrom idleblades within the same chassis. If allblades are active
andreach the power cap, service profiles with higher priority power control policies take precedence over
serviceprofiles with lower prioritypower control policies.
Priorityis ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority.
Thedefault priority is 5.
Formission-critical application a special priority called no-cap is also available. Setting the priority to no-cap
preventsCisco UCS from leveraging unused power from that particular blade server. The server is allocated
themaximum amount of power thatthat blade can reach.
Youmust include this policy in a service profile and that service profile must be associated with a server
forit totake effect.
Note
Power Policy
Thepower policy is a global policy that specifies the redundancy for power supplies in all chassis in the Cisco
UCSdomain. This policy is alsoknown as thePSU policy.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
24 OL-25712-04
Server Architecture and Connectivity