Acquire Traffic using Traffic Mirroring – Third Party Orchestration
This section outlines the workflow for acquiring traffic with Traffic Mirroring and deploying GigaVUE Fabric Components using Third Party Orchestration. It provides step-by-step guidance on configuring traffic acquisition, processing, and forwarding to your desired destination.
Note: When GigaVUE-FM and the workload VMs requiring monitoring are in different AWS accounts, you must configure a load balancer. Refer to Acquire Traffic using Customer Orchestrated Source with Network Load Balancer or Acquire Traffic using Customer Orchestrated Source with Gateway Load Balancing for configuration steps.
Step No |
Task |
Refer the following topics |
---|---|---|
1 |
Install GigaVUE-FM on AWS
|
|
2 |
Configure the required permissions in AWS. |
Minimum Permissions Required for Acquiring Traffic using Traffic Mirroring |
3 |
Create the AWS Credentials in GigaVUE-FM |
|
4 |
Configure RBAC for deploying fabric components using Third Party Orchestration |
|
5 |
Create a Monitoring Domain
|
|
6 |
Deploy the GigaVUE Fabric Components using AWS. |
Configure GigaVUE Fabric Components in AWS using Third Party Orchestration - Integrated Mode |
7 |
Create a Monitoring Session |
|
8 |
Add Applications to the Monitoring Session |
|
9 |
Deploy Monitoring Session |
|
10 |
View Monitoring Session Statistics |