1 / 9

ALICANTE UC2 DEMO : Unicast VCANs

ALICANTE UC2 DEMO : Unicast VCANs. WP6- oriented- UC2 DEMO. UC2 Demo - Unicast VCAN Management. Note: This presentation explains the steps demonstrated in the Unicast-demo movie Objective:

arnaud
Télécharger la présentation

ALICANTE UC2 DEMO : Unicast VCANs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ALICANTE UC2 DEMO : Unicast VCANs WP6- oriented- UC2 DEMO

  2. UC2 Demo - Unicast VCAN Management • Note: This presentation explains the steps demonstrated in the Unicast-demo movie • Objective: • Management and Control Plane: demonstrate the actions to establish unicast, CA VCANs in multi-domain environment • Data Plane : demonstrate the QoS capabilities – of the unicast VCAN in a congested network • Entities involved • Bucharest Pilot • Service Provider • 3 x Core Network Domains • 3 x CAN Managers - one per network domain • 3x IntraNRMs - one per domain ALICANTE final Review

  3. UC2 Demo: Unicast VCAN Management • DEMO – The VCAN establishment is named “Step 0” in the chain of steps of the UC2 • SP • Generates a VCAN Create request ( SLS proposed) • Sends the request to the selected initiator CAN manager ( iCANMgr) • iCANMgr • Process the VCAN Create request • Tries to map the requested VCAN on the existing networking resources • Determines involved Core Network Domains • Collects resources from the involved CAN Mangers • Runs a combined algorithm ( QoS constrained routing, admission control and resource reservation ) for VCAN mapping • If enough resources →the request is accepted • Communicates results to involved CAN Managers • SP • Receive the confirmation • Accepts it and records the new VCAN • 1CANMgr • Finalize the negotiation by triggering recording of the new VCAN data in DBs • Triggers VCAN installation ( at SP explicit request or as specified in the SLS) ALICANTE final Review

  4. Virtual network resources in topology matrix- Bucharest Pilot Virtual trunks between MANEs • MPLS paths • DiffServ QoS configured statically Dst MANE–M22 Src MANE-M13 ALICANTE final Review

  5. VCAN Creation Signaling Service Provider CANMgr2 Install VCAN VCAN1 P1 VCAN Create request IntraNRM2 VCAN Create response VCAN Create request VCAN Create Response VCAN1 P1 Configure Ingress MANE VCAN1 P1 CANMgr1 Install VCAN IntraNRM1 Configure Ingress MANE Simplified signaling diagram ALICANTE final Review

  6. Video - Story • Interdomain path throughout Domain 1 and Domain 2 • Source located in Domain 1 – Access Network 10.1.7.0 (SRC Addr = 10.1.7.14) • Destination located in Domain 2 – Access network 10.2.9.0 (Dest Addr=10.2.9.14) • A movie is sent from source to destination • movie received with good quality • Initially, without VCAN, the movie is sent as Best Effort traffic • The movie’s path is flooded with noise traffic → video quality affected • A new VCAN is created from the SP management interface – EF class of service • The VCAN pipe covers the movie’s path • The movie packets will be prioritized by the VCAN’s queues inside the domains • The movie quality is good when flooded with noise traffic ALICANTE final Review

  7. Video – Results illustrated • The policer and clasifiers rules on the Ingress Mane Routers • MANE13 – e125 in Domain 1; MANE 21 – e121 in Domain 2 • Before and after the VCAN is created • The movie packets marking • Marked as BE outside and inside the domain –without VCAN • Marked as BE outside domain and as EF inside domain – with VCAN • The noise traffic which is flooded on the VCAN ‘s pipe segment • The noise traffic is generated with iperf application • Generates from e131 machine in Domain 1 and ends on e121 machine in Domain 2 • Queues load • Video and noise traffic are inserted in BE queue – without VCAN • Video is inserted in EF queue, while noise traffic is inserted in BE queue – with VCAN • VCAN installation in the SP database is illustrated • The VCAN table – contains the VCAN’s parameters • The VCAN pipe segments table – contains the pipes’ segments ALICANTE final Review

  8. Video: Data Plane - no VCAN IP TOS=0 Good quality Bad quality Noise traffic MPLS EXP=0 IP TOS=0 MPLS EXP=0 IP TOS=0 ALICANTE final Review 14 Oct 2013

  9. Video: Data Plane - with VCAN VCAN1 P1 IP TOS=b8 Good quality Good quality Noise traffic VCAN1 P1 MPLS EXP=1 VCAN1 P1 IP TOS=b8 MPLS EXP=1 IP TOS=0 ALICANTE final Review

More Related