Guest

Preview Tool

Cisco Bug: CSCus91342 - Adding VLAN to vNIC template requires reboot

Last Modified

Aug 08, 2018

Products (1)

  • Cisco Unified Computing System

Known Affected Releases

2.2(1a)A 2.2(3)

Description (partial)

Symptom:
The user must reboot his servers in order for a change to a vNIC template to take effect.
BU Escalation update:
The reason for this issue to occur is that when customers upgrade from UCSM 2.1 to 2.2, the disk firmware update is not triggered.

a. Note that customer is upgrading from 2.1 that does not support localDisk FW update
b. This feature is only introduced in 2.2
c. That said when user updates the HFP by pointing to the B Bundle, it appends the local Disk FW update along with GPU
d. However this update is not triggered. Reason for this not getting triggered is that there is one minimum deep discovery that should happen for UCSM to read the localDisk FW. That gets read only after deep discovery. Till then UCSM thinks there is no update required
e. When user makes a trivial change like Adding VLAN to vNIC template, the SP is re-evaluated and UCSM sees a version mismatch between running version of LocalDisk FW and configured version in HFP
f. hence the SP goes into a pending activity stage

This can cause problem to customer as adding the VLAN may look trivial but will be a necessity to bring up services for multi-tenancy kind of environments where the activity will not be possible without a blade reboot

This problem will happen for all customers who have local disk that requires a FW upgrade.

Conditions:
Recently upgraded to 2.2(3d) code. Blades that require the reboot and blades that do not require the reboot have identical firmware versions across all components.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.