act-lbp

Use this command to activate one or more loopback point tests for testing data signaling link elements in an SS7 transmission path. Use this command to:

Activate a test for a specified loopback point that is defined in the LFS database table
Activate a test for one loopback point that is not defined in the LFS database table
Activate tests for all loopback points that have been defined in the LFS database table. See Summary of Loopback Testing Commands and Functions for information about loopback testing commands and functions.

The ent-lbp command can be used to define a maximum of 32 loopback points in the LFS database table.

Parameters

To activate a test for a single loopback point that is defined in the LFS database table, specify the loopback point number in the lbp parameter and do not specify the lfst, rle, rep, or clli parameter in the command. Information from the LFS database is used to activate the test for the specified loopback point.

To activate a test for a single loopback point that is not defined in the LFS database table, specify one or more of the lfst, rle, rep, and clli parameters in the command. (If the clli parameter is not specified, then the value is blank, a null string. If the rep parameter is not specified, the default value is 0.)

To activate tests for all loopback points defined in the LFS database, do not specify the lbp, lfst, rle, rep, or clli parameter in the command. Information from the LFS database table is used to activate tests for all defined loopback points.

link (mandatory)

SS7 signaling link. The SS7 signaling link to be tested.

Synonym:

port

Range:

a, b, a1 - a31, b1 - b31

Not all card types support all link parameter values.

See Table A-1 for valid link parameter range values for each type of card that can have assigned signaling link ports.

loc (mandatory)

The location of the card containing the signaling link to use for loopback point testing.

Range:: 1101 - 1108, 1111 - 1112, 1201 - 1208, 1211 - 1218, 1301 - 1308, 1311 - 1318, 2101 - 2108, 2111 - 2118, 2201 - 2208, 2211 - 2218, 2301 - 2308, 2311 - 2318, 3101 - 3108, 3111 - 3118, 3201 - 3208, 3211 - 3218, 3301 - 3308, 3311 - 3318, 4101 - 4108, 4111 - 4118, 4201 - 4208, 4211 - 4218, 4301 - 4308, 4311 - 4318, 5101 - 5108, 5111 - 5118, 5201 - 5208, 5211 - 5218, 5301 - 5308, 5311 - 5318, 6101 - 6108, 6111 - 6118

clli (optional)

Common language location identifier. The CLLI code or other mnemonic identifier, used to refer to the given loopback point.

Range:: ayyyyyyyyyy
1 alphabetic character followed by up to 10 alphanumeric characters
Default:: If the rle, lfst, or rep parameter is specified—null string (blank)
If the rle, lfst, or rep parameter is not specified—the value in the LFS database

data (optional)

The data used with the octet or alternate patterns.

Range:: 1 - 255
Default:: 255

force (optional)

The force=yes parameter must be specified to start a test when there are 256 or more tests already running.

Range:

yes
no

Default:

no

lbp (optional)

Loopback point ID. A far-end loopback point that lies along an SS7 signaling link path between the STP and the target device (up to and including the target device).

Range:

1 - 32

Default:

If the rle, clli, rep, or lfst parameter is specified, the default is 1.

If the rle, clli, rep, or lfst parameter is not specified, the default is all loopback points found in the LFS database (up to 32 loopback points), as shown in the rtrv-lbp command output.

lfst (optional)

Link fault sectionalization test.

Note:

This parameter is mandatory if the rle, clli, or rep parameter is specified.

Range:

llt: latching loopback test; a software latch is set at the test point to reverse everything that is received and return it to the sender until the test is complete
mlt: manual latch loopback test; an external hardware latch is set to reverse everything that is received and return it to the sender until the test is complete (for equipment that cannot set a software latch for the test)
nlt: nonlatching loopback test; no permanent latch is set. Loopback codes are alternated with test data until the test is complete.

Default:

The value in the LFS database, as shown in the rtrv-lbp command output

maxerr (optional)

Bit error threshold. This parameter specifies the actual number of errors allowed for a specific time period during which loopback testing is being performed. If this threshold is exceeded, the TEST STATUS field in the output report indicates an error.

Range:: 0 - 4838400
Default:: 56

pattern (optional)

This parameter specifies the type of test pattern used to perform the LFS test.

Range:

b2047: 047-bit BERT pattern sent until it is stopped by software
b511: 511-bit BERT pattern sent until it is stopped by software
octet: Data (from the data parameter) sent continuously until it is stopped by software
alternate: Alternately, a count of 100 octets of the specified data (from the data parameter) followed by 100 octets of 0, sent until it is stopped by the software

The octet and alternate values are valid only when lfst=llt is specified.

Default:

b2047

rep (optional)

Repetition count. The number of link elements of the same type (not including the target device) that lie between the STP and the link element to be tested.

Range:: 0 - 31
Default:: If the rle, clli, rep, or lfst parameter is specified, the default is 0.
If the rle, clli, rep, or lfst parameter is not specified, the default is the value in the LFS database, as shown in the rtrv-lbp command output.

rle (optional)

Remote link element. The link element to be looped back for testing.

Note:

This parameter is mandatory if the lfst, clli, or rep parameter is specified.

Range:

ds0
ocu
csu
dsu
nei

Default:

The value from the LFS database, as shown in the rtrv-lbp command output

time (optional)

The length of time the test must be run in order to determine success or failure. If the number of errors that actually occur during this time exceeds the threshold set by the maxerr parameter, the loopback test is identified as a failure.

Range:

1 - 240000

hhmmss—hh=hours (00-24 ), mm=minutes (00-59), ss=seconds (00-59)

For example, time=1 or time=000001 is one second; time=240000 is 24 hours; time=200 or time=000200 is 2 minutes

Default:

1 second

Example

Activate tests for all loopback points that are defined in the LFS database table:

act-lbp:loc=1205:link=b:pattern=alternate:maxerr=10:time=000200

Activate a test for a single loopback point that is not defined in the LFS database table:

act-lbp:loc=1205:link=b:lbp=1:rle=ds0:lfst=llt:clli=rlghncxa05w

act-lbp:loc=1205:link=b:lbp=1:rle=ds0:lfst=llt:clli=rlghncxa05w:pattern=octet:data=h’ff

act-lbp:loc=1205:link=b:lbp=1:rle=ds0:lfst=llt:clli=rlghncxa05w:maxerr=40:time=12000

Activate a test for a single loopback point that is defined in the LFS database table:

act-lbp:loc=1205:link=b:lbp=3:pattern=alternate:maxerr=10:time=000200

Dependencies

The Link Fault Sectionalization (LFS) feature must be on before this command can be entered.

If the rle=nei parameter is specified, the rep=0 parameter must be specified.

The rep parameter can be specified only if the lfst=llt parameter is specified.

The rle=ds0 or the rle=nei parameter cannot be specified if the lfst=nlt parameter is specified. The DS0 and Network Element Interface (NEI) link elements do not support non-latching loopbacks.

If one or more of the rle, rep, lfst, or clli parameters are specified, the database is not used to look up their values; therefore, the lfst and rle parameters must be specified when the rep or clli parameter is specified.

The data parameter can be specified only if the pattern=octet parameter or pattern=alternate parameter is specified.

The pattern=octet and pattern=alternate parameters cannot be specified for non-latching tests (rle=nlt).

The card location (loc parameter) must contain a provisioned and equipped E5-E1T1-B card, provisioned with the LIMT1 card type, running the SS7ANSI or CCS7ITU application.

The card in the loc parameter location must be in the In-Service-Normal state.

The signaling link that is used for LFS testing must be equipped, and must be deactivated before this command is entered.

The loopback points (LBPs) must have been previously defined in the database.

Only one LFS test can be active on a signaling link at a time.

This command cannot be entered for a signaling link LFS test when the maximum number of LFS tests are active for the card. At least one LFS test must complete before this command can be entered again.

Up to 8 LFS tests at a time can be active on an E5-E1T1-B card used as a T1 card.

This command cannot be entered when the maximum combined total number of LFS and link tests (1024) are in progress in the system. At least one test must complete before this command can be entered again.

The force=yes parameter must be specified to activate a test when there are 256 or more tests already running in the system.

The specified signaling link must not be running a tst-slk test when this command is entered. The tst-slk test must be stopped or allowed to complete before this command can be entered for the link.

The specified signaling link must not be in Command Driven Loopback (CDL) when this command is entered. The link must be removed from CDL before this command can be entered for the link.

This command cannot be entered for a link that is already blocked by another link diagnostic test. The test must be canceled or allowed to complete before this command can be entered for the link.

LFS testing is not available during upgrade.

The maximum number of loopback point entries allowed in the LFS table is 32.

Notes

This command is not supported for E5-ATM-B cards.

If an LFS test is aborted by a card reset, it can leave the remote far-end loopback condition active. Use the dact-lbp command to cancel LFS tests.

The E5-E1T1-B cards support this command on up to 8 T1 channels at a time; the command is not supported for E1.

The test can terminate with the status "ERROR, bit error exceeded threshold" for two reasons.

The number of cumulative bit errors exceeds the specified maxerr parameter value.
The number of bit errors for one second reaches or exceeds 255, without considering the maxerr parameter value.

Output

The LFS report is displayed when the LFS test completes.

This example shows how the test failed because the bit error rate exceeded the threshold. The maxerr=10 parameter is used for a test time of 2 minutes. Because more than 10 errors occurred within 2 minutes, the test is considered a failure and the TEST STATUS field displays the cause. The parameter values are applied to each loopback point. The maxerr value is per test, not cumulative for all tests.

act-lbp:loc=1205:link=b:pattern=alternate:maxerr=10:time=002000


    tekelecstp 05-01-21 17:00:36 EST  EAGLE5 33.0.0
    LOC = 1205  Link = B  LSN = ls11345678  Start time = 11:10:34
    
    PATTERN = ALTERNATE  DATA= FF  MAXERR = 10  TIME = 00:02:00
    
    TEST STATUS = ERROR, bit error exceeded threshold.
    LBP  CLLI         RLE  REP  LFST  BIT_ERROR  ERRORED_SEC  DURATION
    2    rlghncxa05w  DS0  0    LLT   0          0            00:02:00
    3    ------------ OCU  0    NLT   8          2            00:02:00
    5    ------------ NEI  0    LLT   15         1            00:01:20 
;

In this example, the test failed because the loopback could not be established.

act-lbp:loc=1205:link=b:pattern=alternate:maxerr=10:time=000200


    tekelecstp 05-01-21 17:00:36 EST  EAGLE5 33.0.0
    LOC = 1205  Link = B  LSN = ----------  Start time = 11:10:34

    PATTERN = ALTERNATE  DATA= FF  MAXERR = 10  TIME = 00:02:00
    TEST STATUS = ERROR, loopback was not established.

    LBP  CLLI         RLE  REP  LFST  BIT_ERROR  ERRORED_SEC  DURATION
    1    rlghncxa05w  DS0  0    LLT   0          0            00:00:00 
;

Legend

LOC—Card location that contains the signaling being tested
LINK—Signaling link that is being tested on the card
LSN—Name of the linkset that contains the link being tested
Start time—Time that the test started
PATTERN—Type of test pattern used to perform the LFS test
DATA—Data used with the octet or alternate patterns
MAXERR—Bit error threshold; actual number of errors allowed for the specific time period during which loopback testing is being performed. If this threshold is exceeded in the specified time period, the TEST STATUS field in the output report indicates an error.
TIME—Specified length of time to run the test in order to determine success or failure. If the number of errors that actually occur during this time exceeds the threshold set by the maxerr parameter, the loopback test is identified as a failure.
TEST STATUS—Any one of the following TEST STATUS values can appear:
- PASS
- ERROR, LFS HARDWARE is not available.
- ERROR, loopback could not be established.
- ERROR, bit error exceeded threshold.
- ERROR, LFS test aborted.
- ERROR, LFS hardware failed.
LBP—Loopback point used to perform the LFS test
CLLI—Common Language Location Identifier (CLLI) code, or other mnemonic identifier, used to refer to the given loopback point
RLE—Remote link element to be looped back for testing
REP—Repetition count. The number of link elements of the same type (not including the target device) that lie between the STP and the link element to be tested.
LFST—Type of link fault sectionalization loopback test to be performed
BIT_ERROR—The number of bit errors observed during the test
ERRORED_SEC—The number of seconds that contained bit errors during the test. (Bit errors are sampled once per second; each sample that contains bit errors adds one second to this count.)
DURATION—Length of time that the test actually ran for the loopback point. For successful test, the TIME and the DURATION should be the same. If a test ran for less than the specified amount of time, the DURATION will be less than the TIME.

4.9 act-lbp