Prerequisites

Ensure that GigaVUE V Series Node has at least have two Networks Interfaces (NIC) attached to it:

  • A management NIC 

  • A data NIC with Accelerated Networking enabled.

When creating a virtual machine for GigaVUE V Series Node using CLI, you can attach Management NIC and Data NIC at the time of the virtual machine creation. However, if you are using Azure GUI to create the virtual machine for GigaVUE V Series Node, then you can attach the data NIC only after creating the virtual machine.

For details, refer to the following topics:

NOTE:

  • Accelerated Networking must be enabled in the Data NIC only when deploying GigaVUE V Series Nodes using Third Party Orchestration.
  • Accelerated Networking is not required for Management NIC.

Create GigaVUE V Series Node with Management and Data NIC Attached using CLI

  1. Create the management NIC.

    az network nic create -g <resource group> --vnet-name <VNet Name> --subnet <Subnet name> -n <Mangement NIC Name>

  2. Create data NIC with Accelerated Networking enabled.

    az network nic create -g <resource group> --vnet-name <VNet> --subnet <Subnet> -n <Data NIC> --accelerated-networking true

  3. CreateGigaVUE V Series Node virtual machine using the above NICS.

az vm create --resource-group <Resource group> --size <Standard_D4s_v4/Standard_D8S_V4> --name <GigaVUE V Series Node> --admin-username gigamon --generate-ssh-keys --image gigamon-inc:gigamon-gigavue-cloud-suite-v2:vseries-nodev6.11.00:6.11.00 --plan-name vseries-node-v6.11.00 --plan-product gigamon-gigavue-cloud-suite-v2 --plan-publisher gigamon-inc --nics <Management NIC and Data NIC>

Note:  You can use the following command to view all the images from Gigamon.

az vm image list --all --publisher gigamon-inc

Create GigaVUE V Series Node with Management and Data NIC Attached using Azure GUI

Enable Management NIC when creating the GigaVUE V Series Node virtual machine.

For details, refer to the Create virtual machine topic in Azure Documentation.

Perform the following steps to attach the data NIC:

  1. Select the GigaVUE V Series Node virtual machine from the Resources Page.
  2. Stop the Virtual Machine using the Stop button.
  3. Navigate to Setting > Networking from the left navigation pane.
    The Networking page appears.
  4. In the Networking page, select Attach network interface.
  5. Select an existing network interface for Data NIC and select OK.
    To enable accelerated networking, refer to Manage Accelerated Networking through the portal.
  6. Start the Virtual Machine.

Keep in mind the following when deploying the fabric components using third party orchestration in integrated mode:

  • Create tokens in the User Management page in GigaVUE-FM. Refer to Configure Tokens for more detailed information.
  • When GigaVUE-FM is 6.10.00 or above and the Fabric Components are on (n-1) or (n-2) versions, you must create a Username and Password instead of using tokens in the registration data. For more details, refer to the Configure Role-Based Access for Third-Party Orchestration section in the 6.9 Documentation.
  • When configuring UCT-V Controller, select UCT-V as the Traffic Acquisition Method.
  • When you select Customer Orchestrated Source as your Traffic Acquisition Method, UCT-V and UCT-V Controller registration are not applicable.
  • When you deploy the fabric components using third party orchestration, you cannot delete the monitoring domain without unregistering the GigaVUE V Series Nodes or UCT-V Controllers.
  • Deployment of UCT-V Controller, GigaVUE V Series Node, and GigaVUE V Series Proxy through a third-party orchestrator is supported only on Linux platform.
  • Deployment of UCT-V through a third-party orchestrator is supported on Linux and Windows platforms. Refer to Linux UCT-V Installation and Windows UCT-V Installation for detailed information.
  • When creating virtual machine for deploying the fabric components in Azure, SSH public key must only be used as the Authentication type in Azure.