http://www.openswitch.net/documents/user/hardware-compatibil...
I could see us switching from Cumulus Linux to Open Switch, with that hardware support, and if Open Switch stays open source. We'd likely even pay for support, if cost competitive.
$5,795.00
Essentially, one of the aims of OpenSwitch is to build a cohesive API around a wide set of Linux networking tools and daemons, and build a broad community to make it happen.
You could run it on OpenSwitch as the program/module which talks with a controller.
https://git.openswitch.net/cgit/openswitch/ops-arpmgrd/tree/...
/* Build hash key for a given vrf name and ip address */
static int
get_hash_key(char* vrf_name, char *ip, char *key)
{
sprintf(key, "%s-%s", vrf_name, ip);
return strlen(key);
} /* get_hash_key */
Definitely not thinking hard about security over there.
Just check Herb Sutter's talk at CppCon 2015, to the question who uses static analyzers, about 1% of the audience said yes.
But, what contexts is this function used in? Is it supposed to be one-way at all? If not, then this is just a simple way of distributing vrf/ip pairs into buckets. Still smells funny, though.
EDIT: This comment looks like I'm defending the implementation here. I'm not. Seems like it'd me more uniform to just add the bytes in the vrf/IP pair and mod them with something. Seeing a hyphen in the format string of sprintf() is really weird, considering that just he string's length is being used.
Again, assuming this is in no way security-related, then this is just a general, run-of-the-mill WTF.
I didn't even go looking for bad code. I was just curious to see what language they were using. This was near the top of the first file I looked at.
The code looks like C code circa 1990. If a first glance turned up this, what else bad is in there?
I could see this getting traction if they announced it was compatible with some of the newer switches
And honestly, I really don't know how Cisco's Nexus line is going to survive at all. They will coast for a while on the population of Cisco certified engineers that don't want to learn new things, but it is literally cheaper for us to buy new hardware and support contracts than it is to renew our Cisco support contract. And the alternatives are far more capable than NX-OS for our ops people.
The Nexus line is effectively dead, as I see it.
When I asked him what was going on, he pointed out that he only responds to bids he can win. I told him there were no servers in that opportunity, and he went on to discuss that, from a sales point of view, I have a better chance of pushing servers anyway, than pricing Cisco against HP networking. That's from one of their own guys, and it says a lot.
I am going to guess large high throughput switches and some degree of software defined networks that knock putting your printers on one C-network and your servers on another into a cock hat
Apart from raw power, is there some way I can reconfigure my network without moving a cable that I previously could not?
(It's late, so just to be sure, I'm not trolling)
One area where a lot of smarts are needed needed, for example, is making sure that you're intelligently routing encrypted packets to the right machines without reverting to a broadcast to every router, switch, and machine in the DC.
I've also heard a lot about people running brand new untested protocols (like TCP replacements) right alongside traditional protocols through SDN.
I'm probably going to do a much worse job of explaining things than the guys who presented at the Open Networking Summit [1]. I highly recommend giving the keynotes a listen.
[1] https://www.youtube.com/user/OpenNetSummit
Edit: I do think this relates to SDN more than a traditional router/switch OS, based on the comments about "traditional and programmatic, declarative control plane." Either way, though, the link above is definitely good stuff.
It provides open interfaces to interact with the switch through several means like OVSDB, REST API ... or CLI. OpenFlow is not supported yet although will be in near future.
Since it's open source, it also gives you the opportunity to run other agents in the switch control plane ... which is hardly possible with IOS or JunOS.
Github mirroring will be set up in about week.
If you want a bad network solution check out the LG IPECS line of network gear.
This is just a land grab by HP.
Isn't this just another move to sell more switches?
Will there ever be code for some of the older MIPS based switches?