Hey all,
I'm wading outside of my comfort zone and need some clue. I've been recently scratching the surface of OpenFlow and general SDN stuff I normally don't work with (yet) and had some idea pop in my head. I work at an ISP and was wondering if any of you out there were using open source SDN controllers and whitebox gear on your border with an upstream AS. As I've been reading a little more deeply, I just thought it would be killer to be able to power up a whitebox switch with somewhat limited TCAM (124k IPv4 entries for example) and an open source NOS and have an OpenFlow controller sitting behind it to do the actual route lookup heavy lifting for it. For example, a new packet arriving on the OpenFlow whitebox switch with a unique source/destination combination could be queried against the OpenFlow controller to see what to do with it, like which port to egress, or next hop IP, or MPLS next hop label, or whatever configured policy treatment, and give those flow entries a hard timeout so the TCAM stays below the maximum.
Does this sound crazy? Are any of you doing something vaguely like that? Most of what I'm reading is heavily DC architecture focused, but I'm more interested in the network border, AS to AS kind of interaction with big tables rather than leaf/spine Clos type of stuff.
I've read a bit about the early SDN controllers like NOX, POX, Beacon, but wanted to know what the "new hotness" is these days. I guess a good question to ask is, what should I *not* bother with at all?
Any other input or direction would be greatly appreciated!
No comments:
Post a Comment