Filter
Top Products
3. Troubleshooting Functional Failures in Operation
115
3.15.2 Flow Sample Does Not Reach Collector
If problem still persists even after checking "3.15.1 sFlow Packets Do Not Reach Collector," check the following:
(1) Checking presence/absence of the relay packet
Execute the show interfaces command to check to see if the packet is relayed.
Figure 3-26: Display Example of 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: Confirm that the packet is relayed based on the display at underlined part.
(2) Checking settings of collector
Check to see if settings of the collector used are correct.
3.15.3 Counter Sample Does Not Reach Collector
If problem still persists even after checking "3.15.1 sFlow Packets Do Not Reach Collector," check the following:
(1) Checking transmission interval of counter sample
Check to see if the transmission interval of the counter sample related to flow statistics is set to 0 in the configuration of
this system. If set to 0, the counter sample data is not sent to the collector.
Figure 3-27: Display Example of Configuration
(config)# show sflow
sflow destination 192.1.1.1 6455
sflow sample 2048
sflow polling-interval 60
<- 0 must not be set here.
!
(config)#