Reconfiguring Hostname / Routername

Follow these steps to reconfigure the hostname / routername for both appliances in a High Availability (HA) pair where primary and backup in the prompt represent the primary and backup brokers, respectively in the HA pair configuration.

Go into configuration and then shutdown Config-Sync on both the primary and backup brokers:

primary> enable
primary# configure
primary(configure)# config-sync shutdown

backup> enable
backup# configure
backup(configure)# config-sync shutdown

Shutdown the msg-backbone service. Note that after you confirm the command (enter y), all clients are disconnected.

primary(configure)# service msg-backbone shutdown
All clients will be disconnected.
Do you want to continue (y/n)? y

backup(configure)# service msg-backbone shutdown
All clients will be disconnected.
Do you want to continue (y/n)? y

Shutdown redundancy on both nodes by running these commands:

primary(configure)# redundancy shutdown

backup(configure)# redundancy shutdown

Reconfigure the redundancy mate-router-name running these commands, where <new-primary-hostname> and <new-backup-hostname> represent new hostnames/routernames. In each case below, ensure that the mate router is the other hostname.
```
primary(configure)# redundancy
primary(configure/redundancy)# mate-router-name <new-backup-hostname>
```
```
backup(configure)# redundancy
backup(configure/redundancy)# mate-router-name <new-primary-hostname>
```

Configure the new hostname for the primary and backup brokers. Note that it can take up to 15 minutes for the brokers to reload.

primary(configure/redundancy)# exit
primary(configure)# hostname <new-primary-hostname>
This command causes a reload of the system.
Do you want to continue (y/n)?y

backup(configure/redundancy)# exit
backup(configure)# hostname <new-backup-hostname>
This command causes a reload of the system.
Do you want to continue (y/n)?y

After the brokers come up, re-login to your brokers and re-enable redundancy.

primary> enable
primary# configure
primary(configure)# redundancy
primary(configure/redundancy)# no shutdown

backup> enable
backup# configure
primary(configure)# redundancy
backup(configure/redundancy)# no shutdown

(Optional) Reconfigure any affected configuration settings.

This typically is done on any brokers other than the renamed brokers in the configuration (i.e., not the primary for backup brokers). For this reason, the hostname in the example is solace rather than primary or backup.

Reconfigure an MNR neighbor where <old_name> is the hostname you changed from and <new_name> is the new hostname you changed your broker to.

solace> enable
solace# configure
solace(configure)# routing
solace(configure/routing)# cspf
solace(configure/routing/cspf)# no neighbor <old_name>
solace(configure/routing/cspf)# create neighbor <new_name>
solace(configure/routing/cspf)# exit

Reconfigure a bridge using the routername to connect:

solace# configure
solace(configure)# bridge bridge message-vpn <vpn_name>
solace(configure/bridge)# remote message-vpn bridge router v:<old_name>
solace(configure/bridge/remote/message-vpn)# shutdown
solace(configure/bridge/remote/message-vpn)# exit
solace(configure/bridge/remote)# exit
solace(configure/bridge)# no remote message-vpn default router v:<old_name>
solace(configure/bridge)# create remote message-vpn default router v:<new_name>

Then, back on the primary and backup brokers, re-enable the msg-backbone service.

solace> enable

solace# configure
primary(configure)# no service msg-backbone shutdown

solace> enable

solace# configure
backup(configure)# no service msg-backbone shutdown

Re-enable Config-Sync on the primary and backup brokers.

primary(configure)# config-sync
primary(configure/config-sync)# no shutdown

backup(configure)# config-sync
backup(configure/config-sync)# no shutdown

Run the show config-sync command to check that Config-Sync is up on both the primary and backup brokers. You can also run the show config-sync database command to see the individual table statuses on each broker. Config-Sync is up when the Oper Status shows up and all Message VPNs show the Oper status as up.

On the primary broker:

primary> show config-sync

    Admin Status                      : Enabled
    Oper Status                       : Up
    SSL Enabled                       : No
    Authentication
    Client Certificate
    Maximum Chain Depth           : 3
    Validate Certificate Dates    : Enabled
    Server Certificate Configured : Yes
    Client-Profile
    TCP
    MSS                           : 1460
    Initial Window                : 2
    Maximum Window                : 256   KB
    Keepalive
    Count                       : 5
    Idle                        : 3     seconds
    Interval                    : 1     seconds
    Client
    Name                            : #config-sync/primary
    Connection State                : Connected
    Last Fail Reason                :
    Synchronize
    Username                        : Yes
    
primary> show config-sync database
    
    Legend:
    O - Ownership (L=Leader, F=Follower)
    S - Status (I=In-Sync, R=Reconciling, B=Blocked, O=Out-Of-Sync, D=Down,
    U=Unknown)
    
    Type   Name                             O S Time In State
    ------ -------------------------------- - - ------------------
    Router site                             L I 1d 20h 53m 21s
    Vpn    default                          L I 1d 20h 53m 28s

primary>

While on the backup broker:

backup> show config-sync

    Admin Status                      : Enabled
    Oper Status                       : Up
    SSL Enabled                       : No
    Authentication
    Client Certificate
    Maximum Chain Depth           : 3
    Validate Certificate Dates    : Enabled
    Server Certificate Configured : Yes
    Client-Profile
    TCP
    MSS                           : 1460
    Initial Window                : 2
    Maximum Window                : 256   KB
    Keepalive
    Count                       : 5
    Idle                        : 3     seconds
    Interval                    : 1     seconds
    Client
    Name                            : #config-sync/backup
    Connection State                : Connected
    Last Fail Reason                :
    Synchronize
    Username                        : Yes

backup> show config-sync database

    Legend:
    O - Ownership (L=Leader, F=Follower)
    S - Status (I=In-Sync, R=Reconciling, B=Blocked, O=Out-Of-Sync, D=Down,
    U=Unknown)

    Type   Name                             O S Time In State
    ------ -------------------------------- - - ------------------
    Router site                             L I 1d 20h 54m 18s
    Vpn    default                          L I 1d 20h 54m 25s

backup>

If Config-Sync is up, then you are done; otherwise if Config-Sync is down, run the following commands on the active broker . For illustrative purposes, the primary broker is the broker with the operational status of active in this case.

primary> enable
primary# admin
primary#(admin)# config-sync
primary#(admin/config-sync)# assert-leader router
primary#(admin/config-sync)# assert-leader message-vpn *

Provide feedback