15.01.2015 Views

REAL Ethernet Services - VUMS DataCom

REAL Ethernet Services - VUMS DataCom

REAL Ethernet Services - VUMS DataCom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>REAL</strong> <strong>Ethernet</strong> <strong>Services</strong><br />

Presentuje:<br />

Zdeněk Zapletal<br />

zdenekz@datacom.cz<br />

Reliable. Economical.<br />

Accountable. Limitless


Anotace<br />

• <strong>Ethernet</strong> is penetrating everywhere, from enterprise LAN to the<br />

carrier core network, in the metro and in the access networks<br />

as well.<br />

• <strong>Ethernet</strong> has its origin in providing LAN network connectivity<br />

and was not originally used to provide services by carrier and<br />

other operators. Although IEEE <strong>Ethernet</strong> protocol is still used,<br />

Carrier <strong>Ethernet</strong> differs from LAN-based <strong>Ethernet</strong>.<br />

• The Metro <strong>Ethernet</strong> Forum (MEF) is a global industry alliance<br />

that develops technical specifications and implementation<br />

agreements to promote interoperability and deployment of<br />

Carrier <strong>Ethernet</strong>. Its mission is to accelerate the worldwide<br />

adoption of Carrier-class <strong>Ethernet</strong> networks and services.<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 2


Anotace<br />

• The MEF has defined Carrier <strong>Ethernet</strong> as a ubiquitous,<br />

standardized, carrier-class Service and Network. MEF<br />

specified five attributes that distinguish Carrier <strong>Ethernet</strong><br />

from familiar LAN based <strong>Ethernet</strong>: standardized services,<br />

reliability, scalability, quality of service and service<br />

management.<br />

• These requirements are turned into reality in a different way<br />

and in different extent by all important data communication<br />

vendors.<br />

• Carrier <strong>Ethernet</strong> services are carried over physical <strong>Ethernet</strong><br />

networks and other legacy transport technologies. We want<br />

to share with you the vision of one of the leading suppliers of<br />

access solutions, RAD Data Communications, and describe<br />

how the company respond to this challenge.<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 3


MEF <strong>Services</strong> Terminology<br />

<strong>Ethernet</strong> Private Line (EPL) is a Metro<br />

<strong>Ethernet</strong> service type defined by the MEF,<br />

providing a point-to-point <strong>Ethernet</strong> connection<br />

between a pair of dedicated User-Network<br />

Interfaces (UNIs). EPL is implemented as a<br />

point-to-point <strong>Ethernet</strong> Virtual Connection<br />

(EVC) which, unlike <strong>Ethernet</strong> Vitual Private<br />

Line (EVPL), does not allow for Service<br />

Multiplexing, i.e., a dedicated UNI (physical<br />

interface) is used to accept all service frames<br />

and map them to a single EVC.<br />

<strong>Ethernet</strong> Private Line (EPL)<br />

Port Based<br />

CE<br />

*UNI<br />

UNI<br />

*NNI<br />

NNI<br />

Carrier <strong>Ethernet</strong><br />

Network<br />

Point-to-Point EVC<br />

CE<br />

UNI<br />

UNI<br />

<strong>Ethernet</strong> Virtual Private Line (EVPL)<br />

CE<br />

ISP<br />

POP<br />

Internet<br />

<strong>Ethernet</strong> Virtual Private Line (EVPL)<br />

service is very similar to a <strong>Ethernet</strong> Private<br />

Line (EPL) service, via a point-to-point<br />

<strong>Ethernet</strong> Virtual Connection (EVC)<br />

between a pair of User-Network Interfaces<br />

(UNIs).However, unlike EPL, EVPL allows<br />

for Service Multiplexing, i.e., multiple<br />

EVCs or <strong>Ethernet</strong> services per UNI.<br />

Service<br />

Multiplexed<br />

<strong>Ethernet</strong> UNI<br />

CE<br />

Service Based<br />

UNI<br />

NNI<br />

NNI<br />

Carrier <strong>Ethernet</strong><br />

Network<br />

CE<br />

Multipoint-to-Multipoint EVC<br />

UNI<br />

UNI<br />

CE<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 4


MEF <strong>Services</strong> Terminology<br />

<strong>Ethernet</strong> Private LAN (EPLAN) is a Metro <strong>Ethernet</strong><br />

service type defined by the MEF, providing<br />

multipoint-to-multipoint <strong>Ethernet</strong> Virtual Connections<br />

(EVC) between User-Network Interfaces (UNIs).<br />

Because EPLAN services implement multipoint-tomultipoint<br />

EVC, multiple locations can be<br />

interconnected using an EPLAN service. EPLAN<br />

Metro <strong>Ethernet</strong> service does not permit service<br />

multiplexing at the User-Network Interface (UNI).<br />

Each location can be a member of one and only one<br />

EVC. If a given location requires connection to a<br />

second EVC, it will require a second UNI.<br />

<strong>Ethernet</strong> Private LAN (EPLAN)<br />

Port Based<br />

CE<br />

UNI<br />

UNI<br />

UNI<br />

CE<br />

UNI<br />

UNI<br />

UNI<br />

CE<br />

ISP<br />

POP<br />

<strong>Ethernet</strong> Virtual Private LAN (EVPLAN)<br />

<strong>Ethernet</strong> Virtual Private LAN (EVPLAN) is a<br />

service type defined by the MEF, permitting<br />

service multiplexing at the <strong>Ethernet</strong> User-Network<br />

Interface (UNI). Because in an EVPLAN service<br />

there are multiple EVCs per UNI, there is no need<br />

for additional UNI when overlapping multiple<br />

closed-user groups.<br />

Service<br />

Multiplexed<br />

<strong>Ethernet</strong> UNI<br />

CE<br />

Service Based<br />

UNI<br />

CE<br />

UNI<br />

UNI<br />

CE<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 5


<strong>REAL</strong> <strong>Ethernet</strong> Access<br />

What does it mean<br />

Reliable<br />

Always on resilient connections with 4 or 5 nines<br />

24/7 E2E network management<br />

Automatic fault isolation<br />

QoS guarantees per class of service (CoS)<br />

Economical<br />

Accountable<br />

Limitless<br />

SOLUTION<br />

Cost-effective customer located equipment (CLE)<br />

High throughput, flexible and scalable data rates<br />

Minimal down-time for servicing and repair<br />

Service level agreements (SLA)-based performance commitments<br />

Granular data rates from 1 Mbps to 1 Gbps<br />

Versatile connectivity options<br />

Consistent service over any infrastructure<br />

Inteligent Demarcation Devices<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 6


Demarcation Device - NTU<br />

(Network Termination Unit)<br />

EVC<br />

CPE ETX<br />

ETX CPE<br />

Operator B<br />

Operator A<br />

Customer Premises<br />

End-to-end OAM<br />

Customer Premises<br />

Points of Demarcation<br />

NTU = Customer Located Equipment (CLE) providing:<br />

• Clear demarcation between provider’s and Customer’s networks – quickly<br />

determine responsibility of service affecting problems<br />

• Operations Administration & Maintenance (OAM)<br />

Allow for end-to-end fault management and performance monitoring<br />

• Traffic management starting at customer premises<br />

• Service Level Agreement Monitoring<br />

Customers demand proof of the SLA contract<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 7


Standard <strong>Ethernet</strong> OAM<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 8


End-to-End <strong>Ethernet</strong> OAM<br />

Continuity Check, Loopback, Link trace<br />

• End-to-End OAM is defined in two standards<br />

• IEEE - 802.1ag defines Fault Management<br />

• Y.1731 – defines Fault Management and Performance Management<br />

New in ETX Version 3.8<br />

• Latest drafts are interoperable for Fault Management<br />

• Standard Fault Management<br />

• Loopback (LB)– Equivalent to IP Ping<br />

New in ETX Version 3.8<br />

• Link trace (LT) – Equivalent to IP Trace route<br />

• Continuity Check (CC)– Indication of connectivity (100msec)<br />

802.3ah (Access Link ME)<br />

CPE E-NTU<br />

E-NTU CPE<br />

Operator B<br />

Operator A<br />

Customer Premises<br />

802.1ag/ Y.1731 (UNI-N to UNI-N ME)<br />

Customer Premises<br />

• RAD’s Performance Management remains proprietary<br />

• Performance Monitoring is RAD Proprietary<br />

• Each EVC can be configured to be RAD Proprietary/Standard<br />

• On a RAD proprietary EVC still replies to LT and LB requests<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 9


End-to-End OAM<br />

Continuity Check (CC) OAM<br />

Customer Premises<br />

Customer Premises<br />

CPE E-NTU<br />

E-NTU CPE<br />

CC Sink<br />

Operator B<br />

Operator A<br />

CC Source<br />

• Connectivity Check messages:<br />

CC OAM Frames<br />

• Defined per EVC, allows for one-way connectivity monitoring<br />

• Sent every 1 second (default) configurable for 100ms, 10 sec, 1 min & 10 min<br />

• Loss of Continuity (LOC) (only at the sink side)<br />

• LOC declared upon 3.5 seconds without receiving CC OAM frame<br />

• Loss of Continuity (LOC) is cleared upon sink side after receiving 2 CC OAM<br />

frames within a window of 3.5 seconds<br />

• Upon CC failure send trap and update active alarm log<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 10


End-to-End OAM<br />

Loopback (LB) OAM<br />

CPE E-NTU<br />

E-NTU CPE<br />

Customer Premises<br />

Operator B<br />

LB OAM Request<br />

LB OAM Reply<br />

MEP = Maintenance-End-Point<br />

Operator A<br />

MIP = Maintenance-Intermediate-Point<br />

MEG = Maintenance Entity Group<br />

Customer Premises<br />

• Standard 802.1ag implementation<br />

• Defined per EVC, allows for non-intrusive<br />

loopback (round trip) connectivity<br />

monitoring, applies to OAM messages only<br />

• Sent from MEP, looped by either MEP or MIP<br />

• LB Failure is declared upon 2 seconds<br />

without receiving the specific LB OAM frame<br />

• Required for performance monitoring<br />

• Upon LB failure send trap and update alarm<br />

log<br />

Service OAM MEPs and MIPs<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 11


End-to-End OAM<br />

Link Trace (LT) OAM<br />

Customer Premises<br />

Customer Premises<br />

CPE E-NTU<br />

Operator B<br />

Operator A<br />

E-NTU CPE<br />

LT Req<br />

LT Resp<br />

• Once a problem detected with CC or LB than LT can be used to<br />

pin point where the problem is<br />

• OAM is sent to the final MAC address and all nodes in the path<br />

that receive the LT request send back LT response, this way the<br />

failure point is found<br />

• Can be used also the resolve disputes when more than 1<br />

network is used<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 12


End-to-End <strong>Ethernet</strong> OAM<br />

Applications<br />

Fault Detection with Connectivity<br />

Check (CC) Messages<br />

No CC within 3.5 sec interval -> RDI<br />

Fault Verification with Loopback<br />

Messages<br />

Fault isolation with Link Trace (LT) messages<br />

Provides L2 path as well as isolation<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 13


<strong>Ethernet</strong> Demarcation Devices<br />

Variety of <strong>Ethernet</strong> Access Solutions<br />

Branch<br />

10BT<br />

<strong>Ethernet</strong> over PDH<br />

RICi-E1<br />

GFP<br />

GbE<br />

<strong>Ethernet</strong> over SDH<br />

ADM<br />

RICi-622GE<br />

RICi-622GE<br />

GbE<br />

Branch<br />

Branch<br />

10BT<br />

RICi-4/8E1<br />

MLPPP<br />

GbE<br />

RICi-155GE<br />

SDH<br />

STM1/4<br />

RICi-155GE<br />

GbE<br />

Branch<br />

EoPDH<br />

Branch<br />

RICi-16<br />

100BT<br />

GFP-VCAT<br />

<strong>Ethernet</strong> over Fiber<br />

ETX-202<br />

F.ETH<br />

GbE<br />

ADM<br />

SDH<br />

STM-1/OC-3<br />

GbE<br />

Egate<br />

Service Provider<br />

Packet Switched<br />

Network<br />

GbE<br />

GbE<br />

IPDSLAM<br />

IPDSLAM<br />

ASMi-54<br />

<strong>Ethernet</strong> over DSL<br />

EFM<br />

Bonding<br />

ATM<br />

LA-210<br />

LA-110<br />

ASMi-54<br />

F.ETH<br />

F.ETH<br />

Branch<br />

Branch<br />

Headquarters<br />

SHDSL.bis<br />

GbE<br />

ETX-202A<br />

GbE<br />

Metro<br />

<strong>Ethernet</strong><br />

GbE<br />

•Extending the reach of the provider’s network<br />

over a variety of access technologies<br />

Branch<br />

•Consistent <strong>Ethernet</strong> service across different<br />

access technologies<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 14


EtherAccess feature-set<br />

Enhanced L-2 <strong>Ethernet</strong> capabilities over any access infrastructure<br />

• EPL/EVPL services, partially EPLAN/EVPLAN (MEF certified)<br />

• Flow base<br />

• Traffic classification and mapping<br />

• CE VLAN ID, P-bit, DSCP, IP Precedence<br />

• Enhanced QoS<br />

• Policing per service (per flow) Dual leaky bucket supporting CIR+CBS, EIR+EBS<br />

• Scheduling – Queues according to Strict priority or WFQ<br />

• Rate limit on the egress port - Conforms egress traffic to specific rate<br />

• OAM<br />

• IEEE 802.3ah – Single Segment<br />

• IEEE 802.1ag – End-to-End<br />

• ITU-T Y.1731 – End-to-End<br />

EFM OAM Format<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 15


<strong>REAL</strong> <strong>Ethernet</strong> <strong>Services</strong><br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 16


<strong>Ethernet</strong> Access over Fiber<br />

ETX NTUs: Product Definition and Application<br />

Customer Premises<br />

Customer Premises<br />

EVC A<br />

ETX<br />

CPE<br />

CPE<br />

ETX-A<br />

Operator B<br />

Operator A<br />

Customer Premises<br />

EVC B<br />

ETX<br />

CPE<br />

End-to-end OAM between demarcation points<br />

• Clear demarcation between provider’s and Customer’s networks<br />

• OAM allow for E2E fault management and performance monitoring<br />

• Traffic management starting at customer premises<br />

• Prove of SLA contracts by continuous monitoring<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 17


<strong>Ethernet</strong> Access over Fiber<br />

ETX NTU - Product Overview<br />

Product Physical Description Highlights<br />

ETX-102 V3.8<br />

Fast <strong>Ethernet</strong><br />

NTU<br />

ETX-201 V3.8<br />

Gigabit & Fast<br />

<strong>Ethernet</strong> NTU<br />

ETX-202 V3.8<br />

Gigabit <strong>Ethernet</strong><br />

NTU<br />

• Compact 1U, half 19” plastic enclosure<br />

• 1xFE Net, 1xFE Net/User, up to 4 FE User<br />

• Compact 1U, half 19” plastic enclosure<br />

• 1xGE Net, 1xGE Net/User, up to 4xFE user ports<br />

• Auto-detect GE/FE SFP Slots<br />

• Compact 1U, half 19”, metal enclosure<br />

• 2xGE Net, up to 4xGE user ports<br />

• Switching & Bridging<br />

• <strong>Ethernet</strong> OAM 802.3ah<br />

• <strong>Ethernet</strong> OAM 802.1ag<br />

• Standard PM per y.1731<br />

• SLA Monitoring<br />

• Uplink redundancy<br />

• L1 and L2 Loopback<br />

• Per VLAN Statistics<br />

• Serial Craft port<br />

• Configurable OOB mgt. port<br />

• Wide range of SFP<br />

• Temp. Hardened option<br />

• Standard wide range AC/DC<br />

48-220 PSU<br />

• Optional wide range DC 24-48<br />

PSU option<br />

• Dying Gasp Support<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 18


<strong>Ethernet</strong> Access over Fiber<br />

ETX NTU - Product Overview<br />

Product Physical Description Highlights<br />

• Up to 4x GE SFP Optical Uplinks<br />

ETX-550<br />

GE Carrier <strong>Ethernet</strong><br />

Aggregation<br />

• Up to 24x UTP 10/100 or 100 FE<br />

Optical User ports<br />

• Switching & Bridging<br />

Compact 1U or 1.5U, 19”<br />

• Redundant PSU AC or DC<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 19


<strong>Ethernet</strong> Access over Fiber<br />

ETX NTUs: Performance Monitoring (PM)<br />

• Performance Monitoring Per EVC<br />

• up to 48* PM instances<br />

• Performance Monitoring (PM) OAM Availability<br />

• Traps can be defined per EVC per parameter with<br />

threshold<br />

• OAM PM Statistics<br />

• 15 minute intervals<br />

End-to-End OAM<br />

• Record of last 24 hours stored (96 cyclic intervals kept)<br />

• Additional PM (not OAM related)<br />

• Performance Measurements per port (RMON based RFC<br />

2819) such as dropped frames, oversize frames etc.<br />

• Traps with thresholds ‘Rising’ and ‘Falling’ thresholds<br />

definition<br />

* In VLAN stacking mode (Q-in-Q), 16 PM instances are available<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 20


<strong>Ethernet</strong> Access over Fiber<br />

ETX NTUs:Fault Propagation Network Port to User Port<br />

CPE Switches to<br />

alternative path<br />

CPE<br />

Failure propagated<br />

to user port<br />

X<br />

E-NTU<br />

X<br />

Network port<br />

failure<br />

Packet Switched<br />

Network<br />

Eth/IP/MPLS<br />

• ‘Link down’ status on the Network port causes ‘link<br />

down’ status on the user port.<br />

• In case of multiple user ports, ‘link down’ status on<br />

all user ports or part of them according to parameter<br />

• ‘Wait to restore’ parameter - defines the time<br />

between network port becoming ‘up’ and restoring<br />

user port link<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 21


<strong>Ethernet</strong> Access over Fiber<br />

ETX NTUs: Diagnostic Loopbacks<br />

• Layer 1 Loopback<br />

ETX loopbacks traffic from Rx to Tx<br />

• Out of service – disrupts service<br />

• Cannot traverse <strong>Ethernet</strong> bridge<br />

• Supported on any ETX port<br />

Tester<br />

• Performed on all traffic of the ETX port<br />

• Loopback activation is via<br />

management not OAM protocol<br />

No Layer L2<br />

Loopback<br />

• Layer 2 Loopback (at wire speed)<br />

ETX loopbacks traffic and swaps MAC<br />

Addresses<br />

• ETX replaces Source Address with<br />

Destination Address<br />

Tester<br />

ETX<br />

• Can traverse <strong>Ethernet</strong> bridges<br />

• Performed per VLAN (or EVC)<br />

With Layer L2<br />

Loopback<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 22


<strong>Ethernet</strong> Access over Fiber<br />

Summary of ETX NTUs<br />

The ETX-202; ETX-201 & ETX-102 are state-of-the-art<br />

Carrier <strong>Ethernet</strong> Demarcation Device<br />

• Its enhanced capabilities include:<br />

• Complete OAM package with standard 802.3ah, 802.1ag and Y.1731<br />

• SLA enforcement from customer premises<br />

• Link redundancy<br />

• The ETXs positioned completely differently from media converters<br />

and enterprise switches<br />

• Its support for VLAN based EVC enabling deployment of E-Line<br />

and E-LAN services, allow service provider to improved their<br />

network utilization<br />

• Fault isolation and performance monitoring with layer 1 and layer<br />

2 loopback will dramatically lower OPEX<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 23


<strong>Ethernet</strong> Access over Fiber<br />

ETX Supported Service Topologies Summary<br />

• EPL and EPLAN are supported by ETX products<br />

• EVPL and EVPLAN are supported with new ETX A series<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 24


<strong>REAL</strong> <strong>Ethernet</strong> <strong>Services</strong><br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 25


<strong>Ethernet</strong> Access over PDH<br />

RICi-E1/4E1/8E1/16E1, Egate-20/100<br />

•Egate Family: •RICi Family:<br />

•Egate-100<br />

•MIRICi-E1, MIRICi-E3<br />

•Egate-20<br />

•RICi-E1<br />

•RICi-4/8/16E1<br />

Egate-100<br />

Provider’s Node<br />

Egate-20<br />

FE<br />

E1/T1<br />

E1/T1<br />

n x E1/T1<br />

Customer Premises<br />

ETX-202 with<br />

MIRICi-E1/T1<br />

ETH<br />

Customer Premises<br />

RICi-E1/T1<br />

ETH<br />

Customer Premises<br />

RICi-4/8<br />

ETH<br />

PSN<br />

ETH/IP/MPLS<br />

GE<br />

FE<br />

Egate-100<br />

8 x E1/T1<br />

STM-1/OC-3/<br />

3 x DS3<br />

n x E1/T1/<br />

2 x DS3<br />

SDH/<br />

SONET<br />

n x E1/T1<br />

Customer Premises<br />

RICi-16<br />

ETH<br />

RICi-16<br />

Customer Premises<br />

n x E1/T1<br />

RICi-16<br />

ETH<br />

Control Room<br />

RICi-E1<br />

RICi-4E1/8E1<br />

RICi-16<br />

MIRICi-E1<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 26


Egate and RIC Main Features<br />

Demarcation Point between Carrier’s and Customer’s Networks<br />

• RICi and Egate provide a demarcation point between the private LAN<br />

and the operator’s PDH/SDH network<br />

• Enable service providers and ISPs to supply transparent <strong>Ethernet</strong><br />

services, without interfering with user traffic<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 27


RICi-E1<br />

• EPL Service<br />

Backup<br />

• Fault propagation<br />

LAN<br />

E1<br />

SDH<br />

E1<br />

LAN<br />

ETH Link<br />

is down<br />

AIS<br />

ETH Link<br />

is down<br />

• Flow control support at 100 Mbps<br />

• QoS<br />

• VLAN Priority (802.1p)<br />

• IP Precedence<br />

• New standard encapsulation: GFP (G.8040)<br />

• Extreme temperature:<br />

• -22–70°C (7.6–158°F)<br />

• 24 VDC metal box enclosure support extreme<br />

temperature<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 28


RICi-4E1/8E1<br />

Physical Features<br />

• <strong>Ethernet</strong><br />

• Copper: 4 or 2, 10/100 BaseT<br />

• Fiber Optic: 2, SFP-based 100 BaseFx<br />

• Network interfaces:<br />

• Up to 4 or 8 E1 unframed/framed<br />

• MLPPP bonding<br />

• Power Supply<br />

• AC/DC wide range<br />

• 24VDC<br />

• Temperature-hardened: -22–70°C (7.6–158°F)<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 29


RICi-4E1/8E1<br />

Features<br />

• EPL Service<br />

• OAM & Diagnostics<br />

• 802.1ag/Y.1731 OAM<br />

• E1/T1 BERT<br />

• Fault propagation (bidirectional)<br />

• MLPPP link to <strong>Ethernet</strong><br />

• <strong>Ethernet</strong> to MLPPP link<br />

• QoS (VLAN priority, DSCP, IP precedence, port based)<br />

• Management:<br />

• Secure Web session (SSL)<br />

• Secure Telnet session (SSH)<br />

• Radius authentication system<br />

10. Partnerský den <strong>VUMS</strong> <strong>DataCom</strong> 30

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!