Switching

Hi,

is sFlow implemented in EX2300/EX3400/EX4300 v5 or not? I can not find this info anywhere (it is written in datasheets for EX4600 for example and QFX5k switches) 

The feature explorer tools is the best place to confirm which platforms and Junos versions are needed for particular functions.  Here is the sflow   page.

https://apps.juniper.net/feature-explorer/feature-info.html?fKey=1314&fn=sFlow%20technology

Sure, but  there is no information regarding sFlow version at feature explorer

That is why I checked datasheets and there is no information available for EX2k/3k/4k (except EX46xx)

So my question still is not answered. Speak about poor documentation and information. Shame on you Juniper

EDIT: For reference -

https://sflow.org/sflow_version_5.txt

"This memo describes sFlow version 5. It replaces sFlow version 4 described in RFC 3176"

https://www.juniper.net/documentation/en_US/junos/topics/concept/sflow-ex-series.html

"The Juniper Networks Junos operating system (Junos OS) fully supports the sFlow standard described in RFC 3176"

So factually Juniper says implemented sFlow version is v4, not v5. However EX46xx and QFX have v5 implemented.

So not clear, what version  EX2k/EX3k/EX4k (ie EX2300/EX3400/EX4300) have implemented ...

sFlow is correctly documented in the feature explorer: https://apps.juniper.net/feature-explorer/feature-info.html?fKey=1314&fn=sFlow%20technology

It is also mentioned correctly in the release notes when the EX2300/EX3400 was introduced: https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/ex-series/release-notes/ex-series-junos-release-notes-15.1X53-D50.pdf on page 4.

I have just briefly tested on an EX3400 VC and it looks like it's working - i don't have a collector to validate that received data is actually useable... but I would expect so.

user@EX3400-VC# show protocols sflow
polling-interval 30;
inline-sampling;
sample-rate {
    ingress 500;
    egress 500;
}
collector X.X.1.10 {
    udp-port 6343;
}
interfaces ge-0/0/15.0;
interfaces ge-0/0/16.0;

user@EX3400-VC# run show sflow collector
Collector                                  Udp-port    Dscp     Forwarding-Class                No. of samples
 address
X.X.1.10                                6343        0        best-effort                     6      

{master:0}[edit]
user@EX3400-VC# run show sflow interface
Interface         Status              Sample              Adapted            Polling
                                       rate             sample rate          interval

               Egress  Ingress     Egress   Ingress      Egress   Ingress
ge-0/0/15.0     Enabled Enabled    500      500          500      500          30
ge-0/0/16.0     Enabled Enabled    500      500          500      500          30

{master:0}[edit]

TY for help and your time. Yes, all clear (from the start) - sFlow is implemented in EX2k/3k/4k.

However still not sure if it is v5 that is implemented or v4 on these swithches?

PS Some other brands have "show sFlow agent" command enabled, that shows sFlow version. But I guess we are out of luck with juniper ...

You are right. This is missing both in the documentation and cli output.

I expanded my test a bit and it's version 5 it's sending:

[root@space-XXXX ~]# tcpdump -vvvvvni eth0 port 6343
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:48:25.390592 IP (tos 0x0, ttl 255, id 288, offset 0, flags [none], proto UDP (17), length 272)
    X.X.1.5.50035 > X.X.1.110.sflow: [udp sum ok] sFlowv5, IPv4 agent X.X.1.5, agent-id 16, seqnum 288, uptime 1213994542, samples 1, length 244
        flow sample (1), length 208,
20:48:32.104573 IP (tos 0x0, ttl 255, id 289, offset 0, flags [none], proto UDP (17), length 296)
    X.X.1.5.50035 > X.X.1.110.sflow: [udp sum ok] sFlowv5, IPv4 agent X.X.1.5, agent-id 16, seqnum 289, uptime 1214001257, samples 1, length 268
        counter sample (2), length 232,

I will push information back that documentation and feature explorer should be updated to reflect this.... but no promises about it being fixed.

TY, this is info we needed ...

You're welcome 🙂

I have filed documentation PR 1399956 so there is a task to get the documentation updated - again, I don't know when it will happen but now there is an official task on it 😉