[j-nsp] sflow on 2x EX4200 VC - no sflow data send

[Giovanni Bellac]

Hi

do you think a upgrade of the VC (2x 4200) to JunOS 10.4 will solve the problem 
?

I can not believe that JunOS 10.0S10 is so broken ... :/
I have read that some people are using sflow with JunOS 9.6 in the Juniper 
forums.

We need to run sflow for traffic accounting.

Best regards
Giovanni




________________________________
Von: Chris Evans <chrisccnpspam2 at gmail.com>
An: Giovanni Bellac <giovannib1979 at ymail.com>
CC: juniper-nsp at puck.nether.net
Gesendet: Donnerstag, den 17. März 2011, 14:04:53 Uhr
Betreff: Re: [j-nsp] sflow on 2x EX4200 VC - no sflow data send


I can lol.  Still tons of things broken or half baked in the ex platforms. 
On Mar 17, 2011 8:26 AM, "Giovanni Bellac" <giovannib1979 at ymail.com> wrote:
> Hello
> 
> sflow was introduced in JunOS 9.3 to EX platform.
> 
> I can not believe, that sflow is not really working in 10.0...
> 
> :(
> 
> Best regards
> Giovanni
> 
> 
> 
> 
> ________________________________
> Von: Chris Evans <chrisccnpspam2 at gmail.com>
> An: Richard A Steenbergen <ras at e-gerbil.net>
> CC: juniper-nsp at puck.nether.net; Giovanni Bellac <giovannib1979 at ymail.com>
> Gesendet: Dienstag, den 15. März 2011, 17:40:00 Uhr
> Betreff: Re: [j-nsp] sflow on 2x EX4200 VC - no sflow data send
> 
> 
> Agree with Rich on this. Slow currently is practically worthless. 
> On Mar 15, 2011 12:29 PM, "Richard A Steenbergen" <ras at e-gerbil.net> wrote:
>> On Tue, Mar 15, 2011 at 02:15:52PM +0000, Giovanni Bellac wrote:
>>> 
>>> The problem is, that the VC is not exporting sflow data to the 
>>> collector.
>> 
>> We found a number of sFlow issues in our testing. For example, it didn't 
>> actually export any data at all on routed interfaces until 10.2. Of 
>> course it's not actually useable for us until they fix some of the 
>> missing fields (like dst ifindex and nexthop, added in 10.4 I believe), 
>> so our testing was very limited. Actually it probably won't be usable in 
>> our production systems until the fix the lack of a netmask field (i.e. 
>> it'll tell you that the dst IP is 1.2.3.4, but they don't send the field 
>> to tell you that the dst route was 1.2.3.0/24), so we're still waiting 
>> to do anything serious with it. :)
>> 
>> -- 
>> Richard A Steenbergen <ras at e-gerbil.net> http://www.e-gerbil.net/ras
>> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp