topic Re: Invalid FQDN Object on import in Expedition Discussions

Invalid FQDN Object on import

dschlosser1 — Mon, 20 May 2019 15:31:43 GMT

When importing panorama we have two fqdn address objects that are detected as invalid:

EXT-SaS-Monitoring_02ws.centrastage.net fqdn 02ws.centrastage.net

EXT-SaS-Monitoring_02cc.centrastage.net fqdn 02cc.centrastage.net

All objects with a number as the first character of the fqdn are detected as "invalid" objects.

Unable to use auto update features of Expedition because we have to change these two objects in order for them to be considered valid objects by the Expedition tool.

Is there a work around or updated that corrects this issue?

Re: Invalid FQDN Object on import

sjanita — Mon, 20 May 2019 19:51:18 GMT

I will report this issue to be reviewed.

Re: Invalid FQDN Object on import

sjanita — Tue, 21 May 2019 00:14:59 GMT

FYi, you can move forward and generate the XML with the objects as is. The marking of the object as invalid is used as an alert for the admin to review and correct the flagged objects. If you do not make changes to those objects Expedition will retain their configuration and add them to the generated XML and also the API output.