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:
We split a /24 into two /25 segments:eth 1/1 - 184.108.40.206/25eth 1/2 - 220.127.116.11/25eth 1/3 - 18.104.22.168 - ISP link So the whole /24 lives on the router, but split. When I advertise 22.214.171.124/24 to ISP, it doesn't show up as and advertised route. Is there a...
is it possible to add more than 1 ip wccp redirect on a vlan interface ? Each one with a different associated access list, will both redirect access list be searched for a match ? interface Vlan903ip address 10.250.1.21 255.255.255.252ip wccp 5 redir...
I have a legacy network originally designed to allocate subnets to individual servers through VLANs, controlled through bridged switches to our individual cabinets. Each server would be assigned a switch port and a subnet VLAN. Over the ...