Filter
Top Products
3. Troubleshooting Functional Failures in Operation
112
3.15 Troubleshooting of sFlow Statistics (Flow Statistics)
Function
The flow for troubleshooting of sFlow statistics function in this system is as follows.
Figure 3-18: Troubleshooting Flow of sFlow Statistics Function
3.15.1 sFlow Packets Do Not Reach Collector
(1) Checking route to the collector
See "3.6.1 Communication Is Disabled or Is Disconnected" and "3.9.1 Communication Is Disabled or Is Disconnected"
to check to see if the collector is properly connected to network. If the maximum size of sFlow packets
(max-packet-size) is changed with the configuration, check to see if the connection to the collector can be established
with the specified packet size.
(2) Checking operation status by operation command
Execute the show sflow command several times to display the sFlow statistical information and check to see if
sFlow statistics function operates normally. If the underlined values shown below are not incremented, see
"(3)Checking configuration." If incremented, see "3.6.1 Communication Is Disabled or Is Disconnected," "
3.9.1 Communication Is Disabled or Is Disconnected" and "(5)Checking settings of collector" to check to see if the
collector is properly connected to network.
Figure 3-19: Display Example of show sflow 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) :
Checking operation status by operation
command.
Checking route to the collector.
Checking configuration.
Checking failures etc.