S/UNI®-ATLAS-3200 Telecom Standard Product Data Sheet
Preliminary
These PM connections may be configured to be sinks, sources or monitoring points of F4 or F5
segment or end-to-end PM flows.
The figure below illustrates the PM flow capability of the S/UNI-ATLAS-3200.
Figure 19 PM Flows
Generated Fwd
Monitoring PM Cell
(3)
Fwd Monitoring PM
Cell (1)
Ingress
Generated Bwd
Reporting PM cell
(4)
S/UNI-ATLAS-3200
Backwards Reporting
PM Cell (2)
Generated Fwd
Monitoring PM Cell (2)
Egress
Fwd Monitoring PM
Cell (4)
Generated Bwd
Reporting PM Cell
(1)
S/UNI-ATLAS-3200
Bwd Reporting PM
Cell (3)
The figure above illustrates two unique bi-directional PM flows. In the first PM flow, indicated
by (1), the Ingress S/UNI-ATLAS-3200 is terminating a Forward Monitoring PM cell and it
generates a Backward Reporting PM cell through the Backward Cell Interface and the Egress
S/UNI-ATLAS-3200 . This is one half of the bi-directional PM flow. The second half of the bi-
directional flow is indicated by (2). Here, the Egress S/UNI-ATLAS-3200 is generating a
Forward Monitoring PM cell . Another downstream entity (e.g. another ATLAS device) would
terminate that Forward Monitoring cell and transmit a Backward Reporting PM cell. This
Backward Reporting PM cell is received at the Ingress S/UNI-ATLAS-3200 and terminated. To
enable this PM session, the termination of the Forward Monitoring PM cell (1) and the statistics
collected from the termination of the Backwards Reporting PM cell (2) would be maintained by
the Ingress S/UNI-ATLAS-3200 Processor in one RAM location. The generation of the Forward
Monitoring PM cell (2) would be maintained by the Egress S/UNI-ATLAS-3200 in one RAM
location.
Proprietary and Confidential to PMC-Sierra, Inc., and for its Customers’ Internal Use
Document ID: PMC-1990553, Issue 4
119
PMC [ PMC-SIERRA, INC ]
