Troubleshooting guide

3. Troubleshooting Functional Failures During Operation
141
(1) Checking whether packets are forwarded
Execute the
show interfaces command, and check whether packets are forwarded.
Figure 3-27: 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 to make sure packets are forwarded.
(2) Checking the settings on the collector
Make sure that the collector currently used is configured correctly.
3.16.3 Counter 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.
(1) Checking the sending interval of counter samples
Make sure that the sending interval of counter samples related to the flow statistics is not zero in
the configuration of the Switch. If the value is zero, counter sample data cannot be sent to the
collector.
Figure 3-28: Configuration example
(config)# show sflow
sflow destination 192.1.1.1 6455
sflow sample 2048
sflow polling-interval 60
<-- This value must not be set to zero
!
(config)#