Hi,
Some conditions are reported as APS defect conditions and result in the release of the selector. this defect is called FOP (failure of the protocol). in G.783 FOP is one defect of MSP and more information about that are explained in G.841.
- In bidirectional operation, If there is a mismatch between the signal numbers indicated on received K2 and sent K1 bytes and this mismatch persists for 50 ms, the selector is released and a mismatch is indicated as FOP;
Note1: If the protection section is in SF condition, the selector is released and the mismatch indication is disabled.
- A mismatch of bit 5 of the sent and received K2 for 50 ms (optional);

Note2: This occurs when a 1 + 1 architecture connects to a 1:1 architecture.

- In bidirectional operation, an inappropriate code that persists for 50 ms in the received K1 bits 1-4. Appropriate codes are a higher priority request than the local request, an identical request to the local request, or a reverse request for any local
request except no request. Any other value that persists for 50 ms is considered an inappropriate code;
- In bidirectional operation, an inappropriate or invalid traffic signal number that persists for 50 ms in the received K1 bits 5-8.
- If the switch is not completed because the requested/bridged signals did not match within 50 ms, the selectors would remain released and the failure of the protocol would be indicated. This may occur when one end is provisioned as unidirectional and
the other as bidirectional.
- A mismatch may also occur when a locked-out traffic signal at one end is not locked out at the other.
my question is, except releasing selector in some conditions what another action must be done? for example, we just must display FOP to a user or need to reset configs or...

thanks in advance,
Elnaz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello Elnaz,

You wrote:

Hi,
Some conditions are reported as APS defect conditions and result in the release of the selector. this defect is called FOP (failure of the protocol). in G.783 FOP is one defect of MSP and more information about that are explained in G.841.
- In bidirectional operation, If there is a mismatch between the signal numbers indicated on received K2 and sent K1 bytes and this mismatch persists for 50 ms, the selector is released and a mismatch is indicated as FOP;
Note1: If the protection section is in SF condition, the selector is released and the mismatch indication is disabled.
- A mismatch of bit 5 of the sent and received K2 for 50 ms (optional);

Note2: This occurs when a 1 + 1 architecture connects to a 1:1 architecture.

- In bidirectional operation, an inappropriate code that persists for 50 ms in the received K1 bits 1-4. Appropriate codes are a higher priority request than the local request, an identical request to the local request, or a reverse request for any

local request except no request. Any other value that persists for 50 ms is considered an inappropriate code;

- In bidirectional operation, an inappropriate or invalid traffic signal number that persists for 50 ms in the received K1 bits 5-8.
- If the switch is not completed because the requested/bridged signals did not match within 50 ms, the selectors would remain released and the failure of the protocol would be indicated. This may occur when one end is provisioned as unidirectional and

the other as bidirectional.

- A mismatch may also occur when a locked-out traffic signal at one end is not locked out at the other.
my question is, except releasing selector in some conditions what
another action must be done? for example, we just must display FOP
to a user or need to reset configs or...

Indeed the FOP has to be reported and recorded.
It should be a red alarm, immediate action required because it
will affect the availability of the protected service.

What would be the result of the reset of config?
Is there a default config, but question is if the default is the
same at both protection endpoints.

Best regards, Huub.


--
reply to hhelvooort with 2 'o's ================================================================
http://www.van-helvoort.eu/ ================================================================
Always remember that you are unique...just like everyone else...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)