Invalid FQDN Object on import

Reply
L0 Member

Invalid FQDN Object on import

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?

 

 

 

Tags (1)
L4 Transporter

Re: Invalid FQDN Object on import

I will report this issue to be reviewed.

L4 Transporter

Re: Invalid FQDN Object on import

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.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!