Smart1 cloud migration tool does not recognize SMS and won't run.

[dmoore19975]

I am trying to migrate a stand alone R80.40  JHF take 139 SMS to Smart 1 cloud. I have downloaded the migration script from the tenant and copied it to /var/log. I changed the file permissions. When I run the script, I get the following output:

[Expert@cpsm1:0]# ./maas_export_tools_wiley-z29uvkfa.sh
Export to Smart-1 Cloud is supported from Security Management Server only.

I have already successfully migrated the SMS database to a Smart 1 cloud tenant. In this case, I split out 3 gateways managed by the SMS, and now manage them from a Smart 1 cloud tenant.

I want to migrate the remaining gateways into another tenant. Is having already done a migration of the same database to another tenant causing issues with the next migration?

Any assistance would be greatly appreciated. I have a case open with Diamond support, but looking for info on all avenues.

Thanks,

Dave Moore

[_Val_]

It should not be an issue to migrate the same DB more than once. Please work with TAC to resolve this.

[dmoore19975]

Thanks Val, appreciate the response. TAC is trying to replicate the issue in their lab. They came back and said that HA should be disabled to run the script. Our environment is a primary and secondary SMS, but not an MDS. Odd thing is, I ran the script the first time with the same HA configuration in place, so, it does not make sense that I would need to disable HA this time.

[the_rock]

I agree 100%, it makes no sense to me either. I never personally did it from management HA, just regular single mgmt, but yea, I get what you are saying.

Andy

[TomerLev]

Hi Dave

Currently Stand Alone migration to Smart-1 Cloud should go through an intermediate phase of manual migration to SMC with TAC and then migrate with the tool to S1C (will be changed soon to be fully tool based).   It is not clear (at least to me) what is the exact layout of the migration(s) you already did and trying to reproduce, you are more then welcome to contact me privately with the ticket ID and more details in order to clarify a resolution.
Thanks
Tomer