| Slide 1 |
| Why do we need Dynamic Circuits ? |
| Fermilab was an early implementer of E2E circuits | ||
| We are an early user of E2E dynamic circuits as well | ||
| A natural evolution in line with developments in E2E technology | ||
| Our traffic patterns (high impact, bursty, & frequent) lend themselves to E2E circuits | ||
| High bandwidth paths are highly desirable | ||
| Want to minimize impact on general use network paths | ||
| Economics expected to play a big role: | ||
| Lower cost of DC service vs dedicated link makes it attractive | ||
| User Interface with Lambda Station |
| Multiple API calls or functions (~25) provided as WEB Services via SOAP protocol to make a reservation and activate service, query status and etc | ||
| Interactively by a human through Web form | ||
| Programmatic via SOAP (LS awareness in application) | ||
| FtWatch traffic sensing tool (netflow analysis) | ||
| Multiple deployment scenarios: dynamically configurable LANs, pre-configured, static and dynamic DSCP | ||
| Interfacing with Dynamic Circuit Services |
| Lambda Station architecture includes a WAN control plane module | ||
| DCN service is available as Web services via OSCARS API library. | ||
| To place a call is not the problem | ||
| A solid and sophisticated protocol is more complicated. | ||
| This is very much a work in progress | ||
| Some areas of needed effort |
| Verification that path is actually established | ||
| Regular circuit heartbeat | ||
| Circuit characteristics modification: | ||
| Extension of existing reservations | ||
| Change in requested bandwidth when ticket is active | ||
| A capability to identify the current state of the circuit to destination | ||
| Lookup services oriented for user's applications | ||
| For more details... |
| Please check the information available at www.lambdastation.org | |