Also, what do your stats look like? 6kft is getting beyond the sweet spot for
VDSL2, particularly if you're trying to push 10Mbps on the upstream.
Sent from my iPhone
On Jan 15, 2015, at 5:36, Shawn L sha...@up.net wrote:
I was going to ask if you've tested the cable pair at all. If the
We always adhere to JTAC:
http://kb.juniper.net/InfoCenter/index?page=contentid=KB21476actp=SUBSCRI
PTION unless otherwise required by their support to change.
Currently it is Junos 13.2X51-D26.
My advice to you is to not use 14.1 unless you have a reason, as that is
more of a dev branch in
On Tue, Jan 13, 2015 at 4:45 PM, Stephen R. Carter
stephen.car...@gltgc.org wrote:
We love our 5100s here.
Out of interest: Are you running 13.2 or 14.1?
What features are you using?
Our own experiences with a bunch of 48 96 port machines running 14.1
is painful to say the least.
Richard
I'm going to guess you're a CLEC from your website and a common problem
I've seen in that scenario is that vectoring doesn't work between DSLAMs
because it needs all pairs to be part of the vector group so that the DSLAM
can mitigate FEXT. DSLAM vendors have been working on system level, rather
Software Defined Networking (SDN) features that QFX5100 supports:
Automatic configuration of OVSDB-managed VXLANs with trunk interfaces
14.1X53-D15
OVSDB support 14.1X53-D10
OpenFlow v1.0 14.1X53-D10
OpenFlow v1.3.1 14.1X53-D10
VXLAN Gateway 14.1X53-D10
I was going to ask if you've tested the cable pair at all. If the pair is
bad, or even a little out of balance, bad scotch loks, etc. VDSL isn't
going to work properly.
We have customers that are definitely in-range for VDSL but who cannot get
it because there is a 26 gauge insert between two
6 matches
Mail list logo
