Troubleshooting guide

3. Troubleshooting Functional Failures During Operation
140
switchport mode access
s
flow forward ingress <-- sflow forward must be set.
!
(config)#

Make sure that filter has not been set for the physical port at which the flow statistics are
recorded. For details about the procedure, see 3.25.1 Checking the filters and QoS
configuration information.
 If the sender (agent) IP address of an sFlow packet has been set by using the sflow source
command, make sure that the IP address has been assigned to the port of the Switch.
Figure 3-25: Configuration example 4
(config)# show sflow
sflow destination 192.1.1.1 6455
sflow sample 2048
sflow source 192.1.1.100 <-- This IP address must be the one assigned to the
port of the Switch
!
(config)#
(4) Checking the NIF status and port status
Execute the
show interfaces command, and make sure the up/down status of the physical port on
the Switch monitored by the sFlow statistics and the physical port connected to the collector is
active (normal operation).
Figure 3-26: Example of the port status
> show interfaces gigabitethernet 1/5
Date 2006/10/24 17:19:34 UTC
NIF1: active
48-port 10BASE-T/100BASE-TX/1000BASE-T retry:0
Average:150Mbps/24Gbps Peak:200Mbps at 15:44:37
Port5: active up
100BASE-TX full(auto) 0012.e220.ec31
Time-since-last-status-change:1:47:47
Bandwidth:10000kbps Average out:5Mbps Average in:5Mbps
Peak out:5Mbps at 15:44:36 Peak in:5Mbps at 15:44:18
Output rate: 4893.5kbps 16.8kpps
Input rate: 4893.5kbps 16.8kpps
Flow control send :off
Flow control receive:off
TPID:8100
:
>
Note: Make sure that the underlined parts are active or active up.
If the port status is DOWN, see 3.7.1 Communication is not possible or is disconnected and
3.10.1 Communication is not possible or is disconnected.
(5) Checking the settings on the collector
• Make sure that the UDP port number (6343 by default) of the collector has been set so that
data can be received. If data cannot be received, ICMP (
[Type]Destination Unreachable
[
Code]Port Unreachable) is sent to the Switch.
• In addition, make sure that the collector currently used is configured correctly.
3.16.2 Flow samples cannot be sent to the collector
If you have taken actions according to 3.16.1 sFlow packets cannot be sent to the collector but
your problem is not resolved, check the following.