kennysarmy Posted May 29, 2015 Posted May 29, 2015 I've upgraded from version 11 to version 12 successfully. But I'm confused by the below upgrades that are showing and how I verify the software version is as they state? Anyone help? If I click to Continue I get:
john Posted May 29, 2015 Posted May 29, 2015 So I read that as you haven't finished upgrading yet, StoreVirtual needs you to tell it you have manually updated those plug ins that it is listing that you maybe using or may not be and then tick the box and it will then apply the updates to your appliances.
Tall_Paul Posted May 29, 2015 Posted May 29, 2015 They're additional 'bolt ons' that you may or may not have installed. All it's saying is that it's put the current versions in those locations should you wish to upgrade them (which you'll have to do manually from the specified download location). It's nothing to be concerned about.
RobD Posted May 29, 2015 Posted May 29, 2015 You can check storage system themselves for the version:
kennysarmy Posted June 1, 2015 Author Posted June 1, 2015 OK. So the upgrade has gone fine - or appeared to! But one of my SAN's now seem to be unresponsive and I can't log in to VMware vSphere Client to see which servers are struggling.... AArrrgggghhhhhhh
john Posted June 1, 2015 Posted June 1, 2015 OK. So the upgrade has gone fine - or appeared to! But one of my SAN's now seem to be unresponsive and I can't log in to VMware vSphere Client to see which servers are struggling.... AArrrgggghhhhhhh Using VMware VCentre Appliance per chance? This is the exact reason I have said as have some others on here many times to keep all of VMware VCentre on a physical box (and this includes the HP Tools for these SANs) then you can get into that when things go wrong if you only have one cluster and host the appliance on the same cluster.
kennysarmy Posted June 1, 2015 Author Posted June 1, 2015 I can get on to each host - using the root password..... Raised a support ticket with our local supplier to see if they can find out anything....
RobD Posted June 1, 2015 Posted June 1, 2015 I had this when I migrated to v12, had to reboot the node manually. Long story short part of the issue seemed to be with routing and my DNS.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now