Network interfaces
The following table lists the network interfaces present on the custom VMs.
|
The various IP addresses for the interfaces must each be on a separate subnet. In addition, each cluster of VMs must share a subnet for each applicable traffic type (e.g. all signaling addresses for the custom VMs must be on the same subnet). The recommended configuration is to use one subnet per traffic type. If your deployment has multiple sites then use one subnet per traffic type per site. |
| Interface | Description | Examples of use |
|---|---|---|
Management |
Used for managing the node. |
|
Signaling |
Used for signaling messages. |
|
Secondary signaling |
This is an optional interface used for SCTP multihoming. You only need to specify the configuration for this interface if you plan to use SCTP multihoming. |
|
Cluster |
Used by Rhino to do cluster operations. |
|
Please note the cluster interface is only used when Rhino is configured to be clustered on this VM.
The Secondary signaling interface
The custom VM supports an optional second signaling interface, known as the Secondary signaling interface, which can be used for whatever purposes suit your application. To enable this interface, specify configuration for the Secondary signaling network interface when creating the VM - either in the SDF if you are deploying the VM using the SIMPL VM, or in the bootstrap parameters if deploying manually.
Other Metaswitch products use the Secondary signaling interface for SCTP multihoming (redundant SCTP connections). However, your product’s Resource Adaptors may use this interface for a different purpose, such as reserving this interface for a particular type of signaling traffic.
