Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1REV5REV6REV3REV1

 

Noprint

Back to Table of Contents

This section provides information on installing and running SBC SWe Lite on VMware EXSi.

Warning

SBC SWe Lite is a closed network device. Customer modifications at the Linux level are not allowed or supported. These modifications can cause stability, update and fail-over issues.

Customers should only configure SBC SWe Lite using the supported interfaces (CLI, REST, EMA, and EMS).

Panel
borderColorgreen
bgColortransparent
borderWidth2

Additional sections:

Children Display
styleh6

 

 

 

VMware ESXi Getting Started link:

AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb41059c, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHCHOR-3017
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9d6032b, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a0c86062358001607df6f45d0013, userName='null'}


Panel

Contents:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:

compatibility guide


Note

SWe Lite is not supported on Hypervisor platform VMWARE ESXi5.5 running on Dell PowerEdge 740 hardware.


Info

SWe Lite supports the following (depending on your license):

  • For Memory (RAM), valid settings are 1 GiB (1024 MiB), 1.5 GiB (1536 MiB), or 2.5 GiB (2560 MiB).
  • For vCPUs, valid settings are 1, 2, 4 or 10 vCPUs.

For detailed information, refer to SBC SWe Lite Hardware and Software Requirements.

For adding vCPUs or increasing memory on a SWe Lite upgraded to Release 8.0, refer to Adding vCPU and Increasing Memory/VM Size.


Multiexcerpt
MultiExcerptNameVMware

This section provides information on installing and running

Spacevars
0series3
on VMware ESXi.

Prerequisites

Perform the steps in Downloading the SBC SWe Lite Package before performing this procedure.

 

Install SBC SWe Lite on the ESXi Server

Note
iconfalse
titleNote

Screen captures on this page show fields and values that represent a typical installation. When prompted, use values and responses appropriate for your location. 


Warning
iconfalse
titleWarning

Spacevars
0series3
is a closed network device. Customer modifications at the Linux level are not allowed or supported. These modifications can cause stability, update and fail-over issues.

Customers should only configure

Spacevars
0series3
using the supported interfaces (WebUI, CLI, REST).


Note
titleSBC SWe Lite Operations in an ESXi Cluster are Supported, with Restrictions


The SBC SWe Lite supports operations within an ESXi host under the control of a vCenter Server (centralized management utility for VMware) provided the operations and features invoked on the ESXi host by the vCenter Server match those invoked by the ESXi host console when running outside the control of the vCenter Server.

Refer to the following guidelines and restrictions:

  1. Select operations on the ESXi host initiated by the vCenter Server (such as those not available with the ESXi host console when running in standalone mode) may result in a disruption of SBC SWe Lite operations. Examples of popular vCenter Server-initiated operations that are not supported by the SBC SWe Lite include vMotion and Fault Tolerance.
  2. If unsupported vCenter Server-initiated operations result in a disruption of the SBC SWe Lite, a new unprovisioned (blank) and unlicensed SBC SWe Lite may need to instantiated to replace the original SBC SWe Lite instance.  Please contact Ribbon TAC to initiate a licence re-issuance.
  1. Use VMware vSphere Client to connect to the ESXi server.
  2. Enter the ESXi server IP address into a browser address bar to login.

  3. After logging on to the ESXi server, select Deploy OVF Template from the File drop-down list.

  4. Select the location of the OVF package, and then click Next.

    Caption
    0Figure
    1OVF Template Location
    3OVF Template Location
    Image Added


  5. When the OVF Template Details pane opens, make note of the information listed and then click Next.

    Caption
    0Figure
    1OVF Template Details
    3OVF Template Details

    Image Added


  6. When the Name and Location pane opens, rename the 

    Spacevars
    0series3
     instance to make it unique in the inventory folder, and then click Next.

    Caption
    0Figure
    1Rename the File
    3Rename the File

    Image Added


  7. Select the Resource Pool to deploy the template, and then click Next.

    Caption
    0Figure
    1Select Resource Pool
    3Select Resource Pool

    Image Added


  8. Ensure that the Thick Provision Lazy Zeroed option is selected in the Disk Format dialog box, and then click Next.

    Caption
    0Figure
    1Disk Format
    3Disk Format

    Image Added


  9. Review the Network Mapping dialog box. If necessary, select a different media port network interface from the Destination Networks drop-down list, and then click Next.

    Caption
    0Figure
    1Network Mapping
    3Network Mapping

    Image Added


  10. Make note of the deployment settings, and then click Finish to start the deployment task.

    Caption
    0Figure
    1Ready to Complete
    3Ready to Complete

    Image Added


Info

Ribbon recommends that all customers review and, if necessary, optimize their Network Interface configurations before proceeding. Failure to do so could lead to interface mapping issues. See Mapping Network Interfaces and then return to this section.

Edit the Virtual Machine Settings

  1. Select the newly-created 

    Spacevars
    0series3
     from the list in the left pane.

  2. Select the Edit virtual machine settings link on the Getting Started tab.
Note
iconfalse
titleNote

The default

Spacevars
0series3
comes with 1 GiB memory, one CPU and five network interfaces.  

Configuring Virtual Network Adapters

  1. Select Network adapter 1 from the Hardware tab of Virtual Machine Properties.
  2. In MAC Address section of the right window pane, select Manual.

    Note
    iconfalse
    titleNote

    You must assign the MAC address manually. Do not accept the automatic default.
    The MAC address field is populated with the first three octets.


  3. Finish configuring the static MAC address provided by your Network IT Administrator.

  4. Repeat for the remaining four Network adapters (2 -5).

    Caption
    0Figure
    1Configure Network Adapter 1


    Image Added


  5. Configure at least two network interfaces for the appropriate network.

  6. Click OK to save and then exit the Settings window.

  7. Power on the 

    Spacevars
    0series3
     by selecting Power on the virtual machine link on the Getting Started tab.

    Caption
    0Figure
    1Power on Virtual Machine
    3Power on Virtual Machine

    Image Added


  8. Click the Console tab.


Complete Initial Setup

Proceed to SBC SWe Lite Initial Setup. After setup is complete, proceed to License Installation.

License Installation

Trial License Installation

If you are installing an SBC SWe Lite for a trial or demonstration deployment, proceed to Obtaining and Installing a Permanent SWe Lite Trial License.

Production License Installation

If you are installing an SBC SWe Lite instance to carry live enterprise traffic, proceed to Obtaining and Installing a SWe Lite License.


Pagebreak

 

Download and Install vSphere

If you need to access the ESXi server remotely, you need to download and install vSphere Client in your desktop. 
To download the vSphere, use Web browser to access the link  (https://sbc3kv-esxi.e.sonusnet.com/ or https://10.56.113.178 )
Image Removed

Login to the ESXi Server

After running the installer, start the vSphere client; use your sonus user credential to login to the ESXi Server

Image Removed

 

Reserve IP Addresses

Before you create your SBC SWeLite, you need to reserve two static IP addresses for your SBC SWeLite. One for management port, and the other one for media port.

The managemet port is on the 10.56.230.x subnet and the media port is on the 10.56.227.x subnet; the x is between 100-254;

You can use this link to reserve your IP addresses: Fremont Resource Management

Install SBC SWeLite on the ESXi Server

Once you log in to the ESXi server, you can install the SBC SWeLite OVA file to create your own SBC SWeLites;

The latest SBC SWeLite plateform build is alpha build 12 and located at this link \\192.168.2.230\Software\VSBC-Platform-Releases\ESXi\SBC3000v6.1.0.Alpha.B12.ova

Click the File on the  top of the menu, in the pull down menu, select Deploy OVF Template, it will pop up an deploy window.

place the SBC SWeLite build link or ova files to the source window

The build link example:

(\\192.168.2.230\Software\VSBC-Platform-Releases\ESXi\SBC3000v6.1.0.Alpha.B12.ova)

(\\fmt-automation.e.sonusnet.com\builds\Chorus\Test\FLUTE\FLUTE build 40\esxi\SBCSWeLite-release-6.1.0.build40\esxi\SBCSWeLite-release-6.1.0.build40.ova)

 

Image Removed

 

Image Removed

Hit next and next go to the Name and Location template, you should change the name of the SBC SWeLite. The reason is we sharing this ESXi server, ever one can see all the other person's SBC SWeLites. To avoid accidental duplicate or delete other person's SBC SWeLite. I suggest use this format: SBCSWeLitename.buildnumber_yourName_IPaddressLastNumber. For example SBCSWeLite.B12_nanyi_100; or SBC3000.B12_nanyi_100; which means I will use IP address 10.56.230.100 as management port, and IP address 10.56.227.100 as media port.

Image Removed

 

Hit next go to Disk format

Image Removed

 

Hit next goto Network Mapping

To change the media port network interface; select the network interface on the pull down menu from the Destination Networks:

Hit next will go to Ready to Complete page, and Hit finish you create your SBC SWeLite !!

 

Edit the Virtual Machine Settings

 The default SBC SWeLite comes with 512MB memory, 1 CPU and Five Network interfaces. You need to gather the MAC address information for each interface to further configure the SBC SWeLite interfaces from the console; therefore, you must edit he virtual machine setting by click the SBC SWeLite you created; on the Getting started tab, click the link Edit virtual machine settings

Image Removed

 

Change the Memory setting

Change the memory setting by click the memory and change the memory size to 1G

Image Removed 

 

Map the Interface to the Network Using the Network Interface MAC Address

To gather the network interface Mac address and map the interface to desired network, you need to at least power on once of the virtual machine, then power off the virtual machine to generate Mac address on each interface (refer to next session for power on virtual machine) click each of the network adapters and write down the Mac address and network mappings, later configuration need those information to further configure the network interfaces from the console.

Image Removed

Power-On the Virtual Machine

To start your SBC SWeLite, you need to power on the virtual machine by click the "Power on the virtual machine" link from the Getting started tab. 

 

Image Removed

 

Access the Console

In order to further configure the virtual machine, you need the console access. To access the console,  you need to click the console tab or from the Summary tab click the Open Console link.

Image Removed

 

Network Interface Configuration

 To access the SBC SWeLite virtual machine, you need to further configure the network interfaces from the virtual machine console.

Login as User netconfig

Log in as user 'netconfig' with password 'config'. This automatically runs the interface mapping shell script. Then the console will ask user to change the netconfig password. The password need to be at least 6 characters with upper, lower, number or other characters combination.

Image Removed

 

 Configure the Interface Name and Map the MAC Address

The interface mapping shell script will ask user to provide interface name to map the interface showing from the WebUI. in order to correctly map the interface you need to use the mac address gathered from above virtual machine editing session. To activate the interface you need to specify the name and Mac address mapping. If you just hit enter, the interface will not specified and it will not showing on the WebUI.

For example:  

Image Removed

 After apply the configuration change in the first time, the system will be rebooted by itself.

Obtain the Admin Port IP Address

 

The admin port should be connected to a network that the DHCP server enabled. If the network mapping and the connection is correct, the admin IP address should be showing on the console port. Otherwise, you need to check you connection and mappings.

 

Image Removed

 

Login as User root From the Console

if you need to access the root of the console before the WebUI initial setup, you can login to root with default password chorus

After the WebUI initial setup, if you need to access root from the console you need to enable the ssh access following this link (SBC 1k/2k troubleshooting)

Image Removed

 

 

 

 

 

Complete the Initial Setup

From your web browser access the initial admin IP address of your SBC SWeLite, it will bring up the SBC SWeLite initial setup page.

 Image Removed

Complete the intial setup and configured the static Admin IP address and all the interfaces IP address. You need to powered cycle the virtual machine. After the virtual machine comes on line. your SBC SWeLite is ready to use!