In this section:

Verify the VM resources are configured based on the recommendations in

Adjusting Resource Allocations for VM
page before continuing.

Redirecting ISO File

Adjust the resource by executing the following steps:

  1. Click your VM name. Click Resource Allocation tab. Click Edit in the CPU box.

    Selecting Resource Allocations

  2. Click Hardware tab. Click CD/DVD drive 1. Click the radio button for Datastore ISO File.

    Datastore ISO File

  3. Click Browse... Select the ISO image software file. For example, the ISO file name is sbc-V05.00.00R000-connexip-os_03.00.00-R000_amd64.iso. Click OK.

    Browse Datastore

  4. Check the box to Connect at power on. Verify the ISO file is listed in the Datastore ISO File.

    Verifying the ISO File

Install SBC SWe OS

Perform the following steps to install the ConnexIP operating system:

  1. Select VM Name. Click Power>Power On. This is required to power on the virtual machine with the ISO image.

    Connecting at Power On

  2. The Connex IP OS Window Appears. Select Install option and click Enter.

    Installing OS



  3. Select the required keyboard language and click Enter. By default, American English is selected.

    Selecting Language

    The installation takes 10-15 minutes to complete and on completion the VM instance will reboot.

    Intance Reboot

  4. Uncheck the Connect at power on option in CD/DVD Drive device status.

    1. Select Resource Allocation tab and click Edit.

    2. Select CD/DVD drive 1 option.

    3. Uncheck the Connect at power on option in Device status frame and click OK.

      Unchecking Connect at Power On Status



  5. On instance restart you are prompted to login to ConnexIP. You must first login as linuxadmin with sonus as the password.

    ConnexIP Login Screen



  6. Enter the following command to login as root user with password as sonus1.

     su - root

    Root Login

  7. System prompts for Primary Management IP address, network mask and gateway IP address. If you want to set IPv6 address, click y and provide IPv6 address otherwise click n to continue.

    The IPv6 address for management can be configured only in this step.

    Caution
    Make sure you enter exact primary management IP, network mask and gateway details. If it is entered wrongly, you have to re-install the OS again.


    Following is the example screen:

    Configuring Primary Management, Netmask and Gateway

Verify Logical Interfaces Mapping using MAC Address

You can verify the configured logical interfaces (management interface, HA interface and packet interfaces) are exactly matching with the MAC address. 

  1. Get the mapping MAC address in console by executing the following command:

    ifconfig -a


    To get the specific interface MAC address for example management interface, execute the following command:

    ifconfig mgt0

    Noting MAC Address



  2. Note down the mapping MAC address for each interface.  For example, in the above screen, the MAC address for mgt0 is 00:0c:29:c7:5d:ca.

  3. Select the VM and click Resource Allocation tab and click Edit. The Virtual Machine Properties dialog displays. Select the Network interface and verify the MAC address is mapped exactly to the created network interface. Following example screen shows management interface and its MAC address:

    Checking MAC address with Logical Interfaces

    Do not uncheck the Connected and Connect at power on check boxes under Device Status. This must be in power on state always.



  4. Similarly you can check for other interfaces like HA, PKT0, PKT1.

    If you have more network interfaces configured for NIC Teaming, you can verify the mapped network interfaces and corresponding MAC address.

This completes the installation of SBC operating system.

 

Keystroke Errors After OS Installation

If you are using a wide-area or low-bandwidth connection, the time delay over the network may be long enough to cause the virtual machine to start auto-repeat. This can manifest in unintended repeated keystrokes when typing in a remote console. If you experience this issue, refer to the VMware Knowledge Base for a solution.

 

  • No labels