Moving Message VPN Configurations Between Event Brokers

General Steps

To move an individual Message VPN configuration from one Solace PubSub+ event broker to another, follow these steps:

1. On the first event broker, run the show current-config User EXEC command to generate the sequence of CLI configuration commands needed to backup the specified Message VPN, redirecting the command output to a script file (for example, mvpn1.cli).
2. Using a File Transfer user account (refer to Configuring Internal CLI User Accounts for more information), transfer the backup script generated in Step 1 from the first event broker to the second using the copy Privileged EXEC command.
3. On the second event broker:
   1. Run the show current-config User EXEC command, this time with the remove attribute, to generate the sequence of CLI configuration commands needed to remove the specified Message VPN, redirecting the command output to a script file (for example, tmp.cli).
   2. Using the remove script generated above, run the source script User EXEC command to remove the current Message VPN configuration and delete any messages spooled in the Message VPN from the second event broker.
   3. Using the backup script transferred in Step 2, run the source script User EXEC command to restore the Message VPN configuration onto the second event broker.

      Always specify using the source script User EXEC command attributes stop-on-error and no-prompt so that the script stops running on encountering an error, and that the script also ignores yes/no confirmation prompting.

Example

A sample session to move the configuration of Message VPN blue on event broker solace1 to event broker solace2 is:

1. Generate the sequence of CLI commands needed to create the Message VPN blue configuration on solace1 by running the following show current-config User EXEC command, redirecting the command output for creating Message VPN blue to script file blue.cli:

   solace1> show current-config message-vpn blue > cliscripts/blue.cli

   CLI paging is automatically disabled for the duration of a redirected CLI command, but confirmation prompts, error and warning messages are not; they remain displayed on the CLI console.

2. Using a File Transfer user account, transfer the script file from solace1 to solace2 using the copy Privileged EXEC command:

   solace1> enable
   solace1# copy cliscripts/blue.cli sftp://sftp@192.168.128.69/cliscripts

3. Generate the sequence of CLI commands needed to remove the Message VPN blue configuration on solace2 (so that it can be replaced by the configuration from solace1) by running the following show current-config User EXEC command, redirecting the command output for removing Message VPN blue to script file tmp.cli:

   solace2> show current-config message-vpn blue remove > cliscripts/tmp.cli

4. Run the following source script User EXEC command to remove the current Message VPN blue configuration and delete any messages spooled in the Message VPN from solace2 using script file tmp.cli, always specifying that the script stop running on encountering an error and also ignore yes/no confirmation prompting:

   solace2> source script tmp.cli stop-on-error no-prompt

5. Run the following source script User EXEC command to restore the configuration of Message VPN blue from solace1 onto solace2 using script file blue.cli, always specifying that the script stop running on encountering an error and also ignore yes/no confirmation prompting:

   solace2> source script blue.cli stop-on-error no-prompt

For more information on running scripts from Solace CLI refer to Writing and Running Basic CLI Scripts.