change the name on a GP portal and gateway

[jdprovine]

Is is possible to rename an repurpose a global protect portal and gateway? I have one named student that is not being used but I want to repurpose the IP's and save myself from rebuilding a new one by just renaming and reusing student portal and gateway  but the name is greyed out

[TranceforLife]

Hi,

Just tested and don't think it is possible for me as well. At least through the GUI 

[jdprovine]

bummer I will probably have to delete and re-create it with a new name

[ansharma]

Hi jprovine,

You can change the name in the configuration xml file.

I followed these steps:

1) Save named configuration snapshot

2) Export the saved file

3) Edit the name in the notepad++

4) Import the configuration snapshot

5) Load this configuration snapshot

6) Commit

Hope this helps.

Regards,

Anurag

[jdprovine]

interesting approach, thanks for the option

[TranceforLife]

XML nice and tweakable, you definitely need this option when doing migration from the different hardware range. 

[TomYoung]

Hi @jdprovine ,

The rename command on the CLI (in configuration mode) will do it.  You will need to rename the Gateway-N in addition to the Portal and Gateway.

Thanks,

Tom

[upelister]

Hello,

If your are using wildcard certificate in portal config you can use multiple fqdn for one portal.

Example: *.acme.com certificate used for portal and gateway certificate profile so you can use;

vpn1.acme.com

vpn2.acme.com

vpnN.acme.com

for the same gateway and portal config.

[AVintha]

You can change Global Protect Portal/Gateway names via CLI.

The steps I followed and worked for me are,

1) Pull the "Show" output from Panorama CLI in set output format.

Example:

panorama> set cli config-output-format set
panorama> configure
Entering configuration mode
[edit]
panorama# show
This will provide Panorama configuration in a "set" format.

2) Next look for the Global Protect Portal/Gateway name you want to modify in the output and replace the "set" with" rename"

Example:

panorama# rename template <template name> config vsys <vsys name> global-protect-portal/global-protect-gateway <old name> to <new name>

Thanks,
Anurag

[gcastro]

This worked.  I'm not seeing any users under "Remote Users" now, though connections work fine.  

[gcastro]

Once I did a commit, Remote Users began showing up.

[TErwineFIATech]

This process worked well for me. One issue I had was the dependency on my tunnel interface. When attempting to commit to the firewall nodes I receive an error that the tunnel interface is already in use. I'm guessing this wouldn't happen without the tunnel functionality enabled on the gateway. I haven't tried updating the tunnel configuration via the same rename commands yet.