To Next Page

To Previous Page

The router passes the following OAM cells transparently:

■ F5 alarm indication signal (AIS) segment and end-to-end

■ F5 remote defect indication (RDI) segment and end-to-end

■ F5 loopback segment and end-to-end

■ Resource management

■ F5 continuity check segment and end-to-end

In addition, F4 OAM cell forwarding is supported.

JUNOSe software does not allow for setting a segment endpoint on an ATM

cross-connect interface. Segment OAM cells are forwarded to the egress interface in

the same manner as end-to-end cells.

QoS Classification

Packets are subject to normal quality of service (QoS) classification according to

service categories assigned to ATM virtual circuits that make up the connection.

Limitations

The JUNOSe implementation of the Martini draft has the following limitations:

■ Only AAL5 packets and OAM cells are forwarded.

■ There is no equivalent of VP switching.

■ Point-to-multipoint connections are not supported.

■ Automatic connection setup using user-to-network interface (UNI) signaling and

private network-to-network interface (PNNI) is not supported.

■ The ATM MIB cross-connected table is not supported.

■ Connections between ATM circuits and non-ATM interfaces are not supported.

Control Word Support

Martini draft encapsulation includes a control word with the following fields:

■ T bit for transport type

■ E bit for explicit forward congestion indication (EFCI)

■ C bit for cell loss priority (CLP)=1 indication

■ U bit for command/response indication based on AAL5 common part convergence

sublayer user-to-user indication (CPCS-UU)

■ Optional sequence number

The current JUNOSe implementation supports the T bit and optional sequence number

fields.

ATM Layer 2 Services over MPLS ■ 517

Chapter 6: Layer 2 Services over MPLS Overview

Juniper BGP - CONFIGURATION GUIDE V 11.1.X User Manual

Questions and Answers: