Deployment Options for GigaVUE Cloud Suite for Third Party Orchestration
This section provides a detailed information on the multiple ways in which GigaVUE Cloud Suite for Third Party Orchestration can be configured to provide visibility for physical and virtual traffic. There are five different ways in which GigaVUE Cloud Suite for Third Party Orchestration can be configured based on the traffic acquisition method and the method in which you want to deploy fabric components. For more detailed information and the work flow refer the following topics:
- Deploy GigaVUE Fabric Components using Generic Mode
- Deploy GigaVUE Fabric Components using Integrated Mode
Deploy GigaVUE Fabric Components using Generic Mode
If you wish to deploy GigaVUE fabric components using generic mode, it can be done in four ways:
Without Creating Monitoring Domain
In generic mode, when deploying the fabric components, you can provide the monitoring domain and connection name directly in your orchestrator. A Monitoring Domain will be created under the Third Party Orchestration monitoring domain page in GigaVUE‑FM and your GigaVUE fabric components will be deployed in that monitoring domain.
Traffic Acquisition Method as UCT-V
Follow instruction in the below table, if you wish to use UCT-V as your traffic acquisition method. When using UCT-V the traffic from the Virtual Machines are acquired using the UCT-V and it is sent to the GigaVUE V Series Nodes.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM
|
|
|
2 |
Install UCT-V |
|
|
3 |
Create User and Password |
|
|
4 |
Configure GigaVUE Fabric Components |
|
|
5 |
Create Monitoring session |
|
|
6 |
Add Applications to the Monitoring Session |
|
|
7 |
Deploy Monitoring Session |
|
|
8 |
View Monitoring Session Statistics |
Traffic Acquisition Method as Customer Orchestrated Source
Follow instruction in the below table if you wish to use Customer Orchestrated Source as your traffic acquisition method. In this case you can use tunnels as a source where the traffic is directly tunneled to GigaVUE V Series Nodes without deploying UCT-V or UCT-V controllers.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM
|
|
|
2 |
Create User and Password |
|
|
3 |
Configure GigaVUE Fabric Components |
|
|
4 |
Create Monitoring session |
|
|
5 |
Create Ingress and Egress Tunnel Endpoints |
|
|
6 |
Add Applications to the Monitoring Session |
|
|
7 |
Deploy Monitoring Session |
|
|
8 |
View Monitoring Session Statistics |
By Creating Monitoring Domain
In generic mode, you can also create a monitoring domain under Third Party Orchestration and provide the monitoring domain name and the connection name in the user data that will be used in your orchestrator.
Traffic Acquisition Method as UCT-V
Follow instruction in the below table, if you wish to use UCT-V as your traffic acquisition method. When using UCT-V the traffic from the Virtual Machines are acquired using the UCT-V and it is sent to the GigaVUE V Series Nodes.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM
|
|
|
2 |
Install UCT-V |
|
|
3 |
Create User and Password |
|
|
4 |
Create a Monitoring Domain |
|
|
5 |
Configure GigaVUE Fabric Components |
|
|
6 |
Create Monitoring session |
|
|
7 |
Add Applications to the Monitoring Session |
|
|
8 |
Deploy Monitoring Session |
|
|
9 |
View Monitoring Session Statistics |
Traffic Acquisition Method as Customer Orchestrated Source
Follow instruction in the below table, if you wish to use Customer Orchestrated Source as your traffic acquisition method. In this case you can use tunnels as a source where the traffic is directly tunneled to V Series nodes without deploying UCT-V or UCT-V controllers.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM
|
|
|
2 |
Create User and Password |
|
|
3 |
Create a Monitoring Domain |
|
|
4 |
Configure GigaVUE Fabric Components |
|
|
5 |
Create Monitoring session |
|
|
6 |
Create Ingress and Egress Tunnel Endpoints |
|
|
7 |
Add Applications to the Monitoring Session |
|
|
8 |
Deploy Monitoring Session |
|
|
9 |
View Monitoring Session Statistics |
Deploy GigaVUE Fabric Components using Integrated Mode
GigaVUE‑FM allows you to use your own cloud platform as an orchestrator to deploy GigaVUE fabric components and then use GigaVUE-FM to configure the advanced features supported by these nodes. In integrated mode, you create a monitoring domain in your respective GigaVUE Cloud Suite in GigaVUE-FM and then use your own orchestration system to just deploy nodes. The GigaVUE V Series Nodes deployed using your own orchestration system will be displayed under the monitoring domain created in your respective GigaVUE Cloud Suite. In this case, ensure that the monitoring domain and the connection name given in the GigaVUE-FM matches the groupName and subGroupName in the user data provided in your orchestration system. Refer the following table for the step-by-step instructions.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM
|
|
|
2 |
Create User and Password in GigaVUE-FM. |
|
|
3 |
Install UCT-V |
|
|
4 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is disabled. |
Refer to the Create Monitoring Domain section in the respective cloud guide. |
|
5 |
Configure GigaVUE Fabric Components Note: Select UCT-V as the Traffic Acquisition Method. When using integrated mode you can only use UCT-V as the traffic acquisition method. |
|
|
6 |
Create Monitoring session |
|
|
7 |
Add Applications to the Monitoring Session |
|
|
8 |
Deploy Monitoring Session |
|
|
9 |
View Monitoring Session Statistics |
