Opened 10 years ago
Closed 10 years ago
#140 closed (fixed)
OpenFlow over stitched connection to Rutgers fails due to missing flowvisor proxy
| Reported by: | lnevers@bbn.com | Owned by: | asydney@bbn.com |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Experiment | Version: | SPIRAL6 |
| Keywords: | confirmation tests | Cc: | |
| Dependencies: |
Description
The Rutgers InstaGENI site is not a meso-scale site and confirmation testing for OpenFlow? at this site use a stitched connection back to GPO and configures an OpenFlow? Controller for the link.
However the Rutger OF switch never connects to the configured controller. This may be due to the site not having a proxy configured on the flowvisor host, which is how the controller connection is usually allowed.
This issue is blocking to confirmation testing for the Rutgers rack.
Change History (4)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Both Chicago and Rutgers look fine - what controller IP are you testing? Perhaps there is some other reachability problem.
comment:3 Changed 10 years ago by
Just checked and found connections to the host controller where not being accepted. After a reboot of the controller host the flows were installed without problem. Running tests now for Chicago, once I complete the tests for Rutgers, I will close the ticket.
comment:4 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Able to run OpenFlow over a stitched link at both Rutgers and Chicago. Problem is solved. Closing ticket.
The Chicago InstaGENI rack is also not able needed proxy to allow connection to remote experimenter OpenFlow controller.