By combining EEM with the Embedded Packet Capture (EPC) feature, one can create an ever-running packet capture on the device that can be automatically stopped when a problem occurs. Once stopped, the resulting capture file will be emailed to a recipient. The result is a snapshot of the traffic leading up to and at the moment a problem occurs on the network.
The attached Tcl policy uses the standard EEM email environment variables as well as the following:
$dpr_syslog : Syslog message pattern for which to watch before stopping the packet capture
$dpr_cappnt : EPC capture point
$dpr_capbuf : EPC Capture buffer
A sample EPC configuration for this policy would be:
Hi Team, I ran into the problem of organizing a boot in legacy and UEFI on one DHCP pool, understanding rfc4578, or rather how to registaer two boot files on one DHCP pool with an understanding of 0, 6, 9 labels to select either legasy or EFI boot.&n...
Hi All,We have remote site connected via two ISP (4G and ethernet) connection and is using DMVPN to connect to HQ. The DMVPN is currently setup successfully over the 4G internet but I need to configure 2nd internet connection as a backup to 4G.  ...
Hello Team,I try to upgrade large number of NCS55 and would like to use ZTP helping me with iPXE. For that I use a Linux machine with dhcp an web server. The DHCP Server is able to differentiate between iPXE and ZTP and if I start iPXE by command it runs ...
Hello Friends,I have built the SD-WAN lab on EVE-NG Community on my server. I use the same lab with same configuration for both vedge-cloud and CSR1000v. For vedge-cloud everything works perfectly fine, it builds control connection to all the controllers ...