Curtis, earlier you stated:
[[Late edit: I just noticed your reply to me. We apparently sent messages at the same time, we've crossed each other in the ether. Please note that in some of my earlier messages I stated that the APS and other protection functions were removed, along with other overhead features in some new SONET schemes in an attempt to skinny down the overall SONET profile. Now, let me go back and read your post, which I think begins to address this one, even though you haven't seen it yet. This is getting a little like weird scenes inside the gold mine.]]
"...there ARE NO OADMs (All Optical Add-Drop Multiplexers) that can process SONET/SDH overhead in the SONET/SDH frame. Remember, those are the Bytes in Section/Line/Path and other such as the DCC's and the Automatic Protection Switch Bytes..".
I initially agreed with you, but now I think I may have agreed with you too soon. I agreed initially because my sense was that the current state of integration in OADMs had not advanced this far, yet. Or, perhaps, because I felt on some level that they wont go there at all in many cases. Could we both be wrong?
======
The following is from Ciena's CoreStream optical add-drop multiplexer (OADM) element specifications sheet. Note the use of SONET interface specifications which define the actual ports.
Also note, especially, the use of SONET overhead bytes in tracking both optical power (B1) and trace section monitoring (J1).
I've bolded those, along with the analog optical overhead wavelength of 1625 nm (outside the region of normal L and C band dwdm) which is used to support an E1 stream at 2 Mb/s in support of the optical service channel.
How are these overhead byte utilizations explained? Are the lambda
steams individually o-e'ed, in every case? Or, are they broken out at the
time of test, through an appliqué? The site doesn't go into detail. Perhaps
there are some CIEN or MRVC DWDM/OADM mavens here who can
help us out with the details.
I've obviously got some catching up to do.
From: ciena.com :
=======
Format: OC-12/STM-4/OC-12c/STM-4c;
OC-48/STM-16/OC-48c/STM-16c; OC-192/STM-64
System Configuration: 5 spans x 25 dB (500 km) nominal for 2.5 Gbs; 5
spans x 20 dB (240km) nominal for 10 Gbs
Channel Interface: 2.5 Gbs WDM Transceiver: 1250 to 1600 nm input
wavelength; SONET: Bellcore GR-253-CORE; OC48 Short Reach;
SDH:ITU-T G.957 I-16 Intra-office 10 Gbs WDM Transceiver;
OC192/STM64
Link Parameters: System BER <10 -15
Network Management: EMS Supported by CIENA WaveWatcher®
EMS (FMS or EMS) Simultaneous management of MultiWave®
products from a single WaveWatcher terminal
Channel Performance Monitoring: Channel bit errors via B1 in
SONET/SDH overhead, Optical power
Optical Service Channel 2.048 Mb/s at 1625 nm
Section Trace Monitoring: via J0 in SONET/SDH overhead
|
