No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-How we can judge if E1 fault in Local Site cause by close the E1 in T2000 in remote site

Publication Date:  2012-07-25 Views:  106 Downloads:  0

Issue Description

Sometime we need judge the down of E1 through the alarm thats if this fault from Human setting (that he forgets to return it to the normal) or from external reasons such: cabling problem, punching in DDF or others reasons…

So when the Human set the E1 in PQ1 to Non-Load state (Through T2000: Select the PDH Interface/Service Load Indication) in local site what the alarm that should report in the remote site?

For Metro3000 it report LP_RDI alarm in remote site, but for OSN3500 this alarm not support in this case, because this alarm report only when the E1 detected the value of the V5 byte in lower order is 1 but not related to the signal if loss or not configure…

This alarm is very important & will be useful for engineers to judge whether the E1 is used or not.

So how we can judge for the OSN3500 if the E1 down from Human setting in T2000?

Alarm Information


Handling Process

When the E1 set to Non-Load in OSN3500 there no alarm report in the remote E1 in opposite site!

Actually there one Alarm will report if enable the Path Not Used in T2000 when the E1 state in Non-Load, so the alarm that will report is LP_UNEQ Alarm in Remote Siteif the E1 in the Local Site are in Non-Load State.

To display this alarm (LP_UNEQ)in OSN when the E1 in Non-Load state, so you should Enable the Path Not Used as bellow diagram:



Root Cause