Help me about this log on n1000v : %VDC_MGR-2-VDC_CRITICAL:

[fedcre]

After an upgrade of N1000v from SV1(5.2) to SV2(2.2) , when i started to put the new vem with the new vib file , so i have a mixed of the new vem and the old one i have this message :

 %VDC_MGR-2-VDC_CRITICAL: vdc_mgr has hit a cri
tical error: SPROM data is invalid. Please reprogram your SPROM!

the module are now :

Mod  Sw                  Hw
---  ------------------  ------------------------------------------------
1    4.2(1)SV2(2.2)      0.0
2    4.2(1)SV2(2.2)      0.0
9    4.2(1)SV1(5.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
11   4.2(1)SV1(5.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
12   4.2(1)SV1(5.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
13   4.2(1)SV1(5.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
15   4.2(1)SV1(5.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
18   4.2(1)SV1(5.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)
19   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
20   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
21   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
22   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
23   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
24   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)

25   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
26   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
27   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
28   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
29   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)
30   4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1474528 (3.2)

Does anybody  know the meaning of the log message. Is something i can do, or the message can disappear after i've completed all the vem ?

Thanks

Federica

[joeharb]

I am experiencing the same issue, did you get any resolution to this issue?

Thanks,

Joe

[fedcre]

Hi,

no resolution on that.. The log is stopped after the new vem insertion.. It seems a log from NXOS , properly of an hardware device (7k, 5k), it seems strange on n1000v talking about a reprogramming of SPROM... no commands on that...

Let me know if you resolve the issue.

Federica

[skarthic · Accepted solution]

You are running into the following defect

https://tools.cisco.com/bugsearch/bug/CSCul65853/

The error message occurs during the time aVEM is attached to VSM and can be ignored.

Thanks,
Karthic 

[fedcre]

Thanks Karthic ,

i'm pleased to know that no action is to be done... 

Have a good day

Federica

[Vinay Sharma]

Thank you Karthic for sharing such a crucial information with users, 5+ :-)

This information has been captured in Document.

Regards,

Vinay Sharma
Community Manager