Monitoring, Management & Location Tracking

Not able to do TcpDump on ALE2.0
Requirement:

 

We would need to do packet capture to find out connectivity issues between the network devices. However, ALE 2.0 doesn't come up with the RPM for Tcpdump due to which we won't be able to do the packet capture.



Solution:

 

We wont be able to find the tcp command when we try to do the packet capture.

We can check the tcp packet by executing the below command on ALE CLI,

 

[root@ale ~]# rpm -qa | grep tcp*

 

Output would be empty as we don't have the packet installed.

To resolve this we have to install the TcpDump rpm manually.



Configuration:

 

To install the rpm for TcpDump we can follow the below steps,

 

  • Make sure we have internet access on the server
  • Execute the below command to install the rpm package

 

# yum install tcpdump



Verification

 

Once we do the yum install, we can use the below command to verify whether the packet is installed

 

[root@localhost mercury]# rpm -qa | grep tcp

tcpdump-4.0.0-5.20090921gitdf3cb4.2.el6.x86_64

 

Now we should be able to do the packet capture using the TcpDump command.

Version history
Revision #:
2 of 2
Last update:
‎03-18-2017 12:59 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.