Page History

This section explains the prerequisites and the configurations to be done on the SBC SWe cluster and PSX Manager so that the SBC cluster has the view of the PSX cluster and the PSX has the view of the SBC cluster. To configure SBC SWe clusters as gateways in the PSX SWe Manager, refer to "Configuring SBC Cluster ID as Gateway" in the PSX documentation.  

Prerequisites

• EMS instance is up and running
• PSX Master instance is up and running

The PSX instances within a cluster must be visible to the instances within the SBC SWe cluster.  Registering the PSX cluster FQDN in the Remote Policy Server, instead of the IP address, allows the SBC SWe to have a view of the PSX instances within the cluster. When a new instance is created, it will query the PSX using the FQDN.

Access the SBC Configuration Manager

Disable the PSX Local Server

1. Navigate: All > System > Policy Server > Local Server. Select the PSX_LOCAL_SERVER.

2. Change the State to Disabled and Mode to Out of Service.

3. Click Save.
   

   Caption
   0 Figure 1 Local Server

Add a Remote Policy Server with the PSX Cluster FQDN

1. Navigate through All > System > Policy Server > Remote Server. The following screen appears:

   Caption
   0 Figure 1 Remote Policy Server

2. Click New Remote Server and add the required values, for example:

   1. Enter the Name as the cluster name (PSX_15).

   2. Enter the FQDN of the PSX Cluster, for example "psx2.sonusnet.com".

   3. Check the radio button for Enabled.

   4. Change the Mode to Standby.

      Caption
      0 Figure 1 Remote Policy Server Values

   5. Click Save.

      Caption
      0 Figure 1 Remote Policy Server List

   6. Create another Remoter Server with the following details:

      1. Name: PSX_14
      2. FQDN: psx1.sonusnet.com (example)
      3. Mode: Active

The PSX Master cluster FQDN is added to the SBC configuration.

Click Save at the top of the SBC Configuration Manager window when you have completed making configuration changes. When prompted, confirm that you want to save all your changes and push the configuration to all nodes in the SBC cluster.