YD - Physical Layer Trail Termination Point Handling
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not
be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks
(“Agreement”) under which this document is distributed. No part of this document may be used, copied,
reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that
Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of
the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right
to change any such information and statements without notice. Nokia Solutions and Networks has made all
reasonable efforts to ensure that the content of this document is adequate and free of material errors and
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction
of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © 2016 Nokia Solutions and Networks. All rights reserved.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
products and services. We would like to encourage you as our customers and users to join us in working
towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations
for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia Solutions and Networks for any additional information.
2 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling
Table of Contents
This document has 24 pages
1 Summary of changes .................................................................... 4
2 YD - PHYSICAL LAYER TRAIL TERMINATION POINT
HANDLING.....................................................................................5
3 YDC CREATE PHYSICAL LAYER TRAIL TERMINATION POINT .
6
4 YDD DELETE PHYSICAL LAYER TRAIL TERMINATION POINT ..
9
5 YDI INTERROGATE PHYSICAL LAYER TRAIL TERMINATION
POINT ..........................................................................................11
6 YDR DETACH PHYTTP FROM PHYSICAL INTERFACE .......... 14
7 YDS ATTACH PHYTTP TO PHYSICAL INTERFACE ................. 16
8 YDT INTERROGATE DETACHED PHYTTP ...............................20
Issue: 05 DN015954 3
Summary of changes YD - Physical Layer Trail Termination Point Handling
1 Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes made between issues 4-0 (RU30, 2009-01-30) and 05 (RU50, 2014-02-16)
NIS1 related information is removed from the document.
Changes made between issues 3-2 and 4-0
The YDS: ATTACH PHYTTP TO PHYSICAL INTERFACE command has been updated
because of a new functionality. It is now possible to attach the phyTTP also to the NIS1
and NIS1P units.
Changes made between issues 3-1 and 3-2
Editorial corrections have been made.
4 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YD - PHYSICAL LAYER TRAIL TERMINATION POINT
HANDLING
Issue: 05 DN015954 5
YDC CREATE PHYSICAL LAYER TRAIL YD - Physical Layer Trail Termination Point Handling
TERMINATION POINT
This parameter is not applicable for RNC.
IMA group
IMA = IMA group id
This parameter is not applicable for RNC.
This parameter identifies the SET of the VC path that is used for the phyTTP.
This parameter is optional. If this parameter is given, no other parameters of this block
are allowed.
protection group
6 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDC CREATE PHYSICAL LAYER TRAIL
TERMINATION POINT
PROTGROUP = Protection group id
This parameter identifies the SDH protection group of the VC path that is used for the
phyTTP.
This parameter is optional. If this parameter is given, no other parameters of this block
are allowed.
VC path number
This parameter identifies the virtual container path that is used for the phyTTP.
The VC path must be free so that it is not used in another phyTTP. You can check
whether a VC path belongs to a phyTTP using command YAI.
The allowed values for the parameter depend on the SDH interface type. You can check
the SDH interface type with command YAI.
The VC path is always the same in both SETs if the phyTTP consists of a protected SET
pair.
This parameter is optional. It is allowed only if SDH exchange terminal index or a
protection group id is given.
The default value is 1 and is used if the parameter is not given and the SDH exchange
terminal index or a protection group id is given.
Payload type
This parameter identifies the type of payload in the data transfer. Possible values for
SET and SDH protection group are ATM and PPP.
The default is ATM.
PPP scrambling
This parameter defines whether the payload is scrambled in the data transfer.
Possible values for PPP type of payload are ON and OFF. The default is ON.
For ATM type of payload this parameter cannot be given.
Examples
1. Create a phyTTP with id 1 of SET with index 10.
YDC:1:SET=10;
2. Create a phyTTP of path 3 that belongs to protection group 2. Let the system select
a free id for the phyTTP. Payload type is ATM.
YDC::PROTGROUP=2:1:ATM;
3. In case destination interface unit's main state is TE create a phyTTP with id 15 of
SET with index 13. In this case the configuration will be done only to the
configuration file and the new configuration will be taken into use when the
destination unit is restarted.
YDC:15:SET=13;
Execution printouts
Issue: 05 DN015954 7
YDC CREATE PHYSICAL LAYER TRAIL YD - Physical Layer Trail Termination Point Handling
TERMINATION POINT
1. The execution printout of command example 1 is:
CREATE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
2. The execution printout of command example 2 is:
CREATE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
3. The execution printout of command example 3 is:
CREATE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
8 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDD DELETE PHYSICAL LAYER TRAIL
TERMINATION POINT
1. Delete phyTTP with id 3.
YDD:3;
2. In case destination interface unit's main state is TE delete phyTTP with id 15. In this
case the configuration will be done only to the configuration file and the new
configuration will be taken into use when the destination unit is restarted.
YDD:15;
Execution printouts
The execution printout of command example 1 is as follows:
DELETE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
The execution printout of command example 2 is as follows:
DELETE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
Semantic error messages
If an error occurs, the system outputs a general MML semantic error message.
Execution error messages
Issue: 05 DN015954 9
YDD DELETE PHYSICAL LAYER TRAIL YD - Physical Layer Trail Termination Point Handling
TERMINATION POINT
If an error occurs, the system outputs a general MML execution error message.
10 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDI INTERROGATE PHYSICAL LAYER TRAIL
TERMINATION POINT
1. Interrogate all phyTTP ids in the system.
YDI;
2. Interrogate phyTTP ids 10 and 12.
YDI:10&12;
3. Interrogate all phyTTPs with id in the range 20 to 25.
YDI:20&&25;
4. Interrogate all phyTTPs from the network interface unit NPS1P-1.
YDI:,NPS1P,1;
Execution printouts
Issue: 05 DN015954 11
YDI INTERROGATE PHYSICAL LAYER TRAIL YD - Physical Layer Trail Termination Point Handling
TERMINATION POINT
1. The execution printout of command example 1 can be as follows:
INTERROGATE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
2. The execution printout of command example 2 can be as follows:
INTERROGATE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
3. The execution printout of command example 3 can be as follows:
INTERROGATE PHYSICAL LAYER TRAIL TERMINATION POINT
COMMAND EXECUTED
4. The execution printout of command example 4 can be as follows:
INTERROGATE PHYSICAL LAYER TRAIL TERMINATION POINT
12 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDI INTERROGATE PHYSICAL LAYER TRAIL
TERMINATION POINT
COMMAND EXECUTED
Issue: 05 DN015954 13
YDR DETACH PHYTTP FROM PHYSICAL YD - Physical Layer Trail Termination Point Handling
INTERFACE
14 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDR DETACH PHYTTP FROM PHYSICAL
INTERFACE
Examples
1. Detach phyTTP 1 from the physical interface.
YDR:1;
2. Detach all phyTTPs of the NPS1P-1 unit.
YDR:,NPS1P,1;
Execution printouts
1. The execution printout of command example 1 is:
PHY TTP
-------
1
COMMAND EXECUTED
2. The execution printout of command example 2 could be:
PHY TTP
-------
2
5
7
8
430
550
551
570
COMMAND EXECUTED
Issue: 05 DN015954 15
YDS ATTACH PHYTTP TO PHYSICAL INTERFACE YD - Physical Layer Trail Termination Point Handling
16 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDS ATTACH PHYTTP TO PHYSICAL INTERFACE
SET The attachment will be done to a single SET. In this case
the SET index parameter value is obligatory.
PGSET A phyTTP which is based on the protection group is
attached. The attachment can be done by defining both
working section SET index and protection section SET
index to where the phyTTP will be attached. In this case
the attachment can also be done by using one SET index:
working or protection section SET index.
PROTGROUP The attachment will be done to a protection group. The
destination protection group has to be created before
executing the attach command based on the protection
group. In this case, it is obligatory to give also the
protection group id value.
SET index
This parameter defines the SET index to where the attachment will be done. If the
phyTTP to be attached is based on the SET, the attachment can be done to a single
SET. This parameter is obligatory in case the destination attach object is SET.
protection group id
This parameter defines the protection group to where the attachment will be done. The
destination protection group has to be created before executing the attach command
based on the protection group id. This parameter is obligatory in case the destination
attach object is PROTGROUP.
Examples
1. Attach the SET based detached phyTTP 2 to SET index 3.
YDS:2:SET,3;
2. Attach the Protection group based detached phyTTP 3 to the working section SET
index 4 and protection section SET index 12.
YDS:3:PGSET,4,12;
Issue: 05 DN015954 17
YDS ATTACH PHYTTP TO PHYSICAL INTERFACE YD - Physical Layer Trail Termination Point Handling
3. Attach the Protection group based detached phyTTP 4 to the working section SET
index 2.
YDS:4:PGSET,2;
4. Attach the Protection group based detached phyTTP 8 to the protection section SET
index 10.
YDS:8:PGSET,,10;
5. Attach the detached phyTTP 15 to the protection group 5.
YDS:15:PROTGROUP,5;
Execution printouts
The execution printout of command example 1 is:
ATTACHED PHYTTP: 2
COMMAND EXECUTED
The execution printout of command example 2 is:
ATTACHED PHYTTP: 3
COMMAND EXECUTED
The execution printout of command example 3 is:
ATTACHED PHYTTP: 4
COMMAND EXECUTED
The execution printout of command example 4 is:
ATTACHED PHYTTP: 8
COMMAND EXECUTED
The execution printout of command example 5 is:
ATTACHED PHYTTP: 15
COMMAND EXECUTED
Semantic error messages
18 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDS ATTACH PHYTTP TO PHYSICAL INTERFACE
If an error occurs, the system outputs a general MML semantic error message.
Execution error messages
If an error occurs, the system outputs a general MML execution error message.
Issue: 05 DN015954 19
YDT INTERROGATE DETACHED PHYTTP YD - Physical Layer Trail Termination Point Handling
output mode
This parameter identifies the execution output mode.
The parameter can have the following values:
BASIC Basic information of the detached phyTTP is interrogated
and output. This is the default output mode value.
ALL ALL information of the detached phyTTP is interrogated
and output.
Examples
1. Interrogate BASIC information of the detached phyTTP 1.
ZYDT:1:BASIC;
2. Interrogate BASIC information of all the detached phyTTPs by using the default
phyTTP id value ALL and the default output mode value BASIC.
ZYDT:;
3. Interrogate information of all the detached phyTTPs
ZYDT::ALL;
Execution printouts
The execution printout of command example 1 could be:
20 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDT INTERROGATE DETACHED PHYTTP
COMMAND EXECUTED
The execution printout of command example 2 could be:
COMMAND EXECUTED
The execution printout of command example 3 could be:
Issue: 05 DN015954 21
YDT INTERROGATE DETACHED PHYTTP YD - Physical Layer Trail Termination Point Handling
22 DN015954 Issue: 05
YD - Physical Layer Trail Termination Point Handling YDT INTERROGATE DETACHED PHYTTP
FORMAT:64 BYTES
VALUE:
OUT_PATH_TRACE_OUT_PATH_TRACE_OUT_PATH_TRACE_OUT_PATH_TRACE_OU
Issue: 05 DN015954 23
YDT INTERROGATE DETACHED PHYTTP YD - Physical Layer Trail Termination Point Handling
VALUE: -
COMMAND EXECUTED
Semantic error messages
If an error occurs, the system outputs a general MML semantic error message.
Execution error messages
If an error occurs, the system outputs a general MML execution error message.
24 DN015954 Issue: 05