Attached is a PDF of a visio diagram of the single rack layout.
A couple of things about the diagram-
One blade per chassis is on the 10G “control network” – A1 and B1 to be used as controllers\ and C1 as the monitor/SNMP poller.
The blade chassis are connected via 1G to the control network as well (console/ssh access)
Initial configuration will not connect the data networks to the production network
Later testing needs to be done to run load over the OpenFlow VRF
In addition to our current ongoing activity around load testing (both traffic and rules) we need to start work on testing the general use cases.
Use Case #1 – Expressway #1
- Normal traffic will flow over the A links between switches
- Traffic from A2 to B2 will be routed over the B link between switch #1 and switch #2
This will require a fairly simple rule – but it could be based on MAC address, source/dest IP, port, …
I think we should load up traffic on the A link and then show that we can independently load up traffic on the B path. We should also plan to put rule set updates/stress on the servers as well.
Use Case #2 – Expressway #2A
This is similar to above but traffic has to flow through two switches
- Traffic from A2 to C2 will flow over the B paths
Use Case #3 – Expressway #2B
This is similar to #1 – but the path is between switch #1 and switch #3 and bypasses switch #2
- Traffic from A2 to C2 will flow over the C path
Note that most of use cases for general research support are bypass connections – either to specific external resources such as in a science DMZ or to internal resources such as file shares.
I went to visit the rack this morning, and took a few pictures and traced some cables. Now I’m trying to describe it all.