Release Notes for Cisco UCS Manager, Release 3.0, for Cisco UCS Mini

B200 M3

3.0(1d)

3.0(2f)

C220 M3

3.0(1d)

3.0(2f)

C240 M3

3.0(1d)

3.0(2f)

B200 M4

3.0(2c)

3.0(2f)

B420 M3

3.0(2c)

3.0(2f)

B22 M3

3.0(2c)

3.0(2f)

C220 M4

3.0(2c)

3.0(2f)

C240 M4

3.0(2c)

3.0(2f)

UCS-VIC-M82-8P
UCSB-MLOM-40G-0
UCSB-MLOM-PT-01

3.0(1d)

3.0(2f)

UCSB-MLOM-40G-03
UCSB-VIC-M83P-8P
UCSC-MLOM-CSC-02

3.0(2c)

3.0(2f)

UCSC-PCIE-CSC-02

3.0(1d)

3.0(2f)

UCSB-5108-AC2

3.0(1e)

3.0(2f)

UCSB-5108-DC2

3.0(2c)

3.0(2f)

Cisco UCS 6324

3.0(1e)

3.0(2f)

UCSB-PSU-2500ACDV

3.0(1e)

3.0(2f)

QSFP-4SFP10G-CU1M
QSFP-4SFP10G-CU3M
QSFP-4SFP10G-CU5M

—

—

QSFP-4X10G-AC7M
QSFP-4X10G-AC10M

—

—

QSFP-4X10G-AOC1M
QSFP-4X10G-AOC2M
QSFP-4X10G-AOC3M
QSFP-4X10G-AOC5M
QSFP-4X10G-AOC7M
QSFP-4X10G-AOC10M

—

—

SFP-10G-LR
SFP-10G-LR-X
SFP-10G-SR
SFP-10G-SR-X
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M

—

—

SFP-H10GB-ACU7M
SFP-H10GB-ACU10M

—

—

SFP-10G-AOC1M
SFP-10G-AOC3M
SFP-10G-AOC5M
SFP-10G-AOC7M
SFP-10G-AOC10M

—

—

DS-SFP-FC8G-SW
DS-SFP-FC8G-LW

—

—

DS-SFP-FC4G-LW
DS-SFP-FC4G-SW

—

—

GLC-GE-T
GLC-LH-SM
GLC-SX-MM
GLC-T (V03 or higher)

—

—

CSCuw78688

System outage no longer occurs during an FI reboot or UCSM activation to a new version where the DME database having a corrupted entry.

2.2(3a)A

3.0(2f)A

CSCur48661

Global service profile association no longer fails with a ‘failed to copy images’ error.

2.2(3b)A

3.0(2f)A

CSCus11782

After rebooting a Fabric Interconnect (FI) that is operating in the FC end-host mode, all member links of the SAN port channel come up.

2.2(1d)A

3.0(2f)A

CSCus76125

2.2(3d)A

3.0(2f)A

CSCus82914

Configuring SPAN on Cisco UCS fabric interconnects for all VLANs including vMotion and storage Ethernet no longer decreases performance.

2.1(3a)A

3.0(2f)A

CSCuv06504

The svc_sam_dme process is no longer crashing during a steady state of operation when a database (db) corruption is detected primarily on the subordinate fabric interconnect.

2.2(3d)A

3.0(2f)A

CSCux10203

When you decommission a C-Series server after it was discovered in direct attached configuration, and the direct attached switch port was changed from Ethernet to FC mode, the following error message no longer appears:

2.2(3h)A

3.0(2f)A

CSCuo93591

For a fabric interconnect in end-host mode, the MAC address table aging time no longer gets stuck at 300 regardless of the configuration.

2.2(1c)A

3.0(2f)A

CSCup95855

FSM tasks are no longer stuck in the throttled state in Cisco UCS Manager during Cisco UCS C240 M3 server upgrade.

2.2(1d)A

3.0(2f)A

CSCur01185

The HA policy of Reset is no longer triggering the fabric interconnect to reset.

2.2(1d)A

3.0(2f)A

CSCus32933

Cisco UCS Manager now displays an error message when a WILL_BOOT_FAULT event is raised because of an incorrect CPLD version.

2.2(1a)A

3.0(2f)A

CSCus34689

When using Cisco UCS Manager with C-Series integration, Cisco UCSM GUI no longer displays the following message on hovering between the C-Series servers and FIs:

2.2(1b)A

3.0(2f)A

CSCus73964

When you download an infrastructure software bundle onto a system where the same infrastructure software bundle was previously installed, but was subsequently deleted, the UCS Manager FIs, and IOMs no longer downgrade to that software bundle.

2.1(3e)A

3.0(2f)A

CSCus93431

Adding other storage, such as a local disk or a USB to a SAN boot policy no longer deletes the SAN boot policy from Cisco UCS Manager.

2.2(3c)A

3.0(2f)A

CSCut78943

When making changes to vNICs or vHBAs that will be provisioned on Cisco Virtual Interface Cards (VICs) 1340 and 1380 adapters, a warning on the placement order impact appears.

2.2(3c)A

3.0(2f)A

CSCuu04780

Erroneous interrupts from the Chassis locator LED no longer cause dmserver cores on the fabric interconnect.

3.0(2c)A, 3.0(2d)A

3.0(2f)A

CSCuv85779

FSM association is no longer stuck in copyRemoteStage on peerdown.

2.2(3a)A

3.0(2f)A

CSCuw44595

DIMMs with correctable ECC errors are marked Inoperable or Degraded even though correctable errors do not affect normal system operation. This issue is now resolved.

2.2(3a)A

3.0(2f)A

CSCux76128

Firmware Auto Install upgrade validation fails as expected when upgrading to Cisco UCS Manager Release with deprecated hardware. Auto Install can now be initiated by using the force option either through the GUI or the CLI.

2.1(3j)A

3.0(2f)A

CSCus64439

Cisco UCS Manager Mezz logs and VMware vmkernel logs no longer indicate storage latency and numerous FNIC aborts.

2.0(1q)B

3.0(2e)B

CSCuv32417

Cisco B200 M4 and B420 M4 blade servers that boot in UEFI mode will not reboot unexpectedly.

Note BIOS POST not being set as complete, which causes the next shallow discovery to reboot the server, has been resolved. Shallow discovery can occur because of different events including Cisco UCS Manager cluster failover, CIMC reset, or chassis reacknowledgment.

3.0(2d)B

3.0(2e)B

CSCuv72663

When the FC port on the UCS Mini Fabric interconnect is directly connected to an IBM Storwize V5000 storage processor in FC Mode, if the FC link is disrupted, for example by power-cycling the IBM, placing the IBM in service mode, or removing the IBM from service mode, the FC port will reconnect after the power cycling is completed or the storage processor has completely reboot itself.

3.0(2d)A

3.0(2e)A

CSCuv83954

Traffic continues to be forwarded downstream to the servers from an external host or from another server in the same setup after a reset, reboot, HIF flap, or port channel flap.

3.0(2d)A

3.0(2e)A

CSCuw50417

After upgrading the BIOS of Cisco UCS B200 M3 servers to Release 3.0(2e), the OS no longer displays the following error message if the OS boot time is exceptionally slow:

3.0(1a)B

3.0(2e)B

CSCus56140

Fabric Interconnect failover status in a cluster is no longer stuck in Switchover In Progress when the management interface of the primary fabric interconnect is down for more than the Management Interface Monitoring Period.

2.2(3a)A

3.0(2e)A

CSCut10525

After updating the firmware on Cisco UCS B200 M4 servers to Release 3.0(2e), the following error is no longer displayed in the fault summary:

2.2(4c)B

3.0(2e)B

CSCut99437

A B200 M4 blade without a RAID controller installed no longer fails discovery with following error:

2.2(3d)B

3.0(2e)B

CSCuu15465

While trying to downgrade board controller to a lower version for Cisco UCS B200-M4 servers, Cisco UCS Manager will raise a firmware activation failure fault.

3.0(2a)A

3.0(2e)T

CSCuv04436

Cisco UCS B200 M4 servers with the following CPUs will not experience significant performance degradation:

• E5-2667 v3
• E5-2643 v3
• E5-2640 v3
• E5-2637 v3
• E5-2630 v3
• E5-2630L v3
• E5-2623 v3
• E5-2620 v3
• E5-2609 v3

3.0(2c)A

3.0(2d)A

CSCus85186

After activating Cisco Trusted Platform Module (TPM), the enable and active statuses will not remain as disabled and deactivated at the BIOS prompt.

2.2(1d)B

3.0(2d)A

CSCut70585

After a NetApp C-mode connection toggle or FI reboot, the port will not lose access to the NetApp CMOS FCoE target.

3.0(2c)A

3.0(2d)A

CSCuu51652

When two VMs are pinned on different Cisco UCS Mini FIs, traffic will be forwarded downstream to the servers.

3.0(1c)A

3.0(2d)A

CSCur86104

When the FC is directly connected via the FC storage port on the FI, if the physical connection is manually disconnected, for example, pulling the cable from the SFP or rebooting the storage processor on an appliance, the FC connectivity will reconnect after the cable has been reconnected or the storage processor has completely reboot itself.

3.0(1c)A

3.0(2d)A

CSCut43895

The following errors will not happen on a dmserver restart:

• In Cisco UCS Manager, FI-IOM remains stuck in the discovery/configuration state.
• The FI-IOM shows high CPU usage.

3.0(2c)A

3.0(2d)A

CSCuu90088

Standalone catalog upgrade from Cisco UCS Manager 3.0(1x) will no longer fail.

3.0(2c)A

3.0(2d)A

CSCut08588

Installing the license on the Cisco UCS Mini scalability port no longer fails with the following error message:

3.0(1d)A

3.0(2c)A

CSCuj74570

B420 M3 with UCSB-MLOM-PT-01 installed no longer reboots for discovery when first IOM is upgraded to 2204XP.

2.1(2a)B

3.0(2c)A

CSCul38768

“Management services are unresponsive” fault no longer displayed in Cisco UCS Manager unless there is actually an HA condition failure.

2.1(1e)A

3.0(2c)A

CSCul44120

Cisco UCS blade servers performing a PXE boot from a Citrix PVS system no longer fail after the initial bootloader initialization with a “No API found” error.

2.1(2a)B

3.0(2c)B

CSCum43435

The Cisco UCS VIC 1280 adapter on a Cisco UCS B440 M2 blade no longer hangs during PXE boot.

2.2(1b)B

3.0(2c)B

CSCum51025

Cisco UCS Manager domains registered in Cisco UCS Central no longer fail during scheduled backups.

2.2(1b)A

3.0(2c)A

CSCum60793

Cisco UCS Manager no longer reports ‘mount suspend success’ to operations manager errors when UCS becomes unreachable or unregistered with Cisco UCS Central.

2.1(2c)

3.0(2c)A

CSCum87525

The httpd.sh process on the subordinate FI no longer crashes after upgrading to 2.2(2c) from 2.1(3a) via auto install.

2.2(1b)A

3.0(2c)A

CSCum95854

Cisco UCS Manager no longer frequently closes with an "event sequencing is skewed" error.

2.2(2c)A

3.0(2c)A

CSCum98771

User no longer receives config failure message ‘ Flexflash controller error, probably not supported, not equipped or inoperable’ when Cisco UCS Manager is updated from 2.1(2a) or above to 2.2(1) with FlexFlash State enabled.

2.2(1b)A

3.0(2c)A

CSCun94906

The Cisco UCS Manager DME no longer crashes when a SP is referring to a SP template and Cisco UCS Manager is connected to Cisco UCS Central during policy ownership conflict checks.

2.2(1b)B

3.0(2c)B

CSCuo09527

A blade running on a 2-socket B420 M3 no longer boots to the BIOS screen after an update if the boot order is configured in the Cisco UCS Manager and the BIOS is set to strict mode.

2.2(1b)A

3.0(2c)A

CSCuo34760

vEthernet interfaces and VIFs no longer remain in down state if the primary FI in a HA cluster is rebooted and comes up as the secondary FI.

2.1(2d)A

3.0(2c)A

CSCup07488

ECC sensors no longer read or report invalid “Upper Non-Recoverable” data when there are existing failed PECI transactions on a blade.

2.2(2c)B

3.0(2c)B

CSCup47504

Cisco UCS VIC 1240 adapter no longer fails to complete the PXE boot process due to missing DHCP offer on a Cisco UCS 6200 FI using an ASA as the DHCP relay.

2.2(1d)B

3.0(2c)B

CSCup88161

6248 fabric interconnects no longer crash if a memory location that was freed is being used.

2.1(1d)A

3.0(2c)A

CSCuq09971

VIC cards no longer fail with an “identify failed” message when attempting to access the card from CIMC.

2.1(2c)A

3.0(2c)A

CSCuq46105

UCS Manager now uses power sequencer version 3.0 to address the rare issue of an unexpected reboot to the Cisco UCS 6248 FI.

2.2(1c)A

3.0(2c)A

CSCuq74472

Unnecessary thermal events on IOM stating that the thermal sensor reading is not available no longer occur.

2.1(3c)A

3.0(2c)A

CSCuq92477

Infra bundle upgrades from no longer fail if performed from Cisco UCS Central.

2.2(3a)A

3.0(2c)A

CSCur29264

The security vulnerability identified by Common Vulnerability and Exposures (CVE) CVE-2014-3566 is addressed.

2.2(3a)A

3.0(2c)A

CSCur66094

Multiple components no longer stick in discovery or upgrade state with no FSM progression.

2.2(2c)A

3.0(2c)A

CSCur86084

Packets with an IP header matching the hex value of 0x67 are no longer dropped by the Cisco UCS 6324 FI.

3.0(1c)A

3.0(1e)A

CSCuq35685

IGMPv2 traffic no longer causes MAC flapping on upstream switches when the FI has multiple uplinks connecting to different switches.

2.2(1b)A

3.0(1d)A

CSCur01379

The security vulnerabilities identified by Common Vulnerability and Exposures (CVE) CVE-2014-7169, CVE-2014-6271, CVE-2014-6277, CVE-2014-7186, CVE-2014-7187, and CVE-2014-6278 are addressed.

2.0(1q)A

3.0(1d)A

CSCuq04083

Trunking on uplink port-channel no longer fails when VSANs are mapped to VLANs with the same ID.

3.0(1c)A

3.0(1d)A

CSCuq00171

Zone server crashes no longer occur when you reduce the zone database size.

3.0(1c)A

3.0(1d)A

CSCuj48002

vIFs and vNICs no longer fail to come up after servers are reset.

CSCul74278

Cisco UCS Manager mode- BIOS no longer fails to find local boot device.

CSCul96021

dcosAG process no longer crashes after upgrading to Cisco UCS Manager, Release 2.2(1b).

CSCum02561

Server no longer reboots after an infra-only upgrade followed by a service profile change.

CSCum04646

FI no longer reboots during snmpwalk when ldap config is enabled.

CSCum25003

Associated LSP/GSP events are no longer sent every 3 minutes to Cisco UCS Central inventory.

CSCum51025

Cisco UCS Manager scheduled backups from Cisco UCS Central no longer fail.

CSCum57954

Excessive dropped pings eliminated during vmotion on ESXi VMFEX DVS.

CSCum63448

Blades no longer prevent non-disruptive changes if firmware status gets stuck in “activating” state.

CSCum82888

Access to Cisco UCS Manager via GUI or CLI using VIP is no longer blocked if default keyring is deleted after an upgrade to Cisco UCS Manager Release 2.2(1b).

CSCun01514

Changes to boot order between SAN & other devices via CLI or XML API no longer fails.

CSCun19289

FI mgmt0 no longer drops packets coming from blades behind that FI.

CSCun21077

Blades running ESXi OS and vEthernet no longer enforce QoS policy bandwidth cap of 10GB when hardware allows for higher speeds unless such cap is configured by user.

CSCun70365

Service profile association no longer failing at BIOS post completion stage.

CSCun93977

Logical switch GUID no longer gets changed after a backup and restore config event.

CSCuo01287

CLI now provides the ability to report packet count per QoS class.

CSCup43698

LEDs no longer light up for wrong ports when configured with both FC and Ethernet ports.

CSCus55944

Adding a VLAN to a vNIC on an service profile template reboots the rack server that is associated with the inherited service profile.

To work around this issue, do the following:

1. Run show detail under both the adaptors and note the managing instance of both the adaptors.

2. Shut down the host-facing port from FI-A that is connected to the server under question.

3. Wait for 5 minutes

4. Repeat Step 1 and ensure that the subordinate FI is the managing instance for both the adaptors.

5. Apply the service profile configuration change. This initiates reboot.

The adaptor activation status will be ready.

Any subsequent service profile configuration change will not initiate reboot unless the configuration itself requires a reboot.

CSCuv32417

Cisco B200 M4 and B420 M4 blade servers that boot in UEFI mode reboot unexpectedly when BIOS POST is not marked as complete.

There is no workaround for this issue.

CSCuv72663

When the FC port on the UCS Mini Fabric interconnect is directly connected to an IBM Storwize V5000 storage processor in FC Mode, if the FC link is disrupted, for example by power-cycling the IBM, placing the IBM in service mode, or removing the IBM from service mode, the FC port will not come-up after the power cycling is completed or the storage processor has completely reboot itself.

To work around this issue, do the following:

1. Change the fill-pattern from ARBFF to IDLE.

UCSM > FI > FC Interface > Interface Properties > Select IDLE fill word

2. Bounce the ports.

CSCuv83954

Traffic may not be forwarded downstream to the servers from an external host or from another server in the same setup after a reset, reboot, HIF flap, or port channel flap.

To work around this issue, shut and then no shut the uplink interfaces or port-channel.

CSCuv46749

When using Cisco B200 M4 blade servers with the UCSB-MRAID12G storage controller, the following random transient alerts or faults are reported, and these alerts or faults get cleared in 30 to 40 secs.

• Critical Fault [F1004] Controller Inoperable, Reason: Device reported corrupt data
• Critical Fault [F1004] Controller Inoperable, Reason: Device non-responsive

Though these alerts include 'Device reported corrupt data' faults, there is no user data corruption involved.

Note When a Storage Controller device is non-responsive, the virtual drives and local disks for this controller are also reported as Inoperable as a result.

This issue has no known workaround.

CSCuu04780

Erroneous interrupts from the Chassis locator LED cause dmserver cores on the fabric interconnect. Thermal alerts are observed shortly before the core dump happens.

When this issue occurs, contact TAC to apply the workaround.

CSCuv04436

Cisco UCS B200 M4 servers with the following CPUs may experience significant performance degradation:

• E5-2667 v3
• E5-2643 v3
• E5-2640 v3
• E5-2637 v3
• E5-2630 v3
• E5-2630L v3
• E5-2623 v3
• E5-2620 v3
• E5-2609 v3

There is no workaround for this issue. See the Software Advisory.

A patch will be released in July, 2015.

CSCus12618

When installing RHEL 7 on an iSCSI LUN using iBFT with multiple paths to the target, the OS installs without issues, but after each reboot, the OS takes a long time to come up.

This issue occurs on all supported Cisco UCS B-Series servers with VIC adaptor on RHEL 7 installation where the ip=ibft kernel parameter was passed on the kernel command line for iSCSI multipath installation.

To work around this issue, try one of the following:

• Use a single path during installation, and add a second path after the installation is complete.
• Forcefully bring the other interfaces in the same subnet in which the iFBT interfaces are configured, which allows the iSCSI session to go through those interfaces. Use the kickstart file to bring interfaces up during installation.

CSCur86104

When the FC is directly connected via the FC storage port on the FI, if the physical connection is manually disconnected, for example, pulling the cable from the SFP or rebooting the storage processor on an appliance, the FC connectivity does not reconnect after the cable has been reconnected or the storage processor has completely reboot itself.

To work around this issue, try one of the following:

• Reseat the SFP.
• Hard code the link speed to 4 Gigs.
• Change the word fill from "ARBFF" to "IDLE".
  UCSM > FI > FC Interface > Interface Properties > select "IDLE" fill word.
• Bounce the ports.

CSCut04335

The License State and License Grace Period for the scalability port may not be in sync with the Operational State and Grace Period Used displayed in UCS Manager.

Enabling or disabling the break out ports on the peer FI may correct this issue.

CSCuu51652

When two VMs are pinned on different Cisco UCS Mini FIs, certain traffic may not be forwarded downstream to the servers.

To work around this issue, try the following steps:

1. Identify the erroneous MAC entry that is out of sync between the hardware and software.

2. Use back door Cisco NX-OS CLI to configure as static MAC on the vEthernet interface.

Note Contact Cisco TAC if you need assistance with back door Cisco NX-OS CLI configuration.

3. Shut then no shut the vEthernet interface.

CSCut43895

The following errors may happen on a dmserver restart:

• In Cisco UCS Manager, FI-IOM remains stuck in the discovery/configuration state.
• The FI-IOM shows high CPU usage.

Contact Cisco TAC to resolve this issue.

CSCut70585

After a NetApp C-mode connection toggle or FI reboot, the port may lose access to the NetApp CMOS FCoE target.

To recover from this issue, try to shut no shut the port.

CSCuu90088

Standalone catalog upgrade fails when upgrading from Cisco UCS Manager release 3.0 (1.x).

To avoid this issue, do a full Cisco UCS Manager Infra bundle upgrade.

CSCuu15465

While trying to downgrade board controller to a lower version for Cisco UCS B200-M4 servers, Cisco UCS Manager will call for a power cycle.

This issue has no known workaround.

CSCuw36128

Under rare conditions, there may be statsAG mts q leaks, and the following fault may be raised:

(It could be for either A or B side, or even both)

The error messages shown in the statsAG log file may include the following:

When this issue occurs, restart UCSM processes through the CLI:

UCS-A# connect local-mgmt

UCS-A(local-mgmt)# pmon stop

UCS-A(local-mgmt)# pmon start

CSCur86104

When the FC is directly connected via the FC storage port on the FI, if the physical connection is manually disconnected, for example, pulling the cable from the SFP or rebooting the storage processor on an appliance, the FC connectivity does not reconnect after the cable has been reconnected or the storage processor has completely reboot itself.

To work around this issue, try one of the following:

• Reseat the SFP.
• Hard code the link speed to 4 Gigs.
• Change the word fill from "ARBFF" to "IDLE".
  UCSM > FI > FC Interface > Interface Properties > select "IDLE" fill word.
• Bounce the ports.

CSCtr05546

A hard-pinned vNIC does not go down after VLAN is removed from pin group.

Do not use pin group policy for a vNIC.

CSCug61578

In some cases, when the mgmt 0 interface on the primary FI goes down, SNMP traps are not triggered.

This issue has no known workaround.

CSCum72579

There is no mac entry on Cisco UCS Mini for IP multicast when viewing debug command output.

Hardware forwarding mechanism is different for Cisco UCS Mini, so debug CLI has changed.

For IP multicast, use show hard int libsdk mtc l3 route-mc valid command to dump fwding entries.

CSCun80871

Cisco UCS Mini does not support some commands that are supported in classic Cisco UCS Manager releases. For example, fex and iom are not supported and all related commands are inapplicable. Additionally, some show commands do not generate output and some scope commands will return an error.

No workaround is required; avoid use of commands not supported in Cisco UCS Manager, Release 3.0.

CSCuo01287

Although output for show queuing interface command displays drop count and per-VL/qos Rx counters, it does not include per-VL Tx statistics.

This issue has no known workaround.

CSCuo36944

In some cases when rebooting Cisco UCS Mini while connected to Cisco Nexus 5000, Release 5.1(3) or older via FCoE uplink, vFC may not come up and, as a result, corresponding vSAN on Nexus 5000 may end up isolated.

Upgrade Cisco Nexus 5000 to a newer release than 5.1(3).

CSCuo74243

In rare cases, when port-channel member interface is flapped, some traffic may get dropped.

This issue has no known workaround.

CSCup45483

In some cases, with one or a combination of the following configurations, one or all FC/FCoE up-links will remain down and, if the up-links do come up, there may be traffic disruptions and timeouts on all interfaces:

a. More than one FCoE port channel up-link.

b. More than one FC port channel up-link.

c. More than one FCoE up-link (non port-channel).

d. More than one FC up-link (non port-channel).

For cases a. and b., disable all except one port-channel.

For cases c. and d., it is advisable to convert multiple up-links to a single port-channel.

In general, there should be exactly one up-link connection to the same switch.

CSCup67796

In some cases, after activating Cisco UCS Manager on a single FI-IOM in clustering mode, user is unable to login via the GUI or access Cisco UCS Manager CLI commands.

It takes longer for Cisco UCS Manager HA election to complete on a system with a single FI-IOM in clustering mode (can take several minutes). Until the FI-IOM assumes the role of a primary node, Cisco UCS Manager will be inaccessible until FI-IOM becomes primary. You can check on progress by using the connect local-mgmt command followed by the show cluster state command.

CSCuu51652

When two VMs are pinned on different Cisco UCS Mini FIs, certain traffic may not be forwarded downstream to the servers.

To work around this issue, try the following steps:

1. Identify the erroneous MAC entry that is out of sync between the hardware and software.

2. Use back door Cisco NX-OS CLI to configure as static MAC on the vEthernet interface.

Note Contact Cisco TAC if you need assistance with back door Cisco NX-OS CLI configuration.

3. Shut then no shut the vEthernet interface.

CSCuu90088

Standalone catalog upgrade fails when upgrading from Cisco UCS Manager release 3.0 (1.x).

To avoid this issue, do a full Cisco UCS Manager Infra bundle upgrade.

CSCuw50417

After upgrading the BIOS of Cisco UCS B200 M3 servers to any release between 3.0(1c) and 3.0(2d), the OS may randomly report the following messages in the /var/log/boot.gz file of the OS if the OS boot time is exceptionally slow:

When this error occurs, it disables the OS PM capability, but has no known workaround to resolve it.

CSCui95113

Blade discovery fails with the following error:

This issue is found when adapters are in DIAG mode.

2.1(2a)B

CSCun25132

On platforms with OOB storage controller, Cisco UCS Manager displays usable (coerced) value in disk inventory section, which is different than the raw 'NumberOfBlocks' value displayed in catalog section.

This is a non-issue; Cisco UCS Manager is designed to report the coerced, or usable, size as reported by the LSI controller. Both the host and OOB interfaces report this same value.

2.2(1b)T