Planning for the procedure
Background knowledge
This procedure assumes that:
-
You are installing into an existing VMware deployment which has pre-configured networks and VLANs; this procedure does not cover setting up a VMware deployment from scratch.
-
You know the IP networking information (IP address, subnet mask in CIDR notation, and default gateway) for the ShCM nodes.
Reserve maintenance period
This procedure does not require a maintenance period. However if you are integrating into a live network then it is recommended to implement measures to mitigate any unforeseen events.
Tools and access
This document references an external document: the Commissioning VM Documentation. Ensure you have a copy available before proceeding.
Installation Questions
| Question | More information |
|---|---|
Do you have a list of the IP addresses that you intend to give to each node? |
Each node requires an IP address for each interface. |
Do you have DNS and NTP Server information? |
It is expected that the deployed nodes will integrate with the IMS Core NTP and DNS servers. |
Method of procedure
Write the SDF
The Solution Definition File (SDF) contains all the information required to set up your ShCM cluster. It is therefore crucial to ensure all information in the SDF is correct before beginning the deployment.
Documentation on how to write an SDF is available in the 'Write an SDF' section of the Commissioning VM Documentation.
The format of the SDF is common to all Metaswitch products, so information can be reused as necessary.
However, one element only applies to Rhino VoLTE TAS node types: cds-addresses.
This element lists all the Config Data Store addresses.
In almost all circumstances, this should be set to all the signaling IPs of the TSN nodes in the deployment.
It is recommended to start from a template SDF and edit it as desired instead of writing an SDF from scratch. An example SDF is included in the CSAR, or can be found here.
