On Mon, 25 Oct 2004, Ray Taft wrote: > No, you can not monitor a VE interface. It will report back zero usage. > Bummer, I know. > > Ray >
That is indeed a pain. Does anyone know if the lack of VE interface counters is a hardware problem? Does it change with a VM-1 card installed? I've started looking at how to extract the information from sFlow, but annoyingly I can't even seem to get sFlow exporting working. [EMAIL PROTECTED] run | inc sflow sflow enable sflow sample 512 sflow polling-interval 30 sflow destination w.x.y.z [EMAIL PROTECTED] t [EMAIL PROTECTED](config)#int e1/3 [EMAIL PROTECTED](config-if-e1000-1/3)#sflow forwarding [EMAIL PROTECTED](config-if-e1000-1/3)#exit [EMAIL PROTECTED](config)#exit [EMAIL PROTECTED] sflow sFlow services are enabled. sFlow agent IP address: 10.134.221.4 Collector IP w.x.y.z, UDP 6343 Polling interval is 30 seconds. Configured default sampling rate: 1 per 512 packets. Actual default sampling rate: 1 per 512 packets. 0 UDP packets exported 0 sFlow samples collected. No ports configured for sFlow sampling. Module Sampling Rates [EMAIL PROTECTED] run int e1/3 !Building configuration... !Current configuration : 47 bytes interface ethernet 1/3 port-name Gi0/1 Net1 ! So basically it's just ignoring the sFlow port configuration. I've read through the Foundry docs and can't seem to figure out why. The interface e1/3 is one of the GE ports on the B4GMR4 card, and the box is running 07.7.01T53 (B2R07701). Feels like I'm missing something very obvious, but I can't see what. Sam > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jonas Frey > Sent: Monday, October 25, 2004 12:07 PM > To: Cliff Fogle > Cc: [email protected] > Subject: RE: [f-nsp] Measurement of BigIron virtual interfaces > > Hi, > > please bare in mind: sflow is only supported on the jetiron m4 boards, > not on the (old) ironcore ones. > I dont know about ve monitoring/accounting. > > Btw, i got some foundry equipment to sell...if anyone is interessted: > B2P622-SM-IR > M4R4G (somehow defective, tends to crash when running bgp/using alot of > routes) > > > Regards, > Jonas > > On Mon, 2004-10-25 at 18:57, Cliff Fogle wrote: >> NTOP kind of has sflow support. It really only gives 'top talkers' >> info. The best thing out there at this time is really InMon's traffic >> server: >> >> http://www.inmon.com/products/trafficserver.php >> >> (warning: There is a free demo avaialble and it's addictive) >> >> Foundry is apparently building much better sflow support into INM 1.8, >> but I have yet to see anything other than a PowerPoint mock up of it. >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Sam Stickland >> Sent: Monday, October 25, 2004 6:47 AM >> To: [email protected] >> Subject: [f-nsp] Measurement of BigIron virtual interfaces >> >> Hi, >> >> Is it possible to measure the virtual interface bandwidth stats on the >> BigIrons (Mmgt4)? I notice that the interface OID's appear to be >> readable but the counters never seem to increment (running 07.7.01T53) >> >> Can this information be read via SNMP. If not, a cursorsy glance at the >> sFlow specs seems to suggest is it possible to measure this information >> using sFlow. If so are there any opensource or reasonably lightweight >> tools that can process the information in this regard? >> >> Thanks, >> >> Sam >> _______________________________________________ >> foundry-nsp mailing list >> [email protected] >> http://puck.nether.net/mailman/listinfo/foundry-nsp >> >> >> >> _______________________________________________ >> foundry-nsp mailing list >> [email protected] >> http://puck.nether.net/mailman/listinfo/foundry-nsp > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > From [EMAIL PROTECTED] Tue Oct 26 12:18:16 2004 From: [EMAIL PROTECTED] (Cliff Albert) Date: Tue Oct 26 12:18:20 2004 Subject: [f-nsp] Measurement of BigIron virtual interfaces In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Tue, Oct 26, 2004 at 05:13:32PM +0100, Sam Stickland wrote: > [EMAIL PROTECTED] run | inc sflow > sflow enable > sflow sample 512 > sflow polling-interval 30 > sflow destination w.x.y.z > > [EMAIL PROTECTED] t > [EMAIL PROTECTED](config)#int e1/3 > [EMAIL PROTECTED](config-if-e1000-1/3)#sflow forwarding > [EMAIL PROTECTED](config-if-e1000-1/3)#exit > [EMAIL PROTECTED](config)#exit > > [EMAIL PROTECTED] sflow > sFlow services are enabled. > sFlow agent IP address: 10.134.221.4 > Collector IP w.x.y.z, UDP 6343 > Polling interval is 30 seconds. > Configured default sampling rate: 1 per 512 packets. > Actual default sampling rate: 1 per 512 packets. > 0 UDP packets exported > 0 sFlow samples collected. > No ports configured for sFlow sampling. > Module Sampling Rates > > [EMAIL PROTECTED] run int e1/3 > !Building configuration... > !Current configuration : 47 bytes > interface ethernet 1/3 > port-name Gi0/1 Net1 > ! > > So basically it's just ignoring the sFlow port configuration. I've read > through the Foundry docs and can't seem to figure out why. The interface > e1/3 is one of the GE ports on the B4GMR4 card, and the box is running > 07.7.01T53 (B2R07701). > > Feels like I'm missing something very obvious, but I can't see what. Config looks really similair to mine: sflow enable sflow sample 512 sflow destination you.know.where and then per interface I monitor an sflow-forwarding directive. Works just fine, running 7.7.01bT53. I have a jetcore setup. -- Cliff Albert <[EMAIL PROTECTED]> From [EMAIL PROTECTED] Tue Oct 26 12:22:56 2004 From: [EMAIL PROTECTED] (Jonas Frey) Date: Tue Oct 26 12:22:59 2004 Subject: [f-nsp] Measurement of BigIron virtual interfaces In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Sam, you have a old M4 based on the ironcore chipset (see my last mail to the list), this doesnt support sflow. You can configure it but it will NOT work. A VM1 *does* support sflow. Regards, Jonas On Tue, 2004-10-26 at 18:13, Sam Stickland wrote: > On Mon, 25 Oct 2004, Ray Taft wrote: > > > No, you can not monitor a VE interface. It will report back zero usage. > > Bummer, I know. > > > > Ray > > > > That is indeed a pain. > > Does anyone know if the lack of VE interface counters is a hardware > problem? Does it change with a VM-1 card installed? > > I've started looking at how to extract the information from sFlow, but > annoyingly I can't even seem to get sFlow exporting working. > > [EMAIL PROTECTED] run | inc sflow > sflow enable > sflow sample 512 > sflow polling-interval 30 > sflow destination w.x.y.z > > [EMAIL PROTECTED] t > [EMAIL PROTECTED](config)#int e1/3 > [EMAIL PROTECTED](config-if-e1000-1/3)#sflow forwarding > [EMAIL PROTECTED](config-if-e1000-1/3)#exit > [EMAIL PROTECTED](config)#exit > > [EMAIL PROTECTED] sflow > sFlow services are enabled. > sFlow agent IP address: 10.134.221.4 > Collector IP w.x.y.z, UDP 6343 > Polling interval is 30 seconds. > Configured default sampling rate: 1 per 512 packets. > Actual default sampling rate: 1 per 512 packets. > 0 UDP packets exported > 0 sFlow samples collected. > No ports configured for sFlow sampling. > Module Sampling Rates > > [EMAIL PROTECTED] run int e1/3 > !Building configuration... > !Current configuration : 47 bytes > interface ethernet 1/3 > port-name Gi0/1 Net1 > ! > > So basically it's just ignoring the sFlow port configuration. I've read > through the Foundry docs and can't seem to figure out why. The interface > e1/3 is one of the GE ports on the B4GMR4 card, and the box is running > 07.7.01T53 (B2R07701). > > Feels like I'm missing something very obvious, but I can't see what. > > Sam > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Jonas Frey > > Sent: Monday, October 25, 2004 12:07 PM > > To: Cliff Fogle > > Cc: [email protected] > > Subject: RE: [f-nsp] Measurement of BigIron virtual interfaces > > > > Hi, > > > > please bare in mind: sflow is only supported on the jetiron m4 boards, > > not on the (old) ironcore ones. > > I dont know about ve monitoring/accounting. > > > > Btw, i got some foundry equipment to sell...if anyone is interessted: > > B2P622-SM-IR > > M4R4G (somehow defective, tends to crash when running bgp/using alot of > > routes) > > > > > > Regards, > > Jonas > > > > On Mon, 2004-10-25 at 18:57, Cliff Fogle wrote: > >> NTOP kind of has sflow support. It really only gives 'top talkers' > >> info. The best thing out there at this time is really InMon's traffic > >> server: > >> > >> http://www.inmon.com/products/trafficserver.php > >> > >> (warning: There is a free demo avaialble and it's addictive) > >> > >> Foundry is apparently building much better sflow support into INM 1.8, > >> but I have yet to see anything other than a PowerPoint mock up of it. > >> > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of Sam Stickland > >> Sent: Monday, October 25, 2004 6:47 AM > >> To: [email protected] > >> Subject: [f-nsp] Measurement of BigIron virtual interfaces > >> > >> Hi, > >> > >> Is it possible to measure the virtual interface bandwidth stats on the > >> BigIrons (Mmgt4)? I notice that the interface OID's appear to be > >> readable but the counters never seem to increment (running 07.7.01T53) > >> > >> Can this information be read via SNMP. If not, a cursorsy glance at the > >> sFlow specs seems to suggest is it possible to measure this information > >> using sFlow. If so are there any opensource or reasonably lightweight > >> tools that can process the information in this regard? > >> > >> Thanks, > >> > >> Sam > >> _______________________________________________ > >> foundry-nsp mailing list > >> [email protected] > >> http://puck.nether.net/mailman/listinfo/foundry-nsp > >> > >> > >> > >> _______________________________________________ > >> foundry-nsp mailing list > >> [email protected] > >> http://puck.nether.net/mailman/listinfo/foundry-nsp > > > > _______________________________________________ > > foundry-nsp mailing list > > [email protected] > > http://puck.nether.net/mailman/listinfo/foundry-nsp > > > > _______________________________________________ > > foundry-nsp mailing list > > [email protected] > > http://puck.nether.net/mailman/listinfo/foundry-nsp > >
