Specifications
3-46
Cisco ONS 15454 and Cisco ONS 15327 TL1 Command Guide, R3.3
May 2002
Chapter 3 TL1 Command Descriptions
TL1 Commands
3.5.18 ED-<STS_PATH>: Edit (STS1, STS3C, STS6C, STS9C, STS12C, STS24C,
STS48C, STS192C)
(STS192C supported for Cisco ONS 15454 only)
This command edits the attributes associated with an STS path.
The SFBER, SDBER, RVRTV, and RVTM parameters only apply to UPSR.
The path trace message is a 64 character string including the terminating CR (carriage return) and LF
(line feed) that is transported in the J1 byte of the SONET STS Path overhead. Both the EXPTRC and
TRC string can be provisioned by user with up to 62 character string.
The EXPTRC indicates the contents of the expected incoming path trace are provisioned by the user. The
TRC indicates the contents of the outgoing path trace message. The INCTRC indicates the contents of
the incoming path trace message.
The path trace mode has three modes: OFF, MANUAL, and AUTO. The path trace mode defaults to OFF.
The MANUAL mode performs the comparison of the received string with the user-entered expected
string. The AUTO mode performs the comparison of the present received string with an expected string
set to a previously received string. If there is a mismatch, TIM-P alarm is raised. When the path trace
mode is in OFF mode, there is no path trace processing, and all the alarm and state conditions are reset.
The TACC parameter edits an existing single STS or VT and changes it to a test access path. When an
editing command on TACC is executed, it assigns the STS for the first 2WAY test access connection and
STS=1 as the second 2WAY connection. For STS3C and STS12C, the next available STS of the same
width is chosen. For more information on TACC, refer to the “Test Access” section on page 1-9.
J1 is implemented on the DS1/DS1N, DS3, DS3E/DS3NE, DS3XM, EC1, OC3, OC48AS and OC192
cards.
DS3/DS3N, OC12, OC48, E100, and E1000 cards do not support path trace.
DS1/DS1N, DS3E/DS3NE, and DS3XM support both TRC and EXPTRC in the ED-STS-PATH
command.
EC1, OC3, OC48AS, and OC192 only support EXPTRC in the ED-STS-PATH command.
Note Each TL1 command must be less than or equal to 255 characters. Any command larger than 255
characters must be split into multiple commands. For example, if you use the ED-<STS_PATH>
command to edit the J1 EXPTRC/TRC message, UPSR attributes, and TACC attributes and the
command exceeds 255 characters the command will not be processed. You must use multiple
ED-<STS_PATH> commands instead.
Note An STS tap created in a DS3XM card cannot be used to connect to an STS having a non-VT structured
payload; for example, DS3, if created traffic cannot be monitored.
Note An STS tap created in a DS3 card cannot be used to connect to an STS having non-DS3 payload; for
example, VT-structured, if created traffic cannot be monitored.
Error conditions:
1. If sending this command to edit SFBER or SDBER or RVRTV or RVTM for the non UPSR STS
path, an error message (cross-connect does not have UPSR path selector) will be returned.