To install from an RPM (.rpm) package on a Redhat, CentOS, or other RPM-based system:
- Download the G-vTAP Agent
6.1.00
RPM (.rpm) package from the Gigamon Customer Portal. For assistance contact Contact Technical Support.
- Copy this package to your instance. Install the package with root privileges, for example:
[user@ip-10-0-0-214 ~]$ lsgvtap-agent_6.1.00
_x86_64.rpm[user@ip-10-0-0-214 ~]$ sudo rpm -i
gvtap-agent_6.1.00
_x86_64.rpm
- Modify the file /etc/gvtap-agent/gvtap-agent.conf to configure and register the source and destination interfaces.The following
example registers the eth0 as the mirror source for both ingress and egress traffic and registers eth1
as the destination for this traffic as follows:
Note: Any changes to the G-vTAP Agent config file made after the initial setup require an agent restart and an inventory refresh or sync from GigaVUE-FM to pick up the new changes and re-initiate the traffic mirroring. When you have an active, successful monitoring session deployed, modifying the G-vTAP config file results in traffic loss until GigaVUE-FM does a periodic sync on its own every 15 minutes.
Example 1—Configuration example to monitor ingress and egress traffic at interface eth0 and use the same interface to send out the mirrored packets
# eth0 mirror-src-ingress mirror-src-egress mirror-dst
Example 2—Configuration example to monitor ingress and egress traffic at interface eth0 and use the interface eth1 to send out the mirrored packets
# eth0 mirror-src-ingress mirror-src-egress# eth1 mirror-dst
Example 3—Configuration example to monitor ingress and egress traffic at interface eth0 and eth 1; use the interface eth1 to send out the mirrored packets
# eth0 mirror-src-ingress mirror-src-egress# eth1 mirror-src-ingress mirror-src-egress mirror-dst
- Save the file.
-
To enable the third-party orchestration, a configuration file /etc/gigamon-cloud.conf needs to be created with the following contents:
Registration:
groupName: <Monitoring Domain Name>
subGroupName: <Connection Name>
user: orchestration
password: orchestration123A!
remoteIP: <controller list IP addresses separated by comma>
remotePort: 8891
- Reboot the instance.
Check the status with the following command:
[user@ip-10-0-0-214 ~]$ sudo service gvtap-agent status G-vTAP Agent is running