Creating a VTAP

• Console
• CLI
• API

• 1. Open the navigation menu, select Networking, and then select VTAPs, found in the Network Command Center group.
  2. Click Create VTAP.
  3. Enter the following:
     • Name: A descriptive name for the VTAP. It doesn't have to be unique, and it can't be changed later in the Console (but you can change it with the API).
     • Compartment: Leave as is.
     • VCN: Choose a VCN for the VTAP. The Source and Target options only show resources belonging to the VCN you choose.
     • Source: Select the VTAP's intended source. This source is the interface the VTAP monitors. Traffic on this interface that matches criteria in the capture filter is mirrored. Source types include:
       • Database system
       • Exadata VM Cluster
       • Compute instance VNIC
       • Load Balancer
       • Autonomous Data Warehouse

       After you choose the resource type, use the lists to choose the subnet of the current VCN where the resource's IP address or endpoint is located, and the specific resource.

       Traffic from a source can only be mirrored one time.

     • Target: Select the resource of the VTAP's intended target. Mirrored traffic from the source is sent to the target. Types of targets include:
       • Network Load Balancer

       After you choose the resource type, use the lists to choose the subnet of the current VCN where the resource's IP address or endpoint is located, and the specific resource.

     • Capture Filter: Either select an existing capture filter or choose to create a capture filter. A new capture filter needs a Name, Compartment, and at least one rule.
  4. (Optional) Click Show Advanced Options. You can use these options to:
     • VXLAN network identifier (VNI): Enter a VNI to uniquely identify the VXLAN. If you don't choose a VNI, one is generated for you.
     • Max packet size: Choose a maximum packet size between 64 and 9000 bytes. For better performance or efficient ingestion at the target, you can truncate the mirrored packets to a smaller length.
     • Priority mode: Using this option gives equal priority to monitored and mirrored traffic when there is congestion at the source. By default, production traffic is prioritized ahead of VTAP mirrored traffic. When you enable priority mode, monitored traffic and VTAP mirrored traffic are given equal priority. When this option is selected, mirrored traffic might cause some monitored traffic to be dropped whenever the source is congested. If this packet loss is detected you can either disable priority mode or upgrade the source shapes to accommodate more bandwidth.
     • Tags:
       If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.
  5. Click Create VTAP. The VTAP is then created and displayed on the VTAPs page.
     The VTAP is created in the Stopped state. Click Start to start the VTAP if you're ready.

     Traffic from a source can only be mirrored one time. If you start a VTAP and another currently running VTAP monitors the same source, you might disrupt mirroring on the other VTAP.

• When using the CLI, you must create a capture filter before you create the VTAP.

  Use the vtap create command and required parameters to create a VTAP:

  oci network vtap create --capture-filter-id  capture_fliter_OCID --compartment-id  compartment_OCID
  --source-id source_OCID --vcn-id vcn_OCID ... [OPTIONS]

  For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

• When using the API, you must create a capture filter before you create the VTAP.

  Run the CreateVtap operation to create a VTAP.