Oracle L2VPN Services
In a Layer 2 FastConnect service, Tata Communications provides a point-to-point EoMPLS tunnel with Dot1Q tagging (ERS/EVPL, VLAN non-transparent), and you manage IP addressing and BGP directly with Oracle. Layer 2 requires two OCI/VC-IDs (primary and secondary) to maintain Oracle’s standard dual-circuit resiliency, and failover is yours to manage.
How Layer 2 delivery works
For a Layer 2 service, Tata Communications configures an EoMPLS tunnel from your terminating GVPN PE router to the Oracle-interconnect GVPN PE router. The Tata Communications network acts purely as a Layer 2 tunnel (L2VPN on ERS/EVPL): Oracle supports Dot1Q (C-tag), so Tata Communications applies Dot1Q tagging to hand your traffic off to Oracle, and you configure IP addressing and BGP on your CPE and in Oracle. Your last mile must support Dot1Q to connect to the Tata Communications PE, and Tata Communications assigns a different VLAN for each of the primary and secondary services.
Resiliency on Layer 2
Two BGP sessions (primary and secondary) are established by default to match Oracle’s standard resiliency, which means you create two OCI/VC-IDs – one per circuit. Traffic failover is managed by you, using routing between your CPE and Oracle.
Layer 2 limitations
-
Two VLANs/VCs are created where you subscribe to a redundant (dual-circuit) service.
-
VLAN transparency is not supported – The EoMPLS tunnel runs in ERS/EVPL mode.
-
Single-tag 802.1Q only – QinQ (EWS mode) is not supported on the direct Layer 2 service.
-
Multi-site Layer 2 (VPLS) is not supported.
Layer 2 over the partner exchange
Where the Layer 2 service is delivered over the partner exchange, the EoMPLS tunnel runs to the partner-connected GVPN PE, and the partner exchange uses QinQ (S-tag + C-tag). The customer-managed IP and BGP model is otherwise the same.