Set Up the pcemigrate Configuration to Access the On-Premises PCE and SaaS
The pcemigrate tool uses a configuration yaml file to be able to access PCEs and perform various operations. You need to add the parameters of the PCE to the configuration file. These include:
A friendly name for the PCE that can be used by the pcemigrate commands to refer to the PCE. For instance, if the PCE FQDN is
mnctestvc26000.testlabs.io, you can use the friendly name mnctestvc26000 for the PCE.FQDN of the PCE, port, org id, proxy server, session token, api key, and so forth.
The following example adds PCE parameters to the configuration key (including API keys) for the on-premises PCE (4x2testvc10000) and SaaS (mnctestvc26000). If the parameters are correct, pcemigrate accesses the PCE and retrieves the version of the software.
> pcemigrate pce-add --name mnctestvc26000 --fqdn mnctestvc26000.testlabs.io --port 8443 --api-user api_139edfdc329357185 --api-key 3bf8b658edb3463e31ae06bb005efb5bae79ccfd095a4c610a29dd998dfe628c --org 655362
> pcemigrate pce-add --name 4x2testvc10000 --fqdn 4x2testvc10000.testlabs.io --port 8443 --api-user api_1410a3158e8739a9c --api-key 8c6b8d3b4ca9bff8d65bc66f8916d0d46b30f16b0bc1d30c96f4bd930e571628 --org 1
> cat pce.yaml
4x2testvc10000:
disabletlschecking: false
fqdn: 4x2testvc10000.testlabs.io
key: 8c6b8d3b4ca9bff8d65bc66f8916d0d46b30f16b0bc1d30c96f4bd930e571628
org: 1
pce_version: 25.2.12-10283
port: 8443
proxy: ""
user: api_1410a3158e8739a9c
userhref: ""
mnctestvc26000:
disabletlschecking: false
fqdn: mnctestvc26000.testlabs.io
key: 3bf8b658edb3463e31ae06bb005efb5bae79ccfd095a4c610a29dd998dfe628c
org: 655362
pce_version: 25.2.12-5
port: 8443
proxy: ""
user: api_139edfdc329357185
userhref: ""
no_prompt: false
output_format: json