This task allows you to verify IP traffic export parameters such as the monitored ingress interface, which is where the IP
traffic is exported, and outgoing and incoming IP packet information, such as configured ACLs. You can also use this task
to monitor packets that are captured and then transmitted across an interface to a destination host. Use this optional task
to help you troubleshoot any problems with your exported IP traffic configurations.
SUMMARY STEPS
-
enable
-
debug
ip
traffic-export
events
-
show
ip
traffic-export
[interface
interface-name |
profile
profile-name
DETAILED STEPS
|
Command or Action |
Purpose |
Step 1 |
enable
|
Enables privileged EXEC mode.
|
Step 2 |
debug
ip
traffic-export
events
Router# debug ip traffic-export events
|
Enables debugging messages for exported IP traffic packets events.
|
Step 3 |
show
ip
traffic-export
[interface
interface-name |
profile
profile-name
Router# show ip traffic-export
|
Displays information related to exported IP traffic events.
-
interface
interface-name
--Only data associated with the monitored ingress interface is shown.
-
profile
profile-name
--Only flow statistics, such as exported packets and the number of bytes, are shown.
|
Example
The following sample output from the
show
ip
traffic-export command is for the profile βone.β This example is for a single, configured interface. If multiple interfaces are configured,
the information shown below is displayed for each interface.
Router# show ip traffic-export
Router IP Traffic Export Parameters
Monitored Interface FastEthernet0/0
Export Interface FastEthernet0/1
Destination MAC address 0030.7131.abfc
bi-directional traffic export is off
Input IP Traffic Export Information Packets/Bytes Exported 0/0
Packets Dropped 0
Sampling Rate one-in-every 1 packets
No Access List configured
Profile one is Active