newellt Absent Member.
Absent Member.
553 views

Problem migrating 2nd VM appliance from 11.4.3 to 2017

Hi,
I successfully migrated my first primary 11.4.3 appliance with the embedded Sybase DBs and cert authority. When I went to do my 2nd 11.4.3 appliance after supplying root and zenadmin passwords it says it doesn't like the netmask. It shows as 26 which is right but it only wants it in the format 255.255.255.192. First appliance is on same network/mask/gateway didn't have this problem. After typing in the mask the way it wanted it starts the network and configures time then comes up to a screen saying 2 disks are required / supplied by the 2017 appliance and /vastorage that was attached from a copy of the 11.4.3 VM and click here to shutdown appliance and add the disk. Behind that window Yast is asking what disk you want to chose but can't close or click behind that pop-up. 2nd disk was added per instructions same as it was for the first primary. I rebooted, same error. I know it sees the 2nd disk because it comes up with the title 11.4.3 to 2017 migration and it does have the old 11.4.3 machine IP address so the only place it would've known to read that was from the /vastorage disk. I even booted off of a SLES12 ISO into rescue mode and mounted both appliance disks just to make sure I could see everything. Noticed the 2017 mounted disk in it's /etc/fstab only had an entry for /dev/sda1 / ext3 acl 1 1 My good migrated VM also had a line for /dev/sdb1 /vastorage ext3 rw 0 0 as well as one for /swapfile. I even tried adding the /dev/sdb1 /vastorage line then disconnecting the SLES12 ISO and restarting but still no go. It seems like the initial bootup is doing some sort of RAM disk and is maybe trying to re-populate fstab on the fly, I don't know. I also tried the migration on my 3rd VM appliance and got the same problems as the 2nd one. Only difference between primary 1 and 2/3 is that 1 has the DBs and cert but no real content. I didn't want it bogged down too much so I only replicated content to 2 and 3. Which of course means I can't just scrap them and add brand new servers to #1. I did check disk space on all servers before shutting down the 11.4.3 appliances all were fine or expanded and rebooted and verified before migrating. Has anyone ever seen this or have any idea how I can get past this and pick up with the migration of the 11.4.3 data?
Thanks,
Tom
Labels (1)
0 Likes
3 Replies
AutomaticReply Absent Member.
Absent Member.

Re: Problem migrating 2nd VM appliance from 11.4.3 to 2017

newellt,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com



0 Likes
newellt Absent Member.
Absent Member.

Re: Problem migrating 2nd VM appliance from 11.4.3 to 2017

Turns out 2 of the appliances were originally installed with ip address and /26 for the mask instead of putting 255.255.255.192 mask. Worked fine day to day but the /etc/sysconfig/novell/NvlVAinit file didn't like that when migrating. Easiest way to fix was bring back up the 11.4.3 appliance, edit NvlVAinit and find the CIDR format mask which mine was '26' and change it to '255.255.255.192'. Then I re-ran the rpm for the migration prereq but with the --force option so I created a new vaconfig.zip file under /vastorage/conf. With Support we were able to unzip to verify the contents but no zip command to re-zip edited file so we downloaded the file, made the changes, and re-uploaded. But for my other server I figured I try to just change the source instead and re-run the prereq. Then shutdown and re-copied 11.4.3 VM disk for vastorage over to the new 2017 appliance and everything went through fine after that.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Problem migrating 2nd VM appliance from 11.4.3 to 2017

Thanks for Update!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.