Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

Lost IP Address for VMKernel iSCSI After Upgrading to ESX 3.5

$
0
0

Hi Folks:

 

I decided to take the plunge and upgrade one of our ESX 3.0.2 servers to ESX 3.5 with a freshly burnt CD. Now I have the following symptom which I need help fixing:

 

- the IP address seems to have disappeared for the "VMKernel iSCSI" virtual machine port group, i.e. it does not show up in the VI Client (yes, I installed the latest client after the upgrade). Also, I was not able to see the iSCSI volume/lun that the ESX server was seeing before the upgrade. Until that is, I did the following:

 

            - At the service console command line, run esxcfg-swiscsi -e

            - At the service console command line, run esxcfg-swiscsi -d

            - At the service console command line, run esxcfg-swiscsi -e

            - At the service console command line, run esxcfg-swiscsi -s

 

   After this, I could see the volume/lun and was able to browse it and then re-register the VM that I wanted to bring up.

 

- when doing a "esxcfg-vmknic -l" at the SSH command prompt I do see the following:

 

            Interface  Port Group          IP Address         Netmask            Broadcast          MAC Address MTU  TSO MSS   Enabled

                          VMkernel iSCSI   yyy.yyy.yyy.178 255.255.255.192 yyy.yyy.yyy.191 00:50:.....       0        disabled     false

            vmk0       VMotion              yyy.yyy.yyy.177 255.255.255.192 yyy.yyy.yyy.191 00:50:.....      1500   disabled     true

 

- however, the problem now is that there is no way to power up the VM that I re-registered. Everything is greyed out so cannot even select the option to start up the VM. Also, the fact that I cannot see the IP address for the "VMKernel iSCSI" virtual machine port group in the VI Client worries me. I even tried to remove the "VMKernel iSCSI" virtual machine port group but without success - got an error saying it was being used.

 

Help! Any suggestions welcome.


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>