3. Troubleshooting Functional Failures in Operation1153.15.2 Flow Sample Does Not Reach CollectorIf 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 packetExecute 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/5Date 2006/10/24 17:19:34 UTCNIF1: active 48-port 10BASE-T/100BASE-TX/1000BASE-T retry:0Average:150Mbps/24Gbps Peak:200Mbps at 15:44:37Port5: active up 100BASE-TX full(auto) 0012.e220.ec31Time-since-last-status-change:1:47:47Bandwidth:10000kbps Average out:5Mbps Average in:5MbpsPeak out:5Mbps at 15:44:36 Peak in:5Mbps at 15:44:18Output rate: 4893.5kbps 16.8kppsInput rate: 4893.5kbps 16.8kppsFlow control send :offFlow control receive:offTPID:8100 :>Note: Confirm that the packet is relayed based on the display at underlined part.(2) Checking settings of collectorCheck to see if settings of the collector used are correct.3.15.3 Counter Sample Does Not Reach CollectorIf problem still persists even after checking "3.15.1 sFlow Packets Do Not Reach Collector," check the following:(1) Checking transmission interval of counter sampleCheck to see if the transmission interval of the counter sample related to flow statistics is set to 0 in the configuration ofthis system. If set to 0, the counter sample data is not sent to the collector.Figure 3-27: Display Example of Configuration(config)# show sflowsflow destination 192.1.1.1 6455sflow sample 2048sflow polling-interval 60 <- 0 must not be set here.!(config)#
