Also, IBM G8364 (uses Broadcom Trident merchant silicon).
I believe the Force10 S4810 (also Broadcom Trident) is only SFP+?
Intel will force 10GBASE-T on all of us since they can make it backwards
compatible with 1000BASE-T. I think this will make the technology take off
over the next year or
Sorry, that is IBM G8264T. G8316 is the 16x40G version.
On Mon, Oct 1, 2012 at 6:27 PM, Brian Loveland br...@aereo.com wrote:
Also, IBM G8364 (uses Broadcom Trident merchant silicon).
I believe the Force10 S4810 (also Broadcom Trident) is only SFP+?
Intel will force 10GBASE-T on all of us
Interested on where you are buying transit at $1750/mo for full 10G ports
($0.175/meg)?
On Fri, Dec 27, 2013 at 8:18 PM, Baldur Norddahl
baldur.nordd...@gmail.comwrote:
On Sat, Dec 28, 2013 at 12:56 AM, Jon Sands fohdee...@gmail.com wrote:
Yes, and in that world, one should probably not
We've worked through the same issues with Brocade/Intel, although we found
that even though Brocade specs active only, our ICX switches don't reject
passive cables, although oddly the Intel branded passive cables show up as
UNSUPPORTED (but FCI and Molex ones from Digikey show up as the correct
Is anyone from Verizon available to help me chase down an issue off-list?
Since Sunday morning, we've been seeing what looks to be a bad link
aggregation (10+% packet loss on one IP, 0% on an adjacent IP) to all of
the networks we control (on various providers, various AS's, various
locations)
Same here, dozens of opengear devices deployed, about half with cellular,
only issue we ever had 1 DOA (not totally dead, but behaving really badly)
unit and they sent an overnight replacement since we were on the road
visiting a remote site.
On Fri, Feb 21, 2014 at 10:25 AM, Kenneth McRae
In what world is Verizon an XO customer?
But I think the whole premise of blaming XO is broken, just because your
traceroute shows inbound to Netflix via XO does not mean Netflix is sending
bits to you via XO. If you are sitting on AS701, Netflix certainly has
many routes with aspath length = 2
Isn't this most likely a side effect of MPLS tunneling and the 93ms jump
there is actually the trans-atlantic segment? All the european hops
following it are very close in latency to hop 11.
On Mon, Nov 3, 2014 at 5:14 PM, William Herrin b...@herrin.us wrote:
On Mon, Nov 3, 2014 at 4:15 PM,
APC does make some 'half rack' PDU's that take a C20 inlet so they could
hang off a C19 outlet on another PDU:
http://www.apc.com/resource/include/techspec_index.cfm?base_sku=AP8858displayList=ALLpage_type=displaybasicprinter_friendly=yes
We have >100 AT units deployed and about 35 Verizon units and have had
virtually no issues with call home via openvpn. All opengear ACM7xxx
series.
We are using machine to machine plans from marketplace.att.com. Used to be
a great deal, the new plans are still “fair” and better than standard
Anyone have a contact for fixing Hotstar US geoip issues? We have a newer
block that they seem to be filtering, other blocks are fine. No luck
through their support and they seem to be 100% Akamai so no peeringdb/etc
entries.
Thanks,
Brian Loveland
Starry AS27611 & AS395354
Is this well known? Getting lots of reports of 50% packet loss to anything
behind AS15169 from FiOS, including 8.8.8.8
12 matches
Mail list logo
