07-28-2022 08:14 PM
Hi,
VIC 1455 installed on C480 M5 UCSM managed and running RHEL
All of a sudden, one of the host eth interfaces ( trunk VNIC ) gave up .. i.e. stopped responding and "enic" drive tried to reset it as it considered it as "hang" as well. Rebooted the host and found that the VNIC interface probe is failed
Checking the VNIC via CLI , it seems it is in "INIT" state. Tried to reset it in UCSM but it didn't help.
All other 5 VNICs are UP and seen in the OS
I suspect some sort of h/w issue.
Have anyone seen this before and know a resolution?
Thanks
Solved! Go to Solution.
08-05-2022 11:25 AM
Public CDET CSCvs51031 is dupe'd to internal CDET CSCvr15733 which says it's fixed in 4.0(4h).
(I think as versions can be confusing on CDETs sometimes. Is that the VIC version or CIMC version or UCSM version or c-series bundle version. Ugh.)
a b c d e . . . </singing alphabet song>
Yup, your G is older than fixed H.
Try a firmware upgrade to see if that resolves your issue.
07-29-2022 06:24 AM
Hardware issue on a (virtual) vNIC? (;
Haven't seen that exact thing you describe but something similar on Hyperflex:
https://bst.cisco.com/bugsearch/bug/CSCvs51031
CSCvs51031 was an early UCS 4.0(4x) VIC 1400 firmware issue.
What UCS/VIC firmware is your server running?
Decommission/recommission should recover the vNIC. If you are on early 4.0(4x) firmware then upgrading firmware should prevent it in the future.
07-29-2022 09:02 AM
- The bug link(s) respond with You are not entitled to access bug: CSCvr15733
M.
08-05-2022 07:52 AM
Thanks the bug could be related.
UCSM/UCS - 4.0(4g)
VIC firmware - 5.0(1g)
Can you confirm if this firmware is affected by that bug?
Thanks
08-05-2022 11:25 AM
Public CDET CSCvs51031 is dupe'd to internal CDET CSCvr15733 which says it's fixed in 4.0(4h).
(I think as versions can be confusing on CDETs sometimes. Is that the VIC version or CIMC version or UCSM version or c-series bundle version. Ugh.)
a b c d e . . . </singing alphabet song>
Yup, your G is older than fixed H.
Try a firmware upgrade to see if that resolves your issue.
08-17-2022 07:15 PM
The decommissioning and recommissioning did recover the VNIC. Going to upgrade to 4.2(1n).
Thanks
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