Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Follow the same steps as above to commission the Secondary SBC Server.

First Time LogIn

License

Configure Network Settings 

...

NOTE: It is required to use a direct connection between servers for the dedicated interface. This interface needs to be on the same port for both machines, and needs to be connected before copying the configuration to the Secondary server.  For example: If you use Eth4 on the Primary Server, use Eth4 on the Secondary Server.

 

...

Configure Default Gateway and DNS Servers

Configure Media Interfaces

Detect Modules

Configure Placeholder SIP Profile

Apply the Configuration

Registering the Secondary SBC Server

...

A prompt asking to create a configuration backup will appear. Click Ok to create the backup.

Image RemovedImage Added

Once the backup is successful, another prompt will appear to generate the access key. Click Ok to generate the access key.

Image RemovedImage Added

  • Copy the encoded Access Key text from the text box into Clipboard or Notepad or TextEditor

Image RemovedImage Added

 

Adding a Peer on the Primary Server

...

A prompt asking to create a configuration backup will appear. Click Create to create the backup.

Image RemovedImage Added

Once the backup is successful, another prompt will appear to copy the access key generated by the Secondary Server. Write a meaningful name
that best describes the Secondary Server as the other node and then paste the encoded Access Key text obtained from the Secondary Server.

Image RemovedImage Added

 

The system will be registered locally and show on the Peer nodes list - its configuration can be viewed or modified by clicking Modify on the right side of the row.

...

For instance,  if eth4 is used as a Dedicated Network / Interface and is also a direct cable connection between the Primary and Secondary servers then it must be removed from the Failover triggers table. If the Failover triggers  is not removed, in the instance when the Slave Node goes down due to a reboot for instance, it will cause the Master node to temporarily lost NSC service until the Slave node's Cluster service is started.

Image RemovedImage Added

Floating IP Assignment in SIP Profiles on Primary SBC Server

...

Configuration | Signaling | SIP Profiles

Image RemovedImage Added

Create SIP Profile

...

There may be many SIP Profiles with each there own unique Floating IP Address.

Image RemovedImage Added

 

You may Apply the Configuration as this point, knowing that there is plenty of configuration remaining to correct operation.

...

Clicking on Copy configuration to Peer button will start copying the configuration from the Primary to the Secondary server, where all configuration will be copied over, including all the user interface settings and service startup information.  This process may take a few minutes, please be patient.

Image RemovedImage Added

After both servers are configured and the configuration has been copied over, the cluster is now fully configured and ready to start operation.

...

Clicking on Start All Nodes button will start the process joining the HA.  When complete, there will be a Master Node and a Slave Node.  The Master Node is the SBC unit that is actively processing calls, whereas the Slave Node is monitoring the Master Node.

...

Image RemovedImage Added

After pressing Start All Nodes, the required Application Services are started.  Services managed directly by the cluster are called Cluster Resources, and will be shown on the Control Panel as soon as the cluster services are initialized.

...

  1. Stop both the nodes before modifying hostname.

  2. Update the host name and Apply configuration.

  3. Important to copy the configuration to Peer before restarting.

    Image RemovedImage Added
  4. Restart the system.

...