hello,
i started the update procedure and the VM rebooted, no errors have been reported during the boot process.
Now i cant access the machine over the network. syscli --show netcfg shows the right configuration for the network interface, but still the machine is not pingable.
i tried to delete the netcfg configuration from syscli and recreate it, then reboot. still no access !
Tags:
Sorry that this isn't working for you, I hope you made a snapshot of the VM before the upgrade.
So, a few questions:
Thanks and sorry that this isn't working for you.
Oh, and make sure that you aren't assigning an IP address within the range of
10.17.21.0 to
10.17.21.24
Which are reserved and can not be used for the V1000.
Right, thanks for the comprehensive list of check ups. unfortunately i didn't have a backup before the upgrade, but its not a production machine yet, so i'm thankful.
- i read the release notes, no info useful for my situation.
- i'm using a static ip assigned manually, no vlan tags
- no bonding, just one nic
- didn't reboot after deleting net config, going to try it now
- after upgrade, one nic, eth0 and the ip is assigned to eth0:1
- no replication active at time of upgrade
- no network accessibility whatsoever
Uh...that's not correct at all.
The screen shot you show is definitely from the old release. Either the upgrade didn't finish or there was an error.
You mentioned that this wasn't a production system yet. Any chance you could start from scratch with the brand new DXi V1000 version 2.2.1?
You already have a key that would work (I Emailed it to you), so that could be entered directly during the configuration process.
If you want to do this, you do NOT need to use the firmware image upgrade and you do NOT need to register to re-download the binary.
Instead, follow the links for the Download tab at the top of the Forum page where you can read the End User License Agreement (in PDF form) then download the OVF.ZIP file for DXi V1000 version 2.2 directly.
Here is a link to the DXi V1000 version 2.2 Download file directly.
ok i got this sorted.. sorry for that..
actually there were several strange things coinciding, the virtual network switch on the ESX failed the same time i was upgrading the VM, thats why i couldn't get the network up.
the upgrade process did start activation and reboot, but then after i got the network up and logged in, i found out that the upgrade process did ot continue due to admin alerts generated about network downtime.
deleted alerts and the activation went on.
but i'm downloading the new release anyway.
thanks for your time, appreciate it.
Wow. Talk about a strange set of events!
However, I'm personally breathing a sigh of relief.
Once the Activation finishes, you should be fine then and not need to install the new V1000 version 2.2 if you don't want to.
Please do read through the Release Notes for version 2.2 as well as hit the highlights of the Users Guide. There are many new enhancements in this release of the product.
Thanks and thank you for keeping us informed. I was beginning to wonder if we had a new upgrade bug! Turns out that upgrade did exactly what it was supposed to do in that situation!
Just doing a check-in with you. Did you finally get your V1000 upgraded to DXi V1000 version 2.2? If so, I assume your VMware networking became operational again so you can access to V1000?
Please let me know if you still have any issues?
sorry for the late reply.
Thanks, everything is working fine now, no issues.
thanks for the followup!
© 2024 Created by Quantum Forum V. Powered by