1. Ethernet Demarcation Devices
Ethernet WAN Services
Ethernet Demarcation Devices
Circuit 'Turn-Up' Testing & In-Service Assurance for Layer-2 and Layer-3 Network infrastructures

2. Ethernet (L-2) Network - Typical Scenario
click anywhere to continue...
Network Operation Centre (NOC) Console
Value-Added
Services
Management
Access
Ethernet
Service Provider
Core Network
Management
Access
Infrastructure Carrier
Ethernet Circuit
Infrastructure Carrier
Ethernet Circuit
Customer LAN
Site A
Customer LAN
Site B
Service Provider's
Ethernet Demarcation Devices
Ethernet Service Providers typically offer End-to-End or Core-to-Edge services for their customers, which frequently involve infrastructure, or at the least simple 'tail circuits', from 3rd party Carriers. In order to manage configurations and monitor both customer site access and network performance right out to the edges of the network, Ethernet Demarcation Devices (EDDs) are deployed at customer connection points, managed from the Service Provider's Network Operations Centre (NOC).

3. Ethernet Service Commissioning Tests
click anywhere
to 'build' then continue...
4. Results at A can be viewed from NOC console or transmitted to the NOC for inclusion directly to 'birth certificate' documentation
Network Operation Centre (NOC) Console
1. Log in to EDD at Site A
Ethernet
Service Provider
Core Network
3. Ethernet (L-2) Test traffic generated at A is looped back at B (SA/DA swapping, via 'SAM' hardware) for analysis back at A
Customer
Site A
Customer
Site B
Infrastructure Carrier
Ethernet Circuit
Infrastructure Carrier
Ethernet Circuit
2. Set-Up RFC2544 or Y.1564 Test in relation to customer SLA for service(s) between sites A and B
Service Providers need initially to demonstrate that they have provisioned circuits in accordance with their customers requirements, so use this process for comprehensive Service Level Agreement (SLA) verification testing.

4. Subsequent 'In-Service' Monitoring
click anywhere
to 'build' then continue...
NOC Console
Log-In to set up
Agreed Service Parameters
(SLA)
Pro-active SNMP 'Trap'
alarm sent to NOC if
agreed SLA not met
Ethernet
Service Provider
Core Network
Y.1731 protocol exchanges time-stamped test packets in order to monitor service parameters relative to pre-defined customer SLA
Customer
Site B
Customer
Site A
Infrastructure Carrier
Ethernet Circuit
Infrastructure Carrier
Ethernet Circuit
Subsequently, Service Providers require to monitor that SLA performance metrics continue to be satisfied 'in-service'. Pro-active alarming of potential 'SLA breach' conditions enable quick and effective remedial action, to the benefit of both Service Provider and customer.

5. Testing with an IP Network infrastructure?
NOC Console
click anywhere to continue...
Management
Access
Service Provider
Core Network
Management
Access
MPLS (Layer-3, IP) Infrastructure
Customer
Site A
Customer
Site B
Edge/Access Network
(Typically Layer-2)
Edge/Access Network
(Typically Layer-2)
Service Provider's
Ethernet Demarcation Devices
If the Service Provider is provisioning a Layer-3 network, typically an IP-VPN, but the customer is deploying their own Routers, then the Service Provider often still requires management visibility at the customer hand-off point. To enable End-to-End performance testing and monitoring, then Layer-2 test functionality alone within the Demarcation Devices is insufficient. Ethernet MAC packets cannot traverse Layer-3 elements of the network and Layer-3 (IP) packets are required. RFC2544 and/or Y.1564 testing is agnostic to packet type, so IP-addressed frames can just as readily be used, provided that the EDDs support this, along with the necessary IP configuration tools and processes (e.g. ARP for IP Gateway address mapping). Metrodata will support this functionality in the FCM9003 and FCM9005 EDDs.

6. And for in-service performance monitoring?
click anywhere
to 'build' then continue...
Log-In to set up
Agreed Service Parameters
(SLA)
NOC Console
Pro-active SNMP 'Trap'
alarm sent to NOC if
agreed SLA not met
Service Provider
Core Network
TWAMP protocol exchanges time-stamped test packets in order to monitor service parameters relative to pre-defined customer SLA
TWAMP-light
controller
responder
Customer
Site A
MPLS (Layer-3, IP) Infrastructure
Customer
Site B
Edge/Access Network
(Typically Layer-2)
Edge/Access Network
(Typically Layer-2)
For networks including Layer-3 (IP) elements, the 'Two-Way Active Measurement Protocol' (TWAMP) performs a similar role to that of Y.1731 for 'Layer-2 only' networks, i.e. to monitor Latency and Jitter performance characteristics, providing alarms in the event of breaches of the customer's SLA criteria.

7. Metrodata Ethernet Demarcation Devices
FCM9002
Low cost, flexible EDD including single-level VLAN push/pop and support for circuit set-up testing (RFC2544 and Y.1564) plus Y.1731 for in-service Assurance, for Layer-2 Ethernet services only
FCM9004
Advanced Layer-2 EDD, supporting multi-level VLAN push/pop, comprehensive multi-flow testing and in-service Assurance
FCM9003 (from Q3, 2015)
Adds IP-addressing to the FCM9002, for RFC2544 and Y.1564 testing, plus TWAMP-light for in-service monitoring, for Layer-2 and/or Layer-3 networks
FCM9005 (from Q3, 2015)
Adds IP functionality similarly to the FCM9004
Metrodata's FCM9003 & FCM9005 platforms include both Layer-2 and Layer-3 circuit testing and in-service monitoring regimes, offering deployment flexibility for each of Layer-2, Layer-3 & hybrid networks.

8. Ethernet WAN Services Thank you!