Configure GigaVUE Fabric Components in AWS

You can use your own AWS orchestration system to deploy GigaVUE fabric components and use GigaVUE-FM to configure the advanced features supported by these nodes. These nodes register themselves with GigaVUE-FM using the information provided by your AWS orchestration system. Once the nodes are registered with GigaVUE-FM, you can configure monitoring sessions and related services in GigaVUE-FM. Health status of the registered nodes are determined by the heartbeat messages sent from the respective nodes.

You can also upload custom certificates to GigaVUE V Series Nodes, GigaVUE V Series Proxy, and G-vTAP Controller using your own cloud platform when deploying the fabric components. Refer to Install Custom Certificate for more detailed information.

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

When you deploy the fabric components using third party orchestration, you cannot delete the monitoring domain without unregistering the registered fabric components.
You can use AWS as an Orchestrator for deploying GigaVUE fabric components only when using V Series 2 nodes.
GigaVUE V Series Node must have a minimum of two Networks Interfaces (NIC) attached to it, a management NIC and a data NIC. You can add both these interfaces when deploying the GigaVUE V Series Node in AWS. Refer to Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation for more detailed information on how to add network interfaces when launching an instance.
When using VPC mirroring as the traffic acquisition method, you must add a key and value when deploying the respective fabric components in the AWS orchestrator. The key must be GigamonNode and the value can be anything but it must not contain numbers or special characters.
Component
Key
GigaVUE V Series Node
GigamonNode
GigaVUE V Series Proxy
GigamonNode
G-vTAP Controller
GigamonNode

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

Configure GigaVUE V Series Nodes and V Series Proxy in AWS
Configure G-vTAP Controller in AWS
Configure G-vTAP Agent in AWS

Configure GigaVUE V Series Nodes and V Series Proxy in AWS

To configure GigaVUE V Series Nodes and Proxy in AWS platform:

Before configuring GigaVUE fabric components through AWS, you must create a monitoring domain in GigaVUE-FM. Refer to Create a Monitoring Domain for detailed instructions.
In the Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field as you are going to configure the fabric components in AWS Orchestrator.
In your AWS environment, you can deploy GigaVUE V Series Nodes or V Series proxy using the following methods:
- Register GigaVUE V Series Nodes or Proxy using User Data
- Register GigaVUE V Series Node or Proxy using a configuration file

Register GigaVUE V Series Nodes or Proxy using User Data

To register GigaVUE V Series Nodes or proxy using the user data in AWS GUI:

On the Instances page of AWS EC2, click Launch instances. The Launch Instance wizard appears. For detailed information, refer to Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.

On the Step 3: Configure Instance Details tab, enter the User data as text in the following format and deploy the instance. The GigaVUE V Series Nodes or V Series proxy uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM. You can also install custom certificates to GigaVUE V Series Node or Proxy, refer to the below table for details:

Field

User Data

User data without custom certificate

Copy

#cloud-config
 write_files:
 - path: /etc/gigamon-cloud.conf
   owner: root:root
   permissions: '0644'
   content: |
     Registration:
        groupName: <Monitoring Domain Name>
        subGroupName: <VPC Name>
        user: <Username>
        password: <Password>
        remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
        remotePort: 443

User data with custom certificate

Copy

#cloud-config
 write_files:
 - path: /etc/cntlr-cert.conf
   owner: root:root
   permissions: "0644"
   content: |
      -----BEGIN CERTIFICATE-----
      <certificate content>
      -----END CERTIFICATE-----
 - path: /etc/cntlr-key.conf
   owner: root:root
   permissions: "400"
   content: |
      -----BEGIN PRIVATE KEY-----
      <private key content>
      -----END PRIVATE KEY-----
 - path: /etc/gigamon-cloud.conf
   owner: root:root
   permissions: '0644'
   content: |
     Registration:
         groupName: <Monitoring Domain Name>
         subGroupName: <VPC Name>
         user: <Username>
         password: <Password>
         remoteIP: <IP address of the GigaVUE-FM> or <IP address of the Proxy>
         remotePort: 443

You can register your GigaVUE V Series Node directly with GigaVUE‑FM or you can use V Series proxy to register your GigaVUE V Series Node with GigaVUE‑FM. If you wish to register GigaVUE V Series Node directly, enter the remotePort value as 443 or if you wish to deploy GigaVUE V Series Node using V Series proxy then, enter the remotePort value as 8891.
User and Password must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the UserName and Password created in the Add Users Section.

You can navigate to Instances > Actions > Instance Settings > Edit user data and edit the user data.

Register GigaVUE V Series Node or Proxy using a configuration file

To register GigaVUE V Series Node or Proxy using a configuration file:

Log in to the GigaVUE V Series Node or Proxy.
Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data. You can also install custom certificates to GigaVUE V Series Node or Proxy, refer to the below table for details:
Copy
```
Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <VPC Name>
    user: <Username>
    password: <Password>
    remoteIP: <IP address of the GigaVUE-FM>
    remotePort: 443
```
Note: If you wish to register GigaVUE V Series Node using GigaVUE V Series Proxy then, enter the remotePort value as 8891.
Restart theGigaVUE V Seriesproxy service.
- V Series node:
```
$ sudo service vseries-node restart
```
- V Series proxy:
```
$ sudo service vps restart
```

The deployed GigaVUE V Series node or proxy registers with the GigaVUE-FM. After successful registration theGigaVUE V Series node or proxy sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing ,the fabric node status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the GigaVUE V Series node or proxy and if that fails as well then GigaVUE‑FM unregisters the GigaVUE V Series node or proxy and it will be removed from GigaVUE‑FM.

Configure G-vTAP Controller in AWS

You can configure more than one G-vTAP Controller in a monitoring domain.

To configure G-vTAP Controller in AWS platform:

Before configuring GigaVUE fabric components through AWS, you must create a monitoring domain in GigaVUE-FM. While creating the monitoring domain, select G-vTAP as the Traffic Acquisition Method. Refer to Create a Monitoring Domain for detailed instructions.
Note: You can use AWS Orchestrator for GigaVUE fabric node configuration only using V Series 2 nodes.
In the Monitoring Domain Configuration page, select No for the Use FM to Launch Fabric field as you are going to configure the fabric components in AWS Orchestrator.

In your AWS environment, launch the G-vTAP Controller AMI instance using any of the following methods:

Register G-vTAP Controller using User Data

To register G-vTAP Controller using the user data in AWS GUI:

On the Instances page of AWS EC2, click Launch instances. The Launch Instance wizard appears. For detailed information, refer to Launch an instance using the Launch Instance Wizard topic in Amazon EC2 Documentation.

On the Step 3: Configure Instance Details tab, enter the User data as text in the following format and deploy the instance. The G-vTAP Controller uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM. You can also install custom certificates to G-vTAP Controller, refer to the below table for details:

Field

User Data

User data without custom certificate

Copy

#cloud-config
 write_files:
 - path: /etc/gigamon-cloud.conf
   owner: root:root
   permissions: '0644'
   content: |
     Registration:
        groupName: <Monitoring Domain Name>
        subGroupName: <VPC Name>
        user: <Username>
        password: <Password>
        remoteIP: <IP address of the GigaVUE-FM>
        remotePort: 443

User data with custom certificate

Copy

#cloud-config
 write_files:
 - path: /etc/cntlr-cert.conf
   owner: root:root
   permissions: "0644"
   content: |
      -----BEGIN CERTIFICATE-----
      <certificate content>
      -----END CERTIFICATE-----
 - path: /etc/cntlr-key.conf
   owner: root:root
   permissions: "400"
   content: |
      -----BEGIN PRIVATE KEY-----
      <private key content>
      -----END PRIVATE KEY-----
 - path: /etc/gigamon-cloud.conf
   owner: root:root
   permissions: '0644'
   content: |
     Registration:
         groupName: <Monitoring Domain Name>
         subGroupName: <VPC Name>
         user: <Username>
         password: <Password>
         remoteIP: <IP address of the GigaVUE-FM>
         remotePort: 443

User and Password must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the UserName and Password created in the Add Users Section.

You can navigate to Instances > Actions > Instance Settings > Edit user data and edit the user data.

The G-vTAP Controller deployed in AWS EC2 appears on the Monitoring Domain page of GigaVUE-FM.

Register G-vTAP Controller using a configuration file

To register G-vTAP Controller using a configuration file:

Edit the local configuration file (/etc/gigamon-cloud.conf) and enter the following user data. You can also install custom certificates to G-vTAP Controller, refer to the below table for details:

Copy

Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <VPC Name>
    user: <Username>
    password: <Password>
    remoteIP: <IP address of the GigaVUE-FM>
    remotePort: 443

Restart the G-vTAP Controller service.
```
$ sudo service gvtap-cntlr restart
```

The deployed G-vTAP Controller registers with the GigaVUE-FM. After successful registration the G-vTAP Controller sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing ,the fabric node status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the G-vTAP Controller and if that fails as well then GigaVUE‑FM unregisters the G-vTAP Controller and it will be removed from GigaVUE‑FM.

Configure G-vTAP Agent in AWS

G-vTAP Agent should be registered via the registered G-vTAP Controller and communicates through PORT 8891.

Note: Deployment of G-vTAP Agents through a third-party orchestrator is supported on Linux and Windows platforms. Refer to Linux G-vTAP Agent Installation and Windows G-vTAP Agent Installation for detailed information.

To register G-vTAP Agent using a configuration file:

Install the G-vTAP Agent in the Linux or Windows platform. For detailed instructions, refer to Linux G-vTAP Agent Installation and Windows G-vTAP Agent Installation.
Log in to the G-vTAP Agent.
Edit the local configuration file and enter the following user data.
- /etc/gigamon-cloud.conf is the local configuration file in Linux platform.
- C:\ProgramData\gvtap-agent\gigamon-cloud.conf is the local configuration file in Windows platform.
Copy
```
Registration:
    groupName: <Monitoring Domain Name>
    subGroupName: <VPC Name>
    user: <Username>
    password: <Password>
    remoteIP: <IP address of the G-vTAP Controller 1>,
    <IP address of the G-vTAP Controller 2>            
    remotePort: 8891
```
- User and Password must be configured in the User Management page. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information. Enter the UserName and Password created in the Add Users Section.
Restart the G-vTAP Agent service.
- Linux platform:
```
$ sudo service gvtap-agent restart
```
- Windows platform: Restart from the Task Manager.

Note: You can configure more than one G-vTAP Controller for a G-vTAP Agent, so that if one G-vTAP Controller goes down, the G-vTAP Agent registration will happen through another Controller that is active.

The deployed G-vTAP Agent registers with the GigaVUE-FM through the G-vTAP Controller. After successful registration the G-vTAP Agent sends heartbeat messages to GigaVUE-FM every 30 seconds. If one heartbeat is missing, G-vTAP Agent status appears as 'Unhealthy'. If more than five heartbeats fail to reach GigaVUE-FM, GigaVUE‑FM tries to reach the G-vTAP Agent and if that fails as well then GigaVUE‑FM unregisters the G-vTAP Agent and it will be removed from GigaVUE‑FM.

Keep in mind the following when upgrading the GigaVUE-FM to 6.1.00 (when using third party orchestration to deploy fabric components):

When upgrading GigaVUE-FM to any version higher than 6.0.00 and if the GigaVUE V Series Nodes version deployed in that GigaVUE-FM are lower than or equal to 6.0.00, then for the seamless flow of traffic, GigaVUE-FM automatically creates Users and Roles in GigaVUE-FM with the required permission. The username would be orchestration and the password would be orchestration123A! for the user created in GigaVUE-FM. Ensure that there is no existing user in GigaVUE-FM, with the username orchestration.

It is recommended to change the password in the Users page, once the upgrade is complete. Refer to Configure Role-Based Access for Third Party Orchestration for detailed steps on how to change password in the user page.