Configure GigaVUE Fabric Components in AWS using Third Party Orchestration - Integrated Mode

This topic provides instructions on how to register GigaVUE fabric components using AWS GUI or a configuration file.

Prerequisite:

Before deploying GigaVUE Fabric Components in AWS, create a Monitoring Domain in GigaVUE‑FM with the Use FM to Launch Fabric toggle button disabled. For details, refer to Create a Monitoring Domain.

Key Considerations:

• When you deploy the fabric components using third party orchestration, you cannot delete the Monitoring Domain without unregistering the registered fabric components.
• When using Traffic Mirroring as the traffic acquisition method, you must add a key and value when deploying the respective fabric components in the AWS orchestrator. Set the key to GigamonNode and any string to the value. The string cannot contain numbers and special characters.
• GigaVUE V Series Node must have a minimum of two Network Interfaces (NIC) attached to it, a management NIC, and a data NIC. You can add both interfaces when deploying the GigaVUE V Series Node in AWS. For details, refer to the Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.
• 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.
• You must configure a token in the User Management page. For details, refer to Configure Tokens.

In your AWS EC2, you can configure the following GigaVUE fabric components:

• Configure UCT-V Controller in AWS
• Configure UCT-V in AWS
• Configure GigaVUE V Series Nodes and GigaVUE V Series Proxy in AWS

What to do Next:

After deploying the GigaVUE Fabric Components in AWS, you must create a Monitoring Session. For details, refer to Configure Monitoring Session.