|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
X-Original-To: nanog@nanog.org To: Jared Mauch <jared@puck.nether.net>, Colton Conor <colton.conor@gmail.com> From: Mark Tinka <mark.tinka@seacom.mu> Date: Tue, 24 May 2016 08:58:13 +0200 In-Reply-To: <77885102-DE54-45AF-9760-C6EA8DBD93D3@puck.nether.net> Cc: "nanog@nanog.org" <nanog@nanog.org> Errors-To: nanog-bounces@nanog.org On 24/May/16 08:51, Jared Mauch wrote: > I’ve seen optical transport gear be non-transparent in a few situations when > using OTU2 vs OTU2e, but they turned out to be a bug. I've seen this as well, including in an SDH transport, where OSPF packets were being eaten (something Multicast-related). > If a L2 platform is > being used to front-end a router, you could be seeing slow protocols like > CDP/LLDP/LACP being consumed by that switch. If you configure LLDP does it > pass end-to-end? That's what I was thinking at first when I read the OP's post. If the circuit is being transported over MPLS or being fronted by an Ethernet switch, Level(3) would have to tunnel Layer 2 protocols in order to support your LACP frames across the pw. Mark.
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |