Operations and Maintenance Using CLI

Alcatel-Lucent 7302

INTELLIGENT SERVICES ACCESS MANAGER

Alcatel-Lucent 7330

INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE NODE

Alcatel-Lucent 7356

INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE BUILDING OPERATIONS AND MAINTENANCE USING CLI FOR FD 24GBPS NT

R 4 . 3 . 02 3 H H - 1 0104- AAAA-T QZZA E ditio n 0 2 Re le ase d Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2011 © Alcatel-Lucent. All rights reserved.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. Alcatel, Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Copyright 2011 Alcatel-Lucent. All rights reserved. Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications. This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products. However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

When printed by Alcatel-Lucent, this document is printed on recycled paper.

Preface

This preface provides general information about the documentation set for the 7302 Intelligent Services Access Manager (7302 ISAM), the 7330 Intelligent Services Access Manager Fiber to the Node (7330 ISAM FTTN) and the 7356 Intelligent Services Access Manager Fiber to the Building (7356 ISAM FTTB).

Scope This documentation set provides information about safety, features and functionality, ordering, hardware installation and maintenance, CLI and TL1 commands, and software upgrade and migration procedures for the current release.

Audience This documentation set is intended for planners, administrators, operators, and maintenance personnel involved in installing, upgrading, or maintaining the 7302 ISAM, the 7330 ISAM FTTN or the 7356 ISAM FTTB.

Required knowledge Readers must be familiar with general telecommunications principles.

Product naming When the term “ISAM” is used alone, the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB are meant. If a feature is valid for only one of the products, the applicability will be explicitly stated.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

iii

Preface

Documents Refer to the Product Information document for your product to see a list of all relevant customer documents and their part numbers.

Acronymns and initialisms The expansions and optional descriptions of most acronyms and initialisms appear in the glossary which is included in the System Description for FD 24Gbps NT document.

Assistance and ordering phone numbers Alcatel-Lucent provides global technical support through regional call centers. Phone numbers for the regional call centers are available at the following URL: http://www.alcatel-lucent.com/myaccess. For ordering information, contact your Alcatel-Lucent sales representative.

Safety information For safety information, see the Safety Manual for your product.

Special information The following are examples of how special information is presented in this document. Danger — Danger indicates that the described activity or situation

may result in serious personal injury or death; for example, high voltage or electric shock hazards. Warning — Warning indicates that the described activity or situation

may, or will, cause equipment damage or serious performance problems. Caution — Caution indicates that the described activity or situation

may, or will, cause service interruption.

Note — A note provides information that is, or may be, of special

interest.

iv

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Preface

Release notes Be sure to refer to the release notes (such as the Customer Release Notes or Emergency Fix Release Note) issued for software loads of your product before you install or use the product. The release notes provide important information about the software load.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

v

Preface

vi

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

Preface

iii

Scope ............................................................................................... iii Audience ............................................................................................... iii Required knowledge ...................................................................................iii Product naming ........................................................................................ iii Documents .............................................................................................. iv Acronymns and initialisms ............................................................................ iv Assistance and ordering phone numbers ........................................................... iv Safety information ..................................................................................... iv Special information.................................................................................... iv Release notes............................................................................................ v

1—

Introduction 1.1 1.2 1.3

1-1

Introduction .............................................................................. 1-2 How to use this document ............................................................. 1-2 Configuration examples ................................................................ 1-5

Index List (IXL) IXL 100 —

Master Task Index List

IXL 100-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

vii

Contents

Non-Trouble Procedures (NTP) NTP 1101 — Execute script files

NTP 1101-1

NTP 1114 — Perform equipment repairs

NTP 1114-1

NTP 1118 — Monitor performance and view configuration

NTP 1118-1

NTP 1119 — Modify DSL services

NTP 1119-1

NTP 1124 — Maintain the system

NTP 1124-1

NTP 1126 — Manage system logging

NTP 1126-1

NTP 1127 — Configure SHDSL

NTP 1127-1

NTP 1130 — Configure Link Related Ethernet OAM

NTP 1130-1

NTP 1132 — Configure Connectivity Fault Management NTP 1132-1 NTP 2100 — Initial system configuration

NTP 2100-1

NTP 2103 — Configure equipment

NTP 2103-1

NTP 2104 — Configure a VLAN cross-connect

NTP 2104-1

NTP 2105 — Configure an iBridge VLAN

NTP 2105-1

NTP 2106 — Configure an IP-aware bridge

NTP 2106-1

NTP 2107 — Configure an IP router

NTP 2107-1

NTP 2108 — Configure services

NTP 2108-1

viii

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

NTP 2115 — Monitor alarms

NTP 2115-1

NTP 2116 — Perform software management

NTP 2116-1

NTP 2117 — Modify system parameters

NTP 2117-1

NTP 2120 — Troubleshooting the network

NTP 2120-1

NTP 2121 — Manage an SNMP proxy CPE

NTP 2121-1

NTP 2122 — Cluster management

NTP 2122-1

NTP 2129 — Configure a loopback interface on the SHub

NTP 2129-1

NTP 2133 — Configure an enhanced IP router

NTP 2133-1

Detailed Level Procedures (DLP) DLP 1100 — Set up a local CLI session or a local TL1 session

DLP 1100-1

DLP 1112 — Lock and unlock equipment

DLP 1112-1

DLP 1113 — Configure the equipment

DLP 1113-1

DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect

DLP 1117-1

DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect

DLP 1118-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

ix

Contents

DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect

DLP 1119-1

DLP 1120 — Configure a VLAN on the LT for C-iBridge

DLP 1120-1

DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT

DLP 1124-1

DLP 1129 — Create xDSL profiles

DLP 1129-1

DLP 1130 — Configure xDSL bonding

DLP 1130-1

DLP 1134 — Configure QoS

DLP 1134-1

DLP 1145 — Configure 802.1x

DLP 1145-1

DLP 1146 — Configure PPPoE relay on LT

DLP 1146-1

DLP 1147 — Configure PPPoX cross-connect

DLP 1147-1

DLP 1151 — Shut down and restart the NT

DLP 1151-1

DLP 1152 — Reboot the system

DLP 1152-1

DLP 1153 — Shut down and restart individual equipment

DLP 1153-1

DLP 1159 — Manage OSWP

DLP 1159-1

DLP 1163 — Modifying xDSL profiles

DLP 1163-1

DLP 1170 — Configure SSH and SFTP

DLP 1170-1

DLP 1173 — Switch a user from ADSL to VDSL

DLP 1173-1

x

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

DLP 1174 — Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect DLP 1174-1 DLP 1182 — Configure SHDSL

DLP 1182-1

DLP 1183 — Configure IMA on SHDSL spans

DLP 1183-1

DLP 1187 — Configure global VLAN parameters on the LT

DLP 1187-1

DLP 1188 — Configure custom PSD points

DLP 1188-1

DLP 1189 — Configure VDSL2 virtual noise values

DLP 1189-1

DLP 1190 — Configure threshold crossing alerts

DLP 1190-1

DLP 1197 — View port configuration and operational data on LT

DLP 1197-1

DLP 1201 — Configure protocol tracing

DLP 1201-1

DLP 1202 — Configure QoS threshold crossing alerts

DLP 1202-1

DLP 1203 — Configure general security settings

DLP 1203-1

DLP 1205 — Configure Link Related Ethernet OAM

DLP 1205-1

DLP 1206 — Configure an xDSL DPBO profile

DLP 1206-1

DLP 1207 — Modify an xDSL DPBO profile

DLP 1207-1

DLP 1208 — Configure xDSL power back off

DLP 1208-1

DLP 1212 — Create an IP user/subnet

DLP 1212-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

xi

Contents

DLP 1215 — Configure the impulse noise sensor on an xDSL line

DLP 1215-1

DLP 1217 — Configure the xDSL overrule data

DLP 1217-1

DLP 1219 — Forced NT switchover

DLP 1219-1

DLP 1220 — Manage the CDE profile

DLP 1220-1

DLP 1221 — Manage troubleshooting counters on LT

DLP 1221-1

DLP 1225 — Configure the p-bit counter on a VLAN port

DLP 1225-1

DLP 1232 — Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge DLP 1232-1 DLP 1253 — Configure the third-party equipment management port on the 7356 FD REM

DLP 1253-1

DLP 1255 — Configure a port on the NELT-B LT

DLP 1255-1

DLP 1257 — Configure a line with an xDSL RTX profile

DLP 1257-1

DLP 1258 — Modify an xDSL RTX profile

DLP 1258-1

DLP 1270 — Configure spanning tree on the NELT-B LT DLP 1270-1 DLP 1271 — Configure link aggregation on the NELT-B LT

DLP 1271-1

DLP 1282 — Configure the fairness SLA on the NELT-B LT

DLP 1282-1

xii

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

DLP 1283 — Troubleshooting congestion on the NELT-B LT DLP 1283-1 DLP 1291 — Configure a Vectoring Control Entity profile and associate it to a board

DLP 1291-1

DLP 1292 — Modify a Vectoring Control Entity profile

DLP 1292-1

DLP 1293 — Delete a Vectoring Control Entity profile

DLP 1293-1

DLP 1294 — Configure or modify the mapping between the VP board and the SLV LT boards DLP 1294-1 DLP 1295 — Configure a line with an xDSL vectoring profile

DLP 1295-1

DLP 1296 — Modify an xDSL vectoring profile

DLP 1296-1

DLP 1297 — Delete an xDSL vectoring profile

DLP 1297-1

DLP 1298 — Monitor xDSL vectoring lines

DLP 1298-1

DLP 2101 — Create operator profiles and instances

DLP 2101-1

DLP 2103 — Configure system parameters

DLP 2103-1

DLP 2105 — Configure link aggregation usage

DLP 2105-1

DLP 2107 — Manage OSPF

DLP 2107-1

DLP 2108 — Configure RIP

DLP 2108-1

DLP 2109 — Configure SNMP and trap management

DLP 2109-1

DLP 2110 — Manage alarms

DLP 2110-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

xiii

Contents

DLP 2111 — Plan, replan, and unplan equipment

DLP 2111-1

DLP 2114 — Configure NT redundancy

DLP 2114-1

DLP 2115 — Create a L2-terminated forwarder VLAN

DLP 2115-1

DLP 2116 — Create a L2-terminated router VLAN

DLP 2116-1

DLP 2121 — Add a network/LAG port to a VLAN in the SHub

DLP 2121-1

DLP 2122 — Create a forwarding VRF

DLP 2122-1

DLP 2123 — Create a router VRF

DLP 2123-1

DLP 2125 — Create an IPoA user

DLP 2125-1

DLP 2126 — Create an IPoE user

DLP 2126-1

DLP 2128 — Add an LT port to a VLAN on the SHub

DLP 2128-1

DLP 2132 — Configure filtering on the NT

DLP 2132-1

DLP 2136 — Configure the multicast service in the system

DLP 2136-1

DLP 2137 — Configure a multicast VLAN

DLP 2137-1

DLP 2138 — Configure a multicast channel

DLP 2138-1

DLP 2139 — Configure DHCP relay agent in iBridge mode

DLP 2139-1

DLP 2140 — Configure DHCP relay agent in router mode

DLP 2140-1

xiv

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

DLP 2141 — Configure DHCP relay agent in forwarder mode

DLP 2141-1

DLP 2142 — Configure the system security domain

DLP 2142-1

DLP 2144 — Configure RADIUS

DLP 2144-1

DLP 2150 — Configure ARP table entry

DLP 2150-1

DLP 2154 — Create a snapshot alarm table

DLP 2154-1

DLP 2155 — Monitor alarms

DLP 2155-1

DLP 2157 — Manage the SHub database

DLP 2157-1

DLP 2160 — View version of the SHub software

DLP 2160-1

DLP 2162 — Modify the external management VLAN

DLP 2162-1

DLP 2164 — Ping another host

DLP 2164-1

DLP 2165 — Perform a traceroute action

DLP 2165-1

DLP 2166 — Configure SNMP proxy CPE management

DLP 2166-1

DLP 2167 — Script files

DLP 2167-1

DLP 2168 — Modify the system management IP parameters

DLP 2168-1

DLP 2169 — Configure cluster management

DLP 2169-1

DLP 2171 — Enable EMS management

DLP 2171-1

DLP 2172 — Create a default operator profile

DLP 2172-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

xv

Contents

DLP 2175 — Configure system management IP parameters

DLP 2175-1

DLP 2176 — Performance monitoring commands

DLP 2176-1

DLP 2177 — Configure SFP downlink ports

DLP 2177-1

DLP 2179 — Configure system logging

DLP 2179-1

DLP 2180 — Configure static MAC addresses

DLP 2180-1

DLP 2181 — Configure operator authentication via RADIUS

DLP 2181-1

DLP 2185 — Configure DHCP MAC concentration in forwarder mode

DLP 2185-1

DLP 2186 — Configure ANCP session

DLP 2186-1

DLP 2191 — Enable dual tagging in the SHub

DLP 2191-1

DLP 2195 — Configure general bridge parameters on the LT

DLP 2195-1

DLP 2196 — Configure Voice SIP

DLP 2196-1

DLP 2198 — Configure the multicast service on a user port

DLP 2198-1

DLP 2199 — Configure QoS on the SHub

DLP 2199-1

DLP 2200 — Configure Spanning Tree on the SHub

DLP 2200-1

DLP 2204 — Configure an unnumbered IP interface on the SHub

DLP 2204-1

xvi

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

DLP 2209 — Configure vMAC

DLP 2209-1

DLP 2210 — View the status of various system parameters

DLP 2210-1

DLP 2211 — Configure SFP uplink ports

DLP 2211-1

DLP 2213 — Enable OAM counters

DLP 2213-1

DLP 2214 — Configure connectivity fault management

DLP 2214-1

DLP 2216 — Configure Voice MEGACO

DLP 2216-1

DLP 2222 — Create the PCCP group

DLP 2222-1

DLP 2223 — Configure SHub port mirroring

DLP 2223-1

DLP 2224 — Change shelf mode

DLP 2224-1

DLP 2230 — Configure a VLAN on the SHub

DLP 2230-1

DLP 2231 — Manage the ports on the NT

DLP 2231-1

DLP 2236 — Configure the enhanced system clock synchronization

DLP 2236-1

DLP 2273 — External Packet Forwarding

DLP 2273-1

Routine Task Procedure (RTP) RTP 1102 — Retrieve remote inventory

RTP 1102-1

RTP 1103 — Retrieve board temperature

RTP 1103-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

xvii

Contents

RTP 2100 — Backup the configuration

RTP 2100-1

RTP 2101 — Restore the configuration

RTP 2101-1

Trouble Analysis Procedure (TAP) TAP 1100 — Metallic test access

TAP 1100-1

TAP 1101 — F5 loopback test

TAP 1101-1

TAP 1102 — Equipment repair

TAP 1102-1

TAP 1103 — Single ended line testing

TAP 1103-1

TAP 1105 — Dual-ended line testing

TAP 1105-1

TAP 1106 — ITSC

TAP 1106-1

TAP 1107 — MELT

TAP 1107-1

TAP 1108 — Integrated NBLT for MEGACO Termination TAP 1108-1 TAP 1109 — Integrated NBLT for SIP Termination

TAP 1109-1

TAP 2104 — Fault isolation and troubleshooting

TAP 2104-1

Training (TNG) TNG 1104 — DHCP relay agent configuration

TNG 1104-1

TNG 1105 — Overall software packages

TNG 1105-1

xviii

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Contents

TNG 1107 — xDSL parameters

TNG 1107-1

TNG 1108 — SHDSL parameters

TNG 1108-1

TNG 1115 — Slot numbering schemes

TNG 1115-1

TNG 1116 — Link Related Ethernet OAM (EFM OAM)

TNG 1116-1

TNG 1119 — vMAC

TNG 1119-1

TNG 1120 — VLAN translation

TNG 1120-1

TNG 1121 — xDSL bonding

TNG 1121-1

TNG 2100 — Service installation

TNG 2100-1

TNG 2101 — QoS configuration

TNG 2101-1

TNG 2102 — IGMP and multicast configuration

TNG 2102-1

TNG 2106 — Specifying 7330 ISAM FTTN expansion units using the CLI

TNG 2106-1

TNG 2109 — Performance management counters

TNG 2109-1

TNG 2110 — Configuration examples

TNG 2110-1

TNG 2112 — 7330 ISAM FTTN configuration for subtending

TNG 2112-1

TNG 2117 — Enhanced iBridge

TNG 2117-1

TNG 2118 — PPPoE with MAC address concentration

TNG 2118-1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

xix

Contents

Appendix (A) A.

Configuration example values for FD 24Gbps NT A.1 A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 A.10 A.11

A-1

Purpose ................................................................................... A-2 Equipment................................................................................ A-2 xDSL profiles ............................................................................. A-3 SHub ports................................................................................ A-3 VLANs ..................................................................................... A-4 VRFs ....................................................................................... A-5 Lines....................................................................................... A-6 IP bridge .................................................................................. A-7 IP forwarder.............................................................................. A-7 IP router .................................................................................. A-8 Enhanced IP router...................................................................... A-8

Index

xx

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

1—

Introduction

1.1 Introduction

1-2

1.2 How to use this document 1.3 Configuration examples

1-2 1-5

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

1-1

1 — Introduction

1.1

Introduction This document provides instructions on CLI operation and maintenance tasks and procedures for the Alcatel-Lucent 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB. These tasks and procedures are identical for the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB, unless specified otherwise. Throughout the document, the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB will be referred to as the Network Element (NE). See the CLI Commands for FD 24Gbps NT document for more detailed information about the CLI command syntax.

1.2

How to use this document This document follows the task-oriented practice (TOP). The TOP method is a documentation system that uses different types of layers, or documents, to describe the installation, operations, and maintenance of telecommunications equipment and software. Most layers in the TOP system provide step-by-step instructions for the completion of a specific task or procedure. A TOP document is structured so that experienced and less experienced users can effectively use the material to perform work assignments. Less experienced users can refer to detailed procedures to complete a task. Experienced users can bypass detailed procedures and use only the level of information that they need.

TOP layers TOP documentation is constructed in layers, which provide the user with easy access to any point within the task description. This guide may contain any of the following layers:

• • • • • •

Index List (IXL) Non-Trouble Procedure (NTP) Detailed Level Procedure (DLP) Routine Task Procedure (RTP) Trouble Analysis Procedure (TAP) Training (TNG)

Figure 1-1 shows the major paths of TOP layers that may be used in this guide.

1-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

1 — Introduction Figure 1-1 TOP layers and major paths

Index List (IXL)

Non-Trouble Procedure (NTP)

Routine Task Procedure (RTP)

Trouble Analysis Procedure (TAP)

Training (TNG)

Detailed Level Procedure (DLP)

Task index list (IXL)

An IXL lists the available tasks in the TOP document. An IXL is used to find a task category and the applicable procedures to perform a task. Non-trouble procedure (NTP)

An NTP describes how to perform a task, such as how to save a system after it has been installed, turn up a system for service, or maintain a system according to a maintenance plan. NTPs are made up of steps that often refer to DLPs or TNGs. Less experienced users, or experienced users who need more information, can go to the DLPs for detailed procedural and safety information, and TNGs for supporting information. If users go to the referenced DLP or TNG, they must return to the NTP to continue the procedure. Detailed level procedure (DLP)

A DLP contains detailed steps that describe how to perform a task. In addition to step-by-step information, a DLP contains any tables or illustrations that may be required to perform the task. DLPs are typically referenced from an NTP, always referenced from the IXL, and sometimes referenced from other DLPs. When a DLP is referenced from another layer, users must return to the layer at which the DLP was referenced to continue the procedure. Routine task procedure (RTP)

An RTP describes how to perform a routine maintenance task. RTPs are typically referenced from the IXL.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

1-3

1 — Introduction

Trouble analysis procedure (TAP)

A TAP describes how to identify and clear trouble in the system. TAPs are made up of step-by-step instructions. For less experienced users, or experienced users who need more information, some tasks provide a reference to a DLP or TNG. If users go to the referenced DLP or TNG, they must return to the TAP to continue the procedure. Training (TNG)

A TNG contains supplementary information about a task or procedure. A TNG might refer to a DLP or other document. If users go to the referenced document, they need to return to the TNG to read the remaining information.

Step details NTPs, DLPs, RTPs and TAPs use procedural steps and decision steps. Procedural steps provide instructions, and decision steps provide a go-to choice. Procedural steps may contain notations that refer to additional information such as tables, figures, examples and other TOP layers. For example, a step in an NTP might refer to a DLP. Key information required to complete a step is shown at the beginning of the step. More detailed information, which can be accessed according to experience level, is provided at the end of the step, as shown in the example below: “Reconnect the power feeds; see DLP 106.” The completion of a specific task or procedure is indicated as follows: “STOP. This procedure is complete.”

Procedures with options or substeps When there are options in a procedure, they are identified by letters. When there are required substeps in a procedure, they are identified by Roman numerals.

Procedure 1-1 Example of options in a procedure At step 1, you can choose option a or b. At step 2, you must do what the step indicates. 1

2

1-4

This step offers two options. You must choose one of the following: a

This is one option.

b

This is another option.

You must perform this step.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

1 — Introduction

Procedure 1-2 Example of required substeps in a procedure At step 1, you must perform a series of substeps within a step. At step 2, you must do what the step indicates. 1

2

1.3

This step has a series of substeps that you must perform to complete the step. You must perform the following substeps: i

This is the first substep.

ii

This is the second substep.

iii

This is the third substep.

You must perform this step.

Configuration examples Configuration examples are provided in the DLPs. Different rack configurations are used in the examples. These are indicated with Config#1, Config#2 and Config#3. Appendix A “Configuration example values for FD 24Gbps NT” gives an overview of the different configurations and values used in the DLP configuration examples.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

1-5

1 — Introduction

1-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Index List (IXL)

IXL 100 — Master Task Index List

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

IXL 100 — Master Task Index List Table IXL 100-1: Non-Trouble Procedures (NTPs) Title

NTP number

Execute script files

NTP 1101

Perform equipment repairs

NTP 1114

Monitor performance and view configuration

NTP 1118

Modify DSL services

NTP 1119

Maintain the system

NTP 1124

Manage system logging

NTP 1126

Configure SHDSL

NTP 1127

Configure Link Related Ethernet OAM

NTP 1130

Configure Connectivity Fault Management

NTP 1132

Initial system configuration

NTP 2100

Configure equipment

NTP 2103

Configure a VLAN cross-connect

NTP 2104

Configure an iBridge VLAN

NTP 2105

Configure an IP-aware bridge

NTP 2106

Configure an IP router

NTP 2107

Configure services

NTP 2108

Monitor alarms

NTP 2115

Perform software management

NTP 2116

Modify system parameters

NTP 2117

Troubleshooting the network

NTP 2120

Manage an SNMP proxy CPE

NTP 2121

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

IXL 100-1

IXL 100 — Master Task Index List

Title

NTP number

Cluster management

NTP 2122

Configure a loopback interface on the SHub

NTP 2129

Configure an enhanced IP router

NTP 2133

(2 of 2)

Table IXL 100-2: Detailed Level Procedures (DLP) Title

DLP number

Set up a local CLI session or a local TL1 session

DLP 1100

Lock and unlock equipment

DLP 1112

Configure the equipment

DLP 1113

Configure a VLAN on the LT for C-VLAN cross-connect

DLP 1117

Configure a VLAN on the LT for S-VLAN cross-connect

DLP 1118

Configure a VLAN on the LT for S+C-VLAN cross-connect

DLP 1119

Configure a VLAN on the LT for C-iBridge

DLP 1120

Create an xDSL/native Ethernet user and add this user to a VLAN on the LT

DLP 1124

Create xDSL profiles

DLP 1129

Configure xDSL bonding

DLP 1130

Configure QoS

DLP 1134

Configure 802.1x

DLP 1145

Configure PPPoE relay on LT

DLP 1146

Configure PPPoX cross-connect

DLP 1147

Shut down and restart the NT

DLP 1151

Reboot the system

DLP 1152

Shut down and restart individual equipment

DLP 1153

Manage OSWP

DLP 1159

Modifying xDSL profiles

DLP 1163

Configure SSH and SFTP

DLP 1170

Switch a user from ADSL to VDSL

DLP 1173

Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect

DLP 1174

Configure SHDSL

DLP 1182

Configure IMA on SHDSL spans

DLP 1183

Configure global VLAN parameters on the LT

DLP 1187

Configure custom PSD points

DLP 1188

Configure VDSL2 virtual noise values

DLP 1189

Configure threshold crossing alerts

DLP 1190

View port configuration and operational data on LT

DLP 1197

(1 of 4)

IXL 100-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

IXL 100 — Master Task Index List

Title

DLP number

Configure protocol tracing

DLP 1201

Configure QoS threshold crossing alerts

DLP 1202

Configure general security settings

DLP 1203

Configure Link Related Ethernet OAM

DLP 1205

Configure an xDSL DPBO profile

DLP 1206

Modify an xDSL DPBO profile

DLP 1207

Configure xDSL power back off

DLP 1208

Create an IP user/subnet

DLP 1212

Configure the impulse noise sensor on an xDSL line

DLP 1215

Configure the xDSL overrule data

DLP 1217

Forced NT switchover

DLP 1219

Manage the CDE profile

DLP 1220

Manage troubleshooting counters on LT

DLP 1221

Configure the p-bit counter on a VLAN port

DLP 1225

Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge

DLP 1232

Configure the third-party equipment management port on the 7356 FD REM

DLP 1253

Configure a port on the NELT-B LT

DLP 1255

Configure a line with an xDSL RTX profile

DLP 1257

Modify an xDSL RTX profile

DLP 1258

Configure spanning tree on the NELT-B LT

DLP 1270

Configure link aggregation on the NELT-B LT

DLP 1271

Configure the fairness SLA on the NELT-B LT

DLP 1282

Troubleshooting congestion on the NELT-B LT

DLP 1283

Configure a Vectoring Control Entity profile and associate it to a board

DLP 1291

Modify a Vectoring Control Entity profile

DLP 1292

Delete a Vectoring Control Entity profile

DLP 1293

Configure or modify the mapping between the VP board and the SLV LT boards

DLP 1294

Configure a line with an xDSL vectoring profile

DLP 1295

Modify an xDSL vectoring profile

DLP 1296

Delete an xDSL vectoring profile

DLP 1297

Monitor xDSL vectoring lines

DLP 1298

Create operator profiles and instances

DLP 2101

Configure system parameters

DLP 2103

Configure link aggregation usage

DLP 2105

Manage OSPF

DLP 2107

Configure RIP

DLP 2108

Configure SNMP and trap management

DLP 2109

(2 of 4)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

IXL 100-3

IXL 100 — Master Task Index List

Title

DLP number

Manage alarms

DLP 2110

Plan, replan, and unplan equipment

DLP 2111

Configure NT redundancy

DLP 2114

Create a L2-terminated forwarder VLAN

DLP 2115

Create a L2-terminated router VLAN

DLP 2116

Add a network/LAG port to a VLAN in the SHub

DLP 2121

Create a forwarding VRF

DLP 2122

Create a router VRF

DLP 2123

Create an IPoA user

DLP 2125

Create an IPoE user

DLP 2126

Add an LT port to a VLAN on the SHub

DLP 2128

Configure filtering on the NT

DLP 2132

Configure the multicast service in the system

DLP 2136

Configure a multicast VLAN

DLP 2137

Configure a multicast channel

DLP 2138

Configure DHCP relay agent in iBridge mode

DLP 2139

Configure DHCP relay agent in router mode

DLP 2140

Configure DHCP relay agent in forwarder mode

DLP 2141

Configure the system security domain

DLP 2142

Configure RADIUS

DLP 2144

Configure ARP table entry

DLP 2150

Create a snapshot alarm table

DLP 2154

Monitor alarms

DLP 2155

Manage the SHub database

DLP 2157

View version of the SHub software

DLP 2160

Modify the external management VLAN

DLP 2162

Ping another host

DLP 2164

Perform a traceroute action

DLP 2165

Configure SNMP proxy CPE management

DLP 2166

Script files

DLP 2167

Modify the system management IP parameters

DLP 2168

Configure cluster management

DLP 2169

Enable EMS management

DLP 2171

Create a default operator profile

DLP 2172

Configure system management IP parameters

DLP 2175

Performance monitoring commands

DLP 2176

Configure SFP downlink ports

DLP 2177

(3 of 4)

IXL 100-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

IXL 100 — Master Task Index List

Title

DLP number

Configure system logging

DLP 2179

Configure static MAC addresses

DLP 2180

Configure operator authentication via RADIUS

DLP 2181

Configure DHCP MAC concentration in forwarder mode

DLP 2185

Configure ANCP session

DLP 2186

Enable dual tagging in the SHub

DLP 2191

Configure general bridge parameters on the LT

DLP 2195

Configure Voice SIP

DLP 2196

Configure the multicast service on a user port

DLP 2198

Configure QoS on the SHub

DLP 2199

Configure Spanning Tree on the SHub

DLP 2200

Configure an unnumbered IP interface on the SHub

DLP 2204

Configure vMAC

DLP 2209

View the status of various system parameters

DLP 2210

Configure SFP uplink ports

DLP 2211

Enable OAM counters

DLP 2213

Configure connectivity fault management

DLP 2214

Configure Voice MEGACO

DLP 2216

Create the PCCP group

DLP 2222

Configure SHub port mirroring

DLP 2223

Change shelf mode

DLP 2224

Configure a VLAN on the SHub

DLP 2230

Configure the enhanced system clock synchronization

DLP 2236

External Packet Forwarding

DLP 2273

(4 of 4)

Table IXL 100-3: Routine Task Procedure (RTP) Title

RTP number

Retrieve remote inventory

RTP 1102

Retrieve board temperature

RTP 1103

Backup the configuration

RTP 2100

Restore the configuration

RTP 2101

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

IXL 100-5

IXL 100 — Master Task Index List Table IXL 100-4: Trouble Analysis Procedure (TAP) Title

TAP number

Metallic test access

TAP 1100

F5 loopback test

TAP 1101

Equipment repair

TAP 1102

Single ended line testing

TAP 1103

Dual-ended line testing

TAP 1105

ITSC

TAP 1106

MELT

TAP 1107

Integrated NBLT for MEGACO Termination

TAP 1108

Integrated NBLT for SIP Termination

TAP 1109

Fault isolation and troubleshooting

TAP 2104

Table IXL 100-5: Training (TNG) Title

TNG number

DHCP relay agent configuration

TNG 1104

Overall software packages

TNG 1105

xDSL parameters

TNG 1107

SHDSL parameters

TNG 1108

Link Related Ethernet OAM (EFM OAM)

TNG 1116

vMAC

TNG 1119

VLAN translation

TNG 1120

xDSL bonding

TNG 1121

Service installation

TNG 2100

QoS configuration

TNG 2101

IGMP and multicast configuration

TNG 2102

Specifying 7330 ISAM FTTN expansion units using the CLI

TNG 2106

Performance management counters

TNG 2109

Configuration examples

TNG 2110

7330 ISAM FTTN configuration for subtending

TNG 2112

Slot numbering schemes

TNG 1115

Enhanced iBridge

TNG 2117

PPPoE with MAC address concentration

TNG 2118

IXL 100-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Non-Trouble Procedures (NTP)

NTP 1101 — Execute script files NTP 1114 — Perform equipment repairs NTP 1118 — Monitor performance and view configuration NTP 1119 — Modify DSL services NTP 1124 — Maintain the system NTP 1126 — Manage system logging NTP 1127 — Configure SHDSL NTP 1130 — Configure Link Related Ethernet OAM NTP 1132 — Configure Connectivity Fault Management NTP 2100 — Initial system configuration NTP 2103 — Configure equipment NTP 2104 — Configure a VLAN cross-connect NTP 2105 — Configure an iBridge VLAN NTP 2106 — Configure an IP-aware bridge NTP 2107 — Configure an IP router NTP 2108 — Configure services

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2115 — Monitor alarms NTP 2116 — Perform software management NTP 2117 — Modify system parameters NTP 2120 — Troubleshooting the network NTP 2121 — Manage an SNMP proxy CPE NTP 2122 — Cluster management NTP 2129 — Configure a loopback interface on the SHub NTP 2133 — Configure an enhanced IP router

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1101 — Execute script files Purpose A script file is a file containing CLI commands. A script file must follow the same syntax rules as commands entered interactively. Only the tab and the question mark lose their special meaning in a script, so command expansion and single-line help are not available. The script will be aborted if one of the commands in the script fails. A command may be preceded by a minus '-' to prevent the script from being aborted in case of a semantic error; for example, when you try to delete a node instance that does not exist. By default, a command script does not interact with the user. The execution of the script will be aborted if a command or filter requires interaction with the user. Interactivity can be enabled by specifying the interactive option with the exec command. Command scripts may not be nested.

Caution — When an NT switchover takes place during execution of the script, the possibility exists that CLI commands will fail. To recover from this situation the operator should delete the objects which were created before. Then, the CLI command (or script) must be re-executed.

Procedure In order to use script files, you need to perform the following tasks: 1

Create and execute script files; see DLP 2167.

2

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1101-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1101 — Execute script files

NTP 1101-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1114 — Perform equipment repairs Purpose This procedure provides the steps to perform equipment repair on the NE.

Procedure Proceed as follows to perform equipment repair tasks: 1

Plan, unplan, and replan equipment (for example, plug-in units); see DLP 2111.

2

Pull out and plug in equipment. For the procedures, see the hardware installation manual for your equipment.

3

Lock and unlock equipment (mostly plug-in units); see DLP 1112.

4

Start up or shut down the system, select one of:

5

a

Shut down or restart the NT; see DLP 1151.

b

Reboot the entire system; see DLP 1152.

c

Shut down individual equipment; see DLP 1153.

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1114-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1114 — Perform equipment repairs

NTP 1114-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1118 — Monitor performance and view configuration Purpose This procedure list the procedures that can be used for:

• •

Performance Monitoring (PM) viewing the configuration and operational data of a port

Procedure The following tasks can be performed: 1

Configure the Threshold Crossing Alert (TCA); see DLP 1190.

2

Enable the Operations and Maintenance (OAM) counters; see DLP 2213.

3

Manage the troubleshooting counters on the LT; see DLP 1221.

4

Viewing the PM counters; see DLP 2176.

5

Viewing the configuration and operational data of a port (xDSL or Ethernet); see DLP 1197.

6

View the status of different system parameters (system clock, memory usage on the NT and CPU load on the NT); see DLP 2210.

7

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1118-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1118 — Monitor performance and view configuration

NTP 1118-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1119 — Modify DSL services Purpose This procedure provides the steps to adapt the following services on the NE:

• •

xDSL profiles switching a user from ADSL to VDSL

Procedure You can perform the following tasks: 1

Modify an xDSL profile; see DLP 1163.

2

Modify a DPBO profile; see DLP 1207.

3

Modify an RTX profile; see DLP 1258.

4

Modify an xDSL vectoring profile; see DLP 1296.

5

Modify an Vectoring Control Entity profile; see DLP 1292.

6

Switch a user from ADSL to VDSL; see DLP 1173.

7

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1119-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1119 — Modify DSL services

NTP 1119-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1124 — Maintain the system Purpose This NTP provides the steps for system maintenance of the NE.

Procedure Perform this procedure to maintain the system: 1

Back up the system configuration; see RTP 2100.

2

Restore the system configuration; see RTP 2101.

3

Retrieve the remote inventory; see RTP 1102.

4

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1124-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1124 — Maintain the system

NTP 1124-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1126 — Manage system logging Purpose This NTP provides the steps to manage system logging (SYSLOG) for the NE.

General System statistics logs are user configurable and you can create up to 64 system logs. System logs can be saved locally to a remote server, or all active CLI terminals, or all active TL1 terminals. You can perform the following three main tasks using CLI:

• • •

enable and disable logging for all system logs create and configure up to 64 system logs monitor system logs

Using filters, you can determine which messages are sent to the system log file, as well as set the severity level of the system log. The following applies when using SYSLOG in an operational (E2E) environment:

• •

The NE supports SYSLOG according to RFC3164 (aka BSD SYSLOG) The SYSLOG application on the external server has to listen to UDP port 514. Everything that comes in via this port should be considered as being a SYSLOG message. The NE sends out its SYSLOG messages on this port.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1126-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1126 — Manage system logging

•

The severity of the various application messages is predefined. It is reported as follows: • CLI operator commands: INFO • Service Affecting alarm messages: EMERGENCY • Authentication messages: ALERT • Other CLI/TL1 messages (non-service affecting): INFO • protocol tracing: DEBUG • videoCDR reporting: NOTICE

Note — See DLP 1201 for the configuration of protocol tracing.

See the CLI Command Guide for FD 24Gbps NT document for more information about CLI commands used to configure system logging. See the System Description for FD 24Gbps NT document for more information about system and security statistics logging.

Procedure Use this procedure to manage system logging for the NE. See the references for detailed procedures and safety information.

NTP 1126-2

1

Enable and disable logging for all system logs; see DLP 2179.

2

Create, configure, and monitor system logs; see DLP 2179.

3

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1127 — Configure SHDSL Purpose Single-pair High-speed Digital Subscriber Line (SHDSL) is a physical layer standard based on the ITU-T Recommendation G.991.2. It describes a versatile transmission method for data transport in the telecommunication access networks, capable of supporting whichever network protocol is currently deployed while enabling higher bandwidth and reach (for example, TDM, ATM, Frame Relay and so on). SHDSL transceivers are designed primarily for duplex operation over mixed gauges of two wire twisted metallic pairs. Four-wire and m-pair operations are included as options for extended reach. The use of signal regenerators for both the two-wire and the multi-wire operations is optional. Inverse Multiplexing for ATM (IMA) permits a broadband cell stream to be transported on a number of lower-rate physical links (for example, several SHDSL span lines) by grouping these physical links into a single logical channel. The specification includes a means to maintain cell order and a method to allow in-service loss and restore of individual physical links.

Note — For a more detailed description of the different parameters for SHDSL span, unit and segment configuration, refer to TNG 1108.

Procedure Proceed as follows to configure SHDSL: 1

To configure SHDSL; see DLP 1182.

2

To configure IMA on SHDSL spans; see DLP 1183.

3

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1127-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1127 — Configure SHDSL

NTP 1127-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1130 — Configure Link Related Ethernet OAM Purpose This procedure provides the steps to configure Link Related Ethernet OAM (EFM OAM) on the NE and view local and remote (CPE) EFM OAM configuration, statistics, and counters.

Note — For more information on Link Related Ethernet OAM, see TNG 1116.

Procedure Proceed as follows to configure EFM OAM: 1

Configuration of EFM OAM; see DLP 1205.

2

After configuration, the following actions can be performed:

3

a

Viewing of Local and Remote (CPE) information; see DLP 1205.

b

Viewing of EFM OAM statistics; see DLP 1205.

c

Retrieve MAC counters; see DLP 1205.

d

Retrieve PME counters; see DLP 1205.

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1130-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1130 — Configure Link Related Ethernet OAM

NTP 1130-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 1132 — Configure Connectivity Fault Management Purpose This NTP provides the steps for configuring Connectivity Fault Management (CFM) on the NE and for viewing CFM configuration.

General CFM (802.1ag) is an Ethernet OAM capability providing end to end fault detection and isolation on Ethernet networks. CFM requires that bridge ports throughout the network be configured with software entities, called “maintenance points” (MP). MPs process and respond to CFM messages sent on the dataplane. By looking at the replies from these MPs, a network operator can isolate a fault to a specific link or node. MPs are organized by maintenance domain (MD) and maintenance association (MA). See the System Description for FD 24Gbps NT document for more information about CFM. You can configure MPs on the NE to process and respond to CFM messages sent from the edge router or BNG. You cannot initiate CFM tests from the NE. To configure CFM, you must configure an MD, an MA, and you must configure an MEP or you must configure the MA to auto-create MIPs. The ISAM supports MIPs and network facing MEPs at user ports. Within these MPs the ISAM responds to LBMs and to LTMs coming from the network. The ISAM responds to LBM coming from the user (see DSLF TR-101). The ISAM supports network facing MEPs on the LT board at its GE interface towards the NT board. Within these MEPs the ISAM responds to LBMs and to LTMs. See DLP 2214 for more information on configuration restrictions and prerequisites. You can also view CFM configuration data on the NE.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1132-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 1132 — Configure Connectivity Fault Management

Prerequisites The following prerequisites must be fulfilled before CFM can be configured:

• • •

You must have network management access or craft port access to the NE you want to configure and be familiar with the CLI. CFM must be supported on the access aggregation network. A VLAN must be configured.

Procedure Use this procedure to configure CFM or view CFM configuration. 1

NTP 1132-2

Configure CFM: i

Configure a maintenance domain; see DLP 2214

ii

Configure (create) a maintenance association; see DLP 2214

iii

Configure a maintenance end point; see DLP 2214

iv

Optionally, configure (modify) the maintenance association and set the mhf-creation parameter to mhf-default; see DLP 2214

2

View CFM configuration; see DLP 2214

3

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2100 — Initial system configuration Purpose This document describes the procedure to be used to perform the initial system configuration.

General Figure NTP 2100-1 shows the management topology of the NE system. Figure NTP 2100-1: Management Topology EMS (e.g. AMS 5520)

SNMPv2 or SNMPv3

SNMP agent

TL1 Gateway

UDP

TL1 Terminal

SSH

TL1 agent

Telnet

TL1 CT

CLI Terminal

RS232

SSH

Telnet

CLI agent

CLI CT

Debug Terminal

RS232

UDP

Debug agent

ISAM Table NTP 2100-1 lists the different types of system managers.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2100-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2100 — Initial system configuration Table NTP 2100-1: System Managers Manager type

Description

EMS

Remotely connected Element Management System based on SNMP

TL1 CT

Local Craft Terminal using TL1 commands

CLI CT

Local Craft Terminal using Command Line Interface (CLI) commands

CLI terminal

Remotely connected terminal using CLI commands based over telnet or ssh

TL1 gateway

Remotely connected gateways using TL1 commands over UDP

TL1 terminal

Remotely connected terminal using TL1 commands based on ssh

See the CLI Command Guide for FD 24Gbps NT document for detailed information about the CLI command syntax. See the TL1 Commands and Messages for FD 24Gbps NT document for detailed information about the TL1 command syntax.

Security Considerations The following must be taken into account with regard to system security:

• • • • • • •

It is advised to close the remote debug acess. By default, the accesss is not disabled. It is advised to use secure management channels (CLI/SSH, TL1/SSH, SNMPv3, SFTP). This implies closing the unsecured management channels. It is NOT advised to use unsecured remote management channels: CLI/Telnet, TL1/UDP, SNMPv1/2, or TFTP. If SNMPv1/2 is used anyway, it is advised not to use community string = public. It is advised to change the administrator password of TL1 and CLI (even if TL1 or CLI is not used by the operator). It is advised to deactivate the remote TL1 management interface when no remote TL1 is used. It is not possible to deactivate the local Craft Terminal TL1 access. SHub ACLs can be configured to restrict the traffic from the Element Management Systems (and other management plane services) to be routed to the NT OBC.

Procedure Proceed as follows to perform an initial system configuration:

NTP 2100-2

1

Set up a CLI session; see DLP 1100.

2

Create and configure an Operator Profile; see DLP 2101.

3

Create a default Operator Profile; see DLP 2172.

4

Configure the management IP parameters and network interfaces; see DLP 2175.

5

Configure SSH; see DLP 1170.

6

Configure the general security settings; see DLP 1203.

7

Configure the system parameters; see DLP 2103.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2100 — Initial system configuration

8

Configure the enhanced system clock synchronization; see DLP 2236.

9

Configure Simple Network Management Protocol (SNMP) and trap management; see DLP 2109.

10

Enable the management of EMS; see DLP 2171.

11

Configure the alarm management; see DLP 2110.

12

Save the SHub database; see DLP 2157.

13

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2100-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2100 — Initial system configuration

NTP 2100-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2103 — Configure equipment Purpose This procedure provides the steps to:

• • •

plan, unplan, or replan the equipment lock or unlock the equipment configure the SFP uplink ports and the SFP downlink ports

Some equipment-related items, such as the shelf, are auto-created at system startup and do not need to be created. However, they can be modified.

General The NE consists of a single shelf with plug-in units. You can perform the actions described in Table NTP 2103-1 to configure the equipment. Table NTP 2103-1: Configure plug-in units Action

Description

Planning equipment

Planning a piece of equipment is possible before and after the equipment is physically present and detected by the system (at startup). The system verifies the configuration parameters and checks if the required equipment is available. Note: As long as equipment is not planned, it is impossible to offer service. Units and other equipment are only available from an operation and maintenance point of view.

Unplanning equipment

If necessary, you can unplan any equipment. Unplanning, however, may be rejected in case of hierarchical dependencies. For example, it is impossible to unplan a shelf as long as one or more units in it are still planned.

Replanning equipment

Replanning is done when changing the current equipment.

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2103-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2103 — Configure equipment

Action

Description

Locking and unlocking equipment

When necessary, you can lock any equipment, most often a unit, to put it out of service. Locking a unit renders it inactive. No traffic is generated or received by the units. All alarms related to the unit are filtered except for the “board-missing”, “board installation missing” and “board-type mismatch” alarms. However, the unit is not removed from the configuration, and as soon as you unlock the unit, it becomes active again. It goes back to operational mode without restart or initialization, and traffic can resume immediately. Similarly, you can power down the unit and restart it at a later time. In this case, however, the unit will go through a complete startup cycle before traffic is possible.

(2 of 2)

Change the shelf mode When required, the shelf mode can be changed from NTIO_SUPPORTED (for shelves equipped with an NTIO board (and a second NT board) to NTIO_UNSUPPORTED (for shelves where an NTIO board is not required, in this case 2 extra LT slots are available) or vice versa.

Note — Changing the shelf mode results in an automatic restart of the system.

Procedure Proceed as follows to configure or modify the system equipment:

NTP 2103-2

1

Plan, replan, or unplan equipment; see DLP 2111.

2

Lock or unlock the equipment; see DLP 1112.

3

Modify the configuration of the system equipment; see DLP 1113.

4

If required, change the shelf mode; see DLP 2224.

5

Configure SFP downlink ports; see DLP 2177.

6

Configure SFP uplink ports; see DLP 2211.

7

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2104 — Configure a VLAN cross-connect Purpose The NE supports several VLAN cross-connect models:

• • •

Customer VLAN cross-connect or C-VLAN CC Service provider VLAN cross-connect or S-VLAN CC VLAN stacking or S+C-VLAN CC

Purpose of C-VLAN CC This is the most straightforward VLAN cross-connect model where a single VLAN ID at the EMAN side is associated with a given PVC at the user side. Any kind of traffic issued by the subscriber is passed transparently towards the network using the selected VLAN ID. Cross-connect VLANs can be enabled to be protocol aware for IGMP and 802.1x and to support the configuration of DHCP Option 82 and PPPoE relay.

Purpose of S-VLAN CC In this mode, the Service Provider VLAN (S-VLAN) ID at the EMAN side is associated with a single subscriber interface at the user side. The C-VLANs carried within the S-VLAN are passed transparently to the end user. This allows the end user to specify its own end-to-end connectivity, while remaining transparent for the EMAN. The NE acts as an S-VLAN aware bridge, with the restriction that only one subscriber interface can be attached. Forwarding is only done based on the S-VLAN forwarding context. The forwarding is transparent for the C-VLANs. Frames on the subscriber interface may or may not have an S-VLAN tag. In case of an absent S-VLAN tag (that is for C-VLAN tagged and untagged/priority tagged frames), the subscriber interface’s pre-configured S-VLAN ID will be assigned.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2104-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2104 — Configure a VLAN cross-connect

Purpose of S+C-VLAN CC The basic VLAN cross-connect mode suffers from the fact the that number of VLAN identifiers is limited to 4K. Since the VLAN is a EMAN wide identifier, one ends up with a scalability issue: there cannot be more than 4K end users connected to the whole EMAN. To solve this issue, two VLANs are stacked and the cross-connection is then performed on the combination (S-VLAN, C-VLAN) allowing to theoretically reach up to 16M end users. The NE acts as a C-VLAN aware bridge, with the restriction that only one subscriber interface can be attached. Frames on the subscriber interface may be C-VLAN tagged or untagged/priority tagged. In case of C-VLAN tagged frames, a check will be performed on the received C-VLAN ID, while the subscriber interface‘s preconfigured S-VLAN will be assigned. In case of untagged/priority tagged frames, the subscriber interface’s pre-configured C-VLAN and S-VLAN will be assigned.

Prerequisite The following prerequisites must be fulfilled before a VLAN-CC of any type can be configured:

• •

The board must have been planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129.

Procedure Proceed as follows (see also Figure NTP 2104-1):

NTP 2104-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2104 — Configure a VLAN cross-connect Figure NTP 2104-1: Configure a VLAN Cross-connect on an SHub-based ISAM DLP 1117 (DLP 1118) (DLP 1119)

DLP 2230 DLP 2231

Network Ports

DLP 2121

SHub VLAN

DLP 2231 LT VLAN for

LT port C-VLAN CC

DLP 1124 DLP 1174

DLP 2128

C 11

VLAN 11 (=Bridge)

VLAN CC

VLAN 17 (=Bridge)

VLAN CC

Phy

S17 +C23

C-VLAN CC

S+C-VLAN CC

LT (No VLAN translation shown on user side)

VLAN 13 (=Bridge)

S17 +C29 VLAN CC

S+C-VLAN CC

Phy Phy

LAG

S 13

VLAN 19 (=Bridge) DLP 2105

VLAN CC

S-VLAN CC

LT

NT_SHUB ISAM_SHUB

1

2

C-, S+C- or S-VLAN CC

Configure a VLAN on the LT for VLAN cross-connect. Do one of the following: a

For C-VLAN cross-connect; see DLP 1117.

b

For S-VLAN cross-connect; see DLP 1118.

c

For S+C-VLAN cross-connect; see DLP 1119.

Create a user and add him to a VLAN created in step 1. Do one of the following: a

create an xDSL/native Ethernet user and add him to a VLAN on the LT; see DLP 1124.

b

create an xDSL IPoA user and add him to a VLAN on the LT (for C-VLAN cross-connect): see DLP 1174.

3

Configure network interface and LT interface on the SHub; see DLP 2231.

4

Optionally, configure LAG on the SHub; see DLP 2105.

5

Configure a VLAN on the SHub; see DLP 2230.

• • • 6

In case of C-VLAN cross-connect, the mode of the VLAN must be “cross-connect” and the VLAN ID is the ID of the C-VLAN In case of S-VLAN cross-connect, the mode of the VLAN must be “cross-connect” and the VLAN ID is the ID of the S-VLAN In case of S+C-VLAN cross-connect, the mode of the VLAN must be “cross-connect” and the VLAN ID is the ID of the S-VLAN

Add an LT port to the VLAN on the SHub; see DLP 2128.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2104-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2104 — Configure a VLAN cross-connect

NTP 2104-4

7

Add a network/LAG port to the VLAN on the SHub; see DLP 2121.

8

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2105 — Configure an iBridge VLAN Purpose The concept of a VLAN in intelligent bridging (iBridge) mode is that multiple NSPs are each connected to the NE with a VLAN. The user ports are connected to the VLAN of their corresponding Network Service Provider (NSP). This procedure provides the steps to create an iBridge VLAN.

Prerequisite The following prerequisites must be fulfilled before an iBridge can be configured:

• •

The board must have been planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129.

Procedure Proceed as follows to configure an iBridge (see also Figure NTP 2105-1):

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2105-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2105 — Configure an iBridge VLAN Figure NTP 2105-1: Configure an iBridge

DLP 1120 DLP 2230

DLP 2231

Network DLP 2121 Ports

SHub VLAN

DLP 2231

LT Ports

LT VLAN for iBridge

DLP 1124 DLP 1232

DLP 2128

iBridge VLAN 19

Phy LT

(No VLAN translation shown on user side)

iBridge VLAN 19

Phy LAG

Phy

iBridge VLAN 19

DLP 2105

NT_SHUB

LT

ISAM_SHUB

NTP 2105-2

1

Configure a VLAN on the LT for iBridge; see DLP 1120.

2

Create a user and add him to a VLAN created in step 1. Do one of the following: a

create an xDSL/native Ethernet user and add him to a VLAN on the LT; see DLP 1124.

b

create an xDSL IPoA user and add him to a VLAN on the LT (for iBridge): see DLP 1232.

3

Configure network interface and LT interface on the SHub; see DLP 2231.

4

Optionally, configure LAG on the SHub; see DLP 2105.

5

Configure a VLAN on the SHub; see DLP 2230.

6

Add an LT port to the VLAN on the SHub; see DLP 2128.

7

Add a network/LAG port to the VLAN on the SHub; see DLP 2121.

8

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2106 — Configure an IP-aware bridge Purpose In this mode, the NE can be seen as an IP-aware bridge without being seen as an IP next-hop. Users connected to the NE are seen as being directly attached to the edge router IP interfaces. The end-users use the IP address of the edge router as their default gateway, while the IP edge router sees the end-user subnets as directly attached networks. The NE sits in between and performs packet forwarding at L3. This procedure provides the steps to configure an IP-aware bridge on the NE. Figure NTP 2106-1: IP-aware Bridge VLAN X

NE

Video VLAN

Internet Video

Video VLAN is always in iBridge

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2106-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2106 — Configure an IP-aware bridge Figure NTP 2106-2: IP-aware Bridge: Traffic Flow Source MAC address = PC Destination MAC address = Network

NE

Source MAC address = NE Destination MAC address = Network

PC

Network

Source MAC address = Network Destination MAC address = NE Source MAC address = Network Destination MAC address = PC

Procedure Proceed as follows to configure an IP-aware bridge:

NTP 2106-2

1

Create a forwarder Virtual Routing Forwarding (VRF); see DLP 2122.

2

Create a L2-terminated forwarder VLAN for each of the Network Service Providers (NSP); see DLP 2115.

3

Add the network interfaces to the L2-terminated forwarder VLANs; see DLP 2121.

4

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2107 — Configure an IP router Purpose In this mode, the NE is seen as an IP next-hop by the edge routers to route the IP packets to the users connected to the NE. A single Virtual Router can be configured in this mode, which can co-exist in the same system with a number of VRs that are configured in IP-aware Bridge mode (see NTP 2106). At the user side of the system (xDSL line), unnumbered IP interfaces are used, while user subnets are configured on a user gateway interface. In order to achieve maximum efficiency in the allocation of IP addresses, several users (on different xDSL lines) can share a same subnet. Host routes toward the end-user devices are either dynamically created in the NE in case of dynamic DHCP sessions, or statically provisioned in case of static IP address assignment. Toward the network, IP interfaces are numbered (meaning that the NE IP addresses and subnets are configured).

Caution — The information in this procedure is kept for informational purposes only. The recommended way in which to configure an (enhanced) IP router is described in NTP 2133.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2107-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2107 — Configure an IP router Figure NTP 2107-1: IP Router VLAN X

NE

Video VLAN

Internet Video

VLAN Y Video VLAN is always in iBridge

Virtual VLAN

Figure NTP 2107-2: IP Router: traffic flow Source MAC address = PC Destination MAC address = NE

NE

Source MAC address = NE Destination MAC address = Network

PC

Network

Source MAC address = Network Destination MAC address = NE Source MAC address = NE Destination MAC address = PC

Procedure Proceed as follows to configure an IP router:

NTP 2107-2

1

Create a router VRF; see DLP 2123.

2

Create a L2-terminated router VLAN; see DLP 2116.

3

Add users; see DLP 2125 for adding IPoA user or DLP 2126 for adding IPoE user.

4

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2108 — Configure services Purpose This procedure provides the steps to configure the following services on the NE:

• • • • • • • • • • • • • • •

xDSL profiles Quality of Service (QoS) Multicast Dynamic Host Configuration Protocol (DHCP) relay agent and Option 82 Authentication Point-to-Point Protocol (PPP) configuration NT redundancy Link aggregation Multiple Spanning Tree Protocol (MSTP) Routing protocols (optional) Integrated VoIP Service (MEGACO or SIP) Voice Session Initiation Protocol (SIP) Access Node Control Protocol (ANCP) session Path Connectivity Check Protection (optional) P-bit counter on a VLAN Port (optional)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2108-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

NTP 2108 — Configure services

Procedure To configure a service, you need to perform the following tasks: 1

Configure xDSL profiles: i

For the configuration of the service profiles and the spectrum profiles; see DLP 1129.

ii

For the configuration of custom PSD points; see DLP 1188.

iii

For the configuration of virtual noise values for VDSL2; see DLP 1189.

iv

For the configuration of a Downstream Power Back Off (DPBO) profile; see DLP 1206.

v

For the configuration of an RTX profile (standard ARQ provisioning); see DLP 1257

vi

For the configuration of a Vectoring Control Entity profile; see DLP 1291.

vii

For the configuration of an xDSL vectoring profile; see DLP 1295.

viii For System Level Vectoring (SLV), configuration of the mapping between the VP board and the SLV LT boards; see DLP 1294. For the configuration of power back-off; see DLP 1208.

x

For the configuration of xDSL overrule data; see DLP 1217.

xi

For the configuration of the impulse noise sensor on an xDSL line; see DLP 1215.

2

Configure xDSL bonding; see DLP 1130.

3

Configure general bridge parameters for LT and SHub; see DLP 2195.

4

If required, enable dual tagging on the SHub; see DLP 2191.

5

Configure QoS:

6

NTP 2108-2

ix

i

For the configuration of QoS; see DLP 1134.

ii

For the configuration of QoS on the SHub; see DLP 2199.

iii

For the configuration of QoS Threshold Crossing Alerts (TCA); see DLP 1202.

Configure multicast: i

For the configuration of the multicast service in the system; see DLP 2136.

ii

For the configuration of a multicast VLAN; see DLP 2137.

iii

For the configuration of a multicast channel; see DLP 2138.

iv

For the configuration of the multicast service on a user port; see DLP 2198.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

NTP 2108 — Configure services

7

8

9

10

Configure DHCP Relay: i

For the configuration of the DHCP relay agent in iBridge mode; see DLP 2139.

ii

For the configuration of the DHCP relay agent in router mode; see DLP 2140.

iii

For the configuration of the DHCP relay agent in forwarder mode; see DLP 2141.

iv

For the configuration of DHCP MAC concentration in forwarder mode; see DLP 2185.

Configure the authentication settings: i

For the configuration of the security domain: see DLP 2142.

ii

For the configuration of RADIUS; see DLP 2144.

iii

For the configuration of 802.1x authentication; see DLP 1145.

iv

For the configuration of operator authentication via RADIUS; see DLP 2181.

Configure the PPP relay settings: i

For the configuration of PPPoE relay on the LT; see DLP 1146.

ii

For the configuration of PPPoX cross-connect; see DLP 1147.

If necessary, configure NT redundancy; see DLP 2114.

Note 1 — If NT redundancy is required, then this has to be specifically disabled enabled (this contrary to the earlier, 1. This switchover would result in an SHub configuration loss. iii

Add 1 (or more) network port(s) to the NT 1+1 protection group with the following command: configure interface shub group (group-id) port nt:sfp: | nt:xfp: |

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2114-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2114 — Configure NT redundancy

iv

By default, there is no APS-EPS coupling in the NE. That means that the minimum number of links to be in state operational UP in the protection-group is 0 by default. Or in other words, a link failure will not trigger a switchover from the active NT to the standby NT. If a coupling is required (that is NT switchover in case of link failure), the SHub has to be configured with a threshold > 0 as follows: configure interface shub group (group-id) threshold

v

Unlock the protection group with the following command: configure equipment protection-group (prot-group-id) admin-status unlock

5

You can view the protection group configuration parameters with the following command: show equipment protection-group (prot-group-id)

6

You can view the protection element configuration parameters with the following command: show equipment protection-element (slot-id)

7

STOP. This procedure is complete.

Configuration example (Config#1): configure equipment protection-group 1 admin-status unlock eps-quenchfactor 60000 configure equipment protection-element nt-a redcy-ctrl-status normal configure interface shub port [1...2] admin-status down configure interface shub port [1...2] port-type unused configure interface shub port [1...2] mode automatic port-type subtending configure interface shub port [1...2] admin-status up configure interface shub group 1 configure equipment protection-group 1 admin-status lock configure interface shub group 1 port [1...2] configure interface shub group 1 threshold 2 configure equipment protection-group 1 admin-status unlock configure equipment protection-element nt-b redcy-ctrl-status normal

DLP 2114-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2115 — Create a L2-terminated forwarder VLAN Purpose In the forwarder mode, the LTs operate as IP forwarder and the SHub operates as a bridge. For the LTs, the following applies:

• • •

The user-gateway interface is auto-created by the system when the operator configures the VRF. Subnets of the static users must be configured on the user-gateway interface. Numbered IP interface (trusted or un-trusted) is configured on each network VLAN.

For the SHub, the following applies:

• •

The SHub operates as a bridge. IP addresses that are configured on the network VLANs are owned by the SHub.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2115-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2115 — Create a L2-terminated forwarder VLAN Figure DLP 2115-1: L2-terminated Forwarder VLAN LT PPPoE/A Session PPPoE/A Interface

SHub VRF P-VLAN

ISP

VRF DHCP Relay

ARP Proxy

P-VLAN

VB P-VLAN

LT IPoE/A Session ARP Proxy

IPoE/A Interface

DHCP Relay

VRF

P-VLAN

ISP

ARP Proxy

PPPoE/PPPoA, IPoE/IPoA always untagged

IPoE (P-VLAN)

IPoE (P-VLAN)

This procedure provides the steps to configure a L2-terminated forwarder VLAN.

Prerequisites The following prerequisite must be fulfilled before a L2-terminated forwarder VLAN can be configured:

•

A forwarder VRF must have been configured; see DLP 2122.

Note — In the configuration example, it is assumed that the VRF index of the forwarder VRF is 16.

Procedure Proceed as follows to configure a L2-terminated forwarder VLAN: 1

Create a L2-terminated VLAN on the NT with the following command: configure vlan id (vlanid) (no) name mode layer2-terminated (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) dhcp-opt-82 (no) circuit-id-dhcp (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) dhcpv6-linerate (no) circuit-id-pppoe (no) remote-id-pppoe

DLP 2115-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2115 — Create a L2-terminated forwarder VLAN

(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

2

secure-forwarding aging-time l2cp-transparent in-qos-prof-name ipv4-mcast-ctrl ipv6-mcast-ctrl mac-mcast-ctrl dis-proto-rip proto-ntp dhcpv6-itf-id dhcpv6-remote-id dhcpv6-trst-port enterprise-number icmpv6-sec-fltr dis-ip-antispoof unknown-unicast

Create a bridged VLAN on the SHub with the following command: configure vlan shub id (vlanid) (no) name mode residential-bridge (no) mac-move-allow (no) mac-learning-off (no) user2-comm

3

Create an unnumbered network IP interface on the IPoX interface with the following command: configure ip vrf (vrf-index) network-itf (vlanid) (no) arp-policy unnumbered

4

Define the gateway IP interface with the following command: configure ip vrf (vrf-index) gateway-itf ip-address (ip-address)

5

Add the IP route with the following command: configure ip vrf (index) route-dest (dest-ip-address) next-hop direct:user-port:/ //:: | :network:vlan: | :network:any | direct:network: | direct:user-bridgeport:/ //:: | direct:vlan:/ //:: : | direct:vlan:/

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2115-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2115 — Create a L2-terminated forwarder VLAN

//: | direct:user-port:// / | direct:user-bridgeport:// /

6

Create and configure an SHub network port: i

Configure the SHub network egress port on the network with the following command: configure vlan shub id (vlanid) egress-port (port)

ii

Configure the SHub network egress port on the LT with the following command: configure vlan shub id (vlanid) egress-port lt://

7

Configure the broadcast VLAN with the following command: configure dhcp-relay agent (vrfid) bcast-vlan

8

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan id 101 name “ISPforwVLAN-101” mode layer2-terminated configure vlan shub id 101 name “ISPforwVLAN-101” mode residential-bridge configure ip vrf 16 network-itf 101 arp-policy trusted unnumbered configure ip vrf 16 gateway-itf ip-address 192.168.116.1/21 configure ip vrf 16 route-dest 0.0.0.0/0 next-hop 10.179.136.1:network:vlan:101 configure vlan shub id 101 egress-port network:6 configure vlan shub id 101 egress-port lt:1/1/[4...8] configure dhcp-relay agent 16 bcast-vlan l2-vlan:101

DLP 2115-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2116 — Create a L2-terminated router VLAN Purpose In the router mode, the LTs operate as an IP forwarder and the SHub operates as a router. Between the LTs and the SHub, one VLAN per VRF must be created to indicate the VRF to which the IP packets belong. This VLAN is called as V-VLAN (VRF VLAN). For the LTs, the following applies:

• • • • •

The user-gateway interface is auto-created by the system when the operator configures the VRF. Subnets of the static users must be configured on the user-gateway interface. At least one IP address must be configured on the user-gateway interface. Only one network VLAN (V-VLAN) can be created since LTs will have only one network interface connected to Shub as gateway. An unnumbered IP interface (trusted) is created on the V-VLAN since LTs don't have an IP address on the network interface towards the SHub.

For the SHub, the following applies:

• • •

IP interfaces are created on the network VLANs towards the edge routers. IP interface addresses are seen as the Next-Hop addresses in the downstream from edge routers to ISAM. User-gateway interface is the interface towards the users and it is created on V-VLAN. IP address configured on the user-gateway interface represents the gateway IP address for the users, and subnet configured on the user-gateway interface represents the subnet of the users.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2116-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2116 — Create a L2-terminated router VLAN Figure DLP 2116-1: L2-terminated Router VLAN LT PPPoE/A Session

VRF

PPPoE/A Interface

ARP Proxy

SHub V-VLAN

P-VLAN

IPoE/A Interface

ARP Proxy

DHCP Relay

ARP

VRF

ISP

VRF

LT IPoE/A Session

Routing Protocols (OSPF, RIPv2)

V-VLAN

DHCP Relay

ARP Proxy

PPPoE/PPPoA, IPoE/IPoA always untagged

IPoE (V-VLAN per VR)

IPoE (P-VLAN)

This procedure provides the steps to configure a L2-terminated router VLAN.

Prerequisites The following prerequisite must be fulfilled before a L2-terminated router VLAN can be configured:

•

A router VRF must have been created; see DLP 2123.

Note — In the configuration example, it is assumed that the index of the router VRF of the LT is 16 and the index of the router VRF on the SHub is 5.

Procedure Proceed as follows to configure a L2-terminated router VLAN: 1

Create a virtual L2-terminated VLAN on the LT with the following command: configure vlan id (vlanid) (no) name mode layer2-terminated (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) dhcp-opt-82 (no) circuit-id-dhcp (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) dhcpv6-linerate (no) circuit-id-pppoe

DLP 2116-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2116 — Create a L2-terminated router VLAN

(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

2

remote-id-pppoe secure-forwarding aging-time l2cp-transparent in-qos-prof-name ipv4-mcast-ctrl ipv6-mcast-ctrl mac-mcast-ctrl dis-proto-rip proto-ntp dhcpv6-itf-id dhcpv6-remote-id dhcpv6-trst-port enterprise-number icmpv6-sec-fltr dis-ip-antispoof unknown-unicast

Create a virtual VLAN on the SHub with the following command: configure vlan shub id (vlanid) (no) name mode v-vlan (no) mac-move-allow (no) mac-learning-off (no) user2-comm

3

Add the virtual VLAN to the LT port where the L2-terminated router is active with the following command: configure vlan shub id (vlanid) egress-port (port)

4

Create an IP interface on the virtual VLAN on the SHub with the following command: configure interface shub vlan-id (vlanid)

5

Attach the IP interface to a VRF: configure interface shub ip (vlanid) vrf-id

6

Configure the IP address of the internal IP interface with the following command: configure interface shub ip (vlanid) ip-address /

7

Set the administrative state of the VLAN interface to up with the following command: configure interface shub vlan-id (vlanid) admin-status up

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2116-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2116 — Create a L2-terminated router VLAN

8

Create a L2 network terminated VLAN on the Shub with the following command: configure vlan shub id (vlanid) (no) name mode layer2-term-nwport (no) mac-move-allow (no) mac-learning-off (no) user2-comm

9

Create and configure an SHub network port with the following command: configure interface shub port (network-port) (no) mode port-type network (no) mc-flooding

10

Change the administrative status of the SHub network port with the following command: configure interface shub port (network-port) admin-status up

11

Configure an egress port for the L2 network terminated VLAN on the SHub with the following command: configure vlan shub id (vlanid) egress-port (port)

12

Configure the SHub network egress port for untagged packets with the following command: configure vlan shub id (vlanid) untag-port (port)

13

Configure the port VLAN ID for the untagged packets with the following command: configure bridge shub port (network-port) pvid

14

Create an IP interface on the L2 network terminated VLAN with the following command: configure interface shub vlan-id (vlanid)

15

Attach the IP interface to a VRF with the following command: configure interface shub ip (vlanid) vrf-id

16

Configure the IP address of the external IP interface with the following command: configure interface shub ip (vlanid) ip-address (ip-address)

17

Set the administrative state of the VLAN interface to up with the following command: configure interface shub vlan-id (vlanid) admin-status up

DLP 2116-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2116 — Create a L2-terminated router VLAN

18

Create an unnumbered IP interface on the IPoX interface with the following command: configure ip vrf (vrf-index) network-itf (vlanid) (no) arp-policy unnumbered

19

Configure the gateway IP interface with the following command: configure ip vrf (vrf-index) gateway-itf ip-address (ip-address)

20

Add the IP route with the following command: configure ip shub vrf (index) route-dest (dest) next-hop vlan-id (no) metric

21

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2116-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2116 — Create a L2-terminated router VLAN

Configuration example (for tagged network) (Config#1): configure vlan id 4090 name “ISProutingVLAN” mode layer2-terminated configure vlan shub id 4090 name “ISPvvlanSHub” mode v-vlan configure vlan shub id 4090 egress-port lt:1/1/[4...5] configure interface shub vlan-id 4090 configure interface shub ip 4090 vrf-id 15 configure interface shub ip 4090 ip-addr 10.178.14.97/27 configure interface shub vlan-id 4090 admin-status up configure vlan shub id 1450 name “ISProutingVLAN” mode layer2-term-nwport configure interface shub port 5 mode automatic port-type network configure interface shub port 5 admin-status up configure vlan shub id 1450 egress-port network:5 configure interface shub vlan-id 1450 configure interface shub ip 1450 vrf-id 15 configure interface shub ip 1450 ip-addr 10.178.14.85/27 configure interface shub vlan-id 1450 admin-status up configure ip vrf 5 network-itf 4090 arp-policy trusted unnumbered configure ip vrf 5 gateway-itf ip-address 10.178.14.97/27 configure ip shub vrf 15 route-dest 0.0.0.0/0 next-hop 10.178.14.65 vlan-id 1450

DLP 2116-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2121 — Add a network/LAG port to a VLAN in the SHub Purpose This procedure provides the steps to add a network port (or an LAG port via its primary network port) to a VLAN in the SHub. Figure DLP 2121-1: Add network/LAG port to VLAN on the SHub

DLP Phy iBridge VLAN 19

Phy Phy

LT

LAG

NT_SHUB LT ISAM_SHUB

Prerequisite The following prerequisites must be fulfilled before network ports can be added to a VLAN:

• • •

If the port is a network port, the network port must be configured; see DLP 2231 If the port is a LAG port, the LAG port must be configured; see DLP 2105 An SHub VLAN must have been created; see DLP 2230.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2121-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2121 — Add a network/LAG port to a VLAN in the SHub

Procedure Proceed as follows to add a network/LAG port to a VLAN on the SHub:

Note — Since a LAG is referred to by its primary network port, the procedure to add an LAG port to a VLAN is the same.

1

Configure the SHub network egress port with the following command: configure vlan shub id (vlanid) egress-port (port)

2

Optionally, configure a default VLAN for untagged packets on this network port: i

Configure the SHub network egress port for untagged packets with the following command: configure vlan shub id (vlanid) untag-port (port)

ii

Configure the port VLAN ID for the untagged packets with the following command: configure bridge shub port (port) pvid

3

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan shub id 100 egress-port network:3 configure vlan shub id 100 untag-port network:3 configure bridge shub port 3 pvid 100 configure vlan shub id 299 egress-port network:6

DLP 2121-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2122 — Create a forwarding VRF Purpose In the forwarder mode, the NE is not seen as a hop in the IP path by the edge routers. NE users are seen as directly attached hosts on the IP interfaces of the edge routers. Multiple VRs can be supported. User-to-user communication is not provided by the NE. Figure DLP 2122-1: Create a forwarding VRF

DLP

Forwarding VRF

LT

NT

ISAM

This procedure provides the steps to configure a Virtual Routing Forwarding (VRF) context in forwarding mode on the NT.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2122-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2122 — Create a forwarding VRF

Procedure Proceed as follows to configure the forwarding VRF: 1

Create a VRF in forwarding mode on the NT with the following command: configure ip vrf (index) name (no) desc (no) contact (no) my-ipaddress (no) default-ttl (no) reassem-timeout mode forwarder

Note — The parameter my-ipaddress is an optional parameter. However, if the VRF will be used for PPPoE sessions, then the parameter must be filled in. If this parameter is not filled in, the IP address is assumed to be 0.0.0.0. Most PPPoE clients (running on the PC of the customers), will reject a PPPoE session with a PPPoE server with IP address 0.0.0.0. 2

STOP. This procedure is complete.

Configuration example (Config#1): configure ip vrf 16 name forwardingvrf16 mode forwarder

DLP 2122-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2123 — Create a router VRF Purpose In router mode, the NE is seen as an IP next-hop by the edge routers to route the IP packets to the users connected to the NE. Only one VR in router mode can be configured. The advantages of the router mode are:

• • •

Redundancy for the network routes. ARP table scalability at the edge routers User-to-user communication can be provided by NE at IP level; user-to-user communication can be disabled by ACL filters. Figure DLP 2123-1: Create a router VRF DLP

Router VRF

Fast-path VRF LT

NT

ISAM

This procedure provides the steps to configure a VRF in routing mode.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2123-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2123 — Create a router VRF

Procedure Proceed as follows to configure a VRF in routing mode: 1

Create a VRF in routing mode on the NT with the following command: configure ip vrf (index) name (no) desc (no) contact (no) my-ipaddress (no) default-ttl (no) reassem-timeout mode router

2

Create a VRF in routing mode on the SHub with the following command: configure ip shub vrf (index) name fast-path-mode:ena-user-user-com

Note — The VRF on the SHub must always be created with mode “fast-path-mode”.

3

STOP. This procedure is complete.

Configuration example (Config#1): configure ip vrf 5 name routervrf5 mode router configure ip shub vrf 15 name routervrf15 fast-path-mode:ena-user-user-com

DLP 2123-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2125 — Create an IPoA user Purpose This procedure provides the steps to create an IPoA user.

Prerequisites The following prerequisites must be fulfilled before an IPoA user can be created:

• • •

The LT must be planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129. An IP-aware bridge (see NTP 2106) or an IP router (see NTP 2107) must have been configured.

Procedure Proceed as follows to create an IPoA user: 1

Create an xDSL line with the following command: configure xdsl line (if-index) service-profile none | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts (no) g992-1-a (no) g992-1-b (no) g992-2-a (no) g992-3-a (no) g992-3-b (no) g992-3-l1 (no) g992-3-l2 (no) g992-3-aj

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2125-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2125 — Create an IPoA user

(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

2

g992-3-am g992-5-a g992-5-b ansi-t1.424 etsi-ts itu-g993-1 ieee-802.3ah g992-5-aj g992-5-am g993-2-8a g993-2-8b g993-2-8c g993-2-8d g993-2-12a g993-2-12b g993-2-17a g993-2-30a carrier-data-mode admin-status transfer-mode

Configure the xDSL line with the following command: configure interface port xdsl-line:// / admin-up (no) user

3

Create an ATM PVC with the following command: configure atm pvc (port-index) (no) admin-down (no) aal5-encap-type llc-snap-routed | vc-mux-routed | automatic:ip

4

5

Do one of the following: a

If an IP router is being used (see “Prerequisites”), continue with step 5

b

If an IP-aware bridge is being used (see “Prerequisites”), continue with step 6.

Create a route in the SHub towards the modem with the following command: configure ip shub vrf (index) route-dest (dest) next-hop vlan-id where: route-dest is the subnet which is assigned to the user next-hop is the IP address of the WAN side of the modem.

6

Create a user port interface with the following command: configure ip vrf (index) user-itf port (port-interface) (no) qos-profile none | name:

7 DLP 2125-2

If the user is a static user, continue with the next step, else go to 9.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2125 — Create an IPoA user

8

Configure the IP address to the IP interface with the following command: configure ip vrf (index) route-dest (dest-ip-address) next-hop direct:user-port // /

Note 1 — This command must be repeated for each IP address assigned to that particular user. Note 2 — For the parameter dest-ip-address: only subnet /32 is allowed. 9

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl line 1/1/5/13 service-profile 7 spectrum-profile 5 admin-up configure atm pvc 1/1/5/13:8:35 no admin-down aal5-encap-type vc-mux-routed configure ip vrf 16 user-itf port 1/1/5/13:8:35 configure ip vrf 16 route-dest 10.178.14.53/32 next-hop direct:user-port:1/1/5/13:8:35

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2125-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2125 — Create an IPoA user

DLP 2125-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2126 — Create an IPoE user Purpose This procedure provides the steps to create an IPoE user.

Prerequisites The following prerequisites must be fulfilled before an IPoE user can be created:

• • •

The LT must be planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129. An IP-aware bridge (see NTP 2106) or an IP router (see NTP 2107) must have been configured.

Procedure Proceed as follows to create an IPoE user: 1

Create an xDSL line with the following command: configure xdsl line (if-index) service-profile none | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts (no) g992-1-a (no) g992-1-b (no) g992-2-a (no) g992-3-a (no) g992-3-b (no) g992-3-l1 (no) g992-3-l2 (no) g992-3-aj

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2126-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2126 — Create an IPoE user

(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

g992-3-am g992-5-a g992-5-b ansi-t1.424 etsi-ts itu-g993-1 ieee-802.3ah g992-5-aj g992-5-am g993-2-8a g993-2-8b g993-2-8c g993-2-8d g993-2-12a g993-2-12b g993-2-17a g993-2-30a carrier-data-mode admin-status transfer-mode

Note — The value of the parameter transfer-mode must be set to atm if an ADSL service is required. The value of the parameter can be left on ptm (default value) if a VDSL service or a VDSL2 service is required. 2

Configure the xDSL line with the following command: configure interface port xdsl-line:/// admin-up (no) user

3

4

Do one of the following: a

For a user on an ADSL line, continue with step 4

b

For a user on a VDSL or VDSL 2 line, continue with step 6.

Create an ATM PVC with the following command: configure atm pvc (port-index) (no) admin-down (no) aal5-encap-type llc-snap | vc-mux-bridged-8023 | automatic

5

Create a bridge port with the following command: configure bridge port (port)

6

Create a user port interface with the following command: configure ip vrf (index) user-itf bridgeport (port-interface) (no) qos-profile none | name:

7

DLP 2126-2

If the user is a static user, continue with the next step, else go to 4.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2126 — Create an IPoE user

8

Configure the IP address to the IP interface with the following command: configure ip vrf (index) route-dest (dest-ip-address) next-hop direct:user-bridgeport:// /::

Note — For the parameter dest-ip-address: only subnet /32 is allowed.

9

STOP. This procedure is complete.

Configuration examples (Config#1): 1. For an ADSL user: configure xdsl line 1/1/5/14 service-profile 7 spectrum-profile 5 transfer-mode atm admin-up configure atm pvc 1/1/5/14:8:35 aal5-encap-type vc-mux-bridged-8023 configure bridge port 1/1/5/14:8:35 configure ip vrf 5 user-itf bridgeport 1/1/5/14:8:35 2. For a VDSL or VDSL 2 user: configure xdsl line 1/1/4/14 service-profile 8 spectrum-profile 4 admin-up configure bridge port 1/1/4/14 configure ip vrf 5 user-itf bridgeport 1/1/4/14

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2126-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2126 — Create an IPoE user

DLP 2126-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2128 — Add an LT port to a VLAN on the SHub Purpose This procedure provides the steps to add an LT port to a VLAN in the SHub. Figure DLP 2128-1: Add LT port to VLAN on the SHub

DLP

Phy VLAN

Phy Phy

LT

LAG

NT_SHUB LT ISAM_SHUB

Prerequisite The following prerequisites must be fulfilled before network ports can be added to a VLAN:

• •

The LT port on the SHub must have been configured see DLP 2231 An SHub VLAN must have been created; see DLP 2230.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2128-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2128 — Add an LT port to a VLAN on the SHub

Procedure Proceed as follows: 1

Configure an LT port on the SHub with the following command: configure vlan shub id (vlanid) egress-port lt://

2

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan shub id 200 egress-port lt:1/1/4 configure vlan shub id 299 egress-port lt:1/1/5

DLP 2128-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2132 — Configure filtering on the NT Purpose This procedure provides the steps to configure filtering on the NT. The IP filters for the different protocols take into account source and/or destination IP addresses; either or both must be specified. Optionally the ICMP message type and/or the ICMP message code can be specified. The physical ports where the filters have to be applied are configured subsequently, by means of dedicated configuration commands. When the filter is to be applied to incoming traffic, the command to configure the in-port is to be used. When the filter is to be applied to outgoing traffic, the command to configure the out-port is to be used.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2132-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2132 — Configure filtering on the NT

Procedure Proceed as follows to configure filtering on the NT: 1

Configure the SHub MAC filter with the following command: configure transport shub mac-infilter (index-num) port (no) protocol-type filter vlan-id (no) action-drop

Caution — If the following command is used: configure transport shub mac-infilter action-drop filter any-any

(index-num)

then all traffic (both user and control data) from any port and with any MAC address will be blocked. As a result the LTs will not be managed anymore and they try to reboot. An “inot-boot-failed” alarm will be raised. 2

Configure the rate limit with the following command: configure transport shub rate-limit (ctrl-index) (no) lookup-enabled (no) bcast-pkt-enabled (no) mcast-pkt-enabled max-nbr-pkts

3

Configure an ICMP filter on the SHub with the following command: configure system shub filter ip-filter icmp (index-num) (no) action-drop (no) dst-ip-addr / (no) src-ip-addr / (no) msg-type (no) msg-code (no) direction (no) vlan-id

4

Configure the physical ports where the ICMP filter related to incoming traffic is to be applied with the following command: configure system shub filter ip-filter icmp (index-num) (no) in-port (port)

DLP 2132-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2132 — Configure filtering on the NT

5

Configure the physical ports where the ICMP filter related to outgoing traffic is to be applied: configure system shub filter ip-filter icmp (index-num) (no) out-port (port)

Caution — If egress filtering is used, please be aware that packets matching the filter parameters will only be allowed to egress on the ports marked in the out-port list. 6

Configure a TCP filter on the SHub with the following command: configure system shub filter ip-filter tcp (index-num) (no) action-drop (no) dst-ip-addr / (no) src-ip-addr / (no) min-dst-port (no) max-dst-port (no) min-src-port (no) max-src-port (no) ack (no) rst (no) tos (no) direction (no) vlan-id

7

Configure the physical ports where the TCP filter related to incoming traffic is to be applied with the following command: configure system shub filter ip-filter tcp (index-num) (no) in-port (port)

8

Configure the physical ports where the TCP filter related to outgoing traffic is to be applied: configure system shub filter ip-filter tcp (index-num) (no) out-port (port)

9

Configure an UDP filter on the SHub with the following command: configure system shub filter ip-filter udp (index-num) (no) action-drop (no) dst-ip-addr / (no) src-ip-addr / (no) min-dst-port (no) max-dst-port (no) min-src-port (no) max-src-port (no) direction (no) vlan-id

10

Configure the physical ports where the UDP filter related to incoming traffic is to be applied with the following command: configure system shub filter ip-filter udp (index-num) (no) in-port (port)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2132-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2132 — Configure filtering on the NT

11

Configure the physical ports where the UDP filter related to outgoing traffic is to be applied: configure system shub filter ip-filter udp (index-num) (no) out-port (port)

12

Configure an IP filter on the SHub (for protocols other than ICMP, TCP or UDP) for incoming traffic with the following command: configure system shub filter ip-filter in-port (filter-rule) port (no) protocol (no) action-drop (no) dst-ip-addr (no) src-ip-addr (no) vlan-id

Note — The IP filter takes into account source and/or destination IP addresses; either or both must be specified. The physical ports where the filters have to be applied are configured subsequently, by means of dedicated configuration commands. 13

Configure an IP filter on the SHub (for protocols other than ICMP, TCP or UDP) for outgoing traffic with the following command: configure system shub filter ip-filter out-port (filter-rule) port (no) action-drop (no) dst-ip-addr (no) src-ip-addr (no) vlan-id

Note — The IP filter takes into account source and/or destination IP addresses; either or both must be specified. The physical ports where the filters have to be applied are configured subsequently, by means of dedicated configuration commands. 14

The information on the counters for layer 2 filters can be viewed with the following command: show transport shub mac (index-num) [port ]

Note — Layer 2 filter counters are supported on all the NT boards, except the ECNT-A board.

15

The layer 3 filter information can be viewed with the following command: show system shub filters ip [(index-num)]]

16

DLP 2132-4

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2132 — Configure filtering on the NT

Configuration example (Config#1): configure transport shub mac-infilter 450 port lt:1/1/4 protocol-type 2222 filter any-56:0d:9d:47:dd:aa vlan-id 100 action-drop configure transport shub mac-infilter 451 port lt:1/1/4 protocol-type 2222 filter any-56:0d:9d:47:dd:bb vlan-id 100 action-drop configure system shub filter ip-filter icmp 12 src-ip-addr 192.168.0.1/16 direction out configure system shub filter ip-filter icmp 12 in-port 3 configure system shub filter ip-filter icmp 12 out-port lt:1/1/4 configure system shub filter ip-filter tcp 12 src-ip-addr 192.168.0.1/16 direction out configure system shub filter ip-filter tcp 12 in-port 3 configure system shub filter ip-filter tcp 12 out-port network:3 configure system shub filter ip-filter udp 14 src-ip-addr 192.168.0.1/16 direction out configure system shub filter ip-filter udp 14 in-port 3 configure system shub filter ip-filter udp 14 out-port network:3 configure system shub filter ip-filter in-port 10 port network:4 protocol rsvp action-drop src-ip-addr 192.168.0.1/16 configure system shub filter ip-filter out-port 11 port lt:1/1/5 protocol rsvp src-ip-addr 192.168.0.1/16 show transport shub mac 450 show system shub filters ip 10

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2132-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2132 — Configure filtering on the NT

DLP 2132-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2136 — Configure the multicast service in the system Purpose This procedure provides the steps to configure the multicast service in the system. It is typically executed once, when the multicast service is deployed.

Procedure Proceed as follows to configure multicast on IACM and SHub: 1

Configure the IGMP system parameters in the SHub: i

Configure the IGMP protocol parameters in the SHub with the following command: configure igmp shub igs-system (no) start-snooping (no) enable-snooping self-ip-addr-mode configure | from-ip (no) self-ip-addr trace-selection (no) router-purge-intv (no) host-purge-intv

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2136-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2136 — Configure the multicast service in the system

(no) (no) (no) (no) (no)

ii

max-mcast-learn glb-leave reduced-resp-int remove-root-int full-flooding-off

Configure the CAC parameters in the SHub with the following command: configure mcast shub (no) active-streams (no) max-bw (no) max-no-rate-based

Note — The CAC parameters are related to uplink CAC. This step can be skipped if no uplink CAC is required.

2

Configure the IGMP system parameters in IACM: i

Configure the IGMP protocol parameters in the IACM with the following command: configure igmp system (no) src-ip-address (no) verify-checksum (no) query-interval (no) max-rsp-time (no) robustness (no) mem-query-int (no) last-memb-cnt (no) last-max-resp-tim (no) host-report-intv (no) start (no) preview-valid (no) cdr-validation (no) cdr-generation (no) except-cdr-rate (no) cdr-export (no) cdr-file-aging (no) cdr-polling (no) user-igmp-version (no) netw-igmp-version (no) v3-max-num-rec (no) forking (no) vlan-selection (no) disc-lwr-version

DLP 2136-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2136 — Configure the multicast service in the system

Note 1 — The network side IGMP version must be the same as the IGMP version configured at the SHub. The user side IGMP version can be different, the IGMP system will do the translations. Note 2 — The default version is IGMPv3. Note 3 — If the CDR must be logged on a remote server, the parameter cdr-export must be set to remote-logging. The remote server must have been configured before this command can be executed; see DLP 2179. Note 4 — When forking is enabled all received IGMP packets on a user interface will be forked to the network port. The forking feature can be enabled on system level but also on port level (see DLP 2198). Note 5 — Changing from no vlan-selection to vlan-selection is only possible when the default service context profile is used on all multicast channels and multicast services. ii

Configure the CAC parameters in the IACM with the following command: configure mcast capacity (no) max-num-group (no) max-num-uncfg (no) cfg-res-time (no) uncfg-res-time

Note — The CAC parameters are related to the SHub-LIM link. This step can be skipped if the default settings are OK.

iii

Configure the CDR parameters with the following command: configure igmp system cdr-type (no) periodic (no) period (no) attempt-max-pview (no) attempt-blackout (no) attempt-no-perm

Note — The CDR parameters are related to the Call Data Records. This step can be skipped if CDR is not required.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2136-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2136 — Configure the multicast service in the system

3

Configure the non-configured multicast parameters:

Note — Non-configured multicast parameters are related to a multicast service without pre-configured multicast channels (like best-effort video). This step can be skipped if all multicast services use pre-configured multicast channels. i

Configure the general parameters, which apply to all non-configured multicast channels, with the following command: configure mcast general (no) fast-change (no) pkg-memb-bitmap (no) max-bitrate (no) mean-bit-rate

Note 1 — The minimum bitrate available for multicast is configured with the command configure xdsl service-profile; see DLP 1129. Note 2 — The parameter pkg-memb-bitmap is kept for backward compatibility with previous releases. ii

Configure a package for non-configured multicast with the following command: configure igmp package (index) (no) name (no) template-name template-version

iii

Assign the package generally with the following command: configure mcast general (no) package-member (package)

Note — The package is intended primarily for use by a network element manager, such as AMS, to support multiple sets of packages in different regions. A package is a group of zero or more multicast sources that share a common access permission. By grouping the source channels into one or more packages, it provides flexibility for the service provider to deliver different levels of services to the end-users, for example, “Basic Package”, “Middle-Tier Package”, and “Premium Package”. 4

If required, configure a service context profile on the IACM. This profile is attached to a multicast channel and a multicast service on a user port to denote a provider's context. Use the following command: configure igmp mcast-svc-context (name)

5

DLP 2136-4

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2136 — Configure the multicast service in the system

Configuration example (Config#1): configure igmp shub igs-system enable-snooping self-ip-addr-mode configure self-ip-addr 192.168.100.100 start-snooping configure igmp system start verify-checksum configure mcast general fast-change configure igmp package 1 name NonConfigured template-version 1 configure mcast general package-member 1 configure igmp mcast-svc-context OrangeTV configure igmp mcast-svc-context YellowTV

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2136-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2136 — Configure the multicast service in the system

DLP 2136-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2137 — Configure a multicast VLAN Purpose This procedure provides the steps to configure a VLAN, and some related objects, for multicast services. It is typically configured once, when the multicast service is deployed. In a wholesale environment it is typically configured for each multicast service provider.

Prerequisites The following prerequisites must be fulfilled before a multicast VLAN can be configured:

• •

The multicast service is configured; see DLP 2136. A VLAN has been configured on the LT for iBridge; see DLP 1120.

Procedure Proceed as follows to configure a multicast VLAN on IACM and SHub: 1

Configure the IGMP VLAN protocol parameters in the SHub with the following command: i

Configure the VLAN filter to enable or disable IGMP snooping on that specific VLAN with the following command: configure igmp shub vlan-filter (filter-id) (no) snoop-filter (no) igmp-version (no) operation-mode (no) self-ip-addr-mode (no) self-ip-addr (no) querier (no) query-int (no) v2-max-rsp-time (no) v3-max-rsp-time

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2137-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2137 — Configure a multicast VLAN

(no) (no) (no) (no) (no)

v3-max-num-rec drop-rpt-network robustness unsolicit-rpt-int retry-count

Note 1 — The IGMP version configured at the SHub must be the same as the network side IGMP version. Note 2 — The following applies for enabling or disabling snooping on the VLAN:

•

•

If snooping must be enabled, then the snooping filter must be disabled with the command configure igmp shub vlan-filter (filter-id) no snoop-filter If snooping must be disabled, then the snooping filter must be enabled with the command configure igmp shub vlan-filter (filter-id) snoop-filter

Note 3 — If snooping is enabled on the VLAN and the IGMP version needs to be changed, then snooping must first be disabled (see Note 2) before the IGMP version can be changed. After configuration of the IGMP version, snooping must be enabled again (see Note 2). ii

Configure the SHub response timer for a VLAN with the following command: configure igmp shub response-timer (vlan-id) (no) leave-rsp-timer

2

Configure the IGMP VLAN protocol parameters in IACM with the following command: configure igmp vlan (vlan-id) netw-igmp-version (no) v3-max-num-rec

Note — This step can be skipped if the default settings are OK.

3

Configure the router ports with the following command: configure igmp shub vlan-router-port (vlan-id) network-port nt:sfp: | nt:xfp: |

Note — IGMP Router ports are related to specific dual homing configurations for multicast. They are configured for each multicast VLAN. This step can be skipped if there is only a unique network port.

DLP 2137-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2137 — Configure a multicast VLAN

4

Configure a bundle with the following command: configure igmp shub bundle (bundle) (no) bandwidth (no) max-num-channel

Note — Bundles are related to uplink CAC. This step can be skipped if no uplink CAC is required.

5

Configure one or more packages with the following command: configure igmp package (index) (no) name (no) template-name (no) template-version

6

STOP. This procedure is complete.

Configuration example (Config#1): configure igmp shub vlan-filter 200 no snoop-filter configure igmp package 2 name Basic template-version 1 configure igmp package 3 name Sports template-version 1 configure igmp package 4 name Kids template-version 1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2137-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2137 — Configure a multicast VLAN

DLP 2137-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2138 — Configure a multicast channel Purpose This procedure provides the steps to configure a multicast channel. It is typically configured when the multicast channel offer is extended.

Prerequisites The following prerequisites must be fulfilled before a multicast channel can be configured:

• • •

The multicast service is configured ; see DLP 2136. The multicast VLAN is configured ; see DLP 2137. If the channel is statically provided over NNI subtending ports: • The corresponding Ethernet port must be an NNI port; see DLP 1255 • The corresponding IGMP channel must have been created and enabled; see DLP 2198

Procedure Proceed as follows to configure a multicast channel on IACM and SHub: 1

Configure the multicast channel in IACM with the following command: i

Configure the multicast channel with the following command: configure mcast chn (grp-ip-addr) src-ip-addr vlan-id (no) dis-fast-change (no) name (no) guaranteed-serv (no) peak-bit-rate

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2138-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2138 — Configure a multicast channel

(no) (no) (no) (no) (no) (no)

service-name preview-duration preview-number preview-blackout end-ip-addr mcast-svc-context

Note 1 — The parameter pkg-memb-bitmap is kept for backward compatibility with previous releases. Note 2 — The parameter mcast-svc-context should match the mcast-svc-context of a multicast channel for a join for the multicast channel on this multicast service to be processed as a configured multicast stream. If not, the join is processed as an unconfigured multicast stream for this service. Note 3 — The mcast-svc-context can be used only when the vlanSelection attribute in the IGMP system is not selected; see DLP 2136. Note 4 — The end-ip-addr and grp-ip-addr together define a range of multicast channels. By default, end-ip-addr takes a special value 0.0.0.0 denoting a single entry defined by grp-ip-addr. ii

Configure the multicast source package members with the following command: configure mcast chn (grp-ip-addr) src-ip-addr (no) packagemember (package)

2

If required, configure on-demand monitoring for loss of stream for a specified multicast stream with the following command: configure mcast monitor chn (grp-ip-addr) src-ip-addr vlan-id (no) loss-duration (no) loss-thresh-alert

Note — (no) loss-duration: set the duration to count packets; default=15. (no) loss-thresh-alert: set loss of traffic threshold, alert generated if packet count is less than or equal to the threshold; default=0.

DLP 2138-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2138 — Configure a multicast channel

3

Configure the multicast channel in SHub with the following command: configure mcast shub src (src) vlan-id ip-addr (no) eth-sus-bit-rate (no) guaranteed-serv (no) bundle

Note — Multicast channels in SHub are configured for uplink CAC. This step can be skipped if no uplink CAC is required.

4

5

Configure a static tree for the multicast channel: a

For SHub subtending ports or network ports, go to step 5

b

For NNI Ethernet ports, go to step 7

For SHub subtending ports or network ports, configure a static tree for the multicast channel with the following commands: i

Configure an entry in the IP multicast table for the SHub with the following command: configure mcast shub mcast-addr (mcast-addr) vlan-id

ii

Configure a static branch on SHub subtending ports or network ports with the following command: configure mcast shub mcast-addr (mcast-addr) vlan-id egress-port lt:// | network: | nt:sfp: | nt:xfp: | unassigned-link:

Note — This step can be skipped if the replication tree for this multicast channel is fully dynamically established.

6

Go to step 8

7

For NNI Ethernet ports, configure a static tree for the multicast channel with the following commands: i

Configure an entry in the IP multicast table for the SHub with the following command: configure mcast shub mcast-addr (mcast-addr) vlan-id

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2138-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2138 — Configure a multicast channel

ii

Configure a static branch on SHub LT port with the following command: configure mcast shub mcast-addr (mcast-addr) vlan-id egress-port lt://

Note — This substep can be skipped if there is already a branch for this multicast channel to another LT subtending port on the same LT.

iii

Configure a static branch on the LT NNI interface with the following command: configure mcast static branch (grp-ip-addr) src-ip-addr port

Note — This step can be skipped if the replication tree for this multicast channel is fully dynamically established.

8

DLP 2138-4

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2138 — Configure a multicast channel

Configuration example (Config#1): configure mcast chn 224.1.15.1 src-ip-addr 0.0.0.0 vlan-id 200 name CNN peak-bit-rate 3000 configure mcast chn 224.1.15.1 src-ip-addr 0.0.0.0 vlan-id 200 packagemember 2 configure mcast shub src 224.1.15.1 vlan-id 200 ip-addr 0.0.0.0 eth-sus-bit-rate 10000 guaranteed-serv configure mcast chn 224.1.15.2 src-ip-addr 0.0.0.0 vlan-id 200 name BBC1 peak-bit-rate 3000 configure mcast chn 224.1.15.2 src-ip-addr 0.0.0.0 vlan-id 200 packagemember 2 configure mcast shub src 224.1.15.2 vlan-id 200 ip-addr 0.0.0.0 eth-sus-bit-rate 10000 guaranteed-serv configure mcast chn 224.1.15.3 src-ip-addr 0.0.0.0 vlan-id 200 name Eurosport peak-bit-rate 3000 configure mcast chn 224.1.15.3 src-ip-addr 0.0.0.0 vlan-id 200 packagemember 3 configure mcast shub src 224.1.15.3 vlan-id 200 ip-addr 0.0.0.0 eth-sus-bit-rate 10000 configure mcast chn 224.1.15.1 src-ip-addr 10.1.1.1 vlan-id 300 name NewsChannelGroups end-ip-addr 224.1.15.30 mcast-svc-context name:OrangeTV configure mcast chn 224.1.15.1 src-ip-addr 10.2.2.2 vlan-id 400 name NewsChannelGroups end-ip-addr 224.1.15.30 mcast-svc-context name:YellowTV

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2138-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2138 — Configure a multicast channel

DLP 2138-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2139 — Configure DHCP relay agent in iBridge mode Purpose In the iBridge mode, the user subnets need to be configured on the user gateway interface of the SHub. This is needed to advertise the user subnet routes into the network via routing protocols and also to forward user IP packets in downstream direction to LTs (in the routing table of the Shub, direct subnet routes need to be created on the V-VLAN). DHCP Relay is configured per VLAN:

• • •

Enable/disable DHCP relay agent on the SHub. Enable/disable Option-82 insertion. Option-82 insertion is configurable irrespective of the DHCP relay agent status. The DHCP relay agent IP address (separate configuration parameter) is the IP address of one of the VRF IP interfaces.

This procedure provides the steps to configure the DHCP relay agent in iBridge mode.

Note — The scope of this procedure is for IPv4 only.

Prerequisite The following prerequisite must be fulfilled before DHCP relay agent can be configured on an iBridge VLAN:

•

The iBridge VLAN must have been created; see DLP 1120.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2139-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2139 — Configure DHCP relay agent in iBridge mode

Procedure Proceed as follows to configure the DHCP relay agent: 1

Create a VRF on the SHub with the following command: configure ip shub vrf (index) name slow-path-mode

2

Add DHCP Option-82 to the iBridge VLAN with the following command: configure vlan id (vlanid) dhcp-opt-82 circuit-id-dhcp remote-id-dhcp (no) dhcp-linerate

3

Add an IP address to the iBridge VLAN, and add the VLAN to the VRF with the following commands: i

Change the administrative status of the iBridge VLAN to down with the following command: configure interface shub vlan-id (vlan-id) admin-status down

ii

Add an IP address to the iBridge VLAN with the following command: configure interface shub ip (vlan-id) ip-addr / (no) local-arp-proxy

iii

Add the VLAN to the VRF with the following command: configure interface shub ip (vlan-id) vrf-id

iv

Change the administrative status of the iBridge VLAN to up with the following command: configure interface shub vlan-id (vlan-id) admin-status up

4

Enable the SHub relay agent with the following command: configure dhcp-relay shub relaying

5

Configure the list of DHCP relay server to a particular VRF with the following command: configure dhcp-relay shub instance (vrfid) server (ip-addr) server-name

DLP 2139-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2139 — Configure DHCP relay agent in iBridge mode

6

Configure the DHCP relay agent parameters to a particular VRF with the following command: configure dhcp-relay shub instance (vrfid) (no) relaying (no) secs-threshold (no) hops-threshold (no) agent-ip-addr

7

STOP. This procedure is complete.

Configuration example (Config#1): configure ip shub vrf 10 name ibridge-relay-vrf10 slow-path-mode configure vlan id 100 dhcp-opt-82 circuit-id-dhcp physical-id remote-id customer-id configure interface shub vlan-id 100 admin-status down configure interface shub ip 100 vrf-id 10 configure interface shub ip 100 ip-addr 192.168.100.2/24 configure interface shub vlan-id 100 admin-status up configure dhcp-relay shub relaying configure dhcp-relay shub instance 10 server 192.168.100.13 server-name DHCPRell0 configure dhcp-relay shub instance 10 relaying agent-ip-addr 192.168.100.2

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2139-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2139 — Configure DHCP relay agent in iBridge mode

DLP 2139-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2140 — Configure DHCP relay agent in router mode Purpose In the router mode, the user subnets need to be configured on the user-gateway interface of SHub. This is needed to advertise user subnet routes into network via routing protocols and also to forward user IP packets in downstream to LTs (in the routing table of SHub, direct subnet routes need to be created on the V-VLAN). DHCP Relay is configured per VLAN:

• • •

Enable/disable DHCP relay agent Enable/disable Option-82 insertion Option-82 insertion is configurable irrespective of the DHCP relay agent status. The DHCP relay agent IP address (separate configuration parameter) is the IP address of one of the VRF IP interfaces.

This procedure provides the steps to configure the DHCP relay agent.

Prerequisite The following prerequisite must be fulfilled before a DHCP Relay Agent in router mode can be configured:

•

a V-VLAN must have been created; see DLP 2116.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2140-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2140 — Configure DHCP relay agent in router mode

Procedure Proceed as follows to configure the DHCP relay agent: 1

Configure the DHCP relay agent per VRF interface with the following command: configure dhcp-relay agent (vrfid) bcast-vlan (no) option-82 (no) circuit-id (no) remote-id (no) client-hw-address (no) dhcp-linerate

2

Enable the SHub relay agent with the following command: configure dhcp-relay shub relaying

3

Configure the list of DHCP Relay Servers to a particular VRF with the following command: configure dhcp-relay shub instance (vrfid) server server-name

4

Configure the DHCP relay agent parameters to a particular VRF with the following command: configure dhcp-relay shub instance (vrfid) (no) relaying (no) secs-threshold (no) hops-threshold agent-ip-addr

5

STOP. This procedure is complete.

Configuration example (Config#1): configure dhcp-relay agent 5 bcast-vlan l2-vlan:4090 option-82 circuit-id physical-id remote-id customer-id configure dhcp-relay shub relaying configure dhcp-relay shub instance 15 server 10.178.14.66 server-name Antwerp15 configure dhcp-relay shub instance 15 relaying agent-ip-addr 10.178.14.97

DLP 2140-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2141 — Configure DHCP relay agent in forwarder mode Purpose The DHCP relay port functionality provided by LTs is exactly the same as in the router mode. One difference is that, in the forwarder mode, there is no need to have a dedicated V-VLAN to be used as a broadcast VLAN for DHCP relay. Instead, one of the network VLANs is used at the same time as a broadcast VLAN by LTs. DHCP Relay is configured per VLAN:

• • •

Enable/disable DHCP relay agent Enable/disable Option-82 insertion Option-82 insertion is configurable, irrespective of the DHCP relay agent status. The DHCP relay agent IP address (separate configuration parameter) is the IP address of one of the VRF IP interfaces.

This procedure provides the steps to configure the DHCP relay agent.

Procedure Proceed as follows to configure the DHCP relay agent: 1

Create a VRF on the SHub with the following command: configure ip shub vrf (index) name slow-path-mode

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2141-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2141 — Configure DHCP relay agent in forwarder mode

2

Add DHCP Option-82 to the forwarder VLAN on the LT with the following command: configure dhcp-relay agent (vrfid) bcast-vlan (no) option-82 (no) circuit-id (no) remote-id (no) client-hw-address (no) dhcp-linerate

3

Add an IP address to the forwarder VLAN, and add the VLAN to the VRF with the following commands: i

Change the administrative status of the VLAN to down with the following command: configure interface shub vlan-id (vlan-id) admin-status down

ii

Add an IP address to the VLAN with the following command: configure interface shub ip (vlan-id) ip-addr / (no) local-arp-proxy

iii

Add the VLAN to the VRF with the following command: configure interface shub ip (vlan-id) vrf-id

iv

Change the administrative status of the VLAN to up with the following command: configure interface shub vlan-id (vlan-id) admin-status up

4

Enable the SHub relay agent with the following command: configure dhcp-relay shub relaying

5

Configure the list of DHCP relay servers to the VRF with the following command: configure dhcp-relay shub instance (vrfid) server server-name

6

Configure the DHCP relay agent parameters to the VRF with the following command: configure dhcp-relay shub instance (vrfid) (no) relaying (no) secs-threshold (no) hops-threshold agent-ip-addr

7

DLP 2141-2

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2141 — Configure DHCP relay agent in forwarder mode

Configuration example (Config#1): configure ip shub vrf 17 name forw-relay-vrf17 slow-path-mode configure dhcp-relay agent 16 bcast-vlan l2-vlan:101 option-82 circuit-id physical-id remote-id customer-id configure interface shub vlan-id 101 admin-status down configure interface shub ip 101 vrf-id 17 configure interface shub ip 101 ip-addr 192.168.116.2/24 configure interface shub vlan-id 101 admin-status up configure dhcp-relay shub relaying configure dhcp-relay shub instance 17 server 192.168.116.13 server-name Antwerp17 configure dhcp-relay shub instance 17 relaying agent-ip-addr 192.168.116.2

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2141-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2141 — Configure DHCP relay agent in forwarder mode

DLP 2141-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2142 — Configure the system security domain Purpose This procedure provides the steps to configure the system security domain.

Prerequisites The following prerequisite must be fulfilled before the security domain can be configured:

• •

A forwarding VRF must have been created; see DLP 2122. RADIUS must have been configured; see DLP 2144.

Procedure Proceed as follows to configure the system security domain: 1

Configure the system security domain with the following command: configure system security domain (name) vrf-index (no) vlan-id (no) primary-dns (no) second-dns (no) primary-nbns (no) second-nbns (no) sess-timeout (no) qos-policy none | name: authenticator local | radius: (no) admin-down

2

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2142-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2142 — Configure the system security domain

Configuration example (Config#1): configure system security domain Domain1 vrf-index 16 vlan-id 200 authenticator local

DLP 2142-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2144 — Configure RADIUS Purpose This procedure provides the steps to configure the Remote Authentication Dial-In User Service (RADIUS).

Procedure Proceed as follows to configure RADIUS: 1

Configure the RADIUS authentication server with the following command: configure system security radius auth-server (name) vrf-index ip-address (no) port secret (no) retry-limit (no) timeout-limit (no) admin-down (no) dead-interval

2

Configure the RADIUS accounting server with the following command: configure system security radius acc-server (name) vrf-index ip-address (no) port secret (no) retry-limit (no) timeout-limit (no) admin-down (no) dead-interval

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2144-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2144 — Configure RADIUS

3

Configure the RADIUS policy with the following command: configure system security radius policy (name) nas-id nas-ip-address (no) keep-domain-name (no) disable-accnt-msg (no) acc-interval (no) disable-eap

4

Configure the RADIUS server set with the following command: configure system security radius policy (name) servers (index) auth-server vrf-index-auth (no) acc-server (no) vrf-index-acc priority

5

Enable the RADIUS relay on the SHub with the following command: configure system security radius (no) relay (no) auth-super-user (no) oper-policy-name (no) aut-s-unreach-act

6

Configure the security domain with the following command: configure system security domain (name) vrf-index (no) vlan-id (no) primary-dns (no) second-dns (no) primary-nbns (no) second-nbns (no) sess-timeout (no) qos-policy none | name: authenticator radius: (no) admin-down

7

Configure the RADIUS Dynamic Authorization Clients with the following command: configure system security radius dyn-auth-client (name) vrf-index ip-address secret (no) admin-down

8

DLP 2144-2

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2144 — Configure RADIUS

Configuration example (Config#1): configure ip vrf 1 name Dummy configure system security radius auth-server RADAuthServ1 vrf-index 0 ip-address 10.176.5.5 secret Khinghkhongh timeout-limit 5 configure system security radius acc-server RADAccServ1 vrf-index 0 ip-address 10.176.5.55 secret Ahlakazam configure system security radius policy RADPol23 nas-id MyNASID nas-ip-address 192.168.122.122 configure system security radius policy RADPol23 servers 2 auth-server name:RADAuthServ1 vrf-index-auth 0 acc-server name:RADAccServ1 vrf-index-acc 0 priority 162 configure system security domain SecDomain1 vrf-index 1 authenticator radius:RADPol23 configure system security radius dyn-auth-client DynAuth1 vrf-index 0 ip-address 10.176.5.5 secret Khinghkhongh

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2144-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2144 — Configure RADIUS

DLP 2144-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2150 — Configure ARP table entry Purpose This procedure provides the steps to configure an ARP table entry.

Prerequisite The following prerequisite must be fulfilled before an ARP table entry can be configured:

•

A VLAN must have been created; see DLP 1117, DLP 1118, DLP 1119 or DLP 1120.

Procedure Use the following procedure to configure an ARP table entry: 1

Configure the IP Shub ARP parameters per VLAN with the following command: configure ip shub arp vlan (vlanid) (no) gratuitous-arp

2

STOP. This procedure is complete.

Configuration example (Config#1): configure ip shub arp vlan 4093 gratuitous-arp

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2150-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2150 — Configure ARP table entry

DLP 2150-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2154 — Create a snapshot alarm table Purpose This procedure provides the steps to create a snapshot alarm table.

General In the NE, a lot of different alarms may occur. This can sometimes make it difficult for an operator to investigate, since alarms can appear, disappear, and so on. Therefore, the snapshot principle exists. A snapshot is in fact a picture of all the alarms that are present on the moment the snapshot is taken. A table is created which contains a copy of the alarms which are present in the system at the time the snapshot was taken. The operator can filter this table by specifying a “minimum alarm level”. Only alarms with a level equal to or higher than the specified level, will be present in the table. This table is only temporary and exists only for four minutes. After the four minutes, the table is cleared automatically (the alarms are not displayed anymore), and a new snapshot can be taken. The operator can also clear the table manually if he wants to take a new snapshot immediately (that is, not wait for the 4 minute timer to expire).

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2154-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2154 — Create a snapshot alarm table

Procedure Proceed as follows to create a snapshot alarm table: 1

Create an alarm snapshot table for a minimum severity level with the following command: admin alarm snap-shot start:indeterminate: | start:warning: | start:minor: | start:major: | start:critical: | start::

Note — The command will fail if the snap-shot is already in use. The snap-shot is only kept for a limited time and will be automatically cleared. 2

The alarm snapshot table can be viewed with the following command: show alarm snap-shot {table | equipment | eqpt-holder | ept-holder-ext | plug-in-unit | atm | ether-itf | sw-mgmt | xdsl | xdsl-tca | eo-conversion | authentication | bonding-group | redundancy | custom | sfp | llu-relay | custom-ext-alarm | plug-in-unit-ext | psc | sip-user-agent | sip-plugin-unit | sip-termination | megaco-media-gw | megaco-sig-gw | megaco-term | megaco-sig-lt | shdsl | shdsl-isam | ima-group | ima-link | ether-tca | ether-sfp | qos-slot | qos-queue | filetransfer | lsmredundancy | l2forward | external-device | sync | vect-line | vect-board} (index)

Note 1 — The command can be given with or without extra parameters:

• •

When NO parameter is given, all the alarms will be shown. More detailed information can be displayed by specifying the type of alarm.

Note 2 — The values ldp, mpls, sdp and epipe are not supported. 3

Create an alarm snapshot table on the SHub with the following command: admin alarm shub snap-shot start:indeterminate: | start:warning: | start:minor: | start:major: | start:critical: | start::

DLP 2154-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2154 — Create a snapshot alarm table

4

The SHub alarm snapshot table can be viewed with the following command: show alarm shub snap-shot {table | shub-gen | eth-shub | rip | ospf | uplink-group | forwarding | global-rip | global-ospf | global-fwd} (index)

Note — The command can be given with or without extra parameters:

• • 5

When NO parameter is given, all the tables will be shown. More detailed information can be displayed by specifying the type of alarm.

The alarm snapshot table can be cleared with the following command: admin alarm snap-shot stop

Note — The alarms are not shown anymore and a new snapshot can now be taken, if required.

6

The alarm snapshot table on the SHub can be cleared with the following command: admin alarm shub snap-shot stop

Note — The alarms are not shown anymore and a new snapshot can now be taken, if required.

7

STOP. This procedure is complete.

Configuration example (Config#1): The following command creates an alarm snapshot table for snap-shot owner "tom" showing all the alarms with severity-level "major" and higher. admin alarm snap-shot start:major:tom The following command displays the complete alarm table. show alarm snap-shot table The following command displays more information for the alarm type "equipment". show alarm snap-shot equipment The following command creates an alarm snapshot table on the SHub for snap-shot owner "tomtom" showing all the alarms with severity-level "indeterminate" and higher. admin alarm shub snap-shot start:indeterminate:tomtom The following command displays the complete alarm table for the Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2154-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2154 — Create a snapshot alarm table

SHub. show alarm shub snap-shot table The following command displays more information for the alarm type "eth-shub" on the SHub. show alarm shub snap-shot eth-shub The following command clears the alarm snap shot. admin alarm snap-shot stop The following command clears the alarm snap shot on the SHub. admin alarm shub snap-shot stop

DLP 2154-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2155 — Monitor alarms Purpose This procedure provides the steps to monitor alarms. Monitoring alarms includes viewing current alarms, a snapshot of the NE alarms, and the current configuration of the alarm delta logs.

General Refer to the CLI Command Guide for FD 24Gbps NT document for a full description of all the commands related to alarm monitoring. The most common commands are listed in the procedure below.

Procedure Proceed as follows to monitor alarms: 1

Use the following commands to show the alarm log tables: i

View the general alarm log table with the following command: show alarm log table

ii

View a specific alarm log table with the following command: show alarm log {table | equipment | eqpt-holder | ept-holder-ext | plug-in-unit | atm | ether-itf | sw-mgmt | xdsl misc | xdsl near-end | xdsl far-end | xdsl-tca | eo-conversion | authentication | bonding-group | redundancy | custom | sfp | llu-relay | custom-ext-alarm | plug-in-unit-ext | psc | sip-user-agent | sip-plugin-unit | sip-termination | megaco-media-gw | megaco-sig-gw | megaco-term | megaco-sig-lt | shdsl | shdsl-isam | ima-group | ima-link | ether-tca | ether-sfp | qos-slot | qos-queue | filetransfer | lsmredundancy | l2forward | external-device | sync | vect-line | vect-board} (index)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2155-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2155 — Monitor alarms

Note — The values ldp, mpls, sdp and epipe are not supported.

2

Use the following command to view the common values related to the alarm delta logs: show alarm delta-log alarm-changes

3

Use the following commands to view the current alarms: i

View all the current alarms with the following command: show alarm current table

ii

View the current status of a specific alarm with the following command: show alarm current {table | equipment | eqpt-holder | ept-holder-ext | plug-in-unit | atm | ether-itf | sw-mgmt | xdsl | xdsl-tca | eo-conversion | authentication | bonding-group | redundancy | custom | sfp | llu-relay | custom-ext-alarm | plug-in-unit-ext | psc | sip-plugin-unit | sip-termination | shdsl | shdsl-isam | ima-group | ima-link | ether-tca | ether-sfp | qos-slot | qos-queue | filetransfer | lsmredundancy | l2forward | external-device | mcsrc | vlanport | bgp | rip | lag | ihub-general | vprn | isis | ospf | ihub-l2forward | vpls | ihub-equip | ihub-link | ldp | mpls | sdp | epipe | sync | eqpt-supplemental | vect-line | vect-board} (index)

Note 1 — The “detail” mode can be used to obtain more detailed information on the alarm. Note 2 — The values ldp, mpls, sdp and epipe are not supported. 4

To view values related to the alarm delta log entries, use any of the following commands: a

To display common values related to the delta log alarm, use the following command: show alarm delta-log alarm-changes

b

To display indeterminate values related to the delta log alarm, use the following command: show alarm delta-log indeterminate (index)

c

To display warning values related to the delta log alarm, use the following command: show alarm delta-log warning (index)

d

To display minor values related to the delta log alarm, use the following command: show alarm delta-log minor (index)

DLP 2155-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2155 — Monitor alarms

e

To display major values related to the delta log alarm, use the following command: show alarm delta-log major (index)

f

To display critical values related to the delta log alarm, use the following command: show alarm delta-log critical (index)

5

STOP. This procedure is complete.

Configuration example (Config#1): show alarm log table show alarm log equipment 1 show alarm log xdsl misc show alarm delta-log alarm-changes show alarm current table show alarm delta-log alarm-changes show alarm delta-log indeterminate show alarm delta-log warning show alarm delta-log minor show alarm delta-log major show alarm delta-log critical

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2155-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2155 — Monitor alarms

DLP 2155-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2157 — Manage the SHub database Purpose This document provides the steps to save the SHub configuration database.

Caution — The SHub database is part of the NT database. The system automatically saves the SHub database every 10 minutes. If a change is made to the SHub database and the system is reset prior to the database being saved, the changes can be lost. The operator can check if the database has been saved since the last change with the following command: show system shub entry status

Procedure Proceed as follows to manage the SHub database: 1

Save the SHub database with the following command: admin software-mngt shub database save

2

The status of the save operation (successful, failed, or still in progress) can be viewed with the following command: show software-mngt shub config-file

3

STOP. This procedure is complete.

Configuration example (Config#1): show software-mngt shub config-file show system shub entry status

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2157-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2157 — Manage the SHub database

DLP 2157-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2160 — View version of the SHub software Purpose This procedure provides the steps to view the software version number for the SHub.

Procedure Proceed as follows to view the software version number for the SHub: 1

View the software version of the SHub system parameters with the following command: show system shub entry version

2

STOP. This procedure is complete.

Configuration example (Config#1): show system shub entry version

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2160-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2160 — View version of the SHub software

DLP 2160-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2162 — Modify the external management VLAN Purpose This procedure gives the steps to change the external management VLAN.

Procedure Proceed as follows to change the external management VLAN: 1

If required, you can view the current configuration as follows: i

View the external VLAN in the system with the following command: info configure system

ii

View the external VLAN in the SHub with the following command: info configure system shub entry vlan

iii

View the PVID on the management port with the following command: info configure bridge shub port 1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2162-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2162 — Modify the external management VLAN

2

Change the external VLAN in the system with the following command: configure system id name location contact-person (no) en-snmp-auth-traps (no) ether-shape-rate mgnt-vlan-id system-mac // (no) port-num-inpro

Note — It is not possible to change the system MAC address or the SHub MAC range when a SMAS board is available in the system.

3

Change the external VLAN in the SHub with the following command: configure system shub entry vlan ext-vlan-id

Note — When operating in single IP mode: This command only serves to save the VLAN ID in protected data. 4

Configure the network port as egress port with the following command: configure vlan shub id (vlanid) egress-port (port)

5

If the management traffic is untagged, do the following: i

Configure the untagged port and the PVID with the following commands: configure vlan shub id (vlanid) untag-port (port)

ii

Change the PVID on the management port with the following command: configure bridge shub port (port) pvid

6

Save the SHub database with the following command: admin software-mngt shub database save

7

DLP 2162-2

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2162 — Modify the external management VLAN

Configuration example (Config#1): info configure system info configure system shub entry vlan info configure bridge shub port 7 configure system mgnt-vlan-id 72 configure system shub entry vlan ext-vlan-id 72 configure vlan shub id 72 egress-port network:7 configure bridge shub port 7 pvid 72 admin software-mngt shub database save

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2162-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2162 — Modify the external management VLAN

DLP 2162-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2164 — Ping another host Purpose This procedure provides the steps to ping another host.

Procedure Proceed as follows: 1

Ping another host with the following command: ping (no) (no) (no)

2

Ping another host in a given VRF (from the SHub) with the following command: ping (no) (no) (no)

3

(ip-addr) timeout tries mtu-size

(ip-addr) vrf (vrf) timeout tries mtu-size

The pending ping session can be aborted with the following command: admin ping (ip-addr) abort-session

4

STOP. This procedure is complete.

Configuration example (Config#1): ping 10.176.5.5 tries 3 ping 192.168.116.1 vrf 15 tries 3

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2164-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2164 — Ping another host

DLP 2164-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2165 — Perform a traceroute action Purpose This procedure provides the steps to perform a traceroute action, aiming at determining the route to a destination address.

Note — The following applies for traceroute actions:

• •

Only one traceroute can be ongoing at any point in time A traceroute action must be explicitly terminated before a new traceroute action can be initiated.

Procedure Proceed as follows to perform a traceroute action: 1

For a traceroute action: i

Initiate the traceroute action with the following command: traceroute (ip-addr) first-hop last-hop (no) timeout (no) mtu-size

ii

Terminate the traceroute action with the following command: traceroute (ip-addr) no first-hop

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2165-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2165 — Perform a traceroute action

2

For a traceroute action in a given VRF (from the SHub): i

Initiate the traceroute action with the following command: traceroute (ip-addr) vrf (vrf) first-hop last-hop (no) timeout (no) mtu-size

ii

Terminate the traceroute action with the following command: traceroute (ip-addr) vrf (vrf) no first-hop

3

The pending tracroute session can be aborted with the following command: admin traceroute (ip-addr) abort-session

4

STOP. This procedure is complete.

Configuration example (Config#1): traceroute 10.176.5.5 first-hop 2 last-hop 4 mtu-size 30 traceroute 10.177.5.5 vrf 15 first-hop 2 last-hop 4 mtu-size 30

DLP 2165-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2166 — Configure SNMP proxy CPE management Purpose This procedure provides the steps to configure the CPE management functionality. The configuration of the remote SNMP proxy CPE management functionality involves:

• •

Enabling the CPE remote management function Configuring the IP address of the CPE remote manager

Note — Up to 5 managers can be configured.

•

Configuring the UDP trap port of the CPE remote manager

Procedure Proceed as follows: 1

Configure the CPE remote management function with the following command: configure cpe-management proxy-mode snmp (no) vlan-id

2

Configure the CPE manager with the following command: configure cpe-management (no) manager :

3

Configure a management session to a CPE with the following command: configure cpe-management (no) session (dslport) (no) connection

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2166-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2166 — Configure SNMP proxy CPE management

4

Configure on the SHub the VLAN that will be used to transport IP packets for a CPE management session inside the system with the following command: configure cpe-management shub vlan-id (vlan-id)

5

View the global statistics and the statistics per CPE manager with the following command: show cpe-management snmpproxy-statistics

6

STOP. This procedure is complete.

Configuration example (Config#1): configure cpe-management proxy-mode snmp vlan-id 400 configure cpe-management manager 192.168.200.200:2000 configure cpe-management shub vlan-id 400 show cpe-management snmpproxy-statistics

DLP 2166-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2167 — Script files Purpose A script file is a file containing CLI commands. CLI scripts can be executed when they are stored on the flash-disk. Script files are typically stored in the /var/cmd directory.

Warning — The /var/cmd is cleaned when the system resets, so the configuration file must be transferred to another system with TFTP before resetting the system. Note 1 — Saving the configuration will not work for areas in which resource identifiers are assigned dynamically by the system. Note 2 — There is a built in file size restriction of 400 KB for the output generated by the tee command. There is also a restriction of approximately 750 Kb on the overall size of the directory where the output generated by the tee command is stored. In certain cases, these restriction will prevent the full info configure output from being stored in a file in the /var/cmd directory. It is recommended that the operator store individual info configure sub-domains in this file. A list of available sub-domains is provided in the section below.

Sub-domains The following sub-domains are available:

• • • • • •

alarm trap equipment xdsl atm interface

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2167-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2167 — Script files

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

DLP 2167-2

error system software-mngt pccp transport qos vlan bridge la mstp ip arp-relay igmp mcast pppox-relay pppoe dhcp-relay ospf rip cluster xdsl-bonding cpe-management shdsl ima l2cp voice debug ethernet efm-oam cfm trouble-shooting ipoa/e-iw

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2167 — Script files

Procedure Proceed as follows to create a file containing the CLI configuration output for a given sub-domain and to make use of a CLI configuration file for playback: 1

The complete configuration of the system can be stored in a script with the following command: info configure flat | tee | discard info configure flat | tee append | discard

Note — You can append as many sub-domains as required as long as you do not exceed the maximum file size of file.txt (400 KB).

2

You can do one of the following: a

Retrieve the configuration file from the ISAM (via TFTP) using the following commands: $ tftp tftp> bin tftp> get /var/cmd/

b

Place a configuration file with a list of CLI commands on the ISAM for playback (via TFTP) using the following commands: $ tftp tftp> bin tftp> put /var/cmd/

c

Restore the configuration file on an empty system with the following command: exec /var/cmd/

3

STOP. This procedure is complete.

Configuration example (Config#1): info configure | tee config info configure alarm flat | tee alaflat.cli exec /var/cmd/alaflat.cli

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2167-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2167 — Script files

DLP 2167-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2168 — Modify the system management IP parameters Purpose This document describes the procedure to modify the system management IP parameters.

Procedure Proceed as follows to modify the system management IP parameters: 1

If a default route was defined at the time of creation, remove the default route with the following command: configure system management no default-route

2

Assign a system IP address. Use one of the following commands: a

If a DHCP server is used to assign an IP address, configure the system IP address allocation to “dynamic” with the following command: configure system management host-ip-address bootp

b

If a system IP address will be assigned manually, use the following command: configure system management host-ip-address manual:/

3

Configure the new default route of the system with the following command: configure system management default-route

4

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2168-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2168 — Modify the system management IP parameters

Configuration example (Config#1): configure system management no default-route configure system management host-ip-address manual:192.168.204.147/24 configure system management default-route 192.168.204.254

DLP 2168-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2169 — Configure cluster management Purpose Cluster management in the NE is implemented as follows:

• •

•

•

•

•

Each node of a cluster still keeps its public IP address. The EMS manages each node independently via its public IP address, but offers the possibility to the operator to define “clusters” at the EMS Graphical User Interface (GUI) level, and give commands which are valid for the complete “cluster” (profile management, backup and restore, software management, alarm management). EMS then executes the commands sequentially to each DSLAM of the cluster. The EMS supports topology display, which is made possible by a topology collection process in the NE. For this topology collection, the NE supports the “neighbor-discovery” and “topology-collection” protocols as defined in the CCSA cluster management standard. The EMS defines a command and a backup node for each cluster. Both the command and the backup node will perform topology collection for the cluster. EMS retrieves the collected cluster topology from the command node. If the command node fails, EMS retrieves topology information from the backup node. The neighbor-discovery protocol is supported in each node of the cluster. It sends neighbor-discovery packets (with information of its own node) on each of its up- and subtending links in a regular time-interval (default 60s). Through these packets, each NE learns its directly connected environment. A topology-collection protocol is started from the command node. Topology collection can be done automatically and periodically by the NE (in this case, the EMS is trapped by the NE if the topology is changed), or the operator on the EMS can start a manual topology collection request. The NE sends topology request messages on all the links to its neighbours learned through neighbor discovery. Each neighbor answers with a topology reply containing info on its directly connected

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2169-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2169 — Configure cluster management

•

environment. Each neighbor also forwards the original topology request on its other links, and the second-level neighbours will answer with topology response messages directly to the command node using the command node’s MAC address. With the information received in the topology response messages, the command and backup nodes are able to construct tables giving the complete topology of a cluster (including the MAC and IP address of each node).

This procedure provides the steps to configure cluster management.

Procedure Proceed as follows to configure cluster management: 1

Configure the role of the NE and cluster name with the following command: configure cluster system name role

Note — Use this command for each NE that must be part of the cluster.

2

Configure the neighbour discovery on system level with the following command: configure cluster neighbour (no) discov-mode-off (no) interval (no) hold-time

Note — By default, the automatic neighbour discovery mode is enabled.

3

Configure the topology collection on system level with the following command: configure cluster collection (no) collect-sys-off (no) hop-delay (no) port-delay (no) scope (no) interval (no) manual

Note — By default, the automatic topology-collection mode is enabled.

DLP 2169-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2169 — Configure cluster management

4

Configure the neighbour discovery and topology collection on port level with the following command: configure cluster port nt:sfp: | nt:xfp: | (no) discov-port-off (no) collect-port-off

Note — By default, the automatic neighbour-discovery and topology-collection modes are enabled on port level.

5

View the status of the cluster with the folliwng commands: show cluster counter show cluster neighbour show cluster device show cluster connect

6

STOP. This procedure is complete.

Configuration example (Config#1): configure cluster system name cluster1 role command configure cluster neighbour no discov-mode-off interval 60 hold-time 180 configure cluster collection interval 3000 configure cluster port 1 discov-port-off show cluster counter show cluster neighbour show cluster device show cluster connect

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2169-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2169 — Configure cluster management

DLP 2169-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2171 — Enable EMS management Purpose This procedure provides the steps to enable the management of EMS:

• •

via SNMPv3 via SNMPv1

Note — It is NOT advised to use insecure remote management channels SNMPv1/2. If SNMPv1/2 is used anyway, it is advised not to use community string = public.

Procedure Proceed as follows to enable the management of EMS: 1

2

Do one of the following: a

To enable EMS management via SNMPv3, go to step 2

b

To enable EMS management via SNMPv1, go to step 4

Enable EMS management via SNMPv3 as follows: a

Configure an SNMPv3 user with the following command: configure system security snmp user (name) (no) authentication none | [md5|sha1]:prompt | [md5|sha1]:plain: | [md5|sha1]:encrypted: (no) privacy none | des:prompt | des:plain: | des : encrypted : (no) public

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2171-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2171 — Enable EMS management

b

Configure an SNMPv3 group with the following command: configure system security snmp group (name) security-level context single:nt | single:shub | single:epon | all (no) read-view (no) write-view (no) notify-view

c

Map an SNMPv3 user to an SNMPv3 group with the following command: configure system security snmp map-user-group (name) group-name

3

Go to step 5.

4

Enable EMS management via SNMPv1 as follows: a

Configure the SNMP community name “public” with the following command: configure system security snmp community public host-address /

b

Configure the SNMP community name “NETMAN” with the following command: configure system security snmp community NETMAN host-address / context shub

5

STOP. This procedure is complete.

Configuration example: Configuration example for management via SNMPv3 for single IP address mode (Config#1): configure system security snmp user ftbhuser authentication sha1:plain:myPass privacy des:plain:myPass configure system security snmp group ftbhgroup security-level privacy-and-auth context all configure system security snmp map-user-group ftbhuser group-name ftbhgroup Configuration example for management via SNMPv1 for single IP address mode (Config#1): configure system security snmp community public host-address 10.176.0.0/15 configure system security snmp community NETMAN host-address 10.176.0.0/15 context shub

DLP 2171-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2172 — Create a default operator profile Purpose This command allows the superuser to specify a default operator profile. This default profile is used when an operator is authenticated via a RADIUS server, but the RADIUS server does not support Vendor Specific Attributes. This operator profile determines most of the operator properties.

Procedure Proceed as follows to create a default operator profile: 1

Create a default operator profile with the following command: configure system security default-profile (name) (no) prompt (no) password-timeout (no) terminal-timeout (no) slot-numbering (no) description (no) aaa (no) atm (no) alarm (no) dhcp (no) equipment (no) igmp (no) ip (no) ppoe (no) qos (no) software-mngt

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2172-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2172 — Create a default operator profile

(no) (no) (no) (no) ...

transport vlan xdsl security

Note — Only the main parameters are shown, other parameters can also be modified. For more information, see the CLI Command Guide for FD 24Gbps NT. 2

STOP. This procedure is complete.

Configuration example (Config#1): configure system security default-profile no prompt password-timeout 10 terminal-timeout 30 description defaultprof aaa read atm read alarm write no dhcp equipment write no igmp ip write pppoe write qos write software-mngt write transport write vlan write xdsl write security write

DLP 2172-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2175 — Configure system management IP parameters Purpose This document describes the procedure to configure the system management IP parameters.

Procedure Proceed as follows to configure the system management IP parameters: 1

Configure the system ID parameters with the following command: configure system id name location (no) access-oper-id contact-person (no) en-snmp-auth-trap (no) ether-shape-rate mgnt-vlan-id system-mac (no) port-num-in-proto

Note 1 — The numbering scheme for the line ID format is configured with the parameter port-num-in-proto. For a more detailed explanation on the different numbering schemes, see TNG 1115. Note 2 — The system MAC address must only be configured when the system has no System MAC Address Storage (SMAS) functionality (that is, when no SMAS board or GFC board are present in the system).

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2175-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2175 — Configure system management IP parameters

2

The system can receive an IP address either statically by manual configuration or dynamically via BOOTP. Configure the host IP address of the system with the following command: configure system management host-ip-address bootp | manual:/

Note 1 — In case of manual configuration of the IP address: If the system IP address is not configured (default 0.0.0.0), the user’s session setup requests are refused. Note 2 — In case of dynamic configuration via BOOTP: you can view the IP address that you received from the server with the following command: show transport ip-address

3

Configure the default route of the system with the following command: configure system management default-route (default-route)

4

Configure the network port management (inband or outband) with the following command: configure interface shub port (network-port) (no) mode (no) port-type (no) mc-flooding where port-type can be: user: port to a directly connected user subtending: port to a subtended ISAM network: port to the service provider (ISP) unused: port is not in use outband-mngt: port is used for outband-management Select network for inband management or outband-mngt for outband management Inband or outband management can be checked with the following commands (output of the commands is an example):

show vlan global ---------------------------------------------------------------vlan parameters ---------------------------------------------------------------configured-vlans : 16 management : inband max-rb-vlan : 128 max-layer2-term-vlan : 1280 ===============================================================

show interface shub port ================================================================ port table ================================================================ port admin-status oper-status speed type duplex

DLP 2175-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2175 — Configure system management IP parameters

---------------------------------------------------------------1 down down one-gb unused full 2

up

up

one-gb

outband

full

3

up

down

one-gb

user

full

4

up

down

one-gb

subtending

full

5

up

down

one-gb

network

full

6

up

up

hundred-mbps

network

full

7

up

up

hundred-mbps

network

half

----------------------------------------------------------------

5

Specify the set of ports which are statically allocated as egress ports for the SHub management VLAN with the following command: configure vlan shub id 4093 egress-port (port)

6

Specify the egress ports which should transmit packets for the SHub management VLAN as untagged with the following command: configure vlan shub id 4093 untag-port (port)

7

Configure the bridge port with the following command: configure bridge shub port (port) pvid 4093

8

STOP. This procedure is complete.

Configuration example: Configuration example for dynamic configuration via BOOTP (for tagged network) (Config#1): configure system id SystemID01 configure system management host-ip-address bootp show transport ip-address configure system management no default-route configure interface shub port 7 port-type network show vlan global show interface shub port configure vlan shub id 4093 egress-port network:7 configure bridge shub port 7 pvid 4093

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2175-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2175 — Configure system management IP parameters

Configuration example for static configuration via manual configuration (for tagged network) (Config#1): configure system id SystemID02 configure system management host-ip-address manual:10.177.0.112/17 show transport ip-address configure system management default-route 10.177.127.254 configure interface shub port 7 port-type network show vlan global show interface shub port configure vlan shub id 4093 egress-port network:7 configure bridge shub port 7 pvid 4093

DLP 2175-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2176 — Performance monitoring commands Purpose This procedure provides the commands for performance monitoring on the NE.

Note 1 — For more information on the command syntax and the command parameters, refer to the CLI Command Guide for FD 24Gbps NT. Note 2 — On the SHub, the available memory for counters is 32 kbit.

Procedure The following steps can be used for performance monitoring: 1

Use the following commands to show the xDSL counters: show xdsl counters near-end line current-interval (if-index) detail show xdsl counters far-end line current-interval (if-index) detail show xdsl counters near-end line current-1day (if-index) detail show xdsl counters far-end line current-1day (if-index) detail show xdsl counters near-end line previous-interval (if-index) detail show xdsl counters far-end line previous-interval (if-index) detail show xdsl counters near-end line previous-1day (if-index) detail

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2176-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2176 — Performance monitoring commands

show xdsl counters far-end line previous-1day (if-index) detail

Note 1 — The previous-1day counters are not available until 96 15-min intervals (that is, 24 hours) have passed. Note 2 — For Layer2 LT boards only 32 15-min intervals are available. 2

Use the following commands to show the ATM counters: show atm tc-current-int one-day (port) show atm tc-current-int fifteen-min (port)

3

Use the following commands to show the link aggregation counters: show la aggregator-info (network-port) show la aggregate-list (network-port) show la network-port-info

4

Use the following command to show the MSTP counters: show mstp bridge show mstp instance show mstp network-port show mstp port-instance

5

Use the following command to show the SHub port statistics: show bridge network-port (port)

6

Use the following command to show the QoS statistics: show qos statistics buffer-overflow prev-15min (equip-slot) show qos statistics buffer-overflow current-15min (equip-slot) show qos statistics buffer-overflow prev-1day (equip-slot) show qos statistics buffer-overflow current-1day (equip-slot) show qos statistics buffer-overflow total show qos statistics queue prev-15min (index) show qos statistics queue current-15min (index) show qos statistics ltcos prev-15min (equip-slot) show qos statistics ltcos current-15min (equip-slot) show qos statistics ltcos pre-1day (equip-slot) show qos statistics ltcos current-1day (equip-slot)

DLP 2176-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2176 — Performance monitoring commands

7

Use the following commands to show the IGMP statistics: show igmp channel counter (port) show igmp channel miscellaneous (port) show igmp channel protocol (port) show igmp module-mcast-channel (slot) grp-ip-addr src-ip-addr show igmp module counter (slot-index) show igmp shub igs-stats (vlan-id) show igmp shub system-stats show igmp shub mcast-stats (src) show igmp shub bundle-stats (bundle-name) show igmp shub bundle-stats (bundle-name)

8

Use the following command to show the IP forwarding statistics: show ip vrf-statistics (vrf-id)

9

Use the following command to show the VRF net-to-media statistics: show ip vrf-media (slot:vrf) [ip-address ]

10

Use the following command to show the IP SHub ARP Statistics per VRF forwarding statistics: show ip shub arp-stats (vrf-id)

11

Use the following commands to view the IP user port ARP proxy statistics: a

For user ports configured for Untagged frames, view the ARP counters with the following command: show ip arp-proxy-stats (port-interface) untagged-ip

b

For user ports configured for Tagged frames, view the ARP counters with the following command: show ip arp-proxy-stats (port-interface) vlan (subscr-vlan)

Note — By default, only ARP summary error counters are shown for each of the user ports. If detailed counters are required for monitoring or trouble shooting purposes, they need to be explicitly enabled by the operator for the particular user port, see TNG 2109. 12

Use the following command to show the statistics related to ARP relay: show arp-relay-stats (user-port) [vlan-id]

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2176-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2176 — Performance monitoring commands

13

Use the following command to show SHub DHCP relay agent statistics per VRF forwarding instance: show dhcp-relay shub vrf-agent-stats (vrf)

14

Use the following commands to view the DHCP relay user port statistics: a

For user ports configured for Untagged frames, view the DHCP counters with the following command: show dhcp-relay port-stats (port-interface) untagged-ip

b

For user ports configured for Tagged frames, view the DHCP counters with the following command: show dhcp-relay port-stats (port-interface) vlan (subscr-vlan)

Note — By default, only DHCP summary error counters are shown for each of the user ports. If detailed counters are required for monitoring or trouble shooting purposes, they need to be explicitly enabled by the operator for the particular user port, see TNG 2109. 15

Use the following commands to show the PPPoX relay statistics: show pppox-relay cross-connect statistics engine (vlan-id) show pppox-relay cross-connect statistics client-port (client-port) show pppox-relay cross-connect monitor-statistics engine (vlan-id) show pppox-relay cross-connect monitor-statistics client-port (client-port) show pppox-relay cross-connect session client-port (client-port)

16

Use the following commands to show the RADIUS statistics: show security radius auth-server auth-stats (name) vrf-index show security radius acc-server acc-stats (name) vrf-index

17

Use the following command to show the EAPOL statistics: show security pae eapol-stats (port)

18

Use the following command to show the statistics related to the SNMP protocol: show transport snmp protocol-stats

19

Use the following command to show the MAU statistics: show transport ether-ifmau (if-index) index

DLP 2176-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2176 — Performance monitoring commands

20

Use the following command to show the SHub L2 information: show transport shub mac (index-num)

21

Use the following commands to show the IMA information: show ima group state (if-index) show ima group counters near-end current-interval (if-index) show ima group counters near-end previous-interval (if-index) interval-no show ima group counters far-end current-interval (if-index) show ima group counters far-end previous-interval (if-index) interval-no show ima link state (if-index) show ima link counters near-end current-interval (if-index) show ima link counters near-end previous-interval (if-index) interval-no show ima link counters far-end current-interval (if-index) show ima link counters far-end previous-interval (if-index) interval-no

22

Use the following commands to show the SHDSL information: show shdsl inventory (if-index) unit-id show shdsl span-status (if-index) show shdsl unit-status (if-index) unit-id show shdsl segment-status (if-index) unit-id side wire-pair show shdsl segment-counters current-15min (if-index) unit-id side wire-pair show shdsl segment-counters current-1day (if-index) unit-id side wire-pair show shdsl segment-counters previous-15min (if-index) unit-id side wire-pair int-no

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2176-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2176 — Performance monitoring commands

show shdsl segment-counters previous-1day (if-index) unit-id side wire-pair int-no show shdsl span-counters current-15min (if-index) show shdsl span-counters current-1day (if-index) show shdsl span-counters previous-15min (if-index) interval-number show shdsl span-counters previous-1day (if-index) interval-number

23

Use the following command to show the statistics related to Ethernet: show ethernet counters near-end line current-interval (if-index) show ethernet counters near-end line current-1day (if-index) show ethernet counters near-end line previous-interval (if-index) show ethernet counters near-end line previous-1day (if-index) show ethernet eth-int (if-index)

24

Use the following command to show the statistics related to VLANs: show vlan port-curr-15min-stats (port) show vlan port-curr-day-stats (port) show vlan port-15min-stats (port) interval-number show vlan port-prev-day-stats (port) interval-number show vlan current-15min-stats (vlanid) port ] show vlan current-day-stats (vlanid) port show vlan previous-15min-stats (vlanid) port interval-number show vlan vlan-day-stats (vlanid) port interval-number

25

Use the following commands to view the operational data of the near-end and far-end impulse noise sensor on an xDSL line: show xdsl imp-noise-sensor near-end oper-data (if-index) show xdsl imp-noise-sensor far-end oper-data (if-index)

DLP 2176-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2176 — Performance monitoring commands

26

Use the following commands to view the impulse noise sensor histograms on an xDSL line: show xdsl imp-noise-sensor near-end current-interval | current-1day | previous-interval | previous-1day show xdsl imp-noise-sensor far-end current-interval | current-1day | previous-interval | previous-1day

27

Use the following command to show the statistics related to SIP VoIP: show voice sip statistics system show voice sip statistics perf-info [(if-index)] show voice sip statistics termination current-15min [(if-index)] show voice sip statistics termination current-1day [(if-index)] show voice sip statistics termination prev-15min [(if-index)[ interval-num ]] show voice sip statistics termination prev-1day [(if-index) [interval-num ]] show voice sip statistics board-perfinfo [ (slot-id) ] show voice sip statistics board current-15min [ (slot-id) ] show voice sip statistics board current-1day [ (slot-id) ] show voice sip statistics board prev-15min [ (slot-id) [ interval-num ] ] show voice sip statistics board prev-1day [ (slot-id) [ interval-num ] ] show voice sip statistics call (if-index) interval [(interval-num) [start-time ] [icid ]]

28

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2176-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2176 — Performance monitoring commands

Configuration example (Config#1): show xdsl counters near-end line current-interval show xdsl counters far-end line current-interval show xdsl counters near-end line current-1day show xdsl counters far-end line current-1day show xdsl counters near-end line previous-interval show xdsl counters far-end line previous-interval show xdsl counters near-end line previous-1day show xdsl counters far-end line previous-1day show atm tc-current-int one-day show atm tc-current-int fifteen-min show interface port bridge-port:1/1/4/12 show la aggregator-info show la aggregate-list show la network-port-info show mstp bridge show mstp instance show mstp network-port show mstp port-instance show bridge network-port show qos statistics buffer-overflow total 1/1/4 show igmp channel counter show ip vrf-statistics show ip shub arp-stats show dhcp-relay port-stats 1/1/5/12:8:35 show dhcp-relay shub vrf-agent-stats show pppox-relay cross-connect statistics engine show pppox-relay cross-connect statistics client-port show pppox-relay cross-connect monitor-statistics engine show pppox-relay cross-connect monitor-statistics client-port show security radius auth-server auth-stats

DLP 2176-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2176 — Performance monitoring commands

show security radius acc-server acc-stats show security pae eapol-stats show transport snmp protocol-stats show transport ether-ifmau show transport shub mac show ima group state show ima group counters near-end current-interval show ima group counters near-end previous-interval show ima group counters far-end current-interval show ima group counters far-end previous-interval show ima link state show ima link counters near-end current-interval show ima link counters near-end previous-interval show ima link counters far-end current-interval show ima link counters far-end previous-interval show shdsl inventory show shdsl span-status show shdsl unit-status show shdsl segment-status show shdsl segment-counters current-15min show shdsl segment-counters current-1day show shdsl segment-counters previous-15min show shdsl segment-counters previous-1day show shdsl span-counters current-15min show shdsl span-counters current-1day show shdsl span-counters previous-15min show shdsl span-counters previous-1day show vlan port-curr-15min-stats 1/1/5/12:8:35 show vlan port-curr-day-stats 1/1/5/12:8:35 show vlan port-15min-stats 1/1/5/12:8:35 interval-number 2 show vlan port-prev-day-stats 1/1/5/12:8:35 interval-number 2

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2176-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2176 — Performance monitoring commands

show vlan current-15min-stats 200 port 1/1/5/12:8:35 show vlan current-day-stats 200 port 1/1/5/12:8:35 show vlan previous-15min-stats 200 port 1/1/5/12:8:35 interval-number 2 show vlan vlan-day-stats 200 port 1/1/5/12:8:35 interval-number 2 show xdsl imp-noise-sensor near-end oper-data 1/1/5/3 show xdsl imp-noise-sensor far-end oper-data 1/1/5/3 show xdsl imp-noise-sensor near-end current-1day 1/1/5/3 show xdsl imp-noise-sensor far-end current-1day 1/1/5/3 Configuration example (Config#2): show voice sip statistics system show voice sip statistics perf-info 1/1/3/1 show voice sip statistics termination current-15min 1/1/3/1 show voice sip statistics termination current-1day 1/1/3/1 show voice sip statistics termination prev-15min 1/1/3/1 interval-num 1 show voice sip statistics termination prev-1day 1/1/3/1 interval-num 1 show voice sip statistics board-perfinfo 1/1/3/1 show voice sip statistics board current-15min 1/1/3/1 show voice sip statistics board current-1day 1/1/3/1 show voice sip statistics board prev-15min 1/1/3/1 show voice sip statistics board prev-1day 1/1/3/1 show voice sip statistics call 1/1/3/1 interval 1 start-time 1970-01-10:01:41:59

DLP 2176-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2177 — Configure SFP downlink ports Purpose This procedure provides the steps to configure rack, shelf, and slot IDs of the remote SFP ports to be connected to the SFP downlink ports on:

• • • •

an NCNC-B, or NCNC-D board installed in a 7302 FD ISAM shelf an NCNC-B, NCNC-C, NCNC-D or NCNC-E board installed in a 7330 FD ISAM FTTN shelf an NRNT-A board installed in a 7356 FD ISAM FTTB shelf an ERAM-A Remote Aggregator

General You connect a remote LT unit (SEM, REM, or LT unit in an ES or REM) to an SFP downlink port on the host shelf. The SFP downlink port can be a dedicated SFP downlink port or a configurable port configured as a downlink port. Before a remote LT unit can be detected by the system, you must assign the rack, shelf, and slot number of the remote LT unit to the SFP downlink port in the host shelf to which it is connected. For the 7330 ISAM FTTN ES, the SFP port settings must match the shelf jumper settings of the connected ES and the slot number must match the number of the LT slot in which the connected remote LT unit is installed. The SEM and REM derive their rack and shelf IDs from the SFP port. For an overview of the downlink port assignments on the faceplate of the NCNC-x boards and the ERAM-A Remote Aggregator, see Table DLP 2177-1 and TNG 2106 - “SFP port mapping”.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2177-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2177 — Configure SFP downlink ports Table DLP 2177-1: Faceplate numbers for SFP downlink ports Unit

Faceplate numbers for Configurable up- or downlink ports

Dedicated downlink ports

ERAM-A Remote Aggregator

1 to 8 (1)

9 to 24

NCNC-B

2 to 7 (2)

—

NCNC-C

2 to 7 (2)

8 to 13

NCNC-D

2 to 7 (2)

—

NCNC-E

2 to 7 (2)

8 to 13

NRNT-A

3 to 6 (2)

—

Notes (1) All ports configured as downlink ports must be contiguous. (2)

All ports configured as downlink ports must be contiguous starting from the highest SFP port number. For example, SFP ports 5 and 6 on an NCNC-B cannot be configured as downlink ports unless port 7 is configured as an downlink port.

The host shelf is always assigned to rack 1 and shelf 1. As such, the SFP ports on the host shelf are identified by their faceplate numbers. The SFP ports on a remote LT unit are identified by the rack, shelf, and slot combination. The following conditions apply specifically to the SEM and the REM:

• • •

you are required to configure a rack, shelf, and slot ID for for each SFP port to which an SEM or a REM is connected the slot number is slot 4 (for SEM, using legacy based numbering) or 1 (for REM, using position-based or type-based numbering) up to four shelves are supported in a rack

The following conditions apply specifically to the SB-REM:

• • •

you are required to configure a rack, shelf, and slot ID for each SFP port to which an SB-REM is connected the slot number is the LT slot on the SB-REM that contains the remote LT unit connected to the downlink port up to four shelves are supported in a rack

Warning — Do not swap optical expansion link cables between downlink expansion ports on the host shelf, after the remote expansion unit is configured. Service disruptions will result and an alarm is raised. Do not change shelf and rack ID assignments after remote expansion units are connected and operational. Service disruptions will result and an alarm is raised. Service and port configurations are mapped to the optical expansion link. All affected port and service configurations will require reconfiguration.

DLP 2177-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2177 — Configure SFP downlink ports

See TNG 2106 for more information about rack and shelf assignments for remote expansion units.

Prerequisite The following prerequisites must be fulfilled before the SFP ports can be configured:

• •

The NCNC-x board must be planned; see DLP 2111. The shelf associated with the remote LT unit needs to be planned first; see DLP 2111, step 3.

Note — The ES is auto-planned by the system upon detection.

Procedure Proceed as follows to configure an SFP downlink port on a host shelf that will be connected to a remote LT unit. 1

If the host shelf SFP port you are configuring is a dedicated downlink port, go to step 4.

2

Configure the host shelf SFP port as a downlink port. configure equipment external-link-host (faceplate number) (no) direction

3

You can verify the configured link direction of the configurable ports with the following command: info configure equipment external-link-host (faceplate number)

4

Configure the association between the host shelf SFP downlink port and the remote LT unit with the following command: configure equipment external-link-assign (faceplate number) (no) remote

5

Verify the actual rack, shelf, and slot settings of the connected remote LT unit with the following command: show equipment external-link-host (faceplate number) detail

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2177-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2177 — Configure SFP downlink ports

6

If you are configuring an SFP port on an ERAM-A Remote Aggregator or an NCNC-x card, perform a system reset (with or without self-test) to allow the configuration of the SFP link direction (downlink) to take effect. In a non-redundant system, you can perform an NT reset (with or without self-test) instead of system reset (an NT reset takes less time than a system reset). a

Perform a system reset in a redundant or in a non-redundant system with the following command: admin equipment reboot-isam

b

Perform an NT reset in a non-redundant system with the following command: admin equipment slot nt-a reboot

7

You can troubleshoot a problem with an optical link between a remote LT unit and its host shelf with the following command: show equipment diagnostics sfp [position] detail

• • •

8

If an SFP shows a tx-fault, it must be replaced. If an SFP shows a tx-power value outside the normal range (given in the SFP Unit Data Sheet), it must be replaced. If an SFP shows an rx-power value outside the normal range (given in the SFP Unit Data Sheet), or shows LOS, check the tx-power of the companion SFP. If the tx-power of the companion SFP is in the normal range, the problem may be with the fiber.

STOP. This procedure is complete.

Configuration example for an NCNC-B board (Config#1): configure equipment external-link-host 6 direction remote-lt configure equipment external-link-assign 6 remote 1/2/2 info configure equipment external-link-host 6 admin equipment reboot-isam without-self-test show equipment external-link-host 6 detail show equipment diagnostics sfp iont:1/1/6 detail

DLP 2177-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2177 — Configure SFP downlink ports

Configuration example for an ERAM-A Remote Aggregator (Config#1): configure equipment external-link-host nt:sfp:8 direction remote-lt info configure equipment external-link-host nt:sfp:8 configure equipment external-link-assign nt:sfp:8 remote 1/2/2 admin equipment reboot-isam without-self-test show equipment external-link-host nt:sfp:8 show equipment diagnostics sfp nt:sfp:8 detail

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2177-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2177 — Configure SFP downlink ports

DLP 2177-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2179 — Configure system logging Purpose Use this DLP to configure system logging (SYSLOG).

General There are three main tasks you can perform using CLI when configuring system logging:

• • • •

enable and disable logging for all system logs create and configure up to 64 system logs configure where system logs are saved monitor system logs

The NE supports up to 64 system log files and up to 64 remote system log servers. You can enable or disable logging for all system logs and view system-wide information for system logs. You can view system-wide information for local system logs, such as the maximum message size allowed and statistics about how much combined disk space the local system logs utilize. System-wide information for local system log files are displayed using the show CLI command and can be displayed in four different formats. You can create and configure up to 64 system logs. The combined maximum size of all locally saved system log files is 2 Mbytes. For each system log file, you can set the method of cycling messages when the system log file is full. Cycling of system log messages is performed as follows: new entries are wrapped to overwrite the oldest entries. The limit of 2Mbytes can be overcome by directing the system logs to a remote system log server. This can be useful, for example, for video CDR messages.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2179-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2179 — Configure system logging

You can configure the following parameters for each system log file:

• •

• • • • •

system log filename (local only), entered using up to eight alphanumeric characters followed by a dot separator and a three-alphanumeric character extension; for example, Alrmhigh.txt destination server type: • all active TL1 and CLI terminals (all-users) • all active CLI terminals (all-CLI) • all active TL1 terminals (all-TL1) • single active TL1 terminal (tl1-user) • local file (file:name:size) • remote host (udp:port:serv-ip-addr) destination server address, entered as an alphanumeric host name or in standard dot format (maximum value 255.255.255.255); where 0.0.0.0 is entered for local files action taken when the system log file is full (wrap or discard) activate and deactivate logging delete a system log file view the configuration of a system log file

By default, all message types are logged to the system log files. In addition, alarms generated in the system and the errors encountered are logged to the system log files. You can configure filters to define which messages get logged to which system log file based on message type. Table DLP 2179-1 lists the possible message type and log severity parameters. You can select which messages are sent to specific system log files using filters and can group multiple message types. Table DLP 2179-1: Message type and log severity parameters Item

Description

Parameter

Message type

Authentication actions

authentication

CLI commands

cli-config-chgs

TL1 commands

tl1-config-chgs

CLI messages

cli-msgs

Equipment messages

EQPT

TL1 messages

tl1-msgs

Protocol tracing messages

tracing1 tracing2 tracing3

Video CDR messages

video-cdr

All message types

all

(1 of 2)

DLP 2179-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2179 — Configure system logging

Item

Description

Parameter

Log severity

Emergency

EM

Alert

AL

Critical

CR

Error

ER

Warning

WN

Notice

NO

Information

IN

Debug

DBG

(2 of 2)

When activating or deactivating system logs, you must specify the following information:

• • •

index number of the system log file (1 to 64) message type, or types if grouped, being sent to that system log file severity level set for that particular system log file

The index number is an integer from 1 to 64. Use the information command to view the settings of a system log file before entering the message type and log severity of the system log file to activate or deactivate. To monitor remote system logs dynamically, set the destination server type to all active CLI or all active TL1 terminals for a particular system log. This sends all messages to the active terminals that have a management session with the NE. When you are done monitoring, deactivate system logging for that server. You can view the static contents of a system log file that is saved to a remote server location using any text-based editor. You can also configure system and security logging using TL1 or SNMP. See the TL1 Commands and Messages for FD 24Gbps NT or the latest MIB for more information.

Procedure Proceed as follows to configure system logs: 1

View system-wide information for local system logs with the following command: show system syslog (type) Where: Type is how to display the information, which can be either detail, hierarchical, flat, or xml.

2

Create the system log and set the system log filename and configure the destination server type with the following command: configure system syslog destination (name) type no disable (no) upload-rotate

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2179-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2179 — Configure system logging

3

Delete a system log server with the following command: configure system syslog destination (name) disable

4

Configure which messages must be sent to a given system log destination and assign the appropriate system log parameters to them with the following command: configure system syslog route (name) msg-type facility (no) emergency (no) alert (no) critical (no) error (no) warning (no) notice (no) information (no) debug

5

Retrieve the configuration of a specific system log with the following command: info configure system syslog destination (name) type detail

6

Retrieve the configuration for all configured system logs with the following command: info configure system syslog destination detail

7

Force the system log file to rotate with this command: admin system syslog destination (name) rotate

8

STOP. This procedure is complete.

Configuration example (Config#1): show system syslog configure system syslog destination server1 type file:filename.c:20000 no disable configure system syslog route server1 msg-type authentication facility user no debug info configure system syslog destination server1 detail admin system syslog destination server1 rotate

DLP 2179-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2180 — Configure static MAC addresses Purpose The operator can specify entries in the layer 2 filtering database for a specific VLAN and unicast MAC address. This information is used by the bridge to determine how to propagate a received frame. This document describes the commands to configure static MAC addresses in the NE.

Prerequisite The following prerequisites must be fulfilled before static MAC addresses can be configured:

• • •

A VLAN must exist; see DLP 1117, DLP 1118, DLP 1119 or DLP 1120. The board must have been planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129.

Procedure Proceed as follows to configure static MAC addresses: 1

Configure a static MAC address on the LT with the following command: configure vlan vlan-port (port) unicast-mac (unicast-mac)

2

Configure a static MAC address on the SHub with the following command: configure vlan shub unicast-mac (unicast-mac) vlan-id forward-port

3

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2180-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2180 — Configure static MAC addresses

Configuration example (Config#1): configure vlan vlan-port vlan-port:1/1/5/12:8:35:299 unicast-mac 00:22:22:55:22:11 configure vlan shub unicast-mac 00:00:00:00:00:01 vlan-id 299 forward-port network:6

DLP 2180-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2181 — Configure operator authentication via RADIUS Purpose This procedure provides the steps to configure the authentication for an operator via RADIUS.

Note — This procedure can be used for the default superuser isadmin.

Procedure Proceed as follows to configure operator authentication via RADIUS: 1

Configure the RADIUS authentication server with the following command: configure system security radius auth-server (name) vrf-index 0 ip-address (no) port secret (no) retry-limit (no) timeout-limit (no) admin-down (no) dead-interval where vrf-index is the index of the management VRF, that is 0.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2181-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2181 — Configure operator authentication via RADIUS

2

Configure the RADIUS policy with the following command: configure system security radius policy (name) nas-id nas-ip-address (no) keep-domain-name disable-accnt-msg (no) acc-interval disable-eap

3

Configure the RADIUS server set with the following command: configure system security radius policy (name) servers (index) auth-server none | name: vrf-index-auth (no) acc-server none | name: (no) vrf-index-acc priority where vrf-index-auth is the index of the management VRF, that is 0.

4

Enable the operator policy with the following command: configure system security radius (no) relay (no) auth-super-user oper-policy-name

5

Enable the RADIUS for the superuser with the following command: configure system security radius (no) relay auth-super-user

6

STOP. This procedure is complete.

Configuration example (Config#1): configure system security radius auth-server RADAuthServ1 vrf-index 0 ip-address 10.176.5.5 secret Khinghkhongh timeout-limit 5 no admin-down dead-interval 1 configure system security radius policy oper_e14 nas-id E14 nas-ip-address 10.177.0.112 disable-accnt-msg disable-eap configure system security radius policy oper_e14 servers 1 auth-server name:RADAuthServ1 vrf-index-auth 0 no acc-server priority 1 configure system security radius operator-policy name:oper_e14

DLP 2181-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2185 — Configure DHCP MAC concentration in forwarder mode Purpose The DHCP MAC concentration functionality is only provided in forwarder mode. When the DHCP MAC concentration is enabled, Option 82 must be configured. When the MAC concentration configuration is changed (enabled or disabled), this is considered as a behavior of operator, so it is up to the operator to guarantee that the corresponding already set-up sessions are released by the DHCP server and to acknowledge the DHCP clients Activating the MAC address concentration feature of DHCP has the following impacts:

• •

Enlarged IP-aware Bridge scalability: allows a large number of subscribers in the same shared VLAN Requires the DHCP server to be able to allocate multiple IP addresses to the same chaddr (that is, LT MAC addresses). Consequently, the IP address assignment must be based on other DHCP fields than the chaddr, that is: • Option 82 (Relay Agent Info, that is Line ID): this option allows to allocate one IP address per PVC (ATM) or line (EFM) • Option 60 (Class ID): this option is used together with option 82 and allows to allocate one IP address per {service, PVC} or {service, line} couple • Option 61 (Client ID): if supported by the subscriber's device, this option allows to have a unique identifier of the device (typically filled with the MAC address) and consequently, the same full flexibility as the chaddr regarding IP address assignment

DHCP MAC concentration is configured per VRF:

• •

Enable Option-82 insertion Enable DHCP MAC concentration

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2185-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2185 — Configure DHCP MAC concentration in forwarder mode

Procedure Proceed as follows to configure the DHCP MAC concentration: 1

Add DHCP option to the forwarder VRF on the LT with the following command: configure dhcp-relay agent (vrfid) bcast-vlan option-82 circuit-id remote-id (no) dhcp-linerate

2

Enable DHCP MAC concentration with the following command: configure dhcp-relay agent (vrfid) client-hw-address copysourcemac

3

STOP. This procedure is complete.

Configuration example (Config#1): configure dhcp-relay agent 16 bcast-vlan l2-vlan:101 option-82 circuit-id physical-id remote-id customer-id configure dhcp-relay agent 16 client-hw-address copysourcemac

DLP 2185-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2186 — Configure ANCP session Purpose Currently, Access Node Control Protocol (ANCP) is only supported on top of TCP/IP. Once the IP address of a Broadband Network Gateway (BNG) is configured, and depending on the setting of the GSMP Retry Timer, the NE will start the GSMP Adjacency Protocol to setup a ANCP session with that BNG.

Note — A BNG can be:

• •

a Service Router/Switch (for example, Alcatel 7450 ESS or Alcatel 7750 SR) a BRAS

The NE does not reply to requests for a TCP connection from an “unknown” BNG. This means:

• •

If the TCP Retry Timer is zero, the NE will not start the TCP connection. If the TCP Retry Timer is not zero, the NE will start the setup of a TCP connection to the BNG whose IP address has been configured. If the GSMP Retry Timer is zero, the NE will not start the GSMP Adjacency Protocol, but instead be prepared to handle GSMP Adjacency Protocol messages from that BNG. If the GSMP Retry Timer is not zero, the NE starts the GSMP Adjacency Protocol in addition to being prepared to handle GSMP Adjacency Protocol messages from that BNG.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2186-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2186 — Configure ANCP session

Procedure Proceed as follows to configure an ANCP session: 1

Enable ANCP partitioning with the following command: configure l2cp partition-type

2

Configure the ANCP session parameters for a given session ID with the following command: configure l2cp session (index) bras-ip-address (no) gsmp-version (no) gsmp-sub-version (no) encap-type (no) topo-discovery (no) layer2-oam (no) alive-timer (no) port-reprt-shaper (no) aggr-reprt-shaper (no) tcp-retry-time (no) gsmp-retry-time (no) dslam-name (no) partition-id (no) window-size (no) tcp-port (no) vrf-id (no) sig-partition-id

3

Configure an ANCP interface with the following command: configure l2cp user-port (user-port) partition-id

4

View ANCP information with one or more of the following commands: a

View the ANCP session status (status of GSMP Adjacency Protocol) with the following command: show l2cp session-status (index)

b

View the ANCP session peers (identity of the peers) with the following command: show l2cp session-peers (index)

DLP 2186-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2186 — Configure ANCP session

c

View the ANCP session statistics (traffic counters for L2CP messages) with the following command: show l2cp session-stats (index)

d

View the ANCP partition status (interfaces associated to a given partition) with the following command: show l2cp partition (partition-id) [user-port ]

Note — This command does not list the interfaces associated to the default partition 0.

5

Stop the ANCP session with the following command: configure l2cp no session (index)

6

STOP. This procedure is complete.

Configuration example (Config#1): configure l2cp partition-type fixed-assigned configure l2cp session 1 bras-ip-address 192.168.200.100 partition-id 10 configure l2cp user-port 1/1/5/1 partition-id 10 configure l2cp user-port 1/1/5/2 partition-id 10 configure l2cp user-port 1/1/5/3 partition-id 10 configure l2cp no session 1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2186-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2186 — Configure ANCP session

DLP 2186-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2191 — Enable dual tagging in the SHub Purpose This procedure provides the steps to specify the tagging mode globally applicable to SHub VLANs. When the dual tag mode is set, the SHub works as a stacked-VLAN bridge.

Procedure Proceed as follows to configure dual tagging mode: 1

Set the dual tag mode in the SHub with the following command: configure vlan shub dual-tag-mode

2

Disable the dual tag mode in the SHub with the following command: configure vlan shub no dual-tag-mode

3

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan shub dual-tag-mode

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2191-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2191 — Enable dual tagging in the SHub

DLP 2191-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2195 — Configure general bridge parameters on the LT Purpose This procedure provides the steps to configure the system parameters for all bridge ports.

Procedure Proceed as follows to configure the system parameters for all bridge ports: 1

Configure specify the aging time for dynamically learned MAC addresses in the filtering database of the LT with the following command: configure bridge (no) ageing-time

Note 1 — The setting is applicable to the entire bridge. Note 2 — The setting must be higher then the used ageing timers used on the NT. Typical values: 1800 s on the LT board and 1200 s on the NT board. 2

Configure specify the aging time for dynamically learned MAC addresses in the filtering database of the SHub with the following command: configure bridge shub (no) ageing-time

Note — The setting is applicable to the entire SHub bridge.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2195-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2195 — Configure general bridge parameters on the LT

3

Configure specify the MAC learning states with the following command: configure bridge shub mac-learning (no) disable-nw-port

Note — The setting is applicable to the entire SHub bridge.

4

STOP. This procedure is complete.

Configuration example (Config#1): configure bridge ageing-time 1800 configure bridge shub ageing-time 1200 configure bridge shub mac-learning no disable-nw-port

DLP 2195-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP Purpose This document provides the steps to configure the SIP-based integrated voice service. Note: SIP = Session Initiation Protocol

Prerequisites The following prerequisites must be fulfilled before the SIP-based integrated voice service can be configured:

Board and applique planning The Voice POTS LT board (NPOT-A/NPOT-B/NPOT-C) and, if required, the corresponding applique (NCTA-A) must be planned; see DLP 2111. The Equipment Capability Profile must have been set to “SIP Profile”. When NPOT-C is used to replace NPOT-A in an ISAM shelf without NPOT-B, please refer to the “SW Installation Guide”, Chapter 4.4 “Re-download of the Active OSWP”.

Forwarding deployment models ISAM-Voice supports the Switched and the Routed Voice forwarding model. Either of these models can be configured according to the requirement of the customer.

•

When the Routed Voice forwarding model is selected, the NE must be configured as a router device, meaning that the Open Shortest Path First (OSPF)/RIP Routing Protocol must be enabled on the NE; see DLP 2107/DLP 2108. The Voice configuration will take care of the SHub being the next hop for upstream packet forwarding.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

•

When the Switched Voice forwarding model is selected, the NE must be configured as a L2 switching device. The Voice configuration will take care of the Edge Router being the next hop for upstream packet forwarding

SIP deployment models ISAM-Voice supports a centralized and a distributed SIP model. Either of these models can be configured according to the requirement of the customer.

• •

The centralized SIP model requires a single source/destination IP address for signalling and Voice traffic per ISAM-Voice node. Both IP addresses are configured at the SHub. The distributed SIP model requires a source/destination IP address for signalling and Voice traffic per LT board.

Switched forwarding model

•

•

DLP 2196-2

Centralized SIP model: • A signaling VLAN in mode Voice-VLAN must have been created at the SHub side; see DLP 1120. • A voice VLAN in mode Voice-VLAN must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to both VLANs created at the SHub side; see DLP 2121. • ASAM ports of the LT boards / Subtending links must have been added to both VLANs created at the SHub side; see DLP 2121. • Both the signalling and the voice VLAN created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the signalling VLAN at the SHub side. • A numbered IP interface must have been created on top of the voice VLAN at the SHub side. Distributed SIP model: • A signaling VLAN in mode residential-bridge must have been created at the SHub side. See DLP 1120. • A voice VLAN in mode residential-bridge must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to both VLANs created at the SHub side; see DLP 2121. • ASAM ports of the LT boards / Subtending links must have been added to both VLANs created at the SHub side; see DLP 2121. • Both the signalling and the voice VLAN created at the SHub must have been associated with the fast path VRF.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

Routed forwarding model

•

•

Centralized SIP model: • A signaling VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A voice VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A signaling VLAN in mode Voice-VLAN must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_1 in mode Voice-VLAN must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_2 in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • Network interfaces must have been added to the signalling and voice VLAN created at the SHub VRF network side; see DLP 2121. • ASAM ports of the LT boards must have been added to the Voice VLAN_1 created at the SHub VRF user side; see DLP 2121. • ASAM ports of the SUBTENDING links must have been added to the Voice VLAN_2 created at the SHub VRF user side; see DLP 2121. • ASAM ports of the LT boards must have been added to the signaling VLAN created at the SHub VRF user side; see DLP 2121. • All VLANs created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the signaling VLAN at the SHub VRF network side. • A numbered IP interface must have been created on top of the voice VLAN at the SHub VRF network side. • A numbered IP interface must have been created on top of the signaling VLAN at the SHub VRF user side. • A numbered IP interface must have been created on top of the voice VLAN_1 at the SHub VRF user side. • A numbered IP interface must have been created on top of the voice VLAN_2 at the SHub VRF user side. Distributed SIP model: • A signaling VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A voice VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A signaling VLAN in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_1 in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_2 in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • Network interfaces must have been added to the signalling and voice VLAN created at the SHub VRF network side; see DLP 2121. • ASAM ports of the LT boards must have been added to the Voice VLAN_1 created at the SHub VRF user side; see DLP 2121.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

• • • • • • • •

ASAM ports of the SUBTENDING links must have been added to the Voice VLAN_2 created at the SHub VRF user side; see DLP 2121. ASAM ports of the LT boards must have been added to the signaling VLAN created at the SHub VRF user side; see DLP 2121. All VLANs created at the SHub must have been associated with the fast path VRF. A numbered IP interface must have been created on top of the signaling VLAN at the SHub VRF network side. A numbered IP interface must have been created on top of the voice VLAN at the SHub VRF network side. A numbered IP interface must have been created on top of the signaling VLAN at the SHub VRF user side. A numbered IP interface must have been created on top of the voice VLAN_1 at the SHub VRF user side. A numbered IP interface must have been created on top of the voice VLAN_2 at the SHub VRF user side.

Note — The starting point of the above prerequisite requirements is an ISAM-Voice model that makes use of distinct VLANs for voice and signalling traffic. However, aiming at an IP subnet width reduction, ISAM-Voice supports an alternative model that makes use of a single VLAN sharing voice and signalling traffic. In this case, the prerequisite requirements are identical to the ones related to the voice VLAN described in the above sections for the switched and routed forwarding architecture.

Digitmap configuration policy

Policy

• • • •

•

DLP 2196-4

A digitmap is a concatenation of digitmap rules. The rules inside the digitmap are automatically separated by a “|” All the rules of the digitmap need to be configured one by one a rule can be configured as either • a single digitmap-pattern • a single digitmap-regular-expression • a combination of one or multiple digitmap-patterns and/or a single digitmap-regular-expression A digitmap-pattern may include • 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, *, #: representing the dialable digits on a POTS phone (note: the character digits are case insensitive) • x: can be used as a wildcard, designating any digit in the range [0,1,2,3,4,5,6,7,8,9] • a white space is non significant

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

•

•

• •

•

a digitmap-regular-expression may include: • A set of “alternative” digit symbols can be enclosed in brackets [], - Represents one occurrence of any of the enclosed digit symbols - Allows for ranging using hyphen symbol “-” - If a ^ appears immediately following the opening bracket, it means negation. Hence it represents one occurrence of any NOT enclosed digit symbol • Multiple occurrence symbols: - “.”: signifies zero or more occurrence - “+”: signifies one or more occurrences - “?”: signifies zero or one occurrence • Range identifiers: {m}: signifies exactly m occurrences {m, n}: signifies at least m but no more than n occurrences {m,}: signifies at least m occurrences m can be zero (0) and {,m} is not supported • A sequence of pattern elements enclosed in (): this matches the concatenation of the elements in the sequence. Inter digit timer modifier • The T-modifier can be used to switch from L to S interdigit timer and can be used in a digitmap-pattern as well as a digitmap-regular-expression. In this particular case, a pattern element followed by the symbol T matches if and only if the critical timer expires at that point • The S-modifier can be used to specify that the substring that matches the pattern element that precedes the S modifier represents a service code that is of local interest only. For example: 12S: the pattern 12 is a service code which is of local interest only. • By default, x. equals x.T, and also results in a switch from L to S interdigit timer. The size of one rule cannot exceed 32 bytes (string 0..32). One digitmap-pattern as well as one digitmap-regular-expression cannot exceed the boundaries of one rule. As such, the maximum size of both is also limited to 32 bytes. The same applies for a combination of multiple digitmap-pattern and/or digitmap-regular-expression that are configured inside one rule. The total digitmap size is the sum of the size of all rules in the digitmap and cannot exceed 4K bytes.

Digitmap-patterns/digitmap-regular-expression examples

• •

Pattern with only digit symbols: • 112: Exact match for dial string 112 • 11x: Exact match for any 3 digit dial string that starts with digits 11 Pattern including alternative digit symbols: • 11[134]: Exact match for dial string 111, 113 and 114 • 11[1-3]: Exact match for dial string 111, 112 and 113 • 11[^4]: Exact match for any 3 digit dial string that starts with digits 11, except 114

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

•

•

•

Pattern including multiple occurrence symbol: • 11x+: Exact match after L-timer expiry for any dial string of minimum 3 digits that starts with digits 11 • 11x?: Exact match for any 3 digit dial string that starts with digits 11./ Exact match after L-timer expiry for dial string 11 • 11x.: Exact match after L-timer expiry for any dial string that starts with digits 11. • 11.: Not identical to 11x.T as 11x.T makes use of the S-timer after digit string 11 is received Pattern including multiple occurrence range: • 11x{2}: Exact match for any 4 digit dial string that starts with digits 11 • 11x{0,2}: Exact match for any 4 digit dial string that starts with digits 11 / Exact match after L-timer expiry for any 2 or 3 digit dial string that starts with digits 11 • 11x{2,}: Exact match after L-timer expiry for any dial string of minimum 4 digits that starts with digits 11 Pattern including inter digit timer modifier • 11x.: Exact match after L-timer expiry for any dial string that starts with digits 11. • 11.: Identical to 11x.T as 11x.T makes use of the S-timer after digit string 11 is received • 11x+T: Exact match after S-timer expiry for any dial string of minimum 3 digits that starts with digits 11 • 11x?T: Exact match for any 3 digit dial string that starts with digits 11 / Exact match after S-timer expiry for dial string 11 • 11x{0,2}T: Exact match for any 4 digit dial string that starts with digits 11 / Exact match after S-timer expiry for any 2 or 3 digit dial string that starts with digits 11 • 11x{2,}T: Exact match after S-timer expiry for any dial string of minimum 4 digits that starts with digits 11

Digit collection timers

• • •

The permanent timer • Pre-dialling timer, expires when no digits are dialled The partial timer (L or Long-timer) • Inter-digit timer (re-) started after each received digit The critical timer (S or Short-timer) • Timer associated with the T modifier and starts when previous pattern has been matched.

Best practice The best practise to configure a digit map rule is to put the whole rule within double quotes See also the Basic Type Formatting Rules for CLI in the CLI Command Guide for FD 24Gbps NT:

DLP 2196-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

Printable strings must be placed within double quotes if they contain special characters: double quote “, a backslash \, a question mark ?, a cross #, a space, a tab, a carriage return, or a new line.

Digitmap configuration example Below are two configuration alternatives for the digitmap 100 | 112 | 1471 | 1475 | 17070 | 08001111 | (*|#)x{3}*x+# | (*|#|*#)x{2,3}# | (141|1470)00x{7} | *x{2}*x+# | 00x{7}

•

•

Configuration alternative -1 configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular Configuration alternative -2 configure voice sip digitmap DialPlan1 type regular “100|112|1471|1475|1770|08001111” configure voice sip digitmap DialPlan1 type regular “(*|#)x{3}*x+#|(*|#|*#)x{2,3}#” configure voice sip digitmap DialPlan1 type regular configure voice sip digitmap DialPlan1 type regular

rule rule rule rule rule rule rule rule rule rule rule

“100” “112” “1471” “1475” “17070” “08001111” “(*|#)x{3}*x+#” “(*|#|*#)x{2,3}#” “(141|1470)00x{7}” “*x{2}*x+#” “00x{7}”

rule rule rule “(141|1470)00x{7}” rule “*x{2}*x+#|00x{7}”

Procedure The system requires a strict sequence to be followed during the configuration of the SIP based integrated VoIP Service object groups:

•

STEP 1: • Voice Service Provider Attributes • SIP Server Attributes • DNS Server Attributes • SIP User Agent • SIP User Agent Access Point • SIP Session Timer • SIP Register Attributes • SIP Transport Protocol Attributes • SIP Network Redundancy • Line ID Syntax Profile • Dial Plan • Digit Map • DHCP Authentication (For future use only)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

• •

STEP 2: • SIP Termination • SIP Termination TCA threshold STEP 3: • Trigger Geo-Fail-Over / Geo-Fail-Back

The configuration of the attributes in STEP N must be completed before the configuration of the attributes of STEP N+1 can be done. There is no strict configuration sequence to be followed for the atributes that belong to a particular STEP. Proceed as follows to configure the SIP based integrated VoIP service: 1

STEP 1: i

Configure the SIP Voice Service Provider with the following command: configure voice sip vsp (name) (no) domain-name (no) admin-status (no) tinfo (no) ta4 (no) ttir1 (no) t-acm-delta (no) access-held-time (no) awaiting-time (no) digit-send-mode (no) overlap-484-act (no) dmpm-intdgt-expid (no) dial-start-timer (no) dial-long-timer (no) dial-short-timer (no) uri-type (no) rfc2833-pl-type (no) rfc2833-process (no) min-data-jitter (no) init-data-jitter (no) max-data-jitter (no) release-mode (no) dyn-pt-nego-type (no) vbd-g711a-pl-type (no) vbd-g711u-pl-type

DLP 2196-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

(no) (no) (no) (no) (no)

vbd-mode timer-b timer-f timer-t1 timer-t2

Note 1 — ISAM Voice supports actually only one Voice Service provider. The name of the Voice Service Provider is fixed to “VSP1”. Note 2 — Alcatel-Lucent advises to keep the values for the attributes timer-b, timer-f, timer-t1 and time-t2 set to the default RFC3261 standardised timer values. If these values are changed to non-default values, then this must be done in a network-coordinated way in order to avoid interoperability issues. Note 3 — The following restriction applies when modifying the SIP Voice Service Provider entry:

• •

ii

A modification of the attribute name is not allowed as ISAM Voice actually supports only one Voice Service Provider and the name of the Voice Service Provider is fixed to “VSP1”. A modification of the attributes tinfo, ta4, ttir1, t-acm-delta, access-held-time, awaiting-time, digit-send-mode, overlap-484-act, dmpm-intdgt-expid, dial-start-timer, dial-long-timer, dial-short-timer, uri-type, rfc2833-pl-type, rfc2833-process, min-data-jitter, init-data-jitter, max-data-jitter, release-mode, dyn-pt-nego-type, vbd-g711a-pl-type, vbd-g711u-pl-type, vbd-mode, domain-name, timer-b, timer-f, timer-t1 and timer-t2 is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

Configure the SIP server(s) with the following command: configure voice sip server (name) (no) admin-status address (no) port (no) server-role (no) priority (no) weight (no) site (no) transproto (no) dnsname-type admin-domain-name

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

Note 1 — A SIP Server entry can be configured in one of the following modes:

• •

•

The IP@ Mode (address-type = "IPv4"): The SIP server entry is configured with the IP@ of the SIP Server. This mode must be used for VoIP networks that do not support the Domain Name Service. The Domain Name Mode (address-type = "DNS" & dnsname-type = "DN") : The SIP server entry is configured with the Domain Name of the SIP Server. This mode can only be used for VoIP networks that support the Domain Name Service. The FQDN Mode (address-type = "DNS" & dnsname-type = "FQDN") : The SIP server entry is configured with the Fully Qualified Domain Name of the SIP Server. This mode can only be used for VoIP networks that support the Domain Name Service.

These configuration modes must not be mixed unless a Geo Primary/ESA-Back-up network topology is to be supported. Thus following configuration rules apply:

• •

Primary site and back-up site MUST be configured with the same configuration mode. Exception: the ESA back-up site must always be configured in the IP@ mode.

Note 2 — The "weight" attribute is currently not supported. Note 3 — The configuration of the attributes "port", "priority" and "transproto" is irrelevant in case the Domain Name Mode is used. Note 4 — The configuration of the attributes "port", "priority" and "transproto" is mandatory in case the FQDN Mode or IP@ Mode is used. Note 5 — The attribute server-role can actually only be configured as "Both". Note 6 — ISAM-V supports a feature called "Deliberate Update" offering the ability to perform a fail-over from the actually used SIP first hop server to another SIP server. The "Deliberate Update" has been introduced as to allow the customer to temporarily remove an actually used SIP first hop SIP server from the redundancy group for maintenance purposes. Such fail-over is triggered by means of an update of the list of SIP Servers configured with the IP@ or FQDN mode in the SIP Server table. In this respect, the operator is asked to follow the rule that in case the SIP first hop server to be put in maintenance state is replaced in the redundancy group by another SIP first hop server then this replacing SIP first hop server must be added to the list prior to the deletion of the replaced SIP first hop server from the list. Only when this rule is followed, the ISAM Voice guarantees a successful deliberate update behaviour. Upon the execution of a deliberate update, the ISAM-V will always select the SIP first hop server with the highest priority being present and up and running in the redundancy group to be used as the new target SIP server to address for SIP requests. DLP 2196-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

Note 7 — The following restriction applies when modifying a SIP Server entry:

• • •

iii

A modification of the attribute name is not allowed. The SIP Server name can only be modified through a delete / re-create of the entry. A modification of the attributes priority and site is allowed without condition. A modification of the attributes address, port, server-role, transproto, admin-domain-name and dnsname-type is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

Configure the DNS server(s) with the following command: configure voice sip dnsserver (name) (no) admin-status address (no) priority (no) site admin-domain-name (no) port

Note 1 — A DNS Server entry can be configured in the IP address Mode only. Note 2 — The following restriction applies when modifying a DNS Server entry:

• • •

iv

A modification of the attribute name is not allowed. The DNS Server name can only be modified through a delete / re-create of the entry. A modification of the attributes priority and site is allowed without condition. A modification of the attributes address, port and admin-domain-name is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

Configure the SIP user agent with the following command: configure voice sip user-agent (name) (no) ip-addr-policy (no) ip-config-mode (no) signal-gateway-ip signal-vlan-id (no) signal-dscp (no) signal-pbits (no) signal-link-mtu (no) rtp-gateway-ip rtp-vlan-id

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

(no) (no) (no) (no) (no)

rtp-dscp rtp-pbits rtp-link-mtu dhcp-optreq-list admin-status

Note 1 — ISAM Voice supports actually only 1 SIP User Agent. An instance of this SIP User Agent is created at each of the voice LT boards. Note 2 — The attribute dhcp-optreq-list is defined for future usage. Note 3 — When the attribute ip-config-mode is configured as DHCP, the system creates autonomously the user agent access point entries. These entries cannot be modified by the administrator. Configuring the attribute ip-config-mode to DHCP is only allowed for the SIP distributed model. Note 4 — When the attribute ip-config-mode is configured as MANUAL and the attribute ip-addr-policy is configured as Distributed, the administrator must create a SIP User Agent Access Point for each of the Voice LT boards. Note 5 — When the attribute ip-config-mode is configured as MANUAL and the attribute ip-addr-policy is configured as Centralised, the administrator must create a single SIP User Agent Access Point. This SIP User Agent Access Point is shared by all Voice LT boards. Note 6 — The system can be configured in shared or distinct VLAN mode.

• •

Shared VLAN mode: the attributes signal-vlan-id and rtp-vlan-id are configured with the same VLAN ID, implies a single VLAN that is shared by signaling and VLAN traffic. Distinct VLAN mode: the attributes signal-vlan-id and rtp-vlan-id are configured with a different VLAN ID, implies a different VLAN for signaling traffic than for voice traffic.

Both modes apply to the SIP Centralised Model and the SIP Distributed Model.

Note 7 — In case of Shared VLAN mode, the attributes signal-gateway-ip and rtp-gateway-ip are configured with the same gateway IP address. Otherwise, in case of Distinct VLAN mode, the attributes signal-gateway-ip and rtp-gateway-ip are configured with a different gateway IP address.

DLP 2196-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

Note 8 — The following restriction applies when modifying the SIP User Agent entry:

• • •

v

A modification of the attribute name is not allowed. The SIP User Agent name can only be modified through a delete/re-create of the entry. A modification of the attributes ip-addr-policy and ip-config-mode is not allowed. These attributes can only be modified through a delete/re-create of the entry. A modification of the attributes signal-gateway-ip, signal-vlan-id, signal-dscp, signal-pbits, signal-link-mtu, rtp-gateway-ip, rtp-vlan-id, rtp-dscp, rtp-pbits and rtp-link-mtu is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

If the parameter ip-config-mode has been set to manual in step iv, the configuration of the SIP user agent access point is to be done manually. Configure the SIP user agent access point with the following command: configure voice sip user-agent-ap (ua-name) slot-id signal-ip rtp-ip (no) dhcp-fqdn (no) admin-status

Note 1 — When the SIP User Agent attribute ip-config-mode is configured as MANUAL and the SIP User Agent attribute ip-addr-policy is configured as Distributed , the administrator must create a SIP User Agent Access Point for each of the Voice LT boards. Note 2 — When the SIP User Agent attribute ip-config-mode is configured as MANUAL and the SIP User Agent attribute ip-addr-policy is configured as Centralised , the administrator must create a single SIP User Agent Access Point. This SIP User Agent Access Point is shared by all Voice LT boards. The attribute slot-id is set to the Network termination board slot-id. Note 3 — The attribute dhcp-fqdn is defined for future usage. Note 4 — In case of Shared VLAN mode, the attributes signal-ip and rtp-ip are configured with the same IP address. Otherwise, in case of Distinct VLAN mode, the attributes signal-ip and rtp-ip are configured with a different IP address. Note 5 — The following restriction applies when modifying a SIP User Agent Access Point entry:

• •

A modification of the attribute ua-name is not allowed. The ua-name can only be modified through a delete/re-create of the entry. A modification of the attributes signal-ip and rtp-ip is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

vi

Configure the SIP Session Timer with the following command: configure voice sip system session-timer (no) enable (no) min-se-time (no) se-time (no) admin-status

Note — The following restriction applies when modifying the SIP Session Timer entry: A modification of the attributes min-se-time and se-time is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”. vii

Configure the SIP Register characteristics with the following command: configure voice sip register (provider-name) (no) register-uri (no) register-intv (no) reg-retry-intv (no) reg-prev-ava-intv (no) reg-head-start (no) reg-start-min

Note 1 — The SIP register entry is autonomously created by the system upon the manual creation of the Voice Service Provider entry. Note 2 — ISAM Voice supports actually only 1 Voice Service provider. Consequently there is only one SIP Register entry created by the system. The attribute provider-name is set to the value of the attribute domain-name configured in the Voice Service Provider entry. Note 3 — The following restriction applies when modifying the SIP Register entry: A modification of the attributes register-uri, register-intv, reg-retry-intv, reg-prev-ava-intv, reg-head-start and reg-start-min is allowed with the following condition: the admin state of the corresponding Voice Service Provider must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

DLP 2196-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

viii Configure the SIP Transport Protocol characteristics with the following command: configure voice sip transport (trans-protocol) provider-name (no) admin-status (no) port-rcv (no) tcp-idle-time (no) max-out-udp-size

Note 1 — ISAM Voice supports actually only one Voice Service provider. Consequently there can only one SIP Transport Protocol entry be created. Note 2 — A single entry is created to enable all transport protocols that the system will listen to for incoming SIP requests. The system will listen to the same protocol port number for all transport protocols. Only UDP and TCP are actually supported. Note 3 — In case the attribute ip-addr-policy (SIP User Agent) is configured as Centralised, the attribute port-rcv must be configured with the value 0 meaning that the system does autonomously define the receive port. Note 4 — The attribute tcp-idle-time has only relevance in case TCP is configured as transport protocol being supported by the system. Note 5 — The attribute max-out-udp-size has only relevance in case both, UDP and TCP are configured as transport protocols being supported by the system. Note 6 — The following restriction applies when modifying the SIP Transport Protocol Register entry: A modification of the attributes port-rcv, tcp-idle-time and max-out-udp-size is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”. ix

Configure the Network redundancy characteristics with the following command: configure voice sip redundancy (admin-domain-name) (no) support-redun (no) dns-purge-timer (no) dns-ini-retr-int (no) dns-max-retr-nbr (no) fg-monitor-method (no) fg-monitor-int (no) bg-monitor-method (no) bg-monitor-int (no) stable-obs-period (no) fo-hystersis (no) del-upd-threshold

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

(no) (no) (no) (no) (no)

auto-server-fo auto-server-fb auto-sos-fo auto-sos-fb rtry-after-thrsh

Note 1 — ISAM Voice supports actually only one Voice Service provider. Consequently there can only one SIP Network redundancy entry be created. Note 2 — The attributes fg-monitor-method, fg-monitor-int, bg-monitor-method, bg-monitor-int, stable-obs-period, fo-hysteresis, del-upd-threshold, auto-server-fo, auto-server-fb, auto-sos-fo, auto-sos-fb and rtry-after-thrsh have only relevance when the attribute support-redun is configured as enable. Note 3 — The following restriction applies when modifying the SIP Network Redundancy entry:

•

•

•

A modification of the attributes support-redun, fg-monitor-int, bg-monitor-int, stable-obs-period, fo-hysteresis, del-upd-threshold, auto-server-fo, auto-server-fb, auto-sos-fo, auto-sos-fb and rtry-after-thrshfig-mode is allowed without condition. A modification of the attributes dns-purge-timer, dns-ini-retr-int and dns-max-retr-nbr is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”. A modification of the attributes fg-monitor-method and bg-monitor-method is allowed with the following condition: the admin state of the SIP Voice Service provider must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

DLP 2196-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

x

Configure the SIP Line Identifier Syntax with the following command: configure voice sip lineid-syn-prof (name) (no) syntax-pattern (no) pots-syntax

Note 1 — The Line Identifier syntax is configured as a character string of max 128 characters and composed of a prefix together with a number of pre-defined keywords and operator defined characters. Note 2 — The following keywords can be used in the profile syntax: "Access_Node_ID", "Rack", "Frame", "Slot", "ShSlt", "Port", "ShPrt", “Channel".

• • • • • •

Channel: Specifies the B channel on an ISDN port and/or a PMx port. Port/ShPrt: Specifies the port of the voice LT board to which a SIP termination is connected. "Port": includes leading zeroes; "shPrt" excludes leading zeroes. Slot/ShSlt: Specifies the slot ID of the voice LT board. [The numbering scheme is subject to configuration control, see ISAM.] "Slot": includes leading zeroes; "ShSlt" excludes leading zeroes. Frame: Specifies the shelf within a rack. Rack: Specifies the rack. Access_Node_ID: Specifies the ISAM System ID.

Note 3 — The keywords may not appear in a strict order. Note 4 — All keywords have been defined as optional. It is the responsibility of the operator to define such a Line ID profile syntax that finally each of the translated termination ID values are unique in the voice network. Note 5 — “/” is defined as the default separator between keywords, but the operator can also make use of other tags (such as #,%...). Note 6 — It is allowed to include character strings other than the key words in the line ID profile. These customized character strings will be kept unchanged and copied into the translated string Note 7 — The prefix can be freely defined by the customer Note 8 — The following restriction applies when modifying the SIP Line Identity Syntax entry: A modification of the syntax is allowed without condition. However the modification will only become effective from the moment :

• • •

a new termination is created an existing termination is modified the LT board is reset.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

xi

Configure the Dial Plan with the following command: configure voice sip dialplan (name) (no) pre-activated (no) static-prefix (no) static-suffix

Note 1 — Only one Dial Plan can be created. Note 2 — The following restriction applies when modifying the Dial Plan entry:

• • xii

A modification of the attribute name is not allowed. The ua-name can only be modified through a delete/re-create of the entry. A modification of the attributes pre-activated, static-prefix, and static-suffix is allowed without condition.

Configure the Digit Map profile(s) with the following command: configure voice sip digitmap (name) type rule (no) access-type

Note 1 — When the string in contains a special character, then it must be placed between double quotes. For more information, see the CLI Command Guide for FD 24Gbps NT, section 1.5. Note 2 — The name of the Voice SIP dial plan digitmap profile must be the same as the name of the Voice SIP dial plan profile (see step ix). Note 3 — The parameter access_type is not visible when a new Digit Map is created, but only when an existing Digit Map is modified. Note 4 — The following restriction applies when modifying a Digit Map entry: A digit map entry cannot be modified. An update a digit map entry is to be done by a delete/re-create of the associated entry. xiii Configure the DHCP Authentication with the following command: configure voice sip dhcp-authent-para (ua-name) secret-id (no) key (no) action-type

Note — The DHCP authentication attributes and command were defined for future use only.

DLP 2196-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

2

Do one of the following:

• • i

Configure Local Loop Unbundling; go to step i. If Local Loop Unbundling is not used, the termination must be configured; go to step iii. Configure the Local Loop Unbundling with the following command: configure voice sip termination (termination) local-loop (no) unbundle

ii

Go to step 9.

iii

Configure the SIP terminations with the following command: configure voice sip (no) termination (if-index) ) (no) directory-number (no) user-name (no) display-name (no) uri (no) direct-uri (no) line-feed (no) md5-realm (no) md5-password (no) admin-status (no) clip-mode (no) anti-tapping (no) impedance (no) rx-gain (no) tx-gain

Note 1 — The attribute anti-tapping is defined for future usage only. Note 2 — The MD5 password is encrypted by means of the DES-CBC algorithm and archived in this encrypted format. It will be displayed in a non-readable format. Note 3 — The following restriction applies when modifying a SIP Termination entry: A modification of the parameters directory-number, user-name, display-name, uri, direct-uri, line-feed, md5-realm, md5-password, clip-mode, impedance, rx-gain and tx-gain requires the admin state to be set to “locked” prior to the modification and afterwards the admin state to be set to “unlocked”. iv

Configure the Threshold Crossing Alarm for the SIP terminations with the following command: configure voice sip termination (if-index) tca (no) enable (no) high-jbfl (no) low-jbfl

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

Note 1 — The system will autonomously activate the voice statistics upon the creation of the SIP Termination. Note 2 — The reporting of the Threshold Crossing Alarm can be enabled/ disabled per SIP Termination. Note 3 — The following restriction applies when modifying a TCA: A modification of the attributes high-jbfl and low-jbfl is allowed without condition. 3

Trigger Geo Fail-Over/Geo Fail-Back with the following command: configure voice sip redundancy-cmd (domain-name) (no) start-time (no) end-time fail-x-type

Note 1 — The following strategy applies regarding the attributes start-time and end-time:

• •

start-time = end-time: forced Geo fail-over/Geo fail-back upon start-timer expiry. start-time ≥ 0 and end-time > start-time: graceful Geo fail-over/fail-back upon start-timer expiry, switch to forced Geo fail-over / Geo fail-back upon end-time expiry.

Note 2 — A new Geo Fail-Over/Geo Fail-Back command shall be rejected if a previous Geo Fail-Over/Geo Fail-Back command is still scheduled or has not been completed yet. 4

View the SIP Server operational state with the following command: show voice sip server [(name)]

5

View the SIP User Agent Access Point operational state with the following command: show voice sip user-agent-ap [(name) [slot-id ]]

6

View the SIP Termination Profile with the following command: show voice sip termination [(if-index)]

7

View the Network Redundancy State with the following command: show voice sip redundancy-node redundancy-state [(admin-name) [slot-id ]]

8

View the progress of the Geo-Redundancy Fail-Over / Fail-Back State with the following command: show voice sip redundancy-node redundancy-cmd [(provider-name)]

9

STOP. This procedure is complete.

DLP 2196-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2196 — Configure Voice SIP

Step 1 - Configuration example 1: IP config mode is set to "manual". The IP config mode "manual" applies to both the centralised and the distributed deployment model. (Config#1, Config#2) configure voice sip server SIPServer1 address ipv4:200.200.1.1 configure voice sip server SIPServer1 admin-status up configure voice sip dialplan SIPDialplan1 configure voice sip digitmap SIPDialplan1 type regular rule 120 Distributed deployment model (the SIP User Agent Access Point needs to be configured separately for each of the LT board)(Config#2) configure voice sip user-agent ua_01 signal-gateway-ip 40.0.0.241 signal-vlan-id 87 domain-server 40.0.0.10 rtp-vlan-id 2 rtp-gateway-ip 192.168.0.1 ip-addr-policy distributed ip-config-mode manual admin-status up configure voice sip user-agent-ap ua_01 slot-id lt:1/1/5 signal-ip 40.0.0.136/24 rtp-ip 192.168.0.136/24 admin-status up Centralised deployment model (the SIP user Agent Access Point needs to be configured only once with the slot position of NT-A)(Config#1) configure voice sip user-agent ua_01 signal-gateway-ip 40.0.0.241 signal-vlan-id 87 domain-server 40.0.0.10 rtp-vlan-id 2 rtp-gateway-ip 192.168.0.1 ip-addr-policy centralised ip-config-mode manual admin-status up configure voice sip user-agent-ap ua_01 slot-id nt signal-ip 40.0.0.136/24 rtp-ip 192.168.0.136/24 admin-status up Step 1 - Configuration example 2: IP config mode is set to "DHCP". The IP config mode "DHCP" applies to the distributed deployment model only. No need to configure the SIP User Agent Access Point. The system will autonomously create the SIP User Agent Access Point for each of the LT boards based on the DHCP configuration input. (Config#1) configure voice sip server SIPServer1 address ipv4:200.200.1.1 configure voice sip server SIPServer1 admin-status up configure voice sip dialplan SIPDialplan1 configure voice sip digitmap SIPDialplan1 type regular rule 120 configure voice sip user-agent ua_01 signal-vlan-id 87 rtp-vlan-id 2 ip-addr-policy distributed ip-config-mode dhcp admin-status up Step 2 (Config#1) configure voice sip vsp vsp1 domain-name fs5k8.shanghai.com digit-send-mode overlap-invite no dis-udp no tcp no uri-type no reg-int-timer admin-status up Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2196-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2196 — Configure Voice SIP

configure voice sip system session-timer se-enable enable configure voice sip termination 1/1/3/1 uri [email protected] directory-number 55558236 user-name 8236 md5-realm fs5k8.shanghai.com md5-password newsys admin-status up configure voice sip termination 1/1/3/1 directory-number 55558236 user-name 8236 display-name Test uri [email protected] md5-realm fs5k8.shanghai.com md5-password newsys admin-status up configure voice sip termination 1/1/3/1 tca enable high-jbfl 80 low-jbfl 60

DLP 2196-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2198 — Configure the multicast service on a user port Purpose This procedure provides the steps to configure the multicast service on a user port. It is typically configured when a user subscribes to the multicast service.

Prerequisites The following prerequisites must be fulfilled before a multicast service can be configured:

• • • •

The The The The

multicast service is configured; see DLP 2136. multicast VLAN is configured; see DLP 2137. multicast channels are configured; see DLP 2138. user port is configured; see DLP 1124.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2198-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2198 — Configure the multicast service on a user port

Procedure Proceed as follows to configure the multicast service on a user port: 1

Configure an IGMP channel with the following command: configure igmp channel (port) (no) perm-pkg-bitmap (no) max-num-group (no) igmp-version (no) forking (no) lt-ont-signaling (no) mc-pbit-value (no) mcast-vlan-id (no) mcast-svc-context

Note 1 — The parameter perm-pkg-bitmap is kept for backward compatibility with previous releases. Note 2 — The parameter mcast-svc-context should match the mcast-svc-context of a multicast channel for a join for the multicast channel on this multicast service to be processed as a configured multicast stream. If not, the join is processed as an unconfigured multicast stream for this service. Note 3 — The mcast-svc-context can be used only when the vlanSelection attribute in the IGMP system is not selected; see DLP 2136. 2

Assign full view permissions to certain packages with the following command: configure igmp channel (port) (no) fullview-packages (package)

3

Assign preview permissions to certain packages with the following command: configure igmp channel (port) (no) preview-packages (package)

Note — This step can be skipped if preview is not required.

4

DLP 2198-2

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2198 — Configure the multicast service on a user port

Configuration example for DSL LT (Config#1): configure igmp channel 1/1/5/14:8:35 max-num-group 2 configure igmp channel 1/1/5/14:8:35 fullview-packages 2 configure igmp channel 1/1/5/14:8:35 preview-packages 3 configure igmp channel 1/1/5/14:8:35 max-num-group 2 mcast-svc-context name:OrangeTV

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2198-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2198 — Configure the multicast service on a user port

DLP 2198-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2199 — Configure QoS on the SHub Purpose This procedure provides the steps to configure QoS on the SHub.

Note — For more information about QoS and the configuration of QoS, refer to TNG 2101.

Prerequisites The following prerequisite must be fulfilled before QoS on the SHub can be configured:

•

The egress port must have been added to the VLAN; see DLP 2128.

Procedure Proceed as follows to configure QoS on the SHub: 1

Configure the queues on the SHub ports with the following command: configure qos shub queue-config nt:sfp: | nt:xfp: | (no) queue0-weight (no) queue1-weight (no) rx-pause (no) egress-rate (no) dscp2p-enable

2

Configure the traffic classes on the SHub with the following command: configure qos shub tc-map-dot1p (tc-priority) traffic-class

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2199-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2199 — Configure QoS on the SHub

3

Configure the mapping of the DSCP value to the 802.1p value with the following command: configure qos shub dscp-map-dot1p (dscp-index) dot1p-value

4

Configure the ingress policing parameters on SHub port with the following command: configure qos shub meter (index) (no) name max-ingress-rate burst-size

5

Configure the various flows to be policed with the following command: configure qos shub flow (index) (no) name (no) (type)

6

Configure the policing association with the following command: configure qos shub policer nt:sfp: | nt:xfp: | flow meter

7

STOP. This procedure is complete.

Configuration example (Config#1): configure qos shub queue-config 3 queue0-weight 4 queue1-weight 6 egress-rate 800 configure qos shub tc-map-dot1p 2 traffic-class 1 configure qos shub dscp-map-dot1p 13 dot1p-value 2 configure qos shub meter 32 name QoSShubMeter32 max-ingress-rate 8192 burst-size 4 configure qos shub flow 22 name VLANFLow vlan:300 configure qos shub policer 3 flow 22 meter 32

DLP 2199-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2200 — Configure Spanning Tree on the SHub Purpose The Multiple Spanning Tree Protocol (MSTP), which uses RSTP for rapid convergence, enables VLANs to be grouped into a spanning-tree instance, with each instance having a spanning-tree topology independent of other spanning-tree instances. This architecture provides multiple forwarding paths for data traffic, enables load balancing, and reduces the number of spanning-tree instances required to support a large number of VLANs.

Prerequisite The following prerequisites must be fulfilled before MSTP can be configured:

• •

All VLANs to be protected in an MSTP instance must be created in the SHub and must be associated to the network ports on which MSTP will be enabled The port-type of the network port must be different from unused. This can be verified with the command show interface shub port and can, if necessary, be changed as follows: • Set the port type to no-type with the command: configure interface shub port (network-port) no port-type

•

Change the port type with the command: configure interface shub port (network-port) port-type

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2200-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2200 — Configure Spanning Tree on the SHub

Procedure Proceed as follows to configure MSTP: 1

Configure the general MSTP parameters with the following command: configure mstp general (no) disable-stp (no) priority (no) max-age (no) hello-time (no) forward-delay (no) version stp-compatible | rstp | mstp (no) tx-hold-count (no) path-cost-type 16-bit | 32-bit (no) max-hop-count region-name (no) region-version (no) config-id-sel

Note 1 — The configuration of the parameters applies for the whole bridge. Note 2 — This configuration applies to the SHub. Note 3 — When configuring RSTP, this command has to be split. Refer to the configuration example for RSTP at the end of this procedure. 2

Configure the MSTP parameters for a specific MSTP instance with the following command: configure mstp instance (instance) (no) priority

3

Map/unmap the VLAN on the MSTP instance with the following command: configure mstp instance (instance) (no) associate-vlan (vlan)

Note 1 — The VLAN can be associated with the MSTP instance without being configured first. Note 2 — One or more VLANs can be associated to an instance, but one VLAN can not be assigned to different instances.

DLP 2200-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2200 — Configure Spanning Tree on the SHub

4

Configure the port parameters for the Common Instance with the following command: configure mstp port (port) (no) priority (no) disable-stp path-cost (no) edge-port (no) admin-p2p (no) hello-time

Note — By default MSTP is enabled on the network and outband ports.

5

Configure the MSTP parameters for a specific port-instance configuration with the following command: configure mstp port-instance (network-port) instance (no) priority (no) disable-stp path-cost

6

Manage MSTP related to a port (that is, clear the list of detected protocols) with the following command: admin mstp port (network-port) clear-protocols

7

View the MSTP operational information: a

View all the common spanning tree instances for the whole bridge with the following command: show mstp bridge

b

View the parameters of a multiple spanning tree instance with the following command: show mstp instance (instance)

c

View the MSTP network port information with the following command: show mstp network-port (port)

d

View all the MSTP port instances with the following command: show mstp port-instance (network-port) instance (instance)

8

STOP. This procedure is complete.

Configuration example (Config#1):

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2200-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2200 — Configure Spanning Tree on the SHub

In MSTP mode: configure mstp general priority 61440 max-age 1000 path-cost-type 32-bit version mstp region-name region1 region-version 1 config-id-sel 1 forward-delay 2000 configure mstp instance 1 configure mstp instance 1 associate-vlan 100 configure interface shub port 2 no port-type configure interface shub port 2 port-type network admin-status up configure vlan shub id 100 egress-port network:2 configure mstp port 2 hello-time 100 admin-p2p force-true no disable-stp priority 48 configure mstp port-instance 2 instance 1 priority 32 no disable-stp path-cost 40000 admin mstp port 2 clear-protocols

In RSTP mode: configure mstp no instance 1 configure mstp general version rstp configure mstp general max-age 2100 configure mstp general hello-time 500 forward-delay 2500 no disable-stp priority 4096 path-cost-type 32-bit configure mstp port 2 admin-p2p force-true no disable-stp priority 48

DLP 2200-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2204 — Configure an unnumbered IP interface on the SHub Purpose This procedure provides the steps to configure an unnumbered IP interface on the SHub.

Note — An unnumbered interface can only be configured for the external management VLAN 4093.

Prerequisites The following prerequisite must be fulfilled before an unnumbered IP interface can be configured:

•

The system must run in single IP address mode

Procedure Proceed as follows to configure the unnumbered IP interface: 1

Configure a layer2 terminated VLAN on the network port of the Shub with the following command: configure vlan shub id (vlan-id) mode layer2-term-nwport

2

Configure a VLAN on the SHub with the following command: configure interface shub vlan-id (vlan-id)

3

Configure an IP interface on the VLAN with the following command: configure interface shub ip (vlan-id)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2204-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2204 — Configure an unnumbered IP interface on the SHub

4

Configure a VLAN on the SHub with as egress port the SHub port configured in: configure interface shub ip (vlan-id) ip-addr / (no) local-arp-proxy

5

Set the administrative status of the VLAN to “up” with the following command: configure interface shub vlan-id (vlan-id) admin-status up

6

Configure a management VLAN on the SHub with the following command: configure interface shub vlan-id 4093

7

Configure an unnumbered interface on the management VLAN with the following command: configure interface shub ip 4093

8

Associate the numbered interface with the management VLAN with the following command: configure interface shub ip 4093 unnumbered-as (vlan-id)

Note — “vlan-id” is the ID of the VLAN created in step 2.

9

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan shub id 600 mode layer2-term-nwport configure interface shub vlan-id 600 configure interface shub ip 600 configure interface shub ip 600 ip-addr 13.13.13.1/24 configure interface shub vlan-id 600 admin-status up configure interface shub vlan-id 4093 configure interface shub ip 4093 configure interface shub ip 4093 unnumbered-as 600

DLP 2204-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2209 — Configure vMAC Purpose The concept of virtual MAC (vMAC) replaces the subscriber's MAC address by a MAC address defined by the operator. Enabling vMAC allows improving layer 2 forwarding models in the following two areas:

•

•

Security: Translating the subscriber's MAC address by an operator-defined MAC address ensures by definition the uniqueness of the MAC address across the whole access network, automatically alleviating all issues related with duplicate MAC addresses. Scalability: By guaranteeing that a MAC address is unique across the whole access network, an operator can now choose to connect multiple DSLAMs to the edge router through the same VLAN. By doing so the operator increases the amount of subscribers sharing the same subnet and consequently, improves the pooling effect when allocating IP addresses.

vMAC can be configured on:

• • •

a C-VLAN an S+C-VLAN an iBridge VLAN

This procedure provides the steps to configure vMAC.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2209-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2209 — Configure vMAC

Prerequisite The following prerequisite must be fullfilled before VMAC can be configured:

•

A VLAN must have been created, see DLP 1117, DLP 1119 or DLP 1120.

Note — vMAC is not operational on bridge ports which have MAClearning disabled. To enable MAC learning on a bridge port, use the command: configure bridge port (port) no mac-learn-off

Procedure Proceed as follows to configure vMAC on a VLAN: 1

Configure a unique DSLAM ID for the node with the following command: configure vlan vmac-address-format host-id

Note — The DSLAM ID must be programmed by the operator. It is the responsibility of the operator to ensure unique DSLAM IDs are assigned; otherwise duplicate vMAC addresses may be generated by different DSLAMs. 2

Reset the system after the DSLAM ID has been configured. A database save on the SHub should be done first. Use the following commands: admin software-mngt shub database save admin equipment reboot-isam

3

Enable/disable vMAC translation on a VLAN and configure the vMAC address downstream blocking option with the following command: configure vlan id (vlanid) (no) vmac-translation (no) vmac-dnstr-filter

4

When DHCP is enabled, DHCP option 61 contains the subscriber MAC address. It is possible to configure vMAC so the subscriber MAC address in DHCP Option 61 is unaffected by vMAC or instead is translated into a vMAC address. For this, use the following command: configure vlan id (vlanid) (no) vmac-not-in-opt61

5

You can view the vMAC translation fdb table to see vMAC/user MAC translation with the following command: show vlan vmac-bridge-port-fdb (port) [vlan-id ] [mac ]

6

DLP 2209-2

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2209 — Configure vMAC

Configuration example (Config#1): This example assumes that VMAC learning has been enabled on port 1/1/5/12:8:35 configure bridge port 1/1/5/12:8:35 vlan-id 200 configure vlan vmac-address-format host-id 5 admin software-mngt shub database save admin equipment reboot-isam with-self-test configure vlan id 200 vmac-translation vmac-dnstr-filter show vlan vmac-bridge-port-fdb 1/1/5/12:8:35 vlan-id 200

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2209-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2209 — Configure vMAC

DLP 2209-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2210 — View the status of various system parameters Purpose This document lists the different commands that can be used to view the status of various system parameters:

• • •

system clock memory usage on the NT CPU load on the NT

Procedure Use the following commands to view different system parameters: 1

View the status of the system clock (actual priority, clock status, and clock selection) with the following command: show system clock-mgmt

2

View the memory usage on the NT (size of total memory, size of memory actually in use, percentage of memory in use) with the following command: show system memory-usage (slot)

3

View the CPU load on the NT (start time of monitoring, average load, current condition of monitoring activity) with the following command: show system cpu-load (slot)

4

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2210-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2210 — View the status of various system parameters

Configuration example (Config#1): show system clock-mgmt show system memory-usage nt-a show system cpu-load nt-a

DLP 2210-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2211 — Configure SFP uplink ports Purpose This procedure provides the steps to configure SFP uplink ports on:

• • •

an ERAM-A Remote Aggregator a NCNC-B, NCNC-C, NCNC-D or NCNC-E board installed in a 7330 FD ISAM shelf an NRNT-A board installed in a 7356 FD ISAM FTTB shelf

Prerequisite The following prerequisite must be fulfilled before the SFP ports can be configured:

•

The NCNC-x board must be planned; see DLP 2111.

General You connect a network link to an SFP uplink port. The SFP uplink port can be a dedicated SFP uplink port or a configurable port configured as an uplink port. For an overview of the port assignments on the faceplate of the NCNC-x boards, and ERAM-A Remote Aggregator, see Table DLP 2211-1. Table DLP 2211-1: Faceplate numbers for SFP uplink ports Unit

ERAM-A Remote Aggregator NCNC-B NCNC-C

Faceplate numbers for Configurable ports

Dedicated uplink ports

1 to 8 (1)

—

2 to 7

(1)

—

2 to 7

(1)

—

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2211-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2211 — Configure SFP uplink ports

Unit

Faceplate numbers for Configurable ports

Dedicated uplink ports

NCNC-D

2 to 7 (1)

—

NCNC-E

2 to 7

(1)

14 and 15

3 to 6

(1)

1 and 2(2)

NRNT-A (2 of 2)

Notes (1) All ports configured as uplink ports must be contiguous starting from the lowest SFP port number. For example, SFP ports 3 and 4 on an NCNC-B cannot be configured as uplink ports unless port 2 is configured as an uplink port. (2)

These ports can work in 1GE or 2.5GE mode

Procedure Proceed as follows to configure a configurable SFP port as an uplink port: 1

Configure the SFP port as an uplink port: configure equipment external-link-host (faceplate number) (no) direction

2

You can verify the link direction of the configurable ports with the following command: info configure equipment external-link-host (faceplate number)

3

If you are configuring an SFP port on an ERAM-A Remote Aggregator or an NCNC-x card, perform a system reset (with or without self-test) to allow the configuration of the SFP link direction (uplink) to take effect. In a non-redundant system, you can perform an NT reset (with or without self-test) instead of system reset (an NT reset takes less time than a system reset). a

Perform a system reset in a redundant or in a non-redundant system with the following command: admin equipment reboot-isam

b

Perform an NT reset in a non-redundant system with the following command: admin equipment slot nt-a reboot

DLP 2211-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2211 — Configure SFP uplink ports

4

You can troubleshoot a problem with a network link with the following command: show equipment diagnostics sfp [position] detail

• • •

5

If an SFP shows a tx-fault, it must be replaced. If an SFP shows a tx-power value outside the normal range (given in the SFP Unit Data Sheet), it must be replaced. If an SFP shows an rx-power value outside the normal range (given in the SFP Unit Data Sheet), or shows LOS, check the tx-power of the companion SFP. If the tx-power of the companion SFP is in the normal range, the problem may be with the fiber.

STOP. This procedure is complete.

Configuration example for a NCNC-C board (Config#1): configure interface shub port 6 port-type user admin-status up mc-flooding configure equipment external-link-host 6 direction remote-lt info configure equipment external-link-host 6 admin equipment reboot-isam without-self-test show equipment diagnostics sfp iont:1/1/6 detail

Configuration example for an ERAM-A Remote Aggregator (Config#1): configure equipment external-link-host nt:sfp:6 direction network info configure equipment external-link-host nt:sfp:6 admin equipment reboot-isam without-self-test show equipment diagnostics sfp nt:sfp:6 detail

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2211-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2211 — Configure SFP uplink ports

DLP 2211-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2213 — Enable OAM counters Purpose This procedure provides the steps to enable, view and clear the OAM counters for:

• •

ARP relay DHCP relay

Note — For more information on the individual counters, see TNG 2109.

Prerequisite The following prerequisites must be fulfilled before ARP relay can be configured:

• • • • •

The LT must be planned; see DLP 2111. The xDSL profiles must have been created; see DLP 1129. An VLAN must have been created in enhanced iBridge mode: • for creation of a cross-connect VLAN; see NTP 2104 • for creation of an iBridge VLAN; see NTP 2105 An xDSL user must have been created; see DLP 1124. Configure static MAC addresses; see DLP 2180.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2213-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2213 — Enable OAM counters

Procedure Use the following procedure to enable, view and clear the OAM counters: 1

The following commands can be used to manage the ARP relay counters: i

For each created user interface, enable the detailed counters for ARP relay with the following command: configure arp-relay statistics (vlan-port)

ii

reset the ARP counters of a particular VRF in the Shub. admin ip shub arp-stats (vrf-id) clear-statistics

iii

enable or disable ARP detailed counters on a given user port: configure ip vrf (index) user-itf port (port-interface) [no] arp-proxy-stats

iv

view the summary and detailed counters at any point in time: show arp-relay-stats (user-port) vlan (subscr-vlan) [{summary | extensive}]

v

clear the summary and detailed counters at any point in time: admin ip arp-proxy-stats (user-port) clear-statistics

vi

reset the ARP relay statistics counters: admin arp-relay-stats (vlan-port) clear-statistics

2

The following commands can be used to manage the DHCP relay counters: i

Allows the operator to clear the VRF counters at any point in time: admin dhcp-relay shub vrf-agent-stats (vrf-id) (clear-statistics)

ii

enable or disable DHCP detailed counters on a given user port: configure dhcp-relay [no] port-stats (port-interface)

iii

clear the summary and detailed counters on a given user port at any point of time: admin dhcp-relay port-stats (user-port) (clear-statistics)

3

STOP. This procedure is complete.

Configuration example (Config#1): This example assumes that vlan-port 1/1/5/12:8:35:299 has been

DLP 2213-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2213 — Enable OAM counters

created. configure arp-relay statistics vlan-port:1/1/5/12:8:35:299 show arp-relay-stats 1/1/5/12:8:35 vlan show arp-relay-stats 1/1/5/12:8:35 vlan 299 summary admin arp-relay-stats vlan-port:1/1/5/12:8:35:299 clear-statistics

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

2213-3

DLP 2213 — Enable OAM counters

DLP 2213-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2214 — Configure connectivity fault management Purpose This DLP provides the steps to configure CFM on an NE and retrieve CFM data on configured MPs.

General CFM is configured on an NE as part of a network-wide implementation of CFM on the access aggregation network. To support CFM functionality, network operators must configure maintenance points (MPs) on selected bridge ports on the network. MPs are used to send and receive CFM messages over network links. MPs are organized into maintenance associations (MAs) and maintenance domains (MDs) on a network. See the CLI Command Guide for FD 24Gbps NT document for more information on CFM elements. To configure an NE to support CFM within a VLAN, you must configure at least one MD, and you must configure an MA for that VLAN on the NE. Then you can choose whether to terminate the CFM flow at the level identified in the MD, or whether the NE will act as an intermediate node on the CFM flow that extends between the CPE and another node centrally in the network. In the first case, you have to create MEPs. In the second case, the MIPs are generated automatically by enabling MHF creation within the MA. When CFM is configured, the NE can process downstream CFM messages sent from the BNG or upstream messages from the CPE. CFM tests cannot be initiated from the NE.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2214-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2214 — Configure connectivity fault management

Conditions The following conditions apply:

• • • • • • • •

CFM frames are subject to the rules of the Ethernet protocol filter Deleting a bridge port to VLAN association automatically deletes all the MEPs configured on that bridge port for the VLAN MAs can only be associated with one VLAN on the NE Non-VLAN-aware MAs are not supported (access link level, BBF TR-101, is not supported) Only one MEP can be configured per bridge port in an MA within an MD level MEPs can only be configured on static bridge port to VLAN associations MEPs are not supported on SHub ports Configuration of an MA with MA index = 1 and the MD index = 1 is not supported (reserved for future use)

Prerequisites The following prerequisites must be fulfilled:

• • • • • • • •

CFM must be supported on the access aggregation network For communication with CPEs, the CPEs must support CFM. A L2 forwarder must have been configured. For example, for C-VLAN croos-connect; see DLP 1117. VLAN ports must be configured and linked to the L2 forwarder; see DLP 1124. The LT units must be planned; see DLP 2111. The LT units must support CFM. xDSL profiles must be created; see DLP 1129. Configuration of the VLAN flag “broadcast-frames” must be enabled (it is disabled by default); see DLP 1187. If configuration of this flag is disabled, CFM multicast messages will be dropped. The vMAC host ID must have been configured; see DLP 2209.

Procedure Use this procedure to configure CFM on an NE. 1

Create an MD with the following command: configure cfm domain (domain-index) name level

Note 1 — MDs cannot be modified. They can only be created or deleted. Note 2 — When you delete an MD, all of the elements created in the domain, such as MAs and MPs, are also deleted.

DLP 2214-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2214 — Configure connectivity fault management

2

Create or modify an MA with the following command: configure cfm domain (domain-index) association (association-index) vlan (no) mhf-creation

Note 1 — The mhf-creation parameter can only be modified after the MA is created. Note 2 — When you delete an MA, all MP elements created in the association are also deleted. 3

Configure an MEP within an MA with the following command: configure cfm domain (domain-index) association (association-index) (no) mep (mepid) location

Note 1 — MEPs cannot be modified. They can only be created or deleted. Note 2 — MIPs are not configured individually, as they are automatically enabled or disabled for every bridge port of an MA when the MA is created; see step 2. 4

You can view the MAC address of the MPs (MEP and MIP) with the following command: show cfm stack (location) vlan level direction

5

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan vmac-address-format host-id 2 configure cfm domain 1 name string:system1.com level 1 configure cfm domain 1 association 2 vlan 200 mhf-creation mhf-default bridgeport none configure cfm domain 1 association 2 mep 1 location user:1/1/5/12:8:35

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2214-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2214 — Configure connectivity fault management

DLP 2214-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO Purpose This document provides the steps to configure the Voice cluster.

Forwarding deployment models ISAM-Voice supports the Switched and the Routed Voice forwarding model. Either of these models can be configured according to the requirement of the customer.

•

• •

When the Routed Voice forwarding model is selected, the NE must be configured as a router device, meaning that the Open Shortest Path First (OSPF)/RIP Routing Protocol must be enabled on the NE; see DLP 2107/DLP 2108. The Voice configuration will take care of the SHub being the next hop for upstream packet forwarding. The Routed Voice forwarding model is supported for the Hub and remote node only. When the Switched Voice forwarding model is selected, the NE must be configured as a L2 switching device. The Voice configuration will take care of the Edge Router being the next hop for upstream packet forwarding

Termination ID A subscriber is a logical entity managed by the MG that sources and/or sinks media and/or control streams. Subscribers have unique identities, called "TerminationIDs" assigned by the MG at the time of their creation. The ISAM Voice allows to make use of four different formats for the "TerminationID":

• • •

The LEGACY FLAT termination ID: Typical Format: "Prefix" The IMPROVED FLAT termination ID: Typical Format: 'prefix' The LEGACY HIERARCHICAL termination ID: Typical format: "Prefix/Dslam_Id/rack/shelf/slot/port(/channel"

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

•

The IMPROVED HIERARCHICAL termination ID: Typical format: "Prefix/Dslam_Id/rackXXXXX/shelfXXXXX/slotXXXXX/portXXXXX/channel"

In case the customer decides to make use of the FLAT termination ID format, then such termination id is to be configured for each of the terminations. The termination-id configured with the Voice Megaco Equipment Termination command is used as the H.248 termination ID. The FLAT termination ID can be provisioned in 2 different ways:

• •

By initiating a single "create" command per termination and provisioning the value for the Flat Termination ID. By initiating a batch "create" command for a series of terminations (typically within the limits of a voice LT board). In this case, the operator doesn't provision a value for the Flat termination ID parameter. The system autonomously creates the terminations for a voice LT board and assigns autonomously the value of the Flat Termination ID, starting from 1 or previously successfully completed "create" command. and increment it by 1 for every subsequent termination being created.

In case the customer decides to make use of the hierarchical-termination-id format, then the hierarchical termination syntax is to be configured once and the system will autonomously create the appropriate H.248 termination ID for each of the terminations. However, in addition, also the flat termination id is to be configured. For POTS termination, the flat termination-id configured with the Voice Megaco Equipment Termination command is then used for internal ISAM Voice purposes only. For ISDN, the flat termination ID will be used as integer ISDN IID (Interface Identifier).

• • •

The termination ID must be unique at system level. This rule applies to both POTS users and ISDN users, that is, if a termination ID has been used by a POTS user, the same termination ID cannot be used anymore for an ISDN user. If a Voice Megaco Equipment Termination command contains a termination ID which is already in use, the system will reject this command. If the operator does not enter a value for the termination-id attribute ID in the Voice Megaco Equipment Termination command and the value of the termination-id attribute set in the last but one Voice Megaco Equipment Termination command plus 1 is already in use, the system will reject this command.

Legacy Flat Termination ID

• • • • • •

DLP 2216-2

Consists of a prefix and a termination ID. The format is 'prefix'. Prefix: the prefix can be configured as uppercase or lower case character string with a maximum length of 10 characters. Maximum length of the termination ID digit part is five numeric digits. The configured format defines the MINIMUM length to be generated for the termination ID. However, it does not limit the maximum value of the termination ID itself. Examples: AL0, AL1, AL54, AL4, AL8, AL55 The termination ID value range can start from value "0" or from value "1" (The start value of the value range cannot be derived from the format definition; it is received through the provisioned termination ID value.)

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

• •

POTS: a flat value in the rage [0…32767] ISDN BRI: a flat value in the range [0…8175]

Improved Flat Termination ID

• • • • • • • • •

Consists of a prefix and a termination ID. The format is 'prefix'. Prefix: the prefix can be configured as uppercase or lower case character string with a maximum length of 10 characters. Maximum length of the termination ID is five numeric digits. The configured format defines the MINIMUM length to be generated for the termination ID (might require leading zeroes). However, it does not limit the maximum value of the termination ID itself. The termination ID can be defined as fixed length or variable length termination ID. Fixed length termination ID may imply the insertion of leading zeroes Examples: AL0, AL1, AL54, AL004, AL0008, AL00055 The termination ID value range can start from value "0" or from value "1" (The start value of the value range cannot be derived from the format definition; it is receivedthrough the provisioned termination ID value.) POTS: a flat value in the rage [0…32767] ISDN BRI: a flat value in the range [0…8175]

Legacy Hierarchical Termination ID

• • • • • • •

•

Typical format: "Prefix/Dslam_Id/rack/shelf/slot/port(/channel" Maximum length of the full hierarchical termination ID string equals 72 bytes. The keywords must appear in a pre-defined order: Dslam_Id, rack, shelf, slot, port, channel. The delimiter is mandatory between the pre-defined keywords while optional between the prefix and the subsequent keyword. The delimiter character is fixed to "/". The delimiter character is copied to the generated termination ID. Key-words: Dslam_Id (optional), rack (optional), shelf (mandatory), slot (mandatory), port (mandatory) and channel (mandatory for ISDN-BRI only). • Dslam_id: integer (1..255) • Rack: char (1); value range '1' - '7' • Shelf: char (2); value range ' 01' - '04' • Slot: char (2); The applicable value range will depend on the configured Slot ID numbering scheme • Port: char(3); value range '001' - '072' • Channel: char (2); value range '00' - '99'. Prefix: char (8), optional delimiter not included.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

Improved Hierarchical termination Id.

• • • • • • • • • • • • • • •

Typical format: "Prefix/Dslam_Id/rackXXXXX/shelfXXXXX/slotXXXXX/portXXXXX/channel" All keywords : leading zeroes are to be included where needed. Maximum length of the full hierarchical termination ID string equals 128 bytes. Key-words: Dslam_Id (optional), rack (optional), shelf (mandatory), slot (mandatory), port (mandatory) and channel (mandatory for ISDN-BRI only). The sequence of the key-words as shown in the typical format string must be respected. A key-word can only occur once in the hierarchical termination ID character string. Key-word delimiter is optional. "/" is defined as the default delimiter Delimiter can be any valid character or character string not overlapping with the start character (string) of any of the key-words. The delimiter is copied to the generated termination ID. Each key-word can be followed by a number of numeric digits with the maximum number of digits = 5. The number of digits and the value of the digits configured in the format string define the MINIMUM number of digits to be generated (might require leading zeroes) and the value to start from, "0" or "1". The value following the key-word can start from value "0" or from value "1". Wildcard (*) is supported. The real value of the hierarchical termination id will autonomously be generated by the system based on the configured hierarchical termination id format string. Examples: • (ALshelf001/slot001port00000 whereby the shelf value range shall start from value "1" with max value 999, the slot value range shall start from value "1" with max value 999, while the port value range shall start from value "0" with max value 99999. • AL/Dslam_Id/shelf000slot000port00000 whereby the shelf value range shall start from value "0" with max value 999, the slot value range shall start from value "0" with max value 999, the port value range shall start from value "0" with max value 99999.

Message Identifier (MID) The Message Identifier (MID) being present in H.248 signaling packets can be provisioned as:

• • •

The Media Gateway IP Address, The Media Gateway FQDN The Media Gateway Device Name

Should the Media Gateway FQDN or IP address being provisioned as MID then also the Port number is to be configured. The provisioning of the Media Gateway FQDN only intends this FQDN to be used as MID in H.248 messages. It is not at all used as a trigger to perform DNS look-up for retrieving the media Gateway IP address. The latter IP address is still to be provisioned too. DLP 2216-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Concrete: The Message Identifier (MID) of a message is set to a provisioned name of the entity transmitting the message. The ISAM-Voice allows to provision the MID in accordance to the following provided options:

• • • • •

"ipv4": the media Gateway IP Address is used as the MG MID. "ipv4-port": the media Gateway IP Address together with the media Gateway UDP Port is used as the MG mid. "domain-name": the media Gateway Fully Qualified Domain Name (FQDN) is used as the MG MID. "domain-name-port": the media Gateway FQDN together with the media Gateway UDP Port is used as the MG MID. "device-name": the media Gateway Name is used as the MG MID.

Prerequisite The following boards must have been planned:

•

•

•

For the Hub node: • The Voice server board (NVPS-A) must be planned; see DLP 2111. • The Voice POTS LT (NPOT-x) and the corresponding applique (PSPS-F/NCTA-A) must be planned; see DLP 2111. • The Voice ISDN LT board (NBAT-x) and the corresponding applique (PSUS-A/NCTA-A) must be planned; see DLP 2111. For a subtending node: • The Voice server board (NVPS-A) must be planned; see DLP 2111 (optional). • The Voice POTS LT (NPOT-x) and the corresponding applique (PSPS-F/NCTA-A) must be planned; see DLP 2111. • The Voice ISDN LT board (NBAT-x) and the corresponding applique (PSUS-A/NCTA-A) must be planned; see DLP 2111. For a remote node: • The Voice POTS LT (NPOT-x) and the corresponding applique (PSPS-F/NCTA-A) must be planned; see DLP 2111. • The Voice ISDN LT board (NBAT-x) and the corresponding applique (PSUS-A/NCTA-A) must be planned; see DLP 2111.

The following prerequisites must be fulfilled with regard to the routed / switched forwarding architecture:

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

Switched Forwarding architecture

•

•

•

DLP 2216-6

For the Hub node: • A signaling VLAN in mode residential-bridge must have been created at the SHub side; see DLP 1120. • A voice VLAN in mode Voice-Vlan must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to the VLANs created at the SHub side; see DLP 2121. • ASAM ports of the LT boards / NVPS boards / subtending links must have been added to the Voice VLAN created at the SHub side; see DLP 2121. • ASAM ports of the NVPS boards must have been added to the signaling VLAN created at the SHub side; see DLP 2121. • Both the signalling and the voice VLAN created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the voice VLAN at the NVPS. For a subtending node (no NVPS board planned): • A voice VLAN in mode Voice-Vlan must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to the voice VLAN created at the SHub side; see DLP 2121. • ASAM ports of the LT boards / subtending links must have been added to the voice VLAN created at the SHub side; see DLP 2121. • The voice VLAN created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the voice VLAN at the SHub side. For a remote node: • A voice VLAN in mode Voice-Vlan must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to the voice VLAN created at the SHub side; see DLP 2121. • ASAM ports of the LT boards / subtending links must have been added to the voice VLAN created at the SHub side; see DLP 2121. • The voice VLAN created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the voice VLAN at the SHub side.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Routed Forwarding architecture

•

•

For the Hub node: • A signaling VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A voice VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A signalling VLAN in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_1 in mode Voice-Vlan must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_2 in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • Network interfaces must have been added to the signalling VLAN and the voice VLAN created at the SHub VRF network side; see DLP 2121. • ASAM ports of the LT boards and NVPS boards must have been added to the Voice VLAN_1 created at the SHub VRF user side; see DLP 2121. • ASAM ports of the SUBTENDING links must have been added to the Voice VLAN_2 created at the SHub VRF user side; see DLP 2121. • ASAM ports of the NVPS boards must have been added to the signaling VLAN created at the SHub VRF user side; see DLP 2121. • All VLANs created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the signaling VLAN at the SHub VRF network side. • A numbered IP interface must have been created on top of the voice VLAN at the SHub VRF network side. • A numbered IP interface must have been created on top of the signaling VLAN at the SHub VRF user side. • A numbered IP interface must have been created on top of the voice VLAN_1 at the SHub VRF user side. • A numbered IP interface must have been created on top of the voice VLAN_2 at the SHub VRF user side. For a subtending node: A subtending node still behaves as a switching device. See “Switched Forwarding architecture”.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

•

For a remote node: • A voice VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A voice VLAN_1 in mode Voice-Vlan must have been created at the SHub VRF user side; see DLP 1120. • A voice VLAN_2 in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • Network interfaces must have been added to the voice VLAN at the SHub VRF network side; see DLP 2121. • ASAM ports of the LT boards must have been added to the Voice VLAN_1 created at the SHub VRF user side; see DLP 2121. • ASAM ports of the SUBTENDING links must have been added to the Voice VLAN_2 created at the SHub VRF user side; see DLP 2121. • All VLANs created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the voice VLAN at the SHub VRF network side. • A numbered IP interface must have been created on top of the voice VLAN_1 at the SHub VRF user side. • A numbered IP interface must have been created on top of the voice VLAN_2 at the SHub VRF user side.

Note — The starting point of the above prerequisite requirements is an ISAM-Voice model that makes use of distinct VLANs for voice and signalling traffic. However, aiming at an IP subnet width reduction, ISAM-Voice supports an alternative model that makes use of a single VLAN sharing voice and signalling traffic. In this case, the prerequisite requirements are identical to the ones related to the voice VLAN descried in the above sections for the switched and routed forwarding architecture, and this at all sides, the SHub, the IACM and the NVPS. Aiming at an ultimate reduction of IP address and the IP subnet width, ISAM-Voice supports a last model that makes use of:

• •

DLP 2216-8

A public VLAN sharing voice and signalling traffic, and connecting the NVPS with the voice network together with A private voice VLAN, connecting the NVPS with the Voice LT boards residing at either the Hub and/or the subtending and/or the remote NEs.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Switched Forwarding architecture

•

•

For the Hub node: • A public VLAN in mode Voice-Vlan must have been created at the SHub side; see DLP 1120. • A private voice VLAN in mode Voice-Vlan must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to the public VLAN created at the SHub side; see DLP 2121. • ASAM ports of the LT boards / NVPS boards / Subtending links must have been added to the private Voice VLAN created at the SHub side; see DLP 2121. • ASAM ports of the NVPS boards must have been added to the public VLAN created at the SHub side; see DLP 2121. • Both the public and the private voice VLAN created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the public voice VLAN at the SHub side. • A numbered IP interface must have been created on top of the private voice VLAN at the SHub side. For a subtending node: • A private voice VLAN in mode Voice-Vlan must have been created at the SHub side; see DLP 1120. • Network interfaces must have been added to the private voice VLAN created at the SHub side; see DLP 2121. • ASAM ports of the LT boards must have been added to the private voice VLAN created at the SHub side; see DLP 2121. • The private voice VLAN created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the private voice VLAN at the SHub side.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

Routed Forwarding architecture

•

• •

For the Hub node: • A public VLAN in mode residential-bridge must have been created at the SHub VRF network side; see DLP 1120. • A public VLAN in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • A private voice VLAN_1 in mode Voice-Vlan must have been created at the SHub VRF user side; see DLP 1120. • A private voice VLAN_2 in mode residential-bridge must have been created at the SHub VRF user side; see DLP 1120. • Network interfaces must have been added to the public VLAN created at the SHub VRF network side; see DLP 2121. • ASAM ports of the LT boards must have been added to the private Voice VLAN_1 created at the SHUB VRF user side; see DLP 2121. • ASAM ports of the SUBTENDING links must have been added to the private Voice VLAN_2 created at the SHUB VRF user side; see DLP 2121. • ASAM ports of the NVPS boards must have been added to the public VLAN created at the SHub VRF user side; see DLP 2121. • All VLANs created at the SHub must have been associated with the fast path VRF. • A numbered IP interface must have been created on top of the public VLAN at the SHub VRF network side. • A numbered IP interface must have been created on top of the public VLAN at the SHub VRF user side. • A numbered IP interface must have been created on top of the private voice VLAN_1 at the SHub VRF user side. • A numbered IP interface must have been created on top of the private voice VLAN_2 at the SHub VRF user side. For a subtending node: A subtending node still behaves as a switching device. See “Switched Forwarding architecture”. For a remote node: This third model is irrelevant in the scope of a remote node configured as routed device

DLP 2216-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Procedure All the configuration related to the voice cluster needs to be executed on the Hub node only. Proceed as follows to configure the Voice cluster: 1

Configure the Voice cluster with the following command: configure voice cluster (cluster-id)

Note 1 — The value of the parameter cluster-id can range from 1 to 8. The value of the cluster ID is in direct relation with the position of the NVPS-x board pair in the shelf:

• • • •

Value 1 must be used when the NVPS-x board pair is located in positions LT1 and LT2 Value 2 must be used when the NVPS-x board pair is located in positions LT3 and LT4 ... Value 8 must be used when the NVPS-x board pair is located in positions LT15 and LT16

Note 2 — An NVPS board cannot be planned neither in the NT-B nor in the NTIO slot position. Note 3 — The Voice Server boards of a Voice Server pair must be planned in adjacent slot positions starting with an odd slot position. Note 4 — A single Voice Server board must be planned in an odd slot position. The adjacent slot position can be used to plan a voice LT board.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

2

Configure the Voice Server Addressing properties with the following command: configure voice cluster (cluster-id) ip ivps-ip netmask router-ip vlan-id (no) private-ip (no) private-netmask (no) private-vlan-id

Note 1 — The attributes private-ip, private-netmask and private-vlan-id must only be configured in case of a topology that aims at IP address and IP subnet width reduction. Note 2 — The following restriction applies when modifying the Voice Server addressing properties: A modification of the attributes ivps-ip, netmask, router-ip, vlan-id, private-ip, private-netmask and private-vlan-id is allowed with the following condition: the admin state of the Media Gateway must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked” (a Voice Server board reset is not required.) 3

Configure the ISAM Voice Access Nodes in the Voice cluster with the following command: configure voice cluster (cluster-id) equipment (equip-id) asam-id ip-address (no) nexthop

Note 1 — One xVPS board can manage at most 32 LT boards, so the ID of the equipment is from 1 to 32. Note 2 — The following restriction applies when modifying the ISAM Voice access node properties:

• •

A modification of the attribute ip-address is not allowed. The IP address can only be modified through a delete / re-create of the entry. A modification of the attribute asam-id and nexthop is allowed without condition.

DLP 2216-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

4

Configure the Voice LT boards in the voice cluster with the following command: configure voice cluster (cluster-id) equipment (equip-id) (no) board (board-id) planned-type lanx-port

Note 1 — Board ID (slot) numbering:

•

•

In FD ntb-ntio-supported shelf-mode (non extended-LT mode) the first physical slot LT(1 in FD) must be configured as the first LT (1/1/1),the last physical slot LT(19 in FD) must be configured as the 16th LT (1/1/16). In FD extended LT mode, the slots of NTIO and NTB can be used as LT slots. The physical slot LT10 must be configured as the 17th LT (1/1/17). The physical slot LT11 must be configured as the 18th LT (1/1/18).

Note 2 — The following restriction applies when modifying the Voice LT board properties: A modification of the Voice LT board entry is not allowed. The entry can only be modified through a delete / re-create of the entry. 5

Configure the media gateway with the following command: configure voice cluster (cluster-id) (no) media-gateway (media-gateway-id) (no) name ip-address netmask (no) udp-port (no) router-ip vlan-id (no) mgc-type prim-mgc-ip (no) mgc-id (no) prim-mgc-udp (no) sec-mgc-ip (no sec-mgc-udp (no) tert-mgc-ip (no) tert-mgc-udp (no) mg-mid-type (no) mg-domain-name (no) svcreason-format (no) mg-profile-name (no) admin-status termid-type pstn-term-format isdn-term-format isdn-suffix1 isdn-suffix2 (no) max-transhandling (no) max-network-delay (no) max-retrans

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

red-bat-delay release-delay release-type wt-rls-delay active-heartbeat passive-heartbeat retrans max-waiting-delay prov-rpl-time no signal-dscp signal-pbits rtp-dscp rtp-pbits event-req-id stml-stdsg-evt al-of-evt al-on-evt al-of-strict-evt al-on-strict-evt mg-overload-evt rfc2833-pl-type rfc2833-process dial-start-timer dial-long-timer dial-short-timer min-data-jitter init-data-jitter max-data-jitter ephe-term-prefix ephe-term-min ephe-term-max

Note 1 — The parameters isdn-term-format, isdn-suffix1 and isdn-suffix2 apply to the ISDN BRI service only. Note 2 — The IP address of the Media Gateway must be kept the same as the IP address of the Signaling Gateway.

DLP 2216-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Note 3 — The ISAM Voice supports Media Gateway Controller Redundancy. Up to 3 MGCs can be configured. One of these MGCs might be an ESA MGC intending to support ESA Redundancy. An ESA MGC is to be understood as an MGC that supports a minimum feature set, such that the basic and the emergency call can remain supported in situations of a simultaneous failure of all usual MGCs (primary and secondary). In that respect, it is assumed that the ESA MGC functionality is limited to:

• • •

Basic POTS calls. (ISDN calls and supplementary services are not supported during ESA mode activation.) Establishing calls between user ports controlled by the MG(s) that has(have) a control association with the ESA MGC. Emergency call.

Based on the above, ESA-Redundancy requires the provisioning of at least 2 MGCs with the strict condition that the ESA MGC must be provisioned as the lowest priority MGC. The provisioning of both, Primary + ESA MGC and Primary + Secondary + ESA MGC is allowed. In case of a failure of the Primary (Primary + ESA) or both simultaneously, Primary and Secondary (Primary + Secondary + ESA) MGC, ISAM Voice will make a switch-over to the MGC with the lowest priority potentially allowing for the preservation of stable calls. It is to be noted that the possibility to preserve stable calls during a switch-over depends on the capabilities supported by the MGC. The ISAM Voice, from a perception of being a MG, doesn't have any notion about the capabilities of a MGC being configured as primary, secondary or tertiary MGC. The ISAM-V treats all configured MGCs equally.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

Further on the ISAM Voice assumes that: • The ESA MGC accepts "on-hook" notifications for calls that were established in the course of the control association being established between the MG and the Primary / Secondary MGC but finished in the course of the control association being established between the MG and the ESA MGC. • The ESA MGC is responsible to "subtract" the contexts for calls that were established in the course of the control association being established between the MG and the Primary / Secondary MGC but finished in the course of the control association being established between the MG and the ESA MGC. • The ESA MGC is responsible for the alive monitoring of Primary (and Secondary) MGC when ESA mode being active.

•

•

Whilst the ESA MGC has an active control relationship with the MG, it shall continuously monitor both the primary and the secondary MGC by repeating to send a ServiceChange message with method = "FailOver SVC Forced". Should a reply "ERROR 403 syntax Error" be received from either the Primary or the Secondary MGC, the ESA MGC shall immediately send a ServiceChange message with Method = "HandOff" and [Primary/Secondary MGC] address to the ISAM Voice MG. The capability of the ESA Softswitch to poll only one MGC or multiple MGCs does not have any impact on the ISAM-V in its capacity as MG. This may only influence the time period after which the usual voice service can be resumed.

Control association failure detection and switch-over from Primary/secondary MGC to ESA MGC is identical as for the usual MGC-Redundancy. Note 4 — The following restriction applies when modifying the Media Gateway properties:

• •

•

A modification of the attributes termid-type, pstn-term-format, isdn-term-format, isdn-suffix1, isdn-suffix2 can be done on the condition that no terminations are configured. A modification of the attributes ip-address, netmask, router-ip, vlan-id, max-transhandling, max-network-delay, max-retrans, retrans, dial-start-timer, dial-long-timer, dial-short-timer, ephe-term-prefix, ephe-term-min, ephe-term-max, udp-port, prim-mgc-ip, prim-mgc-udp, sec-mgc-ip, sec-mgc-udp, tert-mgc-ip, tert-mgc-udp, mg-mid-type, mg-domain-name, termid-type, max-waiting-delay, prov-rpl-time is allowed with the following condition : the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”. A modification of the attributes mgc-type, svcreasonformat, mg-profile-name, release-type, red-bat-delay, release-delay, wt-rls-delay, active-heartbeat, passive-heartbeat, signal-dscp, signal-pbits, rtp-dscp, rtp-pbits, event-req-id, stml-stdsg-evt, al-of-evt, al-on-evt, al-of-strict-evt, al-on-strict-evt, mg-overload-evt, RFC2833-pl-type, RFC2833-process, min-data-jitter, init-data-jitter and max-data-jitter is allowed without condition.

DLP 2216-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

6

Configure the Signaling Gateway with the following command: configure voice cluster (cluster-id) (no) signal-gateway (signal-gateway-id) prim-asp-ip prim-sctp-port sec-asp-ip (no) sec-sctp-port tert-asp-ip (no) tert-sctp-port ip-address sgi-user-label sgi-mgi (no) admin-status

Note 1 — This command applies to the ISDN BRI service only. Note 2 — The IP address of the Signaling Gateway is kept the same as the IP address of the Media Gateway. When the operator changes the IP address of the Media Gateway, the system will autonomously change the IP address of the Signalling Gateway to the same. Note 3 — The following restriction applies when modifying the Signaling Gateway properties:

• • •

7

A modification of the attribute gi-mgi is not allowed. The attribute can only be modified through a delete / re-create of the entry. A modification of the attribute ip-address is not allowed (see Note 2). A modification of the attributes prim-asp-ip, prim-sctp-port, sec-asp-ip, sec-sctp-port, tesrt-asp-ip, tert-sctp-port and sgi-user-label is allowed with the following condition: the admin state must be set to “locked” prior to the modification and once the modification been completed, the admin state must be set to “unlocked”.

Configure the Voice termination with the following command: configure voice cluster (cluster-id) equipment (equip-id) (no) termination (port-id) ) (no) type (no) switch-type (no) activate-type termination-id media-gateway-id (no) admin-status (no) line-feed (no) rx-gain (no) tx-gain (no) impedance

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

(no) (no) (no) (no) (no)

rtp-dscp rtp-pbits clip-mode metering-type directory-number

Note 1 — The parameters switch-type and activate-type apply to the ISDN BRI service only. Note 2 — The following policies apply when modifying the Voice Termination configuration:

• • •

8

A modification of the parameters type and media-gateway-id is not allowed. These attributes can only be modified through a delete / re-create of the entry. A modification of the parameters rtp-dscp, rtp-pbits, and clip-mode is allowed without condition A modification of the parameters termination-id, line-feed, , rx-gain, tx-gain, impedance, switch-type, activate-type, metering-type and directory-number requires the admin state to be set to “locked” prior to the modification and afterwards the admin state to be set to “unlocked”.

The Voice MEGACO database can be forcibly saved with the following command: admin voice cluster (cluster-id) database save

Note — Upon MEGACO database modification and if no database save command is entered, the ISAM Voice will autonomously save the modified MEGACO database at periodic time interval (every 10 minutes.) 9

You can view the Voice MEGACO database save progress status with the following command: show voice cluster (cluster-id) database

10

The Voice board communication status can be displayed with the following command: show voice cluster (cluster-id) board (equip-id) (board-id)

11

The Voice MEGACO MGI status can be displayed with the following command: show voice cluster (cluster-id) media-gateway (media-gateway-id)

12

The NVPS signaling port status can be displayed with the following command: show voice cluster (cluster-id) ip

13

The Voice MEGACO SGI status can be displayed with the following command: show voice cluster (cluster-id) signal-gateway (signal-gateway-id)

DLP 2216-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

14

The Voice MEGACO Termination status can be displayed by the following command: show voice cluster (cluster-id) termination (equip-id) (port-id)

15

Manage the Voice MEGACO Termination Service state with the following command: admin voice cluster (cluster-id) equipment (equip-id) port-id lktype

Note 1 — The termination is taken Out Of Service in a forced or graceful way. (This will finally cause the admin state of the termination to be set to “locked”):

•

•

Forced: It indicates that the termination is going Out Of Service immediately. Lock Delay has no effect on the ServiceChangeMethod “Forced”. For this particular termination, the MG sends a Service Change request to the MGC with Method = Forced and Reason code = 905 “termination taken out-of-service” Graceful: It indicates that the termination is going Out Of Service after the Lock Delay. The Service State shall be set to “OutOfService” upon expiry of the Lock Delay or when the termination(s) is removed from an active context (whichever is first) Using a Lock Delay equal to zero or an absent Lock Delay indicates that the termination shall go Out Of Service when it is removed from context through subtraction. For this particular termination, the MG sends a Service Change request to the MGC with Method = Graceful, Reason code = 905 “termination taken out-of-service” and Delay = xx. In case the termination is not involved in an active context, it will immediately enter the Out Of Service state.

Note 2 — To cancel a previously sent (and acknowledged) Graceful Lock on a termination, the admin state of the termination in question shall be changed to “unlocked”. The MG sends a ServiceChange with a ServiceChangeMethod of “Restart” and a ServiceChangeReason of 918 “Cancel Graceful” on the termination in question. The termination shall remain InService. In the event that the termination has already transitioned OutOfService, it shall be returned to service just as it would with any ServiceChange Restart. Note 3 — The termination is brought InService by changing the admin state of the termination in question to the state “unlocked”. The MG sends a ServiceChange with a ServiceChangeMethod of “Restart” and a ServiceChangeReason of 900 “Service Restored” on the termination in question.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

16

Manage the Voice MEGACO Media Gateway lock with the following command: admin voice cluster (cluster-id) media-gateway (media-gateway-id) lktype

Note 1 — The Media Gateway is taken OutOfService in a forced or graceful way. (This will finally cause the admin state of the termination to be set to “locked”):

•

•

Forced: It indicates that the Media Gateway is going OutOfService immediately. The control association is terminated by the MG upon receipt of the command reply from the MGC. Lock Delay has no effect on the ServiceChangeMethod “Forced”. The MG sends a Service Change request, on the Root termination, to the MGC with Method = Forced and Reason code = 905 “termination taken out-of-service” on the Root termination. Graceful: It indicates that the Media Gateway is going OutOfService after the Lock Delay. The control association is terminated at the end of the Lock Delay period. Using a Lock Delay equal to zero or an absent Lock Delay indicates that the MG shall go OutOfService and terminate the control association when the last context is removed through subtraction of its terminations, and that the MGC shall not add new connections. The MG sends a Service Change request, on the Root termination, to the MGC with Method = Graceful, Reason code = 905 “termination taken out-of-service” and Delay = xx.

Note 2 — To cancel a previously sent (and acknowledged) Graceful Lock on a Media Gateway, the admin state of the Media Gateway in question shall be changed to “unlocked”. The MG sends a ServiceChange, on the Root termination, with a ServiceChangeMethod of “Restart” and a ServiceChangeReason of 918 “Cancel Graceful”. The MG shall remain InService, and all terminations previously set OutOfService are returned to service unless otherwise signalled by the MG. In the event that a Cancel Graceful is received after the Delay timer has expired, the MG shall be deemed to have re-registered. Note 3 — The Media Gateway is brought InService by changing the admin state of the Media Gateway to the state “unlocked”. The MG sends a ServiceChange, on the Root termination, with a ServiceChangeMethod of “Restart” and a ServiceChangeReason of 902 “Warm Boot”. 17

STOP. This procedure is complete.

DLP 2216-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Configuration example (Config#2): configure voice cluster 3 configure voice cluster 3 ip ivps-ip 192.168.9.12 netmask 255.255.255.0 router-ip 192.168.9.254 vlan-id 700 configure voice cluster 3 equipment 1 asam-id Voice1 ip-address 192.168.50.39 configure voice cluster 3 equipment 1 board 1/1/6 planned-type npot-a lanx-port 10 Configure the flat mode termination type: configure voice cluster 1 media-gateway 1 name M ip-address 190.168.1.10 netmask 255.255.255.0 router-ip 190.168.1.1 vlan-id 87 prim-mgc-ip 10.0.55.40 admin-status unlocked termid-type flat pstn-term-format AL isdn-term-format BA isdn-suffix1 /B1 isdn-suffix2 /B2 Configure the hierarchy mode termination type: configure voice cluster 1 media-gateway 1 name M ip-address 190.168.1.10 netmask 255.255.255.0 router-ip 190.168.1.1 vlan-id 87 prim-mgc-ip 10.0.55.40 admin-status unlocked termid-type hierarchy pstn-term-format AL/rack/shelf/slot/port isdn-term-format BA/rack/shelf/slot/port/channel isdn-suffix1 /B isdn-suffix2 /B Configure the Improved hierarchy mode termination type: configure voice cluster 1 media-gateway 1 name M ip-address 190.168.1.10 netmask 255.255.255.0 router-ip 190.168.1.1 vlan-id 87 prim-mgc-ip 10.0.55.40 admin-status unlocked termid-type hierarchy pstn-term-format AL/rack001/shelf001/slot001/port001 isdn-term-format BA/rack001/shelf001/slot001/port001/channel isdn-suffix1 /B1 isdn-suffix2 /B2 Or configure voice cluster 1 media-gateway 1 name M ip-address 190.168.1.10 netmask 255.255.255.0 router-ip 190.168.1.1 vlan-id 87 prim-mgc-ip 10.0.55.40 admin-status unlocked termid-type hierarchy pstn-term-format ALrack001shelf001slot001port001 isdn-term-format BArack001shelf001slot001port001channel isdn-suffix1 B1 isdn-suffix2 B2 configure voice cluster 1 signal-gateway 1 sgi-user-label S sgi-mgi 1 ip-address 190.168.1.10 prim-asp-ip 10.0.55.122 prim-sctp-port 9900 admin-status unlocked POTS Termination: configure voice cluster 3 equipment 1 termination 1/1/6/1 type pstn termination-id 1 media-gateway-id 1 admin-status unlock

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

ISDN-BRI Termination: configure voice cluster 3 equipment 1 termination 1/1/6/1 type isdn termination-id 1 media-gateway-id 1 admin-status unlock admin voice cluster 3 database save show voice cluster 3 media-gateway 1 Show voice cluster 3 ip show voice cluster 3 signal-gateway 1 show voice cluster 3 termination show voice cluster 3 board configure voice cluster 3 media-gateway 1 admin-status lock configure voice cluster 3 media-gateway 1 admin-status unlock configure voice cluster 3 equipment 1 termination 1/1/7/1 admin-status lock configure voice cluster 3 equipment 1 termination 1/1/7/1 admin-status unlock

DLP 2216-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2216 — Configure Voice MEGACO

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2216-23 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2216 — Configure Voice MEGACO

DLP 2216-24 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2222 — Create the PCCP group Purpose This procedure provides the steps to create the Path Connectivity Check Protection (PCCP) group.

Prerequisites The following prerequisites must be fulfilled before a PCCP group can be configured:

• •

xSTP must be disabled; see DLP 2200. The network port must be up; see DLP 2175.

Procedure Proceed as follows to create a PCCP group: 1

Enable or disable PCCP in the ISAM with the following command: configure pccp module-status

2

Configure the PCCP group with the following command: configure pccp group (groupid) (no) admin-state ping-interval ping-dest-ipaddr (no) switchover

Note — If the PCCP group feature is disabled during run-time, then the ISAM keeps the current configuration but all the forwarding/discarding states on the ports no longer apply (only the administrative and operational state of the ports apply). The SHub will display a regular bridge behaviour.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2222-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2222 — Create the PCCP group

3

Configure the network PCCP ports with the following command: configure pccp group (groupid) (ports-list (port))

4

Retrieve the PCCP group information with the following command: show pccp group (groupid)

5

Retrieve the PCCP group port information with the following command: show pccp port-entry (ctrl-index)

6

STOP. This procedure is complete.

Configuration example (Config#1): configure mstp general disable-stp configure pccp module-status enable configure pccp group 1 admin-state enable ping-interval 5 ping-dest-ipaddr 10.8.16.1 configure pccp group 1 ports-list network:0 show pccp group 1 show pccp port-entry 0

DLP 2222-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2223 — Configure SHub port mirroring Purpose This procedure provides the steps to configure SHub port mirroring in the system. Mirroring SHub ports is typically used during lab testing. It offers the ability to mirror all traffic from one or more SHub ports onto a single SHub port (the “mirror to” port), which is connected to a traffic analyzing device.

Prerequisite The ports, intended as “mirror-to” port or as “mirrored” port, must be configured; see DLP 1117 step 2.

Procedure Proceed as follows to configure port mirroring: 1

Configure the “mirror-to” port with the following command: configure interface shub mirror to-port

Caution 1 — The “mirror-to” port should not be effectively connected to a network, subtending system or user. The “mirror-to” port is typically connected to specific equipment, such as a traffic analyzer. Caution 2 — When MSTP is enabled, packets are only forwarded on the “mirror-to” port if the corresponding MSTP instance is in the forwarding state on the “mirror-to” port.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2223-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2223 — Configure SHub port mirroring

2

Enable (or disable) the ingress mirroring, or egress mirroring, or both, of traffic forwarded to and from other ports on the interface to the “mirror-to” port with the following command: configure interface shub mirror port lt:// | network: | nt:sfp: | nt:xfp: external (no) ingress (no) egress

Note 1 — The port syntax nt:sfp: or nt:xfp: is used for ERAM-A network ports only. Note 2 — Ingress L3 packets will be mirrored after L3 packet alteration. 3

Enable (or disable) the ingress mirroring, or egress mirroring, or both, of traffic to and from the CPU on the interface to the” mirror-to” port with the following command: configure interface shub mirror port lt:// | network: | nt:sfp: | nt:xfp: internal (no) ingress (no) egress

Note — The port syntax nt:sfp: or nt:xfp: is used for ERAM-A network ports only.

4

The mirroring configuration only becomes effective when it has been enabled with the following command: configure interface shub mirror enable

5

STOP. This procedure is complete.

Configuration example (Config#1): configure interface shub mirror to-port 7 configure interface shub mirror port lt:1/1/5 external ingress egress configure interface shub mirror port lt:1/1/5 internal ingress egress configure interface shub mirror enable

DLP 2223-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2224 — Change shelf mode Purpose This procedure provides the steps to change the shelf mode.

Prerequisite The following prerequisite must be fulfilled before changing the shelf mode:

•

The network port on the NTIO must be “unused”.

Procedure Proceed as follows to change the shelf mode: 1

Check the network port on the NTIO with the following command: show interface shub port

Note — The port must be “unused”. If this is not the case, change the status of the network port with the following command: configure interface shub (network-port) port-type unused

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2224-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2224 — Change shelf mode

2

Use one of the following command to change the shelf mode: a

Change the mode from NTIO_SUPPORTED to NTIO_UNSUPPORTED with the following command: configure equipment shelf (index) mode extended-lt-slots

b

Change the mode from NTIO_UNSUPPORTED to NTIO_SUPPORTED with the following command: configure equipment shelf (index) mode no-extended-lt-slots

3

The system automatically goes into reset after the shelf mode has been changed.

4

STOP. This procedure is complete.

Configuration example (Config#1): configure equipment shelf 1/1 mode extended-lt-slots

DLP 2224-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2230 — Configure a VLAN on the SHub Purpose This procedure provides the steps to configure a VLAN on the SHub. Figure DLP 2230-1: Configure a VLAN on the SHub

DLP

Phy VLAN

Phy

LT

LAG

Phy

NT_SHUB LT ISAM_SHUB

Procedure Proceed as follows: 1

Configure a VLAN on the SHub with the following command: configure vlan id name mode cross-connect | residential-bridge

2

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2230-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2230 — Configure a VLAN on the SHub

Configuration examples (Config#1): configure vlan shub id 300 name "ISP_C_VLAN_300" mode cross-connect configure vlan shub id 400 name "ISP_S_VLAN-400" mode cross-connect configure vlan shub id 500 name "ISP_SC_VLAN-500" mode cross-connect configure vlan shub id 100 name "iBridge-vlan" mode residential-bridge configure vlan shub id 200 name "iBridge-vlan" mode residential-bridge configure vlan shub id 299 name "ISP_C_VLAN_299" mode cross-connect

DLP 2230-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2231 — Manage the ports on the NT Purpose This document describes the procedure to configure the network ports and the LT ports on the SHub. Figure DLP 2231-1: Configure Network Ports and LT Ports on the SHub

DLP Network Ports

LT Ports

Phy LT Phy Phy

NT_SHUB

LT

ISAM_SHUB

Procedure Proceed as follows to configure ports on the SHub: 1

Create and configure an SHub network port with the following command: configure interface shub port (network-port) (no) mode port-type network (no) mc-flooding

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2231-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2231 — Manage the ports on the NT

2

Change the administrative status of the SHub network port with the following command: configure interface shub port (network-port) admin-status auto-up

3

STOP. This procedure is complete.

Configuration examples (Config#1): configure interface shub port 6 port-type network admin-status up configure interface shub port 3 port-type network admin-status up

DLP 2231-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2236 — Configure the enhanced system clock synchronization Purpose The ISAM supports Network Timing Reference to all synchronous interfaces within the system. The system uses its internal clock as a timing source when no external clocks are configured on the system.

Note — For a detailed overview of the NTR support on the ISAM, see the chapter Network timing reference support in ISAM in the System Description for FD 24Gbps NT document. The ISAM supports the configuration of two external NTR clock sources, with an operator assigned priority between them, as eligible references for the internal system NTR clock. This section describes the procedure to configure and monitor external clock sources on the system. Note that the system only supports a single NT in slot NT-A or NT-B. The configuration of the BITS on the NT in slot NT-A corresponds to BITS-A and on the NT of slot NT-B corresponds to BITS-B. This set of sources can be selected from the following options (see Figure DLP 2236-1:

• •

NANT-A: BITS can be supported on slot NT-A, which corresponds to BITS-A, and can be supported on slot NT-B, which corresponds to BITS-B. AGNT-A: support of one BITS reference, connected via the backplane

Note — For NANT-A and AGNT-A, there is no need to configure the BITS configuration.

•

NRNT-A: SyncE must be configured. Only SFP-1 and SFP-2 are possible candidates.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2236-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2236 — Configure the enhanced system clock synchronization Figure DLP 2236-1: Clock sources

For NANT-A:

NT-A active

NT-A stby (loc-clk) BITS-B

BITS-A Loc-Clk For AGNT-A: NT (active) BITS Loc-Clk For NRNT-A:

SyncE-1

NT (active)

SyncE-2 Loc-Clk

For the NRNT-A, the SSMout is supported on external interfaces:

• • •

On SyncE (network) port interfaces On VDSL port interfaces On SHDSL port interfaces

The following factory defaults are assumed by the system:

• •

• • • • •

local clock: the default factory settings assumes no external clock sources are configured and the system uses its internal system clock for system timing. revertive operation of the external NTR clock signal selection, in case an eligible external NTR clock signal of higher quality, or with higher priority as attributed by the operator, becomes available next to the currently applied external NTR clock source. “autoselect” for the BITS mode which corresponds to E1 for ETSI NT or DS1 for ANSI NT. Synchronous Status Message (SSM) support is disabled for all external clock sources SyncE (NRNT-A). SSMout for BITS, SyncE ports and DSL ports: disabled (NRNT-A) SSMout-ceiling parameter: clk-ql-prc (NRNT-A) ntr-ssmout-vlan: 4088 (NRNT-A)

The parameter “Quality Level” can only be configured with a quality value applicable for the selected mode. See Table DLP 2236-1 for ETSI.

DLP 2236-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2236 — Configure the enhanced system clock synchronization Table DLP 2236-1: Hierarchy of quality levels for ETSI QL

Name

Description

Value Name

2

QL-PRC

This synchronization trail transports a timing quality generated by a Primary Reference Clock that is defined in Recommendation G.811.

clk-ql-prc

4

QL-SSU-A

This synchronization trail transports a timing quality generated by Types I or V slave clock that is defined in Recommendation G.812.

clk-ql-ssu-a

8

QL-SSU-B

This synchronization trail transports a timing quality generated by a Type VI slave clock that is defined in Recommendation G.812.

clk-ql-ssu-b

11

QL-SEC

This synchronization trail transports a timing quality generated by a SDH Equipment Clock (SEC) that is defined in Recommendation G.813, Option I.

clk-ql-sec

15

QL-DNU

This signal should not be used for synchronization.

clk-ql-dnu

Remarks 1

SyncE (network) ports cannot be removed form the SyncE SSMout port list. They are always present, and will have SSMout enabled or disabled.

2

DSL ports for SSMout need to be created. Once an entry is created (SSMout is enabled by default), one can put SSMout for an LT port disabled. configure system sync-if-timing ssmout-ltport 1/1/4/1 no ssmout-enable

To remove an entry of the SSMout LTport list configure system sync-if-timing no ssmout-ltport 1/1/4/1

3

SyncE (remote) ports (NTIO) will be automatic configured for SSMout, once the assigned remote LT has one DSL port configured for SSMout. Note that these SSMout messages are VLAN-tagged with the internal reserved VLAN ID (default 4088). The SyncE (remote) ports can also be configured for SSMout by the operator. In this case the SSMout will be send untagged (in parallel to a tagged Vlan SSMout to a remote LT).

Procedure Proceed as follows to configure the network timing reference: 1

Which board a

For NANT-A and AGNT-A, go to step 2

b

For NRNT-A, go to step 4

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2236-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2236 — Configure the enhanced system clock synchronization

2

Configure the BITS interface mode with the following command: configure system sync-if-timing bits e1

Note — The configuration of the bits parameter specifies the type of the BITS interface:

• • • •

AUTOSELECT DS1 E1 2048KHZ

When the configuration is set to the factory default (autoselect), the system automatically selects DS1 for ANSI modules and E1 for ETSI modules. 3

Go to step 16.

4

Configure the system timing clock priority with the following command: configure system sync-if-timing ref-order prio1 configure system sync-if-timing ref-order prio2

Note 1 — The parameter specifies the clock source to be assigned priority #1 (primary) or priority #2 (secondary) which can be one of the following values:

• •

synce-1 synce-2

Note 2 — The clock selection is based on the Quality level of the clock source first, and then the priority configuration - in the event that both clock sources have the same QL. Note 3 — The clock selection of synce-1/2 can be specified in the priority table before the binding to a physical port (see next step), but the clock status will be “no SyncE configuration”. 5

Configure the binding of the Synchronous Ethernet to a physical port with the following command: configure system sync-if-timing synce-1 configure system sync-if-timing synce-2

Note — The parameter specifies the faceplate port to be used as syncE reference. This faceplate port can be one of the following ports:

• • •

DLP 2236-4

nt:sfp:1 nt:sfp:2 none

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2236 — Configure the enhanced system clock synchronization

6

Configure the reception of Synchronous Status Messages (SSM) for the synchronous Ethernet reference with the following command: configure system sync-if-timing ssm (no) ssmenable]

Note — The parameter specifies the clock source to be assigned priority #1 (primary) or priority #2 (secondary) which can be one of the following values:

• • 7

synce-1 synce-2

Configure the manual setting of the Quality Level (QL) of external NTR clock sources without support for SSM signalling (either not supported, or disabled) with the following command: configure system sync-if-timing ssm (no) default-ql ]

Note 1 — The parameter specifies the clock source which can be one of the following values:

• •

synce-1 synce-2

Note 2 — The parameter specifies the manual setting of the clock source in the range [0… 15], chosen in compliance with the applicable regional options for the standards ITU-T G.781, G.8264. The default values for are equal to clk-ql-prc for ETSI 8

Configure the target value of the QL of external NTR clock sources with support for SSM signalling with the following command: configure system sync-if-timing ssm (no) target-ql

Note 1 — The parameter specifies the clock source which can be one of the following values:

• •

synce-1 synce-2

Note 2 — The parameter specifies manual setting of the clock source, chosen in compliance with the standards ITU-T G.781, G.8264. The default value for is clk-ql-prc for ETSI. Other possible values are clk-ql-ssu-a, clk-ql-ssu-b, clk-ql-sec, and clk-ql-dnu.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2236-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2236 — Configure the enhanced system clock synchronization

9

Configure the wait-to-restore time for an external NTR clock source, during which it has to remain physically available, or during which its signaled QL has to remain equal or higher than the configured target QL, before the source can be selected, with the following command: configure system sync-if-timing (no) wait-time

Note — The parameter specifies the amount of time in the range of [0...720] seconds. The default value for is equal to 10 (seconds). 10

Configure the manual selection of the local clock (holdover/free-run) with the following command: configure system sync-if-timing force-reference local

Note — The manual selection of the local clock automatically applies holdover mode, if the clock was locked to an external reference before the manual selection. After a system restart, no holdover data are available. In this case, this command will result in selection of the local clock in free-running mode. The following command releases the manual selection of the clock source and allows for automatic clock source selection based on the system timing configuration: configure system sync-if-timing no force-reference

11

Display the status of the system timing which indicates the status of the configured clock sources with the following command: show system sync-if-timing

12

Optionally, modify the internal VLAN ID reserved for SSMout. By default this VLAN ID is set to 4088. If this VLAN ID is already used in the network, it is required to assign another value from the range 1..4091 to this VLAN ID. Use the following command: configure system ntr-ssmout-vlan

13

Optionally, configure the SSMout on SyncE (network) ports with the following command: configure system sync-if-timing ssmout-synce (no) ssmout-enable

Note — The parameter specifies the faceplate port to be used as syncE reference. This faceplate port can be one of the following ports:

• •

DLP 2236-6

nt:sfp:[1..6] none

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2236 — Configure the enhanced system clock synchronization

14

Optionally, configure the SSMout on DSL ports with the following command: configure system sync-if-timing ssmout-ltport [no] ssmout-enable

Note 1 — Before the DSL ports can be configured for SSMout, the operator must first create the bridge port(s) on top of the DSL port (see DLP 1124). Note 2 — The parameter dsl-port is defined as Rack/Shelf/Slot/Port/(vpi/vci) (for example, for LT-4 on port 6: 1/1/4/6). Note 3 — The command must be repeated for each DSL port. Note 4 — The command applies to local LTs (Host shelf) and/or remote LTs in FD-REM shelf. 15

Optionally, configure the maximum output value for SSMout (also known as ceiling parameter) with the following command: configure system sync-if-timing ssmout-ceiling

Note — The parameter Sys::SysClkSrcQL specifies the manual setting of the clock source, chosen in compliance with the applicable regional options for the standards ITU-T G.781, G.8264. The default value for Sys::SysClkSrcQL is clk-ql-prc for ETSI. 16

STOP. This procedure is complete.

Configuration example for NANT-A (Config#1): configure system sync-if-timing bits e1 show system sync-if-timing Configuration example for NRNT-A (Config#3): configure system sync-if-timing ref-order prio1 synce-1 configure system sync-if-timing ref-order prio2 synce-2 configure system sync-if-timing synce synce-1 nt:sfp:1 configure system sync-if-timing synce synce-2 nt:sfp:2 configure system sync-if-timing ssm synce-1 ssmenable ssm-targetql 8 configure system sync-if-timing ssm synce-2 no ssmenable configure system sync-if-timing wait-time 5 output-ql-thresh 8 configure system sync-if-timing force-reference local show system sync-if-timing

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2236-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2236 — Configure the enhanced system clock synchronization

To configure SSMout parameters (Config#1): configure system ntr-ssmout-vlan 470 configure system sync-if-timing ssmout-ceiling clk-ql-ssu-a configure system sync-if-timing ssmout-synce nt:sfp:1 ssmout-enable configure system sync-if-timing ssmout-synce nt:sfp:[3..6] ssmout-enable configure equipment slot 1/1/4 planned-type NVLS-A configure bridgeport 1/1/4/[1..48] configure system sync-if-timing ssmout-ltport 1/1/4/1 ssmout-enable configure system sync-if-timing ssmout-ltport 1/1/4/[4…8] ssmout-enable

DLP 2236-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2273 — External Packet Forwarding Purpose This document provides the steps to enable or disable External Packet Forwarding (EPF).

General In order to support Lawful Intercept, voice traffic exchanged between 2 voice termination points must be intercepted by an interception point (CCIF and IRIIF) prior to receipt at the destination voice termination point. The interception point is situated outside the ISAM Voice access node, further upstream in the customer's voice network and is referred to as the External EPF device. Obviously, all voice traffic originating at an ISAM Voice access node and destined to either a termination point connected to the same ISAM Voice access node, or a termination point connected to an ISAM Voice access node that subtends to the originating ISAM Voice, or a termination point connected to a remote ISAM Voice access node, or a termination point that resides outside the ISAM Voice cluster, must be brought outside of the originating ISAM Voice access node as to allow this voice traffic to be tapped to the Lawful Intercept device. To serve such Lawful intercept topology, ISAM Voice allows enabling the External Packet Forwarding facility. The EPF facility requires the IP address of the external EPF device to which the voice traffic is to be forwarded as a configuration input. The external EPF device must be directly connected to the ISAM Voice.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2273-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2273 — External Packet Forwarding

When EPF is enabled, all voice traffic that originates from a voice termination point A connected to the ISAM Voice and destined to a voice termination point B, either connected to the same ISAM Voice, or connected to an ISAM Voice that subtends to the former ISAM Voice, or connected to an ISAM Voice that together with the former ISAM Voice subtends to the same Hub ISAM Voice, or to an ISAM Voice connected by means of a layer 2/layer 3 aggregation network with the former ISAM Voice, is forwarded in upstream direction to the external device as being pointed to by the configured IP address prior to the further forwarding to the destined voice termination point. The same forwarding principle as mentioned before, applies when either voice termination point A or voice termination point B becomes replaced by the Voice server due to the support of some supplementary services or the support of an optimized IP addressing scheme.

Restrictions The following restrictions apply: 1

The External Packet Forwarding facility is supported on the 24Gbps NT (including the NRNT-A) only.

2

The External Packet Forwarding facility is supported on the 7302 ISAM, 7330 ISAM FTTN and 7356 ISAM FTTB equipment practices.

3

The External Packet Forwarding facility is supported for the MEGACO and the SIP Centralised based ISAM Voice Service.

4

The External Packet Forwarding facility is supported on the HUB, Subtending and Remote (MEGACO only) ISAM Voice access nodes.

5

The External Packet Forwarding facility is supported on VLANS of type “Voice-VLAN” and “Residential Bridge”.

6

The External Packet Forwarding facility supports L2 aggregated network links through static L2 aggregation group configuration.

7

The External Packet Forwarding facility supports L2 aggregated network links through LACP.

8

The External Packet Forwarding facility supports xSTP.

9

The External Packet Forwarding facility is supported for POTS only (excluding T.38).

10 The External Packet Forwarding facility is supported in case the ISAM Voice Access node connects directly or by means of (an) intermediate ISAM Voice access node(s) to the external EPF device by means of a L2 switching network. 11 Supporting (enabling) the External Packet Forwarding facility is mutual exclusive to the support (configuration) of the private IP addressing topology (IP Address & IP Subnet reduction topology). 12 The External Packet Forwarding facility shall only be enabled for the VLAN that carries the RTP traffic (might be a vlan sharing both RTP and signaling traffic). 13 The External EPF device must allow to disable the ICMP Redirect facility.

DLP 2273-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

DLP 2273 — External Packet Forwarding

Prerequisites The following prerequisites must be fulfilled before the External Packet Forwarding can be enabled/disabled:

•

The NT/SHub of the ISAM-Voice access node where EPF is to be enabled /disabled must be operational

Procedure Proceed as follows to enabled/disable External Packet Forwarding: 1

Show the next available session for integrated line test with the following command: configure interface shub ip (vlan-id) extfwd (no) device-ip ]

Note 1 — External Path Forwarding becomes enabled upon the configuration of the IP address of the external EPF device. Note 2 — External Path Forwarding becomes disabled upon removing the IP address of the external EPF device. 2

STOP. This procedure is complete.

Configuration example (Config#1): Enable External Packet Forwarding: configure interface shub ip 400 extfwd device-ip 10.184.130.44 Disable External Packet Forwarding: configure interface shub ip 400 extfwd no device-ip

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 2273-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

DLP 2273 — External Packet Forwarding

DLP 2273-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Routine Task Procedure (RTP)

RTP 1102 — Retrieve remote inventory RTP 1103 — Retrieve board temperature RTP 2100 — Backup the configuration RTP 2101 — Restore the configuration

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

RTP 1102 — Retrieve remote inventory Purpose This procedure provides the steps to retrieve and show the remote inventory information. Table RTP 1102-1 describes the RI information that is shown. Table RTP 1102-1: RI information RI information

Description

manufacturer

An identification of the board manufacturer

inventory-pba

The Alcatel-Lucent Printed Board Assembly code of the code

inventory-fpba

The Alcatel-Lucent Printed Board Assembly code of the board, which also identifies the boot software

inventory-ics

The Item Change Status iteration code of the board

inventory-clei

The (USA) Common Language Equipment Identification code of the board

serial-no

The serial number of the board

Procedure Proceed as follows to retrieve and show remote inventory information: 1

View the RI information with the following command: show equipment slot // detail show equipment applique // detail

2

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 RTP 1102-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

RTP 1102 — Retrieve remote inventory

Configuration example: show equipment slot detail show equipment applique detail

RTP 1102-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

RTP 1103 — Retrieve board temperature Purpose This command allows the operator to read the sensor temperature attributes of a specified sensor of a board. Table RTP 1103-1 describes the temperature information that is shown. Table RTP 1103-1: Temperature information RI information

Description

actual temperature

Actual temperature of thermal sensor (in degrees Celsius)

tca-threshold-low

Low threshold for the alarm “Temperature Exceeded” (in degrees Celsius)

tca-threshold-high

High threshold for the alarm “Temperature Exceeded” (in degrees Celsius)

shut-threshold-low

Low threshold for the alarm “Temperature Shutdown” (in degrees Celsius)

shut-threshold-high

High threshold for the alarm “Temperature Shutdown” (in degrees Celsius)

Procedure Proceed as follows to show the board sensor temperature: 1

View the board sensor temperature with the following command: show equipment temperature (slot) sensor-id detail]

2

STOP. This procedure is complete.

Configuration example: show equipment temperature 1/1/4 sensor-id 1 detail

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 RTP 1103-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

RTP 1103 — Retrieve board temperature

RTP 1103-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

RTP 2100 — Backup the configuration Purpose This procedure provides the steps to back up the NT database.

Caution 1 — The SHub database is part of the NT database. The system automatically saves the SHub database every 10 minutes. If a change is made to the SHub database and the system is reset prior to the database being saved, the changes can be lost. The operator can check if the database has been saved since the last change with the following command. show system shub entry status

The SHub database can be saved manually with the following command: admin software-mngt shub database save

Caution 2 — If the system is reset within 10-20 seconds after an NT database changes has been made, it is possible that this latest change could be lost. The operator should ensure that no changes to the database have been made 30 seconds prior to resetting or removing the NT or shutting down the power to the system.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 RTP 2100-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

RTP 2100 — Backup the configuration

Warning — Since only three database containers are available in the ISAM the operator should be aware of the fact that the backup of the actual active database requires a dedicated database container to make a temporary copy of the actual active database to allow a smooth upload of this database. Since the system can host two OSWPs with each a linked database the third database container will be used to store the temporary copy. This means that a recently downloaded database that is not yet activated and that is naturally stored in this third container will be removed to store the temporary database copy. It must be clear that this situation does not occur when the operator follows the procedures described in this book. In all normal cases the database that was stored in the third database container and that is removed to make place for the temporary copy during a database backup is not useful for the operator.

General The TFTP daemon on the 5520 AMS assumes a default home directory /var/opt/ni/ne. This means that all the TFTPs initiated from the NE result in a file written relative to this point.

Note 1 — It is highly recommended to name the file to which the database is to be saved dm_complete.tar. The protected database will then be saved including the configured security SNMP community (which is necessary for communication with the AMS after a restore). If another filename (for example dm.tar) is chosen, then the security SNMP community must be recreated manually after a restore.

Note 2 — Only 2 file names are allowed:

• •

dm_complete.tar dm.tar: This is the dm_complete.tar without the management data

Prerequisite An empty file dm_complete.tar must exist in the specified path on the TFTP server before the upload is started. Otherwise, the upload will fail (error “upload-error:file-not-found”).

Note — The superuser must create this file.

Create the dm_complete.tar file on the TFTP server with the following commands ($ prompt is regular user, # prompt is superuser): $ su

RTP 2100-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

RTP 2100 — Backup the configuration

# cd /var/opt/ni/ne

(*)

# touch dm_complete.tar # chmod 666 dm_complete.tar # exit $ The NT database can now be backed up.

Note —

(*)

For AMS, the command is cd /opt/ALAams/systemdata

Procedure Proceed as follows to back up the NT database: 1

Save the SHub database with the following command: admin software-mngt shub database save

2

Back up the NT database (and SHub database) with the following command: admin software-mngt database upload actual-active:: where is the IP address of the AMS server.

3

View the status of the database upload process and, in case of an upload failure, the reason, with the following command: show software-mngt upload-download

4

STOP. This procedure is complete.

Configuration example: show system shub entry status admin software-mngt shub database save show system shub entry status admin software-mngt database upload actual-active:10.176.5.5:dm.tar show software-mngt upload-download admin software-mngt database upload actual-active:10.176.5.5:dm_complete.tar show software-mngt upload-download

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 RTP 2100-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

RTP 2100 — Backup the configuration

RTP 2100-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

RTP 2101 — Restore the configuration Purpose This procedure provides the steps to restore the NT database (and SHub database). The filename of the database is dm_complete.tar.

Procedure Proceed as follows to restore the NT database: 1

Download the database with the following command: admin software-mngt database download : where is the IP address of the AMS server.

2

View the status of the database download process and, in case of a download failure, the reason for this download failure with the following command: show software-mngt upload-download

3

Activate the downloaded database with the following command: admin software-mngt oswp (index current oswp) activate with-linked-db

4

STOP. This procedure is complete.

Configuration example: admin software-mngt database download 10.176.5.5:dm_complete.tar show software-mngt upload-download admin software-mngt oswp 1 activate with-linked-db

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 RTP 2101-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

RTP 2101 — Restore the configuration

RTP 2101-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Trouble Analysis Procedure (TAP)

TAP 1100 — Metallic test access TAP 1101 — F5 loopback test TAP 1102 — Equipment repair TAP 1103 — Single ended line testing TAP 1105 — Dual-ended line testing TAP 1106 — ITSC TAP 1107 — MELT TAP 1108 — Integrated NBLT for MEGACO Termination TAP 1109 — Integrated NBLT for SIP Termination TAP 2104 — Fault isolation and troubleshooting

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1100 — Metallic test access Note Metallic Test Access (MTA) can not be configured using CLI commands. Refer to the Operations and Maintenance Using TL1 for FD 24Gbps NT document, TAP 100 for the configuration of MTA using TL1 commands.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1100-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1100 — Metallic test access

TAP 1100-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1101 — F5 loopback test Purpose This procedure provides the steps to perform an F5 loopback end-to-end test on the NE.

Note — The result of the test is displayed in microseconds.

Procedure Proceed as follows to perform an F5 loopback test: 1

Start an F5 loopback test with the following command: admin atm port (port) f5-loopback-ete start

2

View the result of the test with the following command: info admin atm port (port)

3

STOP. This procedure is complete.

Configuration example: admin atm port 1/1/5/1:8:35 f5-loopback-ete start info admin atm port 1/1/5/1:8:35

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1101-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1101 — F5 loopback test

TAP 1101-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1102 — Equipment repair Purpose This procedure provides the steps to perform equipment repair on the NE.

Procedure Proceed as follows to perform equipment repair tasks: 1

Lock equipment (mostly plug-in units); see DLP 1112.

2

Shut down individual equipment; see DLP 1153.

3

Pull out equipment; see the hardware installation manual for your equipment.

Note — The NE does not keep time while the card is unplugged from the shelf. In order for the time to be synchronized when the card boots up, it must be set to use SNTP or NTP time synchronization with the management station. See DLP 2103. 4

Replan equipment (for example, plug-in units); see DLP 2111.

5

Plug in equipment; see the hardware installation manual for your equipment.

6

Power up individual equipment; see DLP 1153.

7

Unlock equipment (mostly plug-in units); see DLP 1112.

8

Start up or shut down the system. Do one of the following:

9

a

Shut down or restart the SHub; see DLP 1151.

b

Reboot the entire system; see DLP 1152.

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1102-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1102 — Equipment repair

TAP 1102-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1103 — Single ended line testing General Description Single Ended Line Testing (SELT) is a modem-based feature which allows to measure loop characteristics between the U-C and U-R interface. No CPE modem is to be connected. SELT will help in cooperation with a 5530 Network Analyser (NA) for loop pre-qualification and maintenance of the network.

Note — SELT is only managed using the 5530 NA, not via CLI.

Refer to the System Description for FD 24Gbps NT for more detailed information.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1103-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1103 — Single ended line testing

TAP 1103-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1105 — Dual-ended line testing General Description Dual-ended line testing (DELT) tests an xDSL line from the LT unit. It requires a CPE to be connected to the peer side of the line. Refer to the System Description for FD 24Gbps NT for more detailed information about DELT. Refer to TNG 1107 for a description of xDSl line status parameters that can be returned for DELT.

Purpose This section describes the steps to use dual-ended line testing (DELT) to return information about the status of an xDSL line using CLI.

Procedure Use this procedure collect data about an xDSL line using DELT: 1

To run DELT in carrier data mode without re-initialization: i

Start the data collection with the following command: configure xdsl line /// carrier-data on

ii

Verify that the mode is correct with the following command. The value for the carrier-data-mode parameter in the output of the command should be “on”. info configure xdsl line ///

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1105-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1105 — Dual-ended line testing

iii

Collect the results for the xDSL line with the following command: show xdsl carrier-data [near|far]-end /// detail

iv

Stop the data collection with the following command: configure xdsl line /// carrier data off

2

To run DELT in carrier data mode with re-initialization: i

Start the data collection with the following command: configure xdsl line /// carrier-data on-init

ii

Verify that the mode is correct with the following command. The value for the carrier-data-mode parameter in the output of the command should be “on-init”. info configure xdsl line ///

iii

Wait for the line to resynchronize. You can verify the status of the line with the following command; the line has resynchronized when the value of the oper-state parameter in the output of the command is “up”. show xdsl oper-data-port ///

iv

Collect the results for the xDSL line with the following command: show xdsl carrier-data [near|far]-end /// detail

v

Stop the data collection with the following command: configure xdsl line /// carrier data off

3

To run DELT in loop diagnostics mode: i

Start loop diagnostics with the following command: admin xdsl-line /// loop-diagnostic start

ii

Verify that the mode is correct with the following command. The value for the loop-diagnostic parameter in the output of the command should be “start”. info admin xdsl-line ///

iii

Wait until the test is completed. You can verify the status of the line with the following command; the test is complete when the value of the loop-diagnostic parameter in the output of the command is "completed" info admin xdsl ///

TAP 1105-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1105 — Dual-ended line testing

iv

Collect the results for the xDSL line with the following command: show xdsl carrier-data [near|far]-end /// detail

v

Stop the loop diagnostics with the following command: admin xdsl-line /// loop-diagnostic stop

4

To stop DELT in data collection mode and return to in-service monitoring: i

Stop the data collection with the following command: configure xdsl line /// carrier data off

ii

Collect the results for the xDSL line with the following command: show xdsl carrier-data [near|far]-end /// detail

5

To stop DELT in loop diagnostics mode and return to in-service monitoring: i

Stop the loop diagnostics with the following command: admin xdsl-line /// loop-diagnostic stop

ii

Collect the results for the xDSL line with the following command: show xdsl carrier-data [near|far]-end /// detail

6

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1105-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1105 — Dual-ended line testing

TAP 1105-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1106 — ITSC Note ITSC can not be configured using CLI commands. Refer to the Operations and Maintenance Using TL1 for FD 24Gbps NT document, TAP 100 for the configuration of MTA using TL1 commands.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1106-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1106 — ITSC

TAP 1106-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT Purpose This document provides the steps to configure the MELT test parameters and to retrieve the results of the test. Metallic Ended Line Testing (MELT) of a digital lines is part of a management activity which is performed by the operator in order to detect metallic loop issues. MELT is recommended to be executed by means of the Alcatel-Lucent 5530 Network Analyzer (5530 NA), a professional failure diagnose product. Nevertheless, the ISAM also provides the capability of performing MELT directly by CLI commands initiated by the operator. Since the MELT is an interactive process, usually multiple commands need to be executed for a single test case. Metallic Ended Line testing (MELT) is a line-test feature which allows:

• • • • • • • • • •

To locate the fault point for an interrupted copper double wire. To detect the asymmetry between a and b line in a line pair (resistance and capacitance). To detect bad line contacts. To detect Cable moisture. To perform Line fault isolation (e.g. to locate the line fault occurs between CO and MDF (main distribution frame) or between the MDF and the subscriber,...). To detect the presence of external voltage. To detect faulty line connection. To detect Signature topology. Cable pair identification. To detect the presence of a DSL splitter.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

Note — MELT Test and Metallic Test Access (MTA) are mutual exclusive.

Session Management • • • • •

•

•

The ISAM allows to include all subscriber lines of an LT board in a MELT session (NALT-M = 72 lines / NVLT-M = 48 lines /NSLT-B = 24 lines). The max number of simultaneous MELT sessions that can run on an access node shall not exceed 16. Only 1 MELT session can run at a time on an LT board. In case multiple subscriber lines of the same XDSL LT board are involved in a MELT session, then the NE shall execute the MELT for each of the subscriber lines in a sequential way. A configurable "session Inactive timer" object has been introduced in the Line Test Session Table. The inactive timer is applied to all session states except the "Run_Cmd" session state (session state set whilst MELT test is running). A MELT Session will autonomously be dropped by the system if, once the MELT session as been created, no operator triggered management operation is received during a period equals the configured session inactivity timer. Any received SNMP GET or SET operation results in a restart of the timer. Should no value be configured for the session inactivity timer then the system will assume a session inactivity timer = 0, meaning that the MELT session is never autonomously dropped by the system. The execution of a MELT can be stopped for a particular subscriber line only. The system does not allow to stop a MELT for a particular line test type. The system shall not accept a request to stop the MELT on a particular subscriber line, if the results of the test have already been reported by the HW. The system allows to terminate the Cable Pair Identification test by operator command.

Subscriber Line Management •

•

TAP 1107-2

Starting MELT on an xDSL line has no dependency on the xDSL line status. Exception: • Cable pair identification test on SHDSL LT card NSLT-B: The SHDSL line must be in admin state "down", otherwise cable pair identification cannot be started. • Audible tone test can be started at any time without notification. However the SHDSL service on the link will be stopped to start audible tone generation. Afterwards, when the Audible tone test is stopped, the SHDSL state will resume the state from before the test. Running the MELT test at a particular subscriber line does not influence the XDSL service offering and quality of the neighbouring lines connected to the same access node.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

•

MELT testing may influence the behaviour of the line under test in the sense that: • Re-synchronization may not be triggered. • SES (severely errored seconds) may not occur.

SNMP versus CLI A first major difference between the SNMP and the CLI management interfaces is the configuration of the MELT Type-High and the MELT Type-Low parameters: SNMP: the MELT test types can individually and freely be configured considering the object definitions and the MELT feature policies. CLI : A set of predefined MELT test sets is offered as to achieve a more operator friendly management interface . The content of these MELT test sets is fixed.

•

MELT Type-High: 5 MELT test sets defined: 1) Group: group test including following individual tests: • Foreign_AC_RMS_of_User_Circuit (tr) • Foreign_AC_RMS_of_User_Circuit (tg) • Foreign_AC_RMS_of_User_Circuit (rg) • Foreign_DC_Voltage_of_User_Circuit (tr) • Foreign_DC_Voltage_of_User_Circuit (tg) • Foreign_DC_Voltage_of_User_Circuit (rg) • Insulating_resistance_of_User_Circuit (tr) • Insulating_resistance_of_User_Circuit (rt) • Insulating_resistance_of_User_Circuit (tg) • Insulating_resistance_of_User_Circuit (rg) • Capacitance_of_User_Circuit (tr) • Capacitance_of_User_Circuit (tg) • Capacitance_of_User_Circuit (rg) 2) Foreign-ac-vol: Foreign AC RMS voltage test including following individual tests: • Foreign_AC_RMS_Voltage_of_User_Circuit (tr) • Foreign_AC_RMS_Voltage_of_User_Circuit (tg) • Foreign_AC_RMS_Voltage_of_User_Circuit (rg) 3) Foreign-dc-vol: Foreign DC voltage test including following individual tests: • Foreign_DC-Voltage_of_User_Circuit (tr) • Foreign_DC-Voltage_of_User_Circuit (tg) • Foreign_DC-Voltage_of_User_Circuit (rg) 4) Resistance: Insulating Resistance test including following individual tests: • Insulating_resistance_of_User_Circuit (tr) • Insulating_resistance_of_User_Circuit (rt) • Insulating_resistance_of_User_Circuit (tg) • Insulating_resistance_of_User_Circuit (rg) 5) Capacitance: Capacitance test including following individual tests: • Capacitance_of_User_Circuit (tr) • Capacitance_of_User_Circuit (rt) • Capacitance_of_User_Circuit (tg) • Capacitance_of_User_Circuit (rg)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

•

MELT Type-Low: 2 MELT test sets defined: 1)Cable-Pair-Ident : Cable pair identification test 2)Etsi-Signature : Etsi signature test including the following individual tests (72 lines board only): • Capacitance_of_Signature • Resistance_of_Ringer

In general, the ISAM allows to execute the MELT test under the following modes:

• •

Single: The MELT test is executed once. Cablepair: to execute the cable pair test.

MELT Categories The MELT test types are split in the following categories:

• • • • • • • • • •

Category_00 : Category_01 : Category_02 : Category_03 : Category_04 : Category_05 : Category_06 : Category_07 : Category_08 : Category_09 :

Electric N.A. N.A. N.A. Cable-Pair-Identity N.A. N.A. N.A. N.A. N.A.

Only MELT test types that belong to the same category can be executed in the same MELT session. MELT Type_High:

• • • • • • • • • • • • • • • • • TAP 1107-4

Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit

31: 30: 29: 28: 27: 26: 25: 24: 23: 22: 21: 20: 19: 18: 17: 16: 15:

N.A. (N.A.) N.A. (N.A.) N.A. (N.A.) Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) N.A. (N.A.) N.A. (N.A.) N.A. (N.A.) Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) N.A. (N.A.) N.A. (N.A.). Insulating_resistance_of_User_Circuit (Cat_00: Electric) Insulating_resistance_of_User_Circuit (Cat_00: Electric) Insulating_resistance_of_User_Circuit (Cat_00: Electric)

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

• • • • • • • • • • • • • • •

Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit

14: 13: 12: 11: 10: 09: 08: 07: 06: 05: 04: 03: 02: 01: 00:

Insulating_resistance_of_User_Circuit (Cat_00: Electric) N.A. (N.A.) N.A. (N.A.) Capacitance_of_User_Circuit (Cat_00: Electric) Capacitance_of_User_Circuit (Cat_00: Electric) Capacitance_of_User_Circuit (Cat_00: Electric) Capacitance_of_User_Circuit (Cat_00: Electric) N.A. (N.A.) N.A. (N.A.) N.A. (N.A.) N.A. (N.A.) N.A. (N.A.) Reserved (N.A.) N.A. (N.A.) N.A. N.A.

MELT Type_Low:

• • • • • • • • • • • • • • • • • • • • • • • • • • • • •

Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit Bit

31: N.A. (N.A.) 30: N.A. (N.A.) 29: N.A. (N.A.) 28: N.A. (N.A.) 27: N.A. (N.A.) 26: N.A. (N.A.) 25: Reserved (N.A.) 24: N.A. (N.A.) 23: Reserved (N.A.) 22: N.A. (N.A.) 21: Reserved (N.A.) 20 :N.A. (N.A.) 19: Cable_Pair_Identification (Cat_04: Cable-Pair-Identification) 18: N.A. N.A. 17: N.A. (N.A.) 16: N.A. (N.A.) 15: N.A. (N.A.) 14: N.A. N.A. 13: N.A. (N.A.) 12: Capacitance_of_Signature (Cat_00: Electric) 11: Resistance_of_Ringer (Cat_00: Electric) 10: N.AN.A 09: N.A. (N.A.) 08: Reserved (N.A.) 07: Reserved.N.A. 06: Reserved (N.A.) 05: Reserved (N.A.) 04: Reserved (N.A.) 03: Reserved (N.A.)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

• • •

Bit 02: Reserved (N.A.) Bit 01: Reserved (N.A.) Bit 00: Reserved (N.A.)

Minimum and Maximum Thresholds The ISAM reports the results of MELT testing as raw data. As such, it is assumed the full responsibility of an external expert system to verify the test results against provisioned minimum and maximum test thresholds and finally to report the diagnosis. Nevertheless, the ISAM may also perform the validation of the test results on the condition that the minimum and/or maximum thresholds have been configured for this session. Should the MELT test result have exceeded the configured minimum and/or maximum threshold values, an appropriate completion code will be returned. The configured threshold values do only apply to the MELT session for which these were configured. Once this MELT session has been destroyed, the configured minimum and/or maximum threshold values are lost. Should the operator not configure neither a minimum nor a maximum threshold for a MELT session then the system will not do any validation check on the MELT test results.

Test parameter requirements Table TAP 1107-1 provides an overview of the test parameters that are required for each test type. Table TAP 1107-1: Test type parameter requirements Test type

# Parameters

Parameter usage

Threshold configuration

Foreign AC voltage

0

none

no

Foreign DC voltage

0

none

no

Insulating resistance

1

The parameter is optional.

yes

When set and the parameter value = "1" then perform test Resistance rt/tr with PPA Signature; When set and the parameter value = "0" then perform test without PPA Signature. When not set then the test is performed without assigning the PPA Signature. ltValue1: Meaning: isTestSignature Range: 0 (NO), 1 (YES) Default: 0 (NO) Capacitance

0

none

no

(1 of 2)

TAP 1107-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

Test type

# Parameters

Parameter usage

Threshold configuration

Cable Pair Identification

2

•

no

•

ETSI Signature

1

LtValue1: Meaning: Frequency For xDSL Range: 300 to 3400 Hz Default: 800 Hz For SHDSL Range: 800 Hz or 1000 Hz Default: 800 Hz LtValue2: Meaning: Power level For xDSL Range: -600 to 0 (x 0.1 dbm) Default: -160 (x 0.1 dbm) For SHDSL Range: -340 to -40 (x 0.1. dbm) Default: -160 (x 0.1 dbm)

none

no

(2 of 2)

Result Values Following result values may be reported: Table TAP 1107-2: Result values LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Foreign_AC_voltage_tr

Foreign AC RMS voltage of user line (tip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: mV Foreign_AC_voltage_tg

Foreign AC RMS voltage of user line (tip-ground) unit: mV

Foreign_AC_voltage_rg

Foreign AC RMS voltage of user line (ring-ground) unit: mV

Foreign_DC_voltage_tr

Foreign DC voltage of user line (tip-ring) unit: mV

Foreign_DC_voltage_tg

Foreign DC voltage of user line (tip-ground) unit: mV

Foreign_DC_voltage_rg

Foreign DC voltage of user line (ring-ground) unit: mV

Insulating_resistance_tr

Insulating resistance of user line (tip-ring) unit: Ohm

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Insulating_resistance_rt

Insulating resistance of user line (ring-tip)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: Ohm Insulating_resistance_tg

Insulating resistance of user line (tip-ground) unit: Ohm

Insulating_resistance_rg

Insulating resistance of user line (ring-ground) unit: Ohm

Capacitance_tr

Capacitance of user line (tip-ring) unit: nF

Capacitance_rt

Capacitance of user line (ring-tip) unit: nF

Capacitance_tg

Capacitance of user line (tip-ground) unit: nF

Capacitance_rg

Capacitance of user line (ring-ground) unit: nF

Cable Pair Identification

playTraceToneOKTestTerminated(1), playTraceToneOKTimeout(2), playTraceToneFailed(3), stopTraceToneFailed(4)

Capacitance_sig

Capacitance of etsi signature unit: pF

Insulating_resistance_ring

Resistance of etsi signature unit: Ohm

(2 of 2)

Result Value for Cable-Pair-Identification:

• • • •

(1) playTraceToneOKTestTerminated : The search tone has been played successfully; MELT test has been terminated by the operator. (2) playTraceToneOKTimeout: The search tone has been played successfully; the MELT test was stopped due to search tone time-out timer expiry (NPOT-A = 1 minute / NPOT-B = session timer) (3) playTraceToneFailed: Playing the search tone did fail. (4) stopTraceToneFailed: Ending the search tone did fail.

Group Test MELT Group test includes Insulating Resistance, Capacitance, Foreign AC Voltage and Foreign DC Voltage.

Note — The ETSI Signature test type is not part of the MELT Group Test. However, ETSI Signature can run together with the MELT Group Test i.e. within the same MELT session.

TAP 1107-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

Should an operator request to perform a Group Test, including the 13 electric MELT test types as basically defined for a Group test, as well as other MELT test types, then the system will perform the Group test for the 13 electric MELT test types, with the sequence and policies as defined for the Group Test and in addition the system will handle the other requested MELT test types as individual MELT test types. When a Group Test has completed, irrespective of whether full or only partial test results are achieved, the "Common Status" in the Line Test Parameter Table is set to (1) TestFinished. The operator can then check the "Result Status" in the Line Test Line Identity Extended Report Table for additional information on whether an individual MELT test type has been successfully executed or not.

Cable pair Identification Test The search tone is applied symmetrically between Tip and Ring. The characteristics (amplitude and frequency) of the Search Tone are configurable for the MELT session. The search tone can be switched-on / switched-off at all times. When switched-on, the system shall autonomously switch-off the search tone after a configurable time (1…120 minutes)

CLI MELT parameter Description

Single Line Test Session Configuration: session-cmd The following session commands are supported:

• • • • • •

create: create an integrated MELT session. starttest: start the execution of an integrated MELT session (transfer data done). sendinfo: start to transfer info data for an ongoing MELT, to cancel the MELT for 1 or multiple lines. startinfo: transfer info data completed, start info operation. destroy: delete an integrated MELT session and its contents. endtest: stop the integrated MELT session.

Single Line Test Session Configuration: Timeout-period The time-out period defines the maximum time being required to run an MELT session. It is the sum of the maximum delay defined for each subscriber line involved in the MELT session. The maximum delay for a subscriber line is defined as the sum of the maximum delay for each MELT test executed on the subscriber line. Below, the maximum delay for each of the MELT tests is shown:

• • • • •

Overall overhead time per session: 2 s Group test: 18 s Foreign AC Voltage: 5 s Feeded DC Voltage: 5 s Insulating Resistance: 18 s

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

• • •

Capacitance: 18 sec Cable Pair Identification: 65 s ETSI Signature: 18 sec

Single Line Test Session Configuration: Type-High With the type-high parameter the operator may indicate the following MELT tests:

• •

•

•

•

•

None: null Group: group test including following individual tests: • Foreign_AC_RMS_of_User_Circuit (Tip-Ring) • Foreign_AC_RMS_of_User_Circuit (Tip-Ground) • Foreign_AC_RMS_of_User_Circuit (Ring-Ground) • Foreign_DC_Voltage_of_User_Circuit (Tip-Ring) • Foreign_DC_Voltage_of_User_Circuit (Tip-Ground) • Foreign_DC_Voltage_of_User_Circuit (Ring-Ground) • Insulating_resistance_of_User_Circuit (Tip-Ring) • Insulating_resistance_of_User_Circuit (Ring-Tip) • Insulating_resistance_of_User_Circuit (Tip-Ground) • Insulating_resistance_of_User_Circuit (Ring-Ground) • Capacitance_of_User_Circuit (Tip-Ring) • Capacitance_of_User_Circuit (Tip-Ground) • Capacitance_of_User_Circuit (Ring-Ground) Feeded-ac-vol: Feeded AC RMS voltage test including following individual tests: • Feeded_AC_RMS_Voltage_of_User_Circuit (Tip-Ring) • Feeded_AC_RMS_Voltage_of_User_Circuit (Tip-Ground) • Feeded_AC_RMS_Voltage_of_User_Circuit (Ring-Ground) Foreign-dc-vol: Foreign DC voltage test including following individual tests: • Foreign_DC-Voltage_of_User_Circuit (Tip-Ring) • Foreign_DC-Voltage_of_User_Circuit (Tip-Ground) • Foreign_DC-Voltage_of_User_Circuit (Ring-Ground) Resistance: Insulating Resistance test including following individual tests: • Insulating_resistance_of_User_Circuit (Tip-Ring) • Insulating_resistance_of_User_Circuit (Ring-Tip) • Insulating_resistance_of_User_Circuit (Tip-Ground) • Insulating_resistance_of_User_Circuit (Ring-Ground) Capacitance: Capacitance test including following individual tests: • Capacitance_of_User_Circuit (Tip-Ring) • Capacitance_of_User_Circuit (Ring-Tip) • Capacitance_of_User_Circuit (Tip-Ground) • Capacitance_of_User_Circuit (Ring-Ground)

TAP 1107-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

Single Line Test Session Configuration: Type-Low With the type-low parameter the operator may indicate the following MELT tests:

• • •

None: null Cable-Pair-Ident: Cable pair identification test Etsi-signature: etsi signature test, including capacitance and resistance of etsi signature.

Allowed Type-High / Type Low parameter combinations

Table TAP 1107-3: Allowed Type-High / Type Low parameter combinations High

None

Group

Low

Foreign -ac-vol

Foreign -dc-vol

Resistance

Capacitance

None

IR

A

A

A

A

A

Cable-pair-ident

A

NA

NA

NA

NA

NA

ETSI Signature

A

A

A

A

A

A

IR: Irrelevant A: Allowed NA: Not allowed

Single Line Test Session Configuration: Test modes The following test modes are supported:

• •

single: the integrated MELT is executed once. cablepair: the cable pair test

Single Line Test Parameter Configuration: test names The following test types are supported:

• • • • • • • • • • • •

foreign-ac-tr(mv): foreign AC RMS voltage of user circuit (tip-ring) foreign-ac-tg(mv): foreign AC RMS voltage of user circuit (tip-ground) foreign-ac-rg(mv): foreign AC RMS voltage of user circuit (ring-ground) foreign-dc-tr(mv): foreign DC voltage of user circuit (tip-ring) foreign-dc-tg(mv): foreign DC voltage of user circuit (tip-ground) foreign-dc-rg(mv): foreign DC voltage of user circuit (ring-ground) resist-tr(ohm): insulating resistance of user circuit (tip-ring) resist-rt(ohm): insulating resistance of user circuit (ring-tip) resist-tg(ohm): insulating resistance of user circuit (tip-ground) resist-rg(ohm): insulating resistance of user circuit (ring-ground) capacitanc-tr(nf): capacitance of user circuit (tip-ring) capacitanc-rt(nf): capacitance of user circuit (ring-tip)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

• • • • •

capacitanc-tg(nf): capacitance of user circuit (tip-ground) capacitanc-rg(nf): capacitance of user circuit (ring-ground) cable-pair-ident: cable pair identification test capacit-sign(pf) : capacitance of etsi signature resist-sign(ohm): resistance of etsi signature

Procedure Proceed as follows to execute a MELT test task: 1

Fulfil conditions for MELT; see Table TAP 1107-4. Table TAP 1107-4: Conditions for MELT

MELT Test

Type

Pre-MELT Condition to be fulfilled

MID-MELT condition to be fulfilled

Post-MELT condition to be fulfilled

Type = High Group test

E

Ref. Individual MELT tests

Ref. Individual MELT tests

Ref. Individual MELT tests

Foreign AC Voltage

E

None

None

None

Foreign DC Voltage

E

None

None

None

Resistance

E

None

None

None

Capacitance

E

None

None

None

CPI

None

None

MELT Session time-out

E

None

None

None

Type = Low Cable Pair Identification ETSI Signature

2

Show the next available session for MELT with the following command: show linetest single avail-sess

Note — This step checks whether there is a free session available. The system returns the maximum number of sessions supported together with the available session identifier with which MELT can be configured. 3

Configure the session parameters with the following command: configure linetest single ltsession (sessionid) session-cmd ownerid timeout-period line-num

TAP 1107-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

type-high type-low test-parm-num test-mode inactive-timer

Note — For a description of the different session parameters, see “CLI MELT parameter Description”

4

Configure the line parameter with the following command: configure linetest single ltline (sessionid) lineid line-status

5

Configure the parameters with the following command: configure linetest single ltparm (sessionid) test-name(unit) value1 value2 value3 value4 value5 min-threshold max-threshold

Note — For a description of the different single line test parameters and paramter resuirements, see “CLI MELT parameter Description”

6

Run the MELT test with the following command: configure linetest single ltsession (sessionid) session-cmd starttest

7

Show session parameters with the following command: show linetest single ltsession (sessionid)

Note — In case there would be an input parameter inconsistency in the session configuration or parameter configuration command input, the session / parameter configuration command will be rejected with "General SNMP error" and the reason for rejecting the configuration command will be reported through the "input-err-code" field. Table TAP 1107-5 lists the possible return values.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT Table TAP 1107-5: Possible return values Value

Description

noerr

No error

paramnuminconsis

The number of input parameters configured in the parameter configuration command is different from the value configured in the test-param-num parameter of the session configuration command.

paramnumoutrange

The number of input parameters configured in the parameter configuration command exceeds the maximum allowed range (0-4).

typeneednoparam

The test parameter(s) been configured is(are) meaningless, because the MELT test type to be executed doesn't require any test parameter input.

nontestingtype

The test parameter(s) been configured is(are) for MELT test types which have not been defined in the actual configured session.

missingparamconf

Missing test parameter configuration input for the MELT test types been configured in the session configuration command.

missingtimeout

TimeOut-Period parameter input missing in session configuration command.

timeoutnotenough

The value configured for the TimeOut_Period parameter in the session configuration command is below the required minimum delay for executing the configured MELT test type.

linenuminconsis

The line number configured in the session configuration command is different from the line number configured in line parameter configuration command.

linenumoutrange

The configured number of lines in the session configuration command exceeds the maximum allowed range (1-72).

invalidlineid

The configured line identity in the line parameter configuration command is invalid.

duplicatedline

The same line Identity has been configured twice with the line parameter configuration command.

missingtesttype

The parameters Type-High and/or Type-Low are missing in the session configuration command.

invalidtesttype

The configured value(s) for Type-High and/or Type-Low is(are) incorrect.

thresholdnumerr

The value configured for the threshold parameter in the parameter configuration command exceeds the maximum allowed range (0-39).

neednothreshold

The configured threshold value(s) is (are) meaningless, because the MELT test type to be executed doesn't require any threshold input.

threshfornon

The configured threshold value(s) is(are) for MELT test types which have not been defined in the actually configured session.

typemismatchmode

The configured MELT test type does not match the configured test mode.

linenummismatch

The number of lines been configured in the session configuration command does not match with the configured MELT test type and test mode.

wrongstatusforsub

The actual line status for subtest is not as required to execute the subtest.

lineidinnontest

The line Identity configured in the line configuration command is not in testing status.

sessionstateerr

The configuration command is not allowed within the current session state.

(1 of 2)

TAP 1107-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

Value

Description

internalerror

Internal system error

inactivetimeroutrange

The value of the inactive timer parameter configured in the session configuration command exceeds the allowed range (0 or from 120 up to 65535).

(2 of 2)

8

Show all parameters on a specific line id of a session with the following command: show linetest single ltline (sessionid) lineid

9

Show MELT test report with the following command: show linetest single lineid-ext-rept (sessionid) lineid test-name(unit) result-index

10

STOP. This procedure is complete. Configuration example: Type-HIGH NBLT examples: 1 GROUP TEST. 1.1 Show the available Session. show linetest single avail-sess 1.2 Start the Group test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high group type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 1.3 Free the MELT session. configure linetest single ltsession 1 session-cmd destroy 2 FOREIGN-AC-VOL 2.1 Show the available Session. show linetest single avail-sess

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

2.2 Start the Foreign AC Voltage test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high foreign-ac-vol type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 2.3 Free the MELT session. configure linetest single ltsession 1 session-cmd destroy 3 FOREIGN-DC-VOL. 3.1 Show the available Session. show linetest single avail-sess 3.2 Start the Foreign DC Voltage test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high foreign-dc-vol type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 3.3 Free the MELT session. configure linetest single ltsession 1 session-cmd destroy 4 RESISTANCE. 4.1 Show the available Session. show linetest single avail-sess

TAP 1107-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1107 — MELT

4.2 Start the Resistance test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high resistance type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 4.3 Free the MELT session. configure linetest single ltsession 1 session-cmd destroy 5 CAPACITANCE. 5.1 Show the available Session. show linetest single avail-sess 5.2 Start the Capacitance test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high capacitance type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 5.3 Free the MELT session configure linetest single ltsession 1 session-cmd destroy Type-LOW MELT examples: 6 CABLE PAIR IDENTIFICATION. 6.1 Show the available Session. show linetest single avail-sess

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1107-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1107 — MELT

6.2 Start the Cable Pair Identification test configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 600 line-num 1 type-high none type-low cable-pair-ident test-parm-num 0 test-mode cablepair configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest For this MELT test, one has to await the timeout of the MELT session to get the result of the MELT test. show linetest single ltline 1 show linetest single lineid-ext-rept 1 6.3 Free the MELT session. MELT session freed due to Time-Out. 7 ETSI SIGNATURE 7.1 Show the available Session. show linetest single avail-sess 7.2 Start the Status Monitoring test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low etsi-signature test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 7.3 Free the MELT session. configure linetest single ltsession 1 session-cmd destroy

TAP 1107-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination Purpose This document provides the steps to configure integrated Narrow Band Line Test (NBLT) parameters, and receiving the result of NBLT test on the ports which selected.

General Integrated Line testing of voice subscriber ports is part of a management activity which is performed by the operator in order to provide loop pre-qualification and maintenance of the network. Usually, tests can be performed on a routine basis (mainly at night with scheduled facility) or on demand (required by an operator command). The test procedure described in this TAP intends to support inward test, outward test, terminal test and sub-items test (interactive). Integrated Line Test requests will indicate the test to be performed and may indicate the resource(s) to be tested and the timeout period. The Integrated line testing is recommended to be executed by means of the Alcatel-Lucent 5530 Network Analyzer (5530 NA), a professional failure diagnose product. Nevertheless, the ISAM Voice also provides the capability of performing integrated lines test directly by CLI commands initiated by the operator. Since the integrated line test is an interactive process, usually multiple commands need to be executed for a single test case. The involved elements outside the access node include subscriber analogue terminal, i.e. the telephone set in subscriber assisted tests such as Pulse/ DTMF dialling or NT1 for ISDN BA loopback, etc. To evaluate whether a test is passed or failed, a predefined threshold value is used unless the test request contains threshold values, which override the predefined thresholds. The threshold carried in the request applies only for the test itself. After the completion of that test the predefined thresholds shall be restored. For ISDN BRI loopback test, only when the pattern sent and received are totally same, the test result is successful. So neither CDE nor hard-coded threshold is needed.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

The Access Node model At access node side, the 2 wires of a twisted pair are connected to a battery (e.g. 48V, 60 V) through a source impedance (typically 300 Ohm in each wire). This source impedance matches the line impedance and isolates the voice signal from the battery. Figure TAP 1108-1: Access node model

Historically, the source impedance was made of relay coils (known as the 'A' relay). When the phone goes off-hook, the current starts flowing and activates the relays contacts. Those contacts were used to switch the voice signal to the line, via audio coupling capacitors. The positive side of the battery is grounded, so only one of the two wires has a negative potential with regards to the earth. The line voltage was selected to be negative to make the electrochemical reactions on the wet telephone wiring to be less harmful. When the wires are at negative potential compared to the ground the metal ions go from the ground to the wire instead of the situation where positive voltage would cause metal from the wire to leave which causes quick corrosion. The 'positive' wire is called TIP (or A wire) while the 'negative' wire is called RING (or B wire). The terms Tip and Ring originate from the telephone operators' phone plug, which were used in the early days of telephony with operators manually handling customer calls. The names of the wires are derived from the part of the plug to which they were connected

The line model As every transmission line, a phone line can be seen as a cascade of very short RLCG circuits.

TAP 1108-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination Figure TAP 1108-2: Line model

For a single, infinitely short element, the resistance, inductance, capacitance and conductance can be expressed in units relative to the length. As the model assumes that the distributed values are uniform along the line, the total loop characteristics can be obtained by multiplying the per-unit length resistance, inductance, capacitance and conductance by the loop length.

•

•

•

•

Per-unit length resistance (R): The value of this parameter depends on the material conductivity and the wire diameter. For example, the resistance of an AWG24 copper wire is 84 Ohm/km (at 25°C). Per-unit length capacitance (C): The value of this parameter depends on the cable geometry (wires diameter and spacing) and on the dielectric permittivity (epsilon). For the most common type of cables, the typical value is 50nF/km. This value is directly related to the characteristic impedance of the cable. As the majority of the cables are designed on the same characteristic impedance, independently of the wire gauge, the wire capacitance is, at the first order of magnitude, also independent of the wire type. Per-unit length inductance (L): The per-unit length inductance parameter is a function of the cable geometry and of the medium permeability (µ). Typically, the value of the inductance is 0.5mH/km or less. This parameter is typically not measured for POTS troubleshooting. Per-unit length conductance (G): This parameter is related to the insulating resistance between the two wires (the conductance being the inverse of the resistance). The parameter is a function of the dielectric strength and on the wire spacing. Although the unit of conductance is Siemens (S=Ohm^-1), the cable insulation is often expressed as a product of a resistance and a distance (e.g. 800 Mohm per km).

Session Management • • • •

ISAM Voice allows to include all subscriber lines of a voice LT board in an integrated NBLT session (POTS LT board: 48/72 lines). The max number of simultaneous integrated NBLT sessions that can run on an access node shall not exceed 1. In case multiple subscriber lines of the same Voice LT board are involved in an integrated NBLT session, then the access node shall execute the NBLT for each of the subscriber lines connected to a single voice LT board in a sequential way. Upon completion, a NBLT session needs to be “destroyed” by operator command. Not “destroying” a session will keep the session busy for ever. Since the max number of simultaneous integrated NBLT sessions that can run on a Voice cluster equals 1,

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

it would mean that no NBLT sessions can be initiated anymore (there is no pre-defined time period after which the system will autonomously destroy the NBLT session).

Subscriber Line Management •

• • •

TAP 1108-4

When an integrated NBLT (inwards and/or outwards line testing) is running for a particular subscriber line, then this subscriber line shall be blocked for incoming and outgoing calls. In case the integrated NBLT is running at the calling side, no dial tone shall be sent when the subscriber goes off-hook. In case the integrated NBLT is running at the called side, busy tone shall be sent to the calling side. Once the integrated NBLT has been completed on a particular subscriber line, this subscriber line shall be put back in the operational state it had before the integrated NBLT was started. Running the integrated NBLT on a particular subscriber line shall not cause any influence on the voice service offering and quality of the other subscriber lines connected to the same access node. Configuration changes initiated by the operator while NBLT test is running at one or more subscriber lines might cause a considerable difference in time at which the protocol related action is initiated and the time at which the internal state (operational state) / physical state (e.g. power off/on) of the line is changed. For lines under test, such approach may cause a temporarily inconsistent state between the line state maintained at the server/softswitch and the line state maintained at the access node. However, it is assumed that such existing inconsistency during the NBLT test phase will not decline the voice service quality after the NBLT test been completed on the line. • While running the integrated NBLT on a particular subscriber line, it is not allowed to initiate administrative state changes for this subscriber line. Such management commands are rejected and replied with a response code saying that the subscriber line is under test. • While running the integrated NBLT on a particular subscriber line, it is allowed to initiate configuration changes that do not require a lock/unlock of the administrative state (Ref. SIP configuration Detailed Level procedure). Such management commands are accepted and processed even if a subscriber line is under test. • While running the integrated NBLT on a particular subscriber line and the administrative state already being locked, it is allowed to initiate configuration changes that require a lock/unlock of the administrative state (Ref. SIP configuration Detailed Level procedure). Such management commands are accepted and processed even if a subscriber line is under test. (the integrated NBLT can be started on a subscriber line irrespective of the administrative state being set at that moment). • While running the integrated NBLT on a particular subscriber line and having executed the following sequence of configuration commands: (1) Lock ISAM Voice MGI / SGI table (SGI only affect ISDN subscribers). (2) Configuration change of one or more ISAM Voice MGI / SGI table objects, (3) Unlock MGI / SGI table, finally causing a ROOT out-of-service ServiceChange followed by a ROOT restart ServiceChange of MG and block/unblock all subscriber lines, the following behavior is adopted by the ISAM Voice:

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

- H.248 protocol wise, ISAM-V initiates the ROOT out-of-service ServiceChange and ROOT restart ServiceChange requests for MG immediately to the MGC irrespective of whether a subscriber line is under test or not. - From an internal operational state handling perspective, for those subscriber lines that are under test, any operational state change (block/unblock) caused by the afore described management command sequence execution is postponed till the integrated NBLT has completed.

SNMP versus CLI A first major difference between the SNMP and the CLI management interfaces is the configuration of the NBLT Type-High and the NBLT Type-Low parameters. For SNMP: the NBLT test types can individually and freely be configured considering the above mentioned object definitions and the integrated NBLT feature policies. In case of H.248 NBLT: A maximum of 24 NBLT test types (must all be of the same category) may be defined in one NBLT session command. (The reason is that otherwise (should more than 24 NBLT test types been requested) the maximum size of the XLES message (256 bytes) is not sufficient to contain all test results. Such occurrence would cause the XLES path to be lost between the NVPS and the voice LT board). For CLI: A set of predefined NBLT test sets is offered as to achieve a more operator friendly management interface. The content of these NBLT test sets is fixed. 1. NBLT Type-High: 12 NBLT test sets defined:

•

•

•

Group: group test including following individual tests: • Foreign_AC_RMS_of_User_Circuit (tr) • Foreign_AC_RMS_of_User_Circuit (tg) • Foreign_AC_RMS_of_User_Circuit (rg) • Foreign_DC_Voltage_of_User_Circuit (tr) • Foreign_DC_Voltage_of_User_Circuit (tg) • Foreign_DC_Voltage_of_User_Circuit (rg) • Insulating_resistance_of_User_Circuit (tr) • Insulating_resistance_of_User_Circuit (rt) • Insulating_resistance_of_User_Circuit (tg) • Insulating_resistance_of_User_Circuit (rg) • Capacitance_of_User_Circuit (tr) • Capacitance_of_User_Circuit (tg) • Capacitance_of_User_Circuit (rg) Feeded-ac-vol: Feeded AC RMS voltage test including following individual tests: • Feeded_AC_RMS_Voltage_of_User_Circuit (tr) • Feeded_AC_RMS_Voltage_of_User_Circuit (tg) • Feeded_AC_RMS_Voltage_of_User_Circuit (rg) Foreign-ac-vol: Foreign AC RMS voltage test including following individual tests: • Foreign_AC_RMS_Voltage_of_User_Circuit (tr) • Foreign_AC_RMS_Voltage_of_User_Circuit (tg) • Foreign_AC_RMS_Voltage_of_User_Circuit (rg)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

•

•

• •

•

•

• • •

Feeded-dc-vol: Feeded DC voltage test including following individual tests: • Feeded_DC_Voltage_of_User_Circuit (tr) • Feeded_DC_Voltage_of_User_Circuit (tg) • Feeded_DC_Voltage_of_User_Circuit (rg) • Feeded_DC_Voltage_of_User_Circuit (rt) Foreign-dc-vol: Foreign DC voltage test including following individual tests: • Foreign_DC-Voltage_of_User_Circuit (tr) • Foreign_DC-Voltage_of_User_Circuit (tg) • Foreign_DC-Voltage_of_User_Circuit (rg) Feeding-current: Feeding current test Resistance: Insulating Resistance test including following individual tests: • Insulating_resistance_of_User_Circuit (tr) • Insulating_resistance_of_User_Circuit (rt) • Insulating_resistance_of_User_Circuit (tg) • Insulating_resistance_of_User_Circuit (rg) • Insulating_resistance_BAT_of_User_Circuit (gt) • Insulating_resistance_BAT_of_User_Circuit (gr) Capacitance: Capacitance test including following individual tests: • Capacitance_of_User_Circuit (tr) • Capacitance_of_User_Circuit (rt) • Capacitance_of_User_Circuit (tg) • Capacitance_of_User_Circuit (rg) Impedance: Impedance test including following individual tests: • Impedance_of_User_Circuit (tr) • Impedance_of_User_Circuit (rt) • Impedance_of_User_Circuit (tg) • Impedance_of_User_Circuit (rg) Low-capacit-phone: Low capacitance phone test Dialton-delay: Dial tine delay test of User circuit (only in idle state) Msocket-detection: Termination (m_socket detection) test

2. NBLT Type-Low: 13 NBLT test sets defined:

•

•

• • • • • • TAP 1108-6

AC-Current: AC Current test including the following individual tests: • AC_Current_of_user_Circuit (tr) • AC_Current_of_user_Circuit (tg) • AC_Current_of_user_Circuit (rg) DC-Current: DC Current test including the following individual tests: • DC_Current_of_User_Circuit (tr) • DC_Current_of_User_Circuit (tg) • DC_Current_of_User_Circuit (rg) Noise-level: Noise Level test Howler Tone: Howler Tone test Status-Monitored: Status Monitored test Cable-Pair-Ident: Cable pair identification test Talking-Father: Talking test (father test item) Line-Reverse-Sub: Line reverse test; subtest of talking test

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

• • • • •

P-Meter-Pulse-Sub: Private meter pulse test; subtest of talking test Ring-Subscrib-Sub: Ring subscriber with auto ring test; subtest of talking test Dpdtmf-signal-sub: dp/dtmf signal test; subtest of talking test Userloop-Sub: Resistance of user loop (tip-ring); subtest of talking test Isdn-loopback: isdn loop-back test.

In general, the ISAM Voice Allows to execute the integrated NBLT under the following modes:

• • • •

•

Single: The integrated NBLT is executed once. Interactive: the integrated NBLT is executed interactively between the system and the operator. Cablepair: to execute the cable pair test. Block: The system autonomously executes the integrated NBLT 20 times (after having received the “starttest” command). The results of all 20 NBLT iterations can be retrieved after the “en block” integrated line test has been completed. The “Block” mode applies to the following test types: Foreign Voltage (AC/DC), Capacitance, and Insulation Resistance test. Continuous: The integrated NBLT can be infinite times repeated. However, the system shall not autonomously repeat the integrated line test. If repetition is required, the operator must send a repeat command each time a new iteration of the integrated NBLT would be required. It is important that the test results of the previous iteration are retrieved by the operator before the new iteration is requested as otherwise the results of the previous iteration will be overwritten by the results of the last iteration. The “Continuous” mode applies to the following test types: Foreign Voltage (AC/DC), Capacitance, and Insulation Resistance test.

A second major difference between the SNMP and the CLI management interfaces are the BLOCK and CONTINUOUS test modes:

•

•

The BLOCK test mode is applicable to each of the test items in the categories “Electric”. When using the block test mode, the single test item is 20 times repeated. The system buffers all 20 test results for output after the test is finished. The CONTINUOUS test mode is applicable to each of test items in the categories “Electric”. When using the continuous test mode, the test session will not be destroyed after one test cycle is finished. The management platform can send a “repeat” to repeat to same test. Only one test result is buffered. As such, the management platform must retrieve the test result of the completed test cycle prior to the launch of the “repeat” command.

Both the BLOCK and CONTINUOUS test mode can only be applied to one test item at a time. Since the CLI management interface groups several individual test types into predefined test sets and as such only allow the customer to make use of these predefined test sets (individual test types cannot configured by means of the CLI management interface), both, the BLOCK and the CONTINUOUS test mode are NOT be supported by means of the CLI management interface.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

Integrated NBLT Preconditions The Integrated NBLT supports the NBLT test types to run under different subscriber port conditions. Prior to R4.3: All electrical tests can be executed when the subscriber port's administrative status equals "unlocked", operational status equals "enabled" and Line status equals "Idle". From R4.3 onwards Table TAP 1108-1 applies for the 48-line voice LT board and the 72-line voice LT board.

Termination Not provisioned

Termination Provisioned Admin Locked

Termination Provisioned Admin Unlocked Operational Disabled

Termination Provisioned Admin: Unlocked Operational: Enabled Line state: Idle

Termination Provisioned Admin: Unlocked Operational: Enabled Line state: Parking

Test item/Status*

Foreign DC voltage (tr, tg, rg)

Y

Y

Y

Y

Y

Foreign AC voltage (tr, tg, rg)

Y

Y

Y

Y

Y

Capacitance (tr, tg, rg)

Y

Y

Y

Y

Y

Resistance (tr, rt, tg, rg)

Y

Y

Y

Y

Y

AC current (tr, tg, rg)

Y

Y

Y

Y

Y

DC current (tr, tg, rg)

Y

Y

Y

Y

Y

Cable pair identification

Y

Y

Y

Y

Y

Feeding voltage DC

Y

Y

Y(2)

Feeding voltage AC

Y

Y

Y(2)

Feeding current DC

Y

Y

Y(2)

Y

Low capacitance phone detect

Y

Y

Y

Y

M-Socket (PPA) detection (1)

Y

Y

Y

Y

Dial tone delay

Y

Noise level

Y

Y

Y

Y

Y

Status check

Y

Y

Y

Y

Y

Howler tone

Y

Y

Talking tests ISDN Loop-Back

Termination Provisioned Admin: Unlocked Operational Enabled Line state Busy

Table TAP 1108-1: Overview

Y Y

Y

Locked: Port administratively locked by operator (that is, administrative state is down and operational state is down). Disabled: VoIP service is disabled, that is, the port is disabled due to an alarm or disconnected from the network side. The operational state is down.

TAP 1108-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination Notes (1) PPA detection test is not allowed in parking status. (2)

Feeding Voltage DC: Termination provisioned & admin unlocked & operational Enabled & Line State Busy

(3)

Feeding Voltage AC: Following conditions are only supported at the 72 lines voice LT board: Termination provisioned & admin unlocked & operational Enabled & Line State Busy

(4)

Feeding Current DC: Following conditions are only supported at the 72 lines voice LT board: Termination provisioned & admin unlocked & operational Enabled & Line State Busy

To allow the NBLT test types mentioned above to run for a non-provisioned port, the following minimum configuration requirements are required: 1

Configure the internal integrated VoIP service L2/L3 topology at the SHub/IHub.

2

Configure the NT OAM IP address and IP gateway

3

Plan the Voice server

4

Configure the Voice cluster

5

Plan the Voice LT boards in the voice cluster.

6

Configure the internal integrated VoIP service L2/L3 topology at the Voice server

Integrated NBLT to voice LT board Mapping

Table TAP 1108-2: Integrated NBLT to voice LT board Mapping Integrated NBLT Test Type

48 lines POTS LT Board

72 lines POTS LT Board

H-Bit 31: Feeded_AC_RMS_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 30: Feeded_AC_RMS_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 29: Feeded_AC_RMS_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 28: Foreign_AC_RMS_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 27: Foreign_AC_RMS_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 26: Foreign_AC_RMS_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 25: Feeded_DC_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 24: Feeded_DC_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 23: Feeded_DC_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 22: Foreign_DC_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 21: Foreign_DC_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 20: Foreign_DC_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 19: Feeding_Current

Y

Y

H-Bit 18: Feeded_DC_Voltage_of_User_Circuit (rt)

Y

Y

H-Bit 17: Insulating_resistance_of_User_Circuit (tr)

Y

Y

24 lines POTS LT Board

(1 of 3)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

Integrated NBLT Test Type

48 lines POTS LT Board

72 lines POTS LT Board

H-Bit 16: Insulating_resistance_of_User_Circuit (rt)

Y

Y

H-Bit 15: Insulating_resistance_of_User_Circuit (tg)

Y

Y

H-Bit 14: Insulating_resistance_of_User_Circuit (rg)

Y

Y

H-Bit 13: Insulating_resistance_BAT_of_User_Circuit (gt)

Y

Y

H-Bit 12: Insulating_resistance_BAT_of_User_Circuit (gt)

Y

Y

H-Bit 11: Capacitance_of_User_Circuit (tr)

Y

Y

H-Bit 10: Capacitance_of_User_Circuit (rt)

Y

Y

H-Bit 09: Capacitance_of_User_Circuit (tg)

Y

Y

H-Bit 08: Capacitance_of_User_Circuit (rg)

Y

Y

H-Bit 07: Impedance_of_User_Circuit (tr)

Y

Y

H-Bit 06: Impedance_of_User_Circuit (rt)

Y

Y

H-Bit 05: Impedance_of_User_Circuit (tg)

Y

Y

H-Bit 04: Impedance_of_User_Circuit (rg)

Y

Y

H-Bit 03: Low_Capacitance_Phone_Detect

Y

Y

H-Bit 01: Dial tone_delay_of_User_Circuit

Y

Y

H-Bit 00: Termination_testing (M socket)

Y

Y

L-Bit 31: AC_Current_of_user_Circuit (tr)

Y

Y

L-Bit 30: AC_Current_of_user_Circuit (tg)

Y

Y

L-Bit 29: AC_Current_of_user_Circuit (rg)

Y

Y

L-Bit 28: DC_Current_of_User_Circuit (tr)

Y

Y

L-Bit 27: DC_Current_of_User_Circuit (tg)

Y

Y

L-Bit 26: DC_Current_of_User_Circuit (rg)

Y

Y

Y

Y

Y

Y

L-Bit 20: Status_Monitored

Y

Y

L-Bit 19: Cable_Pair_Identification

Y

Y

L-Bit 18: Talking_Father

Y

Y

L-Bit 17: Line_Reverse-Sub_Test

Y

Y

L-Bit 16: Private_Meter_Pulse_Sub_Test

Y

Y

L-Bit 15: Ring_Subscriber-Sub_Test with Auto Ring Test

Y

Y

L-Bit 14: DP/DTMF_Signal_Sub_test

Y

Y

24 lines POTS LT Board

H-Bit 02: Reserved

L-Bit 25: Reserved L-Bit 24: Noise_level L-Bit 23: Reserved L-Bit 22: Howler Tone L-Bit 21: Reserved

(2 of 3)

TAP 1108-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Integrated NBLT Test Type

48 lines POTS LT Board

72 lines POTS LT Board

L-Bit 13: Resistance_of_user_Circuit

Y

Y

24 lines POTS LT Board

L-Bit 12: N.A. L-Bit 11: N.A. L-Bit 10: ISDN-Loop-Back

Y

L-Bit 09: N.A. L-Bit 08: Reserved L-Bit 07: Reserved L-Bit 06: Reserved L-Bit 05: Reserved L-Bit 04: Reserved L-Bit 03: Reserved L-Bit 02: Reserved L-Bit 01: Reserved L-Bit 00: Reserved (3 of 3)

Integrated NBLT Categories The integrated NBLT test types are split into the following categories:

• • • • • • • • • •

Category_00: Electric Category_01: Dial-Tone Category_02: Howler-Tone Category_03: Status-Monitored Category_04: Cable-Pair-Identity Category_05: Talking-Test Category_06: Talking-Sub-Test-DTMF Category_07: Talking-Sub-Test-Other Category_08: Electric-Only-In-Idle-Status Category_09: ISDN-Loop-Back

Only integrated NBLT test types that belong to the same category can be executed in the same integrated NBLT session. NBLT Type_High: 1

Bit 31: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

2

Bit 30: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

3

Bit 29: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

4

Bit 28: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

5

Bit 27: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

6

Bit 26: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

7

Bit 25: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric)

8

Bit 24: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric)

9

Bit 23: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric)

10 Bit 22: Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) 11 Bit 21: Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) 12 Bit 20: Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) 13 Bit 19: Feeding_Current (Cat_00: Electric) 14 Bit 18: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric) 15 Bit 17: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 16 Bit 16: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 17 Bit 15: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 18 Bit 14: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 19 Bit 13: Insulating_resistance_BAT_of_User_Circuit (Cat_00: Electric) 20 Bit 12: Insulating_resistance_BAT_of_User_Circuit (Cat_00: Electric) 21 Bit 11: Capacitance_of_User_Circuit (Cat_00: Electric) 22 Bit 10: Capacitance_of_User_Circuit (Cat_00: Electric) 23 Bit 09: Capacitance_of_User_Circuit (Cat_00: Electric) 24 Bit 08: Capacitance_of_User_Circuit (Cat_00: Electric) 25 Bit 07: Impedance_of_User_Circuit (Cat_00: Electric) 26 Bit 06: Impedance_of_User_Circuit (Cat_00: Electric) 27 Bit 05: Impedance_of_User_Circuit (Cat_00: Electric) 28 Bit 04: Impedance_of_User_Circuit (Cat_00: Electric) 29 Bit 03: Low_Capacitance_Phone_DetectCat_00: Electric) 30 Bit 02: Reserved (N.A.) 31 Bit 01: Dial tone_delay_of_User_Circuit (Cat_01: Dial-Tone) 32 Bit 00: Termination_testing (M socket) (Cat_00: Electric) NBLT Type_Low: 1

Bit 31: AC_Current_of_user_Circuit (Cat_00: Electric)

2

Bit 30: AC_Current_of_user_Circuit (Cat_00: Electric)

3

Bit 29: AC_Current_of_user_Circuit (Cat_00: Electric)

4

Bit 28: DC_Current_of_User_Circuit (Cat_00: Electric)

5

Bit 27: DC_Current_of_User_Circuit (Cat_00: Electric)

6

Bit 26: DC_Current_of_User_Circuit (Cat_00: Electric

7

Bit 25: Reserved (N.A.)

8

Bit 24: Noise_level (Cat_00: Electric)

9

Bit 23: Reserved (N.A.)

10 Bit 22: Howler_Tone (Cat_02: Howler-Tone)

TAP 1108-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

11 Bit 21: Reserved (N.A.) 12 Bit 20:Status_Monitored (Cat_03: Status-Monitored) 13 Bit 19: Cable_Pair_Identification (Cat_04: Cable-Pair-Identification) 14 Bit 18: Talking_Father (Cat_05: Talking-Test) 15 Bit 17: Line_Reverse-Sub_Test (Cat_07: Talking-Sub-Test-Other) 16 Bit 16: Private_Meter_Pulse_Sub_Test (Cat_07: Talking-Sub-Test-Other) 17 Bit 15: Ring_Subscriber-Sub_Test with Auto Ring Test (Cat_07: Talking-Sub-Test-Other) 18 Bit 14: DP/DTMF_Signal_Sub_test (Cat_06: Talking-Sub-Test-DTMF) 19 Bit 13: Resistance_of_user_Circuit (Cat_07: Talking-Sub-Test_Other) 20 Bit 12: N.A. (N.A.) 21 Bit 11: N.A. (N.A.) 22 Bit 10: ISDN Loop-Back (Cat_12: ISDN Loop-Back) 23 Bit 09: N.A. (N.A.) 24 Bit 08: Reserved (N.A.) 25 Bit 07: Reserved (N.A.) 26 Bit 06: Reserved (N.A.) 27 Bit 05: Reserved (N.A.) 28 Bit 04: Reserved (N.A.) 29 Bit 03: Reserved (N.A.) 30 Bit 02: Reserved (N.A.) 31 Bit 01: Reserved (N.A.) 32 Bit 00: Reserved (N.A.)

Minimum and Maximum Thresholds

For releases < R4.3 (for 48-line voice LT board and 72-line voice LT board As a general strategy, ISAM Voice will only report the results of the integrated NBLT testing as raw data. It is assumed that an external expert system (such as 5530NA for example) has the full responsibility to verify the test results against pre-provisioned minimum and maximum test thresholds and to report the diagnosis. Nevertheless, the ISAM Voice also performs some basic validation of the test results based on minimum and maximum thresholds. A predefined threshold can be provisioned in the CDE profile. Such a predefined threshold is provided by the customer. However, if this is not the case then “default threshold values” are provisioned in the CDE profile. If the integrated NBLT test result exceeds the provisioned minimum and/or maximum threshold values, an appropriate completion code will be returned.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

Pre-defined “default values” in CDE profile: Table TAP 1108-3: Default threshold values Type Foreign voltage

Value Maximum voltage AC - a/b

6000000

Maximum voltage AC - a/E

6000000

Maximum voltage AC - b/E

6000000

Maximum voltage DC - a/b

6000000

Minimum voltage DC - a/b

-6000000

Maximum voltage DC - a/E

6000000

Minimum voltage DC - a/E

-6000000

Maximum voltage DC - b/E

6000000

Minimum voltage DC - B/E

-6000000

Maximum capacitance - a/b

5000000

Maximum capacitance - a/E

1000000

Maximum capacitance - b/E

1000000

Loop resistance

Maximum loop resistance - a/b

1800

Insulation resistance

Minimum resistance - a/b and b/a

20000

Minimum resistance - a/E and E/a

20000

Minimum resistance - b/E and E/b

20000

Minimum resistance - a/BAT

20000

Minimum resistance - b/BAT

20000

Minimum current

-100000

Maximum current

100000

Minimum feeding DC voltage - a/b

40000000

Maximum feeding DC voltage - a/b

57000000

Minimum feeding DC voltage - b/a

-57000000

Maximum feeding DC voltage - b/a

-40000000

Minimum feeding current - a/b

7000

Maximum feeding current - a/b

29000

Maximum Idle Noise Level

-50000

Maximum Dial Tone delay

1000

Capacitance

AC and DC current

Inward test

From R4.3.01 onwards (for 72-line voice LT board ONLY) The “threshold default values” are no longer provisioned in the CDE profile.

TAP 1108-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

The threshold values must come from the customer via the CDE-Q. If the customer does not fill in any thresholds in the CDE questionnaire, no thresholds will be included in the CDE profile generated for that customer. ISAM Voice will only report the raw test result. The system does not do any validation check on the NBLT test results.

Migration from release < R4.3.01 to release ≥ R4.3.01 (for 72-line voice LT board ONLY) For customers that want to migrate from a release < R4.3.01 to a release ≥ R4.3.01, the thresholds in the actual CDE profile need to be adapted.

•

•

For the NBLT board types for which the system behavior has been changed from R4.3.01 onwards (feeding current may vary from 0mA~ 18mA, feeding voltage may vary from a small value to ~57V), the thresholds either need to be updated or removed. For the NBLT board types for which the system behavior has not changed in R4.3.01, the thresholds as defined for the former deployed release are kept.

Test parameter requirements Table TAP 1108-4 provides an overview of the test parameters that are required for each test type. Table TAP 1108-4: Test type parameter requirements Test type

# Parameters

Parameter usage

Threshold configuration

Foreign AC voltage

0

none

no

Foreign DC voltage

0

none

no

Feeding DC Voltage

0

none

no

Feeding Current

0

none

no

Insulating resistance

0

none

no

Capacitance

0

none

no

Impedance.

1

ltValue1:

no

Should be a value from 1 up to 4 dependent on the number of polarities to be tested. However due to the limitation of the low driver, the first polarity parameter is considered only. All other polarity parameters are ignored

Meaning: frequency.

0

none

Low capacity Phone detection

Range: 5 up to 3000 Hz. Default: 20 Hz. ltValue2: Meaning: RMS voltage. Range: -150V ~ +150V. Default: 15 V

no

Battery Impedance (1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

Test type

# Parameters

Parameter usage

Threshold configuration

Dial Tone delay

0

none

no

M-Socket detection

0

none

no

AC Current

0

none

no

DC Current

0

none

no

Noise Level

0

none

no

Howler

0

none

no

Line Status Monitoring

1

ltValue1:

no

Meaning: Check real parking or short current state Range: 1, 2 1: No check 2: Check Default: -

Cable Pair Identification

0

none

no

Talking with Subscriber

0

none

no

Line Reverse

0

none

no

Subscriber Private Meter Pulses

1

ltValue1:

no

Meaning: Metering Mode Range: 1, 2 1: TAPI_METER_MODE_TTX 2: TAPI_METER_MODE_REVPOL Default: -

Ring Subscriber

0

none

no

DP/DTMF Signal

1

ltValue1:

no

Meaning: Amount of signals to collect. Range: 1 up to 20 Default: Resistance of User Loop

0

none

no

ISDN Loop Back

1

LtValue1:

no

Meaning: Test Side Range: 1 up to 3 1: LoopbackOnNTSide, loopback test is implemented on NT side 2: LoopbackOnLtSide, loopback test is implemented on LT side 3: LoopbackBothSide, loopback test is implemented on both side Default: (2 of 2)

TAP 1108-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Result Values The following result values may be reported: Table TAP 1108-5: Result values LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Feed_AC_voltage_tr

Feeded AC RMS voltage of user line (tip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: mV Feed_AC_voltage_tg

Feeded AC RMS voltage of user line (tip-ground) unit: mv

Feed_AC_voltage_rg

Feeded AC RMS voltage of user line (ring-ground) unit: mV

Foreign_AC_voltage_tr

Foreign AC RMS voltage of user line (tip-ring) unit: mV

Foreign_AC_voltage_tg

Foreign AC RMS voltage of user line (tip-ground) unit: mV

Foreign_AC_voltage_rg

Foreign AC RMS voltage of user line (ring-ground) unit: mV

Feed_DC_voltage_tr

Feeded DC voltage of user line (tip-ring) unit: mV

Feed_DC_voltage_tg

Feeded DC voltage of user line (tip-ground) unit: mV

Feed_DC_voltage_rg

Feeded DC voltage of user line (ring-ground) unit: mV

Foreign_DC_voltage_tr

Foreign DC voltage of user line (tip-ring) unit: mV

Foreign_DC_voltage_tg

Foreign DC voltage of user line (tip-ground) unit: mV

Foreign_DC_voltage_rg

Foreign DC voltage of user line (ring-ground) unit: mV

Feed_current_tr

Feeding current (tip-ring) unit: µA

Feed_DC_voltage_rt

Feeded DC voltage of user line (ring-tip) unit: mV

(1 of 4)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Insulating_resistance_tr

Insulating resistance of user line (tip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: Ohm Insulating_resistance_rt

Insulating resistance of user line (ring-tip) unit: Ohm

Insulating_resistance_tg

Insulating resistance of user line (tip-ground) unit: Ohm

Insulating_resistance_rg

Insulating resistance of user line (ring-ground) unit: Ohm

Insulating_resistance_tbat

Insulating resistance of user line (tip-bat) unit: Ohm

Insulating_resistance_rbat

Insulating resistance of user line (ring-bat) unit: Ohm

Capacitance_tr

Capacitance of user line (tip-ring) unit: nF

Capacitance_rt

Capacitance of user line (ring-tip) unit: nF

Capacitance_tg

Capacitance of user line (tip-ground) unit: nF

Capacitance_rg

Capacitance of user line (ring-ground) unit: nF

Impedance_tr

Impedance of user line (tip-ring) unit: nF

Impedance_rt

Impedance of user line (ring-tip) unit: nF

Impedance_tg

Impedance of user line (tip-ground) unit: nF

Impedance_rg

Impedance of user line (ring-ground) unit: nF

LowCapDetect

TRUE(1) or FLASE(0)

(2 of 4)

TAP 1108-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Dial_tone_delay

Result of the time interval between the off hook and dial tone is played

Only applicable to SIP 72 lines voice LT board

N.A.

N.A.

N.A.

Result of whether the dial tone is stopped by dialing of an arbitrary digit which is simulated by the LT. N.A. Termination_Testing

TRUE(1) or FLASE(0)

N.A.

N.A.

N.A.

N.A.

AC current test normal test (tip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

(M Socket) AC_current_tr

unit: µA AC_current_tg

AC current test normal test (tip-ground) unit: µA

AC_current_rg

AC current test normal test (ring-ground) unit: µA

DC_current_tr

DC current test normal test (tip-ring) unit: µA

DC_current_tg

DC current test normal test (tip-ground) unit: µA

DC_current_rg

DC current test normal test (ring-ground) unit: µA

Noise_level

unit: 0.001dbm

N.A.

N.A.

N.A.

N.A.

Normal_Condition_Howler

playSuccessfulAndOnHookNormal(1)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

playSuccessfulAndTestTerminated(2) playSuccessfulButOnHookTimeout(3) playFailed(4) Status_Monitored

eStatusMonitoredBlock(2), eStatusMonitoredIdle(3), eStatusMonitoredBusy(4), eStatusMonitoredParking(5), eStatusMonitoredShort(6)

(3 of 4)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Cable Pair Identification

playTraceToneOKTestTerminated(1),

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

playTraceToneOKTimeout(2), playTraceToneFailed(3), stopTraceToneFailed(4) Talking test (father test item) Line Reverse

lineReverseOKTestTerminated(1), lineReverseOKTimeout(2), lineReverseFailed(3)

Private Meter Pulses

meterSuccess(1), meterFailed (2)

Ring Subscriber with Auto Ring

ringSuccessfulAndTestTerminated(1, ringSuccessfulAndStopedByOffHook(2 ), ringSuccessfulAndTimeout(3), ringFailed(4), ringFailedBecausePortisOffHook(5), ringStopFailed(6)

DP/DTMF Signal

numberDP1(1), numberDP2(2), numberDP3(3), numberDP4(4), numberDP5(5), numberDP6(6), numberDP7(7), numberDP8(8), numberDP9(9), numberDP0(10), starDP(11), poundDP(12), numberDTMF1(65537), numberDTMF2(65538), numberDTMF3(65539), numberDTMF4(65540), numberDTMF5(65541), numberDTMF6(65542), numberDTMF7(65543), numberDTMF8(65544), numberDTMF9(65545), numberDTMF0(65546), starDTMF(65547), poundDTMF(65548)

N.A.

N.A.

N.A.

N.A.

Resistance_loop_tr

Resistance of user loop (rip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: Ohm ISDN Loop Back

TestSuceess(1), L1LoopFailOnNT (2), L1PatternFailOnNT(3), L1LoopFailOnLT(4), L1PatternFailOnLT(5), L1LoopFailOnNT_LT(6), L1LoopFailonNT_PatternFailOnLT(7), L1PatternFailOnNT_LoopFailOnLT(8), L1PatternFailOnNT_LT(9)

(4 of 4)

TAP 1108-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Result Value for Howler-Tone

• • • •

1: playSuccessfulAndOnHookNormal: Howler tone has been played successfully. The line went on-hook. 2: playSuccessfulAndTestTerminated: Howler tone has been played successfully. The integrated NBLT test has been terminated by the operator. 3: playSuccessfulButOnHookTimeout: Howler tone has been played successfully. The line did not go on-hook before the Howler Tone time-out timer expired (1 minute). 4: playFailed: Playing the howler tone has failed.

Result Value for Status-Monitoring

• • • • •

2: eStatusMonitoredBlock: The line is blocked due to malfunction, or the line is locked by the operator. 3: eStatusMonitoredIdle: The line is on-hook and in state idle. 4: eStatusMonitoredBusy: The line is involved in a call. 5: eStatusMonitoredParking: The line is in parking state. 6: eStatusMonitoredShort: The line is in short circuit

Result Value for Cable-Pair-Identification

• • • •

1: playTraceToneOKTestTerminated: The search tone has been played successfully. The integrated NBLT test has been terminated by the operator. 2: playTraceToneOKTimeout: The search tone has been played successfully. The integrated NBLT test was stopped due to search tone time-out timer expiry (48 lines voice LT board = 1 minute / 72 lines voice LT board = session timer) 3: playTraceToneFailed: Playing the search tone failed. 4: stopTraceToneFailed: Ending the search tone failed.

Result Value for Line-Reverse

• • •

1: lineReverseOKTestTerminated: The line polarity has been successfully reversed. The integrated NBLT test has been terminated by the operator 2: lineReverseOKTimeout: The line polarity has been successfully reversed. The integrated NBLT test was stopped due to time-out timer expiry (1 minute) 3: lineReverseFailed: The reverse of the line polarity failed

Result Value for Private Meter Pulses

• •

(1) MeterSuccess (2) MeterFailed

Result Value for Ring-Subscriber Sub Test

• • • •

1: ringSuccessfulAndTestTerminated: The ringing has successfully started. The integrated NBLT test has been terminated by the operator. 2: ringSuccessfulAndStopedByOffHook: The ringing has successfully started the integrated NBLT test was stopped due to an off-hook. 3: ringSuccessfulAndTimeout: The ringing has successfully started; the integrated NBLT test was stopped due to time-out timer expiry. 4: ringFailed: The ringing failed due to some internal misbehavior.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

• •

5: ringFailedBecausePortisOffHook: The ringing failed due to the line being in off-hook state. 6: ringStopFailed: The ringing could not be stopped.

Result Value for DP/DTMF Signal Sub Test

• • • • • • • • • • • • • • • • • • • • • • • •

01: numberDP1: pulse digit 1 has been received 02: numberDP2: pulse digit 2 has been received 03: numberDP3: pulse digit 3 has been received 04: numberDP4: pulse digit 4 has been received 05: numberDP5: pulse digit 5 has been received 06: numberDP6: pulse digit 6 has been received 07: numberDP7: pulse digit 7 has been received 08: numberDP8: pulse digit 8 has been received 09: numberDP9: pulse digit 9 has been received 10: numberDP0: pulse digit 0 has been received 11: starDP: pulse digit star(*) has been received 12: poundDP: pulse digit pound(#) has been received 65537: numberDTMF1: dtmf digit 1 has been received 65538: numberDTMF2: dtmf digit 2 has been received 65539: numberDTMF3: dtmf digit 3 has been received 65540: numberDTMF4: dtmf digit 4 has been received 65541: numberDTMF5: dtmf digit 5 has been received 65542: numberDTMF6: dtmf digit 6 has been received 65543: numberDTMF7: dtmf digit 7 has been received 65544: numberDTMF8: dtmf digit 8 has been received 65545: numberDTMF9: dtmf digit 9 has been received 65546: numberDTMF0: dtmf digit 0 has been received 65547: starDTMF: dtmf digit star(*) has been received 65548: poundDTMF: dtmf digit pound(#) has been received

Group Test •

•

Prior to R4.3: • When an operator requests to perform a Group Test (including the 13 electric NBLT test types as basically defined for a Group test, as well as other NBLT test types), then the system handles all the requested NBLT test types as individual NBLT test types. • When a Group Test has completed, the Common Status in the Line Test Parameter Table is set to (1) TestFinished only when all 13 electric NBLT test types were successfully completed. From R4.3 onwards: When an operator requests to perform a Group Test (including the 13 electric NBLT test types as basically defined for a Group test, as well as other NBLT test types), then the system performs the Group test for the 13 electric NBLT test types, with the sequence and policies as defined for the Group Test, and handles the other requested NBLT test types as individual NBLT test types.

TAP 1108-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Validity of test results • •

Prior to R4.3: When a Group test is executed, LTCommonErrCode will be set to testFinished(1) only when the last test item is successful. From R4.3 onwards: When a Group Test has completed, LTCommonErrCode will be set to testFinished(1), irrespective of whether full or only partial test results are achieved. The operator can check LTErrCode for additional information to confirm whether an individual test is valid or not. Additional error codes have been defined to clarify the exact reason for the test failure. the result is valid only when LTCommonErrCode = testFinished(1) and LTErrCode = pPSuccess(1). For details, refer to the linetest MIB.

Feeding DC Voltage / DC Current Test (72-line voice LT board only) Prior to R4.3: Table TAP 1108-6: Feeding DC Voltage / DC Current Test (< R4.3) Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Feeding AC/ DC Voltage

Not allowed

Supported

Not allowed

Feeding DC Current

Not allowed

Supported.

Not allowed

System simulates a 1.8k Ohm loop resistance between a/b lines. Returns feeding current: ~18mA.

From R4.3 onwards: Table TAP 1108-7: Feeding DC Voltage / DC Current Test (≥ R4.3)

Feeding AC/ DC Voltage

Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Not allowed

Supported

Supported. Returns real feeding voltage based on different loop resistances

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-23 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

Feeding DC Current

Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Not allowed

Supported.

Supported.

System measures the real feeding current on the line.

Returns real feeding current: ~18mA.

Returns real feeding current: ~0mA. (2 of 2)

Feeding DC Voltage / DC Current Test (48-line voice LT board only) All releases: Table TAP 1108-8: Feeding DC Voltage / DC Current Test Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Feeding AC/ DC Voltage

Not allowed

Supported

Not allowed

Feeding DC Current

Not allowed

Supported.

Not allowed

System simulates a 1.8k Ohm loop resistance between a/b lines. Returns feeding current: ~18mA.

Foreign DC voltage test (Individual Test / as part of Group Test) (48-line and 72-line voice LT board) The following applies for foreign DC voltage test (Individual Test / as part of Group Test) in case M-socket with large resistance (470 kOhm) and large capacitance (1.8 µF) is connected to the subscriber line:

• • •

In case of a M-socket (470 kOhm, 1.8 µF), the capacitor of this M-socket acts as an energy source and impacts the test accuracy of the Foreign DC voltage test. R2.5: Detection of M-socket termination with 470 kOhm resistance connected in serial with diode. R4.2: To improve the test accuracy, a delay timer is introduced (configurable by means of the CDE profile; default = 3 s) to provide a sufficiently long time period to let the capacitor discharge and as such to improve the test result accuracy.

TAP 1108-24 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Foreign DC voltage test (Individual Test) (72-line voice LT board only) The following applies for foreign DC voltage test (Individual Test) in case M-socket with large resistance (470 kOhm) and large capacitance (1.8 µF) is connected to the subscriber line (72 lines voice LT board only).

• •

Prior to R4.3: Individual Foreign DC voltage test result exceeds CDE threshold. From R4.3 onwards: Individual Foreign DC voltage test result does NOT exceed CDE threshold (The firmware did some improvement to avoid the impact of M-socket).

Note — When Group Test is used, the behavior does not change compared to R4.2.

M-Socket detection M-socket detection function is supported by the ALU 5530 NA only (not by ISAM Voice). From R4.3 onwards: in case of the 72-line voice LT board, and for big-capacitance M-Socket detection, Group Test must be used (delay timer to be set to “0”; Foreign DC voltage test result exceeds CDE threshold).

CLI NBLT parameter description

Single Line Test Session Configuration: session-cmd The following session commands are supported:

• • • • • • • • •

create: create an integrated NBLT session. starttest: start the execution of an integrated NBLT session (transfer data done). sendinfo: start to transfer info data for an ongoing NBLT, to cancel the NBLT for 1 or multiple lines. startinfo: transfer info data completed, start info operation. destroy: delete an integrated NBLT session and its contents. recv-subtest: start to transfer the line sub-test data. start-subtest: transfer sub-test's data done, start the line sub-test. repeat: repeat the last integrated NBLT session. endtest: stop the integrated NBLT session.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-25 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

Single Line Test Session Configuration: Timeout-period The time-out period defines the maximum time being required to run an NBLT session. It is the sum of the maximum delay defined for each subscriber line involved in the NBLT session. The maximum delay for a subscriber line is defined as the sum of the maximum delay for each NBLT test executed on the subscriber line. Below, the maximum delay for each of the NBLT tests is shown:

• • • • • • • • • • • • • • • • • • • • • • • • • • •

Overall overhead time per session: 2 s Group test: 15 s + 5 s (delay time of discharge) Feeded AC Voltage: 3 s Foreign AC Voltage: 10 s Feeded DC Voltage: 3 s Foreign DC Voltage: 10 s + 5 s (delay time of discharge) Feeding Current: 3 s Resistance of Userloop: 6 s Insulating Resistance: 6 s Capacitance: 15 s Impedance: 5 s Low Capacity detect: 20 s Dial Tone Delay: 8 s M-Socket: 6 s AC Current: 66 s DC Current: 66 s Noise Level: 66 s Howler Tone: 120 s Status Monitoring: 3 s Cable Pair Identification: 65 s Talking father: 3 s Talking - User Loop Sub: 600 s Talking - Line Reverse Sub: 5 s Talking - Private Meter Pulse Sub: 6 s Talking - Ring Subscriber Sub: 60 s Talking - DP/DTMF signal Sub: 60 s ISDN Loop Back: 15 s

TAP 1108-26 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Single Line Test Session Configuration: Type-High With the type-high parameter the operator may indicate the following NBLT tests:

• •

•

•

•

•

• •

None: null Group: group test including following individual tests: • Foreign_AC_RMS_of_User_Circuit (Tip-Ring) • Foreign_AC_RMS_of_User_Circuit (Tip-Ground) • Foreign_AC_RMS_of_User_Circuit (Ring-Ground) • Foreign_DC_Voltage_of_User_Circuit (Tip-Ring) • Foreign_DC_Voltage_of_User_Circuit (Tip-Ground) • Foreign_DC_Voltage_of_User_Circuit (Ring-Ground) • Insulating_resistance_of_User_Circuit (Tip-Ring) • Insulating_resistance_of_User_Circuit (Ring-Tip) • Insulating_resistance_of_User_Circuit (Tip-Ground) • Insulating_resistance_of_User_Circuit (Ring-Ground) • Capacitance_of_User_Circuit (Tip-Ring) • Capacitance_of_User_Circuit (Tip-Ground) • Capacitance_of_User_Circuit (Ring-Ground) Feeded-ac-vol: Feeded AC RMS voltage test including following individual tests: • Feeded_AC_RMS_Voltage_of_User_Circuit (Tip-Ring) • Feeded_AC_RMS_Voltage_of_User_Circuit (Tip-Ground) • Feeded_AC_RMS_Voltage_of_User_Circuit (Ring-Ground) Foreign-ac-vol: Foreign AC RMS voltage test including following individual tests: • Foreign_AC_RMS_Voltage_of_User_Circuit (Tip-Ring) • Foreign_AC_RMS_Voltage_of_User_Circuit (Tip-Ground) • Foreign_AC_RMS_Voltage_of_User_Circuit (Ring-Ground) Feeded-dc-vol: Feeded DC voltage test including following individual tests: • Feeded_DC-Voltage_of_User_Circuit (Tip-Ring) • Feeded_DC-Voltage_of_User_Circuit (Tip-Ground) • Feeded_DC-Voltage_of_User_Circuit (Ring-Ground) • Feeded_DC-Voltage_of_User_Circuit (Ring-Tip) Foreign-dc-vol: Foreign DC voltage test including following individual tests: • Foreign_DC-Voltage_of_User_Circuit (Tip-Ring) • Foreign_DC-Voltage_of_User_Circuit (Tip-Ground) • Foreign_DC-Voltage_of_User_Circuit (Ring-Ground) Feeding-current: Feeding current test Resistance: Insulating Resistance test including following individual tests: • Insulating_resistance_of_User_Circuit (Tip-Ring) • Insulating_resistance_of_User_Circuit (Ring-Tip) • Insulating_resistance_of_User_Circuit (Tip-Ground) • Insulating_resistance_of_User_Circuit (Ring-Ground) • Insulating_resistance_BAT_of_User_Circuit (Ground-Tip) • Insulating_resistance_BAT_of_User_Circuit (Ground-Ring)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-27 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

•

•

• • •

Capacitance: Capacitance test including following individual tests: • Capacitance_of_User_Circuit (Tip-Ring) • Capacitance_of_User_Circuit (Ring-Tip) • Capacitance_of_User_Circuit (Tip-Ground) • Capacitance_of_User_Circuit (Ring-Ground) Impedance: Impedance test including following individual tests: • Impedance_of_User_Circuit (Tip-Ring) • Impedance_of_User_Circuit (Ring-Tip) • Impedance_of_User_Circuit (Tip-Ground) • Impedance_of_User_Circuit (Ring-Ground) Low-capacit-phone: Low capacitance phone test Dialton-delay: Dial tine delay test of User circuit (only in idle state Msocket-detection: Termination (m_socket detection) test

Single Line Test Session Configuration: Type-Low With the type-low parameter the operator may indicate the following NBLT tests:

• •

•

• • • • • • • • • • •

None: null AC-Current: AC Current test including the following individual tests: • AC_Current_of_user_Circuit (Tip-Ring) • AC_Current_of_user_Circuit (Tip-Ground) • AC_Current_of_user_Circuit (Ring-Ground) DC-Current: DC Current test including the following individual tests: • DC_Current_of_User_Circuit (Tip-Ring) • DC_Current_of_User_Circuit (Tip-Ground) • DC_Current_of_User_Circuit (Ring-Ground) Noise-level: Noise Level test Howler: Howler Tone test Status-Monitored: Status Monitored test Cable-Pair-Ident: Cable pair identification test Talking-Father: Talking test (father test item) Line-Reverse-Sub: Line reverse test; subtest of talking test P-Meter-Pulse-Sub: Private meter pulse test; subtest of talking test Ring-Subscrib-Sub: Ring subscriber with auto ring test; subtest of talking test Dpdtmf-signal-sub: dp/dtmf signal test; subtest of talking test Userloop-Sub: Resistance of user loop (tip-ring); subtest of talking test Isdn-loopback: isdn loop-back test

Allowed Type-High / Type Low parameter combinations

TAP 1108-28 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Msocket-detection

Impedance

Capacitance

Resistance

Feeding-current

Foreign-dc-vol

Feeded-dc-vol

Foreign-ac-vol

Feeded-ac-vol

Group

None

Low

Dialton-delay

High

Low-capacitance-phone

Table TAP 1108-9: Allowed Type-High / Type Low parameter combinations

None

IR

A

A

A

A

A

A

A

A

A

A

A

A

Ac-current

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Dc-current

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Noise-level

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Howler

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Status-monitored

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Cable-pair-ident

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Talking-father

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Line-reverse-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

p-meter-pulse-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Ring-subscriber-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Dpdtmf-signal-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Userloop-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Isdn-Loopback

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

IR: Irrelevant A: Allowed NA: Not allowed

Single Line Test Session Configuration: Test modes The following test modes are supported:

• • •

single: the integrated NBLT is executed once. interactive: the interactive integrated NBLT. cablepair: the cable pair test

Single Line Test Parameter Configuration: test names The following test types are supported:

• • • • •

feeded-ac-tr(mv): feeded AC RMS voltage of user circuit (tip-ring) feeded-ac-tg(mv): feeded AC RMS voltage of user circuit (tip-ground) feeded-ac-rg(mv): feeded AC RMS voltage of user circuit (ring-ground) foreign-ac-tr(mv): foreign AC RMS voltage of user circuit (tip-ring) foreign-ac-tg(mv): foreign AC RMS voltage of user circuit (tip-ground)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-29 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

foreign-ac-rg(mv): foreign AC RMS voltage of user circuit (ring-ground) feeded-dc-tr(mv): feeded DC voltage of user circuit (tip-ring) foreign-dc-tr(mv): foreign DC voltage of user circuit (tip-ring) foreign-dc-tg(mv): foreign DC voltage of user circuit (tip-ground) foreign-dc-rg(mv): foreign DC voltage of user circuit (ring-ground) feed-current(ua): feeding current (tip-ring) feeded-dc-rt(mv): feeded DC voltage of user circuit (ring-tip) resist-tr(ohm): insulating resistance of user circuit (tip-ring) resist-rt(ohm): insulating resistance of user circuit (ring-tip) resist-tg(ohm): insulating resistance of user circuit (tip-ground) resist-rg(ohm): insulating resistance of user circuit (ring-ground) resist-tbat(ohm): insulating battery resistance of user circuit (tip-bat) resist-rbat(ohm): insulating battery resistance of user circuit (ring-bat) capacitanc-tr(nf): capacitance of user circuit (tip-ring) capacitanc-rt(nf): capacitance of user circuit (ring-tip) capacitanc-tg(nf): capacitance of user circuit (tip-ground) capacitanc-rg(nf): capacitance of user circuit (ring-ground) impedance-tr(ohm): impedance of user circuit (tip-ring) impedance-tg(ohm): impedance of user circuit (tip-ground) impedance-rg(ohm): impedance of user circuit (ring-ground) low-capacit-phone: low capacitance phone detect bat-imped-discard: battery impedance (ring-bat) discarded dialton-delay(ms): dial tone delay of user circuit (only in idle state) msocket-detection: termination (m socket) detection ac-current-tr(ua): AC current normal test (tip-ring) ac-current-tg(ua): AC current normal test (tip-ground) ac-current-rg(ua): AC current normal test (ring-ground) dc-current-tr(ua): DC current normal test (tip-ring) dc-current-tg(ua): DC current normal test (tip-ground) dc-current-rg(ua): DC current normal test (ring-ground) noise-lv-0.001dbm: noise level normal test howler-test-park: Howler tone test under normal test condition (only in parking) status-monitored: status monitored test cable-pair-ident: cable pair identification test talking-father: talking test (father test item) line-reverse-sub: line reverse test; subtest of talking test p-meter-pulse-sub: private meter pulse test; subtest of talking test ring-subscrib-sub: ring subscriber with auto ring test; subtest of talking test dpdtmf-signal-sub: dp/dtmf signal test; subtest of talking test userloop-sub(ohm): resistance of user loop (tip-ring); subtest of talking test feeded-dc-tg(mv): feeded DC voltage of user circuit (tip-ground) feeded-dc-rg(mv): feeded DC voltage of user circuit (ring-ground) impedance-rt(ohm): impedance of user cicuit (ring-tip) isdn-loopback: ISDN Loop Back

TAP 1108-30 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Prerequisites The following prerequisites must be fulfilled before the NBLT test can be started:

•

The target board must be operational

Procedure All the configuration related to the integrated Line Test needs to be executed on the Hub node of the Voice Cluster only. Proceed as follows to configure the Integrated Line Test: 1

Fulfill conditions for NBLT; see Table TAP 1108-10. Table TAP 1108-10: Conditions for NBLT

NBLT Test

Type

Pre-NBLT Condition to be fulfilled

MID-NBLT condition to be fulfilled

Post-NBLT condition to be fulfilled

Type = High Group test

E

Ref. Individual NBLT tests

Ref. Individual NBLT tests

Ref. Individual NBLT tests

Feeded AC Voltage

E

4, 5 ,6*

None

None

Foreign AC Voltage

E

1, 2, 3, 4, 5

None

None

Feeded DC Voltage

E

4, 5 ,6*

None

None

Foreign DC Voltage

E

1, 2, 3, 4, 5

None

None

Feeding Current

E

4, 5, 6*

None

None

Resistance

E

1, 2, 3, 4, 5

None

None

Capacitance

E

1, 2, 3, 4, 5

None

None

Impedance

E

1, 2, 3, 4, 5

None

None

Low Capacitance Phone

E

1, 2, 3, 4, 5

None

None

DT

4

None

None

E

1, 2, 3, 4

None

None

AC Current

E

1, 2, 3, 4, 5

None

None

DC Current

E

1, 2, 3, 4, 5

None

None

Noise Level

E

1, 2, 3, 4, 5

None

None

Howler Tone

HT

5

None

None

Status Monitoring

SM

1, 2, 3, 4, 5, 6

None

None

Cable Pair Identification

CPI

1, 2, 3, 4, 5

None

NBLT Session time-out

Talking Father - Line Reverse Sub

TSTO

6

None

NBLT Session time-out

Talking Father - Private Meter Pulse Sub

TSTO

6

None

None

Dialtone Delay Msocket detection Type = Low

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-31 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

NBLT Test

Type

Pre-NBLT Condition to be fulfilled

MID-NBLT condition to be fulfilled

Post-NBLT condition to be fulfilled

Talking Father - Ring Subscriber Sub

TSTO

6

Terminate Call prior to the start of the Ring Subscriber Sub

None

Talking Father - DT DTMF signal Sub

TSTD

6

Press digits after having started the DP DTMF Signal Sub

None

Talking Father - Userloop Sub

TSTO

6

None

None

IL

4, 5

None

None

ISDN Loop-Back (2 of 2)

(1): Termination not provisioned (2): Termination provisioned / administratively locked (3): Termination provisioned / administratively unlocked / (4): Termination provisioned / administratively unlocked / (5): Termination provisioned / administratively unlocked / (6): Termination provisioned / administratively unlocked / (*): 72 lines voice LT board only

2

operationally down operationally up / idle state operationally up / parking state operationally up / busy state

Show the next available session for integrated line test with the following command: show linetest cluster (cluster-id) avail-sess

Note — This step checks whether a session is available and returns the maximum number of sessions supported together with the available session identifier number with which NBLT can be configured. 3

Configure the session parameters with the following command: configure linetest cluster (cluster-id) ltsession (sessionid) session-cmd ownerid timeout-period line-num type-high type-low test-parm-num test-mode

TAP 1108-32 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

Note 1 — For a description of the NBLT session parameters, see “CLI NBLT parameter description”. Note 2 — The following integrated NBLT can be terminated by operator command:

• • • • • • • • • 4

AC Current DC Current Noise Level Howler Ring subscriber with Auto ring Line Reverse Talking with Subscriber DP/DTMF Signal Cable pair identification tone

Configure the line parameters with the following command: configure linetest cluster (cluster-id) ltline (sessionid) lineid line-status

5

Configure the parameters with the following command: configure linetest cluster (cluster-id) ltparm (sessionid) test-name(unit) value1 value2 value3 value4 value5

Note 1 — For a description of the MEGACO line test parameters, see “CLI NBLT parameter description”. Note 2 — The parameters min-threshold and max-threshold are disabled. 6

Run the NBLT with the following command: configure linetest cluster (cluster-id) ltsession (sessionid) session-cmd starttest

7

Show session parameters with the following command: show linetest cluster (cluster-id) ltsession [(sessionid)]

8

Show all parameters on a specific line id of a session with the following command: show linetest cluster (cluster-id) ltline [(sessionid) [lineid ]]

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-33 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

9

Show Integrated Line Test Report with the following command: show linetest cluster (cluster-id) lineid-ext-rept [(sessionid)] lineid test-name(unit) result-index

10

STOP. This procedure is complete. Type-HIGH NBLT examples: 1 GROUP TEST. 1.1 Line is in idle state: call-status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 1.2 Show the available Session. show linetest cluster 1 avail-sess 1.3 Start the Group test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high group type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 1.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 2 FEEDED-AC-VOL 2.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 2.2 Show the available Session. show linetest cluster 1 avail-sess

TAP 1108-34 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

2.3 Start the Feeded AC Voltage test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high feeded-ac-vol type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 2.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 3 FOREIGN-AC-VOL. 3.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 3.2 Show the available Session. show linetest cluster 1 avail-sess 3.3 Start the Foreign AC Voltage test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high foreign-ac-vol type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 3.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 4 FEEDED-DC-VOL. 4.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 4.2 Show the available Session. show linetest cluster 1 avail-sess Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-35 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

4.3 Start the Feeded DC Voltage test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high feeded-dc-vol type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 4.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 5 FOREIGN-DC-VOL. 5.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 5.2 Show the available Session. show linetest cluster 1 avail-sess 5.3 Start the Foreign DC Voltage test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high foreign-dc-vol type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 5.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 6 FEEDING-CURRENT. 6.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 6.2 Show the available Session. show linetest cluster 1 avail-sess TAP 1108-36 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

6.3 Start the Feeding Current test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high feeding-current type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 6.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 7 RESISTANCE. 7.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 7.2 Show the available Session. show linetest cluster 1 avail-sess 7.3 Start the Resistance test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high resistance type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 7.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 8 CAPACITANCE. 8.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 8.2 Show the available Session. show linetest cluster 1 avail-sess Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-37 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

8.3 Start the Capacitance test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high capacitance type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 8.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 9 IMPEDANCE. 9.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 9.2 Show the available Session. show linetest cluster 1 avail-sess 9.3 Start the Impedance test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high impedance type-low none test-parm-num 1 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltparm 1 test-name(unit) impedance-tr(ohm) value1 20 value2 15 configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 9.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 10 LOW-CAPACIT-PHONE. 10.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]]

TAP 1108-38 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

10.2 Show the available Session. show linetest cluster 1 avail-sess 10.3 Start the Low Capacity Phone test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high low-capacit-phone type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 10.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 11 DIALTON-DELAY. 11.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 11.2 Show the available Session. show linetest cluster 1 avail-sess 11.3 Start the Dialton-Delay test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high dialton-delay type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 11.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 12 MSOCKET-DETECTION. 12.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-39 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

12.2 Show the available Session. show linetest cluster 1 avail-sess 12.3 Start the Msocket-Detection test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high msocket-detection type-low none test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 12.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy Type-LOW NBLT examples: 13 AC CURRENT. 13.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 13.2 Show the available Session. show linetest cluster 1 avail-sess 13.3 Start the AC Current test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low ac-current test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 13.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 14 DC CURRENT. 14.1 Line is in idle state: call- status = on-hook & test-status

TAP 1108-40 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

= no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 14.2 Show the available Session. show linetest cluster 1 avail-sess 14.3 Start the DC Current test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low dc-current test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 14.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 15 NOISE LEVEL 15.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 15.2 Show the available Session. show linetest cluster 1 avail-sess 15.3 Start the Noise Level test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low noise-level test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 15.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 16 HOWLER TONE

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-41 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

16.1 Line is in parking state: call- status = idle-off-key & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 16.2 Show the available Session. show linetest cluster 1 avail-sess 16.3 Start the Howler Tone test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low howler test-parm-num 0 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 16.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 17 STATUS MONITORING 17.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 17.2 Show the available Session. show linetest cluster 1 avail-sess 17.3 Start the Status Monitoring test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low status-monitored test-parm-num 1 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltparm 1 test-name(unit) status-monitored value1 1 configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1

TAP 1108-42 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

17.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 18 CABLE PAIR IDENTIFICATION. 18.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 18.2 Show the available Session. show linetest cluster 1 avail-sess 18.3 Start the Cable Pair Identification test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low cable-pair-ident test-parm-num 0 test-mode cablepair configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest For this NBLT test, one has to await the timeout of the NBLT session to get the result of the NBLT test. show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 18.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 19 TALKING FATHER 19.1 Line Reverse Sub. 19.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 19.1.2 Show the available Session. show linetest cluster 1 avail-sess

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-43 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

19.1.3 Start the Talking Father test configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest 19.1.4 Start the Line-Reverse Sub With a multi-meter instrument, one can measure a voltage reversal every 5 seconds. configure linetest cluster 1 ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low line-reverse-sub test-parm-num 0 test-mode interactive configure linetest cluster 1 ltsession 1 session-cmd start-subtest For this NBLT test, one has to await the timeout of the NBLT session to get the result of the NBLT test. show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 19.1.5 Free the NBLT session. NBLT session freed to Time-Out. 20 TALKING FATHER. 20.1 Private Meter Pulse Sub 20.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 20.1.2 Show the available Session. show linetest cluster 1 avail-sess 20.1.3 Start the Talking Father test configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest

TAP 1108-44 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

20.1.4 Start the Private-Meter-Pulse Sub. configure linetest cluster 1 ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low p-meter-pulse-sub test-parm-num 1 test-mode interactive configure linetest single ltparm test-name(unit) p-meter-pulse-sub value1 1 configure linetest cluster 1 ltsession 1 session-cmd start-subtest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 20.1.5 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 21 TALKING FATHER. 21.1 Ring Subscriber Sub. 21.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 21.1.2 Show the available Session. show linetest cluster 1 avail-sess 21.1.3 Start the Talking Father test configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest 21.1.4 Terminate call (Put phone on-hook) Put only the phone on-hook for the line on which one intends to do the ring test. Applied to the above example: put the phone for line 1/1/1/1/2 on-hook but do not put the phone for line 1/1/1/4 on-hook! Reason: In the above example, first of all the phone for line 1/1/1/1/2 is put on-hook. In a next step the ring test is performed. Now one can hear the line 1/1/1/1/2 is ringing. Then when going off-hook on line 1/1/1/1/2, one still find line 1/1/1/1/2 and line 1/1/1/1/4 being in conversation. Thus, do not put the phone for line 1/1/1/4 on-hook. show voice sip termination

[(if-index)]

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-45 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

21.1.5 Start the Ring Subscriber Sub. configure linetest cluster 1 ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low ring-subscrib-sub test-parm-num 0 test-mode interactive configure linetest cluster 1 ltsession 1 session-cmd start-subtest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 21.1.6 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 22 TALKING FATHER. 22.1 DP DTMF Signal Sub. 22.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 22.1.2 Show the available Session. show linetest cluster 1 avail-sess 22.1.3 Start the Talking Father test configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest 22.1.4 Start the DP DTMF Signal Sub configure linetest cluster 1 ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low dpdtmf-signal-sub test-parm-num 1 test-mode interactive configure linetest cluster 1 ltparm 1 test-name(unit) dpdtmf-signal-sub value1 6 configure linetest cluster 1 ltsession 1 session-cmd start-subtest 22.1.5 Press digits. show linetest cluster 1 lineid-ext-rept 1 22.1.6 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy TAP 1108-46 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1108 — Integrated NBLT for MEGACO Termination

23 TALKING FATHER. 23.1 Userloop Sub. 23.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 23.1.2 Show the available Session. show linetest cluster 1 avail-sess 23.1.3 Start the Talking Father test configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltsession 1 session-cmd starttest 23.1.4 Start the User Loop Sub. configure linetest cluster 1 ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low userloop-sub test-parm-num 0 test-mode interactive configure linetest cluster 1 ltsession 1 session-cmd start-subtest show linetest cluster 1 lineid-ext-rept 1 23.1.5 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy 24 ISDN LOOP-BACK. 24.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice cluster (cluster-id) termination [(equip-id) [port-id]] 24.2 Show the available Session. show linetest cluster 1 avail-sess

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1108-47 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1108 — Integrated NBLT for MEGACO Termination

24.3 Start the ISDN-Loopback test. configure linetest cluster 1 ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low isdn-loopback test-parm-num 1 test-mode single configure linetest cluster 1 ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest cluster 1 ltparm 1 test-name(unit) isdn-loopback value1 1 configure linetest cluster 1 ltsession 1 session-cmd starttest show linetest cluster 1 ltline 1 show linetest cluster 1 lineid-ext-rept 1 24.4 Free the NBLT session. configure linetest cluster 1 ltsession 1 session-cmd destroy

TAP 1108-48 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination Purpose This document provides the steps to configure integrated Narrow Band Line Test (NBLT) parameters for SIP terminations.

General Integrated Line testing of voice subscriber ports is part of a management activity which is performed by the operator in order to provide loop pre-qualification and maintenance of the network. Usually, tests can be performed on a routine basis (mainly at night with scheduled facility) or on demand (required by an operator command). The test procedure described in this TAP intends to support inward test, outward test, terminal test and sub-items test (interactive). Integrated Line Test requests will indicate the test to be performed and may indicate the resource(s) to be tested and the timeout period. The Integrated line testing is recommended to be executed by means of the Alcatel-Lucent 5530 Network Analyzer (5530 NA), a professional failure diagnose product. Nevertheless, the ISAM Voice also provides the capability of performing integrated lines test directly by CLI commands initiated by the operator. Since the integrated line test is an interactive process, usually multiple commands need to be executed for a single test case. The involved elements outside the access node include subscriber analogue terminal, i.e. the telephone set in subscriber assisted tests such as Pulse/ DTMF dialling, etc. To evaluate whether a test is passed or failed, a predefined threshold value is used unless the test request contains threshold values, which override the predefined thresholds. The threshold carried in the request applies only for the test itself. After the completion of that test the predefined thresholds shall be restored.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

The Access Node model At access node side, the 2 wires of a twisted pair are connected to a battery (e.g. 48V, 60 V) through a source impedance (typically 300 Ohm in each wire). This source impedance matches the line impedance and isolates the voice signal from the battery. Figure TAP 1109-1: Access node model

Historically, the source impedance was made of relay coils (known as the 'A' relay). When the phone goes off-hook, the current starts flowing and activates the relays contacts. Those contacts were used to switch the voice signal to the line, via audio coupling capacitors. The positive side of the battery is grounded, so only one of the two wires has a negative potential with regards to the earth. The line voltage was selected to be negative to make the electrochemical reactions on the wet telephone wiring to be less harmful. When the wires are at negative potential compared to the ground the metal ions go from the ground to the wire instead of the situation where positive voltage would cause metal from the wire to leave which causes quick corrosion. The 'positive' wire is called TIP (or A wire) while the 'negative' wire is called RING (or B wire). The terms Tip and Ring originate from the telephone operators' phone plug, which were used in the early days of telephony with operators manually handling customer calls. The names of the wires are derived from the part of the plug to which they were connected

The line model As every transmission line, a phone line can be seen as a cascade of very short RLCG circuits.

TAP 1109-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination Figure TAP 1109-2: Line model

For a single, infinitely short element, the resistance, inductance, capacitance and conductance can be expressed in units relative to the length. As the model assumes that the distributed values are uniform along the line, the total loop characteristics can be obtained by multiplying the per-unit length resistance, inductance, capacitance and conductance by the loop length.

•

•

•

•

Per-unit length resistance (R): The value of this parameter depends on the material conductivity and the wire diameter. For example, the resistance of an AWG24 copper wire is 84 Ohm/km (at 25°C). Per-unit length capacitance (C): The value of this parameter depends on the cable geometry (wires diameter and spacing) and on the dielectric permittivity (epsilon). For the most common type of cables, the typical value is 50nF/km. This value is directly related to the characteristic impedance of the cable. As the majority of the cables are designed on the same characteristic impedance, independently of the wire gauge, the wire capacitance is, at the first order of magnitude, also independent of the wire type. Per-unit length inductance (L): The per-unit length inductance parameter is a function of the cable geometry and of the medium permeability (µ). Typically, the value of the inductance is 0.5mH/km or less. This parameter is typically not measured for POTS troubleshooting. Per-unit length conductance (G): This parameter is related to the insulating resistance between the two wires (the conductance being the inverse of the resistance). The parameter is a function of the dielectric strength and on the wire spacing. Although the unit of conductance is Siemens (S = Ohm^-1), the cable insulation is often expressed as a product of a resistance and a distance (e.g. 800 Mohm per km).

Session Management • • • •

ISAM Voice allows to include all subscriber lines of a voice LT board in an integrated NBLT session (POTS LT board: 48/72 lines). The maximum number of simultaneous integrated NBLT sessions that can run on an access node shall not exceed 16. Only 1 integrated NBLT session can run at a time on a voice LT board. In case multiple subscriber lines of the same Voice LT board are involved in an integrated NBLT session, then the access node shall execute the NBLT for each of the subscriber lines connected to a single voice LT board in a sequential way.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

•

•

ISAM Voice has introduced a session time out mechanism. When one session is created, a configurable timer (default = 30 minutes) will be started. Should no new management input be received for this NBLT session till timer expiry, then this NBLT session will be autonomously destroyed by the system. The session time-out is re-started upon the receipt of a new input command for the associated NBLT session ISAM Voice has introduced a session time out mechanism. Prior to R4.1.03, if a NBLT session is created and no operator triggered management operation is received during the session states “revcmd” or “revinfo” during a period of 30 minutes, then the system will autonomously drop the NBLT session. This inactivity timer is hard-coded to 30 minutes. From R4.1.03 onwards, a configurable “session Inactive timer” object has been introduced in the Line Test Session Table. The inactive timer is applied to all session states except the “Run_Cmd” session state (session state set whilst NBLT test is running). A NBLT Session will autonomously be dropped by the system if, once the NBLT session as been created, no operator triggered management operation is received during a period equals the configured session inactivity timer. Any received SNMP GET or SET operation results in a restart of the timer. Should no value be configured for the session inactivity timer then the system will assume a session inactivity timer = 0, meaning that the NBLT session is never autonomously dropped by the system.

Subscriber Line Management •

• •

TAP 1109-4

When an integrated NBLT (inwards and/or outwards line testing) is running for a particular subscriber line, then this subscriber line shall be blocked for incoming and outgoing calls. In case the integrated NBLT is running at the calling side, no dial tone shall be sent when the subscriber goes off-hook. In case the integrated NBLT is running at the called side, busy tone shall be sent to the calling side. Once the integrated NBLT has been completed on a particular subscriber line, this subscriber line shall be put back in the operational state it had before the integrated NBLT was started. Running the integrated NBLT on a particular subscriber line shall not cause any influence on the voice service offering and quality of the other subscriber lines connected to the same access node.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

•

Configuration changes initiated by the operator while NBLT test is running at one or more subscriber lines might cause a considerable difference in time at which the protocol related action is initiated and the time at which the internal state (operational state) / physical state (e.g. power off/on) of the line is changed. For lines under test, such approach may cause a temporarily inconsistent state between the line state maintained at the server/softswitch and the line state maintained at the access node. However, it is assumed that such existing inconsistency during the NBLT test phase will not decline the voice service quality after the NBLT test been completed on the line. • While running the integrated NBLT on a particular subscriber line, it is not allowed to initiate administrative state changes for this subscriber line. Such management commands are rejected and replied with a response code saying that the subscriber line is under test. • While running the integrated NBLT on a particular subscriber line, it is allowed to initiate configuration changes that do not require a lock/unlock of the administrative state (Ref. SIP configuration Detailed Level procedure). Such management commands are accepted and processed even if a subscriber line is under test. • While running the integrated NBLT on a particular subscriber line and the administrative state already being locked, it is allowed to initiate configuration changes that require a lock/unlock of the administrative state (Ref. SIP configuration Detailed Level procedure). Such management commands are accepted and processed even if a subscriber line is under test. (the integrated NBLT can be started on a subscriber line irrespective of the administrative state being set at that moment). • While running the integrated NBLT on a particular subscriber line and having executed the following sequence of configuration commands: (1) Lock SIP UA / SIP UAAP / SIP VSP table, (2) Configuration change of one or more SIP UA / SIP UAAP / SIP VSP table objects, (3) Unlock SIP UA / SIP UAAP / SIP VSP table, finally causing a de-register followed by a register of all subscriber lines, the following behavior is adopted by the ISAM Voice - SIP protocol wise, ISAM-V initiates the de-register and register requests for all subscriber lines immediately to the IMS core network irrespective of whether a subscriber line is under test or not. - From an internal operational state handling perspective, for those subscriber lines that are under test, any operational state change caused by the afore described management command sequence execution is postponed till the integrated NBLT has completed • While running the integrated NBLT on a particular subscriber line and having executed the following sequence of configuration commands: (1) Lock SIP UA / SIP UAAP / SIP VSP table, (2) Configuration change of one or more SIP UA / SIP UAAP / SIP VSP table objects, (3) Unlock SIP UA / SIP UAAP / SIP VSP table, finally causing a the LT board to reset as to make the new configuration changes effective, the following behavior is adopted by the ISAM Voice: - SIP protocol wise, ISAM-V initiates a de-register request for all subscriber lines immediately to the IMS core network irrespective of whether a subscriber line is under test or not. - From an internal operational state handling perspective, for those subscriber lines that are under test, any operational state change caused by the de-registering is postponed till the integrated NBLT has completed. - The system triggers immediately a board reset irrespective of whether a subscriber line is running the integrated NBLT test or not.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

- Due to this board reset the integrated NBLT test has been aborted. - ISAM-V initiates register requests for all subscriber lines to the IMS core network.

SNMP versus CLI A first major difference between the SNMP and the CLI management interfaces is the configuration of the NBLT Type-High and the NBLT Type-Low parameters. For SNMP: the NBLT test types can individually and freely be configured considering the above mentioned object definitions and the integrated NBLT feature policies. In case of H.248 NBLT: A maximum of 24 NBLT test types (must all be of the same category) may be defined in one NBLT session command. (The reason is that otherwise (should more than 24 NBLT test types been requested) the maximum size of the XLES message (256 bytes) is not sufficient to contain all test results. Such occurrence would cause the XLES path to be lost between the NVPS and the voice LT board). For CLI: A set of predefined NBLT test sets is offered as to achieve a more operator friendly management interface. The content of these NBLT test sets is fixed. 1. NBLT Type-High: 12 NBLT test sets defined:

•

•

•

•

TAP 1109-6

Group: group test including following individual tests: • Foreign_AC_RMS_of_User_Circuit (tr) • Foreign_AC_RMS_of_User_Circuit (tg) • Foreign_AC_RMS_of_User_Circuit (rg) • Foreign_DC_Voltage_of_User_Circuit (tr) • Foreign_DC_Voltage_of_User_Circuit (tg) • Foreign_DC_Voltage_of_User_Circuit (rg) • Insulating_resistance_of_User_Circuit (tr) • Insulating_resistance_of_User_Circuit (rt) • Insulating_resistance_of_User_Circuit (tg) • Insulating_resistance_of_User_Circuit (rg) • Capacitance_of_User_Circuit (tr) • Capacitance_of_User_Circuit (tg) • Capacitance_of_User_Circuit (rg) Feeded-ac-vol: Feeded AC RMS voltage test including following individual tests: • Feeded_AC_RMS_Voltage_of_User_Circuit (tr) • Feeded_AC_RMS_Voltage_of_User_Circuit (tg) • Feeded_AC_RMS_Voltage_of_User_Circuit (rg) Foreign-ac-vol: Foreign AC RMS voltage test including following individual tests: • Foreign_AC_RMS_Voltage_of_User_Circuit (tr) • Foreign_AC_RMS_Voltage_of_User_Circuit (tg) • Foreign_AC_RMS_Voltage_of_User_Circuit (rg) Feeded-dc-vol: Feeded DC voltage test including following individual tests: • Feeded_DC_Voltage_of_User_Circuit (tr) • Feeded_DC_Voltage_of_User_Circuit (tg) • Feeded_DC_Voltage_of_User_Circuit (rg) • Feeded_DC_Voltage_of_User_Circuit (rt)

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

•

• •

•

•

• • •

Foreign-dc-vol: Foreign DC voltage test including following individual tests: • Foreign_DC-Voltage_of_User_Circuit (tr) • Foreign_DC-Voltage_of_User_Circuit (tg) • Foreign_DC-Voltage_of_User_Circuit (rg) Feeding-current: Feeding current test Resistance: Insulating Resistance test including following individual tests: • Insulating_resistance_of_User_Circuit (tr) • Insulating_resistance_of_User_Circuit (rt) • Insulating_resistance_of_User_Circuit (tg) • Insulating_resistance_of_User_Circuit (rg) • Insulating_resistance_BAT_of_User_Circuit (gt) • Insulating_resistance_BAT_of_User_Circuit (gr) Capacitance: Capacitance test including following individual tests: • Capacitance_of_User_Circuit (tr) • Capacitance_of_User_Circuit (rt) • Capacitance_of_User_Circuit (tg) • Capacitance_of_User_Circuit (rg) Impedance: Impedance test including following individual tests: • Impedance_of_User_Circuit (tr) • Impedance_of_User_Circuit (rt) • Impedance_of_User_Circuit (tg) • Impedance_of_User_Circuit (rg) Low-capacit-phone: Low capacitance phone test Dialton-delay: Dial tine delay test of User circuit (only in idle state) Msocket-detection: Termination (m_socket detection) test

2. NBLT Type-Low: 14 NBLT test sets defined:

•

•

• • • • • • • • • •

AC-Current: AC Current test including the following individual tests: • AC_Current_of_user_Circuit (tr) • AC_Current_of_user_Circuit (tg) • AC_Current_of_user_Circuit (rg) DC-Current: DC Current test including the following individual tests: • DC_Current_of_User_Circuit (tr) • DC_Current_of_User_Circuit (tg) • DC_Current_of_User_Circuit (rg) Noise-level: Noise Level test Howler Tone: Howler Tone test Status-Monitored: Status Monitored test Cable-Pair-Ident: Cable pair identification test Talking-Father: Talking test (father test item) Line-Reverse-Sub: Line reverse test; subtest of talking test P-Meter-Pulse-Sub: Private meter pulse test; subtest of talking test Ring-Subscrib-Sub: Ring subscriber with auto ring test; subtest of talking test Dpdtmf-signal-sub: dp/dtmf signal test; subtest of talking test Userloop-Sub: Resistance of user loop (tip-ring); subtest of talking test

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

• •

Electronic Ringer Detection (72 lines board only): Test used to measure the resistance and capacitance of a ringer circuit in phone sets. Longitudinal Current: Longitudinal current

In general, the ISAM Voice Allows to execute the integrated NBLT under the following modes:

• • • •

•

Single: The integrated NBLT is executed once. Interactive: the integrated NBLT is executed interactively between the system and the operator. Cablepair: to execute the cable pair test. Block: The system autonomously executes the integrated NBLT 20 times (after having received the “starttest” command). The results of all 20 NBLT iterations can be retrieved after the “en block” integrated line test has been completed. The “Block” mode applies to the following test types: Foreign Voltage (AC/DC), Capacitance, and Insulation Resistance test. Continuous: The integrated NBLT can be infinite times repeated. However, the system shall not autonomously repeat the integrated line test. If repetition is required, the operator must send a repeat command each time a new iteration of the integrated NBLT would be required. It is important that the test results of the previous iteration are retrieved by the operator before the new iteration is requested as otherwise the results of the previous iteration will be overwritten by the results of the last iteration. The “Continuous” mode applies to the following test types: Foreign Voltage (AC/DC), Capacitance, and Insulation Resistance test.

A second major difference between the SNMP and the CLI management interfaces are the BLOCK and CONTINUOUS test modes:

•

•

The BLOCK test mode is applicable to each of the test items in the categories “Electric”. When using the block test mode, the single test item is 20 times repeated. The system buffers all 20 test results for output after the test is finished. The CONTINUOUS test mode is applicable to each of test items in the categories “Electric”. When using the continuous test mode, the test session will not be destroyed after one test cycle is finished. The management platform can send a “repeat” to repeat to same test. Only one test result is buffered. As such, the management platform must retrieve the test result of the completed test cycle prior to the launch of the “repeat” command.

Both the BLOCK and CONTINUOUS test mode can only be applied to one test item at a time. Since the CLI management interface groups several individual test types into predefined test sets and as such only allow the customer to make use of these predefined test sets (individual test types cannot configured by means of the CLI management interface), both, the BLOCK and the CONTINUOUS test mode are NOT be supported by means of the CLI management interface.

Integrated NBLT Preconditions The Integrated NBLT supports the NBLT test types to run under different subscriber port conditions. TAP 1109-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Prior to R4.3: All electrical tests can be executed when the subscriber port's administrative status equals "unlocked", operational status equals "enabled" and Line status equals "Idle". From R4.3 onwards Table TAP 1109-1 applies for the 48-line voice LT board and the 72-line voice LT board.

Termination Not provisioned

Termination Provisioned Admin Locked

Termination Provisioned Admin Unlocked Operational Disabled

Termination Provisioned Admin: Unlocked Operational: Enabled Line state: Idle

Termination Provisioned Admin: Unlocked Operational: Enabled Line state: Parking

Test item/Status*

Foreign DC voltage (tr, tg, rg)

Y

Y

Y

Y

Y

Foreign AC voltage (tr, tg, rg)

Y

Y

Y

Y

Y

Capacitance (tr, tg, rg)

Y

Y

Y

Y

Y

Resistance (tr, rt, tg, rg)

Y

Y

Y

Y

Y

AC current (tr, tg, rg)

Y

Y

Y

Y

Y

DC current (tr, tg, rg)

Y

Y

Y

Y

Y

Cable pair identification

Y

Y

Y

Y

Y

Feeding voltage DC

Y

Y

Y

Feeding voltage AC

Y

Y

Y

Feeding current DC

Y

Y

Y Y

Longitudinal current DC

Y

Y

Y

Y

Y

Low capacitance phone detect

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

M-Socket (PPA)

detection (1)

Ringer detection Dial tone delay

Y

Y

Noise level

Y

Y

Y

Y

Y

Status check

Y

Y

Y

Y

Y

Howler tone

Y

Y

Talking tests Electronic Ringer Detection

Termination Provisioned Admin: Unlocked Operational Enabled Line state Busy

Table TAP 1109-1: Overview

Y Y

Y

Y

Y

Y

Locked: Port administratively locked by operator (that is, administrative state is down and operational state is down). Disabled: VoIP service is disabled, that is, the port is disabled due to an alarm or disconnected from the network side. The operational state is down. Notes (1) PPA detection test is not allowed in parking status.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination (2)

Feeding Voltage DC: Following conditions are only supported at the 72 lines voice LT board: Termination provisioned & admin unlocked & operational Enabled & Line State Busy

(3)

Feeding Voltage AC: Following conditions are only supported at the 72 lines voice LT board: Termination provisioned & admin unlocked & operational Enabled & Line State Busy

(4)

Feeding Current DC: Following conditions are only supported at the 72 lines voice LT board Termination provisioned & admin unlocked & operational Enabled & Line State Busy

(5)

Electronic Ringer Detection test is only supported on 72 lines voice LT board.

To allow the NBLT test types mentioned above to run for a non-provisioned port, the following minimum configuration requirements are required:

•

•

SIP Centralised Mode: • Configure internal integrated VoIP service L2/L3 topology at the SHub/IHub. • Configure NT OAM IP address and IP gateway. • Plan the Voice LT boards in the local access node. • Configure the internal integrated VoIP service L2/L3 topology at the voice LT boards. SIP Distributed Mode: • Configure internal integrated VoIP service L2 topology at the SHub/IHub. • Configure NT OAM IP address and IP gateway. • Plan the Voice LT boards in the local access node. • Configure the internal integrated VoIP service L2/L3 topology at the voice LT boards.

Integrated NBLT to voice LT board Mapping

Table TAP 1109-2: Integrated NBLT to voice LT board Mapping Integrated NBLT Test Type

48 lines POTS LT Board

72 lines POTS LT Board

H-Bit 31 : Feeded_AC_RMS_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 30 : Feeded_AC_RMS_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 29 : Feeded_AC_RMS_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 28 : Foreign_AC_RMS_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 27 : Foreign_AC_RMS_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 26 : Foreign_AC_RMS_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 25 : Feeded_DC_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 24 : Feeded_DC_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 23 : Feeded_DC_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 22 : Foreign_DC_Voltage_of_User_Circuit (tr)

Y

Y

H-Bit 21 : Foreign_DC_Voltage_of_User_Circuit (tg)

Y

Y

H-Bit 20 : Foreign_DC_Voltage_of_User_Circuit (rg)

Y

Y

H-Bit 19 : Feeding_Current

Y

Y

(1 of 3)

TAP 1109-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Integrated NBLT Test Type

48 lines POTS LT Board

72 lines POTS LT Board

H-Bit 18 : Feeded_DC_Voltage_of_User_Circuit (rt)

Y

Y

H-Bit 17 : Insulating_resistance_of_User_Circuit (tr)

Y

Y

H-Bit 16 : Insulating_resistance_of_User_Circuit (rt)

Y

Y

H-Bit 15 : Insulating_resistance_of_User_Circuit (tg)

Y

Y

H-Bit 14 : Insulating_resistance_of_User_Circuit (rg)

Y

Y

H-Bit 13 : Insulating_resistance_BAT_of_User_Circuit (gt)

Y

Y

H-Bit 12 : Insulating_resistance_BAT_of_User_Circuit (gr)

Y

Y

H-Bit 11 : Capacitance_of_User_Circuit (tr)

Y

Y

H-Bit 10 : Capacitance_of_User_Circuit (rt)

Y

Y

H-Bit 09 : Capacitance_of_User_Circuit (tg)

Y

Y

H-Bit 08 : Capacitance_of_User_Circuit (rg)

Y

Y

H-Bit 07 : Impedance_of_User_Circuit (tr)

Y

Y

H-Bit 06 : Impedance_of_User_Circuit (rt)

Y

Y

H-Bit 05 : Impedance_of_User_Circuit (tg)

Y

Y

H-Bit 04 : Impedance_of_User_Circuit (rg)

Y

Y

H-Bit 03 : Low_Capacitance_Phone_Detect

Y

Y

H-Bit 01 : Dial tone_delay_of_User_Circuit

Y

Y

H-Bit 00 : Termination_testing (M socket)

Y

Y

L-Bit 31 : AC_Current_of_user_Circuit (tr)

Y

Y

L-Bit 30 : AC_Current_of_user_Circuit (tg)

Y

Y

L-Bit 29 : AC_Current_of_user_Circuit (rg)

Y

Y

L-Bit 28 : DC_Current_of_User_Circuit (tr)

Y

Y

L-Bit 27 : DC_Current_of_User_Circuit (tg)

Y

Y

L-Bit 26 : DC_Current_of_User_Circuit (rg)

Y

Y

Y

Y

Y

Y

L-Bit 20 :Status_Monitored

Y

Y

L-Bit 19 : Cable_Pair_Identification

Y

Y

L-Bit 18 : Talking_Father

Y

Y

L-Bit 17 : Line_Reverse-Sub_Test

Y

Y

L-Bit 16 : Private_Meter_Pulse_Sub_Test

Y

Y

L-Bit 15 : Ring_Subscriber-Sub_Test with Auto Ring Test

Y

Y

H-Bit 02 : Reserved

L-Bit 25 : Reserved L-Bit 24 : Noise_level L-Bit 23 : Reserved L-Bit 22 : Howler Tone L-Bit 21 : Reserved

(2 of 3)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

Integrated NBLT Test Type

48 lines POTS LT Board

72 lines POTS LT Board

L-Bit 14 : DP/DTMF_Signal_Sub_test

Y

Y

L-Bit 13 : Resistance_of_user_Circuit

Y

Y

L-Bit 12 : Capacitance_of_Signature (Electronic Ringer Detection)

Y

L-Bit 11 : Resistance_of_Ringer (Electronic Ringer Detection)

Y

L-Bit 10 : N.A. L-Bit 09 : Longitudinal_Current_Test

Y

L-Bit 08 : Reserved L-Bit 07 : Reserved L-Bit 06 : Reserved L-Bit 05 : Reserved L-Bit 04 : Reserved L-Bit 03 : Reserved L-Bit 02 : Reserved L-Bit 01 : Reserved L-Bit 00 : Reserved (3 of 3)

Integrated NBLT Categories The integrated NBLT test types are split into the following categories:

• • • • • • • • • •

Category_00: Electric Category_01: Dial-Tone Category_02: Howler-Tone Category_03: Status-Monitored Category_04: Cable-Pair-Identity Category_05: Talking-Test Category_06: Talking-Sub-Test-DTMF Category_07: Talking-Sub-Test-Other Category_08: Electric-Only-In-Idle-Status Category_09: N.A.

Only integrated NBLT test types that belong to the same category can be executed in the same integrated NBLT session. NBLT Type_High: 1

Bit 31: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

2

Bit 30: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

3

Bit 29: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

4

Bit 28: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

5

Bit 27: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

TAP 1109-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

6

Bit 26: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric)

7

Bit 25: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric)

8

Bit 24: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric)

9

Bit 23: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric)

10 Bit 22: Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) 11 Bit 21: Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) 12 Bit 20: Foreign_DC_Voltage_of_User_Circuit (Cat_00: Electric) 13 Bit 19: Feeding_Current (Cat_00: Electric) 14 Bit 18: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric) 15 Bit 17: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 16 Bit 16: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 17 Bit 15: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 18 Bit 14: Insulating_resistance_of_User_Circuit (Cat_00: Electric) 19 Bit 13: Insulating_resistance_BAT_of_User_Circuit (Cat_00: Electric) 20 Bit 12: Insulating_resistance_BAT_of_User_Circuit (Cat_00: Electric) 21 Bit 11: Capacitance_of_User_Circuit (Cat_00: Electric) 22 Bit 10: Capacitance_of_User_Circuit (Cat_00: Electric) 23 Bit 09: Capacitance_of_User_Circuit (Cat_00: Electric) 24 Bit 08: Capacitance_of_User_Circuit (Cat_00: Electric) 25 Bit 07: Impedance_of_User_Circuit (Cat_00: Electric) 26 Bit 06: Impedance_of_User_Circuit (Cat_00: Electric) 27 Bit 05: Impedance_of_User_Circuit (Cat_00: Electric) 28 Bit 04: Impedance_of_User_Circuit (Cat_00: Electric) 29 Bit 03: Low_Capacitance_Phone_DetectCat_00: Electric) 30 Bit 02: Reserved (N.A.) 31 Bit 01: Dial tone_delay_of_User_Circuit (Cat_01: Dial-Tone) 32 Bit 00: Termination_testing (M socket) (Cat_00: Electric) NBLT Type_Low: 1

Bit 31: AC_Current_of_user_Circuit (Cat_00: Electric)

2

Bit 30: AC_Current_of_user_Circuit (Cat_00: Electric)

3

Bit 29: AC_Current_of_user_Circuit (Cat_00: Electric)

4

Bit 28: DC_Current_of_User_Circuit (Cat_00: Electric)

5

Bit 27: DC_Current_of_User_Circuit (Cat_00: Electric)

6

Bit 26: DC_Current_of_User_Circuit (Cat_00: Electric

7

Bit 25: Reserved (N.A.)

8

Bit 24: Noise_level (Cat_00: Electric)

9

Bit 23: Reserved (N.A.)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

10 Bit 22: Howler_Tone (Cat_02: Howler-Tone) 11 Bit 21: Reserved (N.A.) 12 Bit 20:Status_Monitored (Cat_03: Status-Monitored) 13 Bit 19: Cable_Pair_Identification (Cat_04: Cable-Pair-Identification) 14 Bit 18: Talking_Father (Cat_05: Talking-Test) 15 Bit 17: Line_Reverse-Sub_Test (Cat_07: Talking-Sub-Test-Other) 16 Bit 16: Private_Meter_Pulse_Sub_Test (Cat_07: Talking-Sub-Test-Other) 17 Bit 15: Ring_Subscriber-Sub_Test with Auto Ring Test (Cat_07: Talking-Sub-Test-Other) 18 Bit 14: DP/DTMF_Signal_Sub_test (Cat_06: Talking-Sub-Test-DTMF) 19 Bit 13: Resistance_of_user_Circuit (Cat_07: Talking-Sub-Test_Other) 20 Bit 12: Capacitance_of_Signature (Cat_00: Electric) 21 Bit 11: Resistance_of_Ringer (Cat_00: Electric) 22 Bit 10: N.A. (N.A.) 23 Bit 09: Longitudinal_Current_Test (Cat_00: Electric) 24 Bit 08: Reserved (N.A.) 25 Bit 07: Reserved (N.A.) 26 Bit 06: Reserved (N.A.) 27 Bit 05: Reserved (N.A.) 28 Bit 04: Reserved (N.A.) 29 Bit 03: Reserved (N.A.) 30 Bit 02: Reserved (N.A.) 31 Bit 01: Reserved (N.A.) 32 Bit 00: Reserved (N.A.)

Minimum and Maximum Thresholds

For releases < R4.3 (for 48-line voice LT board and 72-line voice LT board As a general strategy, ISAM Voice will only report the results of the integrated NBLT testing as raw data. It is assumed that an external expert system (such as 5530NA for example) has the full responsibility to verify the test results against pre-provisioned minimum and maximum test thresholds and to report the diagnosis. Nevertheless, the ISAM Voice also performs some basic validation of the test results based on minimum and maximum thresholds. A predefined threshold can be provisioned in the CDE profile. Such a predefined threshold is provided by the customer. However, if this is not the case then “default threshold values” are provisioned in the CDE profile. If the integrated NBLT test result exceeds the provisioned minimum and/or maximum threshold values, an appropriate completion code will be returned. TAP 1109-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Pre-defined “default values” in CDE profile: Table TAP 1109-3: Default threshold values Type Foreign voltage

Value Maximum voltage AC - a/b

6000000

Maximum voltage AC - a/E

6000000

Maximum voltage AC - b/E

6000000

Maximum voltage DC - a/b

6000000

Minimum voltage DC - a/b

-6000000

Maximum voltage DC - a/E

6000000

Minimum voltage DC - a/E

-6000000

Maximum voltage DC - b/E

6000000

Minimum voltage DC - B/E

-6000000

Maximum capacitance - a/b

5000000

Maximum capacitance - a/E

1000000

Maximum capacitance - b/E

1000000

Loop resistance

Maximum loop resistance - a/b

1800

Insulation resistance

Minimum resistance - a/b and b/a

20000

Minimum resistance - a/E and E/a

20000

Minimum resistance - b/E and E/b

20000

Minimum resistance - a/BAT

20000

Minimum resistance - b/BAT

20000

Minimum current

-100000

Maximum current

100000

Minimum feeding DC voltage - a/b

40000000

Maximum feeding DC voltage - a/b

57000000

Minimum feeding DC voltage - b/a

-57000000

Maximum feeding DC voltage - b/a

-40000000

Minimum feeding current - a/b

7000

Maximum feeding current - a/b

29000

Maximum Idle Noise Level

-50000

Maximum Dial Tone delay

1000

Capacitance

AC and DC current

Inward test

From R4.3.01 onwards (for 72-line voice LT board ONLY) The “threshold default values” are no longer provisioned in the CDE profile.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

The threshold values must come from the customer via the CDE-Q. If the customer does not fill in any thresholds in the CDE questionnaire, no thresholds will be included in the CDE profile generated for that customer. ISAM Voice will only report the raw test result. The system does not do any validation check on the NBLT test results.

Migration from release < R4.3.01 to release ≥ R4.3.01 (for 72-line voice LT board ONLY) For customers that want to migrate from a release < R4.3.01 to a release ≥ R4.3.01, the thresholds in the actual CDE profile need to be adapted.

•

•

For the NBLT board types for which the system behavior has been changed from R4.3.01 onwards (feeding current may vary from 0mA~ 18mA, feeding voltage may vary from a small value to ~57V), the thresholds either need to be updated or removed. For the NBLT board types for which the system behavior has not changed in R4.3.01, the thresholds as defined for the former deployed release are kept.

Test parameter requirements Table TAP 1109-4 provides an overview of the test parameters that are required for each test type. Table TAP 1109-4: Test type parameter requirements Test type

# Parameters

Parameter usage

Threshold configuration

Foreign AC voltage

0

none

no

Foreign DC voltage

0

none

no

Feeding DC Voltage

0

none

no

Feeding Current

0

none

no

Insulating resistance

0

none

no

Capacitance

0

none

no

Impedance.

1

ltValue1:

no

Should be a value from 1 up to 4 dependent on the number of polarities to be tested. However due to the limitation of the low driver, the first polarity parameter is considered only. All other polarity parameters are ignored

Meaning: frequency.

0

none

Low capacity Phone detection

Range: 5 up to 3000 Hz. Default: 20 Hz. ltValue2: Meaning: RMS voltage. Range: -150V ~ +150V. Default: 15 V

no

Battery Impedance (1 of 2)

TAP 1109-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Test type

# Parameters

Parameter usage

Threshold configuration

Dial Tone delay

0

none

no

M-Socket detection

0

none

no

AC Current

0

none

no

DC Current

0

none

no

Noise Level

0

none

no

Howler

0

none

no

Line Status Monitoring

1

ltValue1:

no

Meaning: Check real parking or short current state Range: 1, 2 1: No check 2: Check Default: -

Cable Pair Identification

0

none

no

Talking with Subscriber

0

none

no

Line Reverse

0

none

no

Subscriber Private Meter Pulses

1

ltValue1:

no

Meaning: Metering Mode Range: 1, 2 1: TAPI_METER_MODE_TTX 2: TAPI_METER_MODE_REVPOL Default: -

Ring Subscriber

0

none

no

DP/DTMF Signal

1

ltValue1:

no

Meaning: Amount of signals to collect. Range: 1 up to 20 Default: Resistance of User Loop

0

none

no

Electronic Ringer Detection

0

none

no

Longitudonal Current

0

none

no

(2 of 2)

Result Values The following result values may be reported:

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination Table TAP 1109-5: Result values LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Feed_AC_voltage_tr

Feeded AC RMS voltage of user line (tip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: mV Feed_AC_voltage_tg

Feeded AC RMS voltage of user line (tip-ground) unit: mv

Feed_AC_voltage_rg

Feeded AC RMS voltage of user line (ring-ground) unit: mV

Foreign_AC_voltage_tr

Foreign AC RMS voltage of user line (tip-ring) unit: mV

Foreign_AC_voltage_tg

Foreign AC RMS voltage of user line (tip-ground) unit: mV

Foreign_AC_voltage_rg

Foreign AC RMS voltage of user line (ring-ground) unit: mV

Feed_DC_voltage_tr

Feeded DC voltage of user line (tip-ring) unit: mV

Feed_DC_voltage_tg

Feeded DC voltage of user line (tip-ground) unit: mV

Feed_DC_voltage_rg

Feeded DC voltage of user line (ring-ground) unit: mV

Foreign_DC_voltage_tr

Foreign DC voltage of user line (tip-ring) unit: mV

Foreign_DC_voltage_tg

Foreign DC voltage of user line (tip-ground) unit: mV

Foreign_DC_voltage_rg

Foreign DC voltage of user line (ring-ground) unit: mV

Feed_current_tr

Feeding current (tip-ring) unit: µA

Feed_DC_voltage_rt

Feeded DC voltage of user line (ring-tip) unit: mV

Insulating_resistance_tr

Insulating resistance of user line (tip-ring) unit: Ohm

(1 of 4)

TAP 1109-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Insulating_resistance_rt

Insulating resistance of user line (ring-tip)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: Ohm Insulating_resistance_tg

Insulating resistance of user line (tip-ground) unit: Ohm

Insulating_resistance_rg

Insulating resistance of user line (ring-ground) unit: Ohm

Insulating_resistance_tbat

Insulating resistance of user line (tip-bat) unit: Ohm

Insulating_resistance_rbat

Insulating resistance of user line (ring-bat) unit: Ohm

Capacitance_tr

Capacitance of user line (tip-ring) unit: nF

Capacitance_rt

Capacitance of user line (ring-tip) unit: nF

Capacitance_tg

Capacitance of user line (tip-ground) unit: nF

Capacitance_rg

Capacitance of user line (ring-ground) unit: nF

Impedance_tr

Impedance of user line (tip-ring) unit: nF

Impedance_rt

Impedance of user line (ring-tip) unit: nF

Impedance_tg

Impedance of user line (tip-ground) unit: nF

Impedance_rg

Impedance of user line (ring-ground) unit: nF

LowCapDetect

TRUE(1) or FLASE(0)

(2 of 4)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Dial_tone_delay

Result of the time interval between the offhook and dial tone is played

Only applicable to SIP 72 lines voice LT board

N.A.

N.A.

N.A.

Result of whether the dial tone is stopped by dialing of an arbitrary digit which is simulated by the LT. N.A. Termination_Testing

TRUE(1) or FLASE(0)

N.A.

N.A.

N.A.

N.A.

AC current test normal test (tip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

(M Socket) AC_current_tr

unit: µA AC_current_tg

AC current test normal test (tip-ground) unit: µA

AC_current_rg

AC current test normal test (ring-ground) unit: µA

DC_current_tr

DC current test normal test (tip-ring) unit: µA

DC_current_tg

DC current test normal test (tip-ground) unit: µA

DC_current_rg

DC current test normal test (ring-ground) unit: µA

Noise_level

unit: 0.001dbm

N.A.

N.A.

N.A.

N.A.

Normal_Condition_Howler

playSuccessfulAndOnHookNormal(1)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

playSuccessfulAndTestTerminated(2) playSuccessfulButOnHookTimeout(3) playFailed(4) Status_Monitored

eStatusMonitoredBlock(2), eStatusMonitoredIdle(3), eStatusMonitoredBusy(4), eStatusMonitoredParking(5), eStatusMonitoredShort(6)

(3 of 4)

TAP 1109-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

LineTestType

ltExtRptVal

ltExtRp Val2

ltExtRp Val3

ltExtRp Val4

ltExtRp Val5

Cable Pair Identification

playTraceToneOKTestTerminated(1),

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

playTraceToneOKTimeout(2), playTraceToneFailed(3), stopTraceToneFailed(4) Talking test (father test item) Line Reverse

lineReverseOKTestTerminated(1), lineReverseOKTimeout(2), lineReverseFailed(3)

Private Meter Pulses

meterSuccess(1), meterFailed (2)

Ring Subscriber with Auto Ring

ringSuccessfulAndTestTerminated(1, ringSuccessfulAndStopedByOffHook(2 ), ringSuccessfulAndTimeout(3), ringFailed(4), ringFailedBecausePortisOffHook(5), ringStopFailed(6)

DP/DTMF Signal

numberDP1(1), numberDP2(2), numberDP3(3), numberDP4(4), numberDP5(5), numberDP6(6), numberDP7(7), numberDP8(8), numberDP9(9), numberDP0(10), starDP(11), poundDP(12), numberDTMF1(65537), numberDTMF2(65538), numberDTMF3(65539), numberDTMF4(65540), numberDTMF5(65541), numberDTMF6(65542), numberDTMF7(65543), numberDTMF8(65544), numberDTMF9(65545), numberDTMF0(65546), starDTMF(65547), poundDTMF(65548)

N.A.

N.A.

N.A.

N.A.

Resistance_loop_tr

Resistance of user loop (rip-ring)

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

N.A.

unit: Ohm Capacitance_sig

Capacitance of electronic ringer unit: pF

Insulating_resistance_ring

Resistance of electronic ringer unit: Ohm

Longitudinal_current_test

Difference between the currents on the tip-lead and the ring-lead (longitudinal current) unit: µA

(4 of 4)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

Result Value for Howler-Tone

• • • •

1: playSuccessfulAndOnHookNormal: Howler tone has been played successfully. The line went on-hook. 2: playSuccessfulAndTestTerminated: Howler tone has been played successfully. The integrated NBLT test has been terminated by the operator. 3: playSuccessfulButOnHookTimeout: Howler tone has been played successfully. The line did not go on-hook before the Howler Tone time-out timer expired (1 minute). 4: playFailed: Playing the howler tone has failed.

Result Value for Status-Monitoring

• • • • •

2: eStatusMonitoredBlock: The line is blocked due to malfunction, or the line is locked by the operator. 3: eStatusMonitoredIdle: The line is on-hook and in state idle. 4: eStatusMonitoredBusy: The line is involved in a call. 5: eStatusMonitoredParking: The line is in parking state. 6: eStatusMonitoredShort: The line is in short circuit

Result Value for Cable-Pair-Identification

• • • •

1: playTraceToneOKTestTerminated: The search tone has been played successfully. The integrated NBLT test has been terminated by the operator. 2: playTraceToneOKTimeout: The search tone has been played successfully. The integrated NBLT test was stopped due to search tone time-out timer expiry (48 lines voice LT board = 1 minute / 72 lines voice LT board = session timer) 3: playTraceToneFailed: Playing the search tone failed. 4: stopTraceToneFailed: Ending the search tone failed.

Result Value for Line-Reverse

• • •

1: lineReverseOKTestTerminated: The line polarity has been successfully reversed. The integrated NBLT test has been terminated by the operator 2: lineReverseOKTimeout: The line polarity has been successfully reversed. The integrated NBLT test was stopped due to time-out timer expiry (1 minute) 3: lineReverseFailed: The reverse of the line polarity failed

Result Value for Private Meter Pulses

• •

(1) MeterSuccess (2) MeterFailed

Result Value for Ring-Subscriber Sub Test

• • • •

1: ringSuccessfulAndTestTerminated: The ringing has successfully started. The integrated NBLT test has been terminated by the operator. 2: ringSuccessfulAndStopedByOffHook: The ringing has successfully started the integrated NBLT test was stopped due to an off-hook. 3: ringSuccessfulAndTimeout: The ringing has successfully started; the integrated NBLT test was stopped due to time-out timer expiry. 4: ringFailed: The ringing failed due to some internal misbehavior.

TAP 1109-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

• •

5: ringFailedBecausePortisOffHook: The ringing failed due to the line being in off-hook state. 6: ringStopFailed: The ringing could not be stopped.

Result Value for DP/DTMF Signal Sub Test

• • • • • • • • • • • • • • • • • • • • • • • •

01: numberDP1: pulse digit 1 has been received 02: numberDP2: pulse digit 2 has been received 03: numberDP3: pulse digit 3 has been received 04: numberDP4: pulse digit 4 has been received 05: numberDP5: pulse digit 5 has been received 06: numberDP6: pulse digit 6 has been received 07: numberDP7: pulse digit 7 has been received 08: numberDP8: pulse digit 8 has been received 09: numberDP9: pulse digit 9 has been received 10: numberDP0: pulse digit 0 has been received 11: starDP: pulse digit star(*) has been received 12: poundDP: pulse digit pound(#) has been received 65537: numberDTMF1: dtmf digit 1 has been received 65538: numberDTMF2: dtmf digit 2 has been received 65539: numberDTMF3: dtmf digit 3 has been received 65540: numberDTMF4: dtmf digit 4 has been received 65541: numberDTMF5: dtmf digit 5 has been received 65542: numberDTMF6: dtmf digit 6 has been received 65543: numberDTMF7: dtmf digit 7 has been received 65544: numberDTMF8: dtmf digit 8 has been received 65545: numberDTMF9: dtmf digit 9 has been received 65546: numberDTMF0: dtmf digit 0 has been received 65547: starDTMF: dtmf digit star(*) has been received 65548: poundDTMF: dtmf digit pound(#) has been received

Group Test •

•

Prior to R4.3: • When an operator requests to perform a Group Test (including the 13 electric NBLT test types as basically defined for a Group test, as well as other NBLT test types), then the system handles all the requested NBLT test types as individual NBLT test types. • When a Group Test has completed, the Common Status in the Line Test Parameter Table is set to (1) TestFinished only when all 13 electric NBLT test types were successfully completed. From R4.3 onwards: When an operator requests to perform a Group Test (including the 13 electric NBLT test types as basically defined for a Group test, as well as other NBLT test types), then the system performs the Group test for the 13 electric NBLT test types, with the sequence and policies as defined for the Group Test, and handles the other requested NBLT test types as individual NBLT test types.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-23 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

Validity of test results • •

Prior to R4.3: When a Group test is executed, LTCommonErrCode will be set to testFinished(1) only when the last test item is successful. From R4.3 onwards: When a Group Test has completed, LTCommonErrCode will be set to testFinished(1), irrespective of whether full or only partial test results are achieved. The operator can check LTErrCode for additional information to confirm whether an individual test is valid or not. Additional error codes have been defined to clarify the exact reason for the test failure. the result is valid only when LTCommonErrCode = testFinished(1) and LTErrCode = pPSuccess(1). For details, refer to the linetest MIB.

Feeding DC Voltage / DC Current Test (72-line voice LT board only) Prior to R4.3: Table TAP 1109-6: Feeding DC Voltage / DC Current Test (< R4.3) Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Feeding AC/ DC Voltage

Not allowed

Supported

Not allowed

Feeding DC Current

Not allowed

Supported.

Not allowed

System simulates a 1.8k Ohm loop resistance between a/b lines. Returns feeding current: ~18mA.

From R4.3 onwards: Table TAP 1109-7: Feeding DC Voltage / DC Current Test (≥ R4.3)

Feeding AC/ DC Voltage

Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Not allowed

Supported

Supported. Returns real feeding voltage based on different loop resistances

(1 of 2)

TAP 1109-24 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Feeding DC Current

Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Not allowed

Supported.

Supported.

System measures the real feeding current on the line.

Returns real feeding current: ~18mA.

Returns real feeding current: ~0mA. (2 of 2)

Feeding DC Voltage / DC Current Test (48-line voice LT board only) All releases: Table TAP 1109-8: Feeding DC Voltage / DC Current Test Port status = Lock/Disable/Not provisioned

Port status = Idle (Onhook)

Port status = Busy

Feeding AC/ DC Voltage

Not allowed

Supported

Not allowed

Feeding DC Current

Not allowed

Supported.

Not allowed

System simulates a 1.8k Ohm loop resistance between a/b lines. Returns feeding current: ~18mA.

Foreign DC voltage test (Individual Test / as part of Group Test) (48-line and 72-line voice LT board) The following applies for foreign DC voltage test (Individual Test / as part of Group Test) in case M-socket with large resistance (470 kOhm) and large capacitance (1.8 µF) is connected to the subscriber line:

• • •

In case of a M-socket (470 kOhm, 1.8 µF), the capacitor of this M-socket acts as an energy source and impacts the test accuracy of the Foreign DC voltage test. R2.5: Detection of M-socket termination with 470 kOhm resistance connected in serial with diode. R4.2: To improve the test accuracy, a delay timer is introduced (configurable by means of the CDE profile; default = 3 s) to provide a sufficiently long time period to let the capacitor discharge and as such to improve the test result accuracy.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-25 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

Foreign DC voltage test (Individual Test) (72-line voice LT board only) The following applies for foreign DC voltage test (Individual Test) in case M-socket with large resistance (470 kOhm) and large capacitance (1.8 µF) is connected to the subscriber line (72 lines voice LT board only).

• •

Prior to R4.3: Individual Foreign DC voltage test result exceeds CDE threshold. From R4.3 onwards: Individual Foreign DC voltage test result does NOT exceed CDE threshold (The firmware did some improvement to avoid the impact of M-socket).

Note — When Group Test is used, the behavior does not change compared to R4.2.

M-Socket detection M-socket detection function is supported by the ALU 5530 NA only (not by ISAM Voice). From R4.3 onwards: in case of the 72-line voice LT board, and for big-capacitance M-Socket detection, Group Test must be used (delay timer to be set to “0”; Foreign DC voltage test result exceeds CDE threshold).

Cable Pair Identification Test (72-line voice LT board only) From R4.3 onwards: The 60 seconds search tone duration limitation is removed. The characteristics of the Search Tone are provisionable in the CDE profile : Search tone AC level & DC offset. The search tone is applied symmetrically between Tip and Ring. The search tone can be switched-on / switched-off at all times. When switched-on, the system shall autonomously switch-off the search tone after a configurable time (1…120 minutes).

Dial Tone Delay (72 lines voice LT board only) Prior to R4.3:

• • • • •

The bottom driver simulates an off-hook event and records the timestamp (start time). The simulated off-hook event is notified to the upper layer call handling SW application as is usually the case for any off-hook event. The upper call handling SW application triggers the activation of the dial tone. Upon receiving the command to play dial tone, the bottom driver records the timestamp (stop time) The bottom driver simulates on-hook event.

TAP 1109-26 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

From R4.3 onwards:

• • • • •

The complete test process is handled by integrated HW test device library :timestamp recording, dial tone detection and the calculation of the dial tone delay: The integrated HW test device simulates an off-hook event by forcing the off-hook impedance on the test line and records the timestamp (start time) The off-hook event is notified to the upper layer call handling SW application as is usually the case for any off-hook event The upper call handling SW application triggers the activation of the dial tone. The integrated HW test device records the time stamp when detecting the dial tone presence.

The dial tone delay time is calculated by the integrated HW test device.

Electronic Ringer Detection (72-line voice LT board only) This new NBLT type (supported from R4.3 onwards) can be used to measure the resistance and capacitance of a ringer circuit in phone sets.

CLI NBLT parameter description

Single Line Test Session Configuration: session-cmd The following session commands are supported:

• • • • • • • • •

create: create an integrated NBLT session. starttest: start the execution of an integrated NBLT session (transfer data done). sendinfo: start to transfer info data for an ongoing NBLT, to cancel the NBLT for 1 or multiple lines. startinfo: transfer info data completed, start info operation. destroy: delete an integrated NBLT session and its contents. recv-subtest: start to transfer the line sub-test data. start-subtest: transfer sub-test's data done, start the line sub-test. repeat: repeat the last integrated NBLT session. endtest: stop the integrated NBLT session.

Single Line Test Session Configuration: Timeout-period The time-out period defines the maximum time being required to run an NBLT session. It is the sum of the maximum delay defined for each subscriber line involved in the NBLT session. The maximum delay for a subscriber line is defined as the sum of the maximum delay for each NBLT test executed on the subscriber line. Below, the maximum delay for each of the NBLT tests is shown:

• • • •

Overall overhead time per session: 2 s Group test: 15 s + 5 s (delay time of discharge) Feeded AC Voltage: 3 s Foreign AC Voltage: 10 s

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-27 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

• • • • • • • • • • • • • • • • • • • • • • •

Feeded DC Voltage: 3 s Foreign DC Voltage: 10 s + 5 s (delay time of discharge) Feeding Current: 3 s Resistance of Userloop: 6 s Insulating Resistance: 6 s Capacitance: 15 s Impedance: 5 s Low Capacity detect: 20 s Dial Tone Delay: 8 s M-Socket: 6 s AC Current: 66 s DC Current: 66 s Noise Level: 66 s Howler Tone: 120 s Status Monitoring: 3 s Cable Pair Identification: • 48 lines voice LT board: 65 s • 72 lines voice LT board: Duration of session with a maximum of 120 min. Talking father: 3 s Talking - User Loop Sub: 600 s Talking - Line Reverse Sub: 5 s Talking - Private Meter Pulse Sub: 6 s Talking - Ring Subscriber Sub: 60 s Electronic Ringer Detection : 10 s Longitudinal Current : 3 s

Single Line Test Session Configuration: Type-High With the type-high parameter the operator may indicate the following NBLT tests:

• •

None: null Group: group test including following individual tests: • Foreign_AC_RMS_of_User_Circuit (Tip-Ring) • Foreign_AC_RMS_of_User_Circuit (Tip-Ground) • Foreign_AC_RMS_of_User_Circuit (Ring-Ground) • Foreign_DC_Voltage_of_User_Circuit (Tip-Ring) • Foreign_DC_Voltage_of_User_Circuit (Tip-Ground) • Foreign_DC_Voltage_of_User_Circuit (Ring-Ground) • Insulating_resistance_of_User_Circuit (Tip-Ring) • Insulating_resistance_of_User_Circuit (Ring-Tip) • Insulating_resistance_of_User_Circuit (Tip-Ground) • Insulating_resistance_of_User_Circuit (Ring-Ground) • Capacitance_of_User_Circuit (Tip-Ring) • Capacitance_of_User_Circuit (Tip-Ground) • Capacitance_of_User_Circuit (Ring-Ground)

TAP 1109-28 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

•

•

•

•

• •

•

•

• • •

Feeded-ac-vol: Feeded AC RMS voltage test including following individual tests: • Feeded_AC_RMS_Voltage_of_User_Circuit (Tip-Ring) • Feeded_AC_RMS_Voltage_of_User_Circuit (Tip-Ground) • Feeded_AC_RMS_Voltage_of_User_Circuit (Ring-Ground) Foreign-ac-vol: Foreign AC RMS voltage test including following individual tests: • Foreign_AC_RMS_Voltage_of_User_Circuit (Tip-Ring) • Foreign_AC_RMS_Voltage_of_User_Circuit (Tip-Ground) • Foreign_AC_RMS_Voltage_of_User_Circuit (Ring-Ground) Feeded-dc-vol: Feeded DC voltage test including following individual tests: • Feeded_DC-Voltage_of_User_Circuit (Tip-Ring) • Feeded_DC-Voltage_of_User_Circuit (Tip-Ground) • Feeded_DC-Voltage_of_User_Circuit (Ring-Ground) • Feeded_DC-Voltage_of_User_Circuit (Ring-Tip) Foreign-dc-vol: Foreign DC voltage test including following individual tests: • Foreign_DC-Voltage_of_User_Circuit (Tip-Ring) • Foreign_DC-Voltage_of_User_Circuit (Tip-Ground) • Foreign_DC-Voltage_of_User_Circuit (Ring-Ground) Feeding-current: Feeding current test Resistance: Insulating Resistance test including following individual tests: • Insulating_resistance_of_User_Circuit (Tip-Ring) • Insulating_resistance_of_User_Circuit (Ring-Tip) • Insulating_resistance_of_User_Circuit (Tip-Ground) • Insulating_resistance_of_User_Circuit (Ring-Ground) • Insulating_resistance_BAT_of_User_Circuit (Ground-Tip) • Insulating_resistance_BAT_of_User_Circuit (Ground-Ring) Capacitance: Capacitance test including following individual tests: • Capacitance_of_User_Circuit (Tip-Ring) • Capacitance_of_User_Circuit (Ring-Tip) • Capacitance_of_User_Circuit (Tip-Ground) • Capacitance_of_User_Circuit (Ring-Ground) Impedance: Impedance test including following individual tests: • Impedance_of_User_Circuit (Tip-Ring) • Impedance_of_User_Circuit (Ring-Tip) • Impedance_of_User_Circuit (Tip-Ground) • Impedance_of_User_Circuit (Ring-Ground) Low-capacit-phone: Low capacitance phone test Dialton-delay: Dial tine delay test of User circuit (only in idle state Msocket-detection: Termination (m_socket detection) test

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-29 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

Single Line Test Session Configuration: Type-Low With the type-low parameter the operator may indicate the following NBLT tests:

• •

•

• • • • • • • • • • • •

None: null AC-Current: AC Current test including the following individual tests: • AC_Current_of_user_Circuit (Tip-Ring) • AC_Current_of_user_Circuit (Tip-Ground) • AC_Current_of_user_Circuit (Ring-Ground) DC-Current: DC Current test including the following individual tests: • DC_Current_of_User_Circuit (Tip-Ring) • DC_Current_of_User_Circuit (Tip-Ground) • DC_Current_of_User_Circuit (Ring-Ground) Noise-level: Noise Level test Howler: Howler Tone test Status-Monitored: Status Monitored test Cable-Pair-Ident: Cable pair identification test Talking-Father: Talking test (father test item) Line-Reverse-Sub: Line reverse test; subtest of talking test P-Meter-Pulse-Sub: Private meter pulse test; subtest of talking test Ring-Subscrib-Sub: Ring subscriber with auto ring test; subtest of talking test Dpdtmf-signal-sub: dp/dtmf signal test; subtest of talking test Userloop-Sub: Resistance of user loop (tip-ring); subtest of talking test Electronic Ringer Detection: Electronic Ringer Detection test including capacitance and resistance of ringer circuit. Longitudinal-current: longitudinal current test.

Allowed Type-High / Type Low parameter combinations

TAP 1109-30 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Msocket-detection

Impedance

Capacitance

Resistance

Feeding-current

Foreign-dc-vol

Feeded-dc-vol

Foreign-ac-vol

Feeded-ac-vol

Group

None

Low

Dialton-delay

High

Low-capacitance-phone

Table TAP 1109-9: Allowed Type-High / Type Low parameter combinations

None

IR

A

A

A

A

A

A

A

A

A

A

A

A

Ac-current

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Dc-current

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Noise-level

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Howler

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Status-monitored

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Cable-pair-ident

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Talking-father

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Line-reverse-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

p-meter-pulse-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Ring-subscriber-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Dpdtmf-signal-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Userloop-sub

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Electronic Ringer Detection

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

Longitudinal Current

A

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

IR: Irrelevant A: Allowed NA: Not allowed

Single Line Test Session Configuration: Test modes The following test modes are supported:

• • •

single: the integrated NBLT is executed once. interactive: the interactive integrated NBLT. cablepair: the cable pair test

Single Line Test Parameter Configuration: test names The following test types are supported:

• • •

feeded-ac-tr(mv): feeded AC RMS voltage of user circuit (tip-ring) feeded-ac-tg(mv): feeded AC RMS voltage of user circuit (tip-ground) feeded-ac-rg(mv): feeded AC RMS voltage of user circuit (ring-ground)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-31 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

foreign-ac-tr(mv): foreign AC RMS voltage of user circuit (tip-ring) foreign-ac-tg(mv): foreign AC RMS voltage of user circuit (tip-ground) foreign-ac-rg(mv): foreign AC RMS voltage of user circuit (ring-ground) feeded-dc-tr(mv): feeded DC voltage of user circuit (tip-ring) foreign-dc-tr(mv): foreign DC voltage of user circuit (tip-ring) foreign-dc-tg(mv): foreign DC voltage of user circuit (tip-ground) foreign-dc-rg(mv): foreign DC voltage of user circuit (ring-ground) feed-current(ua): feeding current (tip-ring) feeded-dc-rt(mv): feeded DC voltage of user circuit (ring-tip) resist-tr(ohm): insulating resistance of user circuit (tip-ring) resist-rt(ohm): insulating resistance of user circuit (ring-tip) resist-tg(ohm): insulating resistance of user circuit (tip-ground) resist-rg(ohm): insulating resistance of user circuit (ring-ground) resist-tbat(ohm): insulating battery resistance of user circuit (tip-bat) resist-rbat(ohm): insulating battery resistance of user circuit (ring-bat) capacitanc-tr(nf): capacitance of user circuit (tip-ring) capacitanc-rt(nf): capacitance of user circuit (ring-tip) capacitanc-tg(nf): capacitance of user circuit (tip-ground) capacitanc-rg(nf): capacitance of user circuit (ring-ground) impedance-tr(ohm): impedance of user circuit (tip-ring) impedance-tg(ohm): impedance of user circuit (tip-ground) impedance-rg(ohm): impedance of user circuit (ring-ground) low-capacit-phone: low capacitance phone detect bat-imped-discard: battery impedance (ring-bat) discarded dialton-delay(ms): dial tone delay of user circuit (only in idle state) msocket-detection: termination (m socket) detection ac-current-tr(ua): AC current normal test (tip-ring) ac-current-tg(ua): AC current normal test (tip-ground) ac-current-rg(ua): AC current normal test (ring-ground) dc-current-tr(ua): DC current normal test (tip-ring) dc-current-tg(ua): DC current normal test (tip-ground) dc-current-rg(ua): DC current normal test (ring-ground) noise-lv-0.001dbm: noise level normal test howler-test-park: Howler tone test under normal test condition (only in parking) status-monitored: status monitored test cable-pair-ident: cable pair identification test talking-father: talking test (father test item) line-reverse-sub: line reverse test; subtest of talking test p-meter-pulse-sub: private meter pulse test; subtest of talking test ring-subscrib-sub: ring subscriber with auto ring test; subtest of talking test dpdtmf-signal-sub: dp/dtmf signal test; subtest of talking test userloop-sub(ohm): resistance of user loop (tip-ring); subtest of talking test capacit-sign(pf): capacitance of electronic ringer detection resist-sign(ohm): resistance of electronic ringer detection feeded-dc-tg(mv): feeded DC voltage of user circuit (tip-ground) feeded-dc-rg(mv): feeded DC voltage of user circuit (ring-ground)

TAP 1109-32 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

• •

impedance-rt(ohm): impedance of user cicuit (ring-tip) long-current(ua) : longitudinal current

Prerequisites The following prerequisites must be fulfilled before the NBLT test can be started:

•

The target board must be operational

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-33 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

Procedure Proceed as follows to configure the Integrated Line Test: 1

Fulfil conditions for NBLT; see Table TAP 1109-10. Table TAP 1109-10: Conditions for NBLT

NBLT Test

Type

Pre-NBLT Condition to be fulfilled

MID-NBLT condition to be fulfilled

Post-NBLT condition to be fulfilled

Type = High Group test

E

Ref. Individual NBLT tests

Ref. Individual NBLT tests

Ref. Individual NBLT tests

Feeded AC Voltage

E

4, 5, 6*

None

None

Foreign AC Voltage

E

1, 2, 3, 4, 5

None

None

Feeded DC Voltage

E

4, 5, 6*

None

None

Foreign DC Voltage

E

1, 2, 3, 4, 5

None

None

Feeding Current

E

4, 5, 6*

None

None

Resistance

E

1, 2, 3, 4, 5

None

None

Capacitance

E

1, 2, 3, 4, 5

None

None

Impedance

E

1, 2, 3, 4, 5

None

None

Low Capacitance Phone

E

1, 2, 3, 4

None

None

DT

4, 5

None

None

E

1, 2, 3, 4

None

None

AC Current

E

1, 2, 3, 4, 5

None

None

DC Current

E

1, 2, 3, 4, 5

None

None

Noise Level

E

1, 2, 3, 4, 5

None

None

Howler Tone

HT

5

None

None

Status Monitoring

SM

1, 2, 3, 4, 5, 6

None

None

Cable Pair Identification

CPI

1, 2, 3, 4, 5

None

NBLT Session time-out

Talking Father - Line Reverse Sub

TSTO

6

None

NBLT Session time-out

Talking Father - Private Meter Pulse Sub

TSTO

6

None

None

Talking Father - Ring Subscriber Sub

TSTO

6

Terminate Call prior to the start of the Ring Subscriber Sub

None

Talking Father - DT DTMF signal Sub

TSTD

6

Press digits after having started the DP DTMF Signal Sub

None

Talking Father - Userloop Sub

TSTO

6

None

None

1*, 2*, 3*, 4*,5*

None

None

Dialtone Delay Msocket detection Type = Low

Electronic Ringer Detection

E

(1 of 2)

TAP 1109-34 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

NBLT Test

Type

Longitudinal Current

E

Pre-NBLT Condition to be fulfilled

MID-NBLT condition to be fulfilled

4*, 5* ,6*

None

Post-NBLT condition to be fulfilled None

(2 of 2) (1): Termination not provisioned (2): Termination provisioned / administratively locked (3): Termination provisioned / administratively unlocked / (4): Termination provisioned / administratively unlocked / (5): Termination provisioned / administratively unlocked / (6): Termination provisioned / administratively unlocked / (*): 72-lines voice LT board only

2

operationally down operationally up / idle state operationally up / parking state operationally up / busy state

Show the next available session for integrated line test with the following command: show linetest single avail-sess

Note — This step checks whether a session is available and returns the maximum number of sessions supported (maximum 16) together with the available session identifier number with which the actually intended NBLT session can be configured. 3

Configure the session parameters with the following command: configure linetest single ltsession (sessionid) session-cmd ownerid timeout-period line-num type-high type-low test-parm-num test-mode inactive-timer

Note 1 — For a description of the NBLT session parameters, see “CLI NBLT parameter description”. Note 2 — The following integrated NBLT can be terminated by operator command:

• • • • • • • • •

AC Current DC Current Noise Level Howler Ring subscriber with Auto ring Line Reverse Talking with Subscriber DP/DTMF Signal Cable pair identification tone

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-35 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

4

Configure the line parameters with the following command: configure linetest single ltline (sessionid) lineid line-status

5

Configure the parameters with the following command: configure linetest single ltparm (sessionid) test-name(unit) value1 value2 value3 value4 value5 min-threshold max-threshold

Note — For a description of the single line test parameters, see “CLI NBLT parameter description”.

6

Run the NBLT with the following command: configure linetest single ltsession (sessionid) session-cmd starttest

7

Show session parameters with the following command: show linetest single ltsession (sessionid)

Note — In case there would be an input parameter inconsistency in the session configuration or parameter configuration command input, the session / parameter configuration command will be rejected with “General SNMP error” and the reason for rejecting the configuration command will be reported through the “input-err-code” field. Table TAP 1109-11 lists the possible return values. Table TAP 1109-11: Possible return values Value

Description

noerr

No error

paramnuminconsis

The number of input parameters configured in the parameter configuration command is different from the value configured in the test-param-num parameter of the session configuration command.

paramnumoutrange

The number of input parameters configured in the parameter configuration command exceeds the maximum allowed range (0-4).

typeneednoparam

The test parameter(s) been configured is (are) meaningless, because the MELT test type to be executed doesn't require any test parameter input.

(1 of 2)

TAP 1109-36 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

Value

Description

nontestingtype

The test parameter(s) been configured is (are) for MELT test types which have not been defined in the actual configured session.

missingparamconf

Missing test parameter configuration input for the MELT test types been configured in the session configuration command.

missingtimeout

TimeOut-Period parameter input missing in session configuration command.

timeoutnotenough

The value configured for the TimeOut_Period parameter in the session configuration command is below the required minimum delay for executing the configured MELT test type.

linenuminconsis

The line number configured in the session configuration command is different from the line number configured in line parameter configuration command.

linenumoutrange

The configured number of lines in the session configuration command exceeds the maximum allowed range (1-72).

invalidlineid

The configured line identity in the line parameter configuration command is invalid.

duplicatedline

The same line Identity has been configured twice with the line parameter configuration command.

missingtesttype

The parameters Type-High and/or Type-Low are missing in the session configuration command.

invalidtesttype

The configured value(s) for Type-High and/or Type-Low is (are) incorrect.

thresholdnumerr

The value configured for the threshold parameter in the parameter configuration command exceeds the maximum allowed range (0-39).

neednothreshold

The configured threshold value(s) is (are) meaningless, because the MELT test type to be executed doesn't require any threshold input.

threshfornon

The configured threshold value(s) is (are) for MELT test types which have not been defined in the actually configured session.

typemismatchmode

The configured MELT test type does not match the configured test mode.

linenummismatch

The number of lines been configured in the session configuration command does not match with the configured MELT test type and test mode.

wrongstatusforsub

The actual line status for subtest is not as required to execute the subtest.

lineidinnontest

The line Identity configured in the line configuration command is not in testing status.

sessionstateerr

The configuration command is not allowed within the current session state.

internalerror

Internal system error

inactivetimeroutrange

The value of the inactive timer parameter configured in the session configuration command exceeds the allowed range (0 or from 120 up to 65535).

(2 of 2)

8

Show all parameters on a specific line ID of a session with the following command: show linetest single ltline (sessionid) lineid

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-37 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

9

Show Integrated Line Test Report with the following command: show linetest single lineid-ext-rept (sessionid) lineid test-name(unit) result-index

10

STOP. This procedure is complete. Type-HIGH NBLT examples: 1 GROUP TEST. 1.1 Line is in idle state: call-status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 1.2 Show the available Session. show linetest single avail-sess 1.3 Start the Group test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high group type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 1.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 2 FEEDED-AC-VOL 2.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 2.2 Show the available Session. show linetest single avail-sess

TAP 1109-38 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

2.3 Start the Feeded AC Voltage test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high feeded-ac-vol type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 2.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 3 FOREIGN-AC-VOL. 3.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 3.2 Show the available Session. show linetest single avail-sess 3.3 Start the Foreign AC Voltage test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high foreign-ac-vol type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 3.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 4 FEEDED-DC-VOL. 4.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 4.2 Show the available Session. show linetest single avail-sess

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-39 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

4.3 Start the Feeded DC Voltage test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high feeded-dc-vol type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 4.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 5 FOREIGN-DC-VOL. 5.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 5.2 Show the available Session. show linetest single avail-sess 5.3 Start the Foreign DC Voltage test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high foreign-dc-vol type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 5.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 6 FEEDING-CURRENT. 6.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 6.2 Show the available Session. show linetest single avail-sess

TAP 1109-40 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

6.3 Start the Feeding Current test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high feeding-current type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 6.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 7 RESISTANCE. 7.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 7.2 Show the available Session. show linetest single avail-sess 7.3 Start the Resistance test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high resistance type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 7.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 8 CAPACITANCE. 8.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 8.2 Show the available Session. show linetest single avail-sess

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-41 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

8.3 Start the Capacitance test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high capacitance type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 8.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 9 IMPEDANCE. 9.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 9.2 Show the available Session. show linetest single avail-sess 9.3 Start the Impedance test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high impedance type-low none test-parm-num 1 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltparm 1 test-name(unit) impedance-tr(ohm) value1 20 value2 15 configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 9.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 10 LOW-CAPACIT-PHONE. 10.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)]

TAP 1109-42 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

10.2 Show the available Session. show linetest single avail-sess 10.3 Start the Low Capacity Phone test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high low-capacit-phone type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 10.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 11 DIALTON-DELAY. 11.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 11.2 Show the available Session. show linetest single avail-sess 11.3 Start the Dialton-Delay test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high dialton-delay type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 11.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 12 MSOCKET-DETECTION. 12.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)]

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-43 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

12.2 Show the available Session. show linetest single avail-sess 12.3 Start the Msocket-Detection test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high msocket-detection type-low none test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 12.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy Type-LOW NBLT examples: 13 AC CURRENT. 13.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 13.2 Show the available Session. show linetest single avail-sess 13.3 Start the AC Current test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 600 line-num 2 type-high none type-low ac-current test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltline 1 lineid 1/1/1/1/4 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 13.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 14 DC CURRENT. 14.1 Line is in idle state: call- status = on-hook & test-status TAP 1109-44 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

= no-testing. show voice sip termination [if-index)] 14.2 Show the available Session. show linetest single avail-sess 14.3 Start the DC Current test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 600 line-num 2 type-high none type-low dc-current test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltline 1 lineid 1/1/1/1/4 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 14.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 15 NOISE LEVEL 15.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 15.2 Show the available Session. show linetest single avail-sess 15.3 Start the Noise Level test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 600 line-num 1 type-high none type-low noise-level test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 15.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 16 HOWLER TONE Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-45 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

16.1 Line is in parking state: call- status = idle-off-key & test-status = no-testing. show voice sip termination [if-index)] 16.2 Show the available Session. show linetest single avail-sess 16.3 Start the Howler Tone test. configure linetest single ltsession 1 session-cmd create ownerid 123 timeout-period 6000 line-num 1 type-high none type-low howler test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 16.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 17 STATUS MONITORING 17.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 17.2 Show the available Session. show linetest single avail-sess 17.3 Start the Status Monitoring test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 600 line-num 2 type-high none type-low status-monitored test-parm-num 1 test-mode single configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltline 1 lineid 1/1/1/1/4 line-status intest configure linetest single ltparm 1 test-name(unit) status-monitored value1 1 configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1

TAP 1109-46 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

17.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 18 CABLE PAIR IDENTIFICATION. 18.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 18.2 Show the available Session. show linetest single avail-sess 18.3 Start the Cable Pair Identification test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 600 line-num 1 type-high none type-low cable-pair-ident test-parm-num 0 test-mode cablepair configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest For this NBLT test, one has to await the timeout of the NBLT session to get the result of the NBLT test. show linetest single ltline 1 show linetest single lineid-ext-rept 1 18.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 19 TALKING FATHER 19.1 Line Reverse Sub. 19.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice sip termination [if-index)] 19.1.2 Show the available Session. show linetest single avail-sess 19.1.3 Start the Talking Father test configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-47 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

19.1.4 Start the Line-Reverse Sub With a multi-meter instrument, one can measure a voltage reversal every 5 seconds. configure linetest single ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low line-reverse-sub test-parm-num 0 test-mode interactive configure linetest single ltsession 1 session-cmd start-subtest For this NBLT test, one has to await the timeout of the NBLT session to get the result of the NBLT test. show linetest single ltline 1 show linetest single lineid-ext-rept 1 19.1.5 Free the NBLT session. NBLT session freed to Time-Out. 20 TALKING FATHER. 20.1 Private Meter Pulse Sub 20.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice sip termination [if-index)] 20.1.2 Show the available Session. show linetest single avail-sess 20.1.3 Start the Talking Father test configure linetest single ltsession 1 session-cmd create ownerid 1timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest 20.1.4 Start the Private-Meter-Pulse Sub. configure linetest single ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low p-meter-pulse-sub test-parm-num 1 test-mode interactive configure linetest single ltparm 1 test-name(unit) p-meter-pulse-sub value1 1 configure linetest single ltsession 1 session-cmd start-subtest show linetest single ltline 1 show linetest single lineid-ext-rept 1

TAP 1109-48 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

20.1.5 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 21 TALKING FATHER. 21.1 Ring Subscriber Sub. 21.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice sip termination [if-index)] 21.1.2 Show the available Session. show linetest single avail-sess 21.1.3 Start the Talking Father test configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest 21.1.4 Terminate call (Put phone on-hook) Put only the phone on-hook for the line on which one intends to do the ring test. Applied to the above example: put the phone for line 1/1/1/1/2 on-hook but do not put the phone for line 1/1/1/4 on-hook! Reason: In the above example, first of all the phone for line 1/1/1/1/2 is put on-hook. In a next step the ring test is performed. Now one can hear the line 1/1/1/1/2 is ringing. Then when going off-hook on line 1/1/1/1/2, one still find line 1/1/1/1/2 and line 1/1/1/1/4 being in conversation. Thus, do not put the phone for line 1/1/1/4 on-hook. show voice sip termination [if-index)] 21.1.5 Start the Ring Subscriber Sub. configure linetest single ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low ring-subscrib-sub test-parm-num 0 test-mode interactive show linetest single ltline 1 show linetest single lineid-ext-rept 1 21.1.6 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 22 TALKING FATHER.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-49 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

22.1 DP DTMF Signal Sub. 22.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice sip termination [if-index)] 22.1.2 Show the available Session. show linetest single avail-sess 22.1.3 Start the Talking Father test configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest 22.1.4 Start the DP DTMF Signal Sub configure linetest single ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low dpdtmf-signal-sub test-parm-num 1 test-mode interactive configure linetest single ltparm 1 test-name(unit) dpdtmf-signal-sub value1 6 configure linetest single ltsession 1 session-cmd start-subtest 22.1.5 Press digits. show linetest cluster 1 lineid-ext-rept 1 22.1.6 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 23 TALKING FATHER. 23.1 Userloop Sub. 23.1.1 Line to be involved in call: call status = connected & test status = no-testing. show voice sip termination [if-index)] 23.1.2 Show the available Session. show linetest single avail-sess

TAP 1109-50 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 1109 — Integrated NBLT for SIP Termination

23.1.3 Start the Talking Father test configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low talking-father test-parm-num 0 test-mode interactive configure linetest single ltline 1 lineid 1/1/1/1/2 line-status intest configure linetest single ltsession 1 session-cmd starttest 23.1.4 Start the User Loop Sub. configure linetest single ltsession 1 session-cmd recv-subtest ownerid 1 timeout-period 6000 line-num 1 type-high none type-low userloop-sub test-parm-num 0 test-mode interactive configure linetest single ltsession 1 session-cmd start-subtest show linetest single lineid-ext-rept 1 23.1.5 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 24 ELECTRONIC RINGER DETECTION. 24.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index)] 24.2 Show the available Session. show linetest single avail-sess 24.3 Start the Status Monitoring test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low etsi-signature test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 24.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy 25 LONGITUDINAL CURRENT 25.1 Line is in idle state: call- status = on-hook & test-status = no-testing. show voice sip termination [if-index) Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 1109-51 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 1109 — Integrated NBLT for SIP Termination

25.2 Show the available Session. show linetest single avail-sess 25.3 Start the Status Monitoring test. configure linetest single ltsession 1 session-cmd create ownerid 1 timeout-period 6000 line-num 1 type-high none type-low longitudinal-current test-parm-num 0 test-mode single configure linetest single ltline 1 lineid 1/1/1/7/1 line-status intest configure linetest single ltsession 1 session-cmd starttest show linetest single ltline 1 show linetest single lineid-ext-rept 1 25.4 Free the NBLT session. configure linetest single ltsession 1 session-cmd destroy

TAP 1109-52 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting Purpose This TAP provides steps to use the EMS (5520 AMS), CLI, or TL1 to isolate and troubleshoot a problem indicated by an alarm.

General Resolve alarms that affect service before alarms that do not affect service. Use local procedures to correct problems associated with customized alarms. In the event of problems during this procedure, contact Alcatel-Lucent technical support; see http://www.alcatel-lucent.com/support. Use the alarm information obtained from the EMS Event Viewer during analysis. Use the CLI or TL1 autonomous messages generated during trouble locating and additional data, such as visual or audible alarms, when available. Service states should also be considered.

Caution — When an alarm has been disabled, it is not generated or displayed in the EMS Event Viewer.

See the CLI Commands for FD 24Gbps NT document for information about CLI syntax. See the TL1 Commands and Messages for FD 24Gbps NT document for information about TL1 syntax. Several of the protocols in this TAP may require the assistance of someone familiar with UNIX systems and commands. Many of the UNIX troubleshooting protocols and most of the UNIX commands require root access. In these cases, Alcatel-Lucent recommends that a UNIX system administrator perform the troubleshooting.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

Supported alarms are grouped by alarm type in Table TAP 2104-2 and Table TAP 2104-3. Table TAP 2104-1 describes the parameters provided for each alarm in Tables TAP 2104-2 and TAP 2104-3: Table TAP 2104-1: Description of alarm parameters Parameter name

Parameter description

No.

Provides the unique identification number of the alarm

Alarm name

Provides a descriptive alarm name followed by the alarm names shown in CLI and TL1:

• •

CLI: the alarm name as it appears in the CLI configure alarm command TL1: the value of the condition parameter in the output of the appropriate REPT ALM command

Alarms that can only be viewed using CLI do not show a TL1 alarm name, and alarms that can only be viewed using TL1 do not show a CLI alarm name. Class

Indicates the alarm class: communication (Com), processing errors (Proc), quality of service (QoS), environmental (Envir), or equipment (Eqp) You can use the class column of the table to help locate an alarm in the table. The alarm class is not displayed in TL1.

Sev.

Indicates the severity level assigned to the alarm (text in parentheses shows the abbreviations used in Tables TAP 2104-2 and TAP 2104-3): indeterminate (Ind), warning (War), minor (Min), major (Maj), or critical (Crit)

SA

Indicates whether the alarm is service affecting (SA) or non-service affecting (NSA)

NE type

Indicates whether the alarm applies to the 7302 ISAM (7302), the 7330 ISAM FTTN (7330), or both

Description

Describes the conditions that generates the alarm

Troubleshooting recommendations

Provides recommended troubleshooting steps

Note — Except where otherwise specified, the report and logging modes for all alarms are enabled.

TAP 2104-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

Procedure Use this procedure to isolate and troubleshoot a fault indicated by an alarm. 1

2

Choose one of the following methods to access the alarms: a

To access the alarms using the 5520 AMS, see the NTP for managing alarms in the Operations and Maintenance Using 5520 AMS.

b

To access the alarms using CLI, see the NTP for monitoring alarms in the CLI Commands for FD 24Gbps NT guide.

c

To access the alarms using TL1, see the NTP for monitoring alarms in the TL1 Commands and Messages for FD 24Gbps NT guide.

Use the following tables to help you determine the cause of the alarm and the appropriate action for resolving the alarm.

• •

Table TAP 2104-2: System alarm definitions Table TAP 2104-3: SHub alarm definitions

Alarms are grouped by alarm types. See Table TAP 2104-1 for a description of the parameters listed in Tables TAP 2104-2 and TAP 2104-3.

Note 1 — If multiple alarms are present, resolve the alarms in the following order: Critical, Major, Minor. Note 2 — Note that the term “board” as it appears in the alarm names is referred to as either “unit” or “card” throughout the documentation. For example, the NANT-A card is a type of NT unit and the NVLT-G card is a type of LT unit. Table TAP 2104-2: IACM alarm definitions for the 7302 ISAM, the 7330 ISAM FTTN, and the 7356 ISAM FTTB No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

Alarm type = Equip (1) - Index1 = eqptHolderId (Index in equipment holder Table), Index2 = see specific alarm number. 1

Eqp

Crit

Y

persist-data-loss

The system has lost all persistent data after a restart. The system is not configured.

Reconfigure the system.

Index 2 is not used. 2

Eqp

Maj

N

sntp-comm-lost

The SNTP server does not respond to the requested messages.

Check the SNTP server.

Index 2 is not used. 4

Eqp

Maj

N

nt-disk-95%full

The NT disk is 95% full. Index 2 = partition (0 is ISAM SW, 1 is ONT SW)

Clean up the disk space on the NT.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

5

Com

Maj

Y

preferred-mode

The system is configured to synchronize to an external source and a source other than the configured highest priority source is being used to derive synchronization.

Check that the external source signals at the BITS inputs to the system are within specification.

This alarm applies only when using the basic clock management feature. Index 2 is not used. 6

Com

Crit

Y

timing-reference

The system is configured to synchronize to an external source, and the system is deriving synchronization using the internal source due to a failure on the external source signal.

Check that the external source signals at the BITS inputs to the system are within specification.

In Enhanced Clock management, this alarm applies to the state of the external clock sources (see alarm type Sync [134]) independently of the manual clock selection configuration (FORCE). Index 2 is not used. 8

Eqp

Crit

Y

shub-loc

The NT cannot communicate with the SHub or the IHub.

Wait until the SHub or the IHub has finished rebooting.

Index 2 is not used. 25

Eqp

Maj

N

back-pnl-inv

The FD back panel type read from SMAS case is an unknown type. Index 2 is not used.

28

Eqp

Crit

Y

SHub: shub-conf-loss IHub: link-conf-mismatch

The SHub/IHub configuration saved on the NT unit differs from the current SHub/IHub configuration. The last changes on the SHub/IHub database (in between two configuration save actions) were lost due to a subsystem reset.

The system will start up with the default back panel. Check the back panel type configuration when the system is running. Compare the SHub/IHub configuration with the database (last database changes may be lost).

Index 2 is not used. Alarm type = EquipHolder (2); Index1 = eqptHolderId (index in equipment holder table), Index2 = not used 1

Eqp

TAP 2104-4

Min

N

rack-power

The power fuse is broken.

Check the power supplies.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

2

Eqp

Maj

N

rack-fan-unit1

One or more fan has failed or the fan unit has been removed from the shelf.

Check the fan.

This alarm applies only to the ERAM-A Remote Aggregator. 7

9

10

Eqp

Eqp

Eqp

Min

Maj

Min

N

Y

N

shelf-mismatch

shelf-missing

shelf-install-missing

A shelf detected, but the actual shelf type is unknown or it differs from the planned shelf type.

Check the equipment.

A shelf is planned, but no shelf is detected. A shelf has been detected at least once since the shelf was planned.

Verify if there is a shelf-expander unit on the host shelf.

Shelf is planned, but no shelf detected. No shelf has been detected since it is was planned.

Check the configuration.

Check the cabling to the ES. Verify there is an EDSE-A board on the ES. Verify there is at least one LT unit on the ES. Verify there is a PWIO-B on the ES. Check the fan on the ES. Check the power cable on the ES.

15

Envir

Min

N

door

Open FD cabinet door

Close the door.

21

Eqp

Min

N

test-chain-config

The test chain configuration does not support the test requested.

Configure the test chain to support the test requested.

22

Eqp

Min

N

tau-problem

The test cannot be completed because the TAU board is not present or has failed.

A TAU board may be faulty. Force a cold reset of the board. If the board fails again, send the board for repair.

23

Eqp

Min

N

itsc-problem

The test cannot be completed because the ITSC module board is not present or has failed.

The ITSC module may be faulty. Force a cold reset of the board. If the board fails again, send the board for repair.

24

Eqp

Min

N

test-resources

The test cannot be completed because one or more other test resources are not present (for example, the shelf is not available).

Verify the test equipment.

25

Eqp

Min

N

hw-fail

The test equipment has failed during a test.

Force a cold reset of the board. If the board fails again, send the board for repair.

Other equipment reported a hardware failure. 26

Eqp

Min

N

test-blk-sw-download

Test requests are blocked during the ITSC module software download.

Wait until the download is complete before starting a test (test requests are temporarily blocked while a software download is in progress).

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

27

Eqp

Maj

N

test-blk-fail-download

Test requests are blocked when a ITSC software download failure has occurred.

Reset the ITSC (test requests are blocked when a software download has failed).

Alarm type = PlugInUnit (3); Index1 = eqptSlotId (index in equipment board table), Index2 = not used 3

Eqp

Min

N

board-mismatch

An LT unit is detected, but the actual unit type is unknown or differs from the planned unit type.

Check the configuration.

4

Eqp

Maj

N

waiting-for-sw

This system cannot download all the applicable software files (supported by the active OSWP) to a board because of any of the following reasons:

Check the configuration.

•

•

Download the software and wait until the software download is complete.

The board detected belongs to a board type that the active OSWP does not support. The board detected belongs to a board type that the active OSWP supports but one or more of the applicable software files are no longer available on the file disk of the NT unit.

This alarm applies only to LT units. 8

Eqp

Maj

N

temp-exceeded

The temperature threshold on the unit is exceeded. This alarm applies to NT units, LT units and NTIO units (NCNC-G/F). In remote units, the cause may be a dirty fan filter.

12

Eqp

Maj

Y

temp-shutdown

Check the fans and restart the unit. For remote units, check for a dirty fan dust filter.

The unit has powered off as a result of temperatures that are too high.

Check the ambient temperature.

This alarm applies to LT units and NTIO units (NCNC-G/F).

Check the unit.

Check the operation of the fans.

14

Eqp

Maj

Y

board-missing

Unit is planned, no unit is detected, but a unit has been detected at least once since it was planned.

Verify that the unit is present.

15

Eqp

Min

N

board-instl-missing

Unit is planned, no unit is detected, and no unit has ever been detected since it was planned.

Insert the unit.

TAP 2104-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

16

Eqp

Maj

Y

board-init

A unit initialization failure has been detected.

Force a cold reset of the unit. If this fails, repair the unit.

This alarm applies only to LT units. 28

Eqp

Crit

Y

sem-power-fail

Power to the external -48 V dc power supply failed. SEM is running on battery power.

Check the power to the external -48 V dc power supply.

29

Eqp

Crit

Y

sem-ups-fail

External SEM power supply or the batteries failed. The external ac power supply can still provide power, but needs to be checked to ensure uninterruptible power service.

Check for excessive voltage drop on the power feed.

30

Eqp

Maj

Y

board-reset-cf

The LT unit has reset (alarm ON followed by alarm OFF), or there is a communication failure (alarm ON).

Check cabling if alarm is persistent.

The SHub uplink is broken. The alarm is forwarded to the NT, then to the ACU.

Check the SHub uplink cable for loose contacts or missing connections.

31

Eqp

Crit

Y

shub-uplink

If alarm toggles frequently, the board will go in Card Reset Protection mode (alarm 3, 17) and power down.

Alarm type = ATM (8); Index1 = ifIndex of ATM physical port, Index2 = see specific alarm number 2

QoS

Min

Y

cell-discard-up

ATM cell discarded in the upstream direction. Index2 = VPI/VCI

No local repair action. Sender must lower shaping rate.

Report mode = disabled Logging mode = disabled 3

QoS

Min

Y

cell-discard-down

ATM cell discarded in the downstream direction. Index2 = VPI/VCI

No local repair action. Sender must lower shaping rate.

Report mode = disabled Logging mode = disabled Alarm type = CustomizableAlarm (10); Index1 = rack ID (position of the rack), Index2 = not used (3) 1

Envir

Ind

N

custom1

Customizable alarm 1 alarm.

—

2

Envir

Ind

N

custom2

Customizable alarm 2 alarm.

—

3

Envir

Ind

N

custom3

Customizable alarm 3 alarm.

—

4

Envir

Ind

N

custom4

Customizable alarm 4 alarm.

—

5

Envir

Ind

N

custom5

Customizable alarm 5 alarm.

—

Alarm type = CustomizableAlarm (10); Index1 = eqptHolderID (shelf index in equipment holder table), Index2 = not used (4)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

11

Envir

Ind

N

he-custom1

Host/expansion customizable alarm 1 alarm

—

12

Envir

Ind

N

he-custom2

Host/expansion customizable alarm 2 alarm

—

13

Envir

Ind

N

he-custom3

Host/expansion customizable alarm 3 alarm

—

14

Envir

Ind

N

he-custom4

Host/expansion customizable alarm 4 alarm

—

15

Envir

Ind

N

he-custom5

Host/expansion customizable alarm 5 alarm

—

This alarm does not apply to the ERAM-A Remote Aggregator. 16

Envir

Ind

N

he-custom6

Host/expansion customizable alarm 6 alarm

—

This alarm does not apply to the ERAM-A Remote Aggregator. Alarm type = IMA-group (13); Index1 = IfIndex of IMA-group, Index2 = not used 1

Com

Min

Y

ima-grp-fe-su

The far-end is starting up.

Check the IMA group configuration at the far-end.

2

Com

Min

Y

ima-grp-fe-cfg

The far-end is not configured properly.

Check which configurations are supported at the near-end and the far-end.

3

Com

Min

Y

ima-grp-ne-cfg

The near-end is not configured properly.

Check which configurations are supported at the near-end and the far-end.

4

Com

Min

Y

ima-grp-fe-nl

There is an insufficient number of links at the far-end.

Check the status of the links at the far-end.

5

Com

Min

Y

ima-grp-ne-nl

There is an insufficient number of links at the near-end.

Check the status of the links at the near-end.

6

Com

Min

Y

ima-grp-fe-blk

The far-end is blocked.

Check the status of the IMA group at the far-end.

Alarm type = IMA-link (14); Index1 = IfIndex of IMA-link, Index2 = not used 2

Com

Min

Y

ima-lnk-lif

One or more IMA frames are lost.

Check the clock associated with this link.

3

Com

Min

Y

ima-lnk-lods

The link is out of delay synchronization.

Check the clock configuration for the associated group.

4

Com

Min

Y

ima-lnk-misc

There is a connection problem in the link.

Check the link configuration at the far-end.

5

Com

Min

Y

ima-lnk-rfi

There is a remote link failure.

Check the state of the associated facility.

TAP 2104-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

6

Com

Min

Y

ima-lnk-fault

There is a fault in the link facility.

Check for problems with the associated facility.

7

Com

Min

Y

ima-lnk-txblk

The transmission is blocked because of a problem at the far-end.

Check the link configuration at the far-end.

8

Com

Min

Y

ima-lnk-rxblk

The reception is blocked because of a problem at the far-end.

Check the link configuration at the far-end.

Alarm type = Redundancy (20); Index1 = not used, Index2 = not used 1

Eqp

Maj

N

loss-over-cap

The switchover capability in a redundant system has been lost.

Check the link on the standby NT unit. Check the standby units. Wait for the Quench timeout.

3

Eqp

Maj

Y

ping-check-fail

The ping connectivity check to a specific destination IP address has failed.

Check the transmitting fiber cable. Check the default gateway configuration. Check if the configured IP address for the ping connectivity check is correct.

Alarm type = SHDSL (23); Index1 = ifIndex of SHDSL physical port, Index2 = device ID 11

Com

Min

Y

shdsl-n-loopback

Loopback is active on the network side.

Testing is in progress.

12

Com

Min

Y

shdsl-c-loopback

Loopback is active on the customer side.

Testing is in progress.

13

Com

Min

Y

shdsl-conferr

There is a configuration error.

Check the configuration parameters supported by the device.

14

Com

Min

Y

shdsl-atm-lcd

Loss of ATM cell delineation

Check the clock subsystem or the ATM configuration.

15

Com

Min

Y

shdsl-lpr

Loss of power at STU-R

Check the power supply at the STU-R.

16

Com

Min

Y

shdsl-secu-err

Unable to disable STU-R access

Check for devices that do not support disabling the STU-R access.

17

Eqp

Min

Y

shdsl-dev-fault

Device fault

Check the equipment.

18

Com

Min

Y

shdsl-atm-ncd

No ATM cell delineation

Check the clock subsystem or the ATM configuration.

Alarm type = SwMgnt (29); Index1 = see specific alarm, Index2 = not used

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Proc

Maj

Y

sw-rollback

The system cannot make the NotActive OSWP and linked database operational (although no error in the database is detected). The system performs an implicit rollback to the previous active OSWP (and linked database).

Remove the corrupted OSWP (abort operation). Download the desired OSWP again. Activate the downloaded OSWP.

Index1 = eqptSlotId of NT unit 2

Proc

Maj

Y

db-rollback

The system cannot make the selected OSWP and linked database operational (an error is detected in the linked database). The system comes up with the selected OSWP and the previous linked database (if possible).

Download the desired database again.

Index1 = eqptSlotId of NT unit 4

Proc

Maj

Y

xvps-inv-dbase

The voice package server unit has experienced a database corruption. The unit started with the default database.

Download the desired database again. Restore the desired database.

Index1 = lowest eqptSlotId of the active voice package server 5

Proc

Maj

Y

inv-cde-file

This alarm is raised by the NT unit when the CDE file in the voice package server unit is corrupted. The voice package server unit started with the default CDE values.

Download the desired CDE file again. Activate the downloaded CDE file.

Index1 = lowest eqptSlotId of the active voice package server 6

8

Proc

Proc

Maj

Maj

Y

Y

miss-cde-file

cde-hash-error

This alarm is raised by the NT unit when there is no CDE file to download to the voice package server unit.

Download the desired CDE file again.

This alarm is raised by the NT unit when a new CDE profile is active but this CDE profile hash key is wrong.

Download a new CDE profile with valid hash key

Activate the downloaded CDE file.

Activate the downloaded CDE file.

Alarm type = TmpFilter (34); Index1 = 0, Index2 = 0 Note: These values are inherited from the related basic alarm 1..31

Com

Ind(2)

N(2)

der-temp1..31

Derived alarm for temporal filter.

Check the cause of the related basic alarm.

Report mode = disabled

Check the setting of the related temporal filter.

Logging mode = disabled

TAP 2104-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

Derived alarm for spatial filter.

Check the cause of the related basic alarm.

Report mode = disabled

Check the setting of the related spatial filter.

Alarm type = SpaFilter (35); Index1 = 1, Index2 = not used 1..31

Com

Ind(2)

N(2)

der-spa1..31

Logging mode = disabled Alarm type = xDSL (38); Index1 = ifIndex of xDSL physical port, Index2 = not used 1

Com

Min

Y

xdsl-ne-los

A near-end loss of signal has occurred.

Check the physical line.

2

Com

Min

Y

xdsl-ne-lof

A near-end loss of frame has occurred.

Check modem equipment.

3

Com

Min

Y

xdsl-ne-lom

A near-end loss of margin has occurred.

Check the physical line (new distributors).

4

Com

Min

Y

xdsl-ne-ese

Near-end excessive server errors have occurred.

Check the physical communication medium.

5

Com

Crit

Y

xdsl-act-cfg-error

The line configuration data cannot be used.

Update the profile parameters. Ensure that the pilot tones are not marked. If Glite is used, ensure that the bit rates fit within the standard.

6

Com

Maj

Y

xdsl-act-not-feas

The line capacity is not high enough to set up the requested profile.

Check the configuration data. Check the physical line (length and noise).

7

Com

Min

Y

xdsl-up-br-reach

The upstream planned bit rate was not reached after initialization.

Lower planned upstream bit rate.

8

Com

Min

Y

xdsl-ne-ncd

A near-end cell delineation has occurred.

Check the quality of the line.

9

Com

Min

Y

xdsl-ne-lcd

A loss of near-end cell delineation has occurred.

Check the quality of the line.

10

Com

Min

Y

xdsl-fe-los

A far-end loss of signal has occurred.

Check the physical line.

11

Com

Min

Y

xdsl-fe-lof

A far-end loss of frame has occurred.

Check modem equipment.

12

Com

Min

Y

xdsl-fe-lpr

A far-end loss of power was detected.

There is no repair required because this is the normal power-down of CPE.

13

Com

Min

Y

xdsl-fe-lol

A far-end loss of link was detected.

Check the physical line.

14

Com

Min

Y

xdsl-fe-lom

A far-end loss of margin has occurred.

Check the physical line (new distributors).

15

Com

Min

Y

xdsl-fe-ese

Far-end excessive server errors have occurred.

Check the physical line.

16

Com

Maj

Y

xdsl-act-comm

Unsuccessful initialization as a result of communication problems

Check the peer modem type. Check the physical line.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

17

Com

Min

Y

xdsl-act-modem

Peer modem not detected

Wait until the modem is connected. Check the physical line.

18

Com

Min

Y

xdsl-do-br-reach

The downstream planned bit rate was not reached after initialization.

Lower the planned downstream bit rate.

19

Com

Min

Y

xdsl-fe-ncd

A far-end cell delineation has occurred.

Check the quality of the line.

20

Com

Min

Y

xdsl-fe-lcd

A far-end loss of cell delineation has occurred.

Check the quality of the line.

23

Com

Min

Y

xdsl-fe-upbo-vio

A far-end UPBO violation has occurred.

Check the peer modem type.

24

Com

Maj

Y

xdsl-fe-cpe-pol

There was an activation failure due to CPE policing.

Check the peer modem type.

25

Com

Maj

Y

xdsl-tpstc-mis

A mismatch is detected between the configured TPS-TC mode and the mode supported by the connected CPE.

Check the peer modem type or change the TPS-TC mode of the line.

26

Com

Maj

Y

xdsl-frtx-init-fail

No successful initialization due to forced RTX while RTX is not supported at one or both ends.

Ensure that Standard ARQ (ITU-T G.998.4) is supported at both ends (LT, CPE) or modify/unconfigure the retransmission (RTX) profile.

27

Com

Min

Y

xdsl-vect-dle

Loss of upstream signal due to disorderly leaving event.

Check physical line.

Alarm type = xDSLTca (39); Index1 = ifIndex of xDSL physical port, Index2 = not used 1

2

3

QoS

QoS

QoS

Min

Min

Min

N

N

N

xtca-ne-es

xtca-ne-ses

xtca-ne-uas

The number of errored seconds encountered by the ADSL line in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of severely errored seconds encountered by the ADSL line in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of unavailable seconds encountered by the ADSL line in the current 15-minute interval has reached its threshold value.

Check the physical line.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

TAP 2104-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

4

QoS

Min

N

xtca-ne-day-es

The number of errored seconds encountered by the ADSL line in the current one-day interval has reached its threshold value.

Check the physical line.

The number of severely errored seconds encountered by the ADSL line in the current one-day interval has reached its threshold value.

Check the physical line.

The number of unavailable seconds encountered by the ADSL line in the current one-day interval has reached its threshold value.

Check the physical line.

The number of errored seconds encountered by the ADSL far-end line in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of severely errored seconds encountered by the ADSL far-end line in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of unavailable seconds encountered by the ADSL far-end line in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of errored seconds encountered by the ADSL far-end line in the current one-day interval has reached its threshold value.

Check the physical line.

The number of severely errored seconds encountered by the ADSL far-end line in the current one-day interval has reached its threshold value.

Check the physical line.

5

6

7

8

9

10

11

QoS

QoS

QoS

QoS

QoS

QoS

QoS

Min

Min

Min

Min

Min

Min

Min

N

N

N

N

N

N

N

xtca-ne-day-ses

xtca-ne-day-uas

xtca-fe-es

xtca-fe-ses

xtca-fe-uas

xtca-fe-day-es

xtca-fe-day-ses

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

12

QoS

Min

N

xtca-fe-day-uas

The number of unavailable seconds encountered by the ADSL far-end line in the current one-day interval has reached its threshold value.

Check the physical line.

The number of low error-free throughput seconds encountered by the xDSL line in the current 15 minutes interval has reached its threshold value.

Check the physical line.

The number of low error-free throughput seconds encountered by the xDSL line in the current one-day interval has reached its threshold value.

Check the physical line.

The number of low error-free throughput seconds encountered by the xDSL far end line in the current 15 minutes interval has reached its threshold value.

Check the physical line.

The number of low error-free throughput seconds encountered by the xDSL far end line in the current one-day interval has reached its threshold value.

Check the physical line.

13

14

15

16

QoS

QoS

QoS

QoS

Min

Min

Min

Min

N

N

N

N

xtca-leftrs

xtca-day-leftrs

xtca-fe-leftrs

xtca-fe-day-leftrs

Check the modem equipment.

Check the modem equipment. If this does not solve the problem, check whether the RTX configuration is in accordance with the noise conditions expected/observed on the line. Check the modem equipment. If this does not solve the problem, check whether the RTX configuration is in accordance with the noise conditions expected/observed on the line. Check the modem equipment. If this does not solve the problem, check whether the RTX configuration is in accordance with the noise conditions expected/observed on the line. Check the modem equipment. If this does not solve the problem, check whether the RTX configuration is in accordance with the noise conditions expected/observed on the line.

Alarm type = bonding (54); Index1 = IfIndex of bonding group, Index2 = not used 1

Com

Min

Y

up-plan-bitrate

Group upstream actual bit rate is above group upstream minimum bit rate but below group upstream planned bit rate.

Lower group upstream planned bit rate.

TAP 2104-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

2

Com

Min

Y

up-min-bitrate

Group upstream actual bit rate dropped below group upstream minimum bit rate.

Check physical line.

Group upstream actual bit rate is not high enough to set up the configured group upstream minimum bit rate.

Check configuration data.

3

Com

Maj

Y

up-config-notfeas

Check line state.

Check physical line.

4

Com

Min

Y

down-plan-bitrate

Group downstream actual bit rate is above group downstream minimum bit rate but below group downstream planned bit rate.

Lower group downstream planned bit rate.

5

Com

Min

Y

down-min-bitrate

Group downstream actual bit rate dropped below group downstream minimum bit rate.

Check physical line.

Group downstream actual bit rate is not high enough to set up the configured group downstream minimum bit rate.

Check configuration data.

The CPE connected does not support bonding.

Check the modem.

The lines of the bonding group are connected to more than one CPE.

Check the xDSL wiring configuration.

6

8 9

Com

Com Com

Maj

Min Maj

Y

Y Y

down-config-not-feas

non-bonding-cpe multiple-cpes

Check line state.

Check physical line.

Check the physical lines.

Check the CPE.

10

Com

Maj

Y

register

A discovery or aggregation register failure is detected.

Check the CPE.

11

Com

Min

N

group-incomplete

Not all configured lines of the bonding group are actually part of the bonding group.

Check the xDSL wiring configuration. Check the CPE.

Alarm type = authentication (55); Index1 = ifIndex of interface on which authentication occurs (for example, the bridge port interface for 802.1x, the PPPoE interface for PPPoE), Index2 = not used 2

Proc

Maj

Y

vlan-assign-fail

Failure to assign a VLAN for a user session:

Check the system configuration.

•

Check the RADIUS server configuration.

•

unknown VLAN: VLAN returned by RADIUS server is not locally configured in the system; or no VLAN: RADIUS server did not return a VLAN while no default VRF is locally configured for the domain.

Alarm type = authentication (58); Index1 = BRAS IP address, Index2 = BRAS TCP Port

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Com

Maj

N

NA

The alarm is raised when the ISAM has at least one ANCP Session with a certain BRAS that leaves the established state. It is cleared when all the ANCP Sessions with that BRAS enter the established state, or when all the ANCP Sessions with that BRAS are deleted by the operator.

Check the administrative status of all ANCP Adjacency components. For example: the interfaces, the virtual router, the VLAN. Check the compatibility of the ANCP capabilities, partition ID, TCP port number, BRAS IP address, both for the peer equipment and the ISAM.

Alarm type = SFP (76); Index1 = hostSfpFaceplateNumber, Index2 = lanxPortNumber (SHub) or Ethernet Port (IHUB) 1

Com

Crit

Y

host-sfp-los

Host shelf downlink SFP loss of signal.

Check the physical line.

This alarm applies only to an ERAM-A Remote Aggregator. 2

Com

Crit

Y

host-sfp-tx-fail

Host shelf downlink SFP transmission failure.

Check the host shelf SFP module.

This alarm applies only to an ERAM-A Remote Aggregator. 3

Com

Crit

Y

host-sfp-not-prst

Host SFP missing. Host shelf downlink SFP detected but later removed.

Check the host shelf SFP presence.

This alarm applies only to an ERAM-A Remote Aggregator. 4

Com

Crit

Y

host-sfp-inv-id

Host shelf downlink SFP does not have a valid Alcatel-Lucent ID.

Check the host shelf SFP module ID.

This alarm applies only to an ERAM-A Remote Aggregator. 5

Com

Crit

Y

host-sfp-ctrl-fail

Host shelf downlink SFP control failure.

Check the host shelf SFP module or I2C bus.

This alarm applies only to an ERAM-A Remote Aggregator. 6

Eqp

Min

N

host-sfp-rmtlt

The host SFP is not assigned to any remote LT units but a connection to a remote LT unit is detected.

Check for missing host SFP assignment configuration. Check if the remote LT unit is cabled to the wrong host SFP.

TAP 2104-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

7

Eqp

Major

Y

host-sfp-mismatch

The detected slot ID of the remote LT that is cabled to the Host-side SFP module does not match the assigned remote LT slot ID that is configured for the Host-side SFP module.

Check for cabling error or Host-side SFP assignment configuration error.

This alarm applies only to an ERAM-A Remote Aggregator. 8

Eqp

Min

N

host-sfp-incompt

The actual shelf type of the remote LT that is cabled to the Host-side SFP module does not match the planned shelf type of the assigned remote LT configured for the Host-side SFP module.

Check for cabling error, shelf type planning error or assignment configuration error.

Alarm type = SFP (76); Index1 = eqptSlotId of corresponding LT unit in ES, Index2 = not used 11

Com

Crit

Y

exp-sfp-los

ES SFP loss of signal.

Check the physical line.

This alarm applies only to an 7330 ISAM FTTN shelf. 12

Com

Crit

Y

exp-sfp-tx-fail

ES SFP transmission failure.

Check the ES SFP module.

This alarm applies only to an 7330 ISAM FTTN shelf. 13

Com

Crit

Y

exp-sfp-not-prst

ES SFP missing. ES SFP detected but later removed.

Check the ES SFP presence.

This alarm applies only to an 7330 ISAM FTTN shelf. 14

Com

Crit

Y

exp-sfp-inv-id

ES SFP does not have a valid Alcatel-Lucent ID.

Check the ES SFP module ID.

This alarm applies only to an 7330 ISAM FTTN shelf. 15

Com

Crit

Y

exp-sfp-ctrl-fail

The SFP alarm for the ES downlink SFP control failure.

Check the ES SFP module or I2C bus.

This alarm applies only to an 7330 ISAM FTTN shelf. 16

Com

Crit

Y

exp-sfp-1-los

Loss of signal on SFP 1. This alarm applies only to the SB-REM and the FD-SEM.

Check the connections on the optical link. Check if the attenuation on the optical link is excessive. Check the SFP status on the host shelf and remote LT.

17

Com

Crit

Y

exp-sfp-2-los

Loss of signal on SFP 2. This alarm applies only to the SB-REM.

Check the connections on the optical link. Check if the attenuation on the optical link is excessive. Check the SFP status on the host shelf and remote LT.

Alarm type = LLURelay (78); Index1 = eqptSlotId (index in equipment card table), Index2 = not used

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Com

Maj

Y

llu-relay-status

LLU relay set for some ports, but applique inserted in slot is not compatible with LLU relay.

Replace the applique by an applique compatible with the LLU relay.

Alarm type = SHDSL_ISAM (82); Index1 = IfIndex of SHDSL physical port, Index2 = linkID (higher 16 bits) + device ID (lower 16 bits) 3

Com

Min

Y

shdsl-n-losw

Loss of synchronization word on the network side on each pair

Check the signal on the network side.

4

Com

Min

Y

shdsl-c-losw

Loss of synchronization word on the customer side on each pair

Check the signal on the customer side.

5

Com

Min

Y

shdsl-n-aten

Loop attenuation alarm on the network side on each pair

Check the signal on the network side.

6

Com

Min

Y

shdsl-c-aten

Loop attenuation alarm on the customer side on each pair

Check the signal on the customer side.

7

Com

Min

Y

shdsl-n-snr

Signal-to-noise ratio alarm on the network side on each pair

Check the signal on the network side.

8

Com

Min

Y

shdsl-c-snr

Signal-to-noise ratio alarm on the customer side on each pair

Check the signal on the customer side.

9

Com

Min

Y

shdsl-n-dccont

DC continuity fault on the network side on each pair

Check the equipment and wiring on the network side.

10

Com

Min

Y

shdsl-c-dccont

DC continuity fault on the customer side on each pair

Check the equipment and wiring on the customer side.

19

Com

Min

Y

shdsl-c-actfail

Activation failed at a customer segment termination.

Check the CO wiring of the different segments.

Alarm type = CustomExternalAlarms (83); Index1 = eqptSlodId (index in equipment card table), Index2 = not used 1

Eqp

Maj

N

custextalarm1

SB-REM customizable external alarm 1

—

2

Eqp

Maj

N

custextalarm2

SB-REM customizable external alarm 2

—

3

Eqp

Maj

N

custextalarm3

SB-REM customizable external alarm 3

—

4

Eqp

Maj

N

custextalarm4

SB-REM customizable external alarm 4

—

5

Eqp

Maj

N

custextalarm5

SB-REM customizable external alarm 5

—

Alarm type = PlugInUnit2 (84); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 1

Eqp

Maj

N

pluginfan

REM fan power alarm

Check the REM fan.

This alarm applies only to the SB-REM shelf.

TAP 2104-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

2

Eqp

Maj

N

plugin-dc-a

REM DC A voltage low. DC B takes over.

Check the fuse.

This alarm applies only to the SB-REM shelf. 3

Eqp

Maj

N

plugin-dc-b

REM DC B voltage low. DC A takes over. This alarm applies only to the SB-REM shelf.

4

Eqp

Crit

Y

plugin-dg

REM dying gasp alarm. REM going out of service due to power shutdown. Possible causes: power failure, mains switch off, excessive over temperature, an so on.

Check the power cabling.

Check the fuse. Check the power cabling.

Check the following at the REM and the cabinet: cabling, fuse, temperature, on and off switch.

This alarm applies only to the SB-REM shelf. 5

Eqp

Crit

Y

apsf-alarm

Applique power supply malfunction. The relays are no longer configurable and are switched to the hardware default position.

Check applique power supply.

6

Eqp

Maj

Y

ntr-a-loss

The LT unit reports an NTR loss event when the NTR signal is not available. An NTR-A loss is reported even when there is no NT unit in the NT-A slot.

Check the status of the NT-A NTR.

7

Eqp

Maj

Y

ntr-b-loss

The LT unit reports an NTR loss event when the NTR signal is not available. An NTR-B loss is reported even when there is no NT unit in the NT-B slot.

Check the status of the NT-B NTR.

8

Eqp

Min

N

lt-problem

The test cannot be completed because of missing test equipment. The LT unit is not present or has failed.

Verify compatibility with ITSC tests.

The test cannot be completed because of missing test equipment. The applique is not present, not compatible or failed, or the LT unit is not compatible with the applique.

Check the applique. Verify compatibility with the LT unit for test.

9

Eqp

Min

N

applique-problem

Force a cold reset of the board. If the board fails again, send the board for repair.

Force a cold reset of the board. If the board fails again, send the board for repair.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

11

Eqp

Crit

Y

xvps-conf-loss

The voice package server configuration saved on the NT unit differs from the actual configuration on the voice package server. The changes to the voice package server database that were made between two configuration save actions were lost due to a reset of the NT unit or of the voice package server unit.

Compare the configuration on the voice package server configuration saved on the NT unit with the configuration on the voice package server unit. If there are differences, manually save the configuration that is on the voice package server unit to the NT unit.

Index1 = lowest eqptSlotId of the active voice package server pair 12

Eqp

Min

N

mac-entry-nofree

There are no available MAC entries in the MAC table on the LT unit.

No special repair action needed.

17

Eqp

Maj

Y

fibre-conn-mismatch

The detected FD-REM controller board serial number does not match the configured value.

Check the physical connection of the FD-REM.

Note: This alarm is only supported for certain customers (based on the operator ID) 18

Eqp

Maj

N

link-cap-mismatch

The actual link speed is not in line with the end-to-end link capability between NT and remote LT. The end-to-end link capability takes into account the speed capability of equipment between (and including) NT and LT (i.e. speed capability of NT, NTIO, host SFP, remote SFP, CTRL board, Hi-Cap License and LT).

Check the configuration of the CTRL board identification of the FD-REM

Check for faulty fiber link, NTIO, host SFP, remote SFP and CTRL board (on FD-REM).

Index1 = eqptSlotId of the LT. 19

Eqp

Min

N

eqpt-cap-mismatch

HighCap key is enabled. NT and LT are both HighCap capable but at least one piece of equipment between NT and LT is not HighCap capable. The equipment between NT and LT may include NTIO, host SFP, remote SFP and CTRL board (on FD-REM).

Check the speed capability of NTIO, host SFP, remote SFP and CTRL board (on FD-REM).

Index1 = eqptSlotId of the LT.

TAP 2104-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

20

Eqp

Maj

Y

ctrl-dnld-failure

The downloading of the Software image to the controller card failed. Additional Info contains: Current Running Firmware Version of the Controller Card

Check the firmware version in the alarm. Restart the first LT plugged in the expansion shelf.

Alarm type = IntTestSealCur (85); Index1 = ifIndex of xDSL line being sealed, Index2 = not used 1

Proc

Min

N

test-exceeded-max-time

The test duration exceeded the maximum allowed duration.

Try the test again.

2

Eqp

Min

N

dc-termination

The line being sealed with the sealing current is not terminated by a CPE. The sealing current process cannot proceed without DC termination on the CPE equipment.

Verify that the line on the customer side has a proper DC termination.

The line assigned to a sealing current interval could not be completed for two consecutive intervals. Possible reasons are:

Check the configuration.

3

Proc

Min

N

sc-cycle-missed

• • • 4

Eqp

Maj

N

hazardous-potential

ON duration too long too many lines per interval too many lines being tested by operator

Verify the connections of the test chain.

Check the equipment. Reduce or stop the number of manual ITSC tests to increase the time available for line sealing.

A hazardous voltage is detected on the line under test.

Verify the line at the customer side. WARNING: Ensure all proper precautions are taken to prevent injury.

5

Eqp

Min

N

femf

A foreign electromotive force is detected on the line under test.

Verify the line on the customer side.

6

Eqp

Min

N

device-protection

The ITSC board protection is activated for the line under test.

Verify the line on the customer side.

Alarm type = SIP PlugInUnit (99); Index1 = eqpSlotId (index in equipment card table), Index2 = not used 3

Com

Crit

Y

dhcp-unreach

The DHCP server is unreachable on this unit.

Check the link between the system and the DHCP server.

4

Com

Crit

Y

proxy-srv-unreach

The SIP proxy server is unreachable for this unit.

Check the link between the system and the SIP proxy server.

5

Com

Crit

Y

reg-srv-unreach

The SIP registrar server is unreachable for this unit.

Check the link between the system and the SIP registrar server.

Alarm type = SIP Termination (100); Index1 = ifIndex of PSTN physical port, Index2 = not used

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Com

Maj

Y

unknown-sub

The SIP subscriber information configured in the SIP termination does not exist on the SIP application server.

Verify if the directory number, the user name, or the URI of the SIP termination is valid.

2

Eqp

Maj

Y

ground-key

The current threshold of the physical line of the port is exceeded. The usual root causes are:

Check the cabling of the port.

• • 3

Eqp

Maj

Y

port-hightemp

The tip is connected to AC source. The ring is connected to a source of high voltage or to AC.

The temperature threshold on the physical PSTN port is exceeded. The port is automatically shut down.

Check the ambient temperature. Check the operation of the fans. Check the port.

6

Eqp

Maj

Y

port-jbfltca

The Jitter Buffer fill level threshold on this physical PSTN port is exceeded.

Check the JB fill level of the port.

7

Com

Maj

Y

reg-domainname

SIP registration failure, because of resolve domain name failure.

Check the domain name

8

Com

Maj

Y

reg-auth

SIP registration failure, because of authenticate failure

Check the authentication element

9

Com

Maj

Y

reg-timeout

SIP registration failure, because of message timeout

Check the network

10

Com

Maj

Y

reg-srvfailresp

SIP registration failure, because of failure response from server

Check the SIP server

11

Com

Maj

Y

inv-domainname

SIP invite failure, because of resolve domain name failure

Check the domain name

12

Com

Maj

Y

inv-auth

SIP invite failure, because of authenticate failure

Check the authentication element

13

Com

Maj

Y

inv-timeout

SIP invite failure, because of message timeout

Check the network

14

Com

Maj

Y

inv-srvfailresp

SIP invite failure, because of failure response from server

Check the SIP server

15

Com

Maj

Y

subs-srvfailresp

SIP subscribe failure, because of failure response from server

Check the SIP server

Alarm type = NonAlcateldev (104); Index1 = not used, Index2 = not used 1

Eqp

Crit

N

loss-env-mon

The environment box does not exist or is not alive.

Verify if there is an environment box.

Alarm type = FileTransfer (105); Index1 = file server ID (IP address), Index2 = not used

TAP 2104-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Com

Maj

N

fileserv-unavail

The system is not able to connect to the file server for a file transfer or the file transfer has failed. This alarm is raised when this event occurs. The alarm is cleared when a successful file transfer has been completed.

Check if the file transfer server is correctly configured. Check the network-to-file transfer server.

Alarm type = TrafficOverflow (106); Index1 = eqptSlotId (index in NT equipment card table), Index2 = not used 1

QoS

Min

Y

fanout

LT load overflow

Check the LT load.

2

QoS

Min

Y

up-overflow

Upstream load overflow

Check the LT load in upstream.

3

QoS

Min

Y

upobc-overflow

Upstream load to OBC overflow

Check the LT load to OBC in upstream.

4

QoS

Min

Y

dwobc-overflow

Downstream load to OBC overflow

Check the LT load to OBC in downstream.

5

QoS

Min

Y

dw-overflow

Downstream load overflow

Check the LT load in downstream.

6

QoS

Min

Y

lwpri-overflow

The number of BE and CF packets dropped exceeds the threshold.

Check the voice and video loads.

Alarm type = EthTca (107); Index1 = ifIndex of Ethernet interface, Index2 = not used 1

2

3

4

QoS

QoS

QoS

QoS

Min

Min

Min

Min

N

N

N

N

etca-los

etca-fcs

etca-day-los

etca-day-fcs

The number of LOS errors encountered by the Ethernet interface in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of FCS errors encountered by the Ethernet interface in the current 15-minute interval has reached its threshold value.

Check the physical line.

The number of LOS errors encountered by the Ethernet interface in the current one-day interval has reached its threshold value.

Check the physical line.

The number of FCS errors encountered by the Ethernet interface in the current one-day interval has reached its threshold value.

Check the physical line.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Check the modem equipment.

Alarm type = EthSFP (108); Index1 = ifIndex of Ethernet interface, Index2 = not used 1

Com

Min

Y

user-sfp-los

User SFP loss of signal

Check the physical line.

2

Com

Min

Y

user-sfp-tx-fail

User SFP transmission failure

Check the SFP module.

3

Com

Min

Y

user-sfp-not-prst

User SFP is not detected.

Check if the SFP is present.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-23 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

4

Com

Min

Y

user-sfp-inv-id

User SFP does not have a valid Alcatel-Lucent ID.

Check the module ID of the SFP.

5

Com

Crit

Y

user-sfp-t-exceed

User SFP temperature exceeds the threshold which is same as the temperature to cause board in thermal major alarm.

Check the SFP temperature.

6

Com

Min

Y

user-sfp-t-exceed

User SFP mismatches the configured speed rate (100Mbps / 1Gbps)

Check the SFP type.

Alarm type = L2Forward (109); Index1 = ifIndex of bridge port, Index2 = see specific alarm number 1

Com

Min

Y

mac-conflict

Duplicate MAC address on the bridge port indicated by Index1. The bridge port with the next MAC address is causing the conflict.

No special repair action required. Open or close the conflicted port manually if needed.

Index2 = Layer 2 forwarder ID (VLAN ID) Alarm type = QueueCounter (112); Index1 = ifIndex of physical line, Index2 = queue index 1

QoS

Min

Y

queue-drop

The number of packets dropped by the queue exceeds the threshold.

Check the corresponding queue load.

2

QoS

Min

Y

queue-load

The queue load exceeds the threshold.

Check the corresponding queue load.

Alarm type = MEGACOMediaGateway (113); Index1 = slot ID of voice package server unit, Index2 = mediaGatewayId (identifier of the affected media gateway) 1

Com

Crit

Y

mgc-unreachable

Contact is lost with the media gateway controller.

Check the network connections.

Alarm type = MEGACOSignalingGateway (114); Index1 = slot ID of voice package server unit, Index2 = signallingGatewayId (identifier of the affected signaling gateway) 1

Com

Crit

Y

sgc-unreachable

Contact is lost with the signaling gateway controller.

Check the network connections.

Alarm type = MEGACOPlugInUnit (115); Index1 = slot or equipment ID of voice package server unit(8), Index2 = accessBoardId (identifier of the slot holding the voice package server unit) 1

Com

Crit

Y

lcard-unreach-srvcard

The LT unit cannot be reached.

Check the interface between the voice package server unit and the VoIP units.

5

Eqp

Maj

Y

lcard-type-mismatch

An LT unit is detected, but the actual unit type is unknown or differs from the planned unit type.

Check the configuration on the provisioned board against the configuration on the equipped board.

Alarm type = MEGACOTermination (116); Index1 = slot or equipment ID of voice package server unit(8), Index2 = accTerminationUserPortId (identifier of the user port) 1

Com

Maj

Y

meg-unknown-sub

A subscriber profile is defined in the voice package server unit but not in the media gateway controller.

Check the user port identification.

TAP 2104-24 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

2

Eqp

Maj

Y

meg-ground-key

The current threshold for the physical line of the port was exceeded. The usual causes are:

Perform a line test.

• •

Tip is connected to the AC source. Ring is connected to a source of high voltage or AC.

3

Eqp

Maj

Y

meg-high-temp

The temperature threshold on the physical PSTN port was exceeded. The port is automatically shut down.

Perform a line test.

4

Eqp

Maj

Y

meg-act-fail

The first link layer for an ISDN subscriber failed to activate.

Perform a line test.

5

Eqp

Maj

Y

meg-over-current

The physical ISDN port is Over Current. This alarm occurs when the line current is over 40mA. Normally over-current is caused by a short circuit or an inconsistent NT device.

Perform a line test.

6

Com

Maj

Y

line-showering

There is a physical problem in the line that is causing a malfunction in the line circuit.

Check the subscriber line connections.

Alarm type = MEGACOSignalingLt (117); Index1 = slot ID of voice package server unit, Index2 = not used 2

Eqp

Crit

Y

sig-brd-persist-loss

The voice package server unit has lost all persistent data after restart. The board is not configured.

Reconfigure the system.

3

Eqp

Maj

Y

sig-brd-disk-full

The voice package server unit has reached a 90% full level.

Delete the unused data on the voice package server unit.

4

Proc

Maj

Y

sig-brd-db-rollback

The voice package server unit is not able to activate the last downloaded database.

Download the database again.

The voice signaling board resource is overloaded.

Reduce the rate at which the media gateway admits calls.

5

Eqp

Crit

Y

mg-overload

Download the correct database.

Alarm type = equipSupplemental (121) - Index1 = eqptHolderId (Index in equipment holder Table), Index2 = not used. 7

Com

Min

N

eqptsupl-syslog-upload

Upload of the NE's system log file to the system log server failed.

Check the network connectivity to the system log server. Check the system log server configuration and provisioning.

Alarm type = LSM Redundancy (131); Index1 = equipSlotID, Index2 = not used

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-25 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Eqp

Maj

N

loss-lsmswp-cap

Voice package server switchover capability in a redundant system has been lost.

Check link on standby voice package server unit.

Index1 = actual slot ID of the voice package server pair (that is, the slot ID of the preferred active voice package server unit)

Wait for quench time-out.

2

Eqp

Maj

N

inv-xvps-pair-data

The data of the active voice package server unit in a redundant configuration is different from the data of the standby server unit.

Check standby voice package server unit.

Check the data on each unit of the voice package server pair.

Index1 = actual slot ID of the voice package server pair (that is, the slot ID of the preferred active voice package server unit) Alarm type = Sync (134) – Index1 =eqptSlotId, Index2 = portType [upper 16 bits: BITS(0), SFP(1), XFP(2), IEEE(3)] + faceplatePort number [lower 16 bits: BITS-A(0), BITS-B(1), BITSOUT(2), IEEEFAIL-A(3), IEEEFAIL-B(4), SFP (0..n), XFP (1..n)] 1

Eqp

Maj

Y

bits-fail

The BITS timing source has failed or is unavailable. This alarm is only applicable for enhanced clock management.

2

Eqp

Maj

Y

synce-fail

The SyncE timing source has failed or is unavailable, moreover, if the actual QL is worse than the target QL. This alarm is only applicable for enhanced clock management.

Check the peer equipment. Check the connection between the equipment and the ISAM for the corresponding BITS timing reference. Check the peer equipment. Check the connection between the equipment and the ISAM for the timing reference for the specified synchronous Ethernet port.

3

Eqp

Crit

Y

bits-output-shutoff

System QL is lower than the configuration of the QL threshold for BITS-out, resulting in the shutoff of the BITS output. This alarm is only applicable for Enhanced Clock mgmt.

The configuration implies that the BITS output has been shutoff because the overall System QL has become worse than the configured minimum QL for BITS output.

4

Eqp

Maj

Y

bits-output-shutoff

Failure or unavailability of the IEEE1588 timing source. This alarm is only applicable for Enhanced Clock Mgnt.

Check the peer equipment and the connection between the equipment and the ISAM for the corresponding IEEE1588 timing reference.

Alarm type = MGMT Security Access (192) - Index1 = IpAddress of the Operator [Index 1 = 0 for LCT], Index2 = Management Type [upper 16 bits: CLI (0), TL1 (1)] + Session Number [lower 16 bits: see Description]

TAP 2104-26 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Com

Maj

N

login-successful

A user attempted successful login via Management Access.

Check for security measures.

The Session Number will have the range of [1 … 13 for CLI and 0...17 for TL1.] Note: This alarm shall be cleared automatically, when the same user logsoff from the same user session. Additional Info contains: "OperatorName, Login/Logout Timestamp" 2

Com

Maj

N

login-failure

Too many invalid attempts to login alarm via Management Access.

Check for security measures.

The Session number Will have the range of [100...n] This alarm will be reported after a certain period of its previous occurrence. Note: This alarm shall be cleared manually. Additional Info contains: "OperatorName, Login Timestamp" Additional Info contains: "OperatorName, Login/Logout Timestamp" Alarm type = Sip DialPlan (193) - Index1 = sipDialPlanId(index of sipDialPlanTable) , Index2=not used 1

Proc

Crit

Y

bad-digitmap

The configured digitmap is unusable.

Check the configured digitmap.

Alarm type = Sip VSP(Voice Service Provider) (194) - Index1 = sipVSPId(index of sipVSPTable) , Index2=not used 2

Com

Crit

Y

none-dns-srv

No reply for all dns servers

Check the configuration or connection of DNS servers in ISAM Voice

3

Com

Crit

Y

no-dns-srv

No DNS servers are configured when send a SIP request which need DNS server

Check the configuration of DNS servers in ISAM Voice

4

Com

Crit

Y

none-srv

ISAM Voice found that no SIP first hops are actually give reply to sip request even though there are servers configured

Check the configuration of DNS servers in ISAM Voice

5

Com

Crit

Y

no-srv

No SIP first hops are configured when send sip request

Check the configuration of DNS servers in ISAM Voice

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-27 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

6

Com

Crit

Y

reg-srv-unreach

ISAM Voice found that no register servers are actually give reply to SIP register even though there are register servers configured

Check configuration of the register servers of ISAM-V and those allowed to SIP servers ISAM-V should connected

7

Com

Crit

Y

proxy-srv-unreach

ISAM Voice found that no proxy servers are actually give reply to SIP request even though there are proxy servers configured

Check configuration of the proxy servers of ISAM-V and those allowed to SIP servers ISAM-V should connected

Alarm type = Sip Server (196) - Index1 = sipServerId(index of sipServerTable) , Index2=not used 1

Com

Crit

Y

transport-mismatch

Mismatch between the transport protocol(s) actually supported by ISAM-V and the transport protocol(s) to be used to access a SIP first hop.

Check configuration of the transport mode of ISAM Voice and those allowed to SIP servers ISAM Voice should connected.

2

Com

Crit

Y

dns-lookup-failure

DNS lookup failure

Check the configuration of DNS servers in ISAM Voice

Notes (1) For the 7330 ISAM FTTN shelf, the shelf on which the failure occurred automatically powers down after approximately 2 min if one of the following PWIO-B boards is installed: 3FE 24323 AA or 3FE 24323 AB. (2)

Same as the basic alarm

(3)

There are 5 miscellaneous alarms corresponding to ENV-1..5

(4)

There are 6 miscellaneous alarms corresponding to HESENV-1..6

(5)

Temporal filter alarms are derived from alarms in any alarm types in this table. The TL1 alarm name of a temporal filter alarm is TF-condtype, where condtype is the TL1 alarm name of the alarm from which the temporal filter alarm is derived.

(6)

Spatial filter alarms are derived from alarms in any alarm types in this table. The TL1 alarm name of a spatial filter alarm is SF-condtype, where condtype is the TL1 alarm name of the alarm from which the spatial filter alarm is derived.

(7)

This alarm can only be viewed using the EMS.

(8)

The format is rack number/shelf number/slot number/equipment number. The equipment number is an identifier of the NE of the voice package server unit.

Table TAP 2104-3: SHub alarm definitions for the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

Alarm type = LANX (51); Index1 = not used, Index2 = not used 3

Eqp

Maj

Y

db-restore

The SHub database restore has failed.

Check local flash. Check remote file system. Check availability of MIB database.

(1 of 6)

TAP 2104-28 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

5

Eqp

Maj

N

sntp-comm

SHub SNTP communication lost. The SNTP server does not respond to the requested messages from the SHub.

Check SNTP server.

Alarm type = ethLanx (52); Index1 = port identification of SHub Ethernet port, Index2 = see specific alarm number 1

Com

Crit

Y

eth-link-down

The Ethernet link is down.

Check the Ethernet link.

Index2 = not used. 3

Com

Min

Y

mac-conflict

Duplicate MAC address from Ethernet port of LAN switch. Index1 = port with the later coming MAC address that causes conflict.

No special repair action required. The conflict MAC address can be manually prohibited or permitted if needed.

Index2 = VLAN ID of domain on which the conflict happened. 10

Com

Min

N

oper-speed-mismatch

There is mismatch in the administrative speed and the operational speed Index 1 = Logical Port Number Index 2 = not used

Check the configuration mode of the port and change the administrative speed based on the port capability, SFP/XFP/RJ45 interfaces used, so the operational speed matches the administrative speed.

Alarm type = OSPF (69); Index1 = VRF-ID (VRF unique ID), Index2 = see specific alarm number 1

Com

Min

N

ospf-itf-err

Received a packet with:

• • • • • •

OSPF version mismatch area mismatch (area ID or subnet ID not matching) netmask mismatch hello interval mismatch dead interval mismatch options mismatch

Check the configuration on the OSPF and OSPF interface. Check the configuration on the IP interface. Check the OSPF hello packets received on the OSPF interface.

Index2 = interface index 2

Com

Min

N

ospf-auth-err

Received a packet with:

• •

authentication type mismatch authentication failure

Check the authentication type and password configured on the OSPF area and the OSPF interface. Check the authentication time range.

Index2 = interface index 3

Com

Crit

Y

ospf-rx-bad-err

Received a packet that cannot be parsed.

Check the connection between the RIP interface and the cable.

Index2 = interface index (2 of 6)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-29 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

5

Com

Maj

N

ospf-lsdb-oflow

The number of external LSAs has reached the external LSA overflow limit.

Remove some external routes in the OSPF domain.

Index2 = LSDB limit CLI: percentage used

Only input major external network routes.

6

7

Com

Com

Min

Min

Y

Y

ospf-nhbr-statchg

ospf-itf-statchg

Configure the OSPF area as a stub area if possible.

An OSPF neighbor connection is newly established or dismantled.

Check the OSPF neighbor table.

Index2 = interface index (interface on which the neighbor was learned)

•

The OSPF interface status has changed (the DR or BDR may have been changed according to this OSPF interface).

No special repair action required. Check and modify the OSPF interface parameters if desired to change the OSPF interface status.

•

If the neighbor is established correctly, the situation is normal. If the neighbor is down unexpectedly, check the OSPF process status or the interface-related parameters.

Index2 = interface index (interface on which the neighbor was learned) 8

9

Com

Com

Maj

Crit

N

Y

ospf-ext-lsa-threshold

ospf-instance-down

The number of external LSAs has reached 90% of the upper threshold limit.

Check the OSPF route redistribution configuration on the system.

The OSPF instance is down.

Restart the OSPF instance. Do not wait for the time-out period to end.

Check the layer 3 configuration on the AS border router, including the route aggregation configuration.

Check the network layer 3 configuration and the OSPF routing protocol configuration. Check the numbers of the routes configured on all instances for the system and for all other routers within the AS. Check the OSPF route redistribution configuration on the system. Alarm type = RIP (70); Index1 = VRF ID (VRF unique ID), Index2 = interface index 1

Com

Min

N

rip-config-err

Received a packet with:

• •

RIP version mismatch netmask mismatch

Check the configuration on the RIP send and receive version. Check the configuration on the IP interface. Check the RIP request and update packets received on the interface.

2

Com

Min

N

rip-auth-fail

Received a packet with:

• • 3

Com

Min

N

rip-rcv-bad-pkt

authentication type mismatch authentication failure

Received a packet that cannot be parsed

Check the authentication type and password configuration on the RIP interface. Check the authentication time range. Check the connection between the RIP interface and the cable.

(3 of 6)

TAP 2104-30 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

4

Com

Maj

N

rip-table-threshold

The number of RIP routes has reached 90% of the upper threshold limit.

Check the network layer 3 configuration and RIP routing protocol configuration (split horizon, poison reverse). Check the number of routes configured on the instance for the system and for all other routers within the AS. Check the RIP route redistribution configuration on the system.

5

Com

Crit

Y

rip-instance-down

The RIP instance is down.

Restart the RIP instance. Do not wait for the RIP restart after the time-out. Check the network layer 3 configuration and the RIP routing protocol configuration (split horizon, poison reverse). Check the numbers of the routes configured on all instances for the system and for all other routers within the AS. Check the RIP route redistribution configuration on the system.

Alarm type = Forwarding (71); Index1 = VRF-ID (VRF unique ID), Index2 = not used 1

Com

Maj

N

arp-table-full

The number of ARP entries has reached 90% of the upper threshold limit.

Check the network layer 3 configuration. Check the numbers of the routes configured on the system and on all other routers within the AS and the instance. Check the route aggregation configuration on the system and on all other routers in the AS and the instance. Reduce the number of enabled routing protocols in the instance. Check the route maps configuration in other routers on the AS and the instance. Check and reduce the number of hosts directly attached to local subnets on the instance.

2

Com

Maj

Y

route-tbl-overflow

The number of routes in the routing table of this VRF has reached 90% of the upper threshold limit.

Check the number of routes in the routing table and reduce as needed.

Alarm type = LANXuplinkgroup (75); Index1 = see specific alarm, Index2 = not used 1

Eqp

Maj

N

uplink-down

The SHub uplink group is down.

Check the SHub uplink group.

Index1 = uplink group number (4 of 6)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-31 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

2

Eqp

Crit

Y

pccp-down

All the ports of the PCCP group are down.

Check the operational status of the ports in the SHub PCCP group (at least one port in the PCCP group should be up).

Index1 = PCCP group number Alarm type = Global OSPF Routing (122); Index1 = not used, Index2 = not used 1

Com

Maj

N

global-ospf-route

The number of OSPF routes has reached 90% of the upper threshold limit.

Check the layer 3 configuration on the AS border router, including the route aggregation configuration. Check the network layer 3 configuration and the OSPF routing protocol configuration (route aggregation). Check the numbers of the routes configured on all instances for the system and for all other routers within the AS. Check the route redistribution configuration on the system. Check the route aggregation configuration on the system.

2

Com

Maj

N

global-ospf-lsa-tbl

The number of OSPF LSAs has reached 90% of the upper threshold limit.

Check the route redistribution (from other routing protocol) configuration. Check the layer 3 configuration on the AS border router, including the route aggregation configuration. Check the network layer 3 configuration and the OSPF routing protocol configuration (route aggregation). Check the numbers of the routes configured on all instances for the system and for all other routers within the AS. Create more OSPF areas.

3

Com

Maj

N

global-ospf-retrms-tbl

The number of OSPF retransmission entries has reached 90% of the upper threshold limit.

Check for a problem in the neighboring OSPF routers. Check for a link overload that causes excessive packet loss, including loss of multiple OSPF packets.

4

Com

Maj

N

global-ospf-lsaovflw

The number of selfgenerated LSAs, comprising the VRF, has reached 90% of the upper threshold limit.

Check the number of redistributed routes to the OSPF and reduce as needed.

5

Com

Maj

N

global-ospf-topology

The size of the area topology comprising the VRF has reached 90% of the upper threshold limit.

Check the area topology and reduce the number of interfaces in that area as needed. Reduce the neighbor.

Alarm type = Global RIP Routing (124); Index1 = not used, Index2 = not used (5 of 6)

TAP 2104-32 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TAP 2104 — Fault isolation and troubleshooting

No.

Class

Sev.

SA

CLI Alarm

Description

Troubleshooting recommendations

1

Com

Maj

N

global-rip-route-tbl

The number of RIP routes has reached 90% of the upper threshold limit.

Check the network layer 3 configuration and the RIP routing protocol configuration (split horizon, poison reverse). Check the numbers of the routes configured on all instances for the system and for all other routers within the AS. Check the RIP route redistribution configuration on the system.

Alarm type = Global Forwarding (125); Index1 = not used, Index2 = not used 1

Com

Maj

N

global-fwd-arp-tbl

The number of ARP entries has reached 90% of the upper threshold limit.

Check the network layer 3 configuration. Check the numbers of the routes configured on all instances for the system and for all the other routers within the AS. Check the route aggregation configuration on all instances for the system and for all the other routers in the AS. Reduce the number of enabled routing protocols on all instances. Check the route maps configuration on the other routers in the AS. Check and reduce the number of hosts directly attached to all local subnets.

2

Com

Maj

N

global-fwd-route-tbl

The number of forwarding entries has reached 90% of the upper threshold limit.

Check the network layer 3 configuration and the numbers of the routes configured on all instances within the AS. Check the route aggregation configuration on the system and on all the other routers in the AS. Check the route maps configuration on the other routers in the AS. Reduce the number of enabled routing protocols on all instances.

(6 of 6)

3

STOP. This procedure is complete.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TAP 2104-33 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TAP 2104 — Fault isolation and troubleshooting

TAP 2104-34 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Training (TNG)

TNG 1104 — DHCP relay agent configuration TNG 1105 — Overall software packages TNG 1107 — xDSL parameters TNG 1108 — SHDSL parameters TNG 1115 — Slot numbering schemes TNG 1116 — Link Related Ethernet OAM (EFM OAM) TNG 1119 — vMAC TNG 1120 — VLAN translation TNG 1121 — xDSL bonding TNG 2100 — Service installation TNG 2101 — QoS configuration TNG 2102 — IGMP and multicast configuration TNG 2106 — Specifying 7330 ISAM FTTN expansion units using the CLI TNG 2109 — Performance management counters TNG 2110 — Configuration examples TNG 2112 — 7330 ISAM FTTN configuration for subtending

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 2117 — Enhanced iBridge TNG 2118 — PPPoE with MAC address concentration

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1104 — DHCP relay agent configuration General Description The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable network addresses and additional configuration options. DHCP consists of two components: a protocol for delivering host-specific configuration parameters from a DHCP server to a host and a mechanism for allocation of network addresses to hosts. DHCP is built on a client-server model, where designated DHCP server hosts allocate network addresses and deliver configuration parameters to dynamically configured hosts. Figure TNG 1104-1 shows a typical DHCP configuration. Figure TNG 1104-1: Typical DHCP Configuration

ISAM

Internet DHCP server

Upstream packet Downstream 17704

ISAM can be a 7302 ISAM, a 7330 ISAM FTTN, a stand-alone 7356 ISAM FTTB or a 7360 ISAM FX

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1104-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1104 — DHCP relay agent configuration

IP Address Allocation Mechanisms DHCP supports three mechanisms for IP address allocation:

• • •

automatic allocation DHCP assigns a permanent IP address to a client. dynamic allocation DHCP assigns an IP address to a client for a limited period of time (or until the client explicitly relinquishes the address). manual allocation A client's IP address is assigned by the network administrator, and DHCP is used simply to convey the assigned address to the client.

A particular network will use one or more of these mechanisms, depending on the policies of the network administrator.

DHCP Option 82 An option called Option 82 is inserted by the DHCP relay agent running on the system when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing Option 82 may use the information to implement an IP address or other parameter assignment policies. The DHCP server echoes the option back to the relay agent in server-to-client replies. The system strips the option before forwarding the reply to the client. Option 82 is organized as a single DHCP option that contains one or more suboptions that convey information known by the relay agent.

DHCP Relay Parameters Table TNG 1104-1 describes the parameters used to configure DCHP. Table TNG 1104-1: DHCP parameter descriptions Parameter

Description

giaddress

Dy default the gi-address used in the relayed DHCP packet is the primary address on that IP interface. It is possible to specify another IP address, but this other IP address must be one of the secondary IP address(es) configured on that IP interface



The source IP address for sending DHCP relay packets must be one of the secondary IP address(es) configured on that IP interface (when the primary address is not wanted as default)

Conditions and Restrictions The following conditions and restrictions apply:

• •

TNG 1104-2

Before you can enable the DHCP relay agent, you need to configure at least one DHCP server on the VRF IP interface. A maximum of eight DHCP servers can be configured on a VRF.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1105 — Overall software packages Introduction This TNG provides more information about:

• • • • •

Downloading a New OSWP Re-downloading a new OSWP Aborting an OSWP Activating a Non-active OSWP Commiting an OSWP

Downloading a New OSWP The following prerequisites must be fulfilled before a new OSWP can be downloaded:

• • •

The system must have only one Enabled/Active/Committed OSWP. The management channel between the system and the manager has been established. The system is not involved in another OSWP download process.

The manager requests the system to download a new OSWP. He specifies:

• • •

The path name of the overall descriptor files The TFTP servers where the overall descriptor files can be found. The set of overall descriptor files he wants to have available on the system before activating the new OSWP.

The system downloads the overall descriptor files and stores it persistently. The system downloads the software files that are specified in the downloaded overall descriptor files on condition that sufficient resources are available for their persistent storage. The manager has the possibility to monitor the progress of the download process with granularity.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1105-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1105 — Overall software packages

The download process can be implicitly or explicitly interrupted:

•

•

The implicit interruption can occur due to the following: • the unavailability of sufficient resources to store SWP files. • the system is not able to download or interpret the overall descriptor file. • the system is not able to download a selected SWP descriptor file. The explicit interruption can occur when the manager requests the system to abort the ongoing download process.

In case there are no exceptions, finally the system will have two OSWPs:

• •

the Enabled/Active/Committed OSWP. the new downloaded OSWP. The status of the new OSWP is Enabled/NotActive/UnCommitted.

Re-downloading a new OSWP The operator can actualize the board types that are supported by the active OSWP on a given system by re-downloading the actual active OSWP. The command is completely identical to the command for a regular download of a new OSWP. An actualization is needed if the operator wishes to introduce a new board type that is supported by the actual active OSWP, but that was not planned or detected during the first download of the actual active OSWP. As a result of this the software files of the new board type have not been downloaded and are not stored on the CF. This can be rectified by a re-download. Prior to the re-download, the operator must physically plug the new board type in a system or (as a remote alternative) simply plan the new board type. There is an interesting variant of the re-download OSWP case where the download of the new OSWP happens during installation from an external file server that is local to the installation site. At a later time when the operator wishes to re-download the actual active OSWP the external file server is a centralized device with a different IP address compared to the local device. In this case the following procedure must be used:

TNG 1105-2

1

When the IP address of the external file server changes, create a new OSWP descriptor file with a different name than the currently active OSWP descriptor file. The best choice is a different variant name. For example: if the name of the current active OSWP descriptor file is L6GPAA43.085, then the name of the new OSWP descriptor file becomes L6GPAB43.085

2

The content of the new OSWP file is the same except for the IP address and/or the path towards the SWPs.

3

The new OSWP needs to be downloaded in the empty (i.e. NotActive) OSWP position via the regular OSWP download procedure.

4

The operator can either activate and commit the new OSWP or perform an abort after download of all missing SW files. The abort of the newly downloaded OSWP (i.e.without activation) is generally the best option.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1105 — Overall software packages

Aborting an OSWP The manager can abort an OSWP when the system has 2 OSWPs. The status of the first OSWP is Enabled/Active/Committed while the second one will be in one of the following three states:

• • •

Enabled/NotActive/UnCommitted Downloading/NotActive/UnCommitted Disabled/NotActive/UnCommitted.

The management channel between the system and the manager is established and the system is not involved in any other SW download process. The manager requests the system to remove the NotActive/UnCommitted OSWP. The system removes all the persistent stored files and all the databases not related to the Enabled/Active/Committed OSWP (so, also the database that could have recently be downloaded and linked to the aborted OSWP). The status of the OSWP to be removed will be Aborting/NotActive/UnCommitted during the complete remove operation. After the abort is successful the system will have only one OSWP. The status of this OSWP will be Enabled/Active/Committed. Only files and databases related to this OSWP are stored persistently in the system.

Activating a Non-active OSWP To activate a not-active OSWP, the system must have two OSWPs: The first OSWP has the status Enabled/Active, while the second OSWP has the status Enabled/NotActive. The management channel between the system and the manager is established and the system is not involved in another SW download process. The manager requests the system to activate the Enabled/NotActive OSWP: 1

The system selects the database that is compatible with and linked to the Enabled/NotActive OSWP among the available databases.

2

The system starts the activation procedure of the NotActive OSWP.

3

When the activation of the NotActive OSWP is successful, the system has two OSWPs.

The previously NotActive OSWP is now active together with the selected compatible database. The previously Active OSWP is still available but its status is now Enabled/NotActive.

Commiting an OSWP To commit an OSWP, the system has two OSWPs. The first OSWP has the status Enabled/Active/Uncommitted, while the status of the second OSWP is Enabled/NotActive/Committed.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1105-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1105 — Overall software packages

The manager requests the system to commit the active OSWP: 1

The system removes all the persistent stored files and all the databases that do not belong to the Enabled/Active OSWP.

Note — The status of the OSWP to be committed will be Enabled/Active/Committing during the entire commit operation.

2

TNG 1105-4

After commit is successful, the system will have only one OSWP. The status of this OSWP is Enabled/Active/Committed. Only files related to this OSWP are stored persistently in the system.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters Introduction From management perspective, an xDSL interface consists of one xDSL Line Interface and one xDSL Channel Interface. Although the standard allows transporting multiple channels over the same line (up to two for ADSL1/VDSLx, up to four for ADSL2x), only one channel will be supported for each line. xDSL interfaces are grouped per board. Most configuration parameters are configured at line interface level, although some parameters may be configured at board level. Parameters configured at board level are applied to all interfaces of that board, excluding interfaces having the same parameter configured at line level. xDSL interface configuration has always precedence over board level configuration. This TNG describes the commands and parameters associated with configuring and monitoring xDSL lines:

• • • • • •

xDSL xDSL xDSL xDSL xDSL xDSL

service profile configuration parameters spectrum profile parameters DPBO profile configuration parameters line overrule record configuration parameters line status parameters line operational data retrieval

xDSL interfaces are configured by assigning an xDSL spectrum configuration profile and an xDSL service configuration profile to the Line Interface. Optionally, a Downstream Power Back-Off (DPBO) configuration profile can be assigned to a line or to a board. Optionally, some service- and/or spectrum profile parameters can be overruled via an overrule-record assigned to a line.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

In addition, line status parameters can be retrieved using xDSL line diagnostic tests.

•

•

The xDSL service configuration profile groups all the parameters on a service level (data rates, delay, …). These parameters are mainly related to the configuration of the xDSL channel interface. The service parameters are common for all the DSL flavours. In case a parameter is not supported for a specific DSL flavour, this parameter is ignored for that flavour. The xDSL spectrum configuration profile groups all the parameters on a physical level. These parameters are mainly related to the environmental conditions of the line (spectrum management). The spectrum configuration profile contains parameters which have a common value for all DSL flavours (Common) and parameters which have a specific value depending on the used DSL flavour (ADSL1/2, READSL2, ADSL2Plus, VDSL(*), VDSL2(*).

Note — (*): The VDSL parameter set contains the parameters common to VDSL1 and VDSL2 as well as the parameters specific to VDSL1. The VDSL2 parameter set is an extension of the VDSL parameters that contains the parameters specific to the VDSL2 operating modes.

•

•

The actual selected operating mode determines which set of DSL specific parameters is used. In case a common parameter is not supported for a specific DSL flavour, this parameter is ignored for that flavour. The xDSL DPBO configuration profile groups all the parameters linked to the calculation of the DPBO Power Spectral Density (PSD) shape. These parameters are supported for all the DSL flavours, except VDSL1. In case a parameter is not supported for a specific DSL flavour, this parameter is ignored. The Downstream (DS) PSD shape calculated from the DPBO parameters takes precedence over the flavour-specific DS custom PSD shape configured via the xDSL spectrum configuration profile. The DPBO Profile is not a mandatory parameter for line configuration nor for board configuration. The DPBO Profile can be configured at the board level and at line level: • When configured at board level, it is applied on all the lines of that board. • If DPBO is configured at the same time at board and line level, only the line level DPBO configuration is taken into account. The xDSL overrule data groups all the parameters which will overrule the parameters configured in the service and/or spectrum profile attached to that line.

Failure correlation / priorities When conditions are met for more than one failure as defined in Alcatel-Lucent's VDSLx implementation, only one failure will be reported, based on following hierarchy (from highest to lowest priority):

TNG 1107-2

1

All activation failures

2

Far-end Loss Of Power (LPR)

3

Near-end Loss Of Signal (LOS)

4

Near-end Loss Of Frame (LOF)

5

Near-end Excessive Severe Errors (ESE)

6

Near-end Loss of Cell Delineation (LCD)/No Cell Delineation (NCD) Loss of Packet Delineation (LPD)/No Packet Delineation (NPD)

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

7

Near-end Loss Of Margin (LOM)

8

Far-end LOS

9

Far-end LOF

10 Far-end ESE 11 Far-end LCD/NCD LPD/NPD 12 Far-end LOM When failure declaration conditions are met for a certain failure while a lower-priority failure is active, the lower-priority failure will be suppressed and the higher-priority failure will be reported.

xDSL service profile configuration parameters This section describes all the parameters that can be configured in the xDSL service configuration profile. All the parameters of the xDSL service configuration profile are stored persistently. Table TNG 1107-1 gives an overview of the modem configuration parameters of the xDSL service configuration profile and indicates what parameters are applicable for each xDSL flavour. Parameters that are not applicable for a certain mode are ignored in case that mode is used on the line. Table TNG 1107-1: xDSL service profile configuration parameters

ADSL1/ ADSL2

READLS2

ADSL2+

VDSL

VDSL2

Parameter

X

X

X

X

X

X

X

X

X

X

Maximum interleaving delay US/DS

X

X

X

X

X

Minimum impulse noise protection US/DS

X

X

X

X

X

Low power bit rate configuration DS

X(1)

X

X

NA

NA

Erasure detection US/DS

NA

NA

NA

NA

X

SRA maximum delay variation US/DS

NA

NA

NA

NA

X

Common parameters Rate adaptive mode US/DS Channel specific parameters L0 bit rate configuration

• • •

Minimum bit rate US/DS Planned bit rate US/DS Maximum bit rate US/DS

Note (1)

These parameters are ignored for ADSL1 mode of operation.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Rate adaptive mode The DS and US Rate Adaptive (RA) modes are configurable via the xDSL Service Configuration Profile. This parameter specifies the mode of operation of the XTU in the transmit direction. The following RA Modes can be configured in the profile:

•

•

•

TNG 1107-4

RA Mode 1 (MANUAL) The data rate is selected manually: • At startup: The Planned Data Rate parameter specifies the data rate the XTU transmitter operates at for the corresponding bearer channels, with a noise margin which is at least as large as the specified Target Noise Margin, relative to a BER of 10-7, or better. If the XTU fails to achieve the Minimum Data Rate, the XTU fails to initialize. Although the XTU and the line might be able to support a higher data rate, the XTU will not transmit a higher data rate than what is requested. • At showtime: The XTU transmitter maintains the specified Planned Data Rate. RA Mode 2 (AT_INIT) The data rate is automatically selected at startup only and does not change after that: • At startup: The Minimum Data Rate parameter specifies the minimum data rate the XTU transmitter operates at for the corresponding bearer channel, with a noise margin which is at least as large as the specified Target Noise Margin, relative to a BER of 10-7, or better. If the XTU fails to achieve the Minimum Data Rate, the XTU fails to initialize. As long as the data rate is below the Maximum Data Rate, data rate increase takes priority over transmit power reduction. The XTU will not set up a data rate that is higher than the specified Maximum Data Rate. • At showtime: During showtime, no data rate adaptation is allowed. The downstream data rate, which has been settled during initialization, is maintained. RA Mode 3 (DYNAMIC). The data rate is automatically selected at startup and is continuously adapted during operation (at showtime). • At startup: In Mode 3, the XTU operates as in Mode 2. • At showtime:

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

During showtime, rate adaptation is allowed, assuring that the Minimum Data Rate remains available at the required BER of 10-7, or better. The data rate can vary between the Minimum Data Rate and the Maximum Data Rate. Rate adaptation is performed when the conditions specified for Upshift or Downshift Rate Adaptation are satisfied.

Note — RA Mode 2 will be used as a fallback for RA Mode 3 in the exceptional cases specified below:

•

•

In case a profile with RA Mode 3 gets assigned to a line of a board supporting SRA, but this mode cannot be used because the XTU-R does NOT support it, then the XTU-C uses RA Mode 2 as a fallback. It is the responsibility of the modem subsystem to use RA Mode 2 in case the XTU-R does not support RA Mode 3 In case a profile with RA Mode 3 gets assigned to a line of a board NOT supporting SRA, then RA Mode 2 shall be used as a fallback. In this case it is the responsibility of the xDSL Manager to configure RA Mode 2 towards the modem (overrule of profile parameter).

Profile name and scope The name and the scope of the xDSL service configuration profile can be configured. The scope of an xDSL Service Configuration Profile can be local or network wide. For a particular scope, the name of an xDSL Service Configuration Profile must be unique within the existing set of xDSL Service Configuration Profiles, otherwise the profile creation is rejected.

• •

Name: string of up to 32 characters Scope: LocalScope or NetworkScope

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

L0 bit rate configuration The L0 bit rates configured on the line depend both on the native/bonding configuration and the rate adaptation mode setting (see “Rate adaptive mode”):

•

•

xDSL channel configured in native mode: In this case, the L0 Planned, Minimum and Maximum bit rate configured in the xDSL service configuration profile are directly used to configure the modem and determine if the xDSL bit rate threshold alarms have to be raised. • RA Mode 1: Only the Planned Bit rate is used. Towards the modem and higher layer (f.i. ATM), the minimum and maximum bit rate are set equal to this configured Planned Bit rate, independent from the setting in the profile. • RA Mode 2: The Minimum and Maximum Bit rate are used by the modem during initialization. The Planned Bit rate is used only to activate the bit rate threshold alarm in case the actual bit rate achieved in showtime is smaller than this Planned Bit rate. • RA Mode 3: The Minimum and Maximum Bit rate are used by the modem during initialization AND during operation. The Planned Bit rate is used only to activate the bit rate threshold alarm in case the actual bit rate in showtime is smaller than this Planned Bit rate. xDSL channel configured in bonding mode: When an xDSL channel is configured in bonding mode, then the xDSL bit rate threshold alarms will never be raised, because the bit rate threshold is checked at bonding group level. In case the bonding group bit rates are set to 0, then the bonding group bit rates are calculated using the bit rates of the xDSL service configuration profiles: • Minimum bit rate of group = the sum of the minimum bit rates of the xDSL service configuration profile of all the lines in the group • Planned bit rate of group = the sum of the planned bit rates of the xDSL service configuration profile of all the lines in the group • Maximum bit rate of group = the sum of the maximum bit rates of the xDSL service configuration profile of all the lines in the group The bit rate configuration of the xDSL modem for each line is then as follows: • RA Mode 1: The modem will be forced to use the Planned bit rate configured in the xDSL service profile. • RA Mode 2 or 3: The modem bit rate will be derived from the bonding group bit rates, but will be higher or equal than the Minimum bit rate configured in the xDSL service profile. The Planned bit rate and the Maximum bit rate configured in the XDSL service profile will be ignored.

Note — For more information on xDSL bonding, see TNG 1121.

TNG 1107-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

The US and DS L0 Minimum, Planned and Maximum Bit rate are configurable via the xDSL Service Configuration Profile. The profile creation shall be rejected in case RA Mode 2 (AT_INIT) or RA Mode 3 (DYNAMIC) is selected and the following is not respected: Minimum Bit rate ≤Planned Bit rate ≤Maximum Bit rate. For native mode of operation, the Planned, Minimum and Maximum bit rates are defined as follows:

•

•

•

Planned Bit rate: In RA Mode 1, the Planned Bit rate defines the bit rate which shall be set up (not changeable during showtime). Range: 0 to 262143 kbit/s, in steps of 1 kbit/s Minimum Bit rate: In RA Mode 2 or RA Mode 3, the Minimum Bit rate defines the minimum requested bit rate which shall be set up and which shall be maintained during showtime. This parameter has no meaning in RA Mode 1. Range: 0 to 262143 kbit/s, in steps of 1 kbit/s Maximum Bit rate: In RA Mode 2 or RA Mode 3, the Maximum Bit rate defines the maximum allowed bit rate which shall be set up and which shall be maintained during showtime. This parameter has no meaning in RA Mode 1. Range: 0 to 262143 kbit/s, in steps of 1 kbit/s

Rounding of bit rates Although the bit rates can be configured in steps of 1 kbit/s, they will eventually be mapped by the modem to a value that depends on the granularity supported by the corresponding xDSL operational mode:

• • •

For VDSL a granularity of 64 kbit/s applies. For ADSL1x a granularity of 32 kbit/s applies For ADSL2x, the granularity has no fixed value because of the complex framing format. In general, the rounding for ADSL2x shall be limited to a maximum of 8 kbit/s.

In case a bit rate below 32 kbit/s is configured, this bit rate may be rounded up to 32 kbit/s for ADSLx and 64 kbit/s for VDSL. The actual bit rate shall be selected after applying the following rules for rounding:

• •

RA Mode = 1 (MANUAL) Planned Bit Rate: round up RA Mode = 2 (AT_INIT) or RA Mode = 3 (DYNAMIC) • Minimum Bit Rate: round up • Maximum Bit Rate: round down

In the exceptional case that after rounding the minimum bit rate becomes higher than the maximum bit rate, the highest value of both shall be used (i.e. the minimum value rounded up).

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Low power bit rate configuration This parameter is only applicable to ADSLx. This parameter is ignored on boards that do not support L2 (refer to the Product Information manual). The DS L2 Minimum Bit rate is configurable via the xDSL Service Configuration Profile. Range: 0 to 262143 kbit/s, in steps of 1 kbit/s

Maximum interleaving delay The DS and US Maximum Interleaving Delay are configurable via the xDSL Service Configuration Profile. This parameter specifies the maximum one-way interleaving delay introduced by interleaving and deinterleaving function in the corresponding direction. The XTU shall choose the value of its coding parameters such that the actual one-way interleaving delay is less or equal than the configured Maximum Interleaving Delay. The delay is coded in ms, with the value 1 as special value: The fast latency path is used if defined by the applicable standard, otherwise a pseudo-fast latency is used (Sp=1 and Dp=1). Range DS/US: 1 to 63 ms.

Note — Exception: In the following cases, the modem is allowed to operate in pseudo fast mode (Sp=1 and D p=1) although the standard supports a fast latency path:

• •

in order to be able to achieve high bit rates requiring Sp=1/2 to avoid that the upstream and downstream direction use a different latency path.

Minimum impulse noise protection The decoupling between the configuration of the Maximum Interleaving Delay and the configuration of the Minimum Impulse Noise Protection (INP) allows the operator to configure a rather low delay combined with a high impulse noise protection, at the sacrifice of bit rate (because of low coding efficiency). The DS and US Minimum INP are configurable via the xDSL Service Configuration Profile. This parameter specifies the minimum impulse noise protection for the bearer channel. Range DS/US: 0 to 16 symbols, in steps of 0.1 symbols.

Erasure detection This parameter applies only to VDSL2 operating modes.

TNG 1107-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

The DS and US Erasure Detection is configurable via the xDSL Service Configuration Profile. This parameter specifies for the corresponding direction whether the erasure detection mechanism is allowed to be taken into account in order to reach the Minimum INP in case of VDSL2 operating modes. Values: 1 = MinInp must be reached even without erasure detection 0 = MinInp must be reached with or without erasure detection

• •

SRA maximum delay variation This parameter applies only to VDSL2 operating modes. The DS and US SRA Maximum Delay Variation is configurable via the xDSL Service Configuration Profile. This parameter specifies for the corresponding direction the maximum delay variation allowed in downstream direction during SRA in VDSL2 mode. Range: 1..254, 255 (ms in steps of 0.1ms).The special value 255 indicates that no delay variation bound is imposed.

xDSL spectrum profile parameters This section describes all the parameters that can be configured in the xDSL spectrum configuration profile. All the parameters of the xDSL spectrum configuration profile are stored persistently. Table TNG 1107-2 gives an overview of the modem configuration parameters of the xDSL spectrum configuration profile and indicates what parameters are applicable for each xDSL flavour. Parameters that are not applicable for a certain mode are ignored in case that mode is used on the line. Table TNG 1107-2: xDSL spectrum profile configuration parameters

ADSL1/ ADSL2

READLS2

ADSL2+

VDSL1

VDSL2

Parameter

Operating modes

X

X

X

X

X

Noise margin parameters

X

X

X

X

X

Carrier masking

X

X

X

NA

NA

RFI bands

NA

NA

X

X

X

Common parameters

• • •

Minimum noise margin US/DS Target noise margin US/DS Maximum noise margin US/DS

(1 of 3)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

ADSL1/ ADSL2

READLS2

ADSL2+

VDSL1

VDSL2

Parameter

X(1)

X

X

NA

NA

X(1)

X

X

NA

X

X

X

X

NA

NA

Modem features

X

X

X

X

X

VDSL band plan

NA

NA

NA

X

X

Optional band usage

NA

NA

NA

X

X

Optional band start frequency

NA

NA

NA

NA

X

Optional band end frequency

NA

NA

NA

X

X

ADSL band usage

NA

NA

NA

X

X

ADSL band end frequency

NA

NA

NA

X

X

Maximum nominal Power Spectral Density US/DS

X(1)

X

X

X

X

Maximum nominal aggregate transmit power US/DS

X(1)

X

X

X

X

NA

NA

X

X

X

X

NA

X

X

X

NA

NA

X

X

X

NA

NA

NA

NA

X

X(1)

X

X

X

X

NA

NA

NA

NA

X

Maximum aggregate receive power US

X(1)

X

X

NA

NA

Receive PSD Shape Upstream US

NA

NA

NA

X

X

Customized RX PSD Shape Upstream US

NA

NA

NA

X

X

G.Hs Tones Tx Power Control

NA

NA

NA

X

X

Per tone set G.Hs Tones Tx Power Control (A43/B43/A43c/V43)

NA

NA

NA

X

X

Per tone set G.Hs Tones Tx Power Level A43/B43/A43c/V43

NA

NA

NA

X

X

Maximum number of bands

NA

NA

NA

X

X

Maximum frequency

NA

NA

NA

X

X

Power management

• • • •

L0 time L2 time L2Atpr time L2AtprT time

Dynamic rate adaptation

• • • •

RAU noise margin US/DS RAU time US/DS RAD noise margin US/DS RAD time US/DS

Artificial noise PSD DS Flavour specific parameters

Selectable PSD shape

• •

PSD shape DS PSD shape US

Custom DS/US PSD shape

• •

Custom PSD shape DS Custom PSD shape US

Power backoff mode and policing

• •

Power backoff mode US UPBO policing mode

(2 of 3)

TNG 1107-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

ADSL1/ ADSL2

READLS2

ADSL2+

VDSL1

VDSL2

Parameter

A and B Parameters for US PBO PSD

NA

NA

NA

X

X

US PBO electrical length

NA

NA

NA

NA

X

Virtual Noise PSD Shape US/DS

NA

NA

NA

NA

X

Virtual Noise SNRM mode US/DS

NA

NA

NA

NA

X

FEXT Parameters for US PBO PSD

NA

NA

NA

NA

X

(3 of 3) Note (1)

These parameters are ignored for ADSL1 mode of operation.

Operating modes The xDSL Spectrum Configuration Profile defines a set of parameters that are common for all xDSL flavours, but also defines a number of parameters that are specific for one or more xDSL flavours (for example VDSL, ADSL/ADSL2, ADSL2+, …). The Operating Modes bitmap of the xDSL Spectrum Configuration Profile specifies for what operating modes this profile can be used:

• • •

In case one of the xDSL operating modes is enabled, the corresponding xDSL specific configuration parameters shall be configured with valid values. It is possible to use the same xDSL spectrum profile for multiple xDSL flavours (e.g VDSL and ADSL). In case such a profile is assigned to a line, all parameters specific to non-supported modes are ignored. In case none of the operating modes of a certain xDSL flavour are enabled, then the corresponding xDSL specific configuration data stored within that profile has no meaning and is ignored.

The following Operating Modes can each be individually enabled or disabled:

•

ADSL1: • ANSI T1.413 Issue 2: ANSI standard; operation over POTS non-overlapped spectrum • DTS/TM-06006: ETSI standard; operation over ISDN non-overlapped spectrum • G.992.1 Annex A: operation over POTS non-overlapped spectrum; also known as G.dmt; • G.992.1 Annex B: operation over ISDN non-overlapped spectrum • G.992.2 Annex A: operation over POTS non-overlapped spectrum; also known as G.lite

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

•

•

•

•

•

ADSL2: • G.992.3 Annex A: operation over POTS non-overlapped spectrum • G.992.3 Annex B: operation over ISDN non-overlapped spectrum • G.992.3 Annex M: extended upstream operation (up to 3 Mb/s) over POTS non-overlapped • spectrum • G.992.3 Annex J: all Digital Mode operation with non-overlapped spectrum and extended upstream band (spectrally compatible with ADSLx over ISDN) ADSL2Plus: • G.992.5 Annex A: operation over POTS non-overlapped spectrum • G.992.5 Annex B: operation over ISDN non-overlapped spectrum • G.992.5 Annex M: extended upstream operation (up to 3 Mb/s) over POTS non-overlapped spectrum • G.992.5 Annex J: all Digital Mode operation with non-overlapped spectrum and extended upstream band (spectrally compatible with ADSLx over ISDN) RE-ADSL2: • ITU-T G.992.3 Annex L, WIDE: operation over POTS non-overlapped spectrum, Range-Extended Mode 1 • ITU-T G.992.3 Annex L, NARROW: operation over POTS non-overlapped spectrum, Range-Extended Mode 2 VDSL1: • T1.424: ANSI standard • TS 101 270-1/2: ETSI standard • G.993.1: ITU-T standard • 802.3 clause 61: IEEE standard (10PASS-TS or Ethernet First Mile (EFM) VDSL) VDSL2: • G.993.2 profile 8A: VDSL2 profile 8A • G.993.2 profile 8B: VDSL2 profile 8B • G.993.2 profile 8C: VDSL2 profile 8C • G.993.2 profile 8D: VDSL2 profile 8D • G.993.2 profile 12A: VDSL2 profile 12A • G.993.2 profile 12B: VDSL2 profile 12B • G.993.2 profile 17A: VDSL2 profile 17A

Note — It is advised to have either all modes of a certain ADSL flavour enabled or have them all disabled, because this decreases the amount of profiles that has to be maintained by the operator. By enabling multiple xDSL flavours within a single profile, the amount of profiles that has to be maintained will even further decrease. Noise margin parameters Figure TNG 1107-1 gives an overview of the noise margin parameters, and the correlating actions at the modem.

TNG 1107-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters Figure TNG 1107-1: Noise margin parameters

Reduce Output Power at peer modem Maximum Noise Margin

Target Noise Margin

Increase Output Power at peer modem

Minimum Noise Margin 0 dB Margin

Modem restarts if persistent in this region

The DS and US Minimum, Target and Maximum Noise Margins are configurable via the xDSL Spectrum Configuration Profile. The profile creation is rejected in case the following is not respected: Minimum Noise Margin ≤Target Noise Margin ≤Maximum Noise Margin.

•

Target Noise Margin: The DS and US Target Noise Margin specify the noise margin a modem must achieve relative to a BER of 10-7 (as seen by the ATU with respect to its received signal) to successfully complete initialization. When the modem cannot initialize at this noise margin, it will fail. This parameter is not used at showtime in case of RAMode 1 (MANUAL) or RAMode 2 (AT_INIT). Range DS/US: 0 to 31 dB, in steps of 0.1 dB.

Note — Although ADSL2x allows a configurable BER of 10-7, 10-5 or 10-3, always a fixed BER of 10-7 will be used.

•

Minimum Noise Margin: The DS and US Minimum Noise Margin specify the minimum noise margin the XTU tolerates relative to a BER of 10-7. The Minimum Noise Margin is only used at showtime, independently of the rate adaptation mode. If the current noise margin falls below the Minimum Noise Margin, then the modem fails. Range DS/US: 0 to 31 dB, in steps of 0.1 dB.

Note — It is strongly recommended to specify the minimum noise margin several dB (for example, 3 dB) below the target noise margin, in order to allow for some fluctuations on the noise margin without generating an unstable xDSL system.

•

Maximum Noise Margin: The DS and US Maximum Noise Margin specify the maximum noise margin the XTU shall tolerate relative to a BER of 10-7. The Maximum Noise Margin is used both at startup and at showtime, independently of the rate adaptation mode. A special

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

value indicates that no Maximum Noise Margin limit is to be applied. In case of ANSI Operational Mode, the setting of this parameter is ignored (because it is not supported by the corresponding standard). At startup: When the noise margin is higher than the Maximum Noise Margin, then the XTU takes action to reduce the power to get the noise margin below this value. When the noise margin is lower than Maximum Noise Margin, then the XTU takes action to increase the power (if possible), to get its noise margin as close as possible to this value. At showtime: When the current noise margin gets above the Maximum Noise Margin, then the XTU attempts to reduce the far-end output power to get the noise margin below this limit. When the current noise margin gets below the Maximum Noise Margin, then the XTU attempts to increase the far-end output power to get the noise margin as close as possible to this value. Range DS/US: 0 to 51.1 dB, in steps of 0.1 dB All values strictly bigger than 31 are interpreted as meaning that no Maximum Noise Margin limit must be applied (infinity).

Note — For ADSL1/VDSL1 based standards, only values 0 to 31 with 1 dB granularity can be passed to the XTU-R for the DS direction. In that case, non-integer values are rounded to the nearest dB, while the special value 51.1 is translated to 31. Dependent on the type of CPE, value 31 will be interpreted as infinity or as a normal value 31. Carrier masking This parameter is only applicable for ADSLx. The US and DS carrier mask specifies an array of boolean values sc(I). Each entry sc(i) defines whether subcarrier index i is masked on this line in the corresponding direction, for i ranging from 0 to NSCds-1 for DS and from 0 to NSCus-1 for US. It is coded as 1 if masked and 0 if not masked. NSCds/us is the highest subcarrier that can be transmitted in the DS/US direction and depends on the actual operating mode as illustrated in Table TNG 1107-3. Table TNG 1107-3: NSC subcarrier values Operational mode

NSC DS

NSC US

ANSI T1.413

256

32

G.992.1 Annex A

256

32

G.992.1 Annex B

256

64

G.992.2 Annex A

128

32

G.992.3 Annex A

256

32

G.992.3 Annex B

256

64

G.992.3 Annex L (READSL2)

256

32

(1 of 2)

TNG 1107-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

Operational mode

NSC DS

NSC US

G.992.3 Annex M (Extended US ADSL2)

256

64

G.992.3 Annex J

256

64

G.992.5 Annex A (ADSL2+)

512

32

G.992.5 Annex B

512

64

G.992.5 Annex M (Extended US ADSL2)

512

64

G.992.5 Annex J

512

64

(2 of 2)

RFI bands The list of RFI Bands is configurable via the xDSL Spectrum Configuration Profile. Up to N RFI bands can be configured. For ADSL2+, the system supports at least 2 RFI bands within the ADSL2+ spectrum. For VDSLx, the system at least supports the standard ANSI and ETSI HAM bands defined in Table TNG 1107-4. In case more RFI bands are specified than the system can support, an activation failure (configuration error) is raised. N=16 For each RFI Band, the RFI type, egress control and the ingress level is specified. The ingress level and RFI type are specified for information of the xDSL modem subsystem such that it can be taken into account at initialization. Their usage for RFI canceling purposes is vendor discretionary.

• • • •

RF Band: [start frequency, stop frequency] frequency: 0 to 30000 kHz RFI Type: • HAM • AM Egress control: • Notched: PSD level is reduced below -80 dBm/Hz • No control: no notching required for that band Ingress level: • Low: ingress level can be neglected • Weak: expected ingress level is weak (at -30dBm for LT / -20dBm for NT) • Strong: expected ingress level is strong (at -10dBm for LT / 0dBm for NT) Table TNG 1107-4: International amateur radio bands (HAM bands) Band start ETSI/ITU/ANSI (in kHz)

Band stop ETSI/ITU (in kHz)

Band stop ANSI (in kHz)

1810

2000

2000

3500

3800

4000

7000

7100

7300

10100

10150

10150

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Band start ETSI/ITU/ANSI (in kHz)

Band stop ETSI/ITU (in kHz)

Band stop ANSI (in kHz)

14000(1)

14350(1)

14350(1)

18068(1)

18168(1)

18168(1)

21000(1)

21450(1)

21450(1)

24890(1)

24990(1)

24990(1)

28000(1)

29100(1)

29700(1)

(2 of 2) Note (1)

Frequency bands above 12 MHz are out of the VDSL1 modem frequency band.

Power management The L2 Low Power state does only apply to ADSLx. The parameters described in this chapter are ignored on boards that do not support L2.

•

•

Power Management Mode: The Power Management Mode is configurable via the xDSL Spectrum Configuration Profile. This parameter defines the line states the XTU-C or XTU-R may autonomously transition to on this line: • L2 (Low power state) allowed / not allowed • L3 (Idle state) allowed / not allowed The L2/L3 feature is not supported on all types of xDSL boards. In case L2/L3 is not supported, the L2/L3 Power Management mode is set fixed to not allowed towards the modem, independent of what is configured in the assigned profile. It is the responsibility of the xDSL Manager to force this parameter to not allowed in this case (overrule of profile parameter). Configuration of L2 Low Power State parameters: • The L0-TIME parameter defines the minimum time between an exit from the L2 state and the next entry into the L2 state. Range: 0 to 1800 s • The L2-TIME parameter defines the minimum time between an entry into the L2 state and the first power trim in the L2 state and between two consecutive power trims in the L2 state. Range: 0 to 1800 s • The L2-ATPR parameter defines the maximum aggregate transmit power reduction that can be performed in the L2 Request (i.e. at transition from L0 to L2) or through a single power trim in the L2 state. The profile creation is rejected in case the following is not respected: L2-ATPR ≤L2-ATPRT. Range: 0 to 31 dB, in steps of 1 dB • The L2-ATPRT parameter defines the total maximum aggregate transmit power reduction that can be performed in the L2 state. This is the sum of all reductions of L2 Request (i.e. at transition from L0 to L2) and power trims in the L2 state. The profile creation shall be rejected in case the following is not respected: L2-ATPR ≤L2-ATPRT. Range: 0 to 31 dB, in steps of 1 dB

TNG 1107-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

•

Switchover criterion The XTU-C initiates a switchover from L0 to L2 in case the monitored downstream user traffic (non-idle cells) has a bit rate lower than the configured Minimum bit rate in L2 for a period of N consecutive seconds. N is equal to max(10 s, L0-TIME). Once the user traffic ramps up again, the XTU-C switches over immediately from L2 to L0 in order not to loose any traffic. Power state changes from L0 to L2 or vice versa are transparent for the higher layers. Exceptions to the switchover from L0 to L2: • The modem never switches from L0 to L2 in case this would result in a bit rate increase. This situation could occur because the configuration where L2min > L0min is not rejected. • The modem never switches from L0 to L2 in case L2min is configured with value 0. • The modem never switches from L0 to L2 in case the configured value of L2min is bigger than the maximum achievable L2 bit rate within the standard.

Dynamic rate adaptation Dynamic rate adaptation is applicable to ADSLx and VDSL2. This mode is called Seamless Rate Adaptation (SRA) in the ADSL2x standard. The parameters described in this chapter are ignored on boards that do not support SRA (refer to the Product Information manual). Figure TNG 1107-2 illustrates how the upshift/downshift noise margins are used for dynamic rate adaptation. Figure TNG 1107-2: Upshift/Downshift noise margins

Maximum Noise Margin

Increase data rate if Upshift time interval has elapsed

Upshift Noise Margin

Increase data rate

Target Noise Margin Downshift Noise Margin Minimum Noise Margin

Decrease data rate if Downshift time interval has elapsed

Decrease data rate

0 dB Margin

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

The DS and US Upshift and Downshift Noise Margins and the DS and US Upshift and Downshift Time Intervals for rate adaptation are configurable via the xDSL Spectrum Configuration Profile. The profile creation is rejected in case the following is not respected:

• •

Minimum NM ≤Downshift NM ≤Target NM - 1 dB Upshift NM ≥ min(Target NM + 1 dB, 31 dB)

Although these parameters are only relevant in case RA Mode 3 (DYNAMIC) is selected, the rule specified above is checked independent from the RA Mode selection, because the RA Mode selection is specified in another profile.

•

•

Upshift Rate Adaptation: In case RA Mode 3 (DYNAMIC) is selected and the DS/US Noise Margin stays above the DS/US Upshift Noise Margin for more than the time specified by the DS/US Minimum Upshift Rate Adaptation Interval, then the XTU-R/XTU-C shall attempt to increase the DS/US net data rate. Range: • DS/US Upshift Noise Margin: 0 to 31 dB, in steps of 0.1 dB • DS/US Min Time Interval for Upshift Rate Adaptation: 0 to 16383 s Downshift Rate Adaptation: In case RA Mode 3 (DYNAMIC) is selected and the DS/US Noise Margin stays below the DS/US Downshift Noise Margin for more than the time specified by the DS/US Minimum Downshift Rate Adaptation Interval, then the XTU-R/XTU-C shall attempt to decrease the DS/US net data rate. Range: • DS/US Downshift Noise Margin: 0 to 31 dB, in steps of 0.1 dB • DS/US Min Time Interval for Downshift Rate Adaptation: 0 to16383 s

Artificial noise PSD DS This parameter is only applicable for ADSLx. The Artificial Noise PSD shape parameter specifies the transmitted referred artificial noise PSD level to be used as an additional noise source at the downstream transmitter. The same breakpoint definition is used as in custom DS/US PSD shape where the maximum number of PSD points is N=32 for DS. Artificial Noise is not applicable for US. Values: PSD point = [Frequency, PSD value]

• •

Frequency: 0 to 30000 kHz in steps of 1kHz PSD value: -140 to -40 dBm/Hz in steps of 0.5 dB

Note — -167.5 dBm/Hz states no artificial noise has to be applied.

TNG 1107-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

Modem features Proprietary modem features can be enabled or disabled via the xDSL Spectrum Configuration Profile.

• •

In cases where the proprietary modem features are disabled for a certain xDSL flavour, the modem is not allowed to activate proprietary features when operating in that flavour, i.e. the modem is strictly compliant with the standards. In cases where the proprietary modem features are enabled, the modem is allowed to use proprietary features.

Modem features can be individually enabled or disabled. Because the ADSLx modem is not able to deal with a flavour specific setting of the Modem Features parameter, the following restriction applies: The system rejects the creation of an xDSL Spectrum Configuration Profile in cases where the configuration of the Modem Features parameter is not identical for all ADSLx flavors. The setting for VDSLx can differ from the setting for ADSLx and can be different for VDSL1 and VDSL2.

VDSL band plan This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2. The VDSL Band Plan parameter selects one of the predefined VDSL Band Plans for ANSI or ETSI VDSL modes of operation:

•

•

Band Plans for ETSI, ITU-T or IEEE VDSL operational mode: • bandPlanA_4: 4 bands 998 band plan • bandPlanA_3: 3 bands 998 band plan • bandPlanA_2: 2 bands 998 band plan • bandPlanB_4: 4 bands 997 band plan • bandPlanB_3: 3 bands 997 band plan • bandPlanB_2: 2 bands 997 band plan • bandPlanAnnexB997E: ITU-T G993.2 VDSL2 Annex B band plan type “997E” • bandPlanAnnexB998E: ITU-T G993.2 VDSL2 Annex B band plan type “998E” • bandPlanAnnexB998ADE: ITU-T G993.2 VDSL2 Annex B band plan type “998ADE” • bandPlanAnnexBHPE: ITU-T G993.2 VDSL2 Annex B band plan type “HPE” Note: Not compatible with any VDSL1 opmodes and VDSL2 opmodes ITU-T G.993.2 VDSL2 profile 8A/8B/8C/8D Band Plan for ANSI VDSL operational mode: • bandPlanA_4: 4 bands 998 band plan • bandPlanA_3: 3 bands 998 band plan • bandPlanA_2: 2 bands 998 band plan • bandPlanAnnexA998: ITU-T G993.2 VDSL2 Annex A (998 extended) band plan

Optional band usage This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

The Optional Band Usage parameter specifies whether the VDSL modem is allowed to use the Optional band or not and defines its direction in case it is allowed. Values: off, on(US) or on(DS). The optional band usage is independent from the ADSL Band usage parameter: in case the ADSL band usage is set to “not allowed” and the optional band usage is “on”, the modem is still allowed to use the optional band. This parameter is ignored and the optional band usage prohibited if not supported by the HW.

Optional band start frequency This parameter is only applicable to VDSL2. The Optional Band Start Frequency parameter specifies the optional band start frequency in case the optional band usage is enabled. Range: 0, 1 to138 kHz, in steps of 1 kHz. The special value 0 (default) is interpreted as 25 kHz on POTS boards and 120 kHz on ISDN boards.

Optional band end frequency This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2. The Optional Band End Frequency parameter specifies the optional band end frequency in case the optional band usage is enabled. The beginning of the first DS band is shifted accordingly (no spectrum overlap). When the optional band usage is disabled, this parameter still fixes the beginning of the normal DS band. Range: 0, 138 to 552kHz, in steps of 1 kHz The special value 0 (default) is interpreted as 138 kHz on POTS boards and 276 kHz on ISDN boards.

ADSL band usage This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2. The ADSL Band Usage parameter specifies whether the VDSL modem is allowed to use the ADSL spectrum or not. It controls the use of the ADSL spectrum within the selected VDSL band, with the exception of the optional band, which is not impacted by this parameter. The ADSL band to be considered covers 25KHz to ADSL Band End Frequency. Values:

• • •

ADSL spectrum is allowed ADSL (25kHz to 1.1Mhz) spectrum is not allowed ADSL spectrum is not allowed until the ADSL Band End Frequency specified in “ADSL band end frequency”

TNG 1107-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

ADSL band end frequency This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2. The ADSL Band End Frequency parameter specifies the ADSL band end frequency in case the ADSL band usage is not allowed. Range: 276 to 2208 kHz, in steps of 1 kHz and special value 0 indicating that the default value of 1104 kHz shall be used.

Maximum nominal Power Spectral Density ADSLx: The DS and US Maximum Nominal PSD parameter specifies the maximum nominal transmit PSD during initialization and showtime (in dBm/Hz) for the applicable ADSLx flavour. In case the constraint imposed by the applicable standard is more stringent than the configured value, the configured value shall be ignored and the standard value shall be used.

• •

Range US: -60 to -32.9 dBm/Hz, in steps of 0.1 dBm/Hz Range DS: -60 to -37 dBm/Hz, in steps of 0.1 dBm/Hz

The MaxNomPSD parameter cannot be used to boost the PSD beyond the standard PSD, it can only be used to put additional constraints on top of the standard. The constraints imposed by the standards are summarized in Table TNG 1107-5. Table TNG 1107-5: Constraints Operating Mode

MaxNomPSD US

MaxNomPSD DS

ADSL1/ADSL2/ADSL2+ Annex A/B

-38 dBm/Hz

-40 dBm/Hz

READSL2 Mode 1

-36.4 dBm/Hz

-37 dBm/Hz

READSL2 Mode 2

-32.9 dBm/Hz

-37 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-32

-38 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-36

-38.5 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-40

-39 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-44

-39.4 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-48

-39.8 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-52

-40.1 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-56

-40.4 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-60

-40.7 dBm/Hz

-40 dBm/Hz

ADSL2/ADSL2+ Annex M/J EU/ADLU-64

-41 dBm/Hz

-40 dBm/Hz

VDSLx:

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

The DS and US Maximum Nominal PSD parameter specifies the maximum nominal transmit PSD during initialization and showtime (in dBm/Hz) for the applicable VDSLx flavour. It is used to further restrict the maximum Tx PSD mask defined in

• •

Range US: -95.5 to 0 dBm/Hz, in steps of 0.1 dBm/Hz with value 0 meaning “no constraint” Range DS: -95.5 to 0 dBm/Hz, in steps of 0.1 dBm/Hz with value 0 meaning “no constraint”

The MaxNomPSD parameter cannot be used to boost the PSD beyond the configured PSD shape, it can only be used to put additional constraints i.e. to further lower the PSD.

Maximum nominal aggregate transmit power The US and DS Maximum nominal Aggregate Transmit Power (ATP) parameter specifies the maximum nominal aggregate transmit power during initialization and showtime (in dBm) for the applicable xDSL flavour.

• •

Multi-ADSL: In case the constraint imposed by the applicable standard is more stringent than the configured value, the configured value shall be ignored and the standard value shall be used. VDSL: Except when the special value “standard” is configured, this parameter overrules the standard and the configured value applies in combination with the restrictions imposed by the configured PSD. The power can boost above the maximum transmit power defined in the standard. Value 25.5 is used as special “standard” value: • VDSL1: If the selected PSD is referring to a predefined PSD shape, the maximum transmit power defined in the corresponding standard shall be used, according to the deployment type (FTTEx or FTTCab) otherwise (customized PSD) no power limitation has to be applied. • VDSL2: The applicable maximum power constraint is the one corresponding to the selected VDSL2 profile.

Range US/DS:

• •

ADSLx: 0 to 25.5 dBm, in steps of 0.1 dBm VDSLx: -31 to 25.5 dBm, in steps of 0.1 dBm, with value 25.5 meaning “standard”.

The constraints imposed by the standards are summarized in Table TNG 1107-6.

TNG 1107-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters Table TNG 1107-6: Maximum value of MaxNomATP (non-overlapped operating modes) Operating Modes

MaxNomATP US

MaxNomATP DS

ADSL1/ADSL2/ADSL2+ Annex A

12.5 dBm

19.9 dBm

ADSL1/ADSL2/ADSL2+ Annex B

13.3 dBm

19.3 dBm

READSL2

12.5 dBm

18.8 dBm

ADSL2/ADSL2+ Annex M

12.5 dBm

19.3 dBm

ADSL2/ADSL2+ Annex J

13.4 dBm

19.3 dBm

VDSL1 ETSI ex

11.5 dBm

14.5 dBm

VDSL1 ETSI cab

11.5 dBm

11.5 dBm

VDSL1 ANSI ex

14.5 dBm

14.5 dBm

VDSL1 ANSI cab

14.5 dBm

11.5 dBm

VDSL2 profile 8a

14.5 dBm

17.5 dBm

VDSL2 profile 8b

14.5 dBm

20.5 dBm

VDSL2 profile 8c

14.5 dBm

11.5 dBm

VDSL2 profile 8d

14.5 dBm

14.5 dBm

VDSL2 profile 12a

14.5 dBm

14.5 dBm

VDSL2 profile 12b

14.5 dBm

14.5 dBm

VDSL2 profile 17a

14.5 dBm

14.5 dBm

VDSL2 profile 30a

14.5 dBm

14.5 dBm

Note — Because the ADSLx modem is not able to deal with a flavour specific setting of the Maximum Nominal Aggregate Transmit Power parameter, the following restriction applies: The system rejects the creation of an xDSL Spectrum Configuration Profile in cases where the configuration of the Maximum Nominal Aggregate Transmit Power parameter is not identical for all ADSLx flavours.

Selectable PSD shape For each xDSL mode of operation, the standard specifies the PSD shapes (templates or masks), defining the limits for the transmitted signal at XTU-C and XTU-R. Depending on regional spectrum management guidelines, there may be a need for additional constraints on the PSD to enable remote deployment of xDSL. In this case, the XTU-C is located in a remote cabinet located between the central office and the customer premises, rather than the Access Node.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-23 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

In practice, the lower part of the xDSL downstream spectrum should not be used when deploying xDSL in a remote cabinet and sharing the same binder with ADSLx services offered from the central office. Because of the extended spectrum of ADSL2+ and VDSL, for these modes it is possible not to use the lower part of the downstream spectrum and still offer significant bit rates. For VDSL, the enabling or disabling of the ADSL band portion of the VDSL band is done via the ADSL Band Usage configuration parameter.

•

• •

•

ADSL2+: For ADSL2+, the DS PSD shape is configurable via the xDSL Spectrum Configuration Profile. This parameter selects one of the predefined DS PSD Masks for ADSL2+ mode of operation (refer to Table TNG 1107-7). ADSL2 and ADSL2+: For ADSL2 and ADSL2+, the US PSD shape in Annex M and Annex J is configurable via the xDSL Spectrum Configuration Profile. VDSL1: For VDSL1, the DS/US PSD shape is configurable via the xDSL Spectrum Configuration Profile. This parameter selects one of the predefined ANSI or ETSI PSD shapes in the DS/US direction listed in Table TNG 1107-8. Consistency must be checked between the US/DS PSD shapes, operational mode and VDSL band plan parameter settings before a new spectrum profile is accepted. The VDSL1 ANSI PSD shapes are as defined in the VDSL ANSI standard. The VDSL1 ETSI PSD shapes are as defined in the VDSL ETSI standard. The PSD shape variant is selected based on the other configuration parameters, VDSL Band Plan and ADSL Band Usage. VDSL2: For VDSL2, the DS/US PSD shape is configurable via the xDSL Spectrum Configuration Profile. This parameter selects one of the predefined standard PSD shapes in the DS/US direction listed in Table TNG 1107-9. Consistency must be checked between the US/DS PSD shapes, operational mode and VDSL band plan parameter settings before a new spectrum profile is accepted. The VDSL2 PSD shapes are as defined in the VDSL2 ITU-T standard, ref.[18]. The PSD shape details are derived based on the other configuration parameters, VDSL Band Plan, Max Frequency, VDSL2 profile, ADSL Band Usage, Optional Band Usage, Optional Band Start and End Frequency.

Selectable DS PSD for ADSL2+: For ADSL2+ mode of operation a selection has to be made between a number of predefined downstream PSD masks. The normal (default) PSD mask is the one for central office deployment. The masks for cabinet deployment additionally restrict the lower part of the spectrum, with a cut-off frequency depending on the distance between central office and cabinet. In case the Central Office Mask is selected, there is no additional PSD shaping on top of the PSD Mask defined by G.992.5 Annex A/B/M. In case a Cabinet Mask is selected, the lower part of the spectrum is not used. The set of Cabinet Masks only differ in the cut-off frequency for the stop band (see Figure TNG 1107-3).

TNG 1107-24 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters Figure TNG 1107-3: ADSL2+ PSD Masks for Cabinet deployment PSD in dBm/ Hz PSD2 = -36.5

PSD1 = -95 t1

t2

subca rrier index linea r sca le)

subca rrier index = frequency (kHz)/Df (Df = 4.3125 kHz) Each of the Cabinet PSD masks has 2 breakpoints: (t1,PSD1),(t2,PSD2) PSD1=-95 dBm/Hz PSD2=-36.5 dBm/Hz t2 varies from tone 100 to 280 in steps of 10 tones t1 = rounddown (t2 - (PSD2-PSD1)/2.2 dB/tone) = t2-27

This results in a total of 19 PSD Masks for Cabinet deployment, as illustrated in Table TNG 1107-7. Table TNG 1107-7: ADSL2+ PSD masks for Cabinet deployment PSD Mask

t1

t2

f1 (kHz)

f2 (kHz)

ADSL2Plus Ca 100

73

100

314.8125

431.25

ADSL2Plus Ca 110

83

110

357.9375

474.375

ADSL2Plus Ca 120

93

120

401.0625

517.5

ADSL2Plus Ca 130

103

130

444.1875

560.625

ADSL2Plus Ca 140

113

140

487.3125

603.75

ADSL2Plus Ca 150

123

150

530.4375

646.875

ADSL2Plus Ca 160

133

160

573.5

625 690

ADSL2Plus Ca 170

143

170

616.6875

733.125

ADSL2Plus Ca 180

153

180

659.8125

776.25

ADSL2Plus Ca 190

163

190

702.9375

819.375

ADSL2Plus Ca 200

173

200

746.0625

862.5

ADSL2Plus Ca 210

183

210

789.1875

905.625

ADSL2Plus Ca 220

193

220

832.3125

948.75

ADSL2Plus Ca 230

203

230

875.4375

991.875

ADSL2Plus Ca 240

213

240

918.5625

1035

ADSL2Plus Ca 250

223

250

961.6875

1078.125

ADSL2Plus Ca 260

233

260

1004.813

1121.25

ADSL2Plus Ca 270

243

270

1047.938

1164.375

ADSL2Plus Ca 280

253

280

1091.063

1207.5

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-25 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Selectable PSDS for VDSL1: For both ETSI and ANSI VDSL mode of operation, a selection has to be made between a number of predefined downstream and upstream PSD shapes. Different PSDs are defined for central office deployment and for cabinet deployment. Table TNG 1107-8: VDSL1 DS/US PSD Shapes Operational Mode

DS PSD Shape

US PSD Shape

Band Plan

ANSI, ITU, IEEE

ANSI_FTTEx_M1

ANSI_FTTEx_M1

ANSI:

ANSI_FTTEx_M2

ANSI_FTTEx_M2

ANSI_FTTCab_M1

ANSI_FTTCab_M1

ANSI_FTTCab_M2

ANSI_FTTCab_M2

ANSI_FTTCab_M1_ADSL

ANSI_FTTCab_M1

ANSI_FTTCab_M2_ADSL

ANSI_FTTCab_M2

ANSI_FTTCab_M1_ADSL2+

ANSI_FTTCab_M1

ANSI_FTTCab_M2_ADSL2+

ANSI_FTTCab_M2

ETSI_PexP1.M1

P.M1

ETSI_PexP1.M2

P.M2

ETSI_PexP2.M1

P.M1

ETSI_PexP2.M2

P.M2

ETSI_Pcab.M1

P.M1

ETSI_Pcab.M2

P.M2

ETSI_PcabX.M1_ADSL

P.M1

ETSI_PcabX.M2_ADSL

P.M2

ETSI_PcabX.M1_ADSL2+

P.M1

ETSI_PcabX.M2_ADSL2+

P.M2

ETSI_Pex.M2_ADSLSample1

P.M2

ETSI_Pex.M2_ADSLSample2

P.M2

ETSI_Pex.M2_ADSLSample3

P.M2

ETSI_Pex.M2_ADSLSample4

P.M2

Custom PSD shape

P.M1 / P.M2

ETSI, ITU, IEEE

Bandplan A998, AnnexA998

ETSI: All bandplans except AnnexBHPE and AnnexA998

The VDSL DS PSD Shape, VDSL US PSD Shape, Operating Mode and VDSL Band Plan configuration values must be consistent. The combinations listed in Table TNG 1107-8 are allowed, other combinations cause the spectrum profile to be rejected.

Note — Band plans are not accepted by all configured operating modes.

Selectable PSDS for VDSL2:

TNG 1107-26 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

For the VDSL2 modes of operation a selection has to be made between a number of predefined downstream and upstream PSD shapes. Different PSDs are defined depending on the deployment region. Table TNG 1107-9: VDSL2 DS/US PSD Shapes Operational Mode

DS PSD Shape

US PSD Shape

Band Plan

ITU-T G993.2

PsdMaskRegion

PsdMaskRegion

ANSI:

any VDSL2 profile

Custom PSD shape

Custom PSD shape

Bandplan A998 AnnexA998

PsdMaskRegionB_M1

PsdMaskRegionB_M1

ETSI:

Custom PSD shape

All bandplans except AnnexBHPE and AnnexA998

PsdMaskRegionB_M2

PsdMaskRegionB_M2 Custom PSD shape

Custom PSD shape

PsdMaskRegionB_M1/2 Custom PSD shape

PsdMaskRegionB_M1

ITU-T G993.2 VDSL2 profiles 12A/12B/17A(1)

PsdMaskRegionB_M2

PsdMaskRegionB_M1

ETSI:

Custom PSD shape

AnnexBHPE

PsdMaskRegionB_M2 Custom PSD shape

Custom PSD shape

PsdMaskRegionB_M1/2 Custom PSD shape

Note (1)

If 8A/8B/8C/8D is enabled in VDSL2 spectrum profile together with 12A/12B/17A then this will be accepted by xDSL manager. Enabling of VDSL1 operating mode together with VDSL2 12A/12B/17A operating modes with AnnexBHPE bandplan will be allowed.

The VDSL2 DS PSD Shape, VDSL2 US PSD Shape, Operating Mode and VDSL Band Plan configuration values must be consistent. The combinations listed in Table TNG 1107-9 are allowed, other combinations cause the spectrum profile to be rejected.

Note — A bandplan will however be accepted if allowed by a configured operating mode although rejected by another configured operating mode. Region C is not supported. Selectable US PSD for ADSL2/ADSL2+ Annex M and Annex J:

• • • • • • • •

EU-56 EU-60 EU/ADLU-32 EU/ADLU-36 EU/ADLU-40 EU/ADLU-44 EU/ADLU-48 EU/ADLU-52

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-27 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

• • •

EU/ADLU-56 EU/ADLU-60 EU/ADLU-64

Custom DS/US PSD shape For ADSL2+ and VDSLx mode of operation, it is possible to specify custom PSD shapes (templates or masks), defining the limits for the transmitted signal at XTU-C and XTU-R. A custom PSD is configurable for DS and US directions in ADSL2+ and VDSLx mode via the xDSL Spectrum Configuration Profile.

• • •

ADSL2+: Currently supported for DS only, this parameter specifies the max allowed transmit PSD in case the custom PSD shape value is configured in “Selectable PSD shape” and is ignored otherwise. VDSL1: Currently supported for DS only, this parameter specifies the max allowed transmit PSD in case the custom PSD shape value is configured in “Selectable PSD shape” and is ignored otherwise. VDSL2: This parameter specifies the max allowed transmit PSD and can be used in addition of a selectable PSD shape value configured in “Selectable PSD shape”. If both parameters are configured, the per-tone minimum of the two PSDs are applied.

Up to N PSD points can be specified. The PSD mask is made by connecting the points with straight lines, considering a linear PSD axis in [dBm/Hz], and either a linear, either a logarithmic frequency axis in [Hz], depending on the psdFreqScale parameter. The PSD has to be considered as a “Mask” or a “Template”, depending on the PsdType parameter. DS: N=20 (ADSL2+) and N=32 (VDSLx) US: N=20 (VDSLx) Values:

• • • • •

psdFreqScale: linear or logarithmic (VDSLx) psdType: Mask or a Template (VDSLx) PSD point = [Frequency, PSD value] Frequency: • 0 to 2208 kHz (ADSL2+) • 0 to 30000 kHz (VDSLx) PSD value: 0 to -95 dBm/Hz

For ADSL2+ and VDSL, the following rules are applicable:

• •

The successive PSD points must have increasing frequencies. It is allowed that for two successive PSD points, different PSD levels are defined at the same frequency f (brickwall): • point x: PSDx, f • point x+1: PSDx+1,f

TNG 1107-28 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

Power backoff mode and policing Upstream power back-off (UPBO) is a remedy to the near-far problem. It allows for reduction of the upstream transmit PSD on short lines in order not to impact the upstream performance on longer lines. Either the maximum transmit PSD or the maximum receive PSD can be applied. The specification of the maximum receive PSD is more powerful because it takes into account the characteristics of the loop. The US Power Backoff Mode parameter specifies if the US Power Backoff mechanism will be used or not for the applicable xDSL flavour:

•

•

PBO Off: US PBO mechanism is not used: • For ADSLx, the configured Maximum Aggregate Receive Power is not used. • For VDSL, the US Receive PSD shape is don't care. The VTU-R directly uses the US PSD Shape parameter as the transmit PSD mask. PBO On: • For ADSLx, the ATU-C requests US PBO to comply to the configured Maximum Aggregate Receive Power. • For VDSL, the VTU-R derives the transmit PSD mask from the US Receive PSD Shape parameter

To reduce the crosstalk effect and ensure good xDSL performance for multiple ports, it is recommended to use the PBO On Mode. Because the ADSLx modem is not able to deal with a flavour specific setting of the Power Backoff Mode parameter, the following restriction applies: VDSL2: In order to be more robust against Upstream Power Back-Off non-compliant CPEs, the modem at CO side can be configured to police the CPEs compliancy to requested Upstream Power Back-Off. 4 Modes have been defined to fit this requirement and having different impact on the service provided to the end user:

• •

•

•

PBO Policing Off: No check on the actual Power Back-Off is performed. PBO Policing On Passive mode: Actual Power Back-Off is checked against the requested configuration. If a non-compliant CPE is detected, the UPBO Violation alarm is raised. No other corrective action is taken. PBO Policing On Shutdown mode: Actual Power Back-Off is checked against the requested configuration. If a non-compliant CPE is detected, the line is shut down by the modem and the Activation Failure - CPE Policing alarm and the UPBO Violation alarm is raised. The modem stays in L3 Idle mode until either reconfiguration or toggling of the administrative state by the operator. PBO Policing On US0 only mode: Actual Power Back-Off is checked against the requested configuration. If a non-compliant CPE is detected, the line attempts to resynchronize in US0 only mode and the UPBO Violation alarm is raised.

Maximum aggregate receive power This parameter is only applicable to ADSLx.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-29 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

The ADSLx US Maximum Aggregate Receive Power (ARP) parameter represents the maximum upstream aggregate receive power over a set of subcarriers (in dBm) as specified in the relevant recommendation. The ATU-C requests an upstream power cutback such that the upstream aggregate receive power over that set of subcarriers is at or below the configured maximum value for the applicable ADSLx flavour. Range: -25.5 to 25.5 dBm, in steps of 0.1 dB. Because the ADSLx modem is not able to deal with a flavour specific setting of the Maximum Aggregate Receive Power parameter, the following restriction applies: The system rejects the creation of an xDSL Spectrum Configuration Profile in case the configuration of the Maximum Aggregate Receive Power parameter is not identical for all ADSLx flavours.

Receive PSD Shape Upstream This parameter is only applicable to VDSLx. The VDSL Maximum Receive US PSD shape parameter selects (in case of PBO mode On) one of the predefined Rx US PSD shapes corresponding to different ANSI and ETSI noise profiles (A, B, …F) or another predefined custom selection or the special full custom specification (see “Customized RX PSD Shape Upstream”) or the A&B parameters specification (see “A and B Parameters for US PBO PSD”) or the equal FEXT parameters specification. Table TNG 1107-10: VDSL1, VDSL2 RX US PSD Shapes Operational Mode

RX US PSD Shape

VDSL1: ANSI, ITU, IEEE

ANSI_A

VDSL2: ITU

ANSI_F ANSI Custom Ex ANSI Custom Cab ABParamRxPsdShape EqualFextRxPsdUpstream

(1 of 2)

TNG 1107-30 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

Operational Mode

RX US PSD Shape

VDSL1: ETSI, ITU, IEEE

ETSI_A

VDSL2: ITU

ETSI_B ETSI_C ETSI_D ETSI_E ETSI_F ETSI Custom Ex ETSI Custom Cab ABParamRxPsdShape Custom RX PSD Shape EqualFextRxPsdUpstream

(2 of 2)

Customized RX PSD Shape Upstream This parameter is only applicable to VDSLx. The custom RX PSD Shape Upstream parameter specifies the maximum receive PSD allowed in US in case PBO is on and the custom RX PSD shape value is configured in “Receive PSD Shape Upstream” and is ignored otherwise. The same definition is used as in “Custom DS/US PSD shape” where the maximum number of PSD points N=20.

G.Hs Tones Tx Power Control This parameter is only applicable to VDSLx. The G.Hs Tones Power Control parameter specifies how to control the Tx power of the G.hs tones. Values:

• • •

standard: the maximum power as per G994.1 standard definition applies. auto: the maximum Tx power level is derived from the Psd Shape Downstream. per tone set: the power of the different tone sets is controlled individually (see “Per tone set G.Hs Tones Tx Power Control (A43/B43/A43c/V43)”)

Per tone set G.Hs Tones Tx Power Control (A43/B43/A43c/V43) This parameter are only applicable to VDSLx. The G.Hs Tones Power Control is configurable individually for each tone set in VDSLx mode via the xDSL Spectrum Configuration Profile. For each tone set (A43, B43, A43c, V43) this parameter specifies how to control the Tx power of the G.hs tones in case the per tone set value is selected for the overall G.Hs Tones Power Control configuration parameter (see “G.Hs Tones Tx Power Control”) and is ignored otherwise.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-31 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Values:

• • •

standard: the maximum power as per G994.1 standard definition applies. auto: the maximum Tx power level is derived from the Psd Shape Downstream. manual: the value set in GhsTonesTx Power Level of the corresponding tone set applies (see “Per tone set G.Hs Tones Tx Power Level A43/B43/A43c/V43”)

Per tone set G.Hs Tones Tx Power Level A43/B43/A43c/V43 The G.Hs Tones Power Level is configurable per tone set individually in VDSLx mode via the xDSL Spectrum Configuration Profile. For each tone set (A43, B43, A43c, V43) this parameter specifies the Tx power level of the G.hs tones in case the manual value is selected for the corresponding tone set Tx Power Control (see “Per tone set G.Hs Tones Tx Power Control (A43/B43/A43c/V43)”) and is ignored otherwise. The power of each tone of the set is equivalent to the given PSD value integrated in a total bandwidth of 4.3125 kHz. Range: -99 to -40 dBm/Hz in steps of 0.5 dBm/Hz, where value -99 dBm/Hz indicates that the full set is not used (i.e. no power allowed).

Maximum number of bands This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2. The Maximum Number of Bands parameter specifies the number of bands to be supported for the given band plan. In case the selected band plan (see “VDSL band plan”) contains more bands, the system disables the additional bands located at higher frequencies first. Otherwise, this parameter has no effect. The optional band is NOT counted as a band, and does not take part to the number of bands (example: if the maximum number of bands is set to 3, the modem is allowed to use the optional band + DS1 + US1 + DS2). Values: 2-8 and “unlimited”.

Maximum frequency This parameter is only applicable to VDSL and is common for VDSL1 and VDSL2. The Maximum Frequency parameter specifies the maximum frequency usable in DS and US during showtime. Values: 1104 to 30000 kHz and “unlimited”.

A and B Parameters for US PBO PSD This parameter is only applicable to VDSLx. The A and B parameters for US PBO PSD specify the a and b values per upstream band to be used for computing the PSD ref for US PBO in case PBO is on and the ABParamRxPsdShape value or EqualFextRxPsdUpstream is configured in “Receive PSD Shape Upstream”. They are ignored otherwise.

TNG 1107-32 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

If ABParamRxPsdShape is selected, the PSD ref for US PBO will be as shown in Figure TNG 1107-4. Figure TNG 1107-4: PSD reference for US PBO

PSDREF(f) = -(a + b f)

f is the frequency in MHz. Range for a: 40 to 80.95 dBm/Hz Range for b: 0 to 40.95 dBm/Hz Special values a = 40 dBm/Hz and b = 0 dBm/Hz is used to indicate that no A/B parameters are specified for the corresponding band.

US PBO electrical length This parameter is only applicable to VDSL2. The US PBO Electrical Length parameter specifies the US electrical length value to be used instead of the value estimated by the XTU-R. Range: 0 to 127.5dB at 1 MHz in steps of 0.5 dB plus the special value “Electrical Length Estimated by XTU-R”.

Virtual Noise PSD Shape US/DS This parameter is only applicable to VDSL2. The Virtual Noise PSD shape parameter specifies the Tx referred virtual noise PSD level to be used in determining the SNR margin. The same breakpoint definition is used as in “Custom DS/US PSD shape” where the maximum number of PSD points is N=32 for DS and N=16 for US. Values: PSD point = [Frequency, PSD value]

• •

Frequency: 0 to 30000 kHz in steps of 1kHz PSD value: -140 to -40 dBm/Hz in steps of 0.5 dB -167,5 dBm/Hz states no virtual noise has to be applied.

Virtual Noise SNRM mode US/DS This parameter is only applicable to VDSL2. The Virtual Noise SNRM mode parameter specifies the Signal to Noise Ratio Margin mode to be used with the virtual noise.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-33 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Values:

• •

SNRM_MODE_1: the reference noise PSD is the external noise PSD present at U interface SNRM_MODE_2: the reference noise PSD is the maximum (tone per tone) between the external noise PSD present at U interface and the received virtual noise (as defined in Virtual noise PSD shape)

FEXT Parameters for US PBO PSD This parameter is only applicable to VDSL2. The per band FEXT parameter for US PBO PSD specifies the reference electrical length value per upstream band to be used, on top of the A and B parameters defined in “A and B Parameters for US PBO PSD”, for computing the PSD reference for US PBO in case PBO is on and the EqualFextRxPsdUpstream is configured in “Receive PSD Shape Upstream”. They are ignored otherwise. Range is 1.8 to 63 dB with steps of 0.1dB plus special value 0 dB.

• •

Special value 0 dB is used to indicate that automatic mode shall be applied. Special value 1.8 dB is used to indicate that no equal FEXT parameter is specified for the corresponding band.

If the automatic mode is selected, the modem uses a dedicated mechanism to optimally apply the Equal FEXT Upstream Power Back-Off without providing any manual setting for this parameter. The system rejects the creation of an xDSL Spectrum Configuration Profile in case the configuration of the FEXT parameter for US PBO PSD is a mixture of manual and automatic configuration.

xDSL RTX profile configuration parameters This section lists all parameters that can be configured in the xDSL RTX Configuration Profile.

RTX Mode Downstream This parameter allows the manager to enable the RTX feature in downstream direction on lines supporting RTX. As long as the feature has not been enabled, the other RTX parameters will have no effect on this line.

RTX Mode Upstream This parameter allows the manager to enable the RTX feature in upstream direction on lines supporting RTX. As long as the feature has not been enabled, the other RTX parameters will have no effect on this line.

RTX Minimum Expected Throughput Downstream This parameter specifies the minimum expected throughput (bitrate) for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden.

TNG 1107-34 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

Range: 0..262143 kbits/sec. Default: 64 kbits/sec.

RTX Minimum Expected Throughput Upstream This parameter specifies the minimum expected throughput (bitrate) for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 64 kbits/sec.

RTX Planned Expected Throughput Downstream This parameter specifies the planned expected throughput (bitrate) for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 128 kbits/sec.

RTX Planned Expected Throughput Upstream This parameter specifies the planned expected throughput (bitrate) for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 128 kbits/sec.

RTX Maximum Expected Throughput Downstream This parameter specifies the maximum expected throughput (bitrate) for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 262143 kbits/sec.

RTX Maximum Expected Throughput Upstream This parameter specifies the maximum expected throughput (bitrate) for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 262143 kbits/sec.

RTX Maximum Net Data Rate Downstream This parameter specifies the maximum net data rate for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 262143 kbits/sec.

RTX Maximum Net Data Rate Upstream This parameter specifies the maximum net data rate for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0..262143 kbits/sec. Default: 262143 kbits/sec.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-35 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

RTX Minimum Delay Downstream This parameter specifies the minimum instantaneous delay allowed (only due to the effect of the retransmission) for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Range: 0..63 msec. Default: 0 msec.

RTX Minimum Delay Upstream This parameter specifies the minimum instantaneous delay allowed (only due to the effect of the retransmission) for the downstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0..63 msec. Default: 0 msec.

RTX Maximum Delay Downstream This parameter specifies the maximum instantaneous delay allowed (only due to the effect of the retransmission) for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. When RTX is used in this direction it invalidates the xdslMaxInterleavingDelayDownstream parameter of the Service profile Range: 2..63 msec. Default: 12 msec.

RTX Maximum Delay Upstream This parameter specifies the maximum instantaneous delay allowed (only due to the effect of the retransmission) for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. When RTX is used in this direction it invalidates the xdslMaxInterleavingDelayUpstream parameter of the Service profile Range: 2..63 msec. Default: 12 msec.

RTX Minimum Impulse Noise Protection SHINE Downstream This parameter specifies the minimum impulse noise protection against SHINE, for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: 0..63 symbols. Default: 8 symbols.

RTX Minimum Impulse Noise Protection SHINE Upstream This parameter specifies the minimum impulse noise protection against SHINE, for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: 0..63 symbols. Default: 8 symbols.

TNG 1107-36 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

RTX Minimum Impulse Noise Protection REIN Downstream This parameter specifies the minimum impulse noise protection against REIN, for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: 0..7 symbols. Default: 0 symbols.

RTX Minimum Impulse Noise Protection REIN Upstream This parameter specifies the minimum impulse noise protection against REIN, for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: 0..7 symbols. Default: 0 symbols.

RTX REIN Inter-arrival Time Downstream This parameter specifies the inter-arrival time that shall be assumed for REIN protection for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Values: 1 (derivedFrom100Hz), 2 (derivedFrom120Hz). Default: 1

RTX REIN Inter-arrival Time Upstream This parameter specifies the inter-arrival time that shall be assumed for REIN protection for the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. Values: 1 (derivedFrom100Hz), 2 (derivedFrom120Hz). Default: 1

RTX SHINE Ratio Downstream This parameter specifies the SHINE ratio for the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Range: 0 to 0.100 with increments of 0.001. Default: 0.010.

RTX SHINE Ratio Upstream This parameter specifies the SHINE ratio for the downstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0 to 0.100 with increments of 0.001. Default: 0.010.

RTX Leftr Threshold Downstream This parameter specifies the threshold for declaring a near-end 'leftr' defect in the downstream direction when xdslRtxModeDownstream is different from rtxForbidden. Range: 0.01 to 0.99 with increments of 0.01. Default: 0. The special value 0 means the ETR shall be used as the default threshold for declaring a 'leftr' defect.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-37 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

RTX Leftr Threshold Upstream This parameter specifies the threshold for declaring a near-end 'leftr' defect in the upstream direction when xdslRtxModeUpstream is different from rtxForbidden. Range: 0.01 to 0.99 with increments of 0.01. Default: 0. The special value 0 means the ETR shall be used as the default threshold for declaring a 'leftr' defect.

xDSL DPBO profile configuration parameters This section lists all parameters that can be configured in the xDSL DPBO Configuration Profile.

DPBO Electrical Length This parameter specifies the electrical length of the loop segment from the exchange to the remote flexibility point (cabinet). If set to 0 dB, all the DPBO parameters are ignored except xdslDpboCustomPsdMaskDownstream. This parameter matches the DPBOESEL parameter described in ITU-T G.997.1. Range: 0 to 255.9 dB in steps of 0.1 dB

DPBO Assumed Exchange PSD Mask This parameter specifies the Assumed Exchange PSD mask to be protected by the DPBO shaping mechanism at the remote flexibility point (cabinet). This parameter matches the DPBOEPSD parameter described in ITU-T G.997.1. A number of 2 to 16 PSD points can be specified. The successive PSD points must have increasing (≥) frequencies. It is allowed that for two successive PSD points, different PSD levels are defined at a same frequency (brickwall). Values: PSD point = [Frequency, PSD value]

• •

Frequency: 0 to 30000 kHz in steps of 1kHz PSD value: -127.5 to 0 dBm/Hz in steps of 0.1 dB

The system rejects the creation of an xDSL DPBO Configuration Profile in case no Assumed Exchange PSD Mask is specified and the DPBO Electrical Length is different from 0 and the DPBO Minimum Frequency is lower than DPBO Maximum Frequency.

DPBO Cable Model Parameters “ABC” The DPBO Cable Model parameters match the DPBOESCMA, DPBOESCMB, DPBOESCMC parameters described in ITU-T G.997.1.

• • •

DPBOESCMA range is -1 to 1.5 with steps of 2-8. DPBOESCMB range is -1 Hz-0.5 to 1.5 Hz-0.5 with steps of 2-8 Hz-0.5. DPBOESCMC range is -1 Hz-1 to 1.5 Hz-1 with steps of 2-8 Hz.

TNG 1107-38 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

DPBO Minimum and Maximum Frequency These parameters specify the frequency range over which DPBO shaping is applied. These parameters match the parameters DPBOFMIN and DPBOFMAX parameters described in ITU-T G.997.1. If xdslDpboMinFrequency is equal to xdslDpboMaxFrequency, all the DPBO parameter are ignored except xdslDpboCustomPsdMaskDownstream. Range: 0 to 30000Khz with steps of 1Khz. The system rejects the creation of an xDSL DPBO Configuration Profile if the DPBO Minimum Frequency is greater than the DPBO Maximum Frequency.

DPBO Minimum Usable Signal level This parameter specifies the DPBO minimum usable signal level. This parameter is used to determine the maximum usable frequency. Above this frequency DPBO shaping is not applied anymore. This parameter matches the DPBOMUS parameter described in ITU-T G.997.1. Range: -140 to 0 dBm/Hz with steps of 0.1 dBm/Hz.

DPBO Custom PSD Mask Downstream This parameter specifies the PSD breakpoints of the DPBO Custom PSD Mask. A number of 0 or 2 to 32 PSD breakpoints can be specified. This parameter matches the PSDMASKds parameter described in ITU-T G.997.1. This set of breakpoints may contain two subsets:

• •

The first sub-set defines the DPBO Custom PSD Mask. It matches the DPBOPSDMASKds parameter described in ITU-T G.997.1. The second sub-set (if any), defines the DPBO Minimum Override Mask. It matches the DPBOLFO parameter described in ITU-T G.997.1.

The successive PSD points of each sub-set must have increasing (≥) frequencies. It is allowed that for two successive PSD points, different PSD levels are defined at a same frequency (brickwall). Each subset must have 0 or at least 2 PSD breakpoints defined (see also remark below). The second sub-set starts at the first breakpoint whose frequency is lower than the frequency of the previous breakpoint. Values:

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-39 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

PSD point = [Frequency, PSD value]

• •

Frequency: 0 to 30000 kHz in steps of 1kHz PSD value: -127.5 to 0 dBm/Hz in steps of 0.1 dB

Note — As the transition from the Custom PSD Mask to the Minimum Override Mask is detected by a lower frequency than the previous one, if only a Minimum Override Mask is wanted one has to configure a dummy Custom PSD Mask in order to have that frequency transition. Extra DPBO Maximum Usable Frequency Control This parameter specifies the electrical length to be used for the computation of the DPBO Maximum Usable Frequency. It enables a more flexible control of the computation of the DPBO maximum usable frequency compared to the standard. Range: 0 to 255.9 dB with 0,1 dB steps plus special value 300 dB Special value is used to indicate that maximum usable frequency is calculated using standard DPBO algorithm.

Extra DPBO Offset This parameter specifies the additional extra DPBO Offset parameter used for further fine tuning of the “Predicted attenuated exchange PSD Mask”. When configured with special value 0 dB, this parameter is disabled. Range: -256 to 255.9 dB with 0,1 dB steps.

Extra DPBO Remote Side Electrical Length This parameter specifies the extra DPBO remote side electrical length parameter. If this parameter is set different from 0dB it modifies the standard DPBO algorithm defined in ITU-T G.997.1 by adding an extra term, function of this parameter, used to perform equal FEXT DPBO. Range is 0 to 255.99 dB with 0.01dB steps

xDSL line overrule record configuration parameters This section lists all parameters that can be configured in the xDSL line overrule record.

TNG 1107-40 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

The following applies to the xDSL line overrule record:

• • •

The xDSL overrule record can only be created on already configured lines. There is no capacity restriction, it can be done on all configured lines. All the parameters of the xDSL overrule record are stored persistently. The parameters, except the “no-overrule” ones, defined in the xDSL overrule record will replace the (profile) parameters from the line. No consistency checks are performed between profile parameters and overrule parameters. If there is an inconsistency then the proxy will report this as an Configuration Error or Configuration Not Feasible alarm.

Maximum Bit rate (channel related) The DS and US (overrule) maximum bit rates for channel-1 can be configured via the xDSL Overrule Record. This parameter specifies the overruled value of the maximum bit rate specified in the attached service-profile at this line. Range: -1, 0 to 262143 kbit/s, in steps of 1 kbit/s. with value -1 meaning “no_overrule”

Maximum Interleaving Delay (channel related) The DS and US (overrule) Maximum Interleaving Delay for channel-1 can be configured via the xDSL Overrule-Record. This parameter specifies the overruled value of the maximum interleaving delay specified in the attached service-profile at this line. Range DS/US: -1, 1 to 63 ms with value -1 meaning “no_overrule”

Minimum Impulse Noise Protection (channel related) The DS and US (overrule) Minimum Impulse Noise Protection for channel-1 can be configured via the xDSL Overrule-Record. This parameter specifies the overruled value of the Minimum Impulse Noise Protection as specified in the attached service-profile at this line. Range DS/US: -1, 0 to 8 symbols, in steps of 0.1 symbols with value -1 meaning “no_overrule”

Target Noise Margin The DS and US (overrule) Target Noise Margin can be configured via the xDSL Overrule-Record. This parameter specifies the overruled value of the Target Noise Margin as specified in the attached spectrum-profile at this line. Range DS/US: -1, 0 to 31 dB, in steps of 0.1 dB with value -1 meaning “no_overrule”.

Note — No consistency checks will be done with respect to the Minimum- and Maximum- Noise Margins defined in the attached Spectrum Profile since also no consistency checks are possible between the profile parameters and the Overrule-parameters at the moment the profile is changed.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-41 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Maximum Nominal PSD Level The DS and US (overrule) Maximum Nominal PSD can be configured via the xDSL Overrule-Record. This parameter specifies the overruled value of the Maximum Nominal PSD as specified in the attached spectrum-profile at this line. Range US: -95.5 to 0.1 dBm/Hz, in steps of 0.1 dBm/Hz with value 0 meaning “no constraint” and with value 1 meaning “no_overrule”.

Note — This parameter is applicable for all flavours although the original parameter is a flavour dependant parameter. The Manager will overwrite the flavour specific values before applying it to the proxy. To cope with the different ranges following rules have to be taken into account:

• • •

When the overrule value is below the min limit of a specific flavour then this flavour specific value is set equal to his own minimum. When the overrule value is higher then the max limit of a specific flavour then this flavour specific value is set equal to his maximum. In all other cases the overrule value is copied to all flavour specific parameters.

Carrier Mask The DS and US (overrule) carrier mask can be configured via the xDSL Overrule-Record. This parameter specifies the overruled value of the carrier mask as specified in the attached spectrum-profile on this line (for the definition of a carrier mask (see “Carrier masking”)). An “all one’s” configuration means a “no_overrule”.

Noise PSD

•

Noise Psd Mode: The DS and US Noise PSD mode can be configured via the xDSL Overrule-Record. This parameter specifies if the value of the Noise PSD as specified in the overrule-record will overrule the original noise-PSD. If overruled then this parameter specifies the type of noise: artificial or virtual.

Note 1 — In case of Downstream, both Virtual and Artificial can be selected. In case of Upstream only Virtual can be selected. Note 2 — If the NoiseMode is set to Overrule Virtual Noise and

• •

NoisePsd is empty, the VN-SNRM mode parameter in the spectrum profile must be overruled with value 1 NoisePsd is not empty, the VN-SNRM mode parameter in the spectrum profile must be overruled with value 2

TNG 1107-42 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

•

Noise PSD: The DS and US (overrule) Artificial/Virtual Noise PSD can be configured via the xDSL Overrule-Record. This parameter specifies the overruled value of the Artificial/Virtual Noise PSD as specified in the attached spectrum-profile on this line. The same breakpoint definition is used as in “Custom DS/US PSD shape” where the maximum number of PSD points is N=32 for DS and N=16 for US. Values: PSD point = [Frequency, PSD value] • Frequency: 0 to 30000 kHz in steps of 1kHz • PSD value: -140 to -40 dBm/Hz in steps of 0.5 dB -167,5 dBm/Hz states no noise has to be applied.

RTX Mode Downstream This parameter allows the manager to enable the RTX feature in downstream direction on lines supporting RTX which will overrule the xdslRtxModeDownstream parameter in the RTX-profile. As long as the feature has not been enabled, the other RTX parameters will have no effect on this line.

RTX Mode Upstream This parameter allows the manager to enable the RTX feature in upstream direction on lines supporting RTX which will overrule the xdslRtxModeUpstream parameter in the RTX-profile. As long as the feature has not been enabled, the other RTX parameters will have no effect on this line.

RTX Maximum Net Data Rate Downstream This parameter specifies the maximum net data rate for the downstream direction, which will overrule the xdslRtxMaxNetDataRateDownstream of the RTX profile when xdslOverruleRtxModeDownstream is different from rtxForbidden. Range: -1,0..262143 kbits/sec with value -1 meaning “no_overrule”.

RTX Maximum Net Data Rate Upstream This parameter specifies the maximum net data rate for the upstream direction, which will overrule the xdslRtxMaxNetDataRateUpstream of the RtxProfile when xdslOverruleRtxModeUpstream is different from rtxForbidden. Range: -1,0..262143 kbits/sec with value -1 meaning “no_overrule”.

RTX Maximum Expected Throughput Downstream This parameter specifies the maximum expected throughput for the downstream direction, which will overrule the xdslRtxMaxExpThrptDownstream of the RTX profile when xdslOverruleRtxModeDownstream is different from rtxForbidden. Range: -1,0..262143 kbits/sec with value -1 meaning “no_overrule”.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-43 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

RTX Maximum Expected Throughput Upstream This parameter specifies the maximum expected throughput for the upstream direction, which will overrule the xdslRtxMaxExpThrptUpstream of the RTX profile when xdslOverruleRtxModeUpstream is different from rtxForbidden. Range: -1,0..262143 kbits/sec with value -1 meaning “no_overrule”.

RTX Minimum Impulse Noise Protection against SHINE Downstream This parameter specifies the minimum impulse noise protection against SHINE, for the downstream direction, which will overrule the xdslRtxMinInpShineDownstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: -1,0..63 symbols with value -1 meaning “no_overrule”.

RTX Minimum Impulse Noise Protection against SHINE Upstream This object defines the minimum impulse noise protection against SHINE, for the upstream direction, which will overrule the xdslRtxMinInpShineUpstream of the RtxProfile when xdslOverruleRtxModeUpstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: -1,0..63 symbols with value -1 meaning “no_overrule”.

RTX Minimum Impulse Noise Protection against REIN Downstream This parameter specifies the minimum impulse noise protection against REIN, for the downstream direction, which will overrule the xdslRtxMinInpReinDownstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: -1,0..7 symbols with value -1 meaning “no_overrule”.

RTX Minimum Impulse Noise Protection against REIN Upstream This parameter specifies the minimum impulse noise protection against REIN, for the upstream direction, which will overrule the xdslRtxMinInpReinUpstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. It is expressed in DMT symbols with a subcarrier spacing of 4.3125kHz. Range: -1,0..7 symbols with value -1 meaning “no_overrule”.

RTX Minimum Delay Downstream This parameter specifies the minimum instantaneous delay allowed (only due to the effect of the retransmission) for the downstream direction, which will overrule the xdslRtxMinDelayDownstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. Range: -1,0..63 milliseconds with value -1 meaning “no_overrule”.

TNG 1107-44 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

RTX Minimum Delay Upstream This parameter specifies the minimum instantaneous delay allowed (only due to the effect of the retransmission) for the upstream direction, which will overrule the xdslRtxMinDelayUpstream of the RtxProfile when xdslOverruleRtxModeUpstream is different from rtxForbidden. Range: -1,0..63 milliseconds with value -1 meaning “no_overrule”.

RTX Maximum Delay Downstream This parameter specifies the maximum instantaneous delay allowed (only due to the effect of the retransmission) for the downstream direction, which will overrule the xdslRtxMaxDelayDownstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. Range: -1,2..63 milliseconds with value -1 meaning “no_overrule”.

RTX Maximum Delay Upstream This parameter specifies the maximum instantaneous delay allowed (only due to the effect of the retransmission) for the upstream direction, which will overrule the xdslRtxMaxDelayUpstream of the RtxProfile when xdslOverruleRtxModeUpstream is different from rtxForbidden. Range: -1,2..63 milliseconds with value -1 meaning “no_overrule”.

RTX SHINE Ratio Downstream This parameter specifies the SHINE ratio for the downstream direction, which will overrule the xdslRtxShineRatioDownstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. Range: 0 to 0.100 with increments of 0.001 with value -1 meaning “no_overrule”.

RTX SHINE Ratio Upstream This parameter specifies the SHINE ratio for the upstream direction, which will overrule the xdslRtxShineRatioUpstream of the RtxProfile when xdslOverruleRtxModeUpstream is different from rtxForbidden. Range: 0 to 0.100 with increments of 0.001 with value -1 meaning “no_overrule”.

RTX Leftr Threshold Downstream This parameter specifies the threshold for declaring a near-end 'leftr' defect in the downstream direction, which will overrule the xdslRtxLeftrThresholdDownstream of the RtxProfile when xdslOverruleRtxModeDownstream is different from rtxForbidden. Range: 0.01 to 0.99 with increments of 0.01. The special value 0 means the ETR shall be used as the default threshold for declaring a 'leftr' defect. Value -1 means “no_overrule”.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-45 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

RTX Leftr Threshold Upstream This parameter specifies the threshold for declaring a far-end 'leftr' defect in the upstream direction, which will overrule the xdslRtxLeftrThresholdUpstream of the RtxProfile when xdslOverruleRtxModeUpstream is different from rtxForbidden. Range: 0.01 to 0.99 with increments of 0.01. The special value 0 means the ETR shall be used as the default threshold for declaring a 'leftr' defect. Value -1 means “no_overrule”.

xDSL line status parameters This section lists and describes the line status parameters that can be collected using dual-ended line testing (DELT) on xDSL lines. See the 7302 ISAM | 7330 ISAM FTTN System Description for more information about DELT. Table TNG 1107-11 lists the key line status parameters that can be measured for xDSL lines using the available DELT modes. The applicable parameters for an xDSL line depend on the xDSL mode, the type of xDSL LT unit, the type of xDSL line, and the mode in which DELT is run. If you need additional information, contact Alcatel-Lucent technical support; see www.alcatel-lucent.com/support. Table TNG 1107-11: xDSL line status parameters and diagnostic modes Parameter

ADSL2, ADSL2+,READSL2 ADSL (1)

ISM

CD

CD+

(1)

LD

VDSL2 VDSL

(1)

(1)

ISM

CD

CD+

LD

✓

✓

✓

✓

✓

✓

✓

✓

✓

Operational data parameters (from show xdsl operational-data command) Actual line bit rate

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

✓

(tx-rate/ds, tx-rate/us) Attainable line bit rate (max-tx-rate-ds, max-tx-rate-us) Loop attenuation

(2)

✓

(2)

(2)

✓

(2)

(loop-attenuation-down, loop-attenuation-up) Signal attenuation (sig-attenuation-down, sig-attenuation-up) SNR margin (noise-margin- down, noise-margin-up) Actual aggregate output power (output-power- down, output-power-up) Carrier data parameters (from show xdsl carrier-data command) Carrier load

✓

✓

✓

✓

✓

✓

(load-distribution-down, load-distribution-up) Carrier SNR (snr-up, snr-down)

✓

✓

(1 of 2)

TNG 1107-46 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

Parameter

ADSL2, ADSL2+,READSL2 ADSL

CD

CD+

LD

Quiet line noise (qln-up, qln-down)

(3)

✓

Channel transfer function

(3)

(1)

ISM

(1)

✓

VDSL2 VDSL

CD

CD+

LD

✓

(3)

✓

✓

✓

(3)

✓

✓

(1)

ISM

(1)

(char-func-real) ✓

Complex channel transfer functionn

✓

(char-func- complex) Counter parameter (from show xdsl counters command) Code violation count (cv)

✓

✓

✓

✓

✓

✓

✓

✓

(2 of 2) Notes (1) Reporting of parameters will be determined by the implementation and will not always be identical to those referenced in this table. The table is a guide for what is expected to be reported for most implementations. (2)

Although loop attenuation is available in ISM and CD, it is only measured during initialization and not updated during show time. A reinitialization would therefore be required to update the measurement.

(3)

If the QLN and HLOG are presented in CD, then these values are based on the last reinitialization of the line.

Actual line bit rate This parameter returns the upstream or downstream actual net data rate on the line. Range is:

• •

0 to 65 535 kbit/s for multi-ADSL lines 0 to 262 143 kbit/s for VDSL lines

Attainable line bit rate This parameter returns the upstream or downstream maximum attainable net data rate that the modem can sustain on the line. Range is:

• •

0 to 65 535 kbit/s for multi-ADSL lines 0 to 262 143 kbit/s for VDSL lines

Loop attenuation This parameter returns the upstream or downstream loop attenuation measurement for the line. The loop attenuation is the difference in dB between the power received at one end and the power transmitted at the opposite end over all of the carrier groups during initialization. This parameter is not updated during showtime. The aggregate upstream loop attenuation is calculated by averaging the loop attenuation on the different bands. The bands used for the calculation of the upstream loop attenuation depend on the profile used:

• •

In 12a, the bands used are U0, U1, U2 In 8d, only bands U0 and U1 are used

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-47 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Range is 0.0 to 102.3 dB. A measurement outside this range is represented by the minimum or maximum value of the range.

Signal attenuation This parameter returns the upstream or downstream signal attenuation measurement for the line. Signal attenuation is the difference in dB between the power received at one end of the line and the power transmitted at the other end of the line. Signal attenuation differs from loop attenuation in that the transmit power has changed for the carrier groups and that the total number of carrier groups during showtime is typically less than during initialization. Range is 0.0 to 102.3 dB. A measurement outside this range is represented by the minimum or maximum value of the range.

SNR margin This parameter returns the upstream or downstream signal-to-noise ratio margin for the line. The parameter indicates the current SNR margin relative to the noise power that the transceiver unit can tolerate and still meet the target BER at 0 dB noise margin. The SNR margin is the average of the margins for all loaded carrier groups. The range is −64.0 to 63.0 dB. For an ADSL2 line, an out-of-range value for downstream is represented as 51.2 dB.

Actual aggregate output power This parameter returns the actual upstream or downstream aggregate output (transmit) power measurement for the line, that is, the total output power for the carriers when the modem is in showtime.

Carrier load This parameter returns the upstream or downstream bit loading measurement per carrier group over the specified band. The range is 0 to 15 bit.

Carrier SNR This parameter returns the upstream or downstream measured signal-to-noise ratio per carrier over the specified band. Range is −32.0 to 95.0 dB.

Quiet line noise This parameter returns the upstream or downstream measured quiet line noise per carrier when both transceiver units are silent. On VDSL2 lines, the QLN measurement is returned per carrier group, not per carrier. The carrier group size is determined by the modem.

TNG 1107-48 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1107 — xDSL parameters

The noise to be measured is the actual noise present on the loop. Virtual noise, if any, is not taken into account. Range is −150 to −23 dBm/Hz.

Channel transfer function This parameter returns the upstream or downstream channel transfer function magnitude for the line. In VDSL2, the channel transfer function measurement is given per carrier group, not per carrier. The carrier group size is determined by the modem. The range is −96 to 6 dB. A returned parameter value of “NoMeasurement” indicates either that the carrier group is out of the PSD mask passband or that the attenuation is out of the valid range.

Complex channel transfer function This parameter returns the upstream or downstream channel characteristics function complex values in linear scale per carrier group. In VDSL2, the complex channel transfer function measurement is given per carrier group, not per carrier. The carrier group size is determined by the modem. The range is −32 767 to 32 767. A returned parameter value of “NoMeasurement” indicates either that the carrier group is out of the PSD mask passband or that the attenuation is out of the valid range.

Code violation count This parameter returns the number of code violations for the near end and far end, per channel. If the CRC or DELT is applied over multiple channels, then the count for near end and far end anomalies is incremented for each of the individual channels.

xDSL line operational data retrieval A set of modem operational parameters can be provided by the modem subsystem on request of the xDSL Manager via the xDSL API. The parameters can be divided into a number of subgroups:

• • • •

Modem operational data Identification related information Self test results Carrier related data

The latter group of data is all carrier-related settings like SNR, bit loading, carrier gain, and others that are added for troubleshooting purposes. This carrier data acquisition mode is a special mode that can be enabled by the xDSL Manager via the xDSL API. The full set of data, retrievable by the xDSL Manager via the xDSL API, is shown in Table TNG 1107-12. For each parameter, the table indicates during which states the data should be updated: initialization, showtime and/or loop diagnostics (ADSL2x).

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-49 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

Type

Parameter

Instances

Init

Showtime L0

Showtime L2

Loop diagn.

Table TNG 1107-12: Multi-ADSL Operational Data over XDSL API. Updated during

Operational

Current Operational Mode

Line

X

-

-

X

Line

Operational Mode Capabilities

NE/FE

X

-

-

X

SNR Margin (SNRM)

US/DS

X

X

X

X

Last State Transmitted

US/DS

DS

-

-

US

(2x)

(2x)

Loop Attenuation (LATN)

US/DS

X

-

-

X

Signal Attenuation (SATN)

US/DS

X

X

X

X

Aggregate Output Power (ACTATP)

US/DS

X

X

X

X

Actual PSD

US/DS

X

X

X

X

Attainable Line Bit rate

US/DS

X

X

US

X

Actual Line Bit rate

US/DS

X

X

US

-

US/DS

X

-

-

-

Line RCO

US/DS

X

X

US

-

Operational

Attainable ATM bit rate

US/DS

X

X

US

X

Path

Actual ATM bit rate

US/DS

X

X

US

-

Actual L2 low power ATM bit rate

DS

X

-

X

-

Actual Interleaving Delay

US/DS

X

X

US

-

Actual INP

US/DS

X

X

US

-

System Identification

FE

-

X

X

-

Modem Identification

NE/FE

X

-

-

X

Self Test Results

NE/FE

-

X

X

-

Actual Rate Adaptive

Identification

Self-Test

Mode(6)

(1 of 2)

TNG 1107-50 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Type

Parameter

Instances

Init

Showtime L0

Showtime L2

Loop diagn.

TNG 1107 — xDSL parameters

Updated during

Carrier

Carrier load bi(f)

US/DS

X

X

-

-

Carrier gain gi(f)

US/DS

X

X

-

-

Carrier Spectrum Shaping

US/DS

US (all)

-

-

X

& DS(5)

tssi(f)

(2x) Hlin(f)

US/DS

-

-

-

X

Hlog(f)

US/DS

US (all)

-

-

X

-

-

X

US (all)

-

X

X

X

& DS(5) (2x) QLN(f)

US/DS

US (all) & DS(5) (2x)

SNR(f)

US/DS

US

& DS* (2x) Actual Tx PSD(f)

DS

X

X

(2 of 2) Notes (1) “US”: only US parameter is updated. (2)

“DS”: only DS parameter is updated (via overhead messaging).

(3)

“US&DS”: both US parameter and DS parameter are updated.

(4)

“2x”: only available in ADSL2x operation modes.

(5)

The update of the DS parameter is done by the CPE during initialization only, but the actual value is to be retrieved by the CO once in showtime.

(6)

In case SRA in enabled, value can change in showtime once when first OLR request takes place.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1107-51 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1107 — xDSL parameters

TNG 1107-52 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters Introduction This training document gives more information about the parameters used by the SHDSL modem:

• • • • • •

Supported Supported Supported Supported Supported Supported

span operation configuration parameters unit operation configuration parameters segment termination operation configuration parameters span operational data parameters unit operational data parameters segment termination operational data parameters

Configurable lines For SHDSL only chipset-level bonding is used. There are 6 chips on the LT board each treating 4 physical lines. In fact the lines which you only can configure is calculated via the formula: mxn+1 where:

• •

m is the number of pairs per modem n is from 0 to 24/m - 1

In practice, this means that only the following lines can be configured:

• • •

for 1-pair (2-wire mode): all lines for 2-pairs (4-wire mode): lines 1,3,5,7,9,11,13,15,17,19,21,23 for 4-pairs (8-wire mode): lines 1,5,9,13,17,21

Mixing of different “wire modes” on the same LT is possible as long as the lines are not occupied yet.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

An example: If line 9 is configured as an 8-wire then it is not possible to configure line 11 as a 4-wire, because configuration of line 9 as an 8-wire means that lines 9,10,11 and 12 are occupied.

Supported span operation configuration parameters The SHDSL Modem Subsystem accepts the configuration parameters listed hereunder. Based on the required levels, the required modem reaction on each parameter is:

• •

•

•

In case a parameter is indicated as “optional”, the input value is don’t care, and any value is accepted without having impact on the modem subsystem behavior. In case a parameter is indicated to be required to a certain level (for example, only limited set of defined number of input values), only input values corresponding to the required level are accepted. If the input parameter is not accepted, the modem subsystem raises a failure indication to the xDSL Manager indicating “Configuration Error” In case extra consistency checks need to be performed on a parameter or between parameters and the configuration should be rejected, 'rejection' always means that the modem subsystem raises a failure indication to the SHDSL Manager indicating “Configuration Error”, rather that a returned error of the considered SHDSL API call. An SHDSL API configuration request is replied with an error only when the call is done in a wrong administrative state.

The SHDSLx Modem Subsystem allows that the configuration can be independently set on individual line basis. M-pair (1 < M < 4) stands for a multiple-pair operation over SHDSL span for some applications having higher data rate requirements for end users. Four-wire mode is identical to M-pair mode with M = 2, except for the method of assigning ordinal numbers to the wire pairs.

•

•

• • •

TNG 1108-2

Data Rates: M-pair operational mode is capable of supporting user (payload) data rates from M × 192 kbit/s to M × 2.312 Mbit/s in increments of M × 8 kbit/s, where 1 < M < 4. Note that optional extensions described in Annex F/G allow user data rates up to M × 5696 kbit/s. Four-wire mode is identical to M-pair mode with M = 2, except for the method of assigning ordinal numbers to the wire pairs. Embedded Operations Channel (EOC): For optional M-pair operation, each EOC message is sent in parallel such that redundant and identical messages are sent over all M loops. In M-pair mode, eoc01 - eoc20 on Pair 1 carries the primary EOC data. The corresponding Pair 2 to Pair M eoc bits are duplicates of the Pair 1 eoc bits. SHDSL Transceiver Unit at the Remote side (STU-R) Power Status: In M-pair mode, ps on Pair 1 carries the primary power status indication. The ps bit on all other pairs are duplicates of the Pair 1 ps bit. Power Feeding/Wetting Current: In the optional M-pair mode, the requirements for remote power feeding or wetting current for each of the M pairs are identical to the requirements for a single pair. Activation Procedure: In devices supporting the optional M-pair mode, the core activation procedure is considered as an independent procedure for each pair. Such devices are capable of detecting the completion of activation for all pairs and upon completion will initiate the transmission of user data over all pairs.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

• •

Line Probe: In the optional M-pair mode, STU-R remote probe signal Pri and STU-C central probe signal Pci are sent in parallel on all wire pairs. G.994.1: In the optional 4-wire mode, Pair 1 and Pair 2 are determined during the preactivation sequence procedures defined in Annex B/G.994.1 entitled, “Operation over multiple wire pairs”. Pair 1 is defined as the pair on which the final G.994.1 transaction is conducted. In the optional M-pair mode, the G.994.1 exchange follows the defined procedures for multi pair operation.

Operating Modes Table TNG 1108-1 describes the operating modes parameter. Table TNG 1108-1: Operating Modes Name

Operating Modes

Description

Specifies which operational protocol/standard are applicable for a span:

• • • •

(1) ATM-Native (2) ATM-IMA (ATM Forum) (3) PTM-64/65B (EFM) (4) PTM-HDLC

Operational modes not supported by the STU-C shall be ignored (that is, they are not considered selected). Multiple mode selection is not allowed. The operational mode is selected by the SHDSL Manager before startup the line, each line’s operational mode are independent to the other lines, with exception of M-pair mode which requires all lines belong to a M-pair configuration in the same operational mode. Operational modes are not exchanged by G.hs. In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the same value, which would be the same for all links in the IMA group. For this reason, the IMA mode selection and Group assignment needs to be made at the same time as the initial provisioning. IMA is not supported over M-pair links. Instances

Span

Values

shdsl_native_mode shdsl_ima_mode shdsl_efm_mode

Granularity & Unit

-

Spectral Profile Table TNG 1108-2 describes the spectral profile parameter. Table TNG 1108-2: Spectral Profile Name

SHDSL Spectral Profile

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Description

Specifies the spectral mode in which this SHDSL span is to be configured with. One options is supported:

•

SymmetricProfile

Examples: Annex A/2-Wire: 768 kb/s & 1536 kb/s Annex A/4-Wire: 1536 kb/s & 3072 kb/s Annex B/2-Wire: 2048 kb/s & 2304 kb/s Annex B/4-Wire: 4096 kb/s & 4608 kb/s Instances

Span

Values

symmetricProfile

Granularity & Unit

-

(2 of 2)

Wire Mode Table TNG 1108-2 describes the wire mode parameter. Table TNG 1108-3: Wire Mode Name

Wire Mode

Description

Specifies whether 2-Wire or 4-Wire or 6-Wire or 8-Wire operation is in place. The supported wire mode depend on the actual lines of modem ASIC. IMA is not supported over M-pair links. Note: Multi pairs EFM (PTM-64/65B) is EFM bonding.

Instances

Span

Values

shdsl_two_wire shdsl_four_wire shdsl_six_wire shdsl_eight_wire

Granularity & Unit

-

Support Management from STU-R Table TNG 1108-3 describes the support management from STU-R parameter. Table TNG 1108-4: Support Management from STU-R Name

Managed from STU-R

Description

Specifies whether the STU-R initiated management flow is enabled/disabled by the STU-C.

Instances

Span

Values

disabled enabled

Granularity & Unit

TNG 1108-4

-

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Regional Setting Table TNG 1108-4 describes the regional setting parameter. Table TNG 1108-5: Regional Setting Name

Regional Setting

Description

Specifies the regional setting for the SHDSL line per the ITU-T G.992.1 Annexes (Annex A/F and Annex B/G).

• •

Region 1 - G.991.2 Annex A/F Region 2 - G.991.2 Annex B/G

Only a single setting (region 1 or region 2) can be provisioned. In Asymmetric Spectral Profile Mode, the regional setting cannot be modified. The modem rejects the configuration and raises the “Configuration error” activation failure in the following scenarios:

• •

No region is selected (or no STU-C supported region is selected) Region 1 and region 2 are selected together

Instances

Span

Values

BitMap: Bit

Granularity & Unit

Setting

---

---------

0

Region 1

1

Region 2

-

Minimum and Maximum Data Rate Table TNG 1108-6 and Table TNG 1108-7 describe the minimum and maximum requested data rate parameters. Table TNG 1108-6: Minimum Requested Data Rate Name

Minimum Requested Data Rate

Description

Defines the minimum requested transport payload bitrate which shall be set up and which shall be maintained during showtime by the STU. When line probe is enabled, the SHDSL line is probed for levels between this rate and the maximum requested data rate. The Line will not be activated at a lower rate. Only ATM/PTM-64/65B(EFM) mapping is supported, this limits the resulting data rates to multiples of 64k (192 to 5696) in TwoWire mode; and to multiples of 128k (384 to 11,392) in FourWire mode, to multiples of 192k (576 to 17,088) in SixWire mode, to multiples of 256k (768 to 22,784) in EightWire mode. In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the same value which would be the same for all links in the IMA group. This result in a constraint to use exact 64 kb/s multiples in provisioning.

Instances

Span

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Values

2-wire: 192 to 5696 in multiple of 64, and 2312 4-wire: 384 to 11.392 in multiple of 128 6-wire: 576 to 17.088 in multiple of 192 8-wire: 768 to 22.784 in multiple of 384

Granularity & Unit

64 kbit/s x M (pair number)

(2 of 2)

Table TNG 1108-7: Maximum Bitrate Name

Maximum Bitrate

Description

Specifies the maximum requested SHDSL data rate which can range from 192 to 5696 kb/s in Two Wire mode, plus the rate of 2312; and from 384 to 11.392 kb/s in FourWire mode; from 576 to 17,088 kb/s in SixWire mode; from 768 to 22.784 kb/s in EightWire mode The SHDSL line is probed for levels between this rate and the minimum requested data rate. The Line will not be activated at a higher rate. Only the ATM/PTM-64/65B(EFM) mapping is supported, this limits the resulting data rates to multiples of 64k (192 to 5696) in TwoWire mode; and to multiples of 128k (384 to 11.392) in FourWire mode, to multiples of 192k (576 to 17.088) in SixWire mode, to multiples of 256k (768 to 22.784) in EightWire mode. In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the same value which would be the same for all links in the IMA group. This result in a constraint to use exact 64 kb/s multiples in provisioning. This parameter is relevant only in line probe enabled mode. When line probe is not “enabled”, the Maximum Bitrate parameter is ignored. As the data rate granularity is in multiple of 64 kbps, the following rounding scheme for Minimum and Maximum Bitrates is implemented:

• •

The Minimum Bitrate is rounded up and the Maximum Bitrate is rounded down according to the data rate granularity when for the corresponding direction Maximum Bitrate is larger than or equal to Minimum Bitrate after rounding. Otherwise, both bitrates are rounded up and Minimum Bitrate is equal to Maximum Bitrate after rounding up.

Instances

Span

Values

2-wire: 192 to 5696 in multiple of 64, and 2312 4-wire: 384 to 11.392 in multiple of 128 6-wire: 576 to 17.088 in multiple of 192 8-wire: 768 to 22.784 in multiple of 384

Granularity & Unit

64 kbit/s x M (pair number)

Note — To set 2312 kbit/s bandwidth (in 2-wire mode), the minimum and maximum rate has to be set to the same value.

Worst Case Downstream Target Noise Margin Table TNG 1108-8 describes the worst case downstream target noise margin parameter.

TNG 1108-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters Table TNG 1108-8: Worst Case Downstream Target Noise Margin Name

Worst Case Downstream Target Noise Margin

Description

Specifies the Target Margin in the Downstream direction, relative to the reference Worst Case, to be used during handshake and line-probe procedure in gauging a Bit Error Rate (BER) better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated Signal-to-Noise Ratio (SNR) associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

Instances

Span

Values

-11, 0 to 10

Granularity & Unit

1 dB

Current Case Downstream Target Noise Margin Table TNG 1108-9 describes the current case downstream target noise margin parameter. Table TNG 1108-9: Current Case Downstream Target Noise Margin Name

Current Case Downstream Target Noise Margin

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-7 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Description

Specifies the Target Margin in the Downstream direction, relative to the Current noise conditions, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

Instances

Span

Values

-11, 0 to 10

Granularity & Unit

1 dB

(2 of 2)

Worst Case Upstream Target Noise Margin Table TNG 1108-10 describes the worst case upstream target noise margin parameter. Table TNG 1108-10: Worst Case Upstream Target Noise Margin Name

Worst Case Upstream Target Noise Margin

(1 of 2)

TNG 1108-8

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Description

Specifies the Target Margin in the Upstream direction, relative to the reference Worst Case, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

Instances

Span

Values

-11, 0 to 10

Granularity & Unit

1 dB

(2 of 2)

Current Case Upstream Target Noise Margin Table TNG 1108-11 describes the current case upstream target noise margin parameter. Table TNG 1108-11: Current Case Upstream Target Noise Margin Name

Current Case Upstream Target Noise Margin

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-9 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Description

Specifies the Target Margin in the Upstream direction, relative to the Current noise conditions, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

Instances

Span

Values

-11, 0 to 10

Granularity & Unit

1 dB

(2 of 2)

Line Probe Enable Table TNG 1108-12 describes the line probe enable parameter. Table TNG 1108-12: Line Probe Enable Name

Line Probe Enable

Description

Specifies support for Line Probe (rate adaptation) of the units in a SHDSL line. When Line Probe is enabled, the system performs Line Probing to find the best possible rate. If Line probe is disabled, the rate adaptation phase is skipped to shorten set up time. When the 4 Target Margins are all set to -11, this value can only be configured to Disable. When this value is set to Disable, all WC and CC Target Margins which are not equal to -11 shall be ignored.

Instances

Span

(1 of 2)

TNG 1108-10 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Values

disabled enabled

Granularity & Unit (2 of 2)

TC-PAM modulation selection Table TNG 1108-13 describes the TC-PAM modulation selection parameter. Table TNG 1108-13: TC-PAM modulation selection Name

TC-PAM modulation selection

Description

Specifies the TC-PAM modulation selection for the span. In current implementation this configuration only applies to the first segment from STU-C.

Instances

Span

Values

auto tc-pam32 tc-pam16

Granularity & Unit

-

EFM handshake selection Table TNG 1108-14 describes the EFM handshake selection parameter. Table TNG 1108-14: EFM handshake selection Name

EFM handshake selection

Description

Specifies the handshake mode selection for the span

Instances

Span

Values

auto ieee itu not-applicable

Granularity & Unit

-

Cross-talk Cancellation Table TNG 1108-15 describes the Cross-Talk Cancellation (CTC) parameter.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-11 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters Table TNG 1108-15: Cross-Talk Cancellation Name

Cross-Talk Cancellation

Description

Specifies whether Cross-Talk Cancellation is enabled / disabled on the span.

Instances

Span

Values

disabled (default) enabled

Granularity & Unit

-

Bonding Rate Control Mode Table TNG 1108-16 describes the Bonding Rate Control Mode parameter. Table TNG 1108-16: Bonding Rate Control Mode Name

Bonding Rate Control Mode

Description

Specifies the bonding rate control mode on the span. If the bonding rate control mode isspan, the Minimum Requested Data Rate and Maximum Requested Data Rate will take effect. If the bonding rate control mode islink, the link level rate control and TC-PAM selection data will take effect. If the Wire Mode is twoWire or if the Operational Mode is not EFM, then the bonding rate control mode cannot be link.

Instances

Span

Values

span (default) link

Granularity & Unit

-

Minimum Requested Data Link 1 Table TNG 1108-17 describes the Minimum Requested Data Link 1 parameter. Table TNG 1108-17: Minimum Requested Data Link 1 Name

Minimum Requested Data Link 1

Description

Specifies the minimum requested data rate of link 1. It only take effect when the Bonding Rate Control Mode is link. The SHDSL line is probed for levels between this rate and the maximum requested data rate. The line will not be activated at a lower rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

(1 of 2)

TNG 1108-12 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Default

192 kb/s

Granularity & Unit

multiples of 64k

(2 of 2)

Maximum Requested Data Link 1 Table TNG 1108-18 describes the Maximum Requested Data Link 1 parameter. Table TNG 1108-18: Maximum Requested Data Link 1 Name

Maximum Requested Data Link 1

Description

Specifies the maximum requested data rate of link 1. It only take effect when the Bonding Rate Control Mode is link. The SHDSL line is probed for levels between the minimum requested data rate and this rate. The line will not be activated at a higher rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

5696 kb/s

Granularity & Unit

multiples of 64k

Minimum Requested Data Link 2 Table TNG 1108-19 describes the Minimum Requested Data Link 2 parameter. Table TNG 1108-19: Minimum Requested Data Link 2 Name

Minimum Requested Data Link 2

Description

Specifies the minimum requested data rate of link 2. It only take effect when the Bonding Rate Control Mode is link. The SHDSL line is probed for levels between this rate and the maximum requested data rate. The line will not be activated at a lower rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

192 kb/s

Granularity & Unit

multiples of 64k

Maximum Requested Data Link 2 Table TNG 1108-20 describes the Maximum Requested Data Link 2 parameter.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-13 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters Table TNG 1108-20: Maximum Requested Data Link 2 Name

Maximum Requested Data Link 2

Description

Specifies the maximum requested data rate of link 2. It only take effect when the Bonding Rate Control Mode is link. The SHDSL line is probed for levels between the minimum requested data rate and this rate. The line will not be activated at a higher rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

5696 kb/s

Granularity & Unit

multiples of 64k

Minimum Requested Data Link 3 Table TNG 1108-21 describes the Minimum Requested Data Link 3 parameter. Table TNG 1108-21: Minimum Requested Data Link 3 Name

Minimum Requested Data Link 3

Description

Specifies the minimum requested data rate of link 3. It only take effect when the Bonding Rate Control Mode is link and the Wire Mode is sixWire or eightWire. The SHDSL line is probed for levels between this rate and the maximum requested data rate. The line will not be activated at a lower rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

192 kb/s

Granularity & Unit

multiples of 64k

Maximum Requested Data Link 3 Table TNG 1108-22 describes the Maximum Requested Data Link 3 parameter. Table TNG 1108-22: Maximum Requested Data Link 3 Name

Maximum Requested Data Link 3

(1 of 2)

TNG 1108-14 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Description

Specifies the maximum requested data rate of link 3. It only take effect when the Bonding Rate Control Mode is link and the Wire Mode is sixWire or eightWire. The SHDSL line is probed for levels between the minimum requested data rate and this rate. The line will not be activated at a higher rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

5696 kb/s

Granularity & Unit

multiples of 64k

(2 of 2)

Minimum Requested Data Link 4 Table TNG 1108-23 describes the Minimum Requested Data Link 4 parameter. Table TNG 1108-23: Minimum Requested Data Link 4 Name

Minimum Requested Data Link 4

Description

Specifies the minimum requested data rate of link 4. It only take effect when the Bonding Rate Control Mode is link and the Wire Mode is eightWire. The SHDSL line is probed for levels between this rate and the maximum requested data rate. The line will not be activated at a lower rate.

Instances Values

Span autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

192 kb/s

Granularity & Unit

multiples of 64k

Maximum Requested Data Link 4 Table TNG 1108-24 describes the Maximum Requested Data Link 4 parameter. Table TNG 1108-24: Maximum Requested Data Link 4 Name

Maximum Requested Data Link 4

Description

Specifies the maximum requested data rate of link 4. It only take effect when the Bonding Rate Control Mode is link and the Wire Mode is eightWire. The SHDSL line is probed for levels between the minimum requested data rate and this rate. The line will not be activated at a higher rate.

Instances

Span

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-15 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Values

autoSelect TCPAM: 192 kb/s to 5696 kb/s tcPAM16 is selected: 192 kb/s to 3840 kb/s tcPAM32 is selected: 768 kb/s to 5696 kb/s

Default

5696 kb/s

Granularity & Unit

multiples of 64k

(2 of 2)

TC-PAM Selection Link 1 Table TNG 1108-25 describes the TC-PAM Selection Link 1 parameter. Table TNG 1108-25: TC-PAM Selection Link 1 Name

TC-PAM Selection Link 1

Description

Specifies the TC-PAM modulation selection for the link 1. If the Bonding Rate Control Mode is span, this parameter has no effect.

Instances

Span

Values

autoSelect (default) tcPAM32 tcPAM16

Granularity & Unit

-

TC-PAM Selection Link 2 Table TNG 1108-26 describes the TC-PAM Selection Link 2 parameter. Table TNG 1108-26: TC-PAM Selection Link 2 Name

TC-PAM Selection Link 2

Description

Specifies the TC-PAM modulation selection for the link 2. If the Bonding Rate Control Mode is span, this parameter has no effect.

Instances

Span

Values

autoSelect (default) tcPAM32 tcPAM16

Granularity & Unit

-

TC-PAM Selection Link 3 Table TNG 1108-27 describes the TC-PAM Selection Link 3 parameter.

TNG 1108-16 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters Table TNG 1108-27: TC-PAM Selection Link 3 Name

TC-PAM Selection Link 3

Description

Specifies the TC-PAM modulation selection for the link 3. If the Bonding Rate Control Mode is span, this parameter has no effect.

Instances

Span

Values

autoSelect (default) tcPAM32 tcPAM16

Granularity & Unit

-

TC-PAM Selection Link 4 Table TNG 1108-28 describes the TC-PAM Selection Link 4 parameter. Table TNG 1108-28: TC-PAM Selection Link 4 Name

TC-PAM Selection Link 4

Description

Specifies the TC-PAM modulation selection for the link 4. If the Bonding Rate Control Mode is span, this parameter has no effect.

Instances

Span

Values

autoSelect (default) tcPAM32 tcPAM16

Granularity & Unit

-

Supported unit operation configuration parameters

Loop Attenuation Threshold Table TNG 1108-29 describes the loop attenuation threshold parameter. Table TNG 1108-29: Loop Attenuation Threshold Name

Loop Attenuation Threshold

Description

Specifies the Loop Attenuation Threshold Value in dBs, for generated associated alarms. A value of 0 disables alarm generation.

Instances

Unit

Values

0-127

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-17 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Granularity & Unit

1 dB

(2 of 2)

SNR Margin Threshold Table TNG 1108-30 describes the SNR margin threshold parameter. Table TNG 1108-30: SNR Margin Threshold Name

SNR Margin Threshold

Description

Specifies the SNR Margin Threshold Value in dBs, for generated associated alarms. A value of 0 disables alarm generation.

Instances

Unit

Values

0-15

Granularity & Unit

1 dB

Loopback Timeout Table TNG 1108-31 describes the loopback timeout parameter. Table TNG 1108-31: Loopback Timeout Name Description

Loopback Timeout Specifies the Loopback Timeout duration in minutes. A value of 0 disables timeout.

Instances

Unit

Values

0-4095

Granularity & Unit

1minute

Supported segment termination operation configuration parameters

Loopback Configuration Table TNG 1108-32 describes the loopback configuration parameter. Table TNG 1108-32: Loopback Configuration Name

Loopback Configuration

(1 of 2)

TNG 1108-18 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Description

Specifies the loopbacks for the associated side of an SHDSL unit. Only Network Side loopbacks are supported for SRU and STU-R units Only customer-side loopbacks are supported for STU-C. Note: In multi-pair mode the loopbacks cannot be applied to individual pair separately, that is, all the pairs are looped-back and released at the same time.

Instances

Segment Termination

Values

NoLoopback NormalLoopback

Granularity & Unit

-

(2 of 2)

Power Backoff Mode Table TNG 1108-33 describes the power backoff mode parameter. Table TNG 1108-33: Power Backoff Mode Name

Power Backoff Mode

Description

Specifies the Power Backoff rule at the associated Segment Termination.

Instances

Segment Termination

Values

Default Selected Disabled

Granularity & Unit

-

Soft Restart Table TNG 1108-34 describes the soft restart parameter. Table TNG 1108-34: Soft Restart Name Description

Soft Restart Initiate a Soft Restart message towards the relevant segment termination. When the value of this object is set from 0 to 1, a Soft Restart EOC message is initiated. After 5 minutes the value of the object is automatically set back to 0.

Instances

Segment Termination

Values

0 (Normal Operation) 1 (Soft Restart)

Granularity & Unit

-

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-19 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Supported span operational data parameters

Span State Table TNG 1108-35 describes the span state parameter. Table TNG 1108-35: Span State Name

Span State

Description

Indicates the overall state of this SHDSL span

Instances

Span

Values

unknown unequipped faulty idle startup active testing fwdownloading

Granularity & Unit

-

Detected Units Table TNG 1108-36 describes the detected units parameter. Table TNG 1108-36: Detected Units Name

Detected Units

Description

Indicates the units that have been detected on this SHDSL span, bits are set(1) for detected units.

Instances

Span

Values

Bitmap: Bit

Unit

---

------

0

STU-C

1

STU-R

2

SRU-1

3

SRU-2

4

SRU-3

5

SRU-4

6

SRU-5

7

SRU-6

8

SRU-7

9

SRU-8

(1 of 2)

TNG 1108-20 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Granularity & Unit

-

(2 of 2)

Inventoried Units Table TNG 1108-37 describes the detected units parameter. Table TNG 1108-37: Inventoried Units Name

Inventoried Units

Description

Indicates the units in the SHDSL span whose inventory information is available, bits are set(1) for units whose inventory is available.

Instances

Span

Values

Bitmap:

Granularity & Unit

Bit

Unit

---

------

0

STU-C

1

STU-R

2

SRU-1

3

SRU-2

4

SRU-3

5

SRU-4

6

SRU-5

7

SRU-6

8

SRU-7

9

SRU-8

-

Configured Units Table TNG 1108-38 describes the configured units parameter. Table TNG 1108-38: Configured Units Name

Configured Units

Description

Indicates the units in the SHDSL span which have been successfully configured, bits are set (1) for units which have been successfully configured.

Instances

Span

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-21 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Values

Granularity & Unit

Bitmap: Bit

Unit

---

------

0

STU-C

1

STU-R

2

SRU-1

3

SRU-2

4

SRU-3

5

SRU-4

6

SRU-5

7

SRU-6

8

SRU-7

9

SRU-8

-

(2 of 2)

Span Status Table TNG 1108-39 describes the span status parameter. Table TNG 1108-39: Span Status Name Description

Span Status Indicates the overall status of this SHDSL span. Status conditions are associated with individual SHDSL segments. This object represents collective span status by logically-OR-ing individual segment status bits.

Instances

Span

Values

Bitmap: Bit

Condition

---

---------

0

No Error

1

LOSW

2

Loop Attenuation Alarm

3

SNR Margin Alarm

4

DC Continuity Fault

5

Device Fault

6

Configuration Error

7

Loopback(s) Active

8

Non-Conform to STU-C Enable/Disable of STU-R Initiated Management Flow

9

ATM LCD/PTM LPD

10 Loss of Power 11 ATM NCD/PTM NPD 12 Granularity & Unit

Activation failure

-

TNG 1108-22 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Wire Pair Assignment Table TNG 1108-40 describes the wire pair assignment parameter. Table TNG 1108-40: Wire Pair Assignment Name

Wire Pair Assignment

Description

Provides the correlation between the actual ports and their dynamic designation as fistPair and secondPair and thirdPair and fourthPair (if M>2 is supported) as a result of the pre-activation sequence in a modem ASIC. (firstPair is defined as the pair on which the final G.994.1 transaction is conducted) For 4-wire mode:

• •

00000100b: if the first port is the first pair, second port is the second pair 00000001b: if the second port is the first pair

6-wire mode examples:

• • •

00100100b: if the first port is the first pair, second port is the second pair, third port is the third pair 00010010b: if the second port is the first pair, third port is the second pair 00001001b: if the third port is the first pair, first port is the second pair

8-wire mode examples:

• • • •

11100100b: if the first port is the first pair, second port is the second pair, third port is the third pair, fourth port is the fourth pair 10010011b: if the second port is the first pair 01001110b: if the third port is the first pair 00111001b: if the fourth port is the first pair

Instances

Span

Values

Bitmap: Bit

Condition

---

---------

1,0 wirePair of the 1st modem ASIC port for 6/8-wire, 1st/3rd numbered port for 4-wire 3,2 wirePair of the 2nd modem ASIC port for 6/8-wire, 2nd/4th numbered port for 4-wire 5,4

wirePair of the 3rd modem ASIC port for 6/8-wire, set to 0 for 4-wire

7,6

wirePair of the 4th modem ASIC port for 8-wire, set to 0 for 4/6-wire

wirePair ----------

Granularity & Unit

value --------

1stPair

00

2ndPair

01

3rdPair

10

4thPair

11

-

Supported unit operational data parameters Unit Operational Data only exist for those units that are configured as indicated by the shdslSpanConfiguredUnits, and which support SHDSL EOC Performance Status messages defined in ITU-T G.991.2[1].

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-23 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Unit DC Powering Table TNG 1108-41 describes the unit DC powering parameter. Table TNG 1108-41: Unit DC Powering Name

Unit DC Powering

Description

Indicates whether this unit is powered locally, or derives power from the SHDSL span.

Instances

Unit

Values

LocalPowered spanPowered

Granularity & Unit

-

Supported segment termination operational data parameters Segment Termination Operational Data only exist for those units that are configured as indicated by the shdslSpanConfiguredUnits, and which support SHDSL EOC Performance Status messages defined in ITU-T G.991.2[1].

Segment Termination Status Table TNG 1108-42 describes the segment termination status parameter. Table TNG 1108-42: Segment Termination Status Name

Segment Termination Status

Description

Indicates any exception conditions active at this SHDSL segment termination

Instances

Segment Termination

Values

Bitmap: Bit

Condition

---

---------

0

No Error

1

LOSW

2

Loop Attenuation Alarm

3

SNR Margin Alarm

4

DC Continuity Fault

5

Device Fault

6

Configuration Error

7

Loopback(s) Active

8

Non-Conform to STU-C Enable/Disable of STU-R Initiated Management Flow

9

ATM LCD/PTM LPD

10 11 12

Loss of Power ATM NCD/PTM NPD Activation failure

(1 of 2)

TNG 1108-24 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters

Granularity & Unit

-

(2 of 2)

Loopback State Table TNG 1108-43 describes the loopback state parameter. Table TNG 1108-43: Loopback State Name Description

Loopback State Indicates any loopback active at this SHDSL segment termination. In M-pair mode, the loopbacks can only be set-up and torn-down simultaneously on all pairs.

Instances

Segment Termination

Values

noLoopback normalLoopback specialLoopback

Granularity & Unit

-

SNR Margin Table TNG 1108-44 describes the SNR margin parameter. Table TNG 1108-44: SNR Margin Name

SNR Margin

Description

Indicates the currently measured SNR Margin in dB at this SHDSL segment termination. A value of 127 indicates that this information is unavailable.

Instances

Segment Termination

Values

-128 to 127 dB

Granularity & Unit

1 dB

Accuracy

1 dB

Loop Attenuation Table TNG 1108-45 describes the loop attenuation parameter. Table TNG 1108-45: Loop Attenuation Name

Loop Attenuation

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-25 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Description

Indicates the currently measured Loop Attenuation in dB at this SHDSL segment termination. A value of -128 indicates that this information is unavailable.

Instances

Segment Termination

Values

-128 to 127 dB

Granularity & Unit

1 dB

Accuracy

1 dB

(2 of 2)

Power Backoff Level Table TNG 1108-46 describes the power backoff level parameter. Table TNG 1108-46: Power Backoff Level Name

Power Backoff Level

Description

Indicates the current Power Backoff value in dB at this SHDSL segment termination.

Instances

Segment Termination

Values

0 to 31 dB

Granularity & Unit

1 dB

Accuracy

1 dB

Tip Ring Reversal Table TNG 1108-47 describes the tip ring reversal parameter. Table TNG 1108-47: Tip Ring Reversal Name

Tip Ring Reversal

Description

Indicates the current state of the Tip/Ring pair at this SHDSL segment termination.

Instances

Segment Termination

Values

normal reversed

Granularity & Unit

-

Accuracy

-

Power Backoff Status Table TNG 1108-48 describes the power backoff status parameter.

TNG 1108-26 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1108 — SHDSL parameters Table TNG 1108-48: Power Backoff Status Name Description

Power Backoff Status Indicates the Power Backoff status at this SHDSL segment termination. This value indicates the mode that will be selected at the next reset.

Instances

Segment Termination

Values

default selected disabled

Granularity & Unit

-

Accuracy

-

Current data rate Table TNG 1108-49 describes the Current data rate parameter. Table TNG 1108-49: Current data rate Name

Current data rate

Description

Specifies the current SHDSL data rate which can range from 192 to 5696 kb/s in 64 kb/s increments for 2-Wire operation and from Mx192 to Mx5696 kb/s in Mx64 kb/s increments for multi-pair(pair number: M) operation. The rates are restricted to multiples of 64 kb/s for ATM/EFM mapping mode. The current data rate is set automatically, based on the Minimum & Maximum Requested Data Rates and the discovered capability of the line (that is, this object reflects the best achievable rate within the limits imposed by the manager. Only the ATM mapping mode is supported. Therefore the data rate will be a multiple of 64 kb/s. In addition the special rate of 2312 is supported in 2-wire mode While the SHDSL line is not activated, the value of this object is 0.

Instances

Segment Termination

Values

range: [0, 192..5696]

Granularity & Unit

64 kb/s for 2-wire mode. Mx192kb/s for M-wire mode

Accuracy

-

Activation state Table TNG 1108-50 describes the Activation state parameter. Table TNG 1108-50: Activation state Name

Activation state

Description

Indicates the state of this segment termination

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1108-27 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1108 — SHDSL parameters

Instances Values

Segment Termination active idle unknown initialization exception testing fwdownloading

Granularity & Unit

-

(2 of 2)

Activation failure Table TNG 1108-51 describes the Activation failure parameter. Table TNG 1108-51: Activation failure Name

Activation failure

Description

Indicates the coded reason of activation failure. Activation failure code shall be an unsigned integer value comprised of 4 octet values from MSB to LSB. Detailed code meaning refer to 3HH-03653-AAAA-PBZZA:SHDSL Proxy API Definition. Only supported for STU-C customer side.

Instances

Segment Termination

Values

Unsigned integer.

Granularity & Unit

-

TNG 1108-28 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1115 — Slot numbering schemes Purpose This document describes the numbering schemes that are supported by the NE with regard to the slot positions in the subracks. To be able to align the different numbering schemes, an option is provided to the CLI operator to switch from one numbering scheme to the other; see DLP 2101.

Terminology The different slot position schemes are:

• •

• •

type-based: Type-based numbering (flat numbering per slot type from left to right starting with 1, TL1 format.) position-based: This slot position scheme is a flat-numbering scheme from left to right (within the subrack when the boards are positioned vertically) or from bottom to top (within the subrack when the boards are placed horizontally) starting with 1. This is in fact equal to the physical position numbering from left to right or from bottom to top starting with 1. legacy-num: This numbering is identical to position-based except for some very specific configurations where previously a kind of type-based numbering was used (that is, a fixed relation between CLI slot number and equipment log slot number). log-slot-num: Logical slot ID (that is, the numbering method defined for equipment identification in the MIB.)

Note — Regardless of the numbering scheme used, the output is always displayed in the “new” addressing format (which is lt://, for example lt:1/1/1) as opposed to the original addressing format (which was //, for example 1/1/1).

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1115-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1115 — Slot numbering schemes

Translation table • • •

lt x: line board x lp x: applique x silk: what is printed on the subrack itself

7302 ISAM FD equipment For FD equipment, legacy-based numbering is equal to position-based numbering. Table TNG 1115-1 shows the translation table for the 7302 ISAM FD subrack (NFXS-A). Table TNG 1115-1: Translation table for NFXS-A Silk

Type based

Legacy based

Position based

Logical slot ID

lt1

lt1

1

1

3

lt2

lt2

2

2

4

lt3

lt3

3

3

5

lt4

lt4

4

4

6

lt5

lt5

5

5

7

lt6

lt6

6

6

8

lt7

lt7

7

7

9

lt8

lt8

8

8

10

nta

nta

9

9

1

iont/lt17

iont/lt17

10

10

0/19

ntb/lt18

ntb/lt18

11

11

2/20

lt9

lt9

12

12

11

lt10

lt10

13

13

12

lt11

lt11

14

14

13

lt12

lt12

15

15

14

lt13

lt13

16

16

15

lt14

lt14

17

17

16

lt15

lt15

18

18

17

lt16

lt16

19

19

18

7330 ISAM FTTN FD equipment For FD equipment, legacy-based numbering is equal to position-based numbering. Table TNG 1115-2 shows the translation table for the 7330 ISAM FTTN FD subrack (NFXS-B).

TNG 1115-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1115 — Slot numbering schemes Table TNG 1115-2: Translation table for NFXS-B Silk

Type based

Legacy based

Position based

Logical slot ID

nta

nta

1

1

1

iont/lt9

iont/lt9

2

2

0/11

ntb/lt10

ntb/lt10

3

3

2/12

lt1

lt1

4

4

3

lt2

lt2

5

5

4

lt3

lt3

6

6

5

lt4

lt4

7

7

6

lt5

lt5

8

8

7

lt6

lt6

9

9

8

lt7

lt7

10

10

9

lt8

lt8

11

11

10

NFXR-A equipment Table TNG 1115-3 shows the translation table for the NFXR-A. Table TNG 1115-3: Translation table for NFXR-A equipment Silk

Type based

Legacy based

Position based

Logical slot ID

1 (LT1)

lt1

-

1

3

2 (LT2)

lt2

-

2

4

3 (CTRL)

ctrl

-

3

1

NFXR-B equipment Table TNG 1115-4 shows the translation table for the NFXR-B. Table TNG 1115-4: Translation table for NFXR-B equipment Silk

Type based

Legacy based

Position based

Logical slot ID

1 (LT1)

lt1

-

1

3

3 (CTRL)

ctrl1

-

3

1

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1115-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1115 — Slot numbering schemes

TNG 1115-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1116 — Link Related Ethernet OAM (EFM OAM) Introduction As Ethernet moves from being an enterprise-centric technology into a WAN and access technology, carrier-class capabilities need to be brought to Ethernet designs. One of the most important characteristics of a carrier-class technology is the implementation of operational, administration and maintenance (OAM) capabilities. Link Related Ethernet OAM (IEEE802.3 clause 57 standard) provides network operators with the ability to monitor the health of the network and quickly determine the location of failing links or fault conditions. It allows remote side information to be retrieved for a link connected with a node for which SNMP may not be available as default. EFM OAM does not include functions such as station management, bandwidth allocation or provisioning functions, which are considered outside the scope of this standard. Figure TNG 1116-1 shows a typical Link Related Ethernet OAM configuration. Figure TNG 1116-1: Typical Link Related Ethernet OAM Configuration 7302 ISAM or 7330 FTTN CPE IEEE802.3 clause 57 (Link Ethernet OAM)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1116-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1116 — Link Related Ethernet OAM (EFM OAM)

General Description EFM OAM information is conveyed in Slow Protocol frames called OAM Protocol Data Units (PDUs). EFM OAM PDUs contain the appropriate control and status information used to monitor, test and troubleshoot OAM-enabled links. EFM OAM PDUs traverse a single link, being passed between peer OAM entities, and as such, are not forwarded by MAC clients (for example, bridges or switches). Link Related Ethernet OAM provides a mechanism to detect the presence of an OAM sub layer at the remote DTE called Discovery. During the Discovery process, the NE and the CPE exchange their respective configuration information and evaluate the remote information to determine compatibility. The decision for accepting remote configuration is based on the remote system's OAM mode, version, maximum PDU size, Parser Action, Multiplexer Action, and functions supported information. If these parameters are accepted the discovery will complete and Link Related Ethernet OAM will be operational, else the remote configuration is rejected and requires operator intervention to rectify the conflicting parameters. Link Related Ethernet OAM is provisioned to retrieve one or more MIB variables, also referred as attributes, from the CPE. The operator can retrieve MAC layer counters and PME counters from the CPE after successful completion of discovery. Link Related Ethernet OAM is supported on most of the EFM, EFM Bonding and Native Ethernet LTs and some of the compatible CPEs.

Link Related Ethernet OAM Configuration Parameters Link Related Ethernet OAM is managed using the parameters described in Table TNG 1116-1. These values are stored in the database persistently. Table TNG 1116-1: Link Related Ethernet OAM parameter descriptions

TNG 1116-2

Parameter

Description

Values

Default

admin-status

Parameter used to enable / disable Link Related Ethernet OAM on an interface

Enabled / Disabled

Disabled

oam-mode

Dot3 OAM mode value. (NE is always configured in Active mode)

Active / Passive

Active

alive-timer

Time interval between Alive PDUs sent to the CPE after completion of Discovery. (This parameter has impact on the alive timer of the CPE as this value should be same on both NE and CPE). In addition, internally the NE will use (alive-timer + 5 s) as the maximum interval to receive an OAM PDU from the CPE before declaring it down and restarting the discovery

1s - 300 s

300 s

var-response-timer

Maximum time interval for which the NE waits to receive all the variable response PDUs (all requested counters) from the CPE

2 s - 10 s

5s

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1119 — vMAC Introduction The concept of virtual MAC (vMAC) replaces the MAC address of the subscriber by a MAC address defined by the operator. Enabling vMAC allows improving layer 2 forwarding models in the following two areas:

•

•

Security: Translating the MAC address of the subscriber by an operator defined MAC address ensures by definition the uniqueness of the MAC address across the whole access network, automatically alleviating all issues related with duplicate MAC address. Scalability: By guaranteeing that a MAC address is unique across the whole access network, an operator can now choose to connect multiple DSLAMs to the edge router through the same VLAN. By doing so the operator increases the amount of subscribers sharing the same subnet and consequently, improves the pooling effect when allocating IP addresses.

Features Figure TNG 1119-1 shows the packet flow when vMAC is enabled on a VLAN.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1119-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1119 — vMAC Figure TNG 1119-1: Packet flow

ISAM vMAC is enabled on VLAN A

User on VLAN A

Upstream USER PACKET SRC MAC 40:00:0f:61:80:00 DST MAC 13:67:00:00:00:01

EMAN

The source MAC address is converted into vMAC address

USER PACKET SRC MAC 12:34:00:00:00:01 DST MAC 13:67:00:00:00:01

Downstream EMAN

• • • • •

USER PACKET SRC MAC 13:67:00:00:00:01 DST MAC 40:00:0f:61:80:00

The destination vMAC address is converted back into user MACaddress.

USER PACKET SRC MAC 13:67:00:00:00:01 DST MAC 12:34:00:00:00:01

vMAC Address translation applies to packets which are passed through the ISAM and switched based on layer 2 processing. vMAC does not apply for oAoE applications as the Ethernet packet is “generated” on the LT and the LT MAC is used. vMAC does not apply for MAC concentration, as a single LT MAC is used for packets sent towards the network. If MAC concentration is enabled, any vMAC configuration is ignored. vMAC is supported solely on a single shelf configuration. vMAC includes LT recovery of vMAC addresses through a warm reset: • The vMAC address user MAC relationship is stored in reset safe memory and will be restored upon a warm LT reset. • This ensures the network will see the same vMAC assignment after an LT reset and that network forwarding tables do not require an update, nor other protocols which maintain state based on a MAC address (e.g. DHCP). • LT Recovery is automatically enabled on can not be disabled.

vMAC support •

TNG 1119-2

vMAC address translations are supported for: • Ethernet • PPPoE and IPoE • DHCP (including chaddr in payload) • GARP and ARP (including payload MAC) • Enchanced iBridge configurations

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1119 — vMAC

•

vMAC is supported in the following L2 models: • C-VLAN cross-connect • S+C-VLAN cross-connect • iBridge

Note — vMAC cannot be used in conjunction with S-VLAN cross-connect, QoS VLAN or L2-terminated VLAN.

vMAC address format To ensure uniqueness of the vMAC within the EMAN, vMAC can not be enabled on any VLAN until the vMAC signature and the DSLAM ID have been assigned by the operator. In this release, the vMAC signature is hard coded to zero and the operator is not given any interface to modify it. However, the DSLAM ID must be programmed by the operator. It is the responsibility of the operator to ensure unique DSLAM IDs are assigned; otherwise duplicate vMAC addresses may be generated by different DSLAMs.

• •

Table TNG 1119-1 gives the vMAC address format for DSL/Eth. Table TNG 1119-2 gives the vMAC address format for xPON. Table TNG 1119-1: DSL/Eth vMAC format for data traffic forwarding MAC Address

Configurable

Description

Bit 47...45

No

Rack ID (minus 1)

Bit 44

No

ISAM xDSL vMAC set to 0

Bit 43...42

No

Reserved field for other applications, set to 0’s for the vMAC application

Bit 41

No

U/L field set to 1 (local MAC address validity)

Bit 40

No

I/G field set to 0 (unicast address)

Bit 39...21

Yes

DSLAM ID set by the operator [1..524287] A unique DSLAM ID within an EMAN connected to the same IP edges

Bit 20...15

No

Slot ID of the line board [0…63] The logical position of the line card within the DSLAM.

Bit 14...6

No

Port ID of the subscriber interface [0…511]

Bit 5...0

No

MAC ID unique to each subscriber MAC address

Table TNG 1119-2: xPON vMAC format for data traffic forwarding MAC Address

Configurable

Description

Bit 47...45

Yes

DSLAM ID

Bit 44

No

vMAC xPON MAC set to 1

(1 of 2)

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1119-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1119 — vMAC

MAC Address

Configurable

Description

Bit 43...42

No

Reserved field for other applications, set to 0’s for the vMAC application

Bit 41

No

U/L field set to 1 (local MAC address validity)

Bit 40

No

I/G field set to 0 (unicast address)

Bit 39...27

Yes

DSLAM ID set by the operator [1..65536] A unique DSLAM ID within an EMAN connected to the same IP edges

Bit 26...22

No

Slot ID of the line board [0…31] The logical position of the line card within the DSLAM.

Bit 21...18

No

PON Port ID [0…15]

Bit 17...8

No

Port ID (UNI) of the subscriber interface [0…1023]

Bit 7

No

Reserved

Bit 6...0

No

MAC ID unique to each subscriber MAC address

(2 of 2)

vMAC downstream filter Downstream traffic with vMAC source address can be blocked or allowed as configured by the operator (default is allowed). When downstream traffic with vMAC source address is blocked (disable traffic), a filter is implemented at the LT board level. The filter discards any Ethernet packets received from the NT board within the VLAN and where the MAC source address matches the signature of the local vMAC address format. The downstream filter should not be local to the node, it must be global. For instance bits 43-42 (rack ID) are set to zero for vMAC for single-shelf applications. However, once multi-shelf is supported on vMAC, those bits should not be part of the downstream filter to keep it global.

• • • •

Bit Bit Bit Bit

44: vMAC signature bit (default 0) 43-42: Reserved for other application, set to 0 by vMAC 41: U/L field set to 1 (local MAC addressvalidity) 40: I/G field set to 0 (unicast address

Restrictions and limitations The following restictions and limitations apply:

• • • •

TNG 1119-4

The system blocks the creation of static MAC address on a VLAN which has vMAC enabled. The system rejects the enabling of vMAC on a VLAN if the VLAN is associated with a bridge port on an LT that has static MAC addresses. The system does NOT translate the source MAC address of a subscriber packet if the source address is multicast, broadcast, or invalid. The system extracts data packets traveling upstream which have a destination MAC address that matches an existing vMAC address on the same VLAN on that LT. The packet is then dropped.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1119 — vMAC

• • •

If vMAC is enabled/disabled or the DSLAM ID is changed while traffic is present, a small traffic hit will result due to the system re-learning MAC addresses. vMAC is supported on single shelf configurations only. vMAC address translation does not occur in xxxoAoE configurations or MAC concentration configurations.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1119-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1119 — vMAC

TNG 1119-6

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1120 — VLAN translation Introduction This TNG provides configuration examples for the configuration of VLAN translation. The following parameters must be configured to attach the L2 forwarder interface to a L2 forwarder:

•

•

VLAN scope: This parameter indicates whether the VLAN is scoped as local within a bridge port or as network wide. Values: • local: the subscriber VLAN is terminated in the bridge port • network: the VLAN-port interface is attached to a L2 forwarder and the network VLAN has the same VLAN ID. (NO VLAN TRANSLATION) Network VLAN: This parameter is only configured in case of VLAN translation, otherwise it will have the default value “none”. In case of VLAN translation, the operator must configure this parameter to attach the VLAN port to a L2 forwarder, e.g. a network VLAN.

C-VLAN translation This section shows two examples of the steps required to perform C-VLAN translation.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1120-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1120 — VLAN translation

Example 1

1

Create an unstacked VLAN in cross-connect mode: configure vlan id 100 mode cross-connect

Note — For the complete procedure, refer to DLP 1117.

2

Create a bridge port: configure bridge port 1/1/5/11:8:35

Note — pvid must not be configured, if configured pvid= any-C-vlan

3

Associate an unstacked C-VLAN to the bridge port: configure bridge port 1/1/5/11:8:35 vlan-id 10 network-vlan 100 vlan-scope local

4

STOP. This procedure is complete.

Example 2

1

Create an unstacked vlan in residential-bridge mode: configure vlan id 150 mode residential-bridge

Note — For the complete procedure, refer to DLP 1117.

2

Create a bridge port r/s/s/1: configure bridge port 1/1/5/12:8:35

Note — pvid must not be configured, if configured pvid= any-C-vlan

3

Create a bridge port r/s/s/2: configure bridge port 1/1/5/13:8:35

Note — pvid must not be configured, if configured pvid= any-C-vlan

4

Associate an unstacked C-VLAN to the bridge port 1: configure bridge port 1/1/5/12:8:35 vlan-id 10 network-vlan 150 vlan-scope local

TNG 1120-2

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1120 — VLAN translation

5

Associate an unstacked C-VLAN to the bridge port 2: configure bridge port 1/1/5/13:8:35 vlan-id 20 network-vlan 150 vlan-scope local

6

STOP. This procedure is complete.

S-VLAN translation This section shows an example of the steps required to perform S-VLAN translation. The configuration procedure is as follows: 1

Create an S-vlan in cross-connect mode: configure vlan id stacked:200:0 mode cross-connect

Note — For the complete procedure, refer to DLP 1118.

2

Create a bridge port: configure bridge port 1/1/5/14:8:35

Note — pvid must not be configured, if configured pvid= any-S-vlan

3

Associate an S-VLAN to the bridge port: configure bridge port 1/1/5/14:8:35 vlan-id stacked:20:0 network-vlan 200:0 vlan-scope local

4

STOP. This procedure is complete.

Stacked S+C-VLAN This section shows examples of the steps required to perform C-VLAN translation in a stacked S+C-VLAN. The configuration procedure is as follows: 1

Create an S-vlan in L2-terminated mode: configure vlan id stacked:400:0 mode layer2-terminated

2

Create a stacked S+C-VLAN in cross-connect mode: configure vlan id stacked:400:300 mode cross-connect

Note — For the complete procedure, refer to DLP 1119.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1120-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1120 — VLAN translation

3

Create a bridge port: configure bridge port 1/1/5/15:8:35

Note — pvid must not be configured, if configured pvid = 300

4

Associate a C-VLAN to the bridge port: configure bridge port 1/1/5/15:8:35 vlan-id 30 network-vlan 400:300 vlan-scope local

5

TNG 1120-4

STOP. This procedure is complete.

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1121 — xDSL bonding Purpose This TNG describes xDSL bonding, with a focus on ADSL and VDSL:

• • • • • • •

Overview of xDSL bonding ATM bonding and PTM bonding Bonding levels xDSL bonding implementation Configuring xDSL bonding xDSL bonding alarms Examples of xDSL bonding

Overview of xDSL bonding xDSL bonding allows multiple physical xDSL links to be combined as one logical link to increase bitrate capacity to the subscriber and/or extend the reach of existing services. For the purposes of this TNG, “xDSL bonding” refers to combining two xDSL links. In an xDSL bonding scenario, two ports from the ISAM are configured into a bonding group that is connected to a bonding modem at the customer premises. In a bonding scenario, you must use a modem that supports bonding rather than a non-bonding (native) modem. Within a bonding group, one line is referred to as the primary link and the other line is the secondary link. The supported bit rate over the bonding group is the sum of the achieved bit rates on each of the lines in the group. For an overview of the level of xDSL bonding supported per LT board, see the Product Information manual of your system.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1121-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1121 — xDSL bonding

ATM bonding and PTM bonding There are two types of xDSL bonding, depending on whether an ATM or PTM transport protocol is used on the xDSL lines.

ATM bonding ATM bonding is used for ATM-based transmission links for all types of ADSL. ATM bonding adds sequence information to the ATM cells, and thus allows resequencing to support delay variation due to speed differences between the physical links that make up the bonding group. ATM bonding is sometimes referred to as multi-ADSL bonding because multi-ADSL lines typically use ATM-based transmission links. ATM bonding differs from IMA, a commonly used method of logically combining multiple lines for transmission of ATM cells, in that:

• • • •

the links can run at different rates differential delay does not need to be constant (but should be controlled to minimize buffering requirements) the traffic header of the transported ATM cells is modified to carry a sequence ID traffic is distributed to the links at the discretion of the transmitter rather than being distributed in strict round-robin order

ATM bonding is specified by ITU-T G.998.1.

PTM bonding PTM bonding is used for Ethernet-based transmission links using SHDSL, VDSL2 and sometimes ADSL2 or ADSL2+. PTM bonding adds sequence information to the transmitted frames or frame fragments, and thus allows resequencing to support delay variation due to speed or PDU size differences, or both, across the physical links that make up the bonding group. PTM bonding is sometimes referred to as EFM bonding. PTM bonding is specified by ITU-T G.998.2.

Bonding levels There are three levels of xDSL bonding depending on whether the lines that make up a bonding group must connect to adjacent ports on the same LT board, any ports on the same LT board, or across different LT boards.

Chipset-level bonding With chipset-level bonding, bonding traffic is handled by the DSL chipset. Ports to be configured for chipset-level bonding:

• • TNG 1121-2

cannot have any traffic configurations (no atm pvc, bridge ports,...) must be adjacent ports on the same LT board

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1121 — xDSL bonding

Only an odd-numbered port can be the primary port of a bonding group bonded at the chipset level. This is sometimes referred to as “odd-even pair bonding.” The name of the bonding group, also called the bonding group index, is derived from the primary port.

LT-level bonding With LT-level bonding, traffic is handled by the interworking function on the LT board, allowing non-contiguous ports on the same LT board to be bonded. Prior to bonding configuration, ports do not have to be unconfigured (assigned profile#0), but the secondary port must not have any traffic configuration (no bridge ports or VLANs, for example). For LT-level bonding, any port can be the primary port up to a maximum of 24 primary ports per LT board. As with chipset-level bonding, the bonding group index number is derived from the primary port number.

System-level bonding As with LT-level bonding, traffic handling in system level-bonding is done by the interworking function on the LT board. The difference with LT-level bonding is that the two ports do not need to be on the same LT board, or even the same shelf. In all other respects, system-level bonding is the same as LT-level bonding, and supports single line bonding as described in “Line recovery with single line bonding” above.

Note — As of Release 3.5 (Feature Group 3.6), ISAM no longer supports system-level bonding.

xDSL bonding implementation This section describes some features and restrictions that apply to xDSL bonding.

Initialization Each port on a bonding modem does an initial train (probe train) to determine the maximum capacity of its line. This information is used to determine the bandwidth split between the lines that make up a bonding group. With chipset-level bonding, if either line of the bonded pair is out of service during probe train, the bonding group will not initialize. This contrasts with LT-level bonding, for which a feature called single line bonding can be configured to keep the bonding group in service even if one of the links is unavailable during probe train. See “Line recovery with single line bonding” for more information.

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1121-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1121 — xDSL bonding

Redundancy Since two physical lines are used, a benefit of xDSL bonding is that a form of line redundancy is provided. If one of the lines goes out of service after the bonded group has been initialized and bandwidth has been split across the lines, the bonding group can still stay in service with only one line, provided that it can meet the group requirements alone. When the out of service line recovers, it rejoins the group.

Note — Note that this type of incidental redundancy is not provided if the line is already out of service when the bonding group is initialized. In this scenario, the out-of-service line will not join the group when it recovers. It will join the group during the next bandwidth split, which can be triggered by putting the bonding group out of service and back in service. Line recovery with single line bonding There are two possibilities for single line bonding:

• •

configure a bonding group with only a primary line (no secondary line) configure a bonding group with two lines, but provide a means of bonding group recovery if only one link is in service during probe train. This allows the secondary link to join the group under operator control at a later time. In this case, the single line bonding is allowed by setting the group assembly timer to a value different from 0, before the group is put admin up.

By default, this type of single line bonding is disabled, that is, the group assembly timer is set to 0. If the group assembly timer is set to a value other than 0, it will start to count down during the probe train when one of the lines becomes operational. If the other link is not detected or does not become operational before the timer expires, single line bonding is assumed and the single link alone will come into service if it meets the bonding group profile requirements.

Configuring xDSL bonding Bonding groups can be configured using TL1 or CLI. See section “Examples of xDSL bonding” later in this TNG for the configuration commands. This section describes important considerations for xDSL bonding configuration, in particular, how to manage the bandwidth split between the bonded lines. See DLP 1130 for the procedure. There are three distinct ways to configure bonding, as described in Table TNG 1121-1:

TNG 1121-4

December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

TNG 1121 — xDSL bonding Table TNG 1121-1: Bonding group configuration methods Configuration

Description

Values

Populate values for both the individual service profiles and group profile

By populating the bit rates in xsrvc_profile and xbond_profile, both will be taken into account. This gives the operator some control over the bandwidth split ratio. The bit rate configured in xbond_profile will be split proportionally to the attainable bit rate of each line, respecting the bit rates configured in xsrvc_profile:

xbond_profile: min/planned/max

• •

Populate values for the group profile only

Populate values for the service profiles only

xsrvc_profile: min/planned/max

lines configured in RA Mode 1 (MANUAL) will be forced to operate at the planned bit rate of xsrvc_profile. lines configured in RA Mode 2 (AT_INIT) or RA Mode 3 (DYNAMIC) are only allowed to operate at a bit rate higher or equal than the minimum bit rate of xsrvc_profile. The maximum bit rate of xsrvc_profile is ignored.

By setting the bit rates of xsrvc_profile to 0, only the bit rates of xbond_profile are used. This gives the operator no control over the bandwidth split ratio. This configuration only makes sense for lines in RA Mode 2 or 3, because lines in RA Mode 1 would be forced to operate at a bit rate of 0 in case the planned bit rate of xsrvc_profile is set to 0.

xbond_profile: min/planned/max

By setting the bit rates of xbond_profile to 0, the bonding group bitrates are calculated using the bitrates of the xDSL service configuration profiles:

xbond_profile: 0/0/0

• • •

minimum bitrate of group = sum of the minimum bitrates of the xDSL service configuration profile of all the lines in the group planned bitrate of group = sum of the planned bitrates of xDSL service configuration profile of all lines in the group max bitrate of group = sum of max bitrates of xDSL service configuration profile of all lines in the group

xsrvc_profile: 0/0/0

xsrvc_profile: min/planned/max

Note: when lines are configured in RA mode 1 (MANUAL), the min and max bitrate of that line is set equal to the planned bitrate, when calculating the values for the bonding group profile.

In xDSL bonding, all traffic configuration (for example, ATM PVC or bridgeport) must be done on the primary link of the bonding group.

Dynamic Line Management In order to optimise and stabilize individual lines in a bonded group it is possible to reconfigure a number of parameters at line level. The maximum bitrate and the minimum INP for both upstream and downstream direction can be reconfigured by using the matching overrule parameters on the line. The modification of these parameters causes a re-init of the bonding group so the new setting can be taken into account. configure xdsl overrule-data (if-index) max-bitrate-down max-bitrate-up

Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 TNG 1121-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT

TNG 1121 — xDSL bonding

imp-noise-prot-dn imp-noise-prot-up