9 | | || '''Function/Step''' || '''State''' || ''' Ticket ''' || '''Notes''' || |
10 | | |
| 9 | || '''Function/Step''' || '''State''' || ''' Ticket ''' || '''Notes''' || |
| 10 | ||1. Allocated VLANs || || || || |
| 11 | ||2. Ad reflects allocation || || || || |
| 12 | ||3. Add/Modify/Delete VLAN || || || || |
| 13 | ||4. Modify the endpoints || || || || |
| 14 | ||5. Bandwidth allocation || || || || |
| 15 | ||6. Ad of bandwidth allocation || || || || |
| 16 | ||7. Traffic statistics || || || || |
| 17 | ||8. Operator delete VLANs || || || || |
| 31 | |
| 32 | These functions are important for operators in GENI, so that they can track traffic to and from their site through GENI aggregates. |
| 33 | Operator access to OESS information will be verified (note the operator is not the same as the experimenter): |
| 34 | |
| 35 | === 1. Allocated VLANs for use by Aggregate responsible for cross-connect path === |
| 36 | |
| 37 | === 2. Verify Aggregate Advertisement reflects the VLAN allocation === |
| 38 | |
| 39 | === 3. Add/Modify/Delete VLANs === |
| 40 | Add/Modify/Delete the VLANs available for the aggregate, verify Advertisement reflects change for each add/modify/delete operation. |
| 41 | |
| 42 | === 4. Modify the endpoints for a VLAN === |
| 43 | Modify the endpoints for a VLAN and verify Advertisement reflects change. |
| 44 | |
| 45 | === 5. Bandwidth allocation for cross-connect === |
| 46 | |
| 47 | === 6. Aggregate Advertisement of bandwidth allocation === |
| 48 | |
| 49 | Verify that Aggregate Advertisement of bandwidth allocation reflects configured bandwidth allocation defined by operator. |
| 50 | |
| 51 | === 7. Traffic Statistics === |
| 52 | Traffic statistics for all GENI traffic to/from an operators site on OESS |
| 53 | |
| 54 | === 8.Operator delete VLAN === |
| 55 | Operator ability to delete existing VLANs that terminate at their site (the operator is not the experimenter who set up the connections). |
| 56 | |