| Include Page |
|---|
| _Not Applicable to SWe N:1 Disclaimer |
|---|
| _Not Applicable to SWe N:1 Disclaimer |
|---|
|
This section describes the installation procedure of the ConnexIP Operating operating system (OS) and the SBC SWe application software. The SBC application is installed using the Platform Manager GUI and it is configured either as a standalone installation or a high availability (HA) installation.
| Note |
|---|
Before installing the OS and Applicationapplication, ensure the ports used by the are not blocked in your network. Refer to SBC Core Network Listener Ports. |
The
may be deployed in either a standalone or redundant
High Availability ( HA
) configuration
as described in this section.
Installing SBC SWe in a Standalone Configuration
The
standalone deployment consists of a single
Virtual Machine virtual machine. Gather the following information before starting the installation process:
| Caption |
|---|
| 0 | Table |
|---|
| 1 | IP Plan - Standalone Configuration |
|---|
|
Input Parameter | Description | Example/Recommendation |
|---|
Primary Management IPv4 Address | This specifies the physical management IPv4 address associated with the primary management network. | 10.11.13.10 | Primary Management Network Mask | This specifies the Netmask netmask of the primary management network. | 255.255.255.0 | Primary Management Gateway IPv4 Address | This specifies the default gateway IPv4 address associated with the primary management network. | 10.11.13.1 | | Primary Management IPv6 Address | This specifies the physical management IPv6 address associated with the primary management network. | fd00:10:6b50:4300::10b | | Primary Management IPv6 Prefix Length (0-128) | This specifies the prefix of the primary management network. | 60 | | Primary Management Gateway IPv6 Address | This specifies the default gateway IPv6 address associated with the primary management network. | fd00:10:6b50:4300::1 | System Name | A unique name of the overall SBC system, limited to alphanumeric characters: A-Z (uppercase), 0-9. The first character must be an uppercase letter (A-Z) System Name is used for billing, external PSX queries (if applicable), and system logs | WFDSBC01 - The first three letters represent the physical location of the system, e.g. Westford = WFD
- The second three letters identify the system type (SBC)
- The last two digits identify the SBC instance
| Local Hostname | The hostname of the local SBC SWe host in the network Typical naming convention is "<system name>a" | WFDSBC01a | Peer Hostname | The hostname name of the peer SBC SWe host in the network
Typical naming convention is "<system name>b" | For a standalone configuration, Peer Hostname hostname is "none".
If you plan to upgrade to an HA configuration in the future, you can save a step by configuring the Peer Hostname hostname now (e.g. WFDSBC01b). Then at a later date, you can simply install the standby peer and connect the HA cable. | Server Role | The role of the SBC SWe instance (Active active or Standbystandby) | In a standalone configuration, the server role is 'Activeactive'. | Active CE IP | IP address assigned to the HA interface of the configured Active active SBC, used in an HA configuration for e.g. synchronization | Not used for in a standalone configuration, use default value (169.254.99.1). | Standby CE IP | IP address assigned to the HA interface of the configured Standby standby SBC, used in an HA configuration for e.g. synchronization | Not used for in a standalone configuration, use default value (169.254.88.1). | HA Interface Mask (Inter CE Prefix) | Netmask of the network in which the Activeactive/Standby standby IPs are configured | Not used for in a standalone configuration, use default value (255.255.0.0). | TIPC NETID | The SBC SWe uses the unique Transparent Inter-process Communication (TIPC) protocol ID to communicate between active and standby VMs. Use the same TIPC network ID (between 1000 and 9999) for both active and standby systems. | Not used for in a standalone configuration, use 1500 (default).
Default
The default value can also be used If you plan to upgrade to an HA configuration in the future. | NTP Server IP | The IP address (supports both v4 and v6) of the NTP server. A NTP source is necessary for correct system operation. | E.g. 10.35.66.34 | NTP Server Time Zone | The time zone of the NTP server location. | E.g. (GMT – 5:00) Eastern-US |
|
The
is packaged in an .iso file which contains both the OS and the SBC
Applicationapplication. The OS is first installed, and then the SBC
Applicationapplication.
To install the OS, follow the steps in Installing the Operating System on VMware . During this procedure, the
management IP address is needed.
To install the SBC Application application in a standalone configuration, follow the steps in Installing SBC Application in Standalone Mode.
Installing SBC SWe in an HA Configuration
The
can also be deployed in a redundant
High Availability ( HA
) configuration with one standby
Virtual Machine virtual machine protecting the active
Virtual Machine virtual machine. The HA configuration shares the data between the systems and protects each other in a 1
-:1 redundancy model.
Gather the following information before starting the installation process:
| Caption |
|---|
| 0 | Table |
|---|
| 1 | IP Plan - HA Configuration |
|---|
|
Input Parameter | Description | Example/Recommendation |
|---|
Active SBC SWe Primary Management IPv4 Address | This specifies the physical management IPv4 address associated with the primary management network. | 10.11.13.10 | Active SBC SWe Primary Management Network Mask | This specifies the Netmask netmask of the primary management network. | 255.255.255.0 | Active SBC SWe Primary Management Default Gateway | This specifies the default gateway IPv4 address associated with the primary management network. | 10.11.13.1 | | Active SBC SWe Primary Management IPv6 Address | This specifies the physical management IPv6 address associated with the primary management network. | fd00:10:6b50:4300::10b | | Active SBC SWe Primary Management IPv6 Prefix Length (0-128) | This specifies the prefix of the primary management network. | 60 | | Active SBC SWe Primary Management Gateway IPv6 Address | This specifies the default gateway IPv6 address associated with the primary management network. | fd00:10:6b50:4300::1 | Standby SBC SWe Primary Management IPv4 Address | This specifies the physical management IPv4 address associated with the primary management network. | 10.11.14.10 | Standby SBC SWe Primary Management Network Mask | This specifies the Netmask netmask of the primary management network. | 255.255.255.0 | Standby SBC SWe Primary Management Default Gateway | This specifies the default gateway IPv4 address associated with the primary management network. | 10.11.14.1 | | Standby SBC SWe Primary Management IPv6 Address | This specifies the physical management IPv6 address associated with the primary management network. | fd00:10:6b50:7500::10b | | Standby SBC SWe Primary Management IPv6 Prefix Length (0-128) | This specifies the prefix of the primary management network. | 60 | | Standby SBC SWe Primary Management Gateway IPv6 Address | This specifies the default gateway IPv6 address associated with the primary management network. | fd00:10:6b50:7500::1 | System Name | System Name is used for billing, external PSX queries (if applicable), and system logs and must be a unique name throughout the SBC system. SBC naming is limited to alphanumeric characters: A-Z (uppercase), 0-9. The first character must be an uppercase letter (A-Z). | WFDSBC01 - The first three letters represent the physical location of the system, e.g. Westford = WFD.
- The second three letters identify the system type (SBC).
- The last two digits identify the SBC instance.
| Local Hostname | The hostname of the local SBC SWe host in the network. Typical naming convention is "<system name>a". | WFDSBC01a | Peer Hostname | The hostname name of the peer SBC SWe host in the network. Typical naming convention is "<system name>b". | WFDSBC01b | Server Role | The role of the SBC SWe instance (Active active or Standbystandby). | 'Activeactive' or 'Standbystandby'. | Active Primary CE IP | IP address assigned to the HA interface of the configured Active active SBC, used in an HA configuration for e.g. synchronization. | 169.254.99.1 NOTE: Active and Standby standby CE IP addresses must be in the same subnet. | Standby Primary CE IP | IP address assigned to the HA interface of the configured Standby standby SBC, used in an HA configuration for e.g. synchronization. | 169.254.88.1 NOTE: Active and Standby standby CE IP addresses must be in the same subnet. | Inter CE Prefix | Netmask of the network in which the Activeactive/Standby standby IPs are configured. | 255.255.0.0 | TIPC NETID | The SBC SWe uses the unique Transparent Inter-process Communication (TIPC) protocol ID to communicate between active and standby VMs. Use the same TIPC network ID for both active and standby systems. | 1500 | NTP Server IP | The IP address (supports both v4 either IPv4 and v6IPv6) of the NTP server. A An NTP source is necessary for correct system operation. | E.g. 10.35.66.34 | NTP Server Time Zone | The time zone of the NTP server location. | E.g. (GMT – 5:00) Eastern-US |
|
The SBC SWe is packaged in an .iso file which contains both the OS and the SBC Applicationapplication. The OS is installed first, and then the SBC application.
The OS and SBC Application application must be installed on both active and standby SBC SWe instances in the following order:
- Install the OS and the SBC Application application on the Activeactive.
- Install the OS and the SBC Application application on the Standbystandby.
To install the operating system, follow the steps in Installing the Operating System on VMware. The
management IP address is needed for this step.
To install the SBC application in an HA configuration, follow the steps in Installing SBC Application in High Availablility Mode.