Troubleshooting guide

3. Troubleshooting Functional Failures During Operation
139
Send CounterSample UDP packets: 621 Send failed packets: 0
>
Note: Make sure that the underlined values increase.
(3) Checking the configuration
Check the following in the active configuration:
 Make sure that the IP address and UDP port number of the collector to which sFlow packets
are sent have been set correctly in the configuration.
Figure 3-21: Configuration example 1
(config)# show sflow
sflow destination 192.1.1.1 6455 <-- Collector information must be set
correctly.
sflow sample 2048
!
(config)#

Make sure that the sampling interval has been set.
If the sampling interval is not set, a large default value is used. This value is too large, and
almost no flow samples are sent to the collector. Therefore, set an appropriate value for the
sampling interval. Note that if a value that is much smaller than the recommended value is set,
the CPU usage might increase.
Figure 3-22: Make sure that the sampling interval has been set.
(config)# show sflow
sflow destination 192.1.1.1 6455
sflow sample 2048
<-- An appropriate value for the sampling interval must
be set.
!
(config)#
Figure 3-23: Example of the operation command
> show sflow
Date 2006/10/24 20:04:01 UTC
sFlow service status: enable
Progress time from sFlow statistics cleared: 16:00:05
sFlow agent data :
sFlow service version : 4
CounterSample interval rate: 60 seconds
Default configured rate: 1 per 2048 packets
Default actual rate : 1 per 2048 packets
Configured sFlow ingress ports : 1/ 2-4
Configured sFlow egress ports : 5/ 9-11
Received sFlow samples : 37269 Dropped sFlow samples(Dropped Que) :
2093(2041)
Exported sFlow samples : 37269 Couldn't exported sFlow samples : 0
:
>
Note: Make sure that the underlined part displays an appropriate sampling interval.

Make sure that sflow forward has been set for the physical port at which the flow statistics
are recorded.
Figure 3-24: Configuration example 3
(config)# show interfaces
interface gigabitethernet 1/2