The Problem is that the 2nd VSM is at the moment the active and i`m a litttle bit afraid of making changes because of the productive system 
The primary VSM coming up but with no network connectivity and if i connect the NICs from the primary VSM i got the error in my previous post.
#show system redundancy status
Redundancy role
---------------
administrative: secondary
operational: secondary
Redundancy mode
---------------
administrative: HA
operational: None
This supervisor (sup-2)
-----------------------
Redundancy state: Active
Supervisor state: Active
Internal state: Active with no standby
Other supervisor (sup-1)
------------------------
Redundancy state: Not present
When you did the upgrade, did you copy the new image to the bootflash of each VSM?
I copied the image only to the primary VSM.If i make a "dir bootflash:" on the secondary the new images on:
# dir bootflash:
77824 Mar 30 14:32:00 2010 accounting.log
16384 Apr 26 20:04:31 2009 lost+found/
21340160 Apr 26 20:04:33 2009 nexus-1000v-kickstart-mz.4.0.4.SV1.1.bin
21408768 Mar 30 12:22:24 2010 nexus-1000v-kickstart-mz.4.0.4.SV1.2.bin
49869376 Apr 26 20:04:36 2009 nexus-1000v-mz.4.0.4.SV1.1.bin
73068811 Mar 30 12:22:11 2010 nexus-1000v-mz.4.0.4.SV1.2.bin
4096 Apr 26 20:05:01 2009 vdc_2/
4096 Apr 26 20:05:01 2009 vdc_3/
4096 Apr 26 20:05:01 2009 vdc_4/
Ping me the build # and I'll tell you which one you need.
if i look in the vSphere client the Build is 236512 but if i perform a "vem version" from the CLI i git this:
Running esx version -208167 x86_64
VEM Version: 4.0.4.1.1.30-1.9.16
VSM Version: 4.0(4)SV1(2)
System Version: VMware ESX 4.0.0 Releasebuild-208167
What do you think? Everything destroyed or is there some light at the end of the tunnel
