[j-nsp] EX2300 Supply Delays?
Harald F. Karlsen
harald at bgp.no
Sat Aug 27 13:33:42 EDT 2016
On 27.08.2016 19:13, Giuliano Medalha wrote:
> Harald
>
> What kind of bugs did you find in EX2300 ?
Just to mention a few I noticed the first couple days;
* Sflow reports completely wrong values. I have not had time to dig
further into this. I know there's a PR where it says sflow doesn't work
on egress traffic, but this is also affects ingress.
* J-web doesn't work and entering the web gui makes httpd consume 100%
cpu and makes the entire box unresponsive.
* Commit confirmed doesn't always roll back correctly.
* NTP is broken. My device believes it's 2038-01-19 04:14:07 CET now and
with "Time Source: NTP CLOCK".
This is just the ones I can think of right now. I know there are more as
well.
>
> Is it critical ? Some basic functions not working at all ?
That's up to you to decide. I'd say a few of them is pretty basic and
critical.
Also quite a few other features are missing at FRS. Just mentioning some:
* ip-source-guard.
* mld-snooping (Really, it's 2016. All switches should support and run
this by default at FRS. At least when IGMP-snooping is supported and
enabled by default).
* ipv6-source-guard (and a lot of IPv6 first-hop security stuff).
Needless to say, I wouldn't recommend putting these boxes into
production yet.
--
Harald
More information about the juniper-nsp
mailing list