08-29-2019 04:57 PM - edited 08-29-2019 05:01 PM
Since SU and SUDO are restricted in vEdge, and 'request execute' doesn't run as root, how can I capture Ethernet frames on an interface prior to vManage?
oh-god-please-help-me-make-it-stop# request execute vpn 0 tcpdump -i ge2_0
tcpdump: ge2_0: You don't have permission to capture on that device
(socket: Operation not permitted)
I understand you can do this in vManage once the BFDs are up, but I'm talking about investigating WAN circuits with possible VLAN tagging problems caused by MEF carriers during WAN Turn-Up
Solved! Go to Solution.
08-29-2019 10:30 PM
You don't need the request command to run tcpdump. You can run it with just tcpdump directly from the CLI.
08-29-2019 10:30 PM
You don't need the request command to run tcpdump. You can run it with just tcpdump directly from the CLI.
09-18-2019 01:51 PM
That's great news. In what version was that added?
Thanks for being responsive!
10-10-2019 02:56 PM
To answer my own question: 14.1.x but 16.3.x appears to be when it was standardized
Command History
14.1 | Command introduced. |
16.3 | Updated the command options. |
10-10-2019 03:11 PM
All: As of some version of 18.x. (18.3.5, 18.4.302.), tcpdump started being run with the -p flag.
This definitely wasn't the case on 17.2.8 or 16.2.10.
That basically makes it useless for 90% of WAN troubleshooting scenarios.
Is this a mistake that got left in during a debug build? Any way to work around it?
10-10-2019 03:12 PM
All: As of some version of 18.x. (18.3.5, 18.4.302.), tcpdump started being run with the -p flag.
This definitely wasn't the case on 17.2.8 or 16.2.10.
That basically makes it useless for 90% of WAN troubleshooting scenarios.
Is this a mistake that got left in during a debug build? Any way to work around it?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: