Operational Support for DCN

Internet2 envisions three distinct types of operational support that will be needed for DCN.

 Internet2 DCN Operation

For the Internet2 DCN, operational support is managed at a first and second level by the NOC. The NOC uses perfSONAR as its base tool for monitoring and debugging circuit problems. It uses a weather map to see links and link usage, and circuit management tool to see all circuits that are currently up and to track circuits that have terminated.  The NOC has developed some of its own tools for tracking problems, debugging circuits, and interoperating with other domains.

MultiDomain Operational support

For the "ideal" global DCN, there will be a set of agreements between networks. These will be similar to, but not exactly the same as, those for IP networks. In general, it is likely that there will be network providers, such as Internet2, that interconnect with other global providers, such as ESNet or GEANT2. Internet2 will also connect to local providers, such as RONs, and RONs will connect to campuses (and perhaps campuses to departments). This is similar to peering, but naming and path computation is done in a hierarchical way, following what is proposed by ASON.

Networks that have DCN agreements will share information about staff for debugging and other administrative requirements. Internet2 has agreements only with networks that are able to provide IDC protocol interoperation and also provide perfSONAR-DCN capabilities and debugging support.

Operational Software Management

Operational Internet2 software (including DRAGON, Ciena, IDC, and perfSONAR) is managed and deployed by the NOC. The NOC interfaces with software providers and requires software to be tested alone and in conjunction with other software.