When I’m Asked What The Next 5 Years of Networking Will Look Like

June 3, 2013 1 Comment

Enter your comment here...

Fill in your details below or click an icon to log in:

Email (required) (Address never made public)

Name (required)

Website

You are commenting using your WordPress.com account. ( Log Out / Change )

You are commenting using your Twitter account. ( Log Out / Change )

You are commenting using your Facebook account. ( Log Out / Change )

Connecting to %s

@SystemMTUOne For whatever reason, red is Layer 2 and blue is Layer 3 for me. I think it'd be a shade of blue. 1 day ago
Occasionally going over IEEE and IETF docs/standards/drafts is interesting. TIL that there is an IEEE open standard… twitter.com/i/web/status/1… 1 day ago
RT @STDeltaShift: Bumping because I am still damn pleased with how this turned out. 2 days ago
@xxxliquidacion @Slypher369 @stevie_wond3rs @PeterZeihan We had it for Vietnam most recently in the US, but that wa… twitter.com/i/web/status/1… 1 week ago
@dcuplink_ @rawcode Yup, that’s a limitation of link aggregation (IEEE 802.1AX, formerly 802.3ad). Route via IP has… twitter.com/i/web/status/1… 1 week ago
@dcuplink_ @rawcode In terms of dividing up packets between available links, it's purely Link Aggregation. LACP can… twitter.com/i/web/status/1… 1 week ago
@dcuplink_ @rawcode I'm not sure what you mean about splitting. But in terms of what the OP is talking about, divid… twitter.com/i/web/status/1… 1 week ago
@nickpowpow In the DC? Automation. Almost entirely driven by EVPN. 1 week ago
@dcuplink_ @rawcode LACP doesn’t pick the hashing mechanism, it only checks to make sure the right device is plugged into the right device. 1 week ago
@dcuplink_ @rawcode One correction: you’re talking about Link Aggregation, not LACP. LACP does not divide traffic a… twitter.com/i/web/status/1… 1 week ago