|Sonus Documentation Portal|
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.
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.
Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters registered with the EMS.
Click the Configurations tab.
Click Create Candidate Configuration.
Click Load Editor. The SBC Configuration Manager opens where you can make configuration changes. See the EMA User Guide for information on configuring the SBC.
Navigate: All > System > Policy Server > Local Server. Select the PSX_LOCAL_SERVER.
Change the State to Disabled and Mode to Out of Service.
Navigate through All > System > Policy Server > Remote Server. The following screen appears:
Click New Remote Server and add the required values, for example:
Enter the Name as the cluster name (PSX_15).
Enter the FQDN of the PSX Cluster, for example "psx2.sonusnet.com".
Check the radio button for Enabled.
Change the Mode to Standby.
Create another Remoter Server with the following details:
The PSX Master cluster FQDN is added to the SBC configuration.
You can configure either the FQDN or IP address, but not both.
maxPolicyServerCount is the number of IP addresses the SBC selects and registers with from the FQDN resolution result. The default value is 1.
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.