Serviço Experimental de CIrcuitos aPrOvisionados dinamicamente (SE-CIPÓ)

Skip to end of metadata
Go to start of metadata
INTRODUCTION

Circuit Reservations using MEICAN

This document contains a procedure to verify the compatibility of the RNP MEICAN tool with different AutoGOLE domains. For step by step instructions, please refer to the Circuit Reservation Procedure from MEICAN User Guide. The first test below is supposed to work on every domain. If this first test fails, you can request support to RNP MEICAN Team. The remaining tests require the uPa to support some specific features and may fail if they are not supported or if implemented differently than expected. Please share your test details and results at the end of the procedure.

INTRA-DOMAIN TESTS

Intra-domain Tests

  1. Simple Circuit Reservation:

    • Description: A simple reservation request;

    • Procedure: Create an intra-domain circuit selecting both the source and destination Service Termination Points (STP) in your own domain;

    • Expected outcome: This test is expected to work on every domain and results in a NSI service ID for the requested service. If this fails, please contact the RNP MEICAN Team (gre@rnp.br) to request support so we can identify the issue.


  2. Circuit Reservation Cancellation:
    • Description: Forcing a circuit to end immediately;

    • Procedure: After the circuit from test 1 is Provisioned and Activated, terminate the circuit using the “Cancel” button at the Circuit Status page. Confirm that the circuit was terminated at your local uPa;

    • Expected outcome: The circuit should be completely terminated at the local uPa.


  3. Circuit Reservation Expiration:

    • Description: Forcing a circuit to end immediately;

    • Procedure: After the circuit from test 1 is Provisioned and Activated, terminate the circuit using the “Cancel” button at the Circuit Status page. Confirm that the circuit was terminated at your local uPa;

    • Expected outcome: Repeat test 1 using a close end time. A couple of minutes after the end time confirm that the circuit was terminated at your local uPa.


  4. Circuit Reservation Using a VLAN Range:

    • Description: If you don’t need a specific VLAN id to be used, NSI support using a VLAN range instead to let the uPa select an available vlan from the range (NOT intended to request a VLAN range);

    • Procedure: Repeat test 1 using a range in the VLAN field. Ex: 1779-1799;

    • Expected outcome: Follow the messages history at circuit status page. At the “Reserve requested” message MEICAN is sending the selected VLAN range to the uPa through the NSI aggregator. At the “Reserve confirmed” message, the uPa has already computed and selected an available VLAN for each STP.


  5. Modification of Start Time of an Inactive Circuit (Reserved but not yet Activated):

    • Description: Verify that the modification of the circuit start time is supported;

    • Procedure: Repeat test 1 and before the circuit start time (activation), use the “Edit” button at the Circuit Status page and select a new start time after the current start time of the circuit;

    • Expected outcome: The modification of the circuit should be propagated to MEICAN and at the local uPa.


  6. Modification of Bandwidth of an Inactive Circuit: 

    • Description: Verify that the modification of the circuit bandwidth is supported;

    • Procedure: Repeat test 1 and before the circuit start time (activation), use the “Edit” button at the Circuit Status page and select a new end time after the current end time of the circuit bandwidth;

    • Expected outcome: The modification of the circuit should be propagated to MEICAN and at the local uPa.


  7. Modification of End Time of an Inactive Circuit: 

    • Description: Verify that the modification of the circuit end time is supported;

    • Procedure: Repeat test 1 and before the circuit start time (activation), use the “Edit” button at the Circuit Status page and select a new end time after the current end time of the circuit;

    • Expected outcome: The modification of the circuit should be propagated to MEICAN and at the local uPa.


  8. Modification of Ending Time of an Active Circuit: 

    • Description: Based on OSCARS implementation, the end time of the circuit should be modified without interrupting the circuit. Verify that the modification of the end time of an active circuit is supported without interrupting it;

    • Procedure: Repeat test 1 and before the circuit expires, use the “Edit” button at the Circuit Status page and select a new end time after the current end time of the circuit;

    • Expected outcome: The modification of the circuit should be propagated to MEICAN and at the local uPa.


  9. Modification of Start Time of an Active Circuit:

     

    • Description: Based on OSCARS implementation, the start time of the circuit can be modified only if the circuit is inactive. MEICAN will automatically Release the circuit, request the modification and Provision it again;

    • Procedure: Repeat test 1 and before the circuit start time (activation), use the “Edit” button at the Circuit Status page and select a new start time after the current start time of the circuit. If this behavior is not appropriate for your uPa implementation, please let us know;

    • Expected outcome: The modification of the circuit should be propagated to MEICAN and at the local uPa.


  10. Modification of Bandwidth of an Active Circuit:

    • Description: Based on OSCARS implementation, the bandwidth of the circuit can be modified only if the circuit is inactive. MEICAN will automatically Release the circuit, request the modification and Provision it again. If this behavior is not appropriate for your uPa implementation, please let us know;

    • Procedure: Repeat test 1 and before the circuit start time (activation), use the “Edit” button at the Circuit Status page and select a new end time after the current end time of the circuit bandwidth;

    • Expected outcome: The modification of the circuit should be propagated to MEICAN and at the local uPa.


INTER-DOMAIN TESTS

Inter-domain Tests  (STPs at different source and destination domains)

  1. Establishing One Circuit Between Two Domains:

    • Description: Creating a circuit between different domains;

    • Procedure: Create an interdomain circuit selecting one STP from your own domain and another from a neighbor domain;

    • Expected outcome: The circuit should be Reserved and Provisioned in both domains. This test will fail if any of the domains is unavailable or if the peering with them is not correctly established.


  2. Establishing One Circuit Between Multiple Domains:

     

    • Description: Creating a circuit between multiple different domains;

     

    • Procedure: Create an interdomain circuit selecting one STP from your own domain and another STP from a domain your aren’t peering with directly;

    • Expected outcome: The circuit should be Reserved and Provisioned in all domains. This test will fail if any of the domains is unavailable or if the peering between them is not correctly established.


  3. Define the Waypoint /Explicit Route Object (explicit circuit path): 

  • Description: It is possible to detour a circuit defining a Waypoint where the circuit should obligatory pass by;

  • Procedure: Identify an STP outside your domain that can be reached using two different paths. Identify an intermediate STP from each path that is not part of the other path. Create two circuits and select on each of them a different intermediate STP as a waypoint;

  • Expected outcome: Each circuit will have a different path passing by the selected intermediate STP (Waypoint).


OTHER TESTS

Future Tests

  • Explicit intradomain path using internal URNs (Needs testing)

  • Zero Bandwidth (Currently Unsupported)

  • Undefined start time (Currently Unsupported)

  • Undefined end time (Currently Unsupported)

  • Protected path (Currently Unsupported)

  • No labels