Versions Compared

Old Version 7

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 8

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top
top

Add_workflow_for_techpubs
AUTH1
JIRAIDAUTHSYM-23012
REV5
REV6
REV3
REV1

Excerpt Include
UXDOC61:Not_for_SWe
UXDOC61:Not_for_SWe
nopaneltrue
 

Warning
titleREAD BEFORE BEGINNING

You must follow these steps completely and in the order shown. Failure to do so increases the risk of node failure.

...

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction 
1

Login to the WebUI of both each SBC Edge.

 
2

Navigate to Tasks  > Setup Cloud Connector Edition.

 
3

Click the ASM Config tab and configure/verify the Network and IP settings of your ASM as shown below.

 
4

Click Apply. After receiving the activity status as successfully completed, click the Generate CSR tab.

 

Caption
0Figure
1Configuring the ASM – CCE-1

Image Removed

Caption
0Figure
1Configuring the ASM – CCE-2

Image Removed

Generating the CSR

This process is required only if you don't have a public certificate for your deployment. If you already have a certificate, proceed to Import Certificate.

Note

Perform these steps on only one of the

Spacevars
0product
systems.

...

Navigate to Tasks > Setup Cloud Connector Edition > Generate CSR.

From the Remote Desktop Enabled drop down list, select Yes (to enable Remote Desktop) or No (to disable Remote Desktop). 
5From the Windows Firewall Enabled drop down list, select Yes (to enable Windows Firewall) or No (to disable Windows Firewall). 
6From the Proxy Enabled drop down list, Enables use of the Proxy Server on the ASM. Select from the drop down list: Yes (enables Proxy Server on the ASM) or No (disables Proxy Server). 
7From the Proxy Address drop down list, select Yes (to enable the IP address for the Proxy Server in IPv4 format). This field is available only when Proxy Enabled is set to Yes. 
8From the Proxy Port drop down list, select Yes (to enable the port in which the Proxy Server connects). Valid entry: Valid entry: 1 - 65000. This field is available only when Proxy Enabled is set to Yes. 
9Configure/verify the Network and IP settings of your ASM. 
10

Click Apply. After receiving the activity status as successfully completed, click the Generate CSR tab.

 


 

Caption
0Figure
1Configuring the ASM – CCE-1

Image Added

Caption
0Figure
1Configuring the ASM – CCE-2

Image Added

Generating the CSR

This process is required only if you don't have a public certificate for your deployment. If you already have a certificate, proceed to Import Certificate.

Note

Perform these steps on only one of the

...

Generate the CSR as shown below with following information.

...

To ensure creating a valid CSR for Cloud Connector Edition usage, please see the section "Certificate requirements" on https://technet.microsoft.com/en-us/library/mt605227.aspx .

 

Caption
0Figure
1Generate CSR

Image Removed 

Importing Certificate/Keys

Note

Perform these steps on both

Spacevars
0product
systems.

both to Tasks and then click the Import Certificate/Keys tab.
Step Action
1Login to the WebUI of one of the SBC Edge.
2

Navigate

to Tasks > Setup Cloud Connector Edition

 > Generate CSR.

3

On SBC-1, click the Action drop-down list and select the appropriate option:

  • If you generated a Certificate Request (CSR) in the previous section, select the Import X.509 Signed Certificate option using the Choose File button.
  • If you prepare your certificate by yourself, select the Import PKCS12 Certificate and Key option and paste into the Paste Base64 Certificate box.
4Click OK.
5
  • On SBC-1, select the certificate Action, use Export PKCS12 Certificate and Key, enter the password, and then click OK.
  • On SBC-2, select the certificate Action, use Import PKCS12 Certificate and Key to import the pkcs certificate you exported on SBC-1, enter the password, select the relevant certificate file using the Choose File button and then click OK.

 

...

Generate the CSR as shown below with following information.

Note: This example uses aepsite1.sonusms01.com and sip.sonusms01.com as common name and SAN

To ensure creating a valid CSR for Cloud Connector Edition usage, please see the section "Certificate requirements" on https://technet.microsoft.com/en-us/library/mt605227.aspx .

 

Caption
0Figure
1Generate CSR

Image Added
 

Importing Certificate/Keys

Note

Perform these steps on both

Spacevars
0product
systems.

Step Action
1Login to the WebUI of both SBC Edge.
2

Navigate to Tasks > Setup Cloud Connector Edition and then click the Import Certificate/Keys tab.

3

On SBC-1, click the Action drop-down list and select the appropriate option:

  • If you generated a Certificate Request (CSR) in the previous section, select the Import X.509 Signed Certificate option using the Choose File button.
  • If you prepare your certificate by yourself, select the Import PKCS12 Certificate and Key option and paste into the Paste Base64 Certificate box.
4Click OK.
5
  • On SBC-1, select the certificate Action, use Export PKCS12 Certificate and Key, enter the password, and then click OK.
  • On SBC-2, select the certificate Action, use Import PKCS12 Certificate and Key to import the pkcs certificate you exported on SBC-1, enter the password, select the relevant certificate file using the Choose File button and then click OK.

 

Anchor
Configuring the CCE
Configuring the CCE
Configuring the CCE

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of the SBC Edge.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Configure CCE tab.
4

Configure all necessary information and then click OK.

 

Caption
0Figure
1Configuring the ASM – CCE-1

Image Added

 

Caption
0Figure
1Configuring the ASM – CCE-2

Image Added

 

 

Note: Enterthe ASM

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of the SBC Edge.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Configure CCE tab.
4

Configure all necessary information and then click OK.

 

Caption
0Figure
1Configuring the ASM – CCE-1

Image Removed

 

Caption
0Figure
1Configuring the ASM – CCE-2

Image Removed

 

 

 

Note: Enterthe ASM's IP address in the HA Master IP Address field. The Slave uses the same root certification as the Master, and this location contains the shared folder that contains the Root CA of the Master.

5After receiving the activity status as successfully completed, click the Prepare CCE tab to continue.

...

Warning

 If the deployment environment consists of multiple-site with a single certificate, or a wild card certificate, ensure the CCE Site Name and the Edge Server Public Hostname are correct before proceeding.

Verifying and Updating the  the CCE Configuration INI File 

...

Info

When deploying a High Availability (HA) systems, it is important to have Management IP Prefix unique on each HA system. For instance, if your HA Master CCE system has 192.168.213.x as the Management IP Prefix, you need to be sure to configure this attribute differently on HA Slave system. While doing this, also make sure that subnet that you are defining in this field does not conflict in your IP infrastructure.

Note

Perform these steps on both

Spacevars
0product
systems.

Follow these steps to verify and correct values in the  CCE Configuration INI File.

StepAction
1Login to the WebUI of the SBC Edge.
2Click the Configure CCE tab and then click Click to re-configure CCE application.
3Click OK on the popup dialog box.
4

Click the Raw (INI) Config drop-down list, and select an option:

  • Edit. Configurable fields are displayed for editing. Modifications to the CCE configuration requires redeployment of the CCE VM, and this action takes approximately two hours.
  • Export. Exports the .ini file.
  • Import. Imports the .ini file.
5

Verify/correct the values in the CCE Configuration INI File and then click OK.

...

While doing this, also make sure that subnet that you are defining in this field does not conflict in your IP infrastructure.

Note

Perform these steps on both

Spacevars
0product
systems.


Follow these steps to verify and correct values in the  CCE Configuration INI File.

StepAction
1Login to the WebUI of the SBC Edge.
2Click the Configure CCE tab and then click Click to re-configure CCE application.
3Click OK on the popup dialog box.
4

Click the Raw (INI) Config drop-down list, and select an option:

  • Edit. Configurable fields are displayed for editing. Modifications to the CCE configuration requires redeployment of the CCE VM, and this action takes approximately two hours.
  • Export. Exports the .ini file.
  • Import. Imports the .ini file.
5

Verify/correct the values in the CCE Configuration INI File and then click OK.


Preparing the CCE 
Anchor
Preparing the CCE
Preparing the CCE

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of both SBC Edge systems.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Prepare CCE tab.
4

Click the Prepare CCE button. Enter the requested password. A confirmation will request you to enter the password again. The same password should be used on all Appliances in the site. Click OK as shown below.

5

To complete the deployment, continue with  Activating the CCE.

Anchor
Activating
Activating
Customizing the CCE VM

This step stores the two Microsoft product keys, and customizes the CCE VM (which is not yet activated).

...

Note

Perform these steps on both

Spacevars
0product
systems
0product
systems.

Info

Each CCE requires four VMs; each Microsoft Product Key activates two VMs.

StepAction
1Login to the WebUI of both each SBC Edge systems.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Prepare CCE tab.
4

Click the Prepare CCE button. Enter the requested password. A confirmation will request you to enter the password again. The same password should be used on all Appliances in the site. Click OK as shown below.

5

To complete the deployment, continue with  Activating the CCE.

...

.
3Click the Cutomize CCE VMs tab.
4

In Domain Controller and Central Management Store VM > Windows Product Key 1, enter the first Microsoft Product Key. To identify the Product Key, see Identify Microsoft Product Key.

5In Under Mediation Server and Edge Server VM >  Windows Product Key 2, enter the second Microsoft Product Key.To identify the Product Key, see Identify Microsoft Product Key.
6From the Proxy Usage drop down list, select Enabled (enables the Proxy Server on the DMZ facing the internal network) If you select Disable, the Proxy Server is disabled.
7In the Proxy Server IP Address field, enter the server IP address for the Proxy Server in IPv4 format. This field is available only when Proxy Usage is set to Enabled.
8In the Proxy Server Port field, enter the port number for the Proxy Server. Valid entry: 1 - 65535. This field is available only when Proxy Usage is set to Enabled.
9Click Apply.
10

This step stores the Microsoft product keys, and activates the CCE VM (which is not yet activated).

Note

Perform these steps on both

Spacevars
0product
systems.

Info

Each CCE requires four VMs; each Microsoft Product Key activates two VMs.

StepAction
1Login to the WebUI of each SBC Edge.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Activate CCE tab.
4

In Domain Controller and Central Management Store VM > Windows Product Key 1, enter the first Microsoft Product Key. To identify the Product Key, see Identify Microsoft Product Key.

5In Under Mediation Server and Edge Server VM > Windows Product Key 2, enter the second Microsoft Product Key. To identify the Product Key, see Identify Microsoft Product Key.
6Click Activate.
7Access Tasks> Operational Status to verify Windows Activation. If activation fails, see Troubleshooting..
811

To complete the deployment, continue with installing the Installing the CCE Appliance using Sonus Cloud Link Deployer.

 

 

Caption
0Figure
1Activate the CCE

 Image RemovedImage Added

Info
titleIdentify Microsoft Product Key

Anchor
ProductKey
ProductKey
To identify the Microsoft Product Key:

  1. Access the bottom of the SBC unit and locate the two Microsoft Certificate of Authenticity stickers.
  2. Locate the Microsoft Product Key for each.

    Sample Microsoft Certificate of Authenticity Sticker

...