topic Re: CLI Rename Command Syntax - Rename GlobalProtect Gateway in General Topics

CLI Rename Command Syntax - Rename GlobalProtect Gateway

mbrown-revitycu — Thu, 18 Jan 2024 20:33:22 GMT

Totally new to Palo Alto here. I'm looking to rename an existing GlobalProtect gateway on our PA-450.

I have found some posts indicating that this can be done from the CLI of the firewall by using the "rename" command from CLI to update the "GATEWAY" name and the "GATEWAY-N" name on the firewall.

I can see these entries in the config after exporting it to XML.

<global-protect-gateway>
<entry name="GP-GATEWAY">
<roles>

What I can't really find is any concrete documentation on what the proper syntax is to update these.

If I'm parsing the CLI correctly by stepping through commands with "?" it looks like I should at least for one of the entries, use this:

rename global-protect global-protect-gateway GP-GATEWAY to NEWNAME

Is this correct? If so, which of the entries does this change, and how do I change the other?

Thanks!

Re: CLI Rename Command Syntax - Rename GlobalProtect Gateway

JayGolf — Fri, 19 Jan 2024 22:50:17 GMT

Hi @mbrown-revitycu ,

You can rename your gateway by the following command:

rename global-protect global-protect-gateway nameofyourgateway to newgatewayname

The syntax allows you to specify which gateway you would like to replace by entering the name of that gateway. Also, once you've entered your new gateway name you can hit enter.

Hope this helps!

Re: CLI Rename Command Syntax - Rename GlobalProtect Gateway

BPry — Fri, 19 Jan 2024 23:11:26 GMT

@mbrown-revitycu,

The rename command will simply rename the existing entry to whatever you have specified, so say for example that I created a "Test" GlobalProtect-Gateway alongside a "Test" GlobalProtect-Portal entry I could rename them to Test-Gateway and Test-Portal by issuing the following:

rename global-protect global-protect-portal Test to Test-Portal rename global-protect global-protect-gateway Test to Test-Gateway

You can verify that everything is okay from a configuration aspect by running a validation once you've done the rename, but simply renaming those entries won't cause any configuration issues.