OpenFlow 1.0 support on Juniper MX240 with JunOS 12.3

Juniper have added OpenFlow to JunOS 12.3

Do you have a spare MX240 lying around? Chuck a copy of JunOS 12.3 on it and you can get Openflow 1.0 up and running and have a play.

Details

I had a skim over the documentation (download from DropBox), and a few things jumped out at me:

• Fairly full OF1.0 implementation. I don't have a spare MX240 to test, but it would appear that everything is handled in hardware (not sure how Junipers could do otherwise tbh)
• Supports multiple VLANs - if these can be turned on and off from the controller then this would be awesome (let me know if you find this out)
• Doesn't handle buffered packets - make sure your controller can handle OFPT_PACKET_IN messages that don't send a buffer ID (current version of POX doesn't do this?, but the betta branch does)
• Doesn't handle TLS connectivity to the controller - not the end of the world, but I'm curious as to why this was done
• Doesn't do anything related to STP... who cares?
• Only supports MX240s...

This looks like a great start, well done Juniper! Here's my list of requests for the next iteration:

• Support more than one device :) MX80's would be great, also looking to see what the EX series implementation looks like
• Buffered packets! Everyone else does this, and it greatly speeds up the flows-per-second bottleneck between the switch and controller

That's pretty much all from me. OF1.1 support (or 1.3 as this is where everyone is going) would be awesome so we can drive MPLS, but other than that, this is fantastic news.

Update

It looks like it's not quite ready for RouteFlow - Joe Stringer pointed this out in the notes:

• If the controller pushes a flow with a set source MAC address action, the router cannot

   program the corresponding filter term. However, CLI show commands still display the

  flow with the associated action, and the device sends an OFPET_FLOW_MOD_FAILED

 error message with an OFPMFC_UNSUPPORTED code to the controller. [PR 838699]

• If the controller pushes a flow with a set destination MAC address action, the router

   cannot program the corresponding filter term. However, CLI show commands still

  display the flow with the associated action, and the device sends an

 OFPET_FLOW_MOD_FAILED error message with an OFPMFC_UNSUPPORTED code

to the controller. [PR 838709]

• If a flow contains a set IP source address action or a set IP destination address action,

   the device rejects the flow and sends an OFPET_FLOW_MOD_FAILED error m

In other words, no MAC/IP address rewrites = no routing :(

Disclaimer

I've been told that this info and the linked documents are public... If Juniper isn't happy with this, please get in touch and I'll fix it.