Enhanced Lambda Filtering

This topic outlines completely optional settings for configuring lambdas to filter by multiple ranges, in addition to multiple single values. For example, you can trace through a connectable object 1550 nm - 1700 nm and 1750 nm - 1850 nm and completely ignore 1701 nm - 1749 nm, and simultaneously trace through it at 1310 nm but not 1311 nm - 1549 nm.

Configuration at the dB level

  1. Add a new text field to the fiber connectable objects with which you want to filter lambdas (e.g., splitter ports).

  2. Add the FIBER_DSL_DEFINED_LAMBDA model name to the Fiber Field Model Names domain.

  3. Assign the model name to the new field.

Configuration at the object level

For objects that you want to filter lambdas through that have the text field you created and the FIBER_DSL_DEFINED_LAMBDA model name applied, the values are in comma delimited form:

<single lambda 1>,<lambda min 1>-<lambda max1>…<single lambda n>,<lambda min n>-<lambda max n>

So, if you want to pass the following:

1310, 1320 to 1550, 1570, 1578.2 to 1563.8, and 1776

Place the following in the field you created:

1310,1320-1550,1570,1578.2-1563.8,1776

Tracing passes through an object and continues to the next object in these circumstances:

  1. Does the trace define a lambda?

    • No? The trace passes.

    • Yes? Proceed to question 2.

  2. Does the object have the new DSL lambda field configured at a dB level?
    • No? Proceed to question 3.

    • Yes? Proceed to question 4.

  3. Does the object have the old lambda range fields configured on it at a dB level?

    • No? The trace passes.

    • Yes? Proceed to question 4.

  4. Are there values in the field?

    • No? The trace passes.

    • Yes? Proceed to question 5.

  5. Does the lambda defined by the trace match any of the allowable values and/or ranges?

    • No? The trace does not pass.

    • Yes? The trace passes.

QR code for this page

Was this helpful?