Create and Deploy on VMware®

You can deploy Oracle Communications Session Delivery products on ESXI hypervisors running VMware 6. For general deployment tasks, from hardware installation to VM resource management, see the VMware documentation.

Before You Begin:

  • Confirm that the VMware version 6 Hypervisor is installed on an appropriate network server.
  • Confirm that the server has 40GB of space for this installation.

Note:

The following procedure describes a typical deployment. The system may display different screens, depending on the deployment.

Detail on Oracle Communications Session Delivery product-specific setup steps is shown below.

  1. From the VMWare ESXi Host page, click Create/Register VM.
  2. On the Select Creation Type screen, select Deploy a virtual machine from an OVF or OVA file and click Next.
  3. On the Select OVF and VMDK Files screen:
    1. Enter a name for the virtual machine.
    2. Browse to a target .ova file.
    3. Click Next.
  4. On the Select Storage screen, click Next.
  5. On the License Agreements screen, click I agree and click Next.
  6. On the Deployment Options screen:
    1. Map the networks used in this template to networks in your inventory.
      The SBC enumerates and binds network interfaces in the order presented by the hypervisor to the virtual machine. If 3 or less interfaces are presented, the bind order is wancom0, s0p0, s1p0. If more than 3 interfaces are presented, the bind order is:
      1. wancom0
      2. wancom1
      3. wancom2
      4. spare
      5. s0p0
      6. s1p0
      7. s0p1
      8. s1p1
      If your hypervisor randomly allocates addresses for network interfaces, the interface order at the hypervisor does not necessarily match that of the SBC. You can use the interface-mapping show command to determine the MAC address to interface order, and if necessary, adjust it using the interface-mapping swap command.

      By default, all interfaces use the recommended VmxNet3 driver.

    2. For Disk provisioning, select Thin or Thick.
    3. Leave the box checked to power on automatically.
    4. Click Next.
  7. On the Additional Settings screen:
    1. Click Bootloader parameters to expand the settings.
    2. Enter the desired boot parameters.

      Note:

      With S-CZ8.4.0p3 or later, you can enter the SHA1 hash of the password for each account (user, admin, and li-admin) into its respective field.
    3. Click Next.
  8. On the Ready to Complete screen, review the selections, make edits if necessary, and click Finish.

trap-receiver

The trap-receiver element defines the NMSs to which the Oracle Communications Session Border Controller sends SNMP traps for event reporting.

Note:

The trap-receiver element is not used if the session delivery SNMP agent operates in SNMPv3 mode.

Parameters

ip-address
Enter the IP address and port for an NMS. If no port value is specified, the Oracle Communications Session Border Controller uses a default port of 162. This required field must follow the IPv4 or IPv6 address format.
filter-level
Set the filter level for the NMS identified within this trap-receiver element
  • Default: critical
  • Values:
    • All—All alarms, syslogs, and other traps will be trapped out. That is, the corresponding NMS will receive informational, warning, and error events.
    • Minor—All syslogs generated with a severity level greater than or equal to MINOR and all alarms generated with a severity level greater than or equal to MINOR will be trapped out
    • Major—All syslogs generated with a severity level greater than or equal to MAJOR and all alarms generated with a severity level greater than or equal to MAJOR will be trapped out
    • Critical—Syslogs generated with a severity level greater than or equal to CRITICAL and all alarms generated with a severity level greater than or equal to CRITICAL will be trapped out
community-name
Enter the name of the community to which a particular NMS belongs. This required entry must follow the Name format. The community-name field values must be unique. The community-name must be 1-32 characters long and must not contain "'"
user-list
This parameter is configured with the name of one or more snmp-user-entry configuration element user-names for authorizing access to SNMPv3 functionality.

Path

trap-receiver is an element under the system path. The full path from the topmost ACLI prompt is: configure terminal , and then system , and then trap-receiver.

Note:

This is a multiple instance configuration element.