08-10-2017
02:04 AM
- last edited on
03-20-2019
09:28 PM
by
NikolaIvanov
Hello,
for some customers I need some clarifications about this bug from Cisco. The problem is, that the description (especially the More Info section) does not match the product list attached to this bug.
More Info:The issue is only seen on N5K-C5596UP, N5K-C5596T and UCS-FI-6296UP, Nexus 50x0 and Nexus 5548s are NOT affected.
Product: |
(14)
|
09-03-2019 05:05 AM
I experienced a similar problem whereby we lost power to a server and it would no longer turn on. We had to disassociate and then re-associate the server from the template/profile inside of the FI. The server would then power on but would not boot. During the disassociating and re-association one of the PCI ids' of 007 changed to 008. We adjusted boot parameters to account for the PCI id change and were able to fully boot.
In hindsight - I think we could have unplugged both power cables to the server and left it off for 30 seconds and then the power button would have worked and we could have powered up the server without having to disassociate and then re-associate the server from the template/profile inside the FI. This simple tactic may have also prevented the PCI id change.
Equipment: Cisco UCS 6296UP
Problem: Server no longer powering on after power failure / failure to boot after disassociation/re-association
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide