Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [EFM] 802.3ah OAM question




The one that I have handy is D2.1 draft. Figure 57-6 has a transition from WAIT_FOR_TX to
DEC_PDU_CNT to TX_FRAME. The only condition there is valid_pdu_req. valid_pdu_req is basically
says that OAMPDU can be sent but subject to rate limiting counter (pdu_cnt), except for OAMPDU
with critical link event flags.

There is no check of the state of the mux, so OAMPDU is allowed regardless of loopback or not.

Cheers,

-----Original Message-----
From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
Sent: Thursday, February 19, 2004 10:53 AM
To: Stephen Suryaputra; Matt Squire; stds-802-3-efm@ieee.org
Subject: RE: [EFM] 802.3ah OAM question


Hi Stephen,

Is this behavior clearly stated somewhere in 802.3ah?

-Shahram

-----Original Message-----
From: Stephen Suryaputra [mailto:ssuryaputra@HatterasNetworks.com]
Sent: Thursday, February 19, 2004 10:47 AM
To: Shahram Davari; Matt Squire; stds-802-3-efm@ieee.org
Subject: RE: [EFM] 802.3ah OAM question


The node in loopback mode must be able to inject OAM packets. Several reasons for that, I think:
1. Info OAMPDU can be exchanged to keep the session.
2. Any link events can still be communicated.

Cheers,

-----Original Message-----
From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
Sent: Thursday, February 19, 2004 9:22 AM
To: 'Matt Squire'; stds-802-3-efm@ieee.org
Subject: RE: [EFM] 802.3ah OAM question



Hi Matt,

So you are saying that the node that is put in loopback mode can't inject any OAM packet
to the looped back stream. But off course the node that is controlling the loopback can inject
anything including OAM. Correct?

-Shahram

-----Original Message-----
From: Matt Squire [mailto:msquire@mindspring.com]
Sent: Wednesday, February 18, 2004 10:23 PM
To: Shahram Davari; stds-802-3-efm@ieee.org
Subject: Re: [EFM] 802.3ah OAM question




Hi Shahram - 

I guess it depends which node you consider in loopback mode. 

When a OAM entity puts its peer OAM entity in remote loopback mode (via the Loopback Control OAMPDU), the initiating node CAN (and likely will) inject data onto the link - its multiplexer action will be FWD meaning traffic from the higher layer is passed to the lower layer.  

When an OAM entity is put into remote loopback mode (receives the Loopback Control OAMPDU), it CANNOT inject any higher layer data onto the link - its multiplexor state is DISCARD meaning traffic from the higher layer is discarded and not passed to the lower layer. 

Hope that helps. 

- Matt

-----Original Message-----
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Sent: Feb 18, 2004 11:49 AM
To: stds-802-3-efm@ieee.org
Subject: [EFM] 802.3ah OAM question


Hi all,

Should the node, which is in loopback mode, be able to generate and inject OAM packets?

Thanks,
Shahram Davari