Bit late to this thread. Further to Charlie's input, if you take an NE/NE+ service request and end-to-end MTU check beforehand if you need >1600 MTU. We've had issues were a NE+ circuit for which the NTE supports an MTU up to 2032 won't go above something smaller (exact value escapes me right now) - one of the MetNets it passes through is old with a low MTU.
We've also had NE+ circuits where we have asked if we can raise the MTU to support jumbo frames, but we couldn't go above 4470 because there are SDH/SONET MetNets in the middle, but this has been possible on other circuits. Also don't forget their SLAs are pants, 30ms or something. We've have multiple VM NNI's and we've had issues where the PoP that feeds that PoP that our NNI is on, has been congested so our NNI is affected (packet loss across all VNO circuits there), increasing the latency on them all from circa 10ms to just under 30ms so its still within SLA but inter site delay is nearly 60ms for two sites on the same NNI (which is no better than ADSL), and VM they have been very slow to recover it. Also most NE/NE+ circuits are pseudowires across their core. I think the control-word is disabled by default. We have had several instances where we have requested they enabled the pseudowire control-word for that circuit and the issues have been reduced (like out of order packets or jitter). Might be worth ordering all circuits with the control-word enabled by default. Cheers, James.
