Vous êtes sur la page 1sur 966

Alcatel-Lucent 7302 Alcatel-Lucent 7330 Alcatel-Lucent 7356

INTELLIGENT SERVICES ACCESS MANAGER INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE NODE 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

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

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 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 1101-1 NTP 1114-1

NTP 1118-1 NTP 1119-1 NTP 1124-1 NTP 1126-1 NTP 1127-1 NTP 1130-1

NTP 1132 Configure Connectivity Fault Management NTP 1132-1 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
viii

NTP 2100-1 NTP 2103-1 NTP 2104-1 NTP 2105-1 NTP 2106-1 NTP 2107-1 NTP 2108-1

December 2011 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 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

NTP 2115-1 NTP 2116-1 NTP 2117-1 NTP 2120-1 NTP 2121-1 NTP 2122-1

NTP 2129-1 NTP 2133-1

Detailed Level Procedures (DLP)


DLP 1100 Set up a local CLI session or a local TL1 session DLP 1112 Lock and unlock equipment DLP 1113 Configure the equipment DLP 1117 Configure a VLAN on the LT for C-VLAN cross-connect DLP 1118 Configure a VLAN on the LT for S-VLAN cross-connect DLP 1100-1 DLP 1112-1 DLP 1113-1

DLP 1117-1

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 1120 Configure a VLAN on the LT for C-iBridge DLP 1124 Create an xDSL/native Ethernet user and add this user to a VLAN on the LT DLP 1129 Create xDSL profiles DLP 1130 Configure xDSL bonding DLP 1134 Configure QoS DLP 1145 Configure 802.1x DLP 1146 Configure PPPoE relay on LT DLP 1147 Configure PPPoX cross-connect DLP 1151 Shut down and restart the NT DLP 1152 Reboot the system DLP 1153 Shut down and restart individual equipment DLP 1159 Manage OSWP DLP 1163 Modifying xDSL profiles DLP 1170 Configure SSH and SFTP DLP 1173 Switch a user from ADSL to VDSL

DLP 1119-1 DLP 1120-1

DLP 1124-1 DLP 1129-1 DLP 1130-1 DLP 1134-1 DLP 1145-1 DLP 1146-1 DLP 1147-1 DLP 1151-1 DLP 1152-1

DLP 1153-1 DLP 1159-1 DLP 1163-1 DLP 1170-1 DLP 1173-1

December 2011 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 1183 Configure IMA on SHDSL spans DLP 1187 Configure global VLAN parameters on the LT DLP 1188 Configure custom PSD points DLP 1189 Configure VDSL2 virtual noise values DLP 1190 Configure threshold crossing alerts DLP 1197 View port configuration and operational data on LT DLP 1201 Configure protocol tracing DLP 1202 Configure QoS threshold crossing alerts DLP 1203 Configure general security settings DLP 1205 Configure Link Related Ethernet OAM DLP 1206 Configure an xDSL DPBO profile DLP 1207 Modify an xDSL DPBO profile DLP 1208 Configure xDSL power back off DLP 1212 Create an IP user/subnet DLP 1182-1 DLP 1183-1

DLP 1187-1 DLP 1188-1 DLP 1189-1 DLP 1190-1

DLP 1197-1 DLP 1201-1 DLP 1202-1 DLP 1203-1 DLP 1205-1 DLP 1206-1 DLP 1207-1 DLP 1208-1 DLP 1212-1
xi

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

Contents

DLP 1215 Configure the impulse noise sensor on an xDSL line DLP 1217 Configure the xDSL overrule data DLP 1219 Forced NT switchover DLP 1220 Manage the CDE profile DLP 1221 Manage troubleshooting counters on LT DLP 1225 Configure the p-bit counter on a VLAN port

DLP 1215-1 DLP 1217-1 DLP 1219-1 DLP 1220-1 DLP 1221-1

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 1255 Configure a port on the NELT-B LT DLP 1257 Configure a line with an xDSL RTX profile DLP 1258 Modify an xDSL RTX profile

DLP 1253-1 DLP 1255-1 DLP 1257-1 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 1282 Configure the fairness SLA on the NELT-B LT

DLP 1271-1

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 1292 Modify a Vectoring Control Entity profile DLP 1293 Delete a Vectoring Control Entity profile

DLP 1291-1 DLP 1292-1 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 1296 Modify an xDSL vectoring profile DLP 1297 Delete an xDSL vectoring profile DLP 1298 Monitor xDSL vectoring lines DLP 2101 Create operator profiles and instances DLP 2103 Configure system parameters DLP 2105 Configure link aggregation usage DLP 2107 Manage OSPF DLP 2108 Configure RIP DLP 2109 Configure SNMP and trap management DLP 2110 Manage alarms

DLP 1295-1 DLP 1296-1 DLP 1297-1 DLP 1298-1 DLP 2101-1 DLP 2103-1 DLP 2105-1 DLP 2107-1 DLP 2108-1 DLP 2109-1 DLP 2110-1
xiii

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

Contents

DLP 2111 Plan, replan, and unplan equipment DLP 2114 Configure NT redundancy DLP 2115 Create a L2-terminated forwarder VLAN DLP 2116 Create a L2-terminated router VLAN DLP 2121 Add a network/LAG port to a VLAN in the SHub DLP 2122 Create a forwarding VRF DLP 2123 Create a router VRF DLP 2125 Create an IPoA user DLP 2126 Create an IPoE user DLP 2128 Add an LT port to a VLAN on the SHub DLP 2132 Configure filtering on the NT DLP 2136 Configure the multicast service in the system DLP 2137 Configure a multicast VLAN DLP 2138 Configure a multicast channel DLP 2139 Configure DHCP relay agent in iBridge mode DLP 2140 Configure DHCP relay agent in router mode
xiv

DLP 2111-1 DLP 2114-1 DLP 2115-1 DLP 2116-1

DLP 2121-1 DLP 2122-1 DLP 2123-1 DLP 2125-1 DLP 2126-1 DLP 2128-1 DLP 2132-1

DLP 2136-1 DLP 2137-1 DLP 2138-1

DLP 2139-1

DLP 2140-1

December 2011 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 2142 Configure the system security domain DLP 2144 Configure RADIUS DLP 2150 Configure ARP table entry DLP 2154 Create a snapshot alarm table DLP 2155 Monitor alarms DLP 2157 Manage the SHub database DLP 2160 View version of the SHub software DLP 2162 Modify the external management VLAN DLP 2164 Ping another host DLP 2165 Perform a traceroute action DLP 2166 Configure SNMP proxy CPE management DLP 2167 Script files DLP 2168 Modify the system management IP parameters DLP 2169 Configure cluster management DLP 2171 Enable EMS management DLP 2172 Create a default operator profile

DLP 2141-1 DLP 2142-1 DLP 2144-1 DLP 2150-1 DLP 2154-1 DLP 2155-1 DLP 2157-1 DLP 2160-1 DLP 2162-1 DLP 2164-1 DLP 2165-1 DLP 2166-1 DLP 2167-1

DLP 2168-1 DLP 2169-1 DLP 2171-1 DLP 2172-1


xv

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

Contents

DLP 2175 Configure system management IP parameters DLP 2176 Performance monitoring commands DLP 2177 Configure SFP downlink ports DLP 2179 Configure system logging DLP 2180 Configure static MAC addresses DLP 2181 Configure operator authentication via RADIUS DLP 2185 Configure DHCP MAC concentration in forwarder mode DLP 2186 Configure ANCP session DLP 2191 Enable dual tagging in the SHub DLP 2195 Configure general bridge parameters on the LT DLP 2196 Configure Voice SIP DLP 2198 Configure the multicast service on a user port DLP 2199 Configure QoS on the SHub DLP 2200 Configure Spanning Tree on the SHub DLP 2204 Configure an unnumbered IP interface on the SHub
xvi

DLP 2175-1 DLP 2176-1 DLP 2177-1 DLP 2179-1 DLP 2180-1

DLP 2181-1

DLP 2185-1 DLP 2186-1 DLP 2191-1

DLP 2195-1 DLP 2196-1

DLP 2198-1 DLP 2199-1 DLP 2200-1

DLP 2204-1

December 2011 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 2210 View the status of various system parameters DLP 2211 Configure SFP uplink ports DLP 2213 Enable OAM counters DLP 2214 Configure connectivity fault management DLP 2216 Configure Voice MEGACO DLP 2222 Create the PCCP group DLP 2223 Configure SHub port mirroring DLP 2224 Change shelf mode DLP 2230 Configure a VLAN on the SHub DLP 2231 Manage the ports on the NT DLP 2236 Configure the enhanced system clock synchronization DLP 2273 External Packet Forwarding

DLP 2209-1

DLP 2210-1 DLP 2211-1 DLP 2213-1 DLP 2214-1 DLP 2216-1 DLP 2222-1 DLP 2223-1 DLP 2224-1 DLP 2230-1 DLP 2231-1

DLP 2236-1 DLP 2273-1

Routine Task Procedure (RTP)


RTP 1102 Retrieve remote inventory RTP 1103 Retrieve board temperature RTP 1102-1 RTP 1103-1
xvii

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

Contents

RTP 2100 Backup the configuration RTP 2101 Restore the configuration

RTP 2100-1 RTP 2101-1

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 1100-1 TAP 1101-1 TAP 1102-1 TAP 1103-1 TAP 1105-1 TAP 1106-1 TAP 1107-1

TAP 1108 Integrated NBLT for MEGACO Termination TAP 1108-1 TAP 1109 Integrated NBLT for SIP Termination TAP 2104 Fault isolation and troubleshooting TAP 1109-1 TAP 2104-1

Training (TNG)
TNG 1104 DHCP relay agent configuration TNG 1105 Overall software packages TNG 1104-1 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 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 TNG 2117 Enhanced iBridge TNG 2118 PPPoE with MAC address concentration

TNG 1107-1 TNG 1108-1 TNG 1115-1 TNG 1116-1 TNG 1119-1 TNG 1120-1 TNG 1121-1 TNG 2100-1 TNG 2101-1 TNG 2102-1

TNG 2106-1 TNG 2109-1 TNG 2110-1

TNG 2112-1 TNG 2117-1 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

Introduction

1.1 Introduction

1-2 1-2 1-5

1.2 How to use this document 1.3 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-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 This step offers two options. You must choose one of the following: a b 2 This is one option. This is another option.

You must perform this step.

1-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

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 This step has a series of substeps that you must perform to complete the step. You must perform the following substeps: i ii iii 2 This is the first substep. This is the second substep. This is the third substep.

You must perform this step.

1.3

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 Execute script files Perform equipment repairs Monitor performance and view configuration Modify DSL services Maintain the system Manage system logging Configure SHDSL Configure Link Related Ethernet OAM Configure Connectivity Fault Management Initial system configuration Configure equipment Configure a VLAN cross-connect Configure an iBridge VLAN Configure an IP-aware bridge Configure an IP router Configure services Monitor alarms Perform software management Modify system parameters Troubleshooting the network Manage an SNMP proxy CPE (1 of 2) NTP number NTP 1101 NTP 1114 NTP 1118 NTP 1119 NTP 1124 NTP 1126 NTP 1127 NTP 1130 NTP 1132 NTP 2100 NTP 2103 NTP 2104 NTP 2105 NTP 2106 NTP 2107 NTP 2108 NTP 2115 NTP 2116 NTP 2117 NTP 2120 NTP 2121

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 Cluster management Configure a loopback interface on the SHub Configure an enhanced IP router (2 of 2)

NTP number NTP 2122 NTP 2129 NTP 2133

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


Title Set up a local CLI session or a local TL1 session Lock and unlock equipment Configure the equipment Configure a VLAN on the LT for C-VLAN cross-connect Configure a VLAN on the LT for S-VLAN cross-connect Configure a VLAN on the LT for S+C-VLAN cross-connect Configure a VLAN on the LT for C-iBridge Create an xDSL/native Ethernet user and add this user to a VLAN on the LT Create xDSL profiles Configure xDSL bonding Configure QoS Configure 802.1x Configure PPPoE relay on LT Configure PPPoX cross-connect Shut down and restart the NT Reboot the system Shut down and restart individual equipment Manage OSWP Modifying xDSL profiles Configure SSH and SFTP Switch a user from ADSL to VDSL Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect Configure SHDSL Configure IMA on SHDSL spans Configure global VLAN parameters on the LT Configure custom PSD points Configure VDSL2 virtual noise values Configure threshold crossing alerts View port configuration and operational data on LT (1 of 4) DLP number DLP 1100 DLP 1112 DLP 1113 DLP 1117 DLP 1118 DLP 1119 DLP 1120 DLP 1124 DLP 1129 DLP 1130 DLP 1134 DLP 1145 DLP 1146 DLP 1147 DLP 1151 DLP 1152 DLP 1153 DLP 1159 DLP 1163 DLP 1170 DLP 1173 DLP 1174 DLP 1182 DLP 1183 DLP 1187 DLP 1188 DLP 1189 DLP 1190 DLP 1197

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 Configure protocol tracing Configure QoS threshold crossing alerts Configure general security settings Configure Link Related Ethernet OAM Configure an xDSL DPBO profile Modify an xDSL DPBO profile Configure xDSL power back off Create an IP user/subnet Configure the impulse noise sensor on an xDSL line Configure the xDSL overrule data Forced NT switchover Manage the CDE profile Manage troubleshooting counters on LT Configure the p-bit counter on a VLAN port Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge Configure the third-party equipment management port on the 7356 FD REM Configure a port on the NELT-B LT Configure a line with an xDSL RTX profile Modify an xDSL RTX profile Configure spanning tree on the NELT-B LT Configure link aggregation on the NELT-B LT Configure the fairness SLA on the NELT-B LT Troubleshooting congestion on the NELT-B LT Configure a Vectoring Control Entity profile and associate it to a board Modify a Vectoring Control Entity profile Delete a Vectoring Control Entity profile Configure or modify the mapping between the VP board and the SLV LT boards Configure a line with an xDSL vectoring profile Modify an xDSL vectoring profile Delete an xDSL vectoring profile Monitor xDSL vectoring lines Create operator profiles and instances Configure system parameters Configure link aggregation usage Manage OSPF Configure RIP Configure SNMP and trap management (2 of 4)

DLP number DLP 1201 DLP 1202 DLP 1203 DLP 1205 DLP 1206 DLP 1207 DLP 1208 DLP 1212 DLP 1215 DLP 1217 DLP 1219 DLP 1220 DLP 1221 DLP 1225 DLP 1232 DLP 1253 DLP 1255 DLP 1257 DLP 1258 DLP 1270 DLP 1271 DLP 1282 DLP 1283 DLP 1291 DLP 1292 DLP 1293 DLP 1294 DLP 1295 DLP 1296 DLP 1297 DLP 1298 DLP 2101 DLP 2103 DLP 2105 DLP 2107 DLP 2108 DLP 2109

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 Manage alarms Plan, replan, and unplan equipment Configure NT redundancy Create a L2-terminated forwarder VLAN Create a L2-terminated router VLAN Add a network/LAG port to a VLAN in the SHub Create a forwarding VRF Create a router VRF Create an IPoA user Create an IPoE user Add an LT port to a VLAN on the SHub Configure filtering on the NT Configure the multicast service in the system Configure a multicast VLAN Configure a multicast channel Configure DHCP relay agent in iBridge mode Configure DHCP relay agent in router mode Configure DHCP relay agent in forwarder mode Configure the system security domain Configure RADIUS Configure ARP table entry Create a snapshot alarm table Monitor alarms Manage the SHub database View version of the SHub software Modify the external management VLAN Ping another host Perform a traceroute action Configure SNMP proxy CPE management Script files Modify the system management IP parameters Configure cluster management Enable EMS management Create a default operator profile Configure system management IP parameters Performance monitoring commands Configure SFP downlink ports (3 of 4)

DLP number DLP 2110 DLP 2111 DLP 2114 DLP 2115 DLP 2116 DLP 2121 DLP 2122 DLP 2123 DLP 2125 DLP 2126 DLP 2128 DLP 2132 DLP 2136 DLP 2137 DLP 2138 DLP 2139 DLP 2140 DLP 2141 DLP 2142 DLP 2144 DLP 2150 DLP 2154 DLP 2155 DLP 2157 DLP 2160 DLP 2162 DLP 2164 DLP 2165 DLP 2166 DLP 2167 DLP 2168 DLP 2169 DLP 2171 DLP 2172 DLP 2175 DLP 2176 DLP 2177

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 Configure system logging Configure static MAC addresses Configure operator authentication via RADIUS Configure DHCP MAC concentration in forwarder mode Configure ANCP session Enable dual tagging in the SHub Configure general bridge parameters on the LT Configure Voice SIP Configure the multicast service on a user port Configure QoS on the SHub Configure Spanning Tree on the SHub Configure an unnumbered IP interface on the SHub Configure vMAC View the status of various system parameters Configure SFP uplink ports Enable OAM counters Configure connectivity fault management Configure Voice MEGACO Create the PCCP group Configure SHub port mirroring Change shelf mode Configure a VLAN on the SHub Configure the enhanced system clock synchronization External Packet Forwarding (4 of 4)

DLP number DLP 2179 DLP 2180 DLP 2181 DLP 2185 DLP 2186 DLP 2191 DLP 2195 DLP 2196 DLP 2198 DLP 2199 DLP 2200 DLP 2204 DLP 2209 DLP 2210 DLP 2211 DLP 2213 DLP 2214 DLP 2216 DLP 2222 DLP 2223 DLP 2224 DLP 2230 DLP 2236 DLP 2273

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


Title Retrieve remote inventory Retrieve board temperature Backup the configuration Restore the configuration RTP number RTP 1102 RTP 1103 RTP 2100 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 Metallic test access F5 loopback test Equipment repair Single ended line testing Dual-ended line testing ITSC MELT Integrated NBLT for MEGACO Termination Integrated NBLT for SIP Termination Fault isolation and troubleshooting TAP number TAP 1100 TAP 1101 TAP 1102 TAP 1103 TAP 1105 TAP 1106 TAP 1107 TAP 1108 TAP 1109 TAP 2104

Table IXL 100-5: Training (TNG)


Title DHCP relay agent configuration Overall software packages xDSL parameters SHDSL parameters Link Related Ethernet OAM (EFM OAM) vMAC VLAN translation xDSL bonding Service installation QoS configuration IGMP and multicast configuration Specifying 7330 ISAM FTTN expansion units using the CLI Performance management counters Configuration examples 7330 ISAM FTTN configuration for subtending Slot numbering schemes Enhanced iBridge PPPoE with MAC address concentration TNG number TNG 1104 TNG 1105 TNG 1107 TNG 1108 TNG 1116 TNG 1119 TNG 1120 TNG 1121 TNG 2100 TNG 2101 TNG 2102 TNG 2106 TNG 2109 TNG 2110 TNG 2112 TNG 1115 TNG 2117 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 2 Create and execute script files; see DLP 2167. 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 2 3 4 Plan, unplan, and replan equipment (for example, plug-in units); see DLP 2111. Pull out and plug in equipment. For the procedures, see the hardware installation manual for your equipment. Lock and unlock equipment (mostly plug-in units); see DLP 1112. Start up or shut down the system, select one of: a b c 5 Shut down or restart the NT; see DLP 1151. Reboot the entire system; see DLP 1152. 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 2 3 4 5 6 7 Configure the Threshold Crossing Alert (TCA); see DLP 1190. Enable the Operations and Maintenance (OAM) counters; see DLP 2213. Manage the troubleshooting counters on the LT; see DLP 1221. Viewing the PM counters; see DLP 2176. Viewing the configuration and operational data of a port (xDSL or Ethernet); see DLP 1197. View the status of different system parameters (system clock, memory usage on the NT and CPU load on the NT); see DLP 2210. 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 2 3 4 5 6 7 Modify an xDSL profile; see DLP 1163. Modify a DPBO profile; see DLP 1207. Modify an RTX profile; see DLP 1258. Modify an xDSL vectoring profile; see DLP 1296. Modify an Vectoring Control Entity profile; see DLP 1292. Switch a user from ADSL to VDSL; see DLP 1173. 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 2 3 4 Back up the system configuration; see RTP 2100. Restore the system configuration; see RTP 2101. Retrieve the remote inventory; see RTP 1102. 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. 1 2 3 Enable and disable logging for all system logs; see DLP 2179. Create, configure, and monitor system logs; see DLP 2179. STOP. This procedure is complete.

NTP 1126-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 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 2 3 To configure SHDSL; see DLP 1182. To configure IMA on SHDSL spans; see DLP 1183. 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 2 Configuration of EFM OAM; see DLP 1205. After configuration, the following actions can be performed: a b c d 3 Viewing of Local and Remote (CPE) information; see DLP 1205. Viewing of EFM OAM statistics; see DLP 1205. Retrieve MAC counters; see DLP 1205. 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 Configure CFM: i ii iii iv 2 3 Configure a maintenance domain; see DLP 2214 Configure (create) a maintenance association; see DLP 2214 Configure a maintenance end point; see DLP 2214 Optionally, configure (modify) the maintenance association and set the mhf-creation parameter to mhf-default; see DLP 2214

View CFM configuration; see DLP 2214 STOP. This procedure is complete.

NTP 1132-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 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) TL1 Gateway TL1 Terminal TL1 CT CLI Terminal CLI CT Debug Terminal

SNMPv2 or SNMPv3

UDP

SSH

Telnet

RS232

SSH

Telnet

RS232

UDP

SNMP agent

TL1 agent

CLI agent

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 EMS TL1 CT CLI CT CLI terminal TL1 gateway TL1 terminal Description Remotely connected Element Management System based on SNMP Local Craft Terminal using TL1 commands Local Craft Terminal using Command Line Interface (CLI) commands Remotely connected terminal using CLI commands based over telnet or ssh Remotely connected gateways using TL1 commands over UDP 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: 1 2 3 4 5 6 7
NTP 2100-2

Set up a CLI session; see DLP 1100. Create and configure an Operator Profile; see DLP 2101. Create a default Operator Profile; see DLP 2172. Configure the management IP parameters and network interfaces; see DLP 2175. Configure SSH; see DLP 1170. Configure the general security settings; see DLP 1203. 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 9 10 11 12 13

Configure the enhanced system clock synchronization; see DLP 2236. Configure Simple Network Management Protocol (SNMP) and trap management; see DLP 2109. Enable the management of EMS; see DLP 2171. Configure the alarm management; see DLP 2110. Save the SHub database; see DLP 2157. 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 Planning equipment Description 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 is done when changing the current equipment.

Replanning 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 Locking and unlocking equipment

Description 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: 1 2 3 4 5 6 7 Plan, replan, or unplan equipment; see DLP 2111. Lock or unlock the equipment; see DLP 1112. Modify the configuration of the system equipment; see DLP 1113. If required, change the shelf mode; see DLP 2224. Configure SFP downlink ports; see DLP 2177. Configure SFP uplink ports; see DLP 2211. STOP. This procedure is complete.

NTP 2103-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


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 interfaces 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 interfaces preconfigured S-VLAN will be assigned. In case of untagged/priority tagged frames, the subscriber interfaces 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

VLAN 11 (=Bridge) Phy VLAN 17 (=Bridge)

C 11 VLAN CC

C-VLAN CC

S17 +C23 VLAN CC LT

S+C-VLAN CC (No VLAN translation shown on user side)

VLAN 13 (=Bridge) Phy Phy LAG VLAN 19 (=Bridge)


DLP 2105

S17 +C29 VLAN CC

S+C-VLAN CC

S 13 VLAN CC LT

S-VLAN CC

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

Configure a VLAN on the LT for VLAN cross-connect. Do one of the following: a b c For C-VLAN cross-connect; see DLP 1117. For S-VLAN cross-connect; see DLP 1118. 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 b create an xDSL/native Ethernet user and add him to a VLAN on the LT; see DLP 1124. create an xDSL IPoA user and add him to a VLAN on the LT (for C-VLAN cross-connect): see DLP 1174.

3 4 5

Configure network interface and LT interface on the SHub; see DLP 2231. Optionally, configure LAG on the SHub; see DLP 2105. Configure a VLAN on the SHub; see DLP 2230.

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

7 8

Add a network/LAG port to the VLAN on the SHub; see DLP 2121. STOP. This procedure is complete.

NTP 2104-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 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 2231 DLP 2230 DLP 2231

Network DLP 2121 Ports

SHub VLAN

LT Ports

LT VLAN for iBridge

DLP 1124 DLP 1232

DLP 2128

Phy LT Phy Phy LAG


DLP 2105

iBridge VLAN 19 iBridge VLAN 19 iBridge VLAN 19 LT (No VLAN translation shown on user side)

NT_SHUB ISAM_SHUB

1 2

Configure a VLAN on the LT for iBridge; see DLP 1120. Create a user and add him to a VLAN created in step 1. Do one of the following: a b create an xDSL/native Ethernet user and add him to a VLAN on the LT; see DLP 1124. create an xDSL IPoA user and add him to a VLAN on the LT (for iBridge): see DLP 1232.

3 4 5 6 7 8

Configure network interface and LT interface on the SHub; see DLP 2231. Optionally, configure LAG on the SHub; see DLP 2105. Configure a VLAN on the SHub; see DLP 2230. Add an LT port to the VLAN on the SHub; see DLP 2128. Add a network/LAG port to the VLAN on the SHub; see DLP 2121. STOP. This procedure is complete.

NTP 2105-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 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: 1 2 3 4 Create a forwarder Virtual Routing Forwarding (VRF); see DLP 2122. Create a L2-terminated forwarder VLAN for each of the Network Service Providers (NSP); see DLP 2115. Add the network interfaces to the L2-terminated forwarder VLANs; see DLP 2121. STOP. This procedure is complete.

NTP 2106-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 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: 1 2 3 4 Create a router VRF; see DLP 2123. Create a L2-terminated router VLAN; see DLP 2116. Add users; see DLP 2125 for adding IPoA user or DLP 2126 for adding IPoE user. STOP. This procedure is complete.

NTP 2107-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 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 ii iii iv v vi vii For the configuration of the service profiles and the spectrum profiles; see DLP 1129. For the configuration of custom PSD points; see DLP 1188. For the configuration of virtual noise values for VDSL2; see DLP 1189. For the configuration of a Downstream Power Back Off (DPBO) profile; see DLP 1206. For the configuration of an RTX profile (standard ARQ provisioning); see DLP 1257 For the configuration of a Vectoring Control Entity profile; see DLP 1291. 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. ix x xi 2 3 4 5 For the configuration of power back-off; see DLP 1208. For the configuration of xDSL overrule data; see DLP 1217. For the configuration of the impulse noise sensor on an xDSL line; see DLP 1215.

Configure xDSL bonding; see DLP 1130. Configure general bridge parameters for LT and SHub; see DLP 2195. If required, enable dual tagging on the SHub; see DLP 2191. Configure QoS: i ii iii For the configuration of QoS; see DLP 1134. For the configuration of QoS on the SHub; see DLP 2199. For the configuration of QoS Threshold Crossing Alerts (TCA); see DLP 1202.

Configure multicast: i ii iii iv For the configuration of the multicast service in the system; see DLP 2136. For the configuration of a multicast VLAN; see DLP 2137. For the configuration of a multicast channel; see DLP 2138. For the configuration of the multicast service on a user port; see DLP 2198.

NTP 2108-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 2108 Configure services

Configure DHCP Relay: i ii iii iv For the configuration of the DHCP relay agent in iBridge mode; see DLP 2139. For the configuration of the DHCP relay agent in router mode; see DLP 2140. For the configuration of the DHCP relay agent in forwarder mode; see DLP 2141. For the configuration of DHCP MAC concentration in forwarder mode; see DLP 2185.

Configure the authentication settings: i ii iii iv For the configuration of the security domain: see DLP 2142. For the configuration of RADIUS; see DLP 2144. For the configuration of 802.1x authentication; see DLP 1145. For the configuration of operator authentication via RADIUS; see DLP 2181.

Configure the PPP relay settings: i ii For the configuration of PPPoE relay on the LT; see DLP 1146. For the configuration of PPPoX cross-connect; see DLP 1147.

10

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, <R4.1, behaviour where the redundancy was by default enabled); see DLP 2114. Note 2 For a forced NT switchover (for example, when an active NT board must be replaced in a redundant configuration); see DLP 1219.
11 If necessary, configure link aggregation. Link aggregation is used to aggregate two or more physical links from one switch to another: i ii 12 For the configuration of link aggregation; see DLP 2105. For the configuration of link aggregation on the NELT-B; see DLP 1271

If necessary, configure Multiple Spanning Tree Protocol (MSTP): i ii to configure MSTP on the SHub; see DLP 2200 to configure MSPT on the NELT-B; see DLP 1270

13

If necessary, configure routing protocols such as OSPF and RIP. The configuration is optional (depends if the network elements which are connected to the ISAM, are using those protocols). The routing protocols are handled in the Shub. i ii For the configuration of Open Shortest Path First (OSPF) management; see DLP 2107. For the configuration of Routing Information Protocol (RIP) management; see DLP 2108.

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

NTP 2108 Configure services

14

Configure integrated VoIP service: i ii For the configuration MEGACO-based VoIP service, see DLP 2216 For the configuration of the SIP-based VoIP service, see DLP 2196

Note 1 For POTS-only service:


Either the MEGACO-based or the SIP-based VoIP service shall be configured. The system does not support both integrated VoIP services to run in parallel for the POTS only service.

Note 2 For POTS + ISDN BRI service one of the following applies:

only the MEGACO-based VoIP service is configured, supporting both the POTS and the ISDN BRI services simultaneously. the SIP-based VoIP Service is configured to support the POTS service and the MEGACO-based VoIP service is configured to support the ISDN BRI service. Only in this latter case does the system allow both integrated VoIP services to run in parallel.

15 16

Configure an ANCP session; see DLP 2186. Configure the Path Connectivity Check Protection (PCCP) group; see DLP 2222.

Note Only applicable when the MEGACO-based VoIP service is configured.

17 18 19

Configure the p-bit counter on a VLAN port; see DLP 1225. If required, configure fairness SLA on the NELT-B; see DLP 1282. STOP. This procedure is complete.

NTP 2108-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 2115 Monitor alarms


Purpose
This procedure provides the steps to monitor the alarms on the NE.

Procedure
Proceed as follows to monitor the alarms: 1 2 3 Create an alarm snapshot table; see DLP 2154. Monitor the alarms; see DLP 2155. STOP. This procedure is complete.

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

NTP 2115 Monitor alarms

NTP 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

NTP 2116 Perform software management


Purpose
This procedure provides the steps to perform software management on the NE.

Procedure
The following steps can be used to perform software management: 1 2 3 4 5 Management of the NT and SHub database; see RTP 2100. Management of the Overall Software Packages; see DLP 1159. View the version of the SHub software; see DLP 2160. Management of Customer Dependant Engineering (CDE) profiles; see DLP 1220. STOP. This procedure is complete.

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

NTP 2116 Perform software management

NTP 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

NTP 2117 Modify system parameters


Purpose
This procedure lists the procedures for system parameter modification.

Procedure
The steps below show the procedures for modifying different system parameters: 1 2 3 4 5 6 Modify the system management IP parameters; see DLP 2168. Change the external management VLAN; see DLP 2162. Configure an ARP table entry; see DLP 2150. Configure filtering on the SHub; see DLP 2132. Configure static MAC addresses; see DLP 2180. STOP. This procedure is complete.

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

NTP 2117 Modify system parameters

NTP 2117-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 2120 Troubleshooting the network


Purpose
The following troubleshooting commands can be used:

Ping: The ping command lets you verify that a particular IP address exists and can accept requests. Ping is used diagnostically to ensure that a host computer you are trying to reach is actually operating. Ping can also be used with a host that is operating to see how long it takes to get a response back. Traceroute: Traceroute is a utility that traces the route in the network for an IP address. It also calculates and displays the amount of time each hop took. The utility initiates the sending of a packet (using the Internet Control Message Protocol (ICMP)), including in the packet a Time To Live (TTL) value that is designed to be exceeded by the first router that receives it, which will return a Time Exceeded message. This enables traceroute to determine the time required for the hop to the first router. Increasing the time limit value, it sends the packet again so that it will reach the second router in the path to the destination, which returns another Time Exceeded message, and so forth. Traceroute determines when the packet has reached the destination by including a port number that is outside the normal range. When it's received, a Port Unreachable message is returned, enabling traceroute to measure the time length of the final hop. As the tracerouting progresses, the records are displayed for you hop by hop.

Procedure
The following troubleshooting commands can be used: 1 2 Ping command; see DLP 2164. Traceroute command; see DLP 2165.

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

NTP 2120 Troubleshooting the network

3 4

Port mirroring; see DLP 2223. STOP. This procedure is complete.

NTP 2120-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 2121 Manage an SNMP proxy CPE


Purpose
The Customer Premises Equipment (CPE) management functionality allows the operator to troubleshoot the CPE at all protocol layers when problems are experienced with either misconfiguration of the CPE or with the end-user's terminals. It allows to have a clear indication if a problem is situated before or after the demarcation point of a telecom carriers responsibility. Additionally, CPE management offers the possibility to control the SW upgrade of CPE by downloading from the network. The function of xDSL CPE remote management includes configuration, monitoring, maintenance and upgrade of an xDSL Remote Terminal. The network reference model is illustrated in Figure NTP 2121-1.
Figure NTP 2121-1: Network Reference Model
Network Management Entity

CPE-MM

RMI

User Management Entity

LMI NE xDSL CPE

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

NTP 2121 Manage an SNMP proxy CPE

The CPE-MM is responsible for the management of CPE. The following interfaces are defined:

LMI: interface between NE and CPE RMI: interface between CPE-MM and NE

Three channels are present on the LMI interface:

Service data channel: This channel is used to carry data traffic (for example, HSI traffic). Basic management channel: This channel is used to carry CPE remote management information. Auxiliary management channel: This channel is used to carry SW download, PPPoE testing, PING testing, bandwidth testing and so on.

The NE relays the SNMP messages between CPE-MM and CPE.

Note This NTP is for CPE management using SNMP.

Procedure
To configure SNMP proxy CPE management, you need to perform the following tasks: 1 2 Configure SNMP proxy CPE management; see DLP 2166. STOP. This procedure is complete.

NTP 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

NTP 2122 Cluster management


Purpose
As a result of the massive deployment of xDSL, many more DSLAMs are provisioned in the network. They are mostly managed separately, which makes the management workload heavy and complicated. To simplify the management workload of the operator, cluster management groups multiple DSLAMs as one logical management domain. The logical management domain of a cluster is formed by a physically interconnected group of DSLAMs. The operator can organize its clusters according to, for example, physical location. Topology display will present the connectivity and status of DSLAMs in a connected environment, possibly over more than one cluster. Moreover, separately managed DSLAMs use more public IP addresses, which are limited. Figure NTP 2122-1 shows an example of the cluster management topology.
Figure NTP 2122-1: Cluster Management Topology
Management Command to Cluster 2

Cluster No. 2 (A logical DSLAM)

EMS (AMS)

Single Logical Management Path DSLAM No. 7

Management Command to Cluster 1

Cluster No.1 (A logical DSLAM)

DSLAM No. 8 DSLAM No. 1 DSLAM No. 2

DSLAM No. 9

DSLAM No. 10 DSLAM No. 4 DSLAM No. 5 DSLAM No. 6

DSLAM No. 11

DSLAM No. 3

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

NTP 2122 Cluster management

Procedure
To configure cluster management, you need to perform the following tasks: 1 2 Configure the cluster; see DLP 2169. STOP. This procedure is complete.

NTP 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

NTP 2129 Configure a loopback interface on the SHub


Purpose
Configure a loopback interface on the SHub.

Prerequisites
The following prerequisite must be fulfilled:

The system must run in single ip-address mode.

Procedure
To configure a loopback interface on the Shub, you need to perform the following tasks: 1 2 3 Configure a host IP address on the NT using a mask 32. Configure an unnumbered interface on the Shub (that is, a VLAN which has the network IP address as numbered interface); see DLP 2204. Configure VRF routes on the SHub:


4 5

a route <host-ip-address-nt/32> via the management VLAN 4093 directly attached. a default route via IP address out of address range of 2.

Configure a default route on the NT via the IP address of the numbered VLAN interface on the SHub. STOP. This procedure is complete.

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

NTP 2129 Configure a loopback interface on the SHub

NTP 2129-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 2133 Configure an enhanced IP router


Purpose
The enhanced IP router has the following adavantages as opposed to the IP router (see NTP 2107):

Subnet and IP next hop support at subscriber side IP routing support for L3 and L2+ boards Easy migration from L2 to L3 model (that is, only the NT configuration needs to be changed to get IP routing without impacting the LT provisioning) IP option support for subscriber

Procedure
Proceed as follows to configure an enhanced IP router: 1 Create a router VRF; see DLP 2123.

Note Only step 2 of this DLP must be executed.

2 3

Create an xDSL Ethernet user and add this user to a VLAN on the LT; see DLP 1124. STOP. This procedure is complete.

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

NTP 2133 Configure an enhanced IP router

NTP 2133-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

Detailed Level Procedures (DLP)

DLP 1100 Set up a local CLI session or a local TL1 session DLP 1112 Lock and unlock equipment DLP 1113 Configure the equipment DLP 1117 Configure a VLAN on the LT for C-VLAN cross-connect DLP 1118 Configure a VLAN on the LT for S-VLAN cross-connect DLP 1119 Configure a VLAN on the LT for S+C-VLAN cross-connect DLP 1120 Configure a VLAN on the LT for C-iBridge DLP 1124 Create an xDSL/native Ethernet user and add this user to a VLAN on the LT DLP 1129 Create xDSL profiles DLP 1130 Configure xDSL bonding DLP 1134 Configure QoS DLP 1145 Configure 802.1x DLP 1146 Configure PPPoE relay on LT DLP 1147 Configure PPPoX cross-connect DLP 1151 Shut down and restart the NT DLP 1152 Reboot the system

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

DLP 1153 Shut down and restart individual equipment DLP 1159 Manage OSWP DLP 1163 Modifying xDSL profiles DLP 1170 Configure SSH and SFTP DLP 1173 Switch a user from ADSL to VDSL DLP 1174 Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect DLP 1182 Configure SHDSL DLP 1183 Configure IMA on SHDSL spans DLP 1187 Configure global VLAN parameters on the LT DLP 1188 Configure custom PSD points DLP 1189 Configure VDSL2 virtual noise values DLP 1190 Configure threshold crossing alerts DLP 1197 View port configuration and operational data on LT DLP 1201 Configure protocol tracing DLP 1202 Configure QoS threshold crossing alerts DLP 1203 Configure general security settings DLP 1205 Configure Link Related Ethernet OAM DLP 1206 Configure an xDSL DPBO profile DLP 1207 Modify an xDSL DPBO profile DLP 1208 Configure xDSL power back off DLP 1212 Create an IP user/subnet DLP 1215 Configure the impulse noise sensor on an xDSL line DLP 1217 Configure the xDSL overrule data DLP 1219 Forced NT switchover DLP 1220 Manage the CDE profile DLP 1221 Manage troubleshooting counters on LT DLP 1225 Configure the p-bit counter on a VLAN port
December 2011 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 1232 Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge DLP 1253 Configure the third-party equipment management port on the 7356 FD REM DLP 1255 Configure a port on the NELT-B LT DLP 1257 Configure a line with an xDSL RTX profile DLP 1258 Modify an xDSL RTX profile DLP 1270 Configure spanning tree on the NELT-B LT DLP 1271 Configure link aggregation on the NELT-B LT DLP 1282 Configure the fairness SLA on the NELT-B LT DLP 1283 Troubleshooting congestion on the NELT-B LT DLP 1291 Configure a Vectoring Control Entity profile and associate it to a board DLP 1292 Modify a Vectoring Control Entity profile DLP 1293 Delete a Vectoring Control Entity profile DLP 1294 Configure or modify the mapping between the VP board and the SLV LT boards DLP 1295 Configure a line with an xDSL vectoring profile DLP 1296 Modify an xDSL vectoring profile DLP 1297 Delete an xDSL vectoring profile DLP 1298 Monitor xDSL vectoring lines DLP 2101 Create operator profiles and instances DLP 2103 Configure system parameters DLP 2105 Configure link aggregation usage DLP 2107 Manage OSPF DLP 2108 Configure RIP DLP 2109 Configure SNMP and trap management DLP 2110 Manage alarms DLP 2111 Plan, replan, and unplan equipment

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

DLP 2114 Configure NT redundancy DLP 2115 Create a L2-terminated forwarder VLAN DLP 2116 Create a L2-terminated router VLAN DLP 2121 Add a network/LAG port to a VLAN in the SHub DLP 2122 Create a forwarding VRF DLP 2123 Create a router VRF DLP 2125 Create an IPoA user DLP 2126 Create an IPoE user DLP 2128 Add an LT port to a VLAN on the SHub DLP 2132 Configure filtering on the NT DLP 2136 Configure the multicast service in the system DLP 2137 Configure a multicast VLAN DLP 2138 Configure a multicast channel DLP 2139 Configure DHCP relay agent in iBridge mode DLP 2140 Configure DHCP relay agent in router mode DLP 2141 Configure DHCP relay agent in forwarder mode DLP 2142 Configure the system security domain DLP 2144 Configure RADIUS DLP 2150 Configure ARP table entry DLP 2154 Create a snapshot alarm table DLP 2155 Monitor alarms DLP 2157 Manage the SHub database DLP 2160 View version of the SHub software DLP 2162 Modify the external management VLAN DLP 2164 Ping another host DLP 2165 Perform a traceroute action DLP 2166 Configure SNMP proxy CPE management

December 2011 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 DLP 2168 Modify the system management IP parameters DLP 2169 Configure cluster management DLP 2171 Enable EMS management DLP 2172 Create a default operator profile DLP 2175 Configure system management IP parameters DLP 2176 Performance monitoring commands DLP 2177 Configure SFP downlink ports DLP 2179 Configure system logging DLP 2180 Configure static MAC addresses DLP 2181 Configure operator authentication via RADIUS DLP 2185 Configure DHCP MAC concentration in forwarder mode DLP 2186 Configure ANCP session DLP 2191 Enable dual tagging in the SHub DLP 2195 Configure general bridge parameters on the LT DLP 2196 Configure Voice SIP DLP 2198 Configure the multicast service on a user port DLP 2199 Configure QoS on the SHub DLP 2200 Configure Spanning Tree on the SHub DLP 2204 Configure an unnumbered IP interface on the SHub DLP 2209 Configure vMAC DLP 2210 View the status of various system parameters DLP 2211 Configure SFP uplink ports DLP 2213 Enable OAM counters DLP 2214 Configure connectivity fault management DLP 2216 Configure Voice MEGACO DLP 2222 Create the PCCP group

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

DLP 2223 Configure SHub port mirroring DLP 2224 Change shelf mode DLP 2236 Configure the enhanced system clock synchronization DLP 2273 External Packet Forwarding

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

Detailed Level Procedures (DLP)

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

-7

Detailed Level Procedures (DLP)

-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

Detailed Level Procedures (DLP)

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

-9

Detailed Level Procedures (DLP)

-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 1100 Set up a local CLI session or a local TL1 session


Purpose
This procedure provides the steps to set up a local CLI session or a local TL1 session with the ISAM via the local craft connection.

Note For security purposes, it is advised to change the default user name and password both for CLI sessions and for TL1 sessions when you log in for the first time.

Procedure
Proceed as follows to set up a local CLI session or a local TL1 session: 1 Enter LOGIN to start up the command line interface. The logon prompt appears. 2 After the question Would you like a CLI(C) or a TL1 login(T) or TL1 normal session(N)? [N]:, type C and press Enter.

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

DLP 1100 Set up a local CLI session or a local TL1 session

Enter the default user name (isadmin) and password (i$@mad-) that were provided to you with the system. If you do not have the default user name and password, contact Alcatel-Lucent technical support.

Note For remote CLI, after you set up the management channel, you can set up a remote CLI session using Telnet.

Warning After three unsuccessful login attempts (that is, each consisting of three failed username/password prompts), the ISAM will block all login attempts from the IP address or from the craft port from which the three unsuccessful login attempts were initiated for a period of two minutes.
If the user fails to successfully log in after this timeout has expired, the ISAM extends the blocking period with two minutes and will continue to extend this blocking period with two minutes for each failed login attempt. 4 5 Log out. Enter LOGIN to start up the command line interface. The logon prompt appears. 6 7 After the question Would you like a CLI(C) or a TL1 login(T) or TL1 normal session(N)? [N]:, type T or N and press Enter. Enter the default user name (SUPERUSER) and password (ANS#150) that were provided to you with the system. If you do not have the default user name and password, contact Alcatel-Lucent technical support. STOP. This procedure is complete.

DLP 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

DLP 1112 Lock and unlock equipment


Purpose
This procedure provides the steps to lock and unlock plug-in units.

Procedure
Proceed as follows to lock and unlock a plug-in unit: 1 Lock a plug-in unit with the following command:
configure equipment slot (index) no unlock

Unlock a plug-in unit with the following command:


configure equipment slot (index) unlock

STOP. This procedure is complete.

Configuration example (Config#1): configure equipment slot lt:1/1/5 no unlock configure equipment slot lt:1/1/5 unlock

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

DLP 1112 Lock and unlock equipment

DLP 1112-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 1113 Configure the equipment


Purpose
The system will auto-configure a number of equipment items and detect the presence of the equipment at startup. It may therefore not be necessary to configure or reconfigure all equipment. The procedure in this section is a guideline only. Refer to the CLI Command Guide for FD 24Gbps NTdocument for a complete description of the commands used in this procedure.

Procedure
Proceed as follows to configure the NE equipment: 1 Configure the description of the system with the following command:
configure equipment isam (no) description <Description>

Configure the rack with the following command:


configure equipment rack (index) (no) description <Description>

Configure the subrack or shelf with the following command:


configure equipment shelf (index) class <Equipm::ShelfClass> (no) planned-type (no) lock (no) mode (no) description <Description-127>

Enable or disable environment monitoring with the following command:


configure equipment envbox (no) enable-supervise

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

DLP 1113 Configure the equipment

Use any of the following commands to view and verify the configuration of the system: a The following command shows the system configuration (planned type, actual type) and status. This configuration is fixed and hardcoded:
show equipment isam detail

The following command shows the rack configuration and status (planned type, actual type):
show equipment rack (rack) detail

The following command shows the shelf configuration and status (planned type, actual type, administrative status, operational status, error status, availability,...):
show equipment shelf (shelf) detail

The following command shows the configuration and status of all slots (planned type, actual type, administrative status, operational status, error status, availability, board identification parameters, LT restart time, LT restart cause,...):
show equipment slot (slot) detail

The following command shows the configuration and status of appliques (planned type, actual type, administrative status, operational status, error status, availability, board identification parameters,...):
show equipment applique (applique) detail

The following command shows the profile ID associated with a profile name, the description of the profile and the board type associated with a given profile:
show equipment capab-profile (profilename) detail

STOP. This procedure is complete.

Configuration example (Config#1): configure equipment isam description Magabir Plant configure equipment rack 1 description ***Main Rack*** configure equipment shelf 1/1 description Testshelf_Antwerp configure equipment envbox enable-supervise show equipment rack 1 detail show equipment shelf 1/1 detail show equipment slot lt:1/1/5 detail show equipment applique iont:1/1 detail

DLP 1113-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 1117 Configure a VLAN on the LT for C-VLAN cross-connect


Purpose
This procedure provides the steps to configure a VLAN on the LT for C-VLAN cross-connect. 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.

Note The operator does not have to identify any specific LT; the ISAM will find out the correct LT when the operator adds the (single) subscriber on the C-VLAN cross-connect.

Figure DLP 1117-1: Configure a VLAN on the LT for C-VLAN cross-connect


DLP

C-VLAN CC LT

NT

ISAM

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

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

Procedure
Proceed as follows to configure a VLAN on the LT for C-VLAN cross-connect: 1 Create a C-VLAN on the LT with the following command:
configure vlan id <Vlan::UVlanIndex> (no) name <Vlan::AdminString> mode cross-connect (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

If required, modify the C-VLAN on the LT with the following command:


configure vlan id (vlanid) (no) name <Vlan::AdminString> mode <Vlan::SystemMode> (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) dhcpv6-linerate <Vlan::Dhcpv6-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime> (no) l2cp-transparent (no) in-qos-prof-name <Qos::QosIngressProfileName> (no) ipv4-mcast-ctrl (no) ipv6-mcast-ctrl (no) mac-mcast-ctrl (no) dis-proto-rip (no) proto-ntp (no) dhcpv6-itf-id (no) dhcpv6-remote-id (no) dhcpv6-trst-port (no) enterprise-number (no) icmpv6-sec-fltr (no) dis-ip-antispoof (no) unknown-unicast

STOP. This procedure is complete.

DLP 1117-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 1117 Configure a VLAN on the LT for C-VLAN cross-connect

Configuration example (Config#1): configure vlan id 301 name "ISP_C_VLAN_301" mode cross-connect configure vlan id 301 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan id 300 name "ISP_C_VLAN_300" mode cross-connect configure vlan id 300 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan id 298 name "ISP_C_VLAN_298" mode cross-connect configure vlan id 298 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan id 299 name "ISP_C_VLAN_299" mode cross-connect configure vlan id 299 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id

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

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

DLP 1117-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 1118 Configure a VLAN on the LT for S-VLAN cross-connect


Purpose
This procedure provides the steps to configure a VLAN on the LT for S-VLAN cross-connect. 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. 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 interfaces pre-configured S-VLAN ID will be assigned.

Note The operator does not have to identify any specific LT; the ISAM will find out the correct LT when the operator adds the (single) subscriber on the C-VLAN cross-connect.

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

DLP 1118 Configure a VLAN on the LT for S-VLAN cross-connect Figure DLP 1118-1: Configure a VLAN on the LT for S-VLAN cross-connect
DLP

S-VLAN CC LT

NT

ISAM

Procedure
Proceed as follows to configure a VLAN on the LT for S-VLAN cross-connect: 1 Create an S-VLAN on the LT with the following command:
configure vlan id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex> name <Vlan::AdminString> mode cross-connect (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>

If required, configure the S-VLAN on the LT with the following command:


configure vlan id (vlanid) (no) name <Vlan::AdminString> mode <Vlan::SystemMode> (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) dhcpv6-linerate <Vlan::Dhcpv6-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime> (no) l2cp-transparent (no) in-qos-prof-name <Qos::QosIngressProfileName> (no) ipv4-mcast-ctrl

DLP 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

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

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

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

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan id stacked:400:0 name IPS_S_VLAN-400 mode cross-connect

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

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

DLP 1118-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 1119 Configure a VLAN on the LT for S+C-VLAN cross-connect


Purpose
This procedure provides the steps to configure a VLAN on the LT for S+C-VLAN crossconnect 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. 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 interfaces preconfigured S-VLAN will be assigned. In case of untagged/priority tagged frames, the subscriber interfaces pre-configured C-VLAN and S-VLAN will be assigned.

Note The operator does not have to identify any specific LT; the ISAM will find out the correct LT when the operator adds the (single) subscriber on the S+C-VLAN cross-connect

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

DLP 1119 Configure a VLAN on the LT for S+C-VLAN cross-connect Figure DLP 1119-1: Configure a VLAN on the LT for S+C-VLAN cross-connect
DLP

S+C-VLAN CCs

LT NT

ISAM

Procedure
Proceed as follows to configure a VLAN on the LT for S+C-VLAN cross-connect: 1 Create an S-VLAN on the LT with the following command:
configure vlan id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex> name <Vlan::AdminString> mode layer2-terminated (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime> (no) in-qos-prof-name <Qos::QosIngressProfileName> (no) ipv4-mcast-ctrl (no) ipv6-mcast-ctrl (no) mac-mcast-ctrl (no) proto-ctrl-flags <Vlan::CtrlFlags>

Create a stacked S+C-VLAN on the LT with the following command:


configure vlan id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex> name <Vlan::AdminString> mode cross-connect (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup>

If required, configure the S+C-VLAN on the LT with the following command:


configure vlan id (vlanid) (no) name <Vlan::AdminString> mode <Vlan::SystemMode> (no) priority <Vlan::Priority> (no) vmac-translation

DLP 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

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

(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)

vmac-dnstr-filter vmac-not-in-opt61 broadcast-frames protocol-filter <Vlan::ProtGroup> pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> dhcp-opt-82 circuit-id-dhcp <Vlan::CircuitIdDhcp> remote-id-dhcp <Vlan::RemoteIdDhcp> dhcp-linerate <Vlan::Dhcp-linerate> pppoe-linerate <Vlan::Pppoe-linerate> dhcpv6-linerate <Vlan::Dhcpv6-linerate> circuit-id-pppoe <Vlan::CircuitIdPppoe> remote-id-pppoe <Vlan::RemoteIdPppoe> secure-forwarding aging-time <Vlan::MacAgingTime> l2cp-transparent in-qos-prof-name <Qos::QosIngressProfileName> 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

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan id stacked:500:0 name ISP_SC_VLAN-500 mode layer2-terminated configure vlan id stacked:500:600 name ISP_SC_VLAN-500-600 mode cross-connect

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

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

DLP 1119-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 1120 Configure a VLAN on the LT for C-iBridge


Purpose
This procedure provides the steps to configure a VLAN on the LT for C-iBridge. 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 NSP.

Note The operator does not have to identify any specific LT; the ISAM will automatically configure the iBridge VLAN on all LTs.

Figure DLP 1120-1: Configure a VLAN on the LT for C-iBridge


DLP

C-VLAN iBridge LT

NT

ISAM

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

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

Procedure
Proceed as follows to create a C-VLAN iBridge on the LT: 1 Create an C-VLAN iBridge on the LT with the following command:
configure vlan id <Vlan::UVlanIndex> (no) name <Vlan::AdminString> mode residential-bridge (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

If required, configure the C-VLAN iBridge with the following command:


configure vlan id (vlanid) (no) name <Vlan::AdminString> mode <Vlan::SystemMode> (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) dhcpv6-linerate <Vlan::Dhcpv6-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime> (no) l2cp-transparent (no) dhcpv6-itf-id <Vlan::Dhcpv6InterfaceId> (no) dhcpv6-remote-id <Vlan::Dhcpv6RemoteId> (no) dhcpv6-trst-port <Vlan::Dhcpv6TrstPort> (no) enterprise-number <Vlan::Enterprisenumber> (no) icmpv6-sec-fltr (no) <Qos::QosIngressProfileName> (no) ipv4-mcast-ctrl (no) ipv6-mcast-ctrl (no) mac-mcast-ctrl (no) dis-proto-rip (no) proto-ntp (no) dis-ip-antispoof (no) unknown-unicast

STOP. This procedure is complete.

DLP 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

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

Configuration examples (Config#1): configure vlan id 100 name iBridge-vlan mode residential-bridge configure vlan id 100 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id secure-forwarding configure vlan id 200 name Multicast-vlan mode residential-bridge

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

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

DLP 1120-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 1124 Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
Purpose
This procedure provides the steps to create an xDSL Ethernet user and add this user to a VLAN on the LT.

Note 1 From R3.3 on, the user line interface stack (that is, ATM PVC and bridge ports) can be configured before the xDSL line is provisioned (that is, before an xDSL profile is assigned to an xDSL line).
Also, when an xDSL line is unprovisioned (that is, when the association between the xDSL line and an xDSL profile is deleted), the user line interface stack (ATM PVCs and bridge ports) is preserved.

Note 2 This entails that, when a clean up of the whole interface stack is required, all the ATM PVCs and bridge ports need to be deleted explicitly.

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

DLP 1124 Create an xDSL/native Ethernet user and add this user to a VLAN on the LT Figure DLP 1124-1: Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
VlanPort BridgePort ATM PVC xDSL

DLP

PVID VLAN LT NT

ISAM

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

The LT must be planned; see DLP 2111. The xDSL profiles must have been created; see DLP 1129. A VLAN must have been created: for creation of a C-VLAN cross-connect; see DLP 1117 for creation of a S-VLAN cross-connect; see DLP 1118 for creation of a S+C-VLAN cross-connect; see DLP 1119 for creation of an iBridge; see DLP 1120.

Procedure
Proceed as follows to create an xDSL Ethernet user: 1 Do one of the following: a b 2 For a user on an ADSL line, VDSL2 line, go to step 2 For a native Ethernet user, continue with step 7.

Create an xDSL line with the following command:


configure xdsl line (if-index) service-profile none | <Xdsl::ProfilePointer> | name: <PrintableString> spectrum-profile none | <Xdsl::ProfilePointer> | name:<PrintableString> (no) dpbo-profile <Xdsl::LineDpboProfile> (no) ansi-t1413 (no) etsi-dts

DLP 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

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

(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)

g992-1-a g992-1-b g992-2-a g992-3-a g992-3-b g992-3-l1 g992-3-l2 g992-3-aj 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 <Xdsl::CarrierDataMode> admin-status transfer-mode <Xdsl::TpsTcMode>

Configure the xDSL interface with the following command:


configure interface port xdsl line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> admin-up (no) link-state-trap (no) user <Itf::asamIfExtCustomerId> (no) severity <Itf::asamIfExtAlmReportingSeverity>

Do one of the following: a b For a user on an ADSL line, continue with step 5 For a user on a VDSL or VDSL2 line, continue with step 8.

Create an ATM PVC (or the necessary ATM PVCs) with the following command:
configure atm pvc (port-index) (no) admin-down (no) aal5-encap-type llc-snap | llc-snap-routed | llc-nlpid | vc-mux-bridged-8023 | vc-mux-routed | vc-mux-pppoa | automatic:ip | automatic:ppp | automatic:pppoa | automatic: ipoe-ppp

6 7

Go to step 8. For configuration of a native Ethernet user, see DLP 1255.

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

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

On top of the PVC / EFM / EthPhy, create a bridge port with the following command:
configure bridge port (port) (no) default-priority <Vlan::Priority (no) mac-learn-off (no) max-unicast-mac <Vlan::MaxMac> (no) qos-profile <Vlan::QosProfileName> (no) prio-regen-prof <Vlan::PrioRegenProfile> (no) max-committed-mac <Vlan::ComitMaxMac> (no) mirror-mode <Vlan::MirrorMode> (no) mirror-vlan <Vlan::MirrorVlan>

For each created bridge port, assign a VLAN to the bridge port and, if required, set the priorities applicable for that port with the following command:
configure bridge port (port) vlan-id (index) (no) tag <Vlan::PortUntagStatus> (no) network-vlan <Vlan::StackedVlan> (no) vlan-scope <Vlan::VlanScope> (no) qos <Vlan::QosPolicy> (no) qos-profile <Vlan::QosProfileName> (no) prior-best-effort (no) prior-background (no) prior-spare (no) prior-exc-effort (no) prior-ctrl-load (no) prior-less-100ms (no) prior-less-10ms (no) prior-nw-ctrl

10

Set the PVID with the following command:


configure bridge port (port) pvid (vlan-id)

Note When it needs to be possible to receive single tagged frames at the user side (S-VLAN cross-connect), a specific C-VLAN ID must be used, namely 4097. The command is then:
configure bridge port (port) pvid stacked:<Vlan::SVlanIndex>:4097

11

STOP. This procedure is complete.

Configuration examples (Config#1):

DLP 1124-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 1124 Create an xDSL/native Ethernet user and add this user to a VLAN on the LT

Configuration example for an ADSL user (Config#1): configure xdsl line 1/1/5/12 service-profile 7 spectrum-profile 5 transfer-mode atm admin-up configure atm pvc 1/1/5/12:8:35 aal5-encap-type vc-mux-bridged-8023 configure bridge port 1/1/5/12:8:35 no mac-learn-off configure bridge port 1/1/5/12:8:35 vlan-id 299 configure bridge port 1/1/5/12:8:35 pvid 299

Configuration example for a VDSL or VDSL2 user (Config#1): configure xdsl line 1/1/4/12 service-profile 8 spectrum-profile 4 admin-up configure bridge port 1/1/4/12 configure bridge port 1/1/4/12 vlan-id 300 configure bridge port 1/1/4/12 pvid 300 Configuration example Board Level Vectoring (Config#1): configure xdsl line 1/1/15/[1..48] service-profile 8 spectrum-profile 4 admin-up configure bridge port 1/1/15/1 configure bridge port 1/1/15/1 vlan-id 500 configure bridge port 1/1/15/1 pvid 500 Configuration example System Level Vectoring (Config#1): configure xdsl line 1/1/17/[148] spectrum-profile 4 service-profile 8 admin-up configure xdsl line 1/1/18/[148] spectrum-profile 4 service-profile 8 admin-up configure bridge port 1/1/17/1 configure bridge port 1/1/17/1 vlan-id 501 configure bridge port 1/1/17/1 pvid 501

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

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

DLP 1124-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 1129 Create xDSL profiles


Purpose
This procedure provides the steps to create xDSL profiles.

General
Before you can create an xDSL line, you need to create the necessary profiles. Table DLP 1129-1 describes the two types of profiles.
Table DLP 1129-1: xDSL profiles
Profile Service Profile Spectrum Profile Description Groups a number of parameters related to the xDSL service Groups a number of parameters related to the xDSL spectrum

The parameters of the xDSL spectrum depend largely on the xDSL flavour (ADSL, READSL, ADSL2(+), VDSL, or VDSL2). That is why the configuration of an xDSL spectrum is done in two steps: 1 Configure the general xDSL spectrum parameters: used profiles noise margins power management mode Seamless Rate Adaptation (SRA) parameters Configure the xDSL flavour specific parameters.

Refer to the System Description for FD 24Gbps NT for more information on power management mode, SRA, and so on.

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

DLP 1129 Create xDSL profiles

See TNG 1107 for a full description of the multi-ADSL related parameters and the VDSL related parameters.

Procedure
Proceed as follows to create an xDSL profile: 1 Create an xDSL service profile with the following command:
configure xdsl service-profile (index) name <AsamProfileName> version <SignedInteger> (no) ra-mode-down <Xdsl::RAModeDownType> (no) ra-mode-up <Xdsl::RAModeUpType> (no) min-bitrate-down <Xdsl::BitRate> (no) min-bitrate-up <Xdsl::BitRate> (no) plan-bitrate-down <Xdsl::BitRate> (no) plan-bitrate-up <Xdsl::BitRate> (no) max-bitrate-down <Xdsl::BitRate> (no) max-bitrate-up <Xdsl::BitRate> (no) max-delay-down <Xdsl::InterleavingDelay> (no) max-delay-up <Xdsl::InterleavingDelay> (no) imp-noise-prot-dn <Xdsl::ImpNoiseProtection> (no) imp-noise-prot-up <Xdsl::ImpNoiseProtection> (no) inp-wo-erasure-dn (no) inp-wo-erasure-up (no) min-l2-br-down <Xdsl::BitRate>

Note The value of min-bitrate-down is also used for the calculation of the available bandwidth for multicast; see DLP 2136.

Activate an xDSL service profile with the following command:


configure xdsl service-profile (index) active

Note 1 The xDSL service profile must be activated within 15 minutes after it has been created, otherwise it will be deleted. Note 2 The activation parameter can also be included in step 1, but then no modification of the parameters is possible afterwards (except name, scope and version; see DLP 1163).
3 Create an xDSL spectrum profile and configure the parameters common to all the DSL flavors with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> local-profile version <SignedInteger> (no) dis-ansi-t1413 (no) dis-etsi-dts (no) dis-g992-1-a

DLP 1129-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 1129 Create xDSL profiles

(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) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

dis-g992-1-b dis-g992-2-a dis-g992-3-a dis-g992-3-b g992-3-l1 g992-3-l2 g992-3-aj g992-3-am g992-5-a g992-5-b ansi-t1.424 dis-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 min-noise-down <Xdsl::NoiseMargin> min-noise-up <Xdsl::NoiseMargin> trgt-noise-down <Xdsl::NoiseMargin> trgt-noise-up <Xdsl::NoiseMargin> max-noise-down <Xdsl::NoiseMarginPlus> max-noise-up <Xdsl::NoiseMarginPlus> carrier-mask-down <Xdsl::CarrierMaskDown> carrier-mask-up <Xdsl::CarrierMaskUp> rf-band-list <Xdsl::RFBand> power_mgnt_mode <Xdsl::LinePowerMgtMode> l0-time <Xdsl::LineTime> l2-time <Xdsl::LineTime> l2-agpow-red-tx <Xdsl::L2Atpr> modification <Xdsl::ModifyStatus> rau-noise-down <Xdsl::NoiseMargin> rau-noise-up <Xdsl::NoiseMargin> rau-time-down <Xdsl::RaTime> rau-time-up <Xdsl::RaTime> rad-noise-down <Xdsl::NoiseMargin> rad-noise-up <Xdsl::NoiseMargin> rad-time-down <Xdsl::RaTime> rad-time-up <Xdsl::RaTime> l2-agpw-to-red-tx <Xdsl::LineL2Atpr>

Configure the artificial noise (that is, the transmitter-referred artificial noise level to be used as additional noise source at the downstream transmitter) with the following command:
configure xdsl spectrum-profile (index) artificial-noise-down (psd-point) (no) frequency <Xdsl::CustFreq> (no) psd <Xdsl::CustPsd>

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

DLP 1129 Create xDSL profiles

If the xDSL type is ADSL or ADSL2, then the ADSL and ADSL2 specific part of an xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) adsl-adsl2 (no) proprietary-feat (no) propr-feat-value <Xdsl::ProprFeatValue> (no) max-agpowlev-down <Xdsl::PowerLevel> (no) max-agpowlev-up <Xdsl::PowerLevel> (no) max-psd-down <Xdsl::Adsl2PowerSpectralDensityDown> (no) max-psd-up <Xdsl::Adsl2PowerSpectralDensityUp> (no) pbo-mode-up (no) max-recv-power-up <Xdsl::RxPowerLevel> (no) psd-mask-up <Xdsl::Adsl2PsdMaskUp>

If the xDSL type is ADSL2+, then the ADSL2+ specific part of an xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) adsl2-plus (no) proprietary-feat (no) propr-feat-value <Xdsl::ProprFeatValue> (no) max-agpowlev-down <Xdsl::PowerLevel> (no) max-agpowlev-up <Xdsl::PowerLevel> (no) max-psd-down <Xdsl::Adsl2PlusPowerSpectralDensityDown> (no) max-psd-up <Xdsl::Adsl2PlusPowerSpectralDensityUp> (no) pbo-mode-up (no) max-recv-power-up <Xdsl::RxPowerLevel> (no) psd-shape-down <Xdsl::Adsl2PlusPsdShapeDown> (no) psd-mask-up <Xdsl::Adsl2PlusPsdMaskUp>

If the xDSL type is Reach Extended ADSL2 (READSL2), then the READSL2 specific part of an xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) re-adsl (no) proprietary-feat (no) propr-feat-value <Xdsl::ProprFeatValue> (no) max-agpowlev-down <Xdsl::PowerLevel> (no) max-agpowlev-up <Xdsl::PowerLevel> (no) max-psd-down <Xdsl::ReAdsl2PowerSpectralDensityDown> (no) max-psd-up <Xdsl::ReAdsl2PowerSpectralDensityUp> (no) pbo-mode-up (no) max-recv-power-up <Xdsl::RxPowerLevel>

If the xDSL type is VDSL, then the VDSL specific part of an xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) vdsl (no) proprietary-feat (no) propr-feat-value <Xdsl::ProprFeatValue> (no) vdsl-band-plan <Xdsl::VdslBandPlan> (no) optional-band <Xdsl::OptionalBandUsage> (no) optional-endfreq <Xdsl::OptionalBandEndFreq> (no) adsl-band <Xdsl::AdslBandUsage> (no) max-agpowlev-down <Xdsl::VdslPowerLevel> (no) max-agpowlev-up <Xdsl::VdslPowerLevel> (no) psd-shape-down <Xdsl::VdslPsdShapeDown> (no) psd-shape-up <Xdsl::VdslPsdShapeUp> (no) pbo-mode-down (no) pbo-mode <Xdsl::PboModeVdsl>

DLP 1129-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 1129 Create xDSL profiles

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

rx-psd-shape-up <Xdsl::RxVdslPsdShapeUp> ghstones-pwr-mode <Xdsl::GhsTonesTxPwr> max-band <Xdsl::VdslMaxBandNum> max-freq <Xdsl::VdslMaxFrequency> m-psd-level-down <Xdsl::MaxPsdDown> m-psd-level-up <Xdsl::MaxPsdUp> psd-pbo-par-a-up <Xdsl::ABParamType> psd-pbo-par-b-up <Xdsl::ABParamType> cust-psd-sc-down <Xdsl::PsdScaleBit> cust-psd-ty-down <Xdsl::PsdTypeBit> cust-rx-psd-sc-up <Xdsl::PsdScaleBit> cust-rx-psd-ty-up <Xdsl::PsdTypeBit> opt-startfreq <Xdsl::OptionalBandStartFreq>

Configure the transmission power of the G.hs tones in VDSL environment with the following command:
configure xdsl spectrum-profile (index) vdsl ghstone-set-pwr-ctrl (no) a43 standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl> (no) b43 standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl> (no) a43c standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl> (no) v43 standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl>

10

If the xDSL type is VDSL2, then the VDSL2 specific part of an xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) vdsl2 (no) proprietary-feat (no) propr-feat-value <Xdsl::ProprFeatValue> (no) max-agpowlev-down <Xdsl::VdslPowerLevel> (no) max-agpowlev-up <Xdsl::VdslPowerLevel> (no) psd-shape-down <Xdsl::Vdsl2PsdShapeDown> cs-psd-shape-dn <Xdsl::Vdsl2CustPsdShape> cs-psd-shape-up <Xdsl::Vdsl2CustPsdShape> (no) psd-shape-up <Xdsl::Vdsl2PsdShapeUp> (no) rx-psd-shape-up <Xdsl::RxVdslPsdShapeUp> (no) psd-pbo-e-len-up <Xdsl::PsdPboElectrLength> (no) m-psd-level-down <Xdsl::MaxPsdDown> (no) m-psd-level-up <Xdsl::MaxPsdUp> (no) psd-pbo-par-a-up <Xdsl::ABParamType> (no) psd-pbo-par-b-up <Xdsl::ABParamType> (no) v-noise-snr-down <Xdsl::SnrmMode> (no) v-noise-snr-up <Xdsl::SnrmMode> (no) v-noise-psd-down <Xdsl::VirtualNoisePsdDownType> (no) v-noise-psd-up <Xdsl::VirtualNoisePsdUpType> (no) cust-psd-sc-down <Xdsl::PsdScaleBit> (no) cust-psd-ty-down <Xdsl::PsdTypeBit> (no) cust-psd-sc-up <Xdsl::PsdScaleBit> (no) cust-psd-ty-up <Xdsl::PsdTypeBit> (no) cust-rx-psd-sc-up <Xdsl::PsdScaleBit> (no) cust-rx-psd-ty-up <Xdsl::PsdTypeBit>

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

DLP 1129 Create xDSL profiles

11

Activate an xDSL spectrum profile with the following command:


configure xdsl spectrum-profile (index) active

12

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl service-profile 7 name ADSL_profile version 1 configure xdsl service-profile 7 active configure xdsl service-profile 8 name VDSL_profile version 1 min-bitrate-down 25000 min-bitrate-up 25000 plan-bitrate-down 40000 plan-bitrate-up 27000 max-bitrate-down 262143 max-bitrate-up 262143 configure xdsl service-profile 8 active configure xdsl service-profile 10 name XSRVC_0_0 version 1 min-l2-br-down 0 configure xdsl service-profile 10 ra-mode-up automatic min-bitrate-up 0 plan-bitrate-up 0 max-bitrate-up 0 max-delay-up 16 imp-noise-prot-up 0 no inp-wo-erasure-up configure xdsl service-profile 10 ra-mode-down automatic min-bitrate-down 0 plan-bitrate-down 0 max-bitrate-down 0 max-delay-down 16 imp-noise-prot-dn 0 no inp-wo-erasure-dn configure xdsl service-profile 10 active configure xdsl spectrum-profile 4 name vdsl_profile version 1 configure xdsl spectrum-profile 4 dis-ansi-t1413 dis-etsi-dts dis-g992-1-a dis-g992-1-b dis-g992-2-a dis-g992-3-a dis-g992-3-b dis-etsi-ts g993-2-8a g993-2-8b g993-2-8c g993-2-8d g993-2-12a g993-2-12b g993-2-17a g993-2-30a configure xdsl spectrum-profile 4 active configure xdsl spectrum-profile 5 name adsl_profile version 1 configure xdsl spectrum-profile 5 active configure xdsl spectrum-profile 22 name "approved-profile" configure xdsl spectrum-profile 22 active

DLP 1129-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 1130 Configure xDSL bonding


Purpose
xDSL bonding allows traffic to be carried to and from a single logical subscriber interface over multiple physical xDSL lines.

Note xDSL is ADSL or VDSL.

This procedure provides the steps to configure xDSL bonding.

Bonding services
It offers the following services:

Extended reach of xDSL service Provisioning of standard xDSL services to subscribers that cannot receive these services over a single xDSL line Higher bit rate services

Bonding levels
Different bonding levels can be configured, depending on the LT board capabilities and board type (ADSL or VDSL)

Odd-even adjacent line bonding (for ATM/ADSL lines) Intra-LT line bonding (for ATM/ADSL lines and for PTM/VDSL lines)

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

DLP 1130 Configure xDSL bonding

Note 1 The following applies to these xDSL lines in case of odd-even adjacent line bonding:

The two lines used for xDSL bonding must be subsequent lines The first line must be an odd line ATM PVC, must be configured AFTER configuring the bonding group

Note 2 The following applies to the first line (also known as bonding group index):

Configuration of parameters such as atm pvc, bridge port, and so on, must be done on that first line. Refer to DLP 1124 for the configuration procedure.

Prerequisites
The following prerequisites must be fulfilled before xDSL bonding can be configured:

The The DLP The

LT must be planned;see DLP 2111. xDSL profiles with the correct transfert mode must have been created; see 1129. transfert mode of the xDSL lines must be correct: If the default transfert mode of the lines is the required transfert mode, no configuration of the lines is necessary. If the default transfert mode of the lines is not the required transfert mode, the xDSL line/user must be configured; see DLP 1124.

Procedure
Proceed as follows to manage an xDSL bonding group: 1 Do you want to: a b 2 Create an xDSL bonding group, go to step 2 Delete an xDSL bonding group, go to step 4

Create a bonding group as follows: i Configure an xDSL bonding group profile with the following command:
configure xdsl-bonding group-profile (index) name <AsamProfileName> local-profile | network-profile version <SignedInteger> (no) min-bitrate-up <Xdsl::Bitrate> (no) min-bitrate-down <Xdsl::Bitrate> (no) plan-bitrate-up <Xdsl::Bitrate> (no) plan-bitrate-down <Xdsl::Bitrate> (no) max-bitrate-up <Xdsl::Bitrate> (no) max-bitrate-down <Xdsl::Bitrate> (no) max-delay-down <Xdsl::InterleavingDelay>

DLP 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

DLP 1130 Configure xDSL bonding

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

max-delay-up <Xdsl::InterleavingDelay> imp-noise-prot-dn <Xdsl::ImpNoiseProtection> imp-noise-prot-up <Xdsl::ImpNoiseProtection> delay-opt-mode-ds <Xdsl::BondingGroupDelayOptimMode> active

Note A bonding group profile can be created in one step (that is, with all the necessary parameters and activation of the bonding group profile). It can also be created in several steps by specifying a few parameters in each step and by activating the bonding group profile in the last step.
ii Configure the bonding group assembly timeout with the following command:
configure xdsl-bonding group-assembly-time <SignedInteger>

Note 1 Default value is zero (0 represents an infinite time), which results in the bonding group remaining down until all lines in this bonding group are up. Note 2 Setting the assembly timer to a certain value (e.g., 120 s) allows the bonding group to become operational once this time is achieved and the minimum configured bandwidth for the bonding group are met, even when not all the lines are in showtime.
iii Create an xDSL bonding group with the following command:
configure xdsl-bonding group (bonding-group-idx) group-profile <Xdsl::GroupProfileIndexWithRemove> | name:<PrintableString>

Note 1 The bonding-group-idx is the primary link number, which is also the bonding group number. Note 2 A primary line will immediately be added to the group when a profile is assigned to a new group.

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

DLP 1130 Configure xDSL bonding

iv

Add links to the xDSL bonding group with the following command:
configure xdsl-bonding group (bonding-group-idx) link (bonding-link-id)

Note 1 A secondary line cannot be added to a group that does not exist yet. Note 2 Removing the prime line will delete the complete group (removing lines is only allowed when the administrative status of the bonding group is down).
v Set the administrative status of an xDSL bonding group to up with the following command:
configure xdsl-bonding group (bonding-group-idx) up

Note The administrative status of an xDSL bonding group cannot be put to up when no group-profile has been assigned to the group yet.

3 4

Go to step 5 The best way to delete a bonding group is to remove the bonding-group profile from the group. Use the following command:
configure xdsl-bonding group (bonding-group-idx) no group-profile configure xdsl-bonding group (bonding-group-idx) group-profile 0

To display information on the xDSL bonding group, the following commands can be used: a View the xDSL bonding profiles with the following command:
show xdsl-bonding profiles [(index)]

View the operational data for the bonding group with the following command:
show xdsl-bonding operational-data group [(if-index)]

View the operational data for the bonding link with the following command:
show xdsl-bonding operational-data link [(bonding-link-id)]

DLP 1130-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 1130 Configure xDSL bonding

View the xDSL bonding failure statistics for near-end, far-end or the group with the following commands:
show xdsl-bonding failure-status near-end [(if-index)] show xdsl-bonding failure-status far-end [(if-index)]] show xdsl-bonding failure-status group [(if-index)]

View the xDSL bonding group summary with the following command:
show xdsl-bonding summary [(index)]

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl-bonding group-profile 1 name XBOND_0_0 local-profile version 1 configure xdsl-bonding group-assembly-time 0 configure xdsl-bonding group-profile 1 min-bitrate-up 0 plan-bitrate-up 0 max-bitrate-up 0 max-delay-up 16 imp-noise-prot-up 0 configure xdsl-bonding group-profile 1 active configure xdsl-bonding group 1/1/5/15 group-profile name:XBOND_0_0 configure xdsl-bonding group 1/1/5/15 link 1/1/5/16 configure xdsl-bonding group 1/1/5/15 up show xdsl-bonding profiles 1 show xdsl-bonding operational-data group 1/1/5/15 show xdsl-bonding operational-data link 1/1/5/15 show xdsl-bonding failure-status near-end 1/1/5/15 show xdsl-bonding failure-status far-end 1/1/5/15 show xdsl-bonding failure-status group 1/1/5/15 show xdsl-bonding summary 1/1/5

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

DLP 1130 Configure xDSL bonding

DLP 1130-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 1134 Configure QoS


Purpose
This procedure provides the steps to configure QoS.

Note In case of S+C VLAN CC, both the S-VLAN and the C-VLAN P-bits are set by the P-bit contract table, port default P-bit, or by the policy action. Note that in this case downstream traffic segregation relies on the P-bits in the C-VLAN tag.

Procedure
Proceed as follows to configure QoS: 1 Configure general QoS parameters (if necessary): i Configure the ATM overhead factor, the EFM overhead factor, and the CAC mode with the following command:
configure qos (no) atm-overhead-fact <Qos::AtmFactor> (no) eth-efm-fact <Qos::EthEfmFactor> (no) enable-alignment (no) cac-mode <Qos::CacMode>

ii

Configure the upstream QoS DSL Control Packet Policer for incoming packets with the following command:
configure qos dsl-ctrl-pkt-policer (no) sustained-rate <Qos::SustainedRate> (no) burst-size <Qos::DslCtrlBurstSize>

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

DLP 1134 Configure QoS

iii

Configure the police rate and burst rate per protocol with the following command:
configure qos trl-pkt-policer (protocol-id) (no) sustained-rate <Qos::SustainedRate> (no) burst-size <Qos::DslCtrlBurstSize>

iv

If required, configure the DSCP to Dot1P Alignment Table for layer 3 forwarded traffic with the following command:
configure qos dscp-map-dot1p (index) dot1p-value <Qos::DscpToDot1PAlign>

Configure the downstream traffic class mapping table (if needed) defining the relationship between the traffic class and the queue and queue drop color, with the following command:
configure qos tc-map-dot1p (index) queue <Qos::Queues> dpcolor <Qos::Color>

vi

Configure the QoS priority bit handling, which is a system-level VLAN-specific parameter, via the command configure vlan (parameter prority-policy) as described in DLP 1187.

Configure the QoS policer profiles with the following command:


configure qos profiles policer (name) committed-info-rate <Qos::CommittedInfoRate> committed-burst-size <Qos::CommittedBurstSize> (no) policer-type <QoS::PolicerType> [excess-info-rate <Qos::ExcessInfoRate>] [excess-burst-size <Qos::ExcessBurstSize>] [coupling-flag <Qos::CouplingFlag>] [color-mode <Qos::ColorMode>] [yellow-action <Qos::YellowAction>] [red-action <Qos::RedAction>] [green-action <Qos::GreenAction>]

Note For more information on configured and actual values for Committed Info Rate (CIR) and Committed Burst size (CBS), see QoS Policer Profile in TNG 2101.
3 Create a QoS marker profile : i Configure a marker for single dot-1P with the following command:
configure qos profiles marker d1p (name) default-dot1p <Qos::ExtVlanSysPrio>

ii

Configure a marker for single DSCP with the following command:


configure qos profiles marker dscp (name) default-dscp <Qos::DscpToDot1PAlignmentDscpIndex> (no) alignment

DLP 1134-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 1134 Configure QoS

iii

Configure a marker for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name) (no) alignment

iv

Configure a codepoint for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name) codepoint (codepoint) (on) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>

Configure a marker for Dot1P and the DSCP contract table with the following command:
configure qos profiles marker d1p-dscp-contract (name) dot1p-value <Qos::ExtVlanSysPrio>

vi

Configure a codepoint for Dot1P and the DSCP contract table with the following command:
configure qos profiles marker d1p-dscp-contract (name) codepoint (codepoint) (no) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>

vii

Configure a marker for Dot1P and single DSCP with the following command:
configure qos profiles marker d1p-dscp (name) default-dscp <Qos::DscpToDot1PAlignmentDscpIndex> default-dot1p <Qos::ExtVlanSysPrio>

viii Configure a marker for Dot1P alignment with the following command:
configure qos profiles marker d1p-alignment (name) (alignment) enable

ix

Configure a marker for dot1p remark table with the following command:
configure qos profiles marker dot1p-remark (name) dot1p-value < Qos::ExtVlanSysPrio> remark-value <Qos::ExtVlanSysPrio >

Note DSCP-to-pbit alignment is only supported on VLAN ports that correspond to the configured pvid and only for untagged IPoE traffic.

Configure a scheduler node profile with the following command:


configure qos profiles scheduler-node (name) priority <Qos::QosPriority> weight <Qos::QosWeight> shaper-profile <Qos::QosShaperProfileName> (no) mcast-inc-shape <Qos::QosMulticastInclShaping>

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

DLP 1134 Configure QoS

Configure a CAC profile with the following command:


configure qos profiles cac (name) res-voice-bandwidth <Qos::BandWidthKBPS> max-mcast-bandwidth <Qos::BandWidthKBPS> res-data-bandwidth <Qos::BandWidthKBPS>

Configure a queue profile (that is, the used algorithm (tail-drop or Random Early Detection (RED)) and threshold(s)) with the following command:
configure qos profiles queue (name) tail-drop:<Qos::MaxThreshold> | red:<Qos::MinThreshold>:<Qos::MaxThreshold>: <Qos::DiscardProbability> | twocolour-taildrop:<Qos::MaxThreshold>: <Qos::MaxThresholdYellow> | twocolourred:<Qos::MinThreshold>:<Qos::MaxThreshold>: <Qos::DiscardProbability>:<Qos::MinThresholdYellow>: <Qos::MaxThresholdYellow>:<Qos::DiscardProbYellow> | gpon-tail-drop:<Qos::MinThreshold>:<Qos::MaxThreshold> | threecolour-taildrop:<Qos::MaxThreshold>: <Qos::MaxThresholdYellow>:<Qos::MaxThresholdRed> | threecolour-red:<Qos::MinThreshold>: <Qos::MaxThreshold>:<Qos::DiscardProbability>: <Qos::MinThresholdYellow>:<Qos::MaxThresholdYellow>: <Qos::DiscardProbYellow>:<Qos::MaxThreshold>: <Qos::DiscardProbability>:<Qos::MinThresholdYellow>: <Qos::MaxThresholdYellow>:<Qos::DiscardProbYellow>: <Qos::MinThresholdRed>:<Qos::MaxThresholdRed>: <Qos::DiscardProbRed>:<Qos::MinQueueSize>:<Qos::MaxQueueSize> (no) unit <Qos::Units>

Use one of the following commands to configure a filter which can be used to build policy actions based on filtering criteria: a To configure a filter using L2 filtering criteria (MAC address, Ethernet type,...), use the following command:
configure qos profiles l2-filter (name) (no) dst-mac-addr <Qos::MacAddrAndMask> (no) src-mac-addr <Qos::MacAddrAndMask> (no) ethertype <Qos::FilterEthernetType> (no) dot1p-priority <Qos::MatchDot1pValue> (no) canonical-format <Qos::FilterCfi> (no) vlan-id <Qos::FilterVlanId>

To configure a filter using L3 filtering criteria (destination IP address, source IP address,...), use the following command:
configure qos profiles l3-filter (name) (no) dst-ip-addr <Ip::AddressAndMaskFull> (no) src-ip-addr <Ip::AddressAndMaskFull> (no) min-dst-port <Qos::L4PortNumber> (no) max-dst-port <Qos::L4PortNumber> (no) min-src-port <Qos::L4PortNumber> (no) max-src-port <Qos::L4PortNumber> (no) dscp-value <Qos::MatchDscpValue> (no) protocol <Qos::Protocol>

DLP 1134-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 1134 Configure QoS

Configure QoS policy action profiless, using the policer profiles created in step 2, with the following command:
configure qos profiles policy-action (name) (no) dscp-value <Qos::SetDscpValue> (no) dot1p-value <Qos::SetDot1pValue> (no) discard-packet (no) shared-policer (no) policer-profile <Policer Profile name>

Configure QoS policy profiles with a set of associated actions. A policy rule contains:

Filter type L2 or L3 filter (see step 7) Precedence of this policy rule Policy action (see step 8).

configure qos profiles policy (name) filter <Qos::PolicyFilter> (no) precedence <Qos::PolicyPrecedence> (no) policy-action <Qos::QosProfileName>

10

Create the QoS session profile: i Configure the session profile table (using policer profiles created in step 1 and marker profiles used in step 3) with the following command:
configure qos profiles session (name) logical-flow-type <Qos::LogicalFlowType> (no) up-policer none | name:<Policer Profile name> (no) down-policer none | name:<Policer Profile name> (no) up-marker none | name:<Marker Profile name>

ii

Configure a list of upstream policy profiles (minimum 2, maximum 16), using policy profiles created in step 9, with the following command:
configure qos profiles session (name) up-policy (Policy name)

iii

Configure a list of downstream policy profiles (minimum 2, maximum 16), using policies created in step 9, with the following command:
configure qos profiles session (name) down-policy (Policy name)

11

Configure an upstream bandwidth profile with the following command:


configure qos profiles bandwidth (name) committed-info-rate <Qos::BwCommittedInfoRate> assured-info-rate <Qos::BwAssuredInfoRate> excessive-info-rate <Qos::BwExcessiveInfoRate> delay-tolerance <Qos::DelayTolerance> )

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

DLP 1134 Configure QoS

12

Configure a shaper profile with the following command:


configure qos profiles shaper (name) committed-info-rate <Qos::ShaperCommittedInfoRate> committed-burst-size <Qos::ShaperCommittedBurstSizeNew> (no) excess-info-rate <Qos::ShaperExcessiveInfoRate> (no) type <Qos::ShaperType>

13

Attach the created session profile to a bridge port with the following command:
configure bridge port <Rack/Shelf/Slot/Port:VCI:VPI> (no) qos-profile <Session-profile>

14

Attach the created queue profile (see step 6) and shaper profile (see step 12) to an interface (can be a DSL port, an SHDSL interface, or an Ethernet link) with the next command:
configure qos interface (index) queue (queue) priority <Qos::QosPriority> weight <Qos::QosWeight> queue-profile <Qos::QosQueueProfileName> shaper-profile <Qos::QosShaperProfileName>]

15

STOP. This procedure is complete.

Configuration example (Config#1): configure qos profiles policer ppUsSap256k committed-info-rate 256 committed-burst-size 32000 configure qos profiles policer ppDsSap3M committed-info-rate 3000 committed-burst-size 96000 configure qos profiles policer ppVoice100k committed-info-rate 100 committed-burst-size 3000 configure qos profiles marker d1p mpUsSap default-dot1p 0 configure qos profiles l3-filter f3pUsVoiceIp src-ip-addr 192.170.0.0/16 configure qos profiles l3-filter f3pDsVoiceIp dst-ip-addr 192.170.0.0/16 configure qos profiles l3-filter l3pUsVodIp dst-ip-addr 192.180.2.2/0 configure qos profiles l3-filter l3pDsVodIp src-ip-addr 192.180.2.2/0 configure qos profiles policy-action apVoice dot1p-value 6 policer-profile name:ppVoice100k configure qos profiles policy-action apVod dot1p-value 3 configure qos profiles policy pcyUpVoice policy-action name:apVoice no precedence filter l3-name:f3pUsVoiceIp DLP 1134-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 1134 Configure QoS

configure qos profiles policy pcyDnVoice policy-action name:apVoice no precedence filter l3-name:f3pDsVoiceIp configure qos profiles policy pcyUpVod policy-action name:apVod filter l3-name:l3pUsVodIp configure qos profiles policy pcyDnVod policy-action name:apVod filter l3-name:l3pDsVodIp

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

DLP 1134 Configure QoS

DLP 1134-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 1134 Configure QoS

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

DLP 1134 Configure QoS

DLP 1134-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 1145 Configure 802.1x


Purpose
This procedure provides the steps to enable, disable, and configure parameters for 802.1x.

Procedure
Proceed as follows to configure 802.1x: 1 Enable 802.1x with the following command:
configure system security pae port-access

Configure the 802.1x parameters with the following command:


configure system security pae authenticator (port) (no) controlled-port <Aaa::PaeControlledPortControl> (no) quiet-period <Aaa::paeQuitTime> (no) tx-period <Aaa::paeTime> (no) supp-timeout <Aaa::paeTime> (no) server-timeout <Aaa::paeTime> (no) max-req <Aaa::paeMaxReq> (no) re-auth-enabled (no) re-auth-period <Aaa::paeReauthPeriod>

Configure the remote authenticator and enable authentication and handshake with the following command:
configure system security pae ext-authenticator (port) (no) authentication (no) init-authreq-off (no) handshake (no) handshake-period <Aaa::PortHandShakePeriod>

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

DLP 1145 Configure 802.1x

Enable initialization control for a port with the following command:


configure system security pae port (port) (no) initialize

Optionally, determine the behavior for 802.1x sessions in case authentication servers are down or unreachable with the following command:
configure system security (no) login-banner <Sec::Banner> (no) welcome-banner <Sec::Banner>

STOP. This procedure is complete.

Configuration example (Config#1): configure system security pae port-access configure system security pae authenticator 1/1/5/12:8:35 controlled-port force-unauthorized server-timeout 20 max-req 5 configure system security pae ext-authenticator 1/1/5/12:8:35 authentication handshake configure system security pae port 1/1/5/12:8:35 initialize

DLP 1145-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 1146 Configure PPPoE relay on LT


Purpose
PPPoE relay needs no configuration. It should only be enabled or disabled on a specific VLAN.
Figure DLP 1146-1: Configure PPPoE relay on the LT
DLP

C 11 VLAN CC Phy S17 +C23 Phy Phy LAG S17 +C29 NT_SHUB VLAN CC VLAN CC LT

iBridge VLAN 19 LT

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

DLP 1146 Configure PPPoE relay on LT

Behavior of the Line ID


The behavior of the line ID is determined by the value of the parameter pppoe-relay-tag. The value of the parameter pppoe-relay-tag can be:

true: if pppoe-relay-tag is set to true, then the values of circuit-id-pppoe and of remote-id-pppoe are irrelevant. The NE adds the vendor-specific tag and always puts the customer-id parameter into the remote-id suboption, and will always generate a string (access node, rack,...) to put in the circuit-id suboption. false (default): if pppoe-relay-tag is false, then the values of circuit-id-pppoe and of remote-id-pppoe are irrelevant. The NE does not add the vendor-specific tag. configurable: if pppoe-relay-tag is set to configurable, then the values of circuit-id-pppoe and of remote-id-pppoe are relevant and subject to the same rules as for DHCP. The NE adds the vendor specific tag according the settings of these suboptions. The DHCP-like rules that apply are that the values of both suboptions cannot be identical (2 x customer-id would result in adding the same configurable string in both suboptions, 2 x notAdd would result in a vendor-specific tag with without suboptions).

In both cases where a string is to be generated (that is, the case where pppoerelaytag is configurable and circuit-id-pppoe is set to physcial-id; and the case where pppoerelaytag is set to true), the string format is identified by:

the configurable syntax parameters (ADSL/EFM): configurable via the loop-id-syntax;see DLP 2103, step 3.

Prerequisite
The following prerequisite must be fulfilled before PPPoE can be enabled on a VLAN:

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

Procedure
Proceed as follows to enable or disable PPPoE relay: 1 Enable PPPoE relay and, if required, configure the vendor-specific tag with the following command:
configure vlan id (vlanid) (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe>

DLP 1146-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 1146 Configure PPPoE relay on LT

Disable PPPoE relay with the following command:


configure vlan id (vlanid) no pppoe-relay-tag

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan id 560 mode residential-bridge name PPPoXVlan560 configure vlan id 560 pppoe-relay-tag configurable circuit-id-pppoe physical-id remote-id-pppoe customer-id pppoe-linerate addactuallinerate configure vlan id 560 no pppoe-relay-tag

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

DLP 1146 Configure PPPoE relay on LT

DLP 1146-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 1147 Configure PPPoX cross-connect


Purpose
This procedure provides the steps to configure PPPoX cross-connect.

Prerequisites
The following prerequisites must be fulfilled before PPPoX cross-connect can be configured:

A cross-connect VLAN or an iBridge VLAN must have been created; see DLP 1117, DLP 1118 or DLP 1120.

Procedure
Proceed as follows to configure PPPoX cross-connect: 1 Configure PPPoX CC global parameters with the following command:
configure pppox-relay cross-connect global-session (no) pado-timeout <PPPoX::PadTimeOut> (no) pads-timeout <PPPoX::PadTimeOut> (no) max-pad-attempts <PPPoX::PadRRetrials> (no) trans-max-age <PPPoX::TransactionMaxAge> (no) cc-max-age <PPPoX::CcMaxAge>

Configure the PPPoX CC engine with the following command:


configure pppox-relay cross-connect engine (vlan-id) (no) mac-addr-conc (no) dslf-iwf-tag (no) max-payload-tag <PPPoX::MaxPayLoadTag> (no) name <PPPoX::EngineName> (no) lock (no) service-name <PPPoX::EngineName>

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

DLP 1147 Configure PPPoX cross-connect

Enable monitoring of the PPPoX CC engine with the following command:


configure pppox-relay cross-connect engine (vlan-id) monitor

Configure PPPoX CC client port with the following command:


configure pppox-relay cross-connect client-port (port) vlan-id <Vlan::UVlanIndex> | stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex> default-priority <PPPoX::DefaultPriority> (no) max-cc <PPPoX::MaxNumPppCc> (no) qos-profile none | name:<PPPoX::IgnoredQosProfileName>

Note The parameter max-cc can be used to configure the maximum number of PPP cross-connections on a port. The values of this parameter can range from 1 to 64.
However, the maximum value of 64 cannot be achieved in all circumstances.

If MAC address concentration is enabled on the PPPoX CC engine to which this PPPoX client port is associated, then the maximum number of cross-connections is 8. If MAC address concentration is not enabled on the PPPoX CC engine to which this PPPoX client port is associated, then the actual maximum number of cross-connections depends on the used LT board.

In the second case, the actual maximum number of cross-connections can be retrieved as follows:

Use the command info configure bridge port. The bridge port is identified with the same rack, shelf, slot, and port values that identify the PPPoX client port Read the value of the parameters max-unicast-mac and the max-committed-mac.

Enable monitoring of the PPPoX CC client port with the following command:
configure pppox-relay cross-connect client-port (port) monitor

STOP. This procedure is complete.

DLP 1147-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 1147 Configure PPPoX cross-connect

Configuration example (Config#1): configure pppox-relay cross-connect global-session trans-max-age 250 cc-max-age 600 configure pppox-relay cross-connect engine 560 name PPPoXRelay560 mac-addr-conc dslf-iwf-tag configure pppox-relay cross-connect engine 560 monitor configure pppox-relay cross-connect engine 560 max-payload-tag insert configure xdsl line 1/1/5/10 service-profile 7 spectrum-profile 5 admin-up configure interface port xdsl-line:1/1/5/10 user Line1152:8.35 configure atm pvc 1/1/5/10:8:35 no admin-down aal5-encap-type automatic:ppp configure pppox-relay cross-connect client-port 1/1/5/10:8:35 vlan-id 560 default-priority 4 configure pppox-relay cross-connect client-port 1/1/5/10:8:35 monitor

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

DLP 1147 Configure PPPoX cross-connect

DLP 1147-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 1151 Shut down and restart the NT


Purpose
This procedure provides the steps to change the flash disk on the NT board and to restart the NT.

Caution The following procedure should be executed during low-traffic hours as the functional working of the NE is affected.

Warning All precautions and warnings with respect to the safety guidelines and electrostatic dangers should be read and followed.

Note It is recommended to take a backup of the NE before executing the procedure.

Caution The xHub configuration must be saved before performing an NT reset or an NT restart.
See RTP 2100 for the procedure for backing up the configuration.

Location of the flash disk on the NT board


The flash disk is located at the top rear of the board; see Figure DLP 1151-1.

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

DLP 1151 Shut down and restart the NT Figure DLP 1151-1: Location of the flash disk on the NT board

0 1

Note Observe how the flash disk is plugged in on the NT board before removing the flash disk.

Procedure
Proceed as follows to restart the NT: 1 Prepare the system for shutdown with the following command:
admin equipment prepare-sys-shutdown

2 3 4 5 6

Pull out the NT board. Swap the flash disk from the old NT board with the new NT board (see Figure DLP 1151-1 for the location of the flash disk). Insert the new NT board in the NE. Observe that the NT is loaded properly. Verify that the previously activated features are working again.

DLP 1151-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 1151 Shut down and restart the NT

7 8

Send the old NT board back to Alcatel-Lucent. STOP. This procedure is complete.

Configuration example (Config#1): admin equipment prepare-sys-shutdown

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

DLP 1151 Shut down and restart the NT

DLP 1151-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 1152 Reboot the system


Purpose
You can reboot the whole system in the following modes:

restart with self-test restart without self-test system hot restart

Caution The xHub configuration must be saved before performing an NT reset or an NT restart.
See RTP 2100 for the procedure for backing up the configuration.

Procedure
Proceed as follows to reboot the system: 1 Reboot the system with the following command:
admin equipment reboot-isam <Equipm::SystemRestart>

To reboot the system without a self-test:


admin equipment reboot-isam without-self-test

To perform a hot restart of the system:


admin equipment reboot-isam hot-restart

STOP. This procedure is complete.

Configuration example (Config#1): admin equipment reboot-isam with-self-test

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

DLP 1152 Reboot the system

DLP 1152-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 1153 Shut down and restart individual equipment


Purpose
This procedure provides the steps to shut down and restart slots containing plug-in units on the NE shelf. The only individual pieces of equipment for which it may be necessary to perform a restart are plug-in units such as LTs.

Procedure
Proceed as follows to shut down and restart individual equipment: 1 Power down a plug-in unit with the following command:
configure equipment slot (index) power-down

Caution Powering down an LT unit causes all vMAC addresses to be lost.

Note Unlike the LTs on host shelves, LTs on remote shelves are not powered off. Instead, the LTs on remote shelves are reset and then go into low-power mode. In this case, the LEDs on these LTs are turned off.
2 Restore power to a plug-in unit with the following command:
configure equipment slot (index) no power-down

STOP. This procedure is complete.

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

DLP 1153 Shut down and restart individual equipment

Configuration example (Config#1): configure equipment slot 1/1/5 power-down configure equipment slot 1/1/5 no power-down

DLP 1153-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 1159 Manage OSWP


Purpose
This procedure provides the steps to manage the Overall Software Package (OSWP).

Note For more information on OSWP; see TNG 1105.

Prerequisite
The NE contains one OSWP, which is committed and active on all the boards.

Procedure
Proceed as follows to manage the OSWP in the NE: 1 Configure the download of an OSWP with the following command:
configure software-mngt oswp (index) primary-file-server-id <SwMngt::serverId> second-file-server-id <SwMngt::serverId> activate manually | after-download

Note When FTP is used for file transfer, the server ID should be present in the configured FTP server list (see DLP 1203).

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

DLP 1159 Manage OSWP

Configure database automatic activation and automatic backup states and attributes. with the following command:
configure software-mngt database (no) activate <SwMngt::DbAutoAct> (no) backup <SwMngt::DbAutoBackup> (no) auto-backup-intvl <SwMngt::DbAutoBackIntvl>

Start the actual OSWP download with the following command:


admin software-mngt oswp (index) download <SwMngt::oswpName>

Note When at a later moment in time a new board type is introduced within the current OSWP context, the missing software files for this new board type can be retrieved via a re-download of the OSWP. The re-download command is identical to the regular OSWP download command. The command will simply re-evaluate the planned and/or detected board types in the system and upload any missing software file (see also TNG 1105 for more details).
4 Abort an OSWP download with the following command:
admin software-mngt oswp (index) abort-download

Activate an OSWP with the following command:


admin software-mngt oswp (index) activate manually | after-download

Commit an OSWP with the following command:


admin software-mngt oswp (index) commit

Manage disk and descriptor files with the following command:


admin software-mngt disk-file (path) [(remove)]

Note A disk file contains information about the different software files and descriptor files that are stored on the file disk. It also contains information such as the file name, file size, file type, file availability status, and file format.
The operator can remove an unused file from the disk by specifying the file name, which is unique over all unit types and over all SWP types for all releases.

DLP 1159-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 1159 Manage OSWP

Information about the relationships between the files known by the system and the available OSWPs can be viewed with the following command:
show software-mngt swp-disk-file (name) [file-name <SwMngt::swpContainsFileName>] [file-board-type <SwMngt::swpBoardType>]

Note If this command is executed immediately after executing the 'download command from step 3 and no output is available, this means the download is still going on. The show command has to be executed some time after the download command has been executed.
9 STOP. This procedure is complete.

Configuration example (Config#1): configure software-mngt oswp 2 primary-file-server-id 192.168.111.112 second-file-server-id 192.168.111.212 activate manually admin software-mngt oswp 2 download OSWP_packages/OSWP1 admin software-mngt oswp 2 activate with-linked-db admin software-mngt oswp 2 commit

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

DLP 1159 Manage OSWP

DLP 1159-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 1163 Modifying xDSL profiles


Purpose
This procedure provides the steps to modify xDSL spectrum profiles. You can modify:

xDSL service profiles Only the parameters name, scope and version can be changed for an existing xDSL service profile. If other parameters need to be changed, then a new xDSL service profile must be created. xDSL spectrum profiles

Prerequisite
The following prerequisite must be fullfilled before an xDSL spectrum profile can be modified:

The xDSL spectrum profile must have been created; see DLP 1129.

Procedure
Proceed as follows to modify an xDSL spectrum profile: 1 Start the modification of an xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) modification start

Modify the parameters of an xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> local-profile version <SignedInteger> (no) dis-ansi-t1413 (no) dis-etsi-dts

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

DLP 1163 Modifying xDSL profiles

(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) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)

dis-g992-1-a dis-g992-1-b dis-g992-2-a dis-g992-3-a dis-g992-3-b g992-3-l1 g992-3-l2 g992-3-aj g992-3-am g992-5-a g992-5-b ansi-t1.424 dis-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 min-noise-down <Xdsl::NoiseMargin> min-noise-up <Xdsl::NoiseMargin> trgt-noise-down <Xdsl::NoiseMargin> trgt-noise-up <Xdsl::NoiseMargin> max-noise-down <Xdsl::NoiseMarginPlus> max-noise-up <Xdsl::NoiseMarginPlus> carrier-mask-down <Xdsl::CarrierMaskDown> carrier-mask-up <Xdsl::CarrierMaskUp> rf-band-list <Xdsl::RFBand> power_mgnt_mode <Xdsl::LinePowerMgtMode> l0-time <Xdsl::LineL0Time> l2-time <Xdsl::LineL2Time> l2-agpow-red-tx<Xdsl::LineL2Atpr> rau-noise-down <Xdsl::NoiseMargin> rau-noise-up <Xdsl::NoiseMargin> rau-time-down <Xdsl::RaTime> rau-time-up <Xdsl::RaTime> rad-noise-down <Xdsl::NoiseMargin> rad-noise-up <Xdsl::NoiseMargin> rad-time-down <Xdsl::RaTime> rad-time-up <Xdsl::RaTime> l2-agpw-to-red-tx <Xdsl::LineL2Atpr>

DLP 1163-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 1163 Modifying xDSL profiles

Use one of the following commands to complete the modification of the xDSL spectrum profile: a When the modifications must be kept:
configure xdsl spectrum-profile (index) modification complete

When the modifications must be cancelled:


configure xdsl spectrum-profile (index) modification cancel

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl spectrum-profile 22 modification start configure xdsl spectrum-profile 22 name test_profile configure xdsl spectrum-profile 22 modification complete

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

DLP 1163 Modifying xDSL profiles

DLP 1163-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 1170 Configure SSH and SFTP


Purpose
This procedure provides the steps to configure the SSH and SFTP functionality.

General
When configuring SSH, the following must be taken into consideration:

SSH can only be configured by the CLI security administrator or by the TL1 manager. SSH can use password or public key authentication: In case of password authentication: The operator can login via SSH without any further configuration (that is, other than the configuration described in DLP 2101). Once logged in, it is advised to disable the non-secure channels (such as Telnet and TFTP). The operator can now configure the client username/password for the SFTP client in the NE. In case of public key authentication: Before being able to login with a public key, the operator has to configure the username/public key on the system, so the NE can authenticate the user. In order to do this, the operator has to login via username/password, configure the username/key combinations and change to key authentication. Again, the operator must make sure that the non-secure channels are closed.

When configuring SFTP, the following must be taken into consideration:

When the NE acts as an SFTP server, both password authentication and public key authentication can be used. When the NE acts as an SFTP client (to another external SFTP server), only password authentication can be used.

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

DLP 1170 Configure SSH and SFTP

Procedure
Proceed as follows to configure the SSH functionality: 1 Configure the SSH server profile (retries, timeout, authentication algorithm, and encryption algorithm) with the following command:
configure system security ssh server-profile (no) server-retries <SSH::ServerRetries> (no) idle-timeout <SSH::ServerIdleTimeOut> (no) dis-hmac-sha-1 (no) dis-hmac-sha-1-96 (no) dis-aes (no) dis-des-3 (no) dis-blowfish (no) dis-des-56

Do one of the following: a b If public key authentication is used, go to step 3 If password authentication is used, go to step 4

Configure the SSH user and the public key, to be used while connecting, with the following command:
configure system security ssh user (name) key <SSH::SshClientPublicKey>

Note 1 The private/public key pair is generated by the operator by an external key generator program on the EMS. The generated key is placed in a file by the generator program. This file can be downloaded to the NE in the SSH directory /pub/SSH/Download via TFTP. Based on the file name and file extension (for example, isadmin.pk2), the NE stores the public key automatically in its database, associated with an operator name. Now the NE can use this key to authenticate the operator when he logs in via CLI. A maximum of 10 users can be configured. Note 2 Once the session is set up, it is advised to try the login first before continuing with the next step. Note 3 When the operator notices that the private/public key pair of the NE has been compromised, the servers public key can be regenerated with the following command:
admin system security ssh generate-key <SSH::RegenerateKey>

DLP 1170-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 1170 Configure SSH and SFTP

Configure an SFTP user name and password for when the NE has to connect to an external SFTP server with the following command:
configure system security ssh sftp-user (username) password prompt | plain:<SSH::SftpPassword>

Note The SFTP user created with the command above, is unique in the system. In case of a second attempt to create such an SFTP user, the first one will be overwritten.
5 STOP. This procedure is complete.

Configuration example (Config#1): configure system security ssh server-profile server-retries 3 idle-timeout 1800 no dis-hmac-sha-1 no dis-hmac-sha-1-96 no dis-aes no dis-des-3 no dis-blowfish no dis-des-56 configure system security ssh user SSH01 configure system security ssh user SSH02 key AAAAB3NzaC1yc2EAAAABJQAAAIEAnDR5OYM3lhz3tYC3wGQhumJhrum9pyGJ 3Ic0WGW0nJ7SW5CkMm7WfDUXujqwY09I2vZ2s1fMtpPHr/yrSAQ29qnLvmnhAeMd can1YoVMgp0TAEjWKdKonn9SlGH9oPe6FFRb+1eJoPNNH3CGpGk03mqROeM0KQWo U/nRlcYFa9c= configure system security ssh sftp-user JohnDoe password plain:sshpsw01

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

DLP 1170 Configure SSH and SFTP

DLP 1170-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 1173 Switch a user from ADSL to VDSL


Purpose
This procedure provides the steps to change the configuration of a user from an ADSL service to a VDSL (1 or 2) service.

Procedure
Proceed as follows to switch a user from ADSL service to VDSL (1 or 2) service: 1 2 At the creation of the service and spectrum profiles, fill in the correct values both for the ADSL and VDSL profiles; see DLP 1129. Enable the modification by changing the value of the parameter transfer-mode from atm to ptm with the following command:
configure xdsl line (if-index) service-profile none | <Xdsl::ProfilePointer> | name: <PrintableString> spectrum-profile none | <Xdsl::ProfilePointer> | name:<PrintableString> (no) dpbo-profile <Xdsl::LineDpboProfile> transfer-mode ptm admin-up

Note The existing interfaces on top of the xDSL line (such as pvc, bridge port and so on) will be automatically removed.

3 4

Create the new forwarding model. Depending on the mode, refer to DLP 1117, DLP 1118, DLP 1119 or DLP 1120 for the correct procedure. STOP. This procedure is complete.

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

DLP 1173 Switch a user from ADSL to VDSL

Configuration example (Config#1): configure xdsl line 1/1/4/1 service-profile 8 spectrum-profile 4 transfer-mode ptm admin-up

DLP 1173-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 1174 Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect
Purpose
This procedure provides the steps to create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect.
Figure DLP 1174-1: Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect
VlanPort BridgePort IPoA/IPoE interworking ATM PVC xDSL

DLP

PVID VLAN LT NT ISAM

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

IWL

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

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

The LT must be planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129. A VLAN on the LT must have been configured for C-VLAN cross-connect; see DLP 1117.

Procedure
Proceed as follows to create an xDSL IPoA user: 1 Create an xDSL line with the following command:
configure xdsl line (if-index) service-profile none | <Xdsl::ProfilePointer> | name: <PrintableString> spectrum-profile none | <Xdsl::ProfilePointer> | name:<PrintableString> (no) dpbo-profile <Xdsl::LineDpboProfile> (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 (no) g992-3-am (no) g992-5-a (no) g992-5-b (no) ansi-t1.424 (no) etsi-ts (no) itu-g993-1 (no) ieee-802.3ah (no) g992-5-aj (no) g992-5-am (no) g993-2-8a (no) g993-2-8b (no) g993-2-8c (no) g993-2-8d (no) g993-2-12a (no) g993-2-12b (no) g993-2-17a (no) g993-2-30a (no) carrier-data-mode <Xdsl::CarrierDataMode> (no) admin-status (no) transfer-mode <Xdsl::TpsTcMode>

DLP 1174-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 1174 Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect

Configure the xDSL line with the following command:


configure interface port xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> /<Eqpt::Port> admin-up (no) user <Itf::asamIfExtCustomerId>

Create an ATM PVC with the following command:


configure atm pvc (port-index) admin-up aal5-encap-type llc-snap-routed

Create the IPoA L2 interworking port with the following command:


configure ipoa/e-iw port (interworking-port) user-ip <Ip::V4AddressHex> gw-ip <Ip::V4AddressHex>

Create a bridge port with the following command:


configure bridge port (port) mac-learn-off

Assign a VLAN to the bridge port with the following command:


configure bridge port (port) vlan-id (index)

Set the PVID with the following command:


configure bridge port (port) pvid (vlan-id)

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl line 1/1/5/7 service-profile 7 spectrum-profile 5 admin-up configure interface port xdsl-line:1/1/5/7 user IPoA cross-connect configure atm pvc 1/1/5/7:8:35 no admin-down aal5-encap-type llc-snap-routed configure ipoa/e-iw port 1/1/5/7:8:35 user-ip 192.168.150.2 gw-ip 192.168.150.1 configure bridge port 1/1/5/7:8:35 mac-learn-off configure bridge port 1/1/5/7:8:35 vlan-id 298 configure bridge port 1/1/5/7:8:35 pvid 298

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

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

DLP 1174-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 1182 Configure SHDSL


Purpose
This procedure provides the steps for configuring SHDSL span, unit and segment.

Note 1 Refer to the System Description for FD 24Gbps NT for a more detailed description of SHDSL. Note 2 For a more detailed description of the different parameters for SHDSL span, unit and segment configuration, refer to TNG 1108.

Prerequisite
The following prerequisite must be fulfilled before SHDSL can be configured:

a VLAN for iBridge must have been configured on the LT; see DLP 1120.

Procedure
Proceed as follows: 1 Manage the SHDSL span profile with the following command:
configure shdsl span (if-index) (no) active (admin-up | admin-down) (no) repeaters <Shdsl::SpanConfNumRepeaters> (no) op-mode <Shdsl::SpanOperationalMode> (no) spectral-profile <Shdsl::SpanSpectralProfile> (no) wire-mode <Shdsl::SpanWireMode> (no) mgmt-by-stu-r (no) regi-set <Shdsl::SpanRegionalSetting> (no) min-line-rate <Shdsl::BitRate> (no) max-line-rate <Shdsl::BitRate> (no) margin-down-worst <Shdsl::NoiseMarginWC> (no) margin-down-curr <Shdsl::NoiseMarginCC>

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

DLP 1182 Configure SHDSL

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

margin-up-worst <Shdsl::NoiseMarginWC> margin-up-curr <Shdsl::NoiseMarginCC> probe <Shdsl::SpanLineProbeEnable> tc-pam-sele <Shdsl::SpanTCPAMSelection> efm-hs-sele <Shdsl::SpanEFMHandshakeSelection> bonding-rate-mode <Shdsl::SpanBondingRateControlMode> min-rate-link1 <Shdsl::BitRate> max-rate-link1 <Shdsl::BitRate> min-rate-link2 <Shdsl::BitRate> max-rate-link2 <Shdsl::BitRate> min-rate-link3 <Shdsl::BitRate> max-rate-link3 <Shdsl::BitRate> min-rate-link4 <Shdsl::BitRate> max-rate-link4 <Shdsl::BitRate> tc-pam-link1 <Shdsl::SpanTCPAMSelectionLink> tc-pam-link2 <Shdsl::SpanTCPAMSelectionLink> tc-pam-link3 <Shdsl::SpanTCPAMSelectionLink> tc-pam-link4 <Shdsl::SpanTCPAMSelectionLink> ctc <Shdsl::SpanCTCSelection>

Note The parameters min-line-rate and max-line-rate must be set to the same value for SHDSL spans used as IMA links.

Manage the SHDSL unit profile in one SHDSL span with the following command:
configure shdsl unit (if-index) unit-id <Shdsl::UnitId> (no) loop-attenuation <Shdsl::UnitLoopAttenThreshold> (no) snr-margin <Shdsl::UnitSnrMarginThreshold> (no) loopback-timeout <Shdsl::UnitLoopbackTimeout>

Configure the SHDSL segment points on either side of an SHDSL unit with the following command:
configure shdsl segment (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> (no) loopback <Shdsl::SegmentTermLoopbackConf> pbo-mode <Shdsl::SegmentTermPowerBackoff>

Manage an SHDSL segment points with the following command:


admin shdsl-seg (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> (no) soft-restart

Activate the SHDSL line with one of the following commands:


configure shdsl span (if-index) admin-up

Do one of the following: a b For a user with operational mode = native; continue with step 7 For a user with operational mode = efm; continue with step 8

DLP 1182-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 1182 Configure SHDSL

Create an ATM PVC (or the necessary ATM PVCs) on the main line with the following command:
configure atm pvc (port-index) (no) admin-down (no) aal5-encap-type llc-snap | llc-snap-routed | llc-nlpid | vc-mux-bridged-8023 | vc-mux-routed | vc-mux-pppoa | automatic:ip | automatic:ppp | automatic:pppoa | automatic: ipoe-ppp

Create a bridge port with the following command:


configure bridge port (port) (no) default-priority <Vlan::Priority (no) mac-learn-off (no) max-unicast-mac <Vlan::MaxMac> (no) qos-profile <Vlan::QosProfileName> (no) prio-regen-prof <Vlan::PrioRegenProfile> (no) max-committed-mac <Vlan::ComitMaxMac> (no) mirror-mode <Vlan::MirrorMode> (no) mirror-vlan <Vlan::MirrorVlan>

Note If step 7 was executed, a bridge port must be create for each of the created PVCs.

For each bridge port created in step 8, assign a VLAN to the bridge port and, if required, set the priorities applicable for that port with the following command
configure bridge port (port) vlan-id (index) (no) tag <Vlan::PortUntagStatus> (no) network-vlan <Vlan::StackedVlan> (no) vlan-scope <Vlan::VlanScope> (no) qos <Vlan::QosPolicy> (no) qos-profile <Vlan::QosProfileName> (no) prior-best-effort (no) prior-background (no) prior-spare (no) prior-exc-effort (no) prior-ctrl-load (no) prior-less-100ms (no) prior-less-10ms (no) prior-nw-ctrl

10

Set the PVID with the following command:


configure bridge port (port) pvid (vlan-id)

11

STOP. This procedure is complete.

Configuration examples:

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

DLP 1182 Configure SHDSL

Configuration example for 4-wire Multi-pair bonding (Config#2): configure shdsl span 1/1/8/1 active wire-mode four-wire min-line-rate 2048 max-line-rate 5120 margin-down-worst 5 margin-up-worst 5 admin-up configure shdsl span 1/1/8/3 active wire-mode four-wire min-line-rate 2048 max-line-rate 5120 margin-down-worst 5 margin-up-worst 5 admin-up configure shdsl unit 1/1/8/1 unit-id stu-r loopback-timeout 10 configure shdsl segment 1/1/8/1 unit-id stu-c side customer loopback normal configure atm pvc 1/1/8/1:8:35 no admin-down aal5-encap-type llc-snap configure atm pvc 1/1/8/3:8:35 no admin-down aal5-encap-type llc-snap configure bridge port 1/1/8/1:8:35 configure bridge port 1/1/8/1:8:35 vlan-id 100 configure bridge port 1/1/8/1:8:35 pvid 100 configure bridge port 1/1/8/3:8:35 configure bridge port 1/1/8/3:8:35 vlan-id 100 configure bridge port 1/1/8/3:8:35 pvid 100 Configuration example is for SHDSL spans used as IMA links (Config#2): configure shdsl span 1/1/8/16 min-line-rate 2304 max-line-rate 2304 margin-down-worst 5 margin-up-worst 5 op-mode ima active admin-up configure shdsl span 1/1/8/18 min-line-rate 2304 max-line-rate 2304 margin-down-worst 5 margin-up-worst 5 op-mode ima active admin-up configure shdsl span 1/1/8/21 min-line-rate 2304 max-line-rate 2304 margin-down-worst 5 margin-up-worst 5 op-mode ima active admin-up configure shdsl span 1/1/8/24 min-line-rate 2304 max-line-rate 2304 margin-down-worst 5 margin-up-worst 5 op-mode ima active admin-up

DLP 1182-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 1182 Configure SHDSL

Configuration example is for EFM (in 4-wire mode) (Config#2): configure shdsl span 1/1/8/5 active wire-mode four-wire min-line-rate 2048 max-line-rate 5120 margin-down-worst 5 margin-up-worst 5 op-mode efm efm-hs-sele auto admin-up configure bridge port 1/1/8/5 configure bridge port 1/1/8/5 vlan-id 100 configure bridge port 1/1/8/5 pvid 100 Configuration example for changing the opmode from ATM to EFM (Config#2): The example assumes that a line has been activated in default operation mode (ATM) and default wire mode (2-wire). To change the operation mode, the line first has to be deactivated with the command configure shdsl span 1/1/8/1 no admin-up no active Then the line has to be activated in EFM mode with the following command (handshake mode is also configured in this example): configure shdsl span 1/1/8/1 op-mode efm efm-hs-sele auto configure shdsl span 1/1/8/1 min-line-rate 2048 max-line-rate 5120 active admin-up Configuration example for link-level rate control and TC-PAM selection (Config#2): configure shdsl span 1/1/8/9 no active no admin-up configure shdsl span 1/1/8/9 active wire-mode eight-wire margin-down-worst 5 margin-up-worst 5 op-mode efm efm-hs-sele auto bonding-rate-mode link-level min-rate-link1 192 max-rate-link1 5696 min-rate-link2 192 max-rate-link2 5696 min-rate-link3 192 max-rate-link3 5696 min-rate-link4 192 max-rate-link4 5696 tc-pam-link1 auto tc-pam-link2 auto tc-pam-link3 auto tc-pam-link4 auto admin-up

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

DLP 1182 Configure SHDSL

DLP 1182-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 1183 Configure IMA on SHDSL spans


Purpose
This procedure provides the steps for configuring Inverse Multiplexing for ATM (IMA).

Note Refer to the System Description for FD 24Gbps NT for a more detailed description of the IMA functionality.

Prerequisite
The following prerequisites must be fulfilled before IMA can be configured on SHDSL links:

a VLAN for iBridge must have been configured on the LT; see DLP 1120. the SHDSL links must have been created as IMA links (and have operational mode ima); see DLP 1182.

Procedure
Proceed as follows: 1 Manage the IMA group profile with the following command:
configure ima group (if-index) (no) activate (admin-up | admin-down) (no) min-tx-links <Ima::GroupMinNumTxLinks> (no) min-rx-links <Ima::GroupMinNumRxLinks> near-end-ima-id <Ima::GroupTxImaId>

Manage the IMA link profile with the following command:


configure ima link (link-if-index) grp-index <Itf::ImaLine>

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

DLP 1183 Configure IMA on SHDSL spans

Activate the IMA line interface with one of the following commands:
configure ima group (if-index) admin-up configure interface port ima-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> admin-up

STOP. This procedure is complete.

Configuration example (Config#2): configure ima group 1/1/8/16 active admin-up min-tx-links 2 min-rx-links 2 near-end-ima-id 0 configure ima link 1/1/8/16 grp-index 1/1/8/16 configure ima link 1/1/8/18 grp-index 1/1/8/16 configure ima link 1/1/8/21 grp-index 1/1/8/16 configure ima link 1/1/8/24 grp-index 1/1/8/16 configure atm pvc 1/1/8/16:0:35 aal5-encap-type vc-mux-bridged-8023 no admin-down configure bridge port 1/1/8/16:0:35 configure bridge port 1/1/8/16:0:35 vlan-id 100 configure bridge port 1/1/8/16:0:35 pvid 100

DLP 1183-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 1187 Configure global VLAN parameters on the LT


Purpose
This procedure provides the steps to specify VLAN parameters which are globally applicable to VLANs:

broadcast-frames: This parameter determines if broadcast frames must be switched for each VLAN. This parameter applies to iBridge VLANs. priority-policy: This parameter specifies how to deal with ethernet priority of the upstream frames. This parameter applies to iBridge VLANs and cross-connect VLANs.

Procedure
Proceed as follows to configure the general VLAN parameters: 1 Configure the general VLAN parameters with the following command:
configure vlan (no) broadcast-frames priority-policy vlan-specific | port-default

STOP. This procedure is complete.

Configuration example (Config#1): configure vlan broadcast-frames priority-policy port-default

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

DLP 1187 Configure global VLAN parameters on the LT

DLP 1187-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 1188 Configure custom PSD points


Purpose
Many operators tend to have locations where copper binders have pairs coming from a CO and pairs coming from a remote cabinet. When the remote cabinet locations get broadband enabled this often creates spectral compatibility issues in the network: the strong ADSL signal coming from the remote cabinet creates strong cross talk to the weak signal coming from the CO. This results in a very unstable line for the one connected to the CO. To resolve this, a custom Power Spectral Density (PSD) shape is configurable via the xDSL spectrum profile. A custom defined PSD allows:

for a better spectrum usage (and better performance as a consequence) for protection of the xDSL coming from the CO

Customized PSD values can be configured for:

ADSL2+ VDSL VDSL2

Up to 20 breakpoints can be configured. When configuring a custom PSD shape, a minimum of 2 PSD points must be configured. Customized PSD points can be configured while creating a new spectrum profile (see DLP 1129) or by modifying an existing spectrum profile (see DLP 1163).

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

DLP 1188 Configure custom PSD points

The commands below help the operator to enter the custom PSD shape in a user-friendly way. Instead of entering octets, the operator can enter numbers corresponding to frequency and PSD.

Warning When a Custom PSD mask is created, it is up to the operator to make sure that the provided breakpoints are in accordance with the PSD slope rules defined in the applicable standard (for example, G992.5, clause 8.5.1).
A PSD mask configuration violating these rules will not be rejected, but the DSL chipset will perform a best-effort fit using the PSD shaping rules of the applicable standard. It is thus possible that the configured PSD mask may be violated. If the PSD breakpoints are configured in accordance with the PSD slope rules defined in the applicable standard then the actual PSD shall always remain below the configured breakpoints. This means that, for example, for ADSL2plus it is not possible to have infinite slopes in the PSD mask. See the CLI Command Guide for FD 24Gbps NT document and also TNG 1107 for a full description of all related parameters.

Procedure
Proceed as follows to configure custom PSD points: 1 For the configuration of:

custom custom custom custom custom custom

PSD points for ADSL2+, go to step 2 downstream PSD points for VDSL, go to step 3 upstream PSD points for VDSL, go to step 4 downstream PSD points for VDSL2, go to step 5 upstream Rx PSD points for VDSL2, go to step 6 upstream PSD points for VDSL2, go to step 7

Configure the custom PSD points for ADSL2+ as follows: i Configure a xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> version <SignedInteger>

ii

Configure the PSD for ADSL2+ as custom PSD with the following command:
configure xdsl spectrum-profile (index) adsl2-plus psd-shape-down custom-psd-down

DLP 1188-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 1188 Configure custom PSD points

iii

Configure the PSD values with the following command:


configure xdsl spectrum-profile (index) adsl2-plus cust-psd-pt-down (psdpt) frequency <Xdsl::CustFrqAdsl2> psd <Xdsl::CustomAdsl2Psd>

iv 3

Go to step 8

Configure the custom downstream PSD points for VDSL as follows: i Configure a xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> version <SignedInteger>

ii

Configure the downstream PSD for VDSL as custom PSD with the following command:
configure xdsl spectrum-profile (index) vdsl psd-shape-down custom-psd-down

iii

Configure the downstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl cust-psd-sc-down linear | logarithmic cust-psd-ty-down mask | template

iv

Configure the downstream PSD values with the following command:


configure xdsl spectrum-profile (index) vdsl cust-psd-pt-down (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

v 4

Go to step 8

Configure the custom upstream PSD points for VDSL as follows: i Configure a xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> version <SignedInteger>

ii

Configure the upstream PSD for VDSL as custom PSD with the following command:
configure xdsl spectrum-profile (index) vdsl rx-psd-shape-up custom-rx-psd-up

iii

Configure the upstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl cust-rx-psd-sc-up linear | logarithmic cust-rx-psd-ty-up mask | template

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

DLP 1188 Configure custom PSD points

iv

Configure the upstream PSD values with the following command:


configure xdsl spectrum-profile (index) vdsl cust-rx-psd-pt-up (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

v 5

Go to step 8

Configure the custom downstream PSD points for VDSL2 as follows: i Configure a xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> version <SignedInteger>

ii

Configure the downstream PSD for VDSL2 as custom PSD with the following command:
configure xdsl spectrum-profile (index) vdsl2 psd-shape-down custom-psd-down

iii

Configure the downstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl2 cust-psd-sc-down linear | logarithmic cust-psd-ty-down mask | template

iv

Configure the downstream PSD values with the following command:


configure xdsl spectrum-profile (index) vdsl2 cust-psd-pt-down (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

v 6

Go to step 8

Configure the upstream Rx PSD points for VDSL2 as follows: i Configure a xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> version <SignedInteger>

ii

Configure the upstream Rx PSD for VDSL2 as custom PSD with the following command:
configure xdsl spectrum-profile (index) vdsl2 rx-psd-shape-up custom-rx-psd-up

iii

Configure the upstream Rx PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl2 cust-rx-psd-sc-up linear | logarithmic cust-rx-psd-ty-up mask | template

DLP 1188-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 1188 Configure custom PSD points

iv

Configure the upstream Rx PSD values with the following command:


configure xdsl spectrum-profile (index) vdsl2 cust-rx-psd-pt-up (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

v 7

Go to step 8

Configure the upstream PSD points for VDSL2 as follows: i Configure a xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) name <AsamProfileName> version <SignedInteger>

ii

Configure the upstream PSD for VDSL2 as custom PSD with the following command:
configure xdsl spectrum-profile (index) vdsl2 psd-shape-up custom-psd-up

iii

Configure the upstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl2 cust-psd-sc-up linear | logarithmic cust-psd-ty-up mask | template

iv

Configure the upstream PSD values with the following command:


configure xdsl spectrum-profile (index) vdsl2 cust-psd-pt-up (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

Activate the xDSL spectrum profile with the following command:


configure xdsl spectrum-profile (index) active

STOP. This procedure is complete.

Configuration examples:

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

DLP 1188 Configure custom PSD points

Configuration example for ADSL2+ (Config#1): configure xdsl spectrum-profile 11 name adsl2-plus version 1 configure xdsl spectrum-profile 11 adsl2-plus psd-shape-down custom-psd-down configure xdsl spectrum-profile 11 adsl2-plus cust-psd-pt-down 1 frequency 1000 psd 55 configure xdsl spectrum-profile 11 adsl2-plus cust-psd-pt-down 2 frequency 1200 psd 65 configure xdsl spectrum-profile 11 active

Configuration example for VDSL (downstream) (Config#1): configure xdsl spectrum-profile 12 name vdsl1-1 configure xdsl spectrum-profile 12 vdsl psd-shape-down custom-psd-down configure xdsl spectrum-profile 12 vdsl cust-psd-sc-down logarithmic cust-psd-ty-down mask configure xdsl spectrum-profile 12 vdsl cust-psd-pt-down 1 frequency 1000 psd 55 configure xdsl spectrum-profile 12 vdsl cust-psd-pt-down 2 frequency 1200 psd 65 configure xdsl spectrum-profile 12 active

Configuration example for VDSL (upstream) (Config#1): configure xdsl spectrum-profile 13 name vdsl1-2 version 1 configure xdsl spectrum-profile 13 vdsl rx-psd-shape-up custom-rx-psd-up configure xdsl spectrum-profile 13 vdsl cust-rx-psd-sc-up logarithmic cust-rx-psd-ty-up template configure xdsl spectrum-profile 13 vdsl cust-rx-psd-pt-up 1 frequency 1000 psd 55 configure xdsl spectrum-profile 13 vdsl cust-rx-psd-pt-up 2 frequency 1200 psd 65 configure xdsl spectrum-profile 13 active

DLP 1188-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 1188 Configure custom PSD points

Configuration example for VDSL2 (downstream) (Config#1): configure xdsl spectrum-profile 14 name vdsl2-1 version 1 configure xdsl spectrum-profile 14 vdsl2 psd-shape-down cust-psd-down configure xdsl spectrum-profile 14 vdsl2 cust-psd-sc-down logarithmic cust-psd-ty-down template configure xdsl spectrum-profile 14 vdsl2 cust-psd-pt-down 1 frequency 1000 psd 55 configure xdsl spectrum-profile 14 vdsl2 cust-psd-pt-down 2 frequency 1200 psd 65 configure xdsl spectrum-profile 14 active

Configuration example for VDSL2 (Rx upstream) (Config#1): configure xdsl spectrum-profile 15 name vdsl2-2 configure xdsl spectrum-profile 15 vdsl2 rx-psd-shape-up custom-rx-psd-up configure xdsl spectrum-profile 15 vdsl2 cust-rx-psd-sc-up logarithmic cust-rx-psd-ty-up template configure xdsl spectrum-profile 15 vdsl2 cust-rx-psd-pt-up 1 frequency 1000 psd 55 configure xdsl spectrum-profile 15 vdsl2 cust-rx-psd-pt-up 2 frequency 1200 psd 65 configure xdsl spectrum-profile 15 active

Configuration example for VDSL2 (upstream) (Config#1): configure xdsl spectrum-profile 16 name vdsl2-3 version 2 configure xdsl spectrum-profile 16 vdsl2 psd-shape-up custom-psd-up configure xdsl spectrum-profile 16 vdsl2 cust-psd-sc-up logarithmic cust-psd-ty-up template configure xdsl spectrum-profile 16 vdsl2 cust-psd-pt-up 1 frequency 1000 psd 55 configure xdsl spectrum-profile 16 vdsl2 cust-psd-pt-up 2 frequency 1200 psd 65 configure xdsl spectrum-profile 16 active

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

DLP 1188 Configure custom PSD points

DLP 1188-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 1189 Configure VDSL2 virtual noise values


Purpose
This procedure provides the steps to configure receiver referred (in upstream direction only) and transmitter referred (both in downstream and upstream direction) virtual noise values for VDSL2. The commands below help the operator to enter the virtual noise values in a user-friendly way. Instead of entering octets, the operator can enter numbers corresponding to frequency and PSD.

Note At least 2 values must be configured.

For more detailed information on the parameters, refer to TNG 1107.

Procedure
Proceed as follows to configure virtual noise values for VDSL2: 1 Configure the virtual noise values in downstream direction with the following command:
configure xdsl spectrum-profile (index) vdsl2 v-noise-psd-pt-down (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

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

DLP 1189 Configure VDSL2 virtual noise values

Configure the virtual noise values in upstream direction with the following command:
configure xdsl spectrum-profile (index) vdsl2 v-noise-psd-pt-up (psdpt) frequency <Xdsl::CustFreq> psd <Xdsl::CustPsd>

Activate an xDSL spectrum profile with the following command:


configure xdsl spectrum-profile (index) active

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl spectrum-profile 17 name vdsl2-4 configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-down 1 frequency 1000 psd 55 configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-down 2 frequency 1200 psd 65 configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-up 1 frequency 1000 psd 55 configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-up 2 frequency 1200 psd 65 configure xdsl spectrum-profile 17 active

DLP 1189-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 1190 Configure threshold crossing alerts


Purpose
This procedure provides the necessary steps to configure Threshold Crossing Alerts (TCA) on xDSL lines and on Ethernet lines.

Note Ensure that the TCA alarm is set to reporting and has a severity equal to or greater than the non-itf-rep-sev-level; see DLP 2110.

Prerequisites
The following prerequisite must be fulfilled before a TCA can be configured:

For a TCA on an xDSL line: the xDSL line must be configured; see DLP 1124.

Procedure
Proceed as follows to configure and enable a TCA: 1 Configure and enable a TCA on an xDSL line with the following command:
configure xdsl line (if-index) tca-line-threshold (no) enable (no) es-nearend <Xdsl::IntervalTcaThreshold> (no) ses-nearend <Xdsl::IntervalTcaThreshold> (no) uas-nearend <Xdsl::IntervalTcaThreshold> (no) es-day-nearend <Xdsl::DayTcaThreshold> (no) ses-day-nearend <Xdsl::DayTcaThreshold> (no) uas-day-nearend <Xdsl::DayTcaThreshold> (no) es-farend <Xdsl::IntervalTcaThreshold>

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

DLP 1190 Configure threshold crossing alerts

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

ses-farend <Xdsl::IntervalTcaThreshold> uas-farend <Xdsl::IntervalTcaThreshold> es-day-farend <Xdsl::DayTcaThreshold> ses-day-farend <Xdsl::DayTcaThreshold> uas-day-farend <Xdsl::DayTcaThreshold>

Configure and enable a TCA on an Ethernet line with the following command:
configure ethernet line (if-index) tca-line-threshold (no) enable (no) los <ETHITF::IntervalTcaThreshold> (no) fcs <ETHITF::IntervalTcaThreshold> (no) los-day <ETHITF::DayTcaThreshold> (no) fcs-day <ETHITF::DayTcaThreshold>

STOP. This procedure is complete.

Configuration example (Config#1): 1. For xDSL line: configure xdsl line 1/1/5/6 tca-line-threshold enable ses-day-nearend 30 2. For Ethernet line: configure ethernet line 1/1/13/4 tca-line-threshold enable los 40

DLP 1190-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 1197 View port configuration and operational data on LT


Purpose
This procedure provides the commands for viewing the configuration and operational data of xDSL ports and Ethernet ports on the NE.

Note For more information on the command syntax and the command parameters, refer to the CLI Command Guide for FD 24Gbps NT.

Procedure
The following commands can be used for viewing the configuration and operational data of ports: 1 Use the following commands to show the configuration data of an xDSL port:
show xdsl config-data-port (if-index) xdsl | atm-pvc (port-index) | interface-atm-pvc | interface-port | igmp (port) | security-pae (port) | bridge-port (port) | qos | pppox-relay (port) | bonding-group

Use the following commands to show the operational data of an xDSL port:
show xdsl oper-data-port (if-index) xdsl | bridge-port (port) | atm-pvc (port-index) | interface-port | igmp (port) | ip-bridge-port (ip-bridge-port) | qos

Use the following commands to show the configuration data of an Ethernet port:
show config-data-port (if-index) interface-port | igmp (port) | security-pae (port) | bridge-port (port) | qos

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

DLP 1197 View port configuration and operational data on LT

Use the following commands to show the operational data of an Ethernet port:
show oper-data-port (if-index) ethernet | bridge-port (port) | interface-port | igmp (port) | ip-bridge-port (ip-bridge-port) | qos

STOP. This procedure is complete.

Configuration example (Config#1): show xdsl config-data-port 1/1/5/12 show xdsl oper-data-port 1/1/5/12 show config-data-port 1/1/13/1 show oper-data-port 1/1/13/1

DLP 1197-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 1201 Configure protocol tracing


Purpose
This procedure allows the operator to enable or disable protocol tracing. The operator can enter the protocol, the port and the level of detail for which tracing can be enabled.

Procedure
Proceed as follows to configure protocol tracing: 1 Configure protocol tracing with the following command:
configure debug-trace protocol-trace (trace-subject) protocol igmp | dhcp | arp | dhcpv6 syslog <Debug::SyslogMsgType> (no) events (no) packet-summary

STOP. This procedure is complete.

Configuration example (Config#1): configure debug-trace protocol-trace dsl-line:1/1/4/15 protocol dhcp syslog tracing2 events packet-summary

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

DLP 1201 Configure protocol tracing

DLP 1201-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 1202 Configure QoS threshold crossing alerts


Purpose
This procedure provides the steps to configure QoS Threshold Crossing Alerts (TCA).

Prerequisites
The following prerequisite must be fulfilled before QoS TCAs can be configured:

The board must have been planned; see DLP 2111.

Procedure
Proceed as follows to configure QoS TCAs: 1 Configure the QoS global variables (LT-level TCAs, enabling of TCAs, ...) with the following command:
configure qos global (index) (no) buffer-occ-thresh <Qos::PercentThresh> (no) queue-stats (no) dsload-tca (no) dsload-thresh <Qos::PercentThresh> (no) buffer-tca (no) up-buf-thresh <Qos::UpAggrBufOvflwTcaTh> (no) up-obc-thresh <Qos::UpObcAggrBufOvflwTcaTh> (no) dn-obc-thresh <Qos::DnObcAggrBufOvflwTcaTh> (no) dn-buf-thresh <Qos::DnUcAggrBufOvflwTcaTh> (no) part-buf-thresh <Qos::PartBufThresh>

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

DLP 1202 Configure QoS threshold crossing alerts

Configure the QoS (queue-specific) TCA table (enable or disable TCAs for a certain queue, setting the threshold for queue traffic load, setting the threshold for discarded frames,...) with the following command:
configure qos tca (index) queue <Qos::TcaQueues> (no) tca-enable (no) load-thresh <Qos::PercentThresh> (no) dis-frame-th <Qos::QosQueueStatsDiscFramesTcaThreshold>

STOP. This procedure is complete.

Configuration example (Config#1): configure qos global lt:1/1/5 queue-stats dsload-thresh 40 configure qos tca 1/1/5/12 queue 1 tca-enable load-thresh 40

DLP 1202-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 1203 Configure general security settings


Purpose
This procedure provides the steps to configure general security settings such as:

access of the different remote management channels (TL1, CLI and debug) CLI password policy file transfer attributes

The following remote management channels are foreseen:

CLI over SSH - secure CLI over telnet - insecure TL1 over SSH - secure TL1 over UDP - insecure variant Debug access - insecure SFTP - secure TFTP - insecure

Note

It is advised to only use secure management channels (CLI over SSH, TL1 over SSH and SFTP). It is advised to close the unused management channels. It is not possible to close CLI over SSH.

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

DLP 1203 Configure general security settings

Procedure
Proceed as follows to configure general security settings: 1 Configure the remote access for CLI with the following command:
configure system security ssh access cli ssh | telnet | telnet-ssh

Configure the remote access for TL1 with the following command:
configure system security ssh access tl1 none | ssh | udp | udp-ssh

Configure the remote access for debug with the following command:
configure system security ssh access debug none | udp

Configure the password policy with the following command:


configure system security password min-length <Sec::PwdLength> min-num-numeric-char <Sec::PwdNumChars> min-num-special-char <Sec::PwdSpeChars> (no) mixed-case <Sec::MixCase>

Configure the file transfer protocol with the following command:


configure system security filetransfer protocol tftp | ftp | sftp

Note Server functionality is supported for TFTP and SFTP.


Client functionality is supported for TFTP, SFTP and FTP. Only one file transfer protocol can be supported at the same time.

DLP 1203-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 1203 Configure general security settings

Configure the remote file server when the NE has to be connected to an external xFTP server with the following command:

Note To configure the file servers user by Operational Software management, see DLP 1159.

For FTP, use the following command:


configure system security filetransfer server (serverid) user-name <SwMngt::UserName> password <SwMngt::Password>

Note Up to 8 different FTP servers can be configured.


If FTP is configured, the server address of the OSWP should be included in the supported FTP server list. b For SFTP, configure an SFTP user name and password with the following command:
configure system security ssh sftp-user (username) password prompt | plain:<SSH::SftpPassword>

Note The SFTP user created with the command above, is unique in the system. In case of a second attempt to create such an SFTP user, the first one will be overwritten. Only password authentication can be used.
c 7 For TFTP, no user configuration possible because TFTP does not support authentication.

STOP. This procedure is complete.

Configuration example (Config#1): configure system security ssh access cli ssh configure system security ssh access tl1 none configure system security ssh access debug none configure system security filetransfer protocol sftp configure system security ssh sftp-user JohnDoe password plain:sshpsw01

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

DLP 1203 Configure general security settings

DLP 1203-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 1205 Configure Link Related Ethernet OAM


Purpose
This procedure provides the steps to enable Link Related Ethernet OAM (EFM OAM) and start discovery of the CPE.

Link Related Ethernet OAM Configuration Parameters


Link Related Ethernet OAM is managed using the parameters described in Table DLP 1205-1. These values are stored in the database persistently.
Table DLP 1205-1: Link Related Ethernet OAM parameter descriptions
Parameter admin-status Description Parameter used to enable / disable Link Related Ethernet OAM on an interface Dot3 OAM mode value. (NE is always configured in Active mode) 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 Values Enabled / Disabled Default Disabled

oam-mode alive-timer

Active / Passive 1s - 300 s

Active 300 s

(1 of 2)

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

DLP 1205 Configure Link Related Ethernet OAM

Parameter var-response-timer

Description Maximum time interval for which the NE waits to receive all the variable response PDUs (all requested counters) from the CPE

Values 2 s - 10 s

Default 5s

(2 of 2)

Prerequisites
The following prerequisites must be fulfilled before Link Related Ethernet OAM can be configured:

Link related Ethernet OAM is supported on LTs terminating DSL lines that operate in PTM mode: The LT must be planned, see DLP 2111. xDSL profiles must have been created, see DLP 1129. DSL line in PTM (default value) is configured with the xDSL profile and Bridge port is created. The interface is connected to a CPE which supports Link Related Ethernet OAM Link related Ethernet OAM is supported on LTs terminating Ethernet lines: The LT must be planned, see DLP 2111. The interface is connected to a CPE which supports Link Related Ethernet OAM

Note The first prerequisite is mandatory to enable, disable and configure Link Related Ethernet OAM.
The other prerequisites are required to start discovery on an interface.

DLP 1205-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 1205 Configure Link Related Ethernet OAM

Procedure
Proceed as follows to enable and configure Link Related Ethernet OAM on an interface 1 Enable/disable and configure Link Related Ethernet OAM with the following command:
configure efm-oam interface (interface) (no) admin-status (no) passive-mode keep-alive-intvl <Ether::KeepAliveTimeTicks> response-intvl <Ether::ResponseTimeTicks>

Note 1 Concerning the keep-alive-intvl parameter:


the value is configurable because:

some types of CPE can function with the default value of 300 s. As a result of this longer interval, less load is generated on the system. other types of CPE have a fixed Alive time of 1 s and cannot function with the default value. For these modems, the parameter keep-alive-intvl should be set to 1 s.

Note 2 The NE will always function in Active mode. All the parameters in this command are optional; therefore the command can be used to configure each of the parameter individually.
2 The configured values can be viewed with the following command:
info configure efm-oam interface [(interface)]

The local (NE) and remote (CPE) configuration can be viewed: a To view the local (NE) configuration, use the following command:
show efm-oam local-oam-info [(interface)]

To view the remote (CPE) configuration, use the following command:


show efm-oam peer-oam-info [(interface)]

Note The remote (CPE) configuration can only be viewed when the operational state is NOT disabled, link-fault or active-send-local.
Use the command from step 3a to get the operational state. 4 Retrieve the OAM statistical information with the following command:
show efm-oam oam-stats [(interface)]

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

DLP 1205 Configure Link Related Ethernet OAM

The MAC counters from the CPE can be retrieved (at any time) with the following command:
show efm-oam mac-stats [(interface)]

Note The discovery status must be operational. Use the command in step 3a to check the discovery status.

The Physical Medium Entity (PME) counters of all the links in a bonding group or of an individual link from the CPE can be retrieved (at any time) as follows:

Note The discovery status must be operational. Use the command in step 3a to check the discovery status.

To retrieve PME counters of all the links in the bonding group, use the following command:
show efm-oam pme-stats [(group)]
where group indicates the primary link of the bonding group

To retrieve PME counters of an individual link, use the following command:


show efm-oam pme-stats [link:(link)]

Note 1 PME counters of an individual link which is not in a bonding group can be retrieved using either of the above commands. Note 2 The command shows the 64/65-octet encapsulation errors, corrected FEC blocks (in CPE), uncorrectable FEC blocks (in CPE) and the number of TC-CRC errors recorded on the CPE
7 STOP. This procedure is complete.

Configuration example (Config#1): configure efm-oam interface 1/1/4/2 admin-up no passive-mode keep-alive-intvl 300 response-intvl 5 configure efm-oam interface 1/1/4/2 admin-up show efm-oam local-oam-info 1/1/4/2 show efm-oam peer-oam-info 1/1/4/2 show efm-oam oam-stats 1/1/4/2 show efm-oam mac-stats 1/1/4/2 show efm-oam pme-stats 1/1/4/2 show efm-oam pme-stats link:1/1/4/2

DLP 1205-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 1206 Configure an xDSL DPBO profile


Purpose
This procedure provides the steps to configure the following parameters that are supported for the configuration of the Downstream Power Back Off (DPBO) PSD shape, as an alternative to the use of PSD breakpoints.

E-side parameter Exchange PSD mask: This is the PSD mask which must protected by the DPBO shaping mechanism at the remote flexibility point. This parameter matches the DPBOEPSD parameter described in ITU-T G.997.1 Mode independent custom PSD mask: PSD breakpoints for the DPBO Mode Independent Custom PSD Mask 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

Prerequisites
The following prerequisite must be fulfilled before enhanced PSD shaping provisioning can be configured:

The LT board must be planned; see DLP 2111.

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

DLP 1206 Configure an xDSL DPBO profile

Procedure
Proceed as follows to configure enhanced PSD shaping provisioning: 1 Create a DPBO profile with the following command:
configure xdsl dpbo-profile (index) name <name>

Configure the DPBO profile parameters with the following command:


configure xdsl dpbo-profile (index) name (no) es-elect-length (no) es-cable-model-a (no) es-cable-model-b (no) es-cable-model-c (no) min-usable-signal (no) min-frequency (no) max-frequency (no) rs-elect-length (no) muf-control (no) offset

If required, configure the exchange PSD mask with the following command:
configure xdsl dpbo-profile (index) epsd-pt-down (psd-point) (no) frequency <Xdsl::DpboFrequency> (no) psd <Xdsl::DpboExchangePsd>

Note A number of 2 to 32 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 (brick wall).
4 If required, configure a mode independent custom PSD mask with the following command:
configure xdsl dpbo-profile (index) micpsd-pt-down (psd-point) (no) frequency <Xdsl::DpboFrequency> (no) psd <Xdsl::DpboCustomPsd>

Note A number of 2 to 16 PSD points can be specified. 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 (brick wall). The second sub-set starts at the first breakpoint whose frequency is lower than the frequency of the previous breakpoint.
5 Activate the DPBO profile with the following command:
configure xdsl dpbo-profile (index) name <name> active

DLP 1206-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 1206 Configure an xDSL DPBO profile

Assign the DPBO to a port or a board. Do one of the following: a To assign the DPBO profile to a port, use the following command:
configure xdsl line <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> dpbo-profile (index)

To assign the DPBO profile to a board, use the following command:


configure xdsl board <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> dpbo-profile (index)

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl dpbo-profile 1 name DPBOProfile1 configure xdsl dpbo-profile 1 active configure xdsl line 1/1/4/12 dpbo-profile 1

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

DLP 1206 Configure an xDSL DPBO profile

DLP 1206-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 1207 Modify an xDSL DPBO profile


Purpose
This procedure provides the steps to modify an existing xDSL DPBO profile.

Prerequisite
The following prerequisite must be fullfilled before a xDSL DPBO profile can be modified:

The xDSL DPBO profile must have been created; see DLP 1206.

Procedure
Proceed as follows to modify a xDSL DPBO profile: 1 Start the modification of a xDSL DPBO profile with the following command:
configure xdsl dpbo-profile (index) modification start

Modify the parameters of an xDSL DPBO profile with the following command:
configure xdsl dpbo-profile (index) name (no) es-elect-length (no) es-cable-model-a (no) es-cable-model-b (no) es-cable-model-c (no) min-usable-signal (no) min-frequency (no) max-frequency (no) rs-elect-length (no) muf-control (no) offset

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

DLP 1207 Modify an xDSL DPBO profile

Use one of the following commands to complete the modification of the xDSL DPBO profile: a When the modifications must be kept:
configure xdsl dpbo-profile (index) modification complete

When the modifications must be cancelled:


configure xdsl dpbo-profile (index) modification cancel

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl dpbo-profile 1 modification start configure xdsl dpbo-profile 1 name test_profile configure xdsl dpbo-profile 1 modification complete

DLP 1207-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 1208 Configure xDSL power back off


Purpose
This procedure provides the steps to specify the power back off parameters for each upstream band for:

VDSL: Parameter A and B can be used for computing the PSD reference for US PBO for each band (including optional band). The range of parameter A for each band is 40..80.95 dBm/Hz in steps of 0.01 dBm/Hz. And the range of parameter B is 0..40.95 dBm/Hz in steps of 0.01 dBm/Hz. VDSL2: Parameter A and B can be used for computing the PSD reference for US PBO for each band (including optional band). The range of parameter A for each band is 40..80.95 dBm/Hz in steps of 0.01 dBm/Hz. And the range of parameter B is 0..40.95 dBm/Hz in steps of 0.01 dBm/Hz. The equal Far End Crosstalk (FEXT) reference electrical length parameter value for each band (including optional band) can be used for computing the PSD reference for US equal FEXT Power Back Off (PBO). The range of this parameter for each band is 1.8 dB to 63 dB in steps of 0.1 dB. The special value 0 dB indicates that the modem has to use dedicated mechanism to optimally apply the equal FEXT without providing any manual setting for this parameter. The special value 1.8 dB disables equal FEXT UPBO in the respective upstream band.

Prerequisite
The following prerequisite must be fulfilled before power back off can be configured:

The xDSL spectrum profile must have been created; see DLP 1129.

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

DLP 1208 Configure xDSL power back off

Procedure
Proceed as follows to configure the PBO parameters: 1 Do one of the following:

for PBO for VDSL, go to step 2 for PBO for VDSL2, go to step 4.

Configure the PBO parameters for VDSL with the following command:
configure xdsl spectrum-profile (index) vdsl pbo (band) (no) param-a <Xdsl::PboParamA> (no) param-b <Xdsl::PboParamB>

3 4

Go to step 5. Configure the PBO parameters for VDSL2 with the following command:
configure xdsl spectrum-profile (index) vdsl2 pbo (band) (no) equal-fext <Xdsl::EqualFextUpstreamParam> (no) param-a <Xdsl::PboParamA> (no) param-b <Xdsl::PboParamB>

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl spectrum-profile 4 modification start configure xdsl spectrum-profile 4 vdsl pbo 1 param-a 6000 configure xdsl spectrum-profile 4 modification complete

DLP 1208-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 1212 Create an IP user/subnet


Purpose
This procedure provides the steps to create IP users/subnet in iBridge and VLAN cross-connect L2 forwarding modes. For VLAN cross-connect, it is only supported on the C-VLAN cross-connect and S+C-VLAN cross-connect, not for the S-VLAN cross-connect or the IPoA-VLAN cross-connect.

Prerequisite
The following prerequisites must be fulfilled before an IP user/subnet can be created:

The LT must be planned; see DLP 2111. The xDSL profiles must have been created; see DLP 1129. A VLAN must have been created: for C-VLAN cross-connect, see DLP 1117 for S+C-VLAN cross-connect, DLP 1119 for iBridge, see DLP 1120. xDSL users have been created: for Ethernet users; see DLP 1124 for IPoA user (for C-VLAN cross-connect); see DLP 1174 for IPoA user (for iBridge); see DLP 1232

Procedure
Use the following procedure to create an IP user/subnet: 1 Add static IP user with the following command:
configure bridge port (port) vlan-id (index) static-user (no) ip-address (ipaddr)

STOP. This procedure is complete.

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

DLP 1212 Create an IP user/subnet

Configuration examples (Config#1): 1. For an ADSL user: configure bridge port 1/1/5/12:8:35 vlan-id 299 static-user ip-address 192.168.1.2/32

2. For a VDSL or VDSL2 user: configure bridge port 1/1/4/12 vlan-id 300 configure bridge port 1/1/4/12 vlan-id 300 static-user ip-address 192.168.1.3/32

DLP 1212-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 1215 Configure the impulse noise sensor on an xDSL line


Purpose
This procedure provides the steps to configure the impulse noise sensor on an xDSL line.

Note The impulse noise sensor configuration parameters are not stored persistently and will revert to their default values after a system reset.

Prerequisites
The following prerequisites must be fulfilled before the impulse noise sensor can be configured on an xDSL line:

The LT must be planned; see DLP 2111. The xDSL profiles must have been created; see DLP 1129. An xDSL user must have been created; see DLP 1124.

Procedure
Proceed as follows to configure the impulse noise sensor on an xDSL line: 1 Enable the impulse noise sensor on the xDSL line with the following command:
configure xdsl line (if-index) imp-noise-sensor

Note The impulse noise sensor can only be disabled by completely deleting the xDSL line.

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

DLP 1215 Configure the impulse noise sensor on an xDSL line

Configure the near-end impulse noise sensor parameters on this xDSL line with the following command:
configure xdsl imp-noise-sensor near-end (if-index) (no) inm-mode <Xdsl::InmMode> (no) inm-eq-inp-mode <Xdsl::InmEquivInpMode> (no) ins-sensitivity <Xdsl::InsSensitivity> (no) inm-cluster-cont <Xdsl::ClusterContinuation> (no) inm-iat-offset <Xdsl::InterArrivalTimeOffset> (no) inm-iat-step <Xdsl::InterArrivalTimeStep>

Configure the far-end impulse noise sensor parameters on this xDSL line with the following command:
configure xdsl imp-noise-sensor far-end (if-index) (no) inm-mode <Xdsl::InmMode> (no) inm-eq-inp-mode <Xdsl::InmEquivInpMode> (no) ins-sensitivity <Xdsl::InsSensitivity> (no) inm-cluster-cont <Xdsl::ClusterContinuation> (no) inm-iat-offset <Xdsl::InterArrivalTimeOffset> (no) inm-iat-step <Xdsl::InterArrivalTimeStep>

During the configuration and startup scenario, it can happen that the configuration is refused and the system returns CE (Configuration Error) or CNF (Configuration not feasible). The cause of the problem can be found using the following commands: a View the xDSL line activation failure error code with the following command :
show xdsl failure-status near-end (if-index)

View the description of that error code with the following command:
show xdsl failure-status near-end (if-index) detail

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl line 1/1/4/12 imp-noise-sensor configure xdsl imp-noise-sensor near-end 1/1/4/12 inm-mode enable inm-cluster-cont 5 configure xdsl imp-noise-sensor far-end 1/1/4/12 inm-mode enable inm-cluster-cont 5

DLP 1215-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 1217 Configure the xDSL overrule data


Purpose
This procedure provides the steps to manage the xDSL overrule data. The overrule data parameters give the operator the ability to overrule per-xDSL-line parameters defined in the xDSL service/spectrum profiles (see DLP 1129). These parameters will overrule the corresponding parameters of the profiles for all DSL flavors. When all the required parameters are configured, the complete overrule data has to be activated.

Prerequisites
The following prerequisite must be fulfilled before the xDSL overrule data can be configured:

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

Procedure
Proceed as follows to configure the xDSL overrule data: 1 Configure the xDSL per-line overrule data with the following command:
configure xdsl overrule-data (if-index) (no) max-bitrate-down <Xdsl::OverruleBitRate> (no) max-bitrate-up <Xdsl::OverruleBitRate> (no) max-delay-down <Xdsl::OverruleInterleavingDelay> (no) max-delay-up <Xdsl::OverruleInterleavingDelay> (no) imp-noise-prot-dn <Xdsl::OverruleImpNoiseProtection> (no) imp-noise-prot-up <Xdsl::OverruleImpNoiseProtection>

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

DLP 1217 Configure the xDSL overrule data

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

trgt-noise-down <Xdsl::OverruleTargetNoiseMargin> trgt-noise-up <Xdsl::OverruleTargetNoiseMargin> max-psd-down <Xdsl::OverrulePsdLevel> max-psd-up <Xdsl::OverrulePsdLevel> carrier-mask-down <Xdsl::OverruleCarrierMaskDown> carrier-mask-up <Xdsl::OverruleCarrierMaskUp> noise-psd-mode-dn <Xdsl::OverruleNoiseMode> noise-psd-mode-up <Xdsl::OverruleNoiseMode>

Configure the virtual/artifical noise in downstream direction with the following command:
configure xdsl overrule-data (if-index) v-noise-psd-pt-down (psd-point) (no) frequency <Xdsl::CustFreq> (no) psd <Xdsl::CustPsd>

Note The operator can enter enter the virtual/artificial noise psd shape in a user-friendly way. The operator can enter numbers corresponding to frequency and psd level.
The parameter noise-psd-mode-dn defines if the operator is configuring the virtual or the artificial noise psd and overrules the corresponding noise psd of the profile. If noise-psd-mode-dn is set to virtual and:

Noise Psd is empty, the v-noise-snr-down parameter in the profile will be overruled towards the modem with mode-1. Noise Psd is not empty, the v-noise-snr-down parameter in the profile will be overruled towards the modem with mode-2.

Configure the virtual noise in downstream direction with the following command:
configure xdsl overrule-data (if-index) v-noise-psd-pt-up (psd-point) (no) frequency <Xdsl::CustFreq> (no) psd <Xdsl::CustPsd>

Note The operator can enter the Rx/Tx virtual noise psd shape in a user-friendly way. The operator can enter numbers corresponding to frequency and psd level.
The parameter noise-psd-mode-up defines if the operator is configuring the receiver or transmitter refered virtual noise psd and overrules the corresponding noise psd of the profile. If noise-psd-mode-up is set to virtual or virtual-rx and:

Noise Psd is empty, the v-noise-snr-up parameter in the profile will be overruled towards the modem with mode-1. Noise Psd is not empty, the v-noise-snr-up parameter in the profile will be overruled towards the modem with mode-2 (virtual) or mode-3 (virtual-rx).

DLP 1217-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 1217 Configure the xDSL overrule data

Activate the xDSL Overrule Data with the following command:


configure xdsl overrule-data (if-index) active

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl overrule-data 1/1/4/12 max-bitrate-down 30000 max-bitrate-up 30000 configure xdsl overrule-data 1/1/4/12 active

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

DLP 1217 Configure the xDSL overrule data

DLP 1217-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 1219 Forced NT switchover


Purpose
This procedure provides the steps to be performed when an NT board must be replaced in a duplex configuration. This procedure is mandatory if the NT board to-be-replaced is the active NT board. By forcing a switchover towards the standby NT board, the NT board to-be-replaced will eventually become the standby NT board.

Procedure
The following commands can be used to view and update the current NT redundancy configuration: 1 Show the administrative status of the protection group with the following command:
show equipment protection-group (prot-group-id)

Show the redundancy control status of a protection group element with the following command:
show equipment protection-element (slot-id)

Configure the standby NT to become active one with the following command:
configure equipment protection-element (index) redcy-ctrl-status forced_active

STOP. This procedure is complete.

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

DLP 1219 Forced NT switchover

Configuration example (Config#1): show equipment protection-group 1 show equipment protection-element nt-a show equipment protection-element nt-b configure equipment protection-element nt-b redcy-ctrl-status forced_active

DLP 1219-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 1220 Manage the CDE profile


Purpose
This procedure provides the steps to manage the CDE profiles (CDE file package).

Prerequisite
The NE contains an OSWP, which is committed and active on the NT.

Procedure
Proceed as follows to manage the CDE profile in the NE: 1 Trigger the download of a CDE file with the following command:
admin software-mngt cdeprof download <SwMngt::DownloadServerId>

Monitor the download progress with the following command:


show software-mngt cdeprof dldstatus

Activate the downloaded CDE profile with the following command:


admin software-mngt cdeprof activate <SwMngt::CDEFileName>

STOP. This procedure is complete.

Configuration example (Config#1): admin software-mngt cdeprof download 169.178.10.1:/path_to_db/CDE_Profile_01 show software-mngt cdeprof dldstatus admin software-mngt cdeprof activate CDE_Profile_01

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

DLP 1220 Manage the CDE profile

DLP 1220-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 1221 Manage troubleshooting counters on LT


Purpose
This procedure provides the steps to manage the troubleshooting counters.

Procedure
Proceed as follows to manage the troubleshooting counters: 1 Enable or disable the dynamic troubleshooting counters with the following command:
configure trouble-shooting statistics interface (if-index)

Use one or more of the following commands to view the troubleshooting counters: a View all the troubleshooting counters of a port with the following commands:
show trouble-shooting statistics interface (if-index)

Note When this show command is invoked, all the commands in underlying nodes are automatically executed (see step b, step c, step d and step e).

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

DLP 1221 Manage troubleshooting counters on LT

View the troubleshooting counters of a port (DSL or Ethernet) or a PVC interface with the following commands:
show trouble-shooting statistics interface (if-index) user (port)

Note When this show command is invoked, all the commands in underlying nodes are automatically executed (see step c, step d and step e).
c View the extensive and summary counters of a VLAN port with the following commands:
show trouble-shooting statistics interface (if-index) user (port) vlan (vlan-id)

Note When this show command is invoked, all the commands in underlying nodes are automatically executed (see step d and step e).

View the summary counters of a VLAN port with the following commands:
show trouble-shooting statistics interface (if-index) user (port) vlan (vlan-id) summary

View the extensive counters of a VLAN port with the following commands:
show trouble-shooting statistics interface (if-index) user (port) vlan (vlan-id) extensive

View the troubleshooting counters of a UNI interface with the following command:
show trouble-shooting statistics uni-interface (if-index)

Note For this command, there is no need to first enable or disable the troubleshooting counters.

When required, reset the reset summary and extensive trouble-shooting counters with the following command:
admin trouble-shooting interface (control-index) clear-statistics

STOP. This procedure is complete.

DLP 1221-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 1221 Manage troubleshooting counters on LT

Configuration example (Config#1): configure trouble-shooting statistics interface 1/1/5/12 show trouble-shooting statistics interface 1/1/5/12 user port:8:35 admin trouble-shooting interface 1/1/5/12 clear-statistics

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

DLP 1221 Manage troubleshooting counters on LT

DLP 1221-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 1225 Configure the p-bit counter on a VLAN port


Purpose
The p-bit traffic counter is designed for customers who need volume-based and separate billing on different services offered by the p-bit and VLAN setting. Per p-bit value range, 2 counters are defined:

Total upstream user traffic which is successfully forwarded to the NT. The count is in number of bytes. The traffic is counted after the policers. Total downstream user traffic which is successfully forwarded to the bridge port/DSL line. The count is in number of bytes. The traffic is counted after the policers, queueing and so on

These rolling 64-bit counters are updated once every 15 minutes.

For 48-line boards, a maximum of eight counter pairs (upstream counter and downstream counter) can be configured per user line. For 72-line boards, a maximum of four counter pairs (upstream counter and downstream counter) can be configured per user line.

The counter pairs can be freely chosen over the VLAN value and the p-bit value or a consecutive range(for example, [0..2]).

Prerequisite
The following prerequisites must be fulfilled before the p-bit counter can be configured on a VLAN port:

a VLAN must be assigned to a forwarder on the user line; see DLP 1124 step 8 or DLP 1147 step 4.

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

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

Procedure
Proceed as follows to configure the p-bit counter on a VLAN port:

Note This procedure assumes that the p-bits are derived from the DSCP bits.

1 2

If required, configure a marker profile for Dot1P alignment; see DLP 1134. Assign the marker profile to a a QoS session profile:
configure qos profiles session (name) logical-flow-type <Qos::LogicalFlowType> (no) up-policer none | name:<Policer Profile name> (no) down-policer none | name:<Policer Profile name> (no) up-marker none | name:<Marker Profile name>

Assign a VLAN and the marker profile to the bridge port and with the following command:
configure bridge port (port) vlan-id (index) (no) tag <Vlan::PortUntagStatus> (no) network-vlan <Vlan::StackedVlan> (no) vlan-scope <Vlan::VlanScope> (no) qos <Vlan::QosPolicy> (no) qos-profile <Vlan::QosProfileName>

Configure the p-bit counter with the following command:


configure vlan pbit-statistics port (vlan-port) min-dot1p <Vlan::Dot1pMin> max-dot1p <Vlan::Dot1pMax>

The p-bit counters can be viewed with the following command:


show vlan pbit-statistics port (vlan-port) [min-dot1p <Vlan::Dot1pMin>] [max-dot1p <Vlan::Dot1pMax>]

STOP. This procedure is complete.

Configuration example (Config#1): This example assumes that vlan-port 1/1/5/12:8:35:299 has been created. configure qos profiles marker d1p-alignment Dot1Palign enable configure qos profiles session Pbitcounter up-marker name:Dot1Palign logical-flow-type generic configure bridge port 1/1/5/12:8:35 vlan-id 299 qos-profile name:Pbitcounter configure vlan pbit-statistics port vlan-port:1/1/5/12:8:35:299 min-dot1p 1 max-dot1p 2 DLP 1225-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 1225 Configure the p-bit counter on a VLAN port

show vlan pbit-statistics port vlan-port:1/1/5/12:8:35:299

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

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

DLP 1225-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 1232 Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge
Purpose
This procedure provides the steps to create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge.
Figure DLP 1232-1: Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge
VlanPort BridgePort IPoA/IPoE interworking ATM PVC (IPoA) xDSL

DLP

VLAN PVID LT NT ISAM

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

IWL

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

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

The LT must be planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129. A VLAN on the LT must have been configured for iBridge; see DLP 1120.

Procedure
Proceed as follows to an xDSL IPoA user and add this user to a VLAN on the LT for iBridge: 1 Create an xDSL line with the following command:
configure xdsl line (if-index) service-profile none | <Xdsl::ProfilePointer> | name: <PrintableString> spectrum-profile none | <Xdsl::ProfilePointer> | name:<PrintableString> (no) dpbo-profile <Xdsl::LineDpboProfile> (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 (no) g992-3-am (no) g992-5-a (no) g992-5-b (no) ansi-t1.424 (no) etsi-ts (no) itu-g993-1 (no) ieee-802.3ah (no) g992-5-aj (no) g992-5-am (no) g993-2-8a (no) g993-2-8b (no) g993-2-8c (no) g993-2-8d (no) g993-2-12a (no) g993-2-12b (no) g993-2-17a (no) g993-2-30a (no) carrier-data-mode <Xdsl::CarrierDataMode> (no) admin-status (no) transfer-mode <Xdsl::TpsTcMode>

DLP 1232-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 1232 Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge

Configure the xDSL line with the following command:


configure interface port xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> /<Eqpt::Port> admin-up (no) user <Itf::asamIfExtCustomerId>

Create an ATM PVC with the following command:


configure atm pvc (port-index) admin-up aal5-encap-type vc-mux-routed

Create the IPoA L2 interworking port and the L2 interworking gateway with the following command:
configure ipoa/e-iw port (interworking-port) user-ip <Ip::V4AddressHex> configure ipoa/e-iw gateway (vlan-id) gw-ip-addr <Ip::V4AddressHex>

Create a bridge port with the following command:


configure bridge port (port) mac-learn-off

Assign a VLAN to the bridge port with the following command:


configure bridge port (port) vlan-id (index)

Set the PVID with the following command:


configure bridge port (port) pvid (vlan-id)

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl line 1/1/5/8 service-profile 7 spectrum-profile 5 admin-up configure interface port xdsl-line:1/1/5/8 user IPoA cross-connect configure atm pvc 1/1/5/8:8:35 aal5-encap-type vc-mux-routed configure ipoa/e-iw port 1/1/5/8:8:35 user-ip 192.168.150.2 configure ipoa/e-iw gateway 100 gw-ip-addr 192.168.150.1 configure bridge port 1/1/5/8:8:35 mac-learn-off configure bridge port 1/1/5/8:8:35 vlan-id 100 configure bridge port 1/1/5/8:8:35 pvid 100

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

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

DLP 1232-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 1253 Configure the third-party equipment management port on the 7356 FD REM
Purpose
The ISAM 7356 FD REM supports an external 10/100 Base-T network port for connecting third-party equipment that needs to be managed over an Ethernet network, and which is located in the same cabinet as the 7356 FD REM.

Note 1 This procedure is only applicable for 7356 FD REM equipped with a controller board. Not for 7356 FD REM equipped with an NRNT-A board.
The third-party equipment uses an Ethernet interface with untagged frames for remote management. this interface is still foreseen on the NRNT-A board , but needs to be configured using the standalone ISAM commands.

Note 2 The commands configure system peripheral-mgnt-vlan-id <vlan-id> and configure system security peripheral-mgnt still exist on the 7356 FD-REM with NRNT-A, for cases where this mini FD-REM is equipped with several legacy 7356 FD-REMs.
The port is not intended for volume traffic, it can handle a sustained throughput of 50 kb/s only in each direction.

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

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

The following assumptions are made about the third-party equipment management traffic:

The third-party equipment uses an Ethernet interface with untagged frames for remote management. The third-party equipment can be identified in the network by one of the following: A pre-configured IP address, for which a destination MAC address can be retrieved through use of the ARP protocol. A public MAC address. The third-party equipment management traffic is conveyed in a dedicated VLAN, configurable by the operator The communication protocol used for remote managing of the third-party equipment allows detecting of communication corruption or disruption. The ISAM itself does not support detection of malfunctions on the FD-REM external equipment management port, and will not generate alarms related to the usage of this port.

Procedure
Proceed as follows to configure the third-party management port: 1 Configure the tagging with a dedicated VLAN value of the third-party equipment management traffic, with the following command:
configure system peripheral-mgnt-vlan-id <vlan-id>

Note <vlan-id> specifies the management VLAN to be used for traffic on this port, in the range [14093].
This is the minimum configuration necessary for use of the FD-REM external equipment management port. The VLAN cross-connect behavior is default and is not configurable on this port.

DLP 1253-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 1253 Configure the third-party equipment management port on the 7356 FD REM

Configure filtering on the destination MAC address for the upstream 3rd party equipment management traffic, with the following command:
configure system security peripheral-mgnt mac-filter (index-num) [no] filter <MacRangeFirst, MacRangeLast>

Note The index number specifies the number of the filter in the white list (that is, the admitted address ranges) of 20 entries, with range [120].
The parameters < MacRangeFirst, MacRangeLast > specify the consecutive upstream destination MAC address range that will be admitted by this filter entry. The default value for all filter entries is <00.00.00.00.00.00, 00.00.00.00.00.00>, that is, no traffic is allowed at all. This offers enhanced security in remote cabinets. In practice, each entry of this list consists of:

An Original manufacturer Unique Identifier (OUI) value, covering the 3 Most Significant Bytes (MSB) of the public MAC address A start value and an end value of a single consecutive range of MAC addresses for the above OUI, covering at maximum the full 3 Least Significant Bytes (LSB) of the public MAC address.

STOP. This procedure is complete.

Configuration example (Config#1): configure system peripheral-mgnt-vlan-id 4093 configure system security peripheral-mgnt mac-filter 1 filter 10.3F.20.00.00.00, 10.3F.20.00.FF.FF

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

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

DLP 1253-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 1255 Configure a port on the NELT-B LT


Purpose
This procedure provides the necessary steps to configure a user port on an Ethernet LT board NELT-B (connected to an Ethernet line). The configurable parameters of this port are its type and its port rate mode. The Ethernet port type can be:

User to Network Interface (UNI): the Ethernet line connects to a subscriber (this is the default value) Network to Network Interface (UNI):the Ethernet line connects to a subtending DSLAM (or business user).

The reason why it is important to distinguish the port type is because the behavior of the system might be different for a number of activities (for example, in case of NNI the subtending node already covers part of the functionality, such as security or protocol control). Figure DLP 1255-1 shows the two different port types in the network. The arrow points to the port location in the scope of this procedure.

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

DLP 1255 Configure a port on the NELT-B LT Figure DLP 1255-1: Ethernet LT Port Types
DLP

UNI

NNI Ethernet LT NT ISAM ISAM

Note The only Ethernet LT board that currently supports an NNI port type is the NELT-B. All other Ethernet boards only support UNI ports directly to the subscriber. Ethernet LT boards UNI functionality may differ per board.

Prerequisite
The board must have been planned and must be operational; see DLP 2111.

Procedure
Proceed as follows to configure the Ethernet port type and port rate mode: 1 Configure the Ethernet port type (uni or nni) with the following command:
configure ethernet line (if-index) port-type <ETHITF::PortType> (no) admin-up

Note The porttype is an optional parameter in this command, with default value uni.

DLP 1255-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 1255 Configure a port on the NELT-B LT

Configure the port power status with the following command:


configure ethernet line (if-index) mau (index) type <ETHITF::MauType> power <ETHITF::Power>

Note The NELT-B board supports Ethernet port power status configuration. The default power status is down, so to make the Ethernet port on the NELT-B board up , the port power status should be set to up. For NELT-A board, the power status is always up and is not configurable.
3 Configure the port rate mode (= the MAU type) with the following command:
configure ethernet line (if-index) mau (index) type <ETHITF::MauType> power <ETHITF::Power>

Note 1 Always keep the MAU index to 1. Note 2 The MAU type is related to the part number (P/N) of the SFP/XFP medium used on the line (connecting the port). Table DLP 1255-1provides an indicative list.
Table DLP 1255-1: List of MAU types
Part Number 3FE25777AA 3FE25778AA 3FE29194AA 3FE29194BA 3FE29195AA 3HH01046PA 3FE63343AA 3FE28784AA 3FE25773AA 3FE25773CA 3FE25774AA 3FE25775AA 3FE25776AA 3FE25771AA 3FE25771AB 3FE25771AC 3FE25771AD (1 of 2) MAU Type 100BaseFXFD 100BaseLX10 1 100BaseBX10D 100BaseBX10D 100BaseBX10U 100baseTXFD 100baseTXFD 1000baseTFD 1000baseSXFD 1000baseSXFD 1000BaseLX10 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Channel 1 1

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

DLP 1255 Configure a port on the NELT-B LT

Part Number 3FE25771AE 3FE25771AF 3FE25771AG 3FE25771AH 3FE25771CA 3FE29549CA 3FE29550CA 3FE29551CA 3FE29552CA 3FE29553CA 3FE29554CA 3FE29555CA 3FE25772AA 3FE25772AB 3FE28785AA 3FE28785AB 3FE65107AA 3FE65106AA (2 of 2)

MAU Type 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000baseLXFD 1000BaseBX10U 1000BaseBX10D 1000baseLXFD 1000baseLXFD 100BaseBX10D 1000BaseBX10D

Channel 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2

Note For example: when the Alcatel-Lucent part number of the SFP is 3FE25774AA, the MAU type is 1000baselx10.

Set the administrative state of the Ethernet line up again with the following command:
configure ethernet line (if-index) admin-up

STOP. This procedure is complete

Configuration examples (Config#1): configure ethernet line 1/1/13/[1,3,5,7] port-type nni no admin-up configure ethernet line 1/1/13/[1,3,5,7] mau 1 power up configure ethernet line 1/1/13/[1,3,5,7] mau 1 type 1000basetfd configure ethernet line 1/1/13/[1,3,5,7] admin-up

DLP 1255-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 1257 Configure a line with an xDSL RTX profile


Purpose
This procedure provides the steps to configure an xDSL line with the parameters that are supported for the configuration of the Standard ARQ (G998.4) feature. All these parameters are also described in ITU-T G.997.1 Amd1.

Prerequisites
The following prerequisite must be fulfilled before standard ARQ provisioning can be configured:

The LT board must be planned; see DLP 2111.

Procedure
Proceed as follows to configure standard ARQ provisioning: 1 Create a RTX profile with the following command:
configure xdsl rtx-profile (index) name <name>

Configure the RTX profile parameters with the following command:


configure xdsl rtx-profile (index) name <name> (no) rtx-mode-dn (no) rtx-mode-up (no) min-exp-thrpt-dn (no) min-exp-thrpt-up (no) plan-exp-thrpt-dn (no) plan-exp-thrpt-up (no) max-exp-thrpt-dn (no) max-exp-thrpt-up (no) max-net-rate-dn

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

DLP 1257 Configure a line with an xDSL RTX profile

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

max-net-rate-up min-delay-dn min-delay-up max-delay-dn max-delay-up min-inp-shine-dn min-inp-shine-up min-inp-rein-dn min-inp-rein-up int-arr-time-dn int-arr-time-up shine-ratio-dn shine-ratio-up leftr-thresh-dn leftr-thresh-up

Activate the RTX profile with the following command:


configure xdsl rtx-profile (index) name <name> active

Assign the RTX profile to a port with the following command:


configure xdsl line <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> rtx-profile (index)

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl rtx-profile 1 name RTXProfile1 configure xdsl rtx-profile 1 rtx-mode-dn forced rtx-mode-up forced configure xdsl rtx-profile 1 min-inp-rein-dn 4 min-inp-rein-up 4 configure xdsl rtx-profile 1 max-delay-dn 10 max-delay-up 10 configure xdsl rtx-profile 1 active configure xdsl line 1/1/4/12 rtx-profile 1

DLP 1257-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 1258 Modify an xDSL RTX profile


Purpose
This procedure provides the steps to modify an existing xDSL RTX profile.

Prerequisite
The following prerequisite must be fulfilled before a xDSL RTX profile can be modified:

The xDSL RTX profile must have been created; see DLP 1257.

Procedure
Proceed as follows to modify a xDSL RTX profile: 1 Start the modification of a xDSL RTX profile with the following command:
configure xdsl rtx-profile (index) modification start

Modify the parameters of an xDSL RTX profile with the following command:
configure xdsl rtx-profile (index) name <name> (no) rtx-mode-dn (no) rtx-mode-up (no) min-exp-thrpt-dn (no) min-exp-thrpt-up (no) plan-exp-thrpt-dn (no) plan-exp-thrpt-up (no) max-exp-thrpt-dn (no) max-exp-thrpt-up (no) max-net-rate-dn (no) max-net-rate-up (no) min-delay-dn (no) min-delay-up (no) max-delay-dn (no) max-delay-up (no) min-inp-shine-dn

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

DLP 1258 Modify an xDSL RTX profile

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

min-inp-shine-up min-inp-rein-dn min-inp-rein-up int-arr-time-dn int-arr-time-up shine-ratio-dn shine-ratio-up leftr-thresh-dn leftr-thresh-up

Note The name of the xDSL RTX profile can be modified without executing step 1 and step 3.

Use one of the following commands to complete the modification of the xDSL RTX profile: a When the modifications must be kept:
configure xdsl rtx-profile (index) modification complete

When the modifications must be cancelled:


configure xdsl rtx-profile (index) modification cancel

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl rtx-profile 1 modification start configure xdsl rtx-profile 1 rtx-mode-dn preferred rtx-mode-up preferred configure xdsl rtx-profile 1 modification complete

DLP 1258-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 1270 Configure spanning tree on the NELT-B LT


Purpose
Logically, the ISAM does not work in transparent mode. The traffic from a user port is only forwarded to a network port, and the traffic from a network port is forwarded to defined user ports. So, even if multiple active paths exist in user ports, no topology loops are introduced by ISAM equipment. So, the main goal of STP/RSTP/MSTP in NELT-B board is to provide link redundancy.

Note 1 NELT-B should always work as Root bridge. This should be ensured by the operator. Note 2 xSTP is only supported on NNI port. Note 3 NELT-B can support MSTP across LTs. The other switches in network will be responsible for reconfiguring the port to designated port/alternate port.

Prerequisite
The following prerequisite must be fulfilled before MSTP can be configured:

The VLANs mapped to an MSTP instance must be created; see DLP The port-type of the port must be NNI; see DLP 1255.

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

DLP 1270 Configure spanning tree on the NELT-B LT

Procedure
Proceed as follows to configure xSTP usage: 1 Configure the general MSTP parameters with the following command:
configure xstp general enable-stp (no) priority <Mstp::StpPriority> (no) max-instance-num <Mstp::StpMaxInstanceNumber> (no) max-age <Mstp::StpMaxAge> (no) hello-time <Mstp::StpHelloTime> (no) forward-delay <Mstp::StpFwDelay> (no) version <Mstp::StpProtVersion> (no) tx-hold-count <Mstp::StpTxHoldCount> (no) path-cost-type <Mstp::StpPathCostType> (no) max-hop-count <Mstp::StpMaxHopCount> region-name <Mstp::StpRegionName> (no) region-version <Mstp::StpRegionVersion> (no) config-id-sel <Mstp::StpConfigIdSelector>]

Note 1 The configuration of the parameters applies for the whole bridge. Note 2 The bridge max-age value should be less than or equal to (2 * ((forward-delay/100)-1) and should be greater than or equal to (2 * ((Port hello-time/100) + 1)). Note 3 The bridge hello-time is only applicable when the version is STP or RSTP. In case the version is MSTP, the port hello-time is used.
2 Configure the MSTP parameters for a specific MSTP instance with the following command:
configure xstp instance (instance) (no) priority <Mstp::StpPriority>

Map a VLAN on the MSTP instance with the following command:


configure xstp instance (instance) (no) associate-vlan (vlan)

Note One or more VLANs can be associated to an instance, but one VLAN cannot be assigned to different instances.

DLP 1270-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 1270 Configure spanning tree on the NELT-B LT

Configure the port parameters for the common instance with the following command:
configure xstp port (port) (no) priority <Mstp::MstpPortPriority> (no) enable-stp path-cost <Mstp::MstpPathCost> (no) edge-port (no) admin-p2p <Mstp::MstpAdminP2PPort> (no) hello-time <Mstp::StpHelloTime>

Note By default MSTP is disabled on the ports.

Configure the MSTP parameters for a specific port-instance with the following command:
configure xstp port-instance (port) instance <Mstp::MstpInstance> (no) priority <Mstp::MstpPortPriority> (no) disable-stp path-cost <Mstp::MstpPathCost>

View the MSTP operational information: a View all the common spanning tree instances for the whole bridge with the following command:
show xstp bridge

View the parameters of a multiple spanning tree instance with the following command:
show xstp instance [(instance)]

View the MSTP port information with the following command:


show xstp port [(port)]

View the MSTP port instances information with the following command:
show xstp port-instance [(port) [instance <Mstp::MstpInstance>]]

STOP. This procedure is complete.

Configuration example (Config#1):

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

DLP 1270 Configure spanning tree on the NELT-B LT

In MSTP mode: configure xstp general enable-stp priority 61440 max-age 1000 forward-delay 2000 configure xstp port 1/1/13/1 enable-stp path-cost 200000 configure xstp instance 1 configure xstp instance 1 associate-vlan 100 configure xstp port-instance 1/1/13/1 instance 1 no disable-stp path-cost 200000 In RSTP mode: configure xstp general version rstp configure xstp general max-age 2100 configure xstp general hello-time 500 forward-delay 2500 configure xstp port 1/1/13/1 enable-stp path-cost 200000

DLP 1270-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 1271 Configure link aggregation on the NELT-B LT


Purpose
This procedure provides the necessary steps to configure link aggregation function on port (UNI/NNI) on an Ethernet LT board NELT-B. Link Aggregation allows combining multiple Ethernet links into a single logical group (a Link Aggregation Group ,or, LAG) that is regarded as a single port /interface by all higher layers such as Bridge. Link aggregation introduced on NELT-B is for:

Provide higher bandwidth capability: Aggregate two or more physical Ethernet links into one logical link. So the capacity of multiple links is combined into one logical link. Perform load sharing on multiple link: The processing and communications activity is distributed across multiple links in a trunk so that no single link is overwhelmed. Provide Ethernet link redundancy: Link aggregation prevents the failure of any single component link from leading to a disruption of the communications between the interconnected devices.

Note 1 Cross LT link aggregation is not supported. Which mean cross LTs ports can not be aggregated into one link aggregation group. Note 2 Only port with same port type and same rate mode could be aggregated into a group. Note 3 Provide the ability to aggregate up to max 8 port in a link aggregation group.

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

DLP 1271 Configure link aggregation on the NELT-B LT

General
This node allows specification of Link Aggregation Group parameters. A Link Aggregation Group(LAG) is identified by means of the primary port.The default Ethernet link of the LAG could be seen as the primary port of the LAG forever.such as, for LAG 1/1/1/1, its primary link is always 1/1/1/1. The operator could add/remove Ethernet port for a LAG. The Ethernet ports in a LAG are seen as the member ports of a LAG. The configuration should be performed for the primary port.

Prerequisite
The following prerequisite must be fulfilled before link aggregation can be configured:

The port-type and rate mode of the member port must be same; see DLP 1255.

Procedure
Proceed as follows to configure link aggregation: 1 Specify the general Link Aggregation parameters with the following command:
configure link-agg general (no) priority <Lacp::SysPriority>

Specify the Link Aggregation port parameters with the following command:
configure link-agg port (port) (no) passive-lacp (no) short-timeout (no) actor-port-prio <Lacp::PortActorPortPriority>

Specify the Link Aggregation Group parameters with the following command:
configure link-agg group (group) load-sharing-policy <Lacp::LoadSharingPolicy> (no) max-active-port <Lacp::MaxActivePort> mode <Lacp::Mode>

Add/remove member links from the Link Aggregation Group with the following command:
configure link-agg group (group) (no) port (port)

View information for a Link Aggregation Group with the following command: a View information for a member port of a Link Aggregation Group with the following command:
show link-agg port-info [(port)]

DLP 1271-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 1271 Configure link aggregation on the NELT-B LT

View information about a Link Aggregation Group with the following command:
show link-agg group-info [(group)]

View information about a Link Aggregation Group member port status with the following command:
show link-agg member-port [(group)][port]

STOP. This procedure is complete.

Configuration example (Config#1): configure link-agg general priority 7 configure link-agg port 1/1/13/[1,3,5,7] actor-port-prio 10 configure link-agg group 1/1/13/[1] max-active-port 2 configure link-agg group 1/1/13/[1] mode dynamic configure link-agg group 1/1/13/[1] load-sharing-policy mac-src configure link-agg group 1/1/13/1 port 1/1/13/[3,5,7] show link-agg group-info 1/1/13/1 show link-agg port-info 1/1/13/1 show link-agg member-port 1/1/13/1 show interface port la-group:1/1/13/1

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

DLP 1271 Configure link aggregation on the NELT-B LT

DLP 1271-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 1282 Configure the fairness SLA on the NELT-B LT


Purpose
This procedure provides the necessary steps to configure a SLA with fairness of service support among the subscribers. There are two main deployment scenarios: 1 User-fairness on UNI in upstream, and user-fairness on UNI in downstream (supported by the default round robin scheduling mechanism among UNI ports, no configuration is needed). User-fairness on NNI in upstream.

In the NELT-B board, the total aggregated bandwidth of a UNI can be 2.5Gbps or 1Gbps depend on the type of NT board, the total aggregated bandwidth of NNI can be 2.5Gbps/5 Gbps or 10Gbps/20 Gbps depending on the type of NT board and whether the NT is simplex or duplex. Considering the range of applications being considered for the NELT-B, that is, 1 2 3 Mix of FE and GE interfaces Mix of residential (UNI) and business users (NNI) A potentially high multiplexing ratio (36:1 or 36:2.5)

It is essential to guarantee some fairness among the subscribers. Fairness in the upstream direction is assured as follows: a minimum bandwidth and a maximum bandwidth can be specified per subscriber (and this for real-time and non-real-time traffic): 1 2 The service guarantee is achieved by means of a two-rate three-color metering per subscriber, combined with color-aware WRED buffer admission control. Traffic below the minimum rate (expressed by a CIR/CBS) is colored green. Note that the minimum rate is only guaranteed if the aggregate CIR is smaller than the capacity offered by NELT-B to the UNIs or NNIs (see above). But the total minimum rate of NNI and UNI shall be less than or equal to backplane. The aggregate CIR of

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

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

UNIs are less than or equal to 2.5Gbps or 1Gbps depending on the type of NT board, and UNI traffic colored in green is still colored in green as merged with NNI traffic, the aggregate CIR of NNIs are less than backplane speed - 2.5Gbps or 1Gbps. 3 Traffic exceeding the maximum rate (expressed by a PIR/PBS) is immediately discarded when the operator configures to discard the out-of-profile traffic (recommendation); traffic exceeding the maximum rate is colored red when the operator configures to color the traffic. Traffic between the minimum and maximum rates is colored yellow. Color-aware WRED is applied at the egress buffer so that excess traffic is only accepted if enough resources are left free by other subscribers, allowing to keep guaranteed resources for the green traffic

4 5

Prerequisite
The following prerequisite must be fulfilled before SLA with fairness support can be configured:

The corresponding Ethernet ports must be a UNI port or NNI; see DLP 1255 A VLAN must have been created: For creation of a VLAN cross-connect; see NTP 2104 For creation of an iBridge; see NTP 2105 The corresponding QoS session profiles with upstream policer profile with color blind trTCM policer have been created; see DLP 1134

Procedure
QoS session profile in VLAN port or bridge port is described in DLP 1134.

DLP 1282-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 1283 Troubleshooting congestion on the NELT-B LT


Purpose
This procedure provides the commands for troubleshooting on the NELT-B board due to possible packet drop in congestion areas. The logical ports 37, 38, 39 and 40 are used as measurement points introduced to monitor such possible packet drops. Note that these are not operator managed and control entities (via explicit commands). The UNI traffic is aggregated into logical port 37 (see Figure DLP 1283-1) The UNI/NNI traffic is aggregated into logical port 39 and logical port 40 from NTA or NTB. Traffic that must be dropped due to congestion issues, may be dropped in logical port 37, logical port 38, logical port 39 and logical port 40. In order to monitor packet drops at these locations, performance counters are used:

Performance packet counter = count of discarded packets/(count of transmitted packets + count of discarded packets) Performance byte counter = count of discarded bytes/(count of transmitted bytes + count of discarded bytes)

The calculated ratios are expressed as a 10-6 value. For example, if the performance packet counter is 80, this means that 80 x 10-6 or 0.000008 packet drops occurred.

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

DLP 1283 Troubleshooting congestion on the NELT-B LT Figure DLP 1283-1:


UNI construct CATAN Switch

Packet processor Max1.7Mpps

1G or 2.5G 37

UNI UNI NNI

38

39

40

Backplane

Input buffers@CATAN (2 queues, SP, p-bit-based) Egress queues, programmable configuration based on forwarder p-bit-to-TC mapping

Egress queues, programmable configuration based on system level p-bit-to-TC mapping

The performance packet drop in logical port 37 is indicated by the upstream buffer overflow counter The performance packet drop in logical port 38 is indicated by the downstream buffer overflow counter The performance packet drop in logical port 39 and logical port 40 is indicated by the backplane counters

Procedure
Proceed as follows to troubleshoot congestion at the NELT-B LT board: 1 To troubleshoot traffic at logical ports 37 and 38 and monitor the upstream and downstream unicast counters: i View the previous quarter counter with the following command:
show qos statistics buffer-overflow prev-15min (equip-slot) [interval-num<Qos::CounterInterval>]

ii

View the current quarter counter with the following command:


show qos statistics buffer-overflow current-15min (equip-slot)

DLP 1283-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 1283 Troubleshooting congestion on the NELT-B LT

iii

View the previous day counter with the following command:


show qos statistics buffer-overflow prev-1day (equip-slot)

iv

View the current day counter with the following command:


show qos statistics buffer-overflow current-1day (equip-slot)

Note Other QoS statistics counters are not used for for NELT-B.

To troubleshoot traffic at logical ports 39 and 40 and monitor the counters of bckpln-low-dis-frame and bckpln-low-dis-bytes , use the following commands: i View the previous quarter counter with the following command:
show qos statistics lt-queue prev-15min (index)

ii

View the current quarter counter with the following command:


show qos statistics lt-queue current-15min (index)

Note Other QoS statistics counters are meaningless for NELT-B.

STOP. This procedure is complete.

Configuration example (Config#1): show qos statistics buffer-overflow prev-15min lt:1/1/13 show qos statistics buffer-overflow current-15min lt:1/1/13 show qos statistics buffer-overflow prev-1day lt:1/1/13 show qos statistics buffer-overflow current-1day lt:1/1/13 show qos statistics lt-queue prev-15min 1/1/13 show qos statistics lt-queue current-15min 1/1/13

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

DLP 1283 Troubleshooting congestion on the NELT-B LT

DLP 1283-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 1291 Configure a Vectoring Control Entity profile and associate it to a board
Purpose
This procedure provides the steps to configure a board with vectoring-processing-related parameters. In case the operator wants to have crosstalk cancellation, a non-null Vectoring Control Entity (VCE) profile should be associated to a board which is capable of processing the vectoring algorithms (Board Level Vectoring (BLV) LT board or System Level Vectoring (SLV) Vector Processing (VP) board).

Note xDSL line crosstalk parameters which are applicable to the vectored line, are configured at line level; see DLP 1295.

Vectoring, Crosstalk Cancellation is standardized for VDSL2 in G.993.5 and its management model in G.997.1 Amd1.

Prerequisites
The following prerequisite must be fulfilled before the VCE profile provisioning can be configured:

For BLV: the BLV LT board must be planned; see DLP 2111 For SLV: the SLV VP board must be planned; see DLP 2111

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

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

Procedure
Proceed as follows to configure the VCE profile provisioning: 1 If required, the maximum number of vectoring control entity profiles and the next free vectoring control entity profile index can be viewed with the following command:
show xdsl profiles

Create a VCE profile with the following command:


configure xdsl vce-profile (index) name <name>

Configure the VCE profile parameters with the following command:


configure xdsl vce-profile (index) name <name> (no) vce-gain-mode <Xdsl::VectGainAchievedMode> (no) vce-join-timeout <Xdsl::VectJoinTime> (no) vce-min-par-join <Xdsl::VectMinParallelJoins> (no) vce-hist-pcoder <Xdsl::VectHistPrePostCoder> (no) vce-band-plan <Xdsl::VectBandPlan>

Activate the VCE profile with the following command:


configure xdsl vce-profile (index) name <name> active

Note 1 Creation, configuration and activation of a profile can be done in one command. Note 2 The xDSL vectoring control entity profile must be activated within 15 minutes after it has been created, otherwise it will be deleted.
5 Assign the VCE profile to a board with the following command:
configure xdsl board <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::SlotId> (no) vce-profile <Xdsl::BoardVceProfile>

STOP. This procedure is complete.

DLP 1291-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 1291 Configure a Vectoring Control Entity profile and associate it to a board

Configuration example for BLV (Config#1): configure xdsl vce-profile 1 name VceProfile1 configure xdsl vce-profile 1 vce-gain-mode during-showtime configure xdsl vce-profile 1 vce-join-timeout 60 vce-min-par-join 16 configure xdsl vce-profile 1 vce-hist-pcoder enable2 configure xdsl vce-profile 1 vce-band-plan annex-b-997e configure xdsl vce-profile 1 active configure xdsl board 1/1/15 vce-profile 1 Configuration example for SLV (Config#1): configure xdsl vce-profile 2 name VceProfile2 configure xdsl vce-profile 2 vce-gain-mode during-showtime configure xdsl vce-profile 2 vce-join-timeout 60 vce-min-par-join 16 configure xdsl vce-profile 2 vce-hist-pcoder enable2 configure xdsl vce-profile 2 vce-band-plan annex-b-997e configure xdsl vce-profile 2 active configure xdsl board 1/1/16 vce-profile 2

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

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

DLP 1291-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 1292 Modify a Vectoring Control Entity profile


Purpose
This procedure provides the steps to modify an existing Vectoring Control Entity (VCE) profile.

Prerequisites
The following prerequisite must be fulfilled before a VCE profile can be modified:

The VCE profile must have been created and activated; see DLP 1291.

Procedure
Proceed as follows to modify a VCE profile: 1 Start the modification of a VCE profile with the following command:
configure xdsl vce-profile (index) modification start

Modify the parameters of an VCE profile with the following command:


configure xdsl vce-profile (index) name <name> (no) vce-gain-mode <Xdsl::VectGainAchievedMode> (no) vce-join-timeout <Xdsl::VectJoinTime> (no) vce-min-par-join <Xdsl::VectMinParallelJoins> (no) vce-hist-pcoder <Xdsl::VectHistPrePostCoder> (no) vce-band-plan <Xdsl::VectBandPlan>

Note The name of the VCE profile can be modified without executing step 1 and step 3.

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

DLP 1292 Modify a Vectoring Control Entity profile

Use one of the following commands to complete the modification of the VCE profile: a When the modifications must be kept:
configure xdsl vce-profile (index) modification complete

When the modifications must be cancelled:


configure xdsl vce-profile (index) modification cancel

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl vce-profile 1 modification start configure xdsl vce-profile 1 vce-gain-mode at-init vce-join-timeout 15 vce-min-par-join 8 vce-hist-pcoder disable vce-band-plan annex-b-998ade configure xdsl vce-profile 1 modification complete

DLP 1292-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 1293 Delete a Vectoring Control Entity profile


Purpose
This procedure provides the steps to delete an existing Vectoring Control Entity (VCE) profile which is in use by the system. This procedure consists of three parts: 1 2 3 Remove the association between the xDSL vectoring profile and the xDSL lines. Remove the association between the VCE profile and the board (BLV LSM or SLV VP). Delete the VCE profile.

Prerequisites
The following prerequisite must be fulfilled before a VCE profile can be deleted:

The system has been configured such that the VCE is capable of vectoring xDSL lines; see DLP 1291. The xDSL vectoring profiles have been created and associated to xDSL lines; see DLP 1295.

Procedure
Proceed as follows to delete a VCE profile: 1 To remove the association between the VCE profile and the xDSL lines for: a b BLV: go to step 2 SLV: go to step 4

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

DLP 1293 Delete a Vectoring Control Entity profile

Remove the xDSL vectoring profile association from all the xDSL lines which are vectored by the VCE profile to be deleted with the following command:
configure xdsl line <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> (no) vect-profile <Xdsl::LineVectProfile>

3 4

Go to step 5 For SLV, both the association between the VCE profile and the xDSL lines and the association between the VCE profile and the SLV VP board have to be removed: i Remove the xDSL vectoring profile association from all the xDSL lines which are vectored by the VCE profile to be deleted with the following command:
configure xdsl line <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> (no) vect-profile <Xdsl::LineVectProfile>

ii

Remove the VP-LT mapping configuration from all SLV-VP boards to which the VCE profile was assigned with the following command:
configure xdsl vp-board (board-index) vp-link <Xdsl::VectVpLink> (no) lt-expect <Xdsl::LsmBoardOrZero>

Remove the VCE profile association from all the boards (BLV LT and/or SLV VP) to which the VCE profile has been assigned with the following command:
configure xdsl board <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::SlotId> (no) vce-profile <Xdsl::BoardVceProfile>

Delete the VCE profile with the following command:


configure xdsl no vce-profile (index)

STOP. This procedure is complete.

Configuration example for BLV (Config#1): configure xdsl line 1/1/15/[148] no vect-profile configure xdsl board 1/1/15 no vce-profile configure xdsl no vce-profile 1 Configuration example for SLV (Config#1): configure xdsl line 1/1/17/[148] no vect-profile configure xdsl line 1/1/18/[148] no vect-profile configure xdsl vp-board 1/1/16 vp-link [14] no lt-expect configure xdsl board 1/1/16 no vce-profile configure xdsl no vce-profile 2

DLP 1293-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 1294 Configure or modify the mapping between the VP board and the SLV LT boards
Purpose
This procedure is only applicable for System Level Vectoring (SLV). It provides the steps to configure, modify or delete the expected mapping/front cabling between the Vectoring Processing (VP) board and the SLV LT boards. The lines of the SLV LT boards can be vectored when a VCE profile has been assigned to the SLV LT boards; see DLP 1295. An alarm can be reported when the actual mapping is not in line with the expected VP-LT mapping.

Prerequisites
The following prerequisite must be fulfilled before the VP-LT mapping provisioning can be configured:

The System Level Vectoring LT boards must be planned; see DLP 2111 The Vectoring Control Entity profile must be associated with the VP board; see DLP 1291.

Note DLP 1291 includes the planning of an SLV VP board.

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

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

Procedure
Proceed as follows to configure the mapping between the VP board and the SLV LT boards: 1 Configure the mapping between the VP board and the SLV LT boards with the following command:
configure xdsl vp-board (board-index) vp-link <Xdsl::VectVpLink> (no) lt-expect <Xdsl::LsmboardOrZero>

View the actual mapping between the VP board and the SLV LT boards with the following command:
show xdsl vp-board [(board-index) [vp-link <Xdsl::VectVpLink>]

STOP. This procedure is complete.

Configuration example for configuring the mapping (Config#1): configure xdsl vp-board 1/1/16 vp-link 1 lt-expect 1/1/17 configure xdsl vp-board 1/1/16 vp-link 2 lt-expect 1/1/18 info configure xdsl vp-board Configuration example for modifying the mapping (Config#1): configure xdsl vp-board 1/1/16 vp-link 1 no lt-expect configure xdsl vp-board 1/1/16 vp-link 2 lt-expect none configure xdsl vp-board 1/1/16 vp-link 1 lt-expect 1/1/18 configure xdsl vp-board 1/1/16 vp-link 2 lt-expect 1/1/17 info configure xdsl vp-board Configuration example for viewing the actual mapping (Config#1): show xdsl vp-board 1/1/16 vp-link 1 show xdsl vp-board 1/1/16 show xdsl vp-board

DLP 1294-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 1295 Configure a line with an xDSL vectoring profile


Purpose
This procedure provides the steps to configure an xDSL line with the parameters that are supported for the configuration of crosstalk cancellation. In case the operator wants to have crosstalk cancellation, a non-null vectoring profile should be associated to a VDSL2 line. Any vectoring profile assigned to a line running in ADSLx mode will be ignored. The vectoring license counter is incremented when a vectoring profile is assigned to an installed xDSL line, independent of its running mode.

Note xDSL line crosstalk parameters which are applicable to the vectoring control entity, are configured at board level; see DLP 1291.

Vectoring, Crosstalk Cancellation is standardized for VDSL2 in G.993.5 and its management model in G.997.1 Amd1.

Prerequisites
The following prerequisite must be fulfilled before the vectoring profile provisioning can be configured:

In case of Board Level Vectoring: This BLV LSM board must be configured with a vectoring control entity profile; see DLP 1291. Note: DLP 1291 includes the planning of an BLV LT board. The xDSL lines to be vectored must be active; see DLP 1124

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

DLP 1295 Configure a line with an xDSL vectoring profile

In case of System Level Vectoring: The mapping between SLV VP and SLV LSM boards must be configured; see DLP 1294. Note: DLP 1294 includes planning of an SLV VP board with a vectoring control entity profile assigned to the board and planning of SLV LT boards The xDSL lines to be vectored must be active; see DLP 1124

Procedure
Proceed as follows to configure the xDSL vectoring profile provisioning: 1 If required, the maximum number of vectoring profiles and the next free vectoring profile index can be viewed with the following command:
show xdsl profiles

Create a vectoring control entity profile with the following command:


configure xdsl vce-profile (index) name <name>

Configure the vectoring profile parameters with the following command:


configure xdsl vect-profile (index) name <name> (no) fext-cancel-up <Xdsl::VectEnable> (no) fext-cancel-up <Xdsl::VectEnable> (no) dis-gvect-cpe (no) gvecfriend-dn-cpe (no) legacy-cpe (no) band-control-up <Xdsl::VectBandControl> (no) band-control-dn <Xdsl::VectBandControl> (no) vect-leav-thresh <Xdsl::VectLeavThresh>

Activate the vectoring profile with the following command:


configure xdsl vect-profile (index) name <name> active

Note 1 Creation, configuration and activation of a vectoring profile can be done in one command. Note 2 The xDSL vectoring profile must be activated within 15 minutes after it has been created, otherwise it will be deleted.
5 Assign the vectoring profile to a port with the following command:
configure xdsl line <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> (no) vect-profile <Xdsl::LineVectProfile> (no) vect-qln-mode <Xdsl::QLNmode>

STOP. This procedure is complete.

DLP 1295-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 1295 Configure a line with an xDSL vectoring profile

Configuration example for BLV (Config#1): configure xdsl vect-profile 1 name VectProfile1 configure xdsl vect-profile 1 gvecfriend-dn-cpe configure xdsl vect-profile 1 vect-leav-thresh 40 configure xdsl vect-profile 1 active configure xdsl line 1/1/15/[1...48] vect-profile 1 vect-qln-mode with-cancel show system license vectoring Configuration example for SLV (Config#1): configure xdsl vect-profile 2 name VectProfile2 configure xdsl vect-profile 2 gvecfriend-dn-cpe configure xdsl vect-profile 2 vect-leav-thresh 40 configure xdsl vect-profile 2 active configure xdsl vect-profile 3 name VectProfile3 active configure xdsl line 1/1/17/[1...48] vect-profile 2 vect-qln-mode with-cancel configure xdsl line 1/1/18/[1...48] vect-profile 3 vect-qln-mode with-cancel show system license vectoring

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

DLP 1295 Configure a line with an xDSL vectoring profile

DLP 1295-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 1296 Modify an xDSL vectoring profile


Purpose
This procedure provides the steps to modify an existing xDSL vectoring profile.

Prerequisites
The following prerequisite must be fulfilled before an xDSL vectoring profile can be modified:

The xDSL vectoring profile must have been created and activated; see DLP 1295.

Procedure
Proceed as follows to modify an xDSL vectoring profile: 1 Start the modification of an xDSL vectoring profile with the following command:
configure xdsl vect-profile (index) modification start

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

DLP 1296 Modify an xDSL vectoring profile

Modify the parameters of the xDSL vectoring profile with the following command:
configure xdsl vect-profile (index) name <name> (no) fext-cancel-up <Xdsl::VectEnable> (no) fext-cancel-up <Xdsl::VectEnable> (no) dis-gvect-cpe (no) gvecfriend-dn-cpe (no) legacy-cpe (no) band-control-up <Xdsl::VectBandControl> (no) band-control-dn <Xdsl::VectBandControl> (no) vect-leav-thresh <Xdsl::VectLeavThresh>

Note 1 The name of the xDSL vectoring profile can be modified without executing step 1 and step 3. Note 2 Modification of the CPE type can be done through multiple parameters. During the modification phase, these parameters should be entered on the same command line, when the modification of the targeted CPE type spans multiple parameters.
3 Use one of the following commands to complete the modification of the xDSL vectoring profile: a When the modifications must be kept:
configure xdsl vect-profile (index) modification complete

When the modifications must be cancelled:


configure xdsl vect-profile (index) modification cancel

STOP. This procedure is complete.

Configuration example (Config#1): configure xdsl vect-profile 1 modification start configure xdsl vect-profile 1 no gvecfriend-dn-cpe no legacy-cpe configure xdsl vect-profile 1 modification complete

DLP 1296-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 1297 Delete an xDSL vectoring profile


Purpose
This procedure provides the steps to delete an existing xDSL vectoring profile which is in use by the system. This procedure consists of two parts: 1 2 Remove the association between the xDSL vectoring profile and the xDSL lines. Delete the xDSL vectoring profile.

Prerequisites
The following prerequisite must be fulfilled before an xDSL vectoring profile can be deleted:

The xDSL vectoring profile must have been created and activated; see DLP 1295.

Procedure
Proceed as follows to delete an xDSL vectoring profile: 1 Remove the xDSL vectoring profile association from all the xDSL lines to which the xDSL vectoring profile was assigned with the following command:
configure xdsl line <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> (no) vect-profile <Xdsl::LineVectProfile>

Delete the xDSL vectoring profile with the following command:


configure xdsl no vect-profile (index)

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

DLP 1297 Delete an xDSL vectoring profile

View the vectoring license counter with the following command:


show system license (feature)

STOP. This procedure is complete.

Configuration example for BLV (Config#1): configure xdsl line 1/1/15/[148] no vect-profile configure xdsl no vect-profile 1 show system license vectoring Configuration example for SLV (Config#1): configure xdsl line 1/1/17/[148] no vect-profile configure xdsl line 1/1/18/[148] no vect-profile configure xdsl no vect-profile 2 configure xdsl no vect-profile 3 show system license vectoring

DLP 1297-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 1298 Monitor xDSL vectoring lines


General
Monitoring operational xDSL vectoring lines requires a vectoring-capable CPE to be connected to the peer side of the line. This procedure is applicable for both Board Level Vectoring and System Level Vectoring. In the latter case, the SLV VP board holds the vectoring specific data. Therefore it also requires operational an SLV VP board and SLV LT boards which are properly cabled and for which the connection is operational.

Purpose
This section describes the steps to return operational information about the vectoring xDSL Lines.

Procedure
Proceed as follows to monitor xDSL vectoring lines: 1 View the disturber list information for the specified victim line with the following command:
show xdsl vect-disturbers (victime-line) [max-reported-dist]

Note The operator can restrict the maximum number of reported disturber lines by specifying the value for the parameter max-reported-dist.

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

DLP 1298 Monitor xDSL vectoring lines

View the carrier data for a specified victim line and disturber with the following commands:
show xdsl vect-carrier-data near-end (line) disturber <Itf::XdslLine> show xdsl vect-carrier-data far-end (line) disturber <Itf::XdslLine>

During the physical line startup with CPEs connected, it can happen that the system returns an activation failure due to communication problems. The cause of the problem can be found using the following commands: i View the xDSL line activation failure error code with the following command:
show xdsl failure-status far-end (if-index)

ii

View the description of that error code with the following command:
show xdsl failure-status far-end (if-index) detail

View the status of the disorderly leaving event vect-dle with the following command:
show xdsl failure-status near-end (if-index)

View the xDSL vectored line or board failure status with the following commands:
show xdsl failure-status vect-line-near-end (if-index) show xdsl failure-status vect-board (if-index)

View the actual operating information which can differ from the configured mode with the following commands: i The parameter vect-cpe-type displays the actual operating mode of the CPE connected to the line:
show xdsl operational-data near-end line (if-index)

ii

The parameters vect-qln-mode-up and vect-qln-mode-down display the actual reported qln:
show xdsl carrier-data near-end (if-index) show xdsl carrier-data far-end (if-index)

STOP. This procedure is complete.

DLP 1298-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 2101 Create operator profiles and instances


Purpose
Before an operator instance can be created, an operator profile must be created An operator profile determines most of the properties of the operator. It is used to limit the commands a group of operators can execute to those for which they have the necessary skills and for which they are responsible. This document describes the procedure to configure and create an operator profile and to create an operator instance.

Operator Profile Rules


The following rules apply to an operator profile:

The permissions of an operator profile cannot be changed as long as one operator belongs to the profile. The operator profile is assigned at the moment the operator is created. It cannot be changed afterwards. If an operator profile needs to be changed, then the operators with this operator profile must first be deleted. Only then can the properties of the profile be changed.

Password Rules
The following rules apply to a plain text password:

the password must consist of a minimum of 6 and a maximum of 20 characters the password must contain a minimum of 1 non-alphanumeric character a new password must be different from the last three passwords

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

DLP 2101 Create operator profiles and instances

Never specify a new password in an encrypted format, because you can enter any hexadecimal string that is not necessarily linked to a password. It is almost impossible to calculate a password from an encrypted string. This method of specifying passwords is only intended to restore an existing configuration. An operator will be requested to enter a new password after logging in for the first time.

Procedure
Proceed as follows to create an operator instance: 1 Create and configure the operator profile to which the operator will belong with the following command:
configure system security profile (name) (no) prompt <Sec::Prompt> (no) password-timeout <Sec::PasswordTimeout> (no) terminal-timeout <Sec::InactivityTimeout> (no) slot-numbering <Sec::SlotDesc> (no) description <Sec::ProfileDesc> (no) aaa <Sec::Aaa> (no) atm <Sec::Atm> (no) alarm <Sec::Alarm> (no) dhcp <Sec::Dhcp> (no) equipment <Sec::Equipment> (no) igmp <Sec::Igmp> (no) ip <Sec::Ip> (no) pppoe <Sec::Pppoe> (no) qos <Sec::Qos> (no) software-mngt <Sec::Sw> (no) transport <Sec::Transport> (no) vlan <Sec::Vlan> (no) xdsl <Sec::Xdsl> (no) security <Sec::Security> ...

Note 1 Only the main parameters are shown, other parameters can also be modified. For more information, see the CLI Command Guide for FD 24Gbps NT. Note 2 No capitals may be used in the profile name.

DLP 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

DLP 2101 Create operator profiles and instances

Create an operator instance with the following command:


configure system security operator (name) profile <Sec::ProfileName> password prompt | plain:<Sec::PlainPassword> | encrypted:<Sec::EncryptedPassword> (no) prompt <Sec::Prompt> (no) description <Sec::OperatorDesc> (no) more

Note No capitals and blanks may be used in the operator name/profile name.

STOP. This procedure is complete.

Configuration example (Config#1): configure system security profile profile1 no prompt password-timeout 10 terminal-timeout 30 description Profile1 aaa read atm read alarm write no dhcp equipment write igmp write ip write pppoe write qos write no software-mngt transport write vlan write xdsl write security write configure system security operator jimphelpsmi profile admin password plain:isam123! prompt %s:%n%d%c description Operator for MI

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

DLP 2101 Create operator profiles and instances

DLP 2101-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 2103 Configure system parameters


Purpose
This document describes the procedure to configure system parameters on the system and on the SHub, such as:

System and SHub ID SNTP date and time system clock management error log handling

Note The following applies for the commands shown below:

If names with blanks are used, these names have to be enclosed in quotations ().

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

DLP 2103 Configure system parameters

Procedure
Proceed as follows to configure the system parameters: 1 Configure the system ID parameters with the following command:
configure system id <Sys::systemId> name <Transport::sysName> location <Transport::sysLocation> (no) access-oper-id <Sys::accessOperatorId> contact-person <Transport::sysContact> (no) en-snmp-auth-trap (no) ether-shape-rate <Sys::etherShapeRate> mgnt-vlan-id <Vlan::VlanId> system-mac <Sys::systemMac> (no) port-num-in-proto <Sys::PortNumberInprotocol>

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).
2 Optionally, configure the SHub ID with the following command:
configure system shub entry id contact <PrintableString> location <PrintableString>

If necessary, configure the system loop ID syntax with the following command:
configure system loop-id-syntax (no) atm-based-dsl <Sys::AtmBasedDsl> (no) efm-based-dsl <Sys::EfmBasedDsl>

Note For the loop ID syntax:

The parameter atm-based-dsl defines the syntax of the loop ID for ATM based DSL lines. The default value is Access_Node_ID atm Rack/Frame/Slot/Port:VPI.VCI The parameter efm-based-dsl defines the syntax of the loop ID for EFM based DSL lines. The default value is Access_Node_ID efm Rack/Frame/Slot/Port

To configure the system time, do one of the following: a Set the system time with the following command:
admin sntp system-time <Sys::Time>

DLP 2103-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 2103 Configure system parameters

Configure SNTP on the NE with the following command:


configure system sntp server-ip-addr <Ip::V4Address> (no) server-port <Sys::portNumber> (no) polling-rate <Sys::pollingRate> enable (no) timezone-offset <Sys::timeZoneOffset>

Configure an SNTP Server in the server table with optional priority with the following command:
configure system sntp ip-address <Ip::V4Address> configure system sntp server-table (no) ip-address <Ip::V4Address> (no) port <udp port> priority <Sys::priority>

Note Up to 3 servers can be configured with priority values ranging from 1 to 3 with 1 being the highest priority. The server configured with the command configure system sntp server-ip-addr is mapped to the entry with priority 1 in the server-table and any changes done to one configuration is internally updated to the other.
5 Configure the system clock source and the clock source priority scheme with the following command:
configure system clock-mgmt (no) priority-scheme <Sys::SysClkSrcPriorityScheme> (no) ext-source <Sys::SysClkExtSource>

Note The last parameter is not available on 7330 ISAM FTTN systems.

If required, configure ICMP-related parameters with the following command:


configure system shub icmp (no) time-stamp-reply <Sys::TsReply>

Note Currently this command is used to enable or disable the ICMP timestamp reply (default is enabled).

Configure the error log handling with the following command:


configure error (no) log-full-action <Error::errorLogFullAction>

View information about the SNTP and its related parameters with the following command:
show sntp

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

DLP 2103 Configure system parameters

View information about the SNTP server table with the following command:
show sntp server-table

10

View information about the NTP protocol in the system with the following command:
show system ntp [{servers|server <server-address>}] [detail]

11

STOP. This procedure is complete.

Configuration example (Config#1): configure system id SystemID02 name Test_Asam location Magabir contact-person Ewan Tendunnit (Phone ext 345) mgnt-vlan-id 4093 configure system shub entry id contact Hugh Shuckman (Phone ext 003) location Magabir configure system loop-id-syntax atm-based-dsl Access_Node_ID atm Rack-Frame-Slot-Port:VPI.VCI configure system loop-id-syntax efm-based-dsl Access_Node_ID eth Rack-Frame-Slot-Port:0.0 admin sntp system-time 2007-01-01:23:55:00 configure system sntp server-ip-addr 10.176.5.5 enable timezone-offset 6 configure system sntp server-table ip-address 172.21.214.235 port 124 priority 2 configure system clock-mgmt priority-scheme local configure error log-full-action wrap show sntp show sntp server-table

DLP 2103-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 2105 Configure link aggregation usage


Purpose
Link aggregation or trunking is a method of combining physical network links into a single logical link for increased bandwidth. The following link aggregation combinations can be used in the NE:

Network links: The number of aggregation links depends on the NT board type For NANT-A: a link aggregation group (LAG) can exist of maximum 8 component links. Subtending links: For an FE type link or a GE type link, an LAG can exist of maximum 7 or 8 (for NANT-A used in combination with NCNC-E) component links

Note 1 Link aggregation cannot be used for user links. Note 2 Network ports associated to a LAG group configured for either active or passive LACP will still send upstream traffic if they are connected to an upstream interface which is operationally up, but is not configured for link aggregation, or is configured for link aggregation without LACP. This only occurs when all ISAM ports in the LAG group are connected to ports which are not configured properly in order to successfully aggregate with the ISAM. To avoid this situation, ensure that the network ports in the LAG group on the ISAM are connected to the proper interfaces on the upstream device. If the minimum number of links is met for the LAG group according to the ISAM, link aggregation will continue to function normally.
This document describes the procedure to configure the link aggregation usage.

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

DLP 2105 Configure link aggregation usage

General
This node allows specification of Link Aggregation Group parameters. A Link Aggregation Group is identified by means of the primary link, also referred to as aggregator-port. The primary link for an Aggregation Group is the link with the lowest SHub logical port number within the group, provided the operational state of the link is UP.

Note This lowest SHub logical port number is not necessarily mapped to the lowest faceplate number of the link. The faceplate number of the link is the link number used in the CLI/TL1 commands.
The configuration should be performed for the primary link. The settings configured for the primary link of the Aggregation Group apply to each and every link that is a member of the Link Aggregation Group.

Note Even if LACP is disabled at system level, configuration of links with the same actor-key are only allowed on the primary port.

The link which is denoted as primary link may change during the lifetime of the aggregation group. To cope with this phenomenon, the operator is advised to repeat the configurations described in this procedure for each link of the Aggregation Group. Care must be taken to configure identical settings for all links within the Aggregation Group.

Prerequisite
The following prerequisite must be fullfilled before link aggregation can be configured: The port-type of the network port must be network or subtending. This can be verified with the command
show interface shub port

and, if necessary, changed with the command


configure interface shub port (network-port) port-type <Sys::Type>

Procedure
Proceed as follows to configure link aggregation usage: 1 Specify the Link Aggregation Group parameters with the following command:
configure la aggregator-port (network-port) name <Shub::AggName> (no) link-up-down-trap (no) actor-sys-prio <Shub::LaPortActorSysPriority> selection-policy <Shub::AggSelectPolicy> actor-key <Shub::LacpKey>

DLP 2105-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 2105 Configure link aggregation usage

(no) actor-port-prio <Shub::LaPortActorPortPriority> (no) active-lacp (no) short-timeout (no) aggregatable lacp-mode <Shub::LacpMode>

Use the following command to configure Link Aggregation on the SHub. It merely allows to enable or disable the Link Aggregation feature:
configure la no disable-lacp

Note This command is only necessary if the Link Aggregation system was shut down manually. By default, Link Aggregation is enabled.

View information for a Link Aggregation Group configured on the Service Hub with the following command:
show la aggregator-info (port)

View information for a member of a Link Aggregation Group configured on the Service Hub with the following command:
show la network-port-info (port)

STOP. This procedure is complete.

Configuration example for manual link aggregation (no LACP) (Config#1): configure interface shub port [4,6] port-type network admin-status up configure la aggregator-port [4,6] name lag1 selection-policy mac-src-dst actor-key 1234 aggregatable lacp-mode manual configure la no disable-lacp show la aggregator-info [4,6] show la network-port-info [4,6] configure interface shub port [4,6] port-type unused configure la disable-lacp Configuration example for link aggregation using active LACP

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

DLP 2105 Configure link aggregation usage

(Config#1): configure interface shub port [4,6] port-type network admin-status up configure la aggregator-port [4,6] name lag1 selection-policy mac-src-dst actor-key 1234 active-lacp aggregatable lacp-mode enable-lacp configure la no disable-lacp show la aggregator-info [4,6] show la network-port-info [4,6] configure interface shub port [4,6] port-type unused configure la disable-lacp Configuration example for link aggregation using passive LACP (Config#1): configure interface shub port [4,6] port-type network admin-status up configure la aggregator-port [4,6] name lag1 selection-policy mac-src-dst actor-key 1234 no active-lacp aggregatable lacp-mode enable-lacp configure la no disable-lacp show la aggregator-info [4,6] show la network-port-info [4,6] configure la disable-lacp

DLP 2105-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 2107 Manage OSPF


Purpose
This procedure provides the steps for managing the Open Shortest Path First (OSPF) Routing Protocol on the NE.

General
An OSPF network is divided into areas. These are logical groupings of routers whose information may be summarized towards the rest of the network. Several special area types are defined:

Backbone area: The backbone area (also known as area zero) forms the core of an OSPF network. All other areas are connected to it, and inter-area routing happens via a router connected to the backbone area. It is the logical and physical structure for the Autonomous System (AS) and is attached to multiple areas. The backbone area is responsible for distributing routing information between non-backbone areas. The backbone must be contiguous, but it does not need to be physically contiguous; backbone connectivity can be established and maintained through the configuration of virtual links.

Note All OSPF areas must connect to the backbone area.

Stub area: A stub area is an area which does not receive external routes. External routes are defined as routes which were distributed in OSPF from another routing protocol. Therefore, stub areas typically need to rely on a default route to send traffic to routes outside the present domain. This implies that AS external routes are not fed into stub areas

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

DLP 2107 Manage OSPF

Not-so-stubby area: A not-so-stubby area (NSSA) is a type of stub area that can import AS external routes and send them to the backbone, but cannot receive AS external routes from the backbone or other areas.

Note The maximum number of routes that can be populated in the OSPF routing table will be always less than the actual capacity.
Background: The OSPF routing table is calculated from the link state database, which contains all the LSAs advertised by the neighbouring routers (see RFC 2328 Secion:16 for route calculation procedure). The number of routes depends on the topology and the number of external/summary LSAs in the LSDB. The maximum capacity of LSDB and maximum capacity of routing table are equal. If either of them over-flows, an instance re-start of OSPF is forced. The LSDB will always contain more entries than the number of routes that can be calculated from them. This depends on the network topology, number of areas etc. If LSAs are advertised from peers to populate the routing table to full capacity, the LSDB will overflow even before the routing table becomes full resulting in an instance reset.

Procedure
Proceed as follows to configure OSPF management: 1 If not done so already, configure a fast path VRF the following command:
configure ip shub vrf <vrf-id> name <vrf-name> fast-path-mode:dis-user-user-com

Configure the OSPF parameters and attributes per instance with the following command:
configure ospf enable router-id <Ip::V4Address> (no) as-border-router (no) enable-opaque-lsa (no) overflow-state-it <Ospf::OvrflowIntrvl> (no) dis-rfc1583-comp (no) abr-type <Ospf::AbrType> (no) asbr-rtr-trans (no) spf-hold-time <Ospf::SpfHoldInterval> (no) spf-delay-time <Ospf::DelayTime> (no) max-num-ext-lsa <Ospf::MaxNbrLsa>

DLP 2107-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 2107 Manage OSPF

Configure the OSPF backbone area parameters: i Configure the OSPF backbone area ID:
configure ospf area (area-id)

ii

Configure the OSPF interface parameters with the following command:


configure ospf area (area-id) interface (ip-addr) (no) disable (no) router-priority <Ospf::Priority> (no) passive (no) itf-type <Ospf::ITFType> (no) authentication <Ospf::AuthType>

iii

Configure the OSPF interface timers with the following command:


configure ospf area (area-id) interface (ip-addr) timers (no) transit-delay <Ospf::TransDelay> (no) retransmit-itvl <Ospf::RetransIntvl> (no) hello-interval <Ospf::HelloIntvl> (no) dead-interval <Ospf::DeadIntvl> (no) poll-interval <Ospf::PollIntvl>

iv

When MD5 is selected as authentication mode for an OSPF interface, use the following command to configure the MD5 key:
configure ospf area (area-id) interface (ip-addr) md5-key (index) key prompt | plain: <Ospf::MD5key> | encrypted: <Ospf::MD5encryptedKey> (no) accept-starts <Ospf::MD5startDelay> (no) generate-starts <Ospf::MD5startDelay>

Confirm the MD5 authentication with the following command:


configure ospf area (area-id) interface (ip-addr) authentication md5

Note If MD5 authentication is to be implemented, first the MD5 key must be set using the command in step iv, then the command from step v must be implemented. Both commands must be implemented for MD5 authentication.
vi Configure the metric for an OSPF interface with the following command:
configure ospf area (area-id) interface (ip-addr) (no) metric value <Ospf::Metric>

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

DLP 2107 Manage OSPF

vii

Inter-area route summarization is done on ABRs and it applies to routes from within the AS. It does not apply to external routes injected into OSPF via redistribution. In order to take advantage of summarization, network numbers in areas should be assigned in a contiguous way to be able to lump these addresses into one range. Configure an OSPF aggregate with the following command:
configure ospf area (area-id) summary-aggregate (dest-ip) (no) omit-advertise

viii External route summarization is specific to external routes that are injected into OSPF via redistribution. Also, make sure that external ranges that are being summarized are contiguous. Summarization overlapping ranges from two different routers could cause packets to be sent to the wrong destination. Configure an OSPF aggregate from external autonomous system with the following command:
configure ospf area (area-id) redist-aggregate (dest-ip) (no) advertise <Ospf::ExtAggregateEffect>

Configure the OSPF stub area parameters: i Configure the OSPF stub area ID with the following command:
configure ospf area (area-id)]

ii

Configure the OSPF stub area with the following command:


configure ospf area (area-id) stub (no) metric-type <Ospf::MetricType> (no) metric <Ospf::StubMetric> (no) summary]

iii

Configure the OSPF stub area interface with the following command:
configure ospf area (area-id) interface (ip-addr) (no) disable (no) router-priority <Ospf::Priority> (no) passive (no) itf-type <Ospf::ITFType> (no) authentication <Ospf::AuthType>

iv

Configure the OSPF stub area interface timers with the following command:
configure ospf area (area-id) interface (ip-addr) timers (no) transit-delay <Ospf::TransDelay> (no) retransmit-itvl <Ospf::RetransIntvl> (no) hello-interval <Ospf::HelloIntvl> (no) dead-interval <Ospf::DeadIntvl> (no) poll-interval <Ospf::PollIntvl>

DLP 2107-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 2107 Manage OSPF

When MD5 is selected as authentication mode for an OSPF stub area interface, use the following command to configure the MD5 key:
configure ospf area (area-id) interface (ip-addr) md5-key (index) key prompt | plain: <Ospf::MD5key> | encrypted: <Ospf::MD5encryptedKey> (no) accept-starts <Ospf::MD5startDelay> (no) generate-starts <Ospf::MD5startDelay>

vi

Confirm the MD5 authentication with the following command:


configure ospf area (area-id) interface (ip-addr) authentication md5

Note If MD5 authentication is to be implemented, first the MD5 key must be set using the command in step iv, then the command from step v must be implemented.
Both commands must be implemented for MD5 authentication. vii Configure the metric for an OSPF stub area interface with the following command:
configure ospf stub-area (area-id) interface (ip-addr) (no) metric value <Ospf::Metric>

viii Configure an OSPF stub aggregate with the following command:


configure ospf area (area-id) summary-aggregate (dest-ip) (no) omit-advertise

Configure the OSPF NSSA area parameters with the following command: i Configure the OSPF NSSA area ID with the following command:
configure ospf area (area-id)]

ii

Configure the OSPF NSSA area with the following command:


configure ospf area (area-id) nssa (no) summary (no) translation <Ospf::Trnsltn> (no) trans-itvl <Ospf::TrnltnIntvl> (no) metric-type <Ospf::NSSAMetricType>]

iii

Configure the OSPF NSSA area interface with the following command:
configure ospf area (area-id) interface (ip-addr) (no) disable (no) router-priority <Ospf::Priority> (no) passive (no) itf-type <Ospf::ITFType> (no) authentication <Ospf::AuthType>

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

DLP 2107 Manage OSPF

iv

Configure the OSPF NSSA area interface timers with the following command:
configure ospf area (area-id) interface (ip-addr) timers (no) transit-delay <Ospf::TransDelay> (no) retransmit-itvl <Ospf::RetransIntvl> (no) hello-interval <Ospf::HelloIntvl> (no) dead-interval <Ospf::DeadIntvl> (no) poll-interval <Ospf::PollIntvl>

When MD5 is selected as authentication mode for an OSPF NSSA area interface, use the following command to configure the MD5 key:
configure ospf area (area-id) interface (ip-addr) md5-key (index) key prompt | plain: <Ospf::MD5key> | encrypted: <Ospf::MD5encryptedKey> (no) accept-starts <Ospf::MD5startDelay> (no) generate-starts <Ospf::MD5startDelay>

vi

Confirm the MD5 authentication with the following command:


configure ospf area (area-id) interface (ip-addr) authentication md5

Note If MD5 authentication is to be implemented, first the MD5 key must be set using the command in step v, then the command from step vi must be implemented.
Both commands must be implemented for MD5 authentication. vii Configure the metric for an OSPF NSSA area interface with the following command:
configure ospf area (area-id) interface (ip-addr) (no) metric value <Ospf::Metric>

viii Configure an OSPF NSSA aggregate with the following command:


configure ospf area (area-id) summary-aggregate (dest-ip) lsa-type <Ospf::LSAType> (no) omit-advertise

ix

Configure an OSPF NSSA aggregate from external autonomous systems with the following command:
configure ospf redist-aggregate (dest-ip) (no) advertise <Ospf::ExtAggregateEffect>

Configure the redistribution of the OSPF with the following command:


configure ospf redistribution (no) enable (no) local (no) static (no) rip

DLP 2107-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 2107 Manage OSPF

Configure the redistribution of the OSPF route parameters with the following command:
configure ospf redistribution route-destination (dest-ip) (no) metric-type <Ospf::RouteMetricType> (no) metric <Ospf::RouteMetric>

Display the different OSPF values with the following commands:


show ospf area detail show ospf link-state-adv link-type detail show ospf link-state-adv asbr-external detail show ospf interface detail show ospf neighbour detail show ospf routing-table detail show ospf statistics detail show ospf status detail

STOP. This procedure is complete.

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

DLP 2107 Manage OSPF

Configuration example (Config#1): configure interface shub port [4...5] port-type network configure ip shub vrf 15 name routervrf15 fast-path-mode:dis-user-user-com configure vlan shub id 70 mode layer2-term-nwport configure vlan shub id 70 egress-port network:4 configure interface shub vlan-id 70 configure interface shub ip 70 vrf-id 15 configure interface shub ip 70 ip-addr 192.168.70.39/24 configure interface shub vlan-id 70 admin-status auto-up configure vlan shub id 80 mode layer2-term-nwport configure vlan shub id 80 egress-port network:5 configure interface shub vlan-id 80 configure interface shub ip 80 vrf-id 15 configure interface shub ip 80 ip-addr 192.168.80.39/24 configure interface shub vlan-id 80 admin-status auto-up configure bridge shub port 4 pvid 70 configure bridge shub port 5 pvid 80 configure ospf enable configure ospf router-id 192.168.70.39 as-border-router configure ospf area 0.0.0.0 configure ospf area 0.0.0.0 interface 192.168.70.39 configure ospf area 0.0.0.0 interface 192.168.70.39 md5-key 2 key plain:ALCATEL configure ospf area 0.0.0.0 interface 192.168.70.39 authentication md5 configure ospf area 0.0.0.0 interface 192.168.70.39 metric value 10 configure ospf area 0.0.0.0 interface 192.168.80.39 configure ospf area 0.0.0.0 interface 192.168.80.39 metric value 10 configure ospf redistribution enable configure ospf redistribution static configure ospf redistribution local DLP 2107-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 2107 Manage OSPF

configure ospf stub-area 1.1.1.1 metric 1 metric-type ospf summary configure ospf nssa-area 2.2.2.2 configure ospf as-border-router configure ospf abr-type standard show ospf area detail show ospf link-state-adv link-type detail show ospf link-state-adv asbr-external detail show ospf interface detail show ospf neighbour detail show ospf routing-table detail show ospf statistics detail show ospf status detail

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

DLP 2107 Manage OSPF

DLP 2107-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 2108 Configure RIP


Purpose
This procedure provides the steps to configure Routing Information Protocol (RIP) management on the NE.

Limitations
The following limitations apply:

RIP support is only offered for IPoA interfaces. Only plain RIP messages will be handled, the triggered RIP protocol is not supported. RIP message propagation is enabled/disabled on the user gateway interface of the SHub, not per user PVC. One or more fast path VRFs must have been created before RIP management can be configured.

Procedure
Proceed as follows to configure RIP management: 1 If not done so already, configure a fast path VRF the following command:
configure ip shub vrf <vrf-id> name <vrf-name> fast-path-mode:dis-user-user-com

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

DLP 2108 Configure RIP

Configure RIP distribution with the following command:


configure rip redistribution (no) enable (no) default-metric <Rip::RouteMetric> (no) local (no) static (no) ospf

Note 1 RIP redistribution enables or disables RIP to participate in Route Redistribution.

If set to enabled then RIP will start advertising the routes learned by other protocols. If set to disabled then RIP will stop the redistribution of routes but will continue to send updates to the VRF routing table.

Note 2 The protocols from which the routes have to be imported to RIP:

Local: the routes have to be imported from the local interface. Static: the routes have to be imported from the static route. OSPF: the routes have to be imported from OSPF.

Note 3 RIP redistribution filters apply to all interfaces


Configure RIP interface parameters with the following command:
configure rip interface (ip-addr) (no) authentication <Rip::AuthType> default-metric <Rip::DefMetric> (no) send <Rip::ConfSend> (no) receive <Rip::ConfRcv> (no) split-horizon <Rip::SpltHorizon> (no) egr-routemap-act <Rip::EgrRouteMapAction> (no) igr-routemap-act <Rip::IngrRouteMapAction>

Configure the RIP interface timers with the following command:


configure rip interface (ip-addr) timers (no) update-timer <Rip::UpdateTmr> (no) route-age-out <Rip::RouteAgeTmr> (no) junk-collection <Rip::GrbTmr>

DLP 2108-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 2108 Configure RIP

If the MD5 authentication method is selected for a RIP interface (see step 3), then the MD5 key can be configured with the following command: i Configure the MD5 key with the following command:
configure rip interface (ip-addr) md5-key (index) key <Rip::AuthTypeMD5> starts <Rip::MD5startDelay> expires <Rip::MD5expiryDelay>

ii

Confirm the MD5 configuration with the following command:


configure rip interface (ip-addr) authentication md5

Note 1 RIP must be configured on the interface for which the MD5 key has to be configured. Note 2 If MD5 authentication is to be implemented, first the MD5 key must be set using the command in step i, then the command from step ii must be implemented.
Both commands must be implemented for MD5 authentication. 6 An MD5 key for a RIP interface can be managed with the following command:
admin rip interface (ip-addr) md5-key <Rip::Md5KeyIndex> expires <Rip::MD5expiryDelay>

Configure RIP interface route map parameters (that is, define an ingress or egress route map for routes redistributed from or to RIP over an interface) with the following command:
configure rip interface (ip-addr) route-map (map-index) direction <Rip::NewRouteMapDirection> ip-addr <Ip::AddressAndIpMaskFull> (no) action <Rip::NewRouteMapAction> (no) prefix-match <Rip::NewRouteMapMatch>

Add or delete a route aggregation with the following command:


configure rip (no) aggregation (ip-addr)

View the information for RIP with the following command:


show rip statistics show rip peer show rip routing-table show rip global

10

STOP. This procedure is complete.

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

DLP 2108 Configure RIP

Configuration example (Config#1): configure ip shub vrf 15 name routervrf15 fast-path-mode:dis-user-user-com configure vlan shub id 90 mode layer2-terminated configure interface shub vlan-id 90 configure interface shub ip 90 configure interface shub ip 90 vrf-id 15 configure interface shub ip 90 ip-addr 192.168.90.39/24 configure rip redistribution enable default-metric 2 configure rip interface 192.168.80.39 default-metric 1 receive rip2 send rip2 split-horizon poison-reverse configure rip interface 192.168.80.39 timers update-timer 30 junk-collection 120 configure rip interface 192.168.80.39 md5-key 4 key plain:AlcatelTest expires never starts now configure rip interface 192.168.80.39 authentication md5 configure rip interface 192.168.80.39 route-map 15 direction egress ip-addr 192.168.145.1/32 configure rip redistribution enable static ospf show rip statistics show rip peer show rip routing-table show rip global

DLP 2108-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 2109 Configure SNMP and trap management


General

SNMP
There are three versions of SNMP available, usually referred as SNMPv1, SNMPv2 and SNMPv3. The security functions provided by the SNMP protocols are categorized into the following two models:

Community-based Security Model, whose data is protected by nothing more than a password, referred to as the community name. Community-based security allows the SNMP agent to authenticate a request based on the community name used and the IP address from which the request originated. This level of security is provided by SNMPv1 and SNMPv2. User-based Security Model (USM), which provides different levels of security, based on the user accessing the managed information. To support this security level, the SNMPv3 framework defines several security functions, such as USM for authentication and privacy and View-based Access Control Model (VACM) which provides the ability to limit access to different MIB objects on a per-user basis and the use of authentication and data encryption for privacy.

Trap management
An SNMP manager will receive traps when an event occurs in the system. The manager can be easily flooded by events in the case where something happens with the system. It can be specified in which traps the manager is interested (trap filtering) and how the traps must be spread in time (trap shaping).

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

DLP 2109 Configure SNMP and trap management

Traps that can not be delivered will be dropped:

cold-start link-down link-up auth-failure change-occurred init-started license-key-change-occurred

You can also set the minimum priority to be reported when a trap occurs. The priority can be urgent, high, medium, or low.

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

It is NOT advised to use unsecure management channels such as SNMPv1 or SNMPv2. If SNMPv1/2 is used anyway, it is advised not to use community string = public It is advised to use secure management channels such as SNMPv3.

Procedure
Proceed as follows to configure SNMP and trap management: 1 Configure a view of a subtree with the following command:
configure system security snmp view (notify-view) subtree <Snmp::ViewSubtree> type <Snmp::FilterType>

Configure the SNMP community name with the following command:


configure system security snmp community (name) host-address <Ip::V4Address>/<Ip::PrefixLengthFull> (no) context <Transport::Context> (no) privilege <Snmp::CommunityPrivilege> (no) read-view <Snmp::ViewName> (no) write-view <Snmp::ViewName> (no) notify-view <Snmp::ViewName>

Do one of the following: a b If SNMPv1 or SNMPv2 is used, continue with step 7. If SNMPv3 is used, continue with step 4.

DLP 2109-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 2109 Configure SNMP and trap management

Configure an SNMPv3 group with the following command:


configure system security snmp group (name) security-level <Snmp::SecurityLevel> context single:nt | single:shub | single:epon | single:xvps1 | single:xvps2 | single:xvps3 | single:xvps4 | single:xvps5 | single:xvps6 | single:xvps7 | single:xvps8 | all (no) read-view <Snmp::ViewName> (no) write-view <Snmp::ViewName> (no) notify-view <Snmp::ViewName>

Configure an SNMPv3 user with the following command:


configure system security snmp user (name) (no) authentication none | [md5|sha1]:prompt | [md5|sha1]:plain:<Sec::PlainPassword> | [md5|sha1]:encrypted:<Snmp::AuthEncryptedKey> (no) privacy none | des:prompt | des:plain:<Sec::PlainPassword> | des : encrypted : <Snmp::PrivacyEncryptedKey> (no) public <Snmp::Identifier>

Map an SNMPv3 user to an SNMPv3 group with the following command:


configure system security snmp map-user-group (name) group-name <Snmp::GroupName>

Configure an SNMP notification profile with the following command:


configure system security snmp notify-profile (name) snmp-version v1 : <Snmp::CommunityString> | v2 : <Snmp::CommunityString> | v3 : <Snmp::SecurityName>: none | authentication | privacy-and-auth

Configure a filter for a notification profile with the following command:


configure system security snmp notify-profile (name) filter notify-view <Snmp::ViewName>

Configure an SNMP element manager with the following command:


configure system security snmp manager (name) destination <Snmp::IpAddress>:<Snmp::AddressPort> notify-profile <Snmp::NotifyProfile> (no) nt (no) shub (no) epon (no) xvps1 (no) xvps2 (no) xvps3 (no) xvps4 (no) xvps5 (no) xvps6 (no) xvps7 (no) xvps8

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

DLP 2109 Configure SNMP and trap management

10

Configure the SNMP trap manager with the following command:


configure trap manager <Ip::V4Address>:<Trap::Port> (no) priority <Trap::Priority> (no) cold-start-trap (no) link-down-trap (no) link-up-trap (no) auth-fail-trap (no) change-trap (no) init-started-trap (no) lic-key-chg-occr (no) topology-chg (no) dhcp-sess-pre (no) alarm-chg-trap (no) phys-line-trap (no) eqpt-change-trap (no) success-set-trap (no) other-alarm-trap (no) warning-trap (no) minor-trap (no) major-trap (no) critical-trap (no) redundancy-trap (no) eqpt-prot-trap (no) craft-login-trap (no) restart-trap (no) ntr-trap (no) max-per-window <Trap::WindowCount> (no) window-size <Trap::WindowSize> (no) max-queue-size <Trap::QueueSize> (no) min-interval <Trap::Interval> (no) min-severity <Alarm::alarmSeverity>]

11

Configure the trap definition table with the following command:


configure trap definition (name) priority <Trap::Priority>

12

If necessary, reset the trap table with the following command:


admin trap manager <Ip::V4Address> : <Trap::Port> reset-trap-buffer

13

STOP. This procedure is complete.

Configuration examples:

DLP 2109-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 2109 Configure SNMP and trap management

Configuration example for SNMPv1 or SNMPv2 (Config#1): configure system security snmp view view1 subtree * type include configure system security snmp view view1 subtree 1.3.6.1.4.1.637.61.1.48.* type exclude configure system security snmp community public host-address 10.176.0.0/15 context nt privilege read-write configure system security snmp community NETMAN host-address 10.176.0.0/15 context shub configure system security snmp community comm1 host-address 10.176.0.0/15 context nt read-view protected write-view view1 notify-view everything configure system security snmp notify-view nview1 subtree * type include configure system security snmp notify-view nview1 subtree bondingMIB.* type exclude configure system security snmp notify-profile nprof1 snmp-version v1:trapcomm configure system security snmp notify-profile nprof1 filter notify-view nview1 configure system security snmp manager Manager01 destination 10.176.25.25:6666 notify-profile nprof1 nt shub configure trap manager 10.176.25.25:6666 cold-start-trap auth-fail-trap eqpt-change-trap warning-trap minor-trap major-trap critical-trap min-severity warning configure trap definition auth-failure priority high admin trap manager 10.176.25.25:6666 reset-trap-buffer

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

DLP 2109 Configure SNMP and trap management

Configuration example for SNMPv3 (Config#1): configure system security snmp view view2 subtree * type include configure system security snmp view view2 subtree bondingMIB.* type exclude configure system security snmp view view2 subtree .1.3.6.1.4.1.637.61.1.48.10.1.* type include configure system security snmp community public host-address 10.176.0.0/15 context nt privilege read-write configure system security snmp community NETMAN host-address 10.176.0.0/15 context shub configure system security snmp community comm1 host-address 10.176.0.0/15 context nt read-view protected write-view view1 notify-view everything configure system security snmp group Group1 security-level none context all read-view protected write-view nothing configure system security snmp group Group1 security-level privacy-and-auth context all read-view protected write-view everything configure system security snmp user user1 authentication md5:plain:pswuser1 privacy des:plain:priuser1 configure system security snmp map-user-group user1 group-name Group1 configure system security snmp notify-view nview2 subtree * type include configure system security snmp notify-view nview2 subtree bondingMIB.* type exclude configure system security snmp notify-view nview2 subtree 1.3.6.1.4.1.637.61.1.48.10.1.* type include configure system security snmp notify-profile nprof2 snmp-version v3:snmpuser1:privacy-and-auth configure system security snmp notify-profile nprof2 filter notify-view nview2 configure system security snmp manager Manager02 destination 10.176.25.25:6666 notify-profile nprof2 nt shub epon configure trap manager 10.176.25.25:6666 cold-start-trap auth-fail-trap eqpt-change-trap warning-trap minor-trap major-trap critical-trap min-severity warning configure trap definition auth-failure priority high admin trap manager 10.176.25.25:6666 reset-trap-buffer

DLP 2109-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 2110 Manage alarms


Purpose
This procedure provides the steps to manage the alarms in the NE. Alarm management includes:

Managing the alarm logs Configuring an alarm profile for remote LT boards: If required, an external alarm profile can be configured. This alarm profile can be assigned to a remote LT board. The profile reflects a configuration of external alarms parameters that corresponds to a certain environment where the remote board is located (in an outdoor cabinet, basement cabinet,...). The use of a profile avoids the need to specify the parameters for each remote board separately. The alarm profile groups all five external alarms parameters. The profile contains a description/meaning of each alarm, as well as an indication that tells us whether or not any alarm outputs are to be triggered if the corresponding external input alarm is raised. On top of these parameters, a mnemonic (short for the description), the polarity and the severity are configurable.

Note The commands for viewing the different alarms are described in DLP 2155.

Prerequisite
The following prerequisite must be fullfilled:

The board must have been planned; see DLP 2111.

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

DLP 2110 Manage alarms

Procedure
Proceed as follows to manage alarms: 1 Manage the alarm logs as follows: i Configure the alarm log settings (alarm severity level, action to be taken when the log buffer is full, minimum severity level for non-interface alarms) with the following command:
configure alarm log-sev-level <Alarm::alarmSeverity> log-full-action <Alarm::alarmLogFullAction> non-itf-rep-sev-level <Alarm::alarmSeverity>

ii

Modify the alarm severity and actions on individual alarms with the following command:
configure alarm entry (index) severity <Alarm::alarmSeverity> (no) service-affecting (no) reporting (no) logging

Note Index refers to the alarm type.


For more information on the different alarm types, see TAP 2104. iii Configure the action to be taken when the alarm log buffer is completely full with the following command:
configure alarm delta-log indet-log-full-action <Alarm::alarmDeltaLogFullAction> warn-log-full-action <Alarm::alarmDeltaLogFullAction> minor-log-full-action <Alarm::alarmDeltaLogFullAction> major-log-full-action <Alarm::alarmDeltaLogFullAction> crit-log-full-act <Alarm::alarmDeltaLogFullAction>
If the action is set to Wrap, then older log records are overwritten by recent ones. If the action is set to Halt, then logging is stopped until the log buffer is reset.

iv

Configure interface management parameters with the following command:


configure interface port (port) (no) admin-status (no) link-state-trap (no) user <Itf::asamIfExtCustomerId> (no) severity <Itf::asamIfExtAlmReportingSeverity>

DLP 2110-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 2110 Manage alarms

Configure the default severity for an alarm on a type of interface with the following command:
configure interface alarm (index) (no) default-severity <Itf::asamIfExtAlmReportingSeverityDefault>

vi

Configure the alarm SHub parameters with the following command:


configure alarm shub entry (index) severity <Alarm::alarmSeverity> (no) service-affecting (no) reporting

Configure an alarm profile for remote LT boards with the following command:
configure alarm custom-profile (name) (no) mnemonic1 <Alarm::AlarmMnemonic> (no) description1 <Alarm::AlarmDescription> (no) visible1 <Alarm::VisibleOutput> (no) audible1 <Alarm::AudibleOutput> (no) polarity1 <Alarm::InversePolarity> (no) severity1 <Alarm::AlarmSeverity> (no) mnemonic2 <Alarm::AlarmMnemonic> (no) description2 <Alarm::AlarmDescription> (no) visible2 <Alarm::VisibleOutput> (no) audible2 <Alarm::AudibleOutput> (no) polarity2 <Alarm::InversePolarity> (no) severity2 <Alarm::AlarmSeverity> (no) mnemonic3 <Alarm::AlarmMnemonic> (no) description3 <Alarm::AlarmDescription> (no) visible3 <Alarm::VisibleOutput> (no) audible3 <Alarm::AudibleOutput> (no) polarity3 <Alarm::InversePolarity> (no) severity3 <Alarm::AlarmSeverity> (no) mnemonic4 <Alarm::AlarmMnemonic> (no) description4 <Alarm::AlarmDescription> (no) visible4 <Alarm::VisibleOutput> (no) audible4 <Alarm::AudibleOutput> (no) polarity4 <Alarm::InversePolarity> (no) severity4 <Alarm::AlarmSeverity> (no) mnemonic5 <Alarm::AlarmMnemonic> (no) description5 <Alarm::AlarmDescription> (no) visible5 <Alarm::VisibleOutput> (no) audible5 <Alarm::AudibleOutput> (no) polarity5 <Alarm::InversePolarity> (no) severity5 <Alarm::AlarmSeverity>

STOP. This procedure is complete.

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

DLP 2110 Manage alarms

Configuration example (Config#1): configure alarm log-sev-level warning log-full-action wrap non-itf-rep-sev-level minor configure alarm entry xdsl-act-not-feas severity major service-affecting reporting logging configure alarm entry non-bonding-cpe severity major service-affecting reporting logging configure alarm delta-log indet-log-full-action wrap warn-log-full-action wrap minor-log-full-action wrap major-log-full-action halt crit-log-full-act halt configure interface port xdsl-line:1/1/5/12 severity major configure interface alarm xdsl-line default-severity critical

DLP 2110-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 2111 Plan, replan, and unplan equipment


Purpose
This document describes the procedure to be used to plan, replan, and unplan equipment. The following applies for the commands used below:

The main subrack can not be planned or unplanned. The extension subrack depends on the main subrack. The active NT (NT-A) can not be planned or unplanned. To replan equipment (except NTs), it must first be unplanned before it can be replanned. Use the same command as for configuring equipment.

Note 1 Refer to TNG 2106 for more information on the planning of remote expansion units. Note 2 The configuration examples in this procedure use the default slot numbering scheme (legacy-based). Refer to TNG 1115 for more information on slot numbering schemes.

NT I/O Board
The following applies for the planning of an NT I/O board:

an NT I/O board that is available at startup will be auto-planned with the detected type if an NT I/O board is replaced, the old board needs to be unplanned first to disable its ports (the operator needs to remove all configuration on the NT I/O ports) if a new NT I/O board is inserted, it needs to be planned before the ports of this NT I/O board are enabled.

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

DLP 2111 Plan, replan, and unplan equipment

SB-REM: dual hosting


For 96-port SB-REM shelves, it can occur that the LT1 board is connected to another host than the LT2 board. From the ISAM's point of view, LT2 will not be visible to the host that connects LT1, and LT1 will not be visible to the host that connects LT2. In the ISAM, there is no way information about another host can be fetched, but the AMS offers this possibility. AMS requires in both hosts an identification of the LT connected to the other host. This identification is offered by the ISAM in two parameters which specify the LT which is connected to the other host, i.e. if an SB-REM shelf is configured from a host with only LT1 connected, then these fields can be specified for LT2. This entry must have EXT_MANAGED (Externally Managed) as planned board type (see step 1 ii)

Example
Suppose:

In Host 1, the SB-REM rack/shelf is configured as 3/1. LT1 is configured as NVLT-D. In Host 2, the same physical SB-REM rack/shelf is configured as 5/3. LT2 is configured as NVLT-D. LT1 is physically connected to Host 1, and LT2 is physically connected to Host 2.

The configuration is then as follows:

In Host 1, the entry for LT2 is put to planned type "EXT_MANAGED", and the parameter dual-host-ip is configured as the IP address of Host 2 and the parameter dual-host-loc is configured as 5/3, identifying the location of LT2 in Host 2. In Host 2, the entry for LT1 is put to planned type "EXT_MANAGED", and the parameter dual-host-ip is configured as the IP address of Host 1 and the parameter dual-host-loc is configured as 3/1, identifying the location of LT1 in Host 1.

Procedure
Proceed as follows to plan, replan, and unplan equipment: 1 Plan units in main subracks as follows: i Plan a subrack with the following command:
configure equipment shelf (index) class <Equipm::ShelfClass> planned-type <Equipm::ShelfType> (no) lock (no) mode <Equipm::HolderMode> (no) description <Description-127>

DLP 2111-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 2111 Plan, replan, and unplan equipment

ii

For each plug-in unit other than an applique, plan the unit in any given slot position with the following command:
configure equipment slot (index) planned-type <Equipm::BoardType> (no) power-down (no) lock (no) alarm-profile <Equipm::AlarmProf> capab-profile <Equipm::CapabilityProfile> dual-host-ip <Ip::V4Address> dual-host-loc <Equipm::Dualhost>

Note 1 An FD passive splitter can be planned by specifying unmanaged for the planned-type parameter. Note 2 The possible values for the parameter capab-profile depend on the actual configuration and software.
The currently allowed values can be shown with online-help. iii If necessary, for each applique, plan the unit with the following command:
configure equipment applique (index) planned-type <Equipm::AppliqueType>

Unplan a subrack with the following command: i If necessary, unplan an applique with the following command:
configure equipment applique (index) no planned-type

ii

Unplan a plug-in unit other than an applique in any given slot position with the following command:
configure equipment slot (index) no planned-type

iii

Unplan a subrack with the following command:


configure equipment shelf (index) no planned-type

Note The main subrack cannot be planned or unplanned, only the description can be changed.

Plan remote equipment (such as remote subracks, REM or SEM) as follows: i If not done already, plan the NT I/O unit in the host subrack with the following command:
configure equipment applique (index) planned-type <Equipm::BoardType>

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

DLP 2111 Plan, replan, and unplan equipment

ii

Plan the remote subrack with the following command:


configure equipment shelf (index) planned-type <Equipm::ShelfType>

iii

Configure the host shelf SFP port as a downlink port with the following command:
configure equipment external-link-host (faceplate number) (no) direction <Equipm::ExternalLinkConfigType>

Note The port must have been configured as residential port with the following command
configure port (faceplate number) ethernet category residential

iv

Configure the SFP downlink port to the remote LT (and SHub VLAN) with the following command:
configure equipment external-link-assign (faceplate-number) remote <Eqpt::ExpRack>/<Eqpt::ExpShelf>/<Eqpt::ExpSlot>

Note The range for the parameter sfp-index depends on the NT board type, see TNG 2106 subsection SFP port mapping for more information.
v Plan the remote LT with the following command:
configure equipment slot (index) planned-type <Equipm::BoardType>

Unplan remote equipment (such as remote subracks, REM or SEM) as follows: i Unconfigure the SFP downlink port with the following command:
configure equipment external-link-assign (faceplate-number) no remote

ii

Unplan the remote LT with the following command:


configure equipment slot (index) planned-type not-planned

iii

Unplan the remote subrack with the following command:


configure equipment shelf (index) planned-type not-planned

View the slot status with the following command:


show equipment slot

STOP. This procedure is complete.

DLP 2111-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 2111 Plan, replan, and unplan equipment

Configuration example for planning a subrack (Config#1): configure equipment shelf 1/1 description "***Mainshelf***" configure equipment slot nt-b planned-type nant-a configure equipment applique iont:1/1 planned-type ncnc-b configure equipment slot lt:1/1/3 planned-type npot-a capab-profile sip configure equipment slot lt:1/1/4 planned-type nvlt-g configure equipment slot lt:1/1/5 planned-type nalt-c configure equipment slot lt:1/1/7 planned-type npot-a configure equipment slot lt:1/1/8 planned-type nslt-a configure equipment slot lt:1/1/13 planned-type nelt-b configure equipment slot lt:1/1/15 planned-type ndlt-c configure equipment slot lt:1/1/16 planned-type ndps-a configure equipment slot lt:1/1/17 planned-type ndlt-g configure equipment slot lt:1/1/18 planned-type ndlt-g info configure equipment slot flat show equipment slot Configuration example for planning a subrack (Config#2): configure equipment shelf 1/1 description "***Mainshelf***" configure equipment slot nt-b planned-type nant-a configure equipment applique iont:1/1 planned-type ncnc-c configure equipment slot lt:1/1/5 planned-type npot-a configure equipment slot lt:1/1/8 planned-type nvps-a configure equipment slot lt:1/1/10 planned-type nbat-b info configure equipment slot flat show equipment slot

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

DLP 2111 Plan, replan, and unplan equipment

Configuration example for planning a remote subrack (Config#3): configure equipment shelf 6/3 planned-type nfxr-a configure interface shub port 7 port-type user admin-status up mc-flooding configure equipment external-link-host 7 direction remote-lt configure equipment external-link-assign 7 remote 6/3/1 configure equipment slot ctrl:6/3 planned-type nrcd-a configure equipment slot 6/3/2 planned-type nvlt-d Configuration example for unplanning a remote subrack (Config#3): configure equipment slot 6/3/2 no planned-type configure equipment slot ctrl:6/3 no planned-type configure equipment external-link-assign 7 no remote configure equipment shelf 6/3 no planned-type

DLP 2111-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 2114 Configure NT redundancy


Purpose
The NE supports line protection and Equipment Protection Switching (EPS). EPS is a mechanism that provides protection against internal failure of the active NT board, if a second redundant NT board is equipped (NT redundancy). For EPS, the concept of protection group is used. A protection group is a group composed of protection and working elements, where the protection element takes over the functionalities of a working element in case it is needed (for example, failure of the working element). For NT redundancy, the protection group consists of both protection elements. Each element represents one NT board. In general, protection elements are defined on slot-level. The protection group and elements are created implicitly by the system, as part of the default configuration. By default the NT protection group is locked.

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

DLP 2114 Configure NT redundancy

Procedure
The following commands can be used to configure NT redundancy or to view the NT redundancy configuration: 1 Configure the administrative status of the protection group with the following command:
configure equipment protection-group (index) (no) admin-status <Equipm::PortGroupAdminStatus> (no) eps-quenchfactor <TimeTicks>

Note 1 The default administrative status of the protection group is locked (that is, NT redundancy is disabled).
If NT redundancy is required, then NT redundancy must be specifically enabled. Use the following command:
configure equipment protection-group 1 admin-status unlock

Note 2 For the parameter eps-quenchfactor:


This timer is used to prevent continuous switchovers in case of unstable EPS and APS. The following must be observed when configuring this timer:

The value 0 is used to disable the EPS quenchfactor timer. The default value is 1440000 (in units of 1/100 seconds). This is a very large value (1440000 = 4 hours). This means that there will be a delay of 4 hours between 2 subsequent operational NT switchover events. You should set this value up front to a more normal value of, for example, 10 minutes (= 60000)

Configure the redundancy control status of a protection group element with the following command:
configure equipment protection-element (index) (no) redcy-ctrl-status <Equipm::ProtElementRedcyCtrlStatus>

DLP 2114-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 2114 Configure NT redundancy

Configure the ports of an SHub interface as follows: i Configure the parameters related to port control configuration of an SHub interface with the following command:
configure interface shub port nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | <Shub::NetworkPort> (no) mode <Sys::PortCtrlMode> (no) port-type <Sys::Type> (no) mc-flooding

ii

Set the adminstrative status of the port(s) to up with the following command:
configure interface shub port nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | <Shub::NetworkPort> admin-status up

Configure redundancy (Link protection and Equipment protection can be coupled or decoupled) in the SHub as follows: i Configure the NT 1+1 protection group on the SHub with the following command:
configure interface shub group (group-id)

ii

Lock the protection group (the system must be in hot-standby configuration first) with the following command:
configure equipment protection-group (prot-group-id) admin-status lock

Note The NT protection group must be locked to avoid the immediate switchover which occurs while configuring the SHub uplink-group threshold value from the default value 0 (= no coupled APS/EPS) towards a value > 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:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | <Shub::NetworkPort>

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 <Itf::Threshold>

Unlock the protection group with the following command:


configure equipment protection-group (prot-group-id) admin-status unlock

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

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

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
ARP Proxy

VRF
DHCP Relay

ISP
P-VLAN

VB LT
IPoE/A Session
IPoE/A Interface ARP Proxy DHCP Relay

P-VLAN

VRF
ARP Proxy

P-VLAN

ISP

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 <Vlan::AdminString> mode layer2-terminated (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) dhcpv6-linerate <Vlan::Dhcpv6-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe>

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)

secure-forwarding aging-time <Vlan::MacAgingTime> l2cp-transparent in-qos-prof-name <Qos::QosIngressProfileName> 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 <Vlan::AdminString> mode residential-bridge (no) mac-move-allow (no) mac-learning-off (no) user2-comm

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 <Vrf::ArpPolicy> unnumbered

Define the gateway IP interface with the following command:


configure ip vrf (vrf-index) gateway-itf ip-address (ip-address)

Add the IP route with the following command:


configure ip vrf (index) route-dest (dest-ip-address) next-hop direct:user-port:<Eqpt::RackId>/<Eqpt::ShelfId> /<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>: <Eqpt::VciId> | <Ip::V4Address>:network:vlan:<Eqpt::VlanId> | <Ip::V4Address>:network:any | direct:network:<Eqpt::VlanId> | direct:user-bridgeport:<Eqpt::RackId>/<Eqpt::ShelfId> /<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>: <Eqpt::VciId> | direct:vlan:<Eqpt::RackId>/<Eqpt::ShelfId> /<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>: <Eqpt::VciId>:<Eqpt::UnstackedVlan> | direct:vlan:<Eqpt::RackId>/<Eqpt::ShelfId>

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

/<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::UnstackedVlan> | direct:user-port:<Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId> | direct:user-bridgeport:<Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId>

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:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>

Configure the broadcast VLAN with the following command:


configure dhcp-relay agent (vrfid) bcast-vlan <Dhcp::VlanId>

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
PPPoE/A Interface

VRF
ARP Proxy

SHub
V-VLAN
Routing Protocols (OSPF, RIPv2)

P-VLAN

VRF
ARP
DHCP Relay

ISP

LT
IPoE/A Session
IPoE/A Interface ARP Proxy DHCP Relay

VRF
ARP Proxy

V-VLAN

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 <Vlan::AdminString> mode layer2-terminated (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) dhcpv6-linerate <Vlan::Dhcpv6-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> 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)

remote-id-pppoe <Vlan::RemoteIdPppoe> secure-forwarding aging-time <Vlan::MacAgingTime> l2cp-transparent in-qos-prof-name <Qos::QosIngressProfileName> 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 <Vlan::AdminString> mode v-vlan (no) mac-move-allow (no) mac-learning-off (no) user2-comm

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)

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

Attach the IP interface to a VRF:


configure interface shub ip (vlanid) vrf-id <Vrf::VrfIndex>

Configure the IP address of the internal IP interface with the following command:
configure interface shub ip (vlanid) ip-address <Ip::V4Address>/<Ip::PrefixLengthFull>

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

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

Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode <Sys::PortCtrlMode> 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 <Vlan::VlanOamIndex>

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 <Vrf::VrfIndex>

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 <Vrf::ArpPolicy> 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 <Ip::NextHopV4Address> vlan-id <Vlan::VlanId> (no) metric <Vrf::ShubRouteMetric>

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 Phy Phy LAG iBridge VLAN 19 LT

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.

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

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 <Vlan::VlanOamIndex>

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 <Vrf::VrfName> (no) desc <Vrf::VrfDescription> (no) contact <Vrf::VrfContact> (no) my-ipaddress <Ip::V4Address> (no) default-ttl <Vrf::DefaultTTL> (no) reassem-timeout<Gauge> 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

Fast-path VRF LT

Router VRF

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 <Vrf::VrfName> (no) desc <Vrf::VrfDescription> (no) contact <Vrf::VrfContact> (no) my-ipaddress <Ip::V4Address> (no) default-ttl <Vrf::DefaultTTL> (no) reassem-timeout<Gauge> mode router

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

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

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 | <Xdsl::ProfilePointer> | name: <PrintableString> spectrum-profile none | <Xdsl::ProfilePointer> | name:<PrintableString> (no) dpbo-profile <Xdsl::LineDpboProfile> (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)

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 <Xdsl::CarrierDataMode> admin-status transfer-mode <Xdsl::TpsTcMode>

Configure the xDSL line with the following command:


configure interface port xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> /<Eqpt::Port> admin-up (no) user <Itf::asamIfExtCustomerId>

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

Do one of the following: a b If an IP router is being used (see Prerequisites), continue with step 5 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 <Ip::NextHopV4Address> vlan-id <Vlan::VlanId>
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.

Create a user port interface with the following command:


configure ip vrf (index) user-itf port (port-interface) (no) qos-profile none | name:<Vlan::QosProfileName>

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

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 <Eqpt::Rack>/<Eqpt::Shelf>/ <Eqpt::LtSlot>/<Eqpt::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 | <Xdsl::ProfilePointer> | name: <PrintableString> spectrum-profile none | <Xdsl::ProfilePointer> | name:<PrintableString> (no) dpbo-profile <Xdsl::LineDpboProfile> (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 <Xdsl::CarrierDataMode> admin-status transfer-mode <Xdsl::TpsTcMode>

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:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port> admin-up (no) user <Itf::asamIfExtCustomerId>

Do one of the following: a b For a user on an ADSL line, continue with step 4 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

Create a bridge port with the following command:


configure bridge port (port)

Create a user port interface with the following command:


configure ip vrf (index) user-itf bridgeport (port-interface) (no) qos-profile none | name:<Vlan::IgnoredQosProfileName>

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

DLP 2126-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 2126 Create an IPoE user

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:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> /<Eqpt::Port>:<Atm::DefaultVpi>:<Atm::DefaultVci>

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

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 Phy Phy LAG VLAN LT

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:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId>

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 <Shub::InDataPort> (no) protocol-type <Sys::ProtocolType> filter <Sys::MacFilter> vlan-id <Sys::FilterVlanId> (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 <Sys::RateCtrlLimit>

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 <Ip::V4Address>/<Ip::PrefixLengthFull> (no) src-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) msg-type <Sys::MsgType> (no) msg-code <Sys::MsgCode> (no) direction <Sys::Direction> (no) vlan-id <Vlan::VlanFilterIndex>

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

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 <Ip::V4Address>/<Ip::PrefixLengthFull> (no) src-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) min-dst-port <Sys::Port> (no) max-dst-port <Sys::Port> (no) min-src-port <Sys::Port> (no) max-src-port <Sys::Port> (no) ack <Sys::AckBit> (no) rst <Sys::RstBit> (no) tos <Sys::Tos> (no) direction <Sys::Direction> (no) vlan-id <Vlan::VlanFilterIndex>

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)

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)

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 <Ip::V4Address>/<Ip::PrefixLengthFull> (no) src-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) min-dst-port <Sys::Port> (no) max-dst-port <Sys::Port> (no) min-src-port <Sys::Port> (no) max-src-port <Sys::Port> (no) direction <Sys::Direction> (no) vlan-id <Vlan::VlanFilterIndex>

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 <Shub::InNetworkPort> (no) protocol<Sys::RestrictedProtocol> (no) action-drop (no) dst-ip-addr <Ip::NetworkAddressAndIpMaskFull> (no) src-ip-addr <Ip::NetworkAddressAndIpMaskFull> (no) vlan-id <Vlan::VlanFilterIndex>

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 <Shub::InNetworkPort> (no) action-drop (no) dst-ip-addr <Ip::NetworkAddressAndIpMaskFull> (no) src-ip-addr <Ip::NetworkAddressAndIpMaskFull> (no) vlan-id <Vlan::VlanFilterIndex>

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 <Shub::InDataPort>]

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

STOP. This procedure is complete.

DLP 2132-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 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 <Ip::V4Address> trace-selection <SignedInteger> (no) router-purge-intv <Igmp::RouterInterval> (no) host-purge-intv <Igmp::HostInterval>

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)

max-mcast-learn <Igmp::MaxMulticastLearn> glb-leave <Igmp::GlobalLeaveMessageStatus> reduced-resp-int <Igmp::ReducedResponseInterval> remove-root-int <Igmp::RemoveRootTimer> full-flooding-off

ii

Configure the CAC parameters in the SHub with the following command:
configure mcast shub (no) active-streams <Igmp::MaxMcastLearn> (no) max-bw <Igmp::SystemMaxbandwidth> (no) max-no-rate-based <Igmp::SystemMaxNoRateBased>

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

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 <Ip::V4Address> (no) verify-checksum (no) query-interval <Igmp::SystemQueryInterval> (no) max-rsp-time <Igmp::SystemQueryMaxResponseTime> (no) robustness <Igmp::SystemRobustness> (no) mem-query-int <Igmp::MembQueryIntvl> (no) last-memb-cnt <Igmp::MembQueryCount> (no) last-max-resp-tim <Igmp::SystemLastMembMaxRespTime> (no) host-report-intv <Igmp::SystemUnsolicitedReportIntvl> (no) start (no) preview-valid <Igmp::SystemPrevalidIntval> (no) cdr-validation <Igmp::SystemPrecdrvalidIntval> (no) cdr-generation (no) except-cdr-rate <Igmp::CDRGenerationForSingles> (no) cdr-export <Igmp::CDRGenerationMethod> (no) cdr-file-aging <Igmp::CDRFileAgingTime> (no) cdr-polling <Igmp::CDRSystemPollingCycle> (no) user-igmp-version <Igmp::igmpSystemGMQToUserSideVersion> (no) netw-igmp-version <Igmp::V3ProcessingAdminStatus> (no) v3-max-num-rec <Igmp::V3MaxNumRecordsReport> (no) forking <Igmp::ForkingStatus> (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 <Igmp::McastCapacityMaxNumGroup> (no) max-num-uncfg <Igmp::McastCapacityMaxNumUnCfg> (no) cfg-res-time <Igmp::reserveTim> (no) uncfg-res-time <Igmp::reserveTim>

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 <Igmp::IntermGenCDRPeriod> (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

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 <Igmp::PkgMemBitMap> (no) max-bitrate <Igmp::GeneralMcastMaxBitRate> (no) mean-bit-rate <Igmp::GeneralMcastMeanBitRate>

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 <PrintableString-0-32> (no) template-name <PrintableString-0-32> template-version <Igmp::igmpPackageTemplateVersion>

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)

STOP. This procedure is complete.

DLP 2136-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 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 <Igmp::VlanVersion> (no) operation-mode <Igmp::VlanMode> (no) self-ip-addr-mode <Igmp::VlanSelfIpAddressMode> (no) self-ip-addr <Ip::V4Address> (no) querier <Igmp::VlanQuerier> (no) query-int <Igmp::VlanQueryInterval> (no) v2-max-rsp-time <Igmp::V2VlanMaxResponseTime> (no) v3-max-rsp-time <Igmp::V3VlanMaxResponseTime>

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 <Igmp::VlanMaxV3AllowedGrps> drop-rpt-network <Igmp::ReportAcptOnAllPorts> robustness <Igmp::VlanRobustnessVar> unsolicit-rpt-int <Igmp::VlanUnsolicitedReportInterval> retry-count <Igmp::VlanRetryCount>

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 <Igmp::LeaveResponse>

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

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

Configure the router ports with the following command:


configure igmp shub vlan-router-port (vlan-id) network-port nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | <Shub::NetworkPort>

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

Configure a bundle with the following command:


configure igmp shub bundle (bundle) (no) bandwidth <Igmp::BundleBandWidth> (no) max-num-channel <Igmp::BundleMaxChannel>

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

Configure one or more packages with the following command:


configure igmp package (index) (no) name <Igmp::igmpPackageName> (no) template-name <Igmp::igmpPackageTemplateName> (no) template-version <Igmp::igmpPackageTemplateVersion>

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 <Ip::V4Address> vlan-id <Igmp::McastChannelVlan> (no) dis-fast-change (no) name <Igmp::multicastSrcName> (no) guaranteed-serv (no) peak-bit-rate <Igmp::McastSrcEtherPeakBitRate>

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 <Igmp::multicastSrcServiceName> preview-duration <Igmp::multicastSrcMaxPreDuration> preview-number <Igmp::multicastSrcMaxPreNumber> preview-blackout <Igmp::multicastSrcPreBlackout> end-ip-addr <Ip::V4Address> mcast-svc-context <Igmp::McastSvcCtxtProfilePointer>

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 <Ip::V4Address> (no) packagemember (package)

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 <Ip::V4Address> vlan-id <Igmp::McastMonitorVlan> (no) loss-duration <Igmp::LossDuration> (no) loss-thresh-alert <Igmp::LossThreshold>

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

Configure the multicast channel in SHub with the following command:


configure mcast shub src (src) vlan-id <Igmp::McastSrcVLANID> ip-addr <Ip::V4Address> (no) eth-sus-bit-rate <Igmp::McastSrcEtherSustainBitRate> (no) guaranteed-serv (no) bundle <Igmp::IgnoredBundleName>

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

Configure a static tree for the multicast channel: a b For SHub subtending ports or network ports, go to step 5 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 <Vlan::VlanId>

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 <Vlan::VlanId> egress-port lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId> | network:<Shub::NetworkPort> | nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | unassigned-link:<Shub::NoExtLink>

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

6 7

Go to step 8 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 <Vlan::VlanId>

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 <Vlan::VlanId> egress-port lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId>

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 <Ip::V4Address> port <Igmp::IgmpIfIndex>

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

STOP. This procedure is complete.

DLP 2138-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

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 <Vrf::ShubVrfName> slow-path-mode

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

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 <Ip::V4Address>/<Ip::PrefixLengthFull> (no) local-arp-proxy

iii

Add the VLAN to the VRF with the following command:


configure interface shub ip (vlan-id) vrf-id <Vrf::ShubVrfID>

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

Enable the SHub relay agent with the following command:


configure dhcp-relay shub relaying

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 <PrintableString-0-32>

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

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 <Dhcp::SecsThreshold> (no) hops-threshold <Dhcp::HopThreshold> (no) agent-ip-addr <Ip::V4Address>

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 <Dhcp::VlanId> (no) option-82 (no) circuit-id <Dhcp::CircuitId> (no) remote-id <Dhcp::RemoteId> (no) client-hw-address <Dhcp::ChaddrMode> (no) dhcp-linerate <Dhcp::Dhcp-linerate>

Enable the SHub relay agent with the following command:


configure dhcp-relay shub relaying

Configure the list of DHCP Relay Servers to a particular VRF with the following command:
configure dhcp-relay shub instance (vrfid) server <Ip::V4Address> server-name <PrintableString-0-32>

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 <Dhcp::SecsThreshold> (no) hops-threshold <Dhcp::HopThreshold> agent-ip-addr <Ip::V4Address>

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 <Vrf::ShubVrfName> 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

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

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 <Ip::V4Address>/<Ip::PrefixLengthFull> (no) local-arp-proxy

iii

Add the VLAN to the VRF with the following command:


configure interface shub ip (vlan-id) vrf-id <Vrf::ShubVrfID>

iv

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

Enable the SHub relay agent with the following command:


configure dhcp-relay shub relaying

Configure the list of DHCP relay servers to the VRF with the following command:
configure dhcp-relay shub instance (vrfid) server <Ip::V4Address> server-name <PrintableString-0-32>

Configure the DHCP relay agent parameters to the VRF with the following command:
configure dhcp-relay shub instance (vrfid) (no) relaying (no) secs-threshold <Dhcp::SecsThreshold> (no) hops-threshold <Dhcp::HopThreshold> agent-ip-addr <Ip::V4Address>

STOP. This procedure is complete.

DLP 2141-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

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 <Aaa::DomainVrfIndex> (no) vlan-id <Vlan::VlanIndexOrZero> (no) primary-dns <Ip::V4Address> (no) second-dns <Ip::V4Address> (no) primary-nbns <Ip::V4Address> (no) second-nbns <Ip::V4Address> (no) sess-timeout <Aaa::DomainSessionTimeout> (no) qos-policy none | name:<Aaa::IgnoredQosProfileName> authenticator local | radius:<Aaa::RadPolicyName> (no) admin-down

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 <Aaa::VrfIndex> ip-address <Ip::V4Address> (no) port <Aaa::InetPortNumber> secret <Password> (no) retry-limit <Aaa::RadiusRetryLimit> (no) timeout-limit <Aaa::RadiusTimeout> (no) admin-down (no) dead-interval <Aaa::RadiusDeadInterval>

Configure the RADIUS accounting server with the following command:


configure system security radius acc-server (name) vrf-index <Aaa::VrfIndex> ip-address <Ip::V4Address> (no) port <Aaa::InetPortNumber> secret <Password> (no) retry-limit <Aaa::RadiusRetryLimit> (no) timeout-limit <Aaa::RadiusTimeout> (no) admin-down (no) dead-interval <Aaa::RadiusDeadInterval>

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

Configure the RADIUS policy with the following command:


configure system security radius policy (name) nas-id <Printable-0-64> nas-ip-address <Ip::V4Address> (no) keep-domain-name (no) disable-accnt-msg (no) acc-interval <Aaa::AccInt> (no) disable-eap

Configure the RADIUS server set with the following command:


configure system security radius policy (name) servers (index) auth-server <Aaa::RadAuthServer> vrf-index-auth <Aaa::VrfIndex> (no) acc-server <Aaa::RadAccServer> (no) vrf-index-acc <Aaa::IgnoredVrfIndex> priority <Aaa::Priority>

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

Configure the security domain with the following command:


configure system security domain (name) vrf-index <Aaa::DomainVrfIndex> (no) vlan-id <Vlan::VlanIndexOrZero> (no) primary-dns <Ip::V4Address> (no) second-dns <Ip::V4Address> (no) primary-nbns <Ip::V4Address> (no) second-nbns <Ip::V4Address> (no) sess-timeout <Aaa::DomainSessionTimeout> (no) qos-policy none | name:<Aaa::IgnoredQosProfileName> authenticator radius:<Aaa::RadPolicyName> (no) admin-down

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

STOP. This procedure is complete.

DLP 2144-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

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

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:<Alarm::alarmSnapShotOwner> | start:warning:<Alarm::alarmSnapShotOwner> | start:minor:<Alarm::alarmSnapShotOwner> | start:major:<Alarm::alarmSnapShotOwner> | start:critical:<Alarm::alarmSnapShotOwner> | start:<SignedInteger>:<Alarm::alarmSnapShotOwner>

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:<Alarm::alarmSnapShotOwner> | start:warning:<Alarm::alarmSnapShotOwner> | start:minor:<Alarm::alarmSnapShotOwner> | start:major:<Alarm::alarmSnapShotOwner> | start:critical:<Alarm::alarmSnapShotOwner> | start:<SignedInteger>:<Alarm::alarmSnapShotOwner>

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

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:

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.

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.

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.

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

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

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

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

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

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

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

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

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

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

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

Change the external VLAN in the system with the following command:
configure system id <Sys::systemId> name <PrintableString-0-255> location <PrintableString-0-255> contact-person <PrintableString-0-255> (no) en-snmp-auth-traps <Transport::SnmpAuthTraps> (no) ether-shape-rate <Sys::etherShapeRate> mgnt-vlan-id <Vlan::VlanOamIndex> system-mac <Sys::MacAddr>/<Sys::MacAddr>/<Sys::Number> (no) port-num-inpro <Sys::PortNumberInprotocol>

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.

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

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)

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 <Vlan::VlanOamIndex>

Save the SHub database with the following command:


admin software-mngt shub database save

STOP. This procedure is complete.

DLP 2162-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

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) (ip-addr) timeout <Ip::PingTimeout> tries <Ip::PingTries> mtu-size <Ip::PingMtu>

Ping another host in a given VRF (from the SHub) with the following command:
ping (no) (no) (no) (ip-addr) vrf (vrf) timeout <Ip::PingTimeout> tries <Ip::PingTries> mtu-size <Ip::PingMtu>

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

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:

Procedure

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.

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 <Ip::TracerouteTTL> last-hop <Ip::TracerouteTTL> (no) timeout <Ip::TracerouteTimeout> (no) mtu-size <Ip::TracerouteMtu>

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

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 <Ip::TracerouteTTL> last-hop <Ip::TracerouteTTL> (no) timeout <Ip::TracerouteTimeout> (no) mtu-size <Ip::TracerouteMtu>

ii

Terminate the traceroute action with the following command:


traceroute (ip-addr) vrf (vrf) no first-hop

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

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 <CpeProxy::VlanIndex>

Configure the CPE manager with the following command:


configure cpe-management (no) manager <CpeProxy::IPaddress>:<CpeProxy::PortNumber>

Configure a management session to a CPE with the following command:


configure cpe-management (no) session (dslport) (no) connection <CpeProxy::cpeIpProxySessionProtocolPort>

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

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)

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

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

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

DLP 2167-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

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 <sub-domain> flat | tee <file.txt> | discard info configure <sub-domain> flat | tee <file.txt> 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).

You can do one of the following: a Retrieve the configuration file from the ISAM (via TFTP) using the following commands:
$ tftp <isam-ip-address> tftp> bin tftp> get /var/cmd/<file.txt>

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

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

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

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

If a system IP address will be assigned manually, use the following command:


configure system management host-ip-address manual:<Ip::V4Address>/<Ip::PrefixLengthHost>

Configure the new default route of the system with the following command:
configure system management default-route <Ip::V4Address>

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 nodes 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 <Cluster::clusterName> role <Cluster::ClusterRole>

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

Configure the neighbour discovery on system level with the following command:
configure cluster neighbour (no) discov-mode-off <Cluster::DiscoverySystemMode> (no) interval <Cluster::DiscoveryInterval> (no) hold-time <Cluster::DiscoveryHoldTime>

Note By default, the automatic neighbour discovery mode is


enabled.

Configure the topology collection on system level with the following command:
configure cluster collection (no) collect-sys-off (no) hop-delay <Cluster::CollectionHopDelay> (no) port-delay <Cluster::CollectionPortDelay> (no) scope <Cluster::CollectScope> (no) interval <Cluster::CollectionInterval> (no) manual <Cluster::CollectionManualMode>

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

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

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

View the status of the cluster with the folliwng commands:


show cluster counter show cluster neighbour show cluster device show cluster connect

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 Do one of the following: a b 2 To enable EMS management via SNMPv3, go to step 2 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:<Sec::PlainPassword> | [md5|sha1]:encrypted:<Snmp::AuthEncryptedKey> (no) privacy none | des:prompt | des:plain:<Sec::PlainPassword> | des : encrypted : <Snmp::PrivacyEncryptedKey> (no) public <Snmp::Identifier>

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

Configure an SNMPv3 group with the following command:


configure system security snmp group (name) security-level <Snmp::SecurityLevel> context single:nt | single:shub | single:epon | all (no) read-view <Snmp::ViewName> (no) write-view <Snmp::ViewName> (no) notify-view <Snmp::ViewName>

Map an SNMPv3 user to an SNMPv3 group with the following command:


configure system security snmp map-user-group (name) group-name <Snmp::GroupName>

3 4

Go to step 5. 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 <Ip::V4Address>/<Ip::PrefixLengthFull>

Configure the SNMP community name NETMAN with the following command:
configure system security snmp community NETMAN host-address <Ip::V4Address>/<Ip::PrefixLengthFull> context shub

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 <Sec::Prompt> (no) password-timeout <Sec::PasswordTimeout> (no) terminal-timeout <Sec::InactivityTimeout> (no) slot-numbering <Sec::SlotDesc> (no) description <Sec::ProfileDesc> (no) aaa <Sec::Aaa> (no) atm <Sec::Atm> (no) alarm <Sec::Alarm> (no) dhcp <Sec::Dhcp> (no) equipment <Sec::Equipment> (no) igmp <Sec::Igmp> (no) ip <Sec::Ip> (no) ppoe <Sec::Ppoe> (no) qos <Sec::Qos> (no) software-mngt <Sec::Sw>

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 <Sec::Transport> vlan <Sec::Vlan> xdsl <Sec::Xdsl> security <Sec::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 <Sys::systemId> name <Transport::sysName> location <Transport::sysLocation> (no) access-oper-id <Sys::accessOperatorId> contact-person <Transport::sysContact> (no) en-snmp-auth-trap (no) ether-shape-rate <Sys::etherShapeRate> mgnt-vlan-id <Vlan::VlanId> system-mac <Sys::systemMac> (no) port-num-in-proto <Sys::PortNumberInprotocol>

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

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:<Ip::V4Address>/<Ip::PrefixLengthHost>

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 users 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

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

Configure the network port management (inband or outband) with the following command:
configure interface shub port (network-port) (no) mode <Sys::PortCtrlMode> (no) port-type <Sys::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 3 4 5 6 7 up up up up up up up down down down up up one-gb one-gb one-gb one-gb hundred-mbps hundred-mbps outband user subtending network network network full full full full full half

----------------------------------------------------------------

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)

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)

Configure the bridge port with the following command:


configure bridge shub port (port) pvid 4093

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)

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

Use the following command to show the MSTP counters:


show mstp bridge show mstp instance show mstp network-port show mstp port-instance

Use the following command to show the SHub port statistics:


show bridge network-port (port)

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

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 <Igmp::MulticastAddress> src-ip-addr <Ip::V4Address> 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)

Use the following command to show the IP forwarding statistics:


show ip vrf-statistics (vrf-id)

Use the following command to show the VRF net-to-media statistics:


show ip vrf-media (slot:vrf) [ip-address <Ip::V4Address>]

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

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

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 <Aaa::VrfIndex> show security radius acc-server acc-stats (name) vrf-index <Aaa::VrfIndex>

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 <Transport::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 <Ima::GroupIntervalNumber> show ima group counters far-end current-interval (if-index) show ima group counters far-end previous-interval (if-index) interval-no <Ima::GroupFarEndIntervalNumber> 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 <Ima::LinkIntervalNumber> show ima link counters far-end current-interval (if-index) show ima link counters far-end previous-interval (if-index) interval-no <Ima::LinkFarEndIntervalNumber>

22

Use the following commands to show the SHDSL information:


show shdsl inventory (if-index) unit-id <Shdsl::UnitId> show shdsl span-status (if-index) show shdsl unit-status (if-index) unit-id <Shdsl::UnitId> show shdsl segment-status (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> wire-pair <Shdsl::SegmentTerminationWirePair> show shdsl segment-counters current-15min (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> wire-pair <Shdsl::SegmentTerminationWirePair> show shdsl segment-counters current-1day (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> wire-pair <Shdsl::SegmentTerminationWirePair> show shdsl segment-counters previous-15min (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> wire-pair <Shdsl::SegmentTerminationWirePair> int-no <Shdsl::IntervalNumber>

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 <Shdsl::UnitId> side <Shdsl::SegmentSide> wire-pair <Shdsl::SegmentTerminationWirePair> int-no <Shdsl::Interval1DayNumber> 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 <Shdsl::PM15MinIntervalNumber> show shdsl span-counters previous-1day (if-index) interval-number <Shdsl::PM1DayIntervalNumber>

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 <Vlan::SignedInteger> show vlan port-prev-day-stats (port) interval-number <Vlan::SignedInteger> show vlan current-15min-stats (vlanid) port <Itf::AtmInterfaceVpiVci> ] show vlan current-day-stats (vlanid) port <Itf::AtmInterfaceVpiVci> show vlan previous-15min-stats (vlanid) port <Itf::AtmInterfaceVpiVci> interval-number <Vlan::SignedInteger> show vlan vlan-day-stats (vlanid) port <Itf::AtmInterfaceVpiVci> interval-number <Vlan::SignedInteger>

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 <Sip::IntervalNumber15min>]] show voice sip statistics termination prev-1day [(if-index) [interval-num <Sip::IntervalNumber1day>]] 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 <Sip::IntervalNumber15min> ] ] show voice sip statistics board prev-1day [ (slot-id) [ interval-num <Sip::IntervalNumber1day> ] ] show voice sip statistics call (if-index) interval [(interval-num) [start-time <Sys::timeInSecs>] [icid <Sip::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 ERAM-A Remote Aggregator NCNC-B NCNC-C NCNC-D NCNC-E NRNT-A 1 to 8 (1) 2 to 7 (2) 2 to 7 (2) 2 to 7 (2) 2 to 7 (2) 3 to 6 (2) Dedicated downlink ports 9 to 24 8 to 13 8 to 13

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 2 If the host shelf SFP port you are configuring is a dedicated downlink port, go to step 4. Configure the host shelf SFP port as a downlink port.
configure equipment external-link-host (faceplate number) (no) direction <Equipm::ExternalLinkConfigType>

You can verify the configured link direction of the configurable ports with the following command:
info configure equipment external-link-host (faceplate number)

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 <Equipm::ExpansionSlotIndex>

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

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 <Equipm::SystemRestart>

Perform an NT reset in a non-redundant system with the following command:


admin equipment slot nt-a reboot <Equipm::BoardRestart>

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

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 Message type Description Authentication actions CLI commands TL1 commands CLI messages Equipment messages TL1 messages Protocol tracing messages Parameter authentication cli-config-chgs tl1-config-chgs cli-msgs EQPT tl1-msgs tracing1 tracing2 tracing3 Video CDR messages All message types (1 of 2) video-cdr all

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 Log severity

Description Emergency Alert Critical Error Warning Notice Information Debug

Parameter EM AL CR ER WN NO IN 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.

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 <Sys::ServerType> 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

Delete a system log server with the following command:


configure system syslog destination (name) disable

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 <Sys::MessageType> facility <Sys::LogFacility> (no) emergency (no) alert (no) critical (no) error (no) warning (no) notice (no) information (no) debug

Retrieve the configuration of a specific system log with the following command:
info configure system syslog destination (name) type <Sys::ServerType> detail

Retrieve the configuration for all configured system logs with the following command:
info configure system syslog destination detail

Force the system log file to rotate with this command:


admin system syslog destination (name) rotate

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)

Configure a static MAC address on the SHub with the following command:
configure vlan shub unicast-mac (unicast-mac) vlan-id <Vlan::VlanIndex> forward-port <Shub::UcastForwardPort>

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 <Ip::V4Address> (no) port <Aaa::InetPortNumber> secret <Password> (no) retry-limit <Aaa::RadiusRetryLimit> (no) timeout-limit <Aaa::RadiusTimeout> (no) admin-down (no) dead-interval <Aaa::RadiusDeadInterval>
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

Configure the RADIUS policy with the following command:


configure system security radius policy (name) nas-id <Printable-0-64> nas-ip-address <Ip::V4Address> (no) keep-domain-name disable-accnt-msg (no) acc-interval <Aaa::AccInt> disable-eap

Configure the RADIUS server set with the following command:


configure system security radius policy (name) servers (index) auth-server none | name:<Aaa::RadAuthServerName> vrf-index-auth <Aaa::VrfIndex> (no) acc-server none | name: <Aaa::RadAccServerName> (no) vrf-index-acc <Aaa::VrfIndex> priority <Aaa::Priority>
where vrf-index-auth is the index of the management VRF, that is 0.

Enable the operator policy with the following command:


configure system security radius (no) relay (no) auth-super-user <Aaa::SuperUserAuth> oper-policy-name <Aaa::OperatorRadPolicyName>

Enable the RADIUS for the superuser with the following command:
configure system security radius (no) relay auth-super-user

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 <Dhcp::VlanId> option-82 circuit-id <Dhcp::CircuitId> remote-id <Dhcp::RemoteId> (no) dhcp-linerate <Dhcp::Dhcp-linerate>

Enable DHCP MAC concentration with the following command:


configure dhcp-relay agent (vrfid) client-hw-address copysourcemac

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 <L2cp::PartitionType>

Configure the ANCP session parameters for a given session ID with the following command:
configure l2cp session (index) bras-ip-address <L2cp::InetAddress> (no) gsmp-version <L2cp::Version> (no) gsmp-sub-version <L2cp::SubVersion> (no) encap-type <L2cp::EncapType> (no) topo-discovery <L2cp::AccessTopologyDiscovery> (no) layer2-oam <L2cp::Layer2OAM> (no) alive-timer <L2cp::AliveTimer> (no) port-reprt-shaper <L2cp::ReportShaper> (no) aggr-reprt-shaper <L2cp::AggrReportShaper> (no) tcp-retry-time <L2cp::TcpRetryTimer> (no) gsmp-retry-time <L2cp::GsmpRetryTimer> (no) dslam-name <L2cp::DslamName> (no) partition-id <L2cp::PartitionId2> (no) window-size <L2cp::WindowSize> (no) tcp-port <L2cp::InetPortNumber> (no) vrf-id <L2cp::VrfIndex> (no) sig-partition-id

Configure an ANCP interface with the following command:


configure l2cp user-port (user-port) partition-id <L2cp::PartitionId>

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)

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

View the ANCP session statistics (traffic counters for L2CP messages) with the following command:
show l2cp session-stats (index)

View the ANCP partition status (interfaces associated to a given partition) with the following command:
show l2cp partition (partition-id) [user-port <Itf::XdslLine>]

Note This command does not list the interfaces associated to the default partition 0.

Stop the ANCP session with the following command:


configure l2cp no session (index)

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

Disable the dual tag mode in the SHub with the following command:
configure vlan shub no dual-tag-mode

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 <Vlan::AgingTime>

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 <Shub::AgingTime>

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

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.

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

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.

DLP 2196-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

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

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

DLP 2196-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 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 rule rule

100 112 1471 1475 17070 08001111 (*|#)x{3}*x+# (*|#|*#)x{2,3}# (141|1470)00x{7} *x{2}*x+# 00x{7}

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 <Sip::VspDomainName> (no) admin-status <Sip::VspAdminStatus> (no) tinfo <Sip::VspTinfo> (no) ta4 <Sip::VspTa4> (no) ttir1 <Sip::VspTtir1> (no) t-acm-delta <Sip::VspTAcmDelta> (no) access-held-time <Sip::VSPAccessHeldTimer> (no) awaiting-time <Sip::VSPAwaitingTimer> (no) digit-send-mode <Sip::VSPDigitSendingMode> (no) overlap-484-act <Sip::VSPOverlap484Action> (no) dmpm-intdgt-expid <Sip::VSPDMPMIntDgtExpid> (no) dial-start-timer <Sip::VSPDialStartTimer> (no) dial-long-timer <Sip::VSPDialLongTimer> (no) dial-short-timer <Sip::VSPDialShortTimer> (no) uri-type <Sip::VSPURIType> (no) rfc2833-pl-type <Sip::VSPRfc2833PayloadType> (no) rfc2833-process <Sip::VSPRfc2833Process> (no) min-data-jitter <Sip::VSPDataJitter> (no) init-data-jitter <Sip::VSPDataJitter> (no) max-data-jitter <Sip::VSPDataJitter> (no) release-mode <Sip::VSPReleaseMode> (no) dyn-pt-nego-type <Sip::VSPDynamicPTNegoType> (no) vbd-g711a-pl-type <Sip::VSPVbdG711APayloadType> (no) vbd-g711u-pl-type <Sip::VSPVbdG711UPayloadType>

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 <Sip::VSPVbdMode> timer-b <Sip::CommonCfgTimerB> timer-f <Sip::CommonCfgTimerF> timer-t1 <Sip::CommonCfgTimerT1> timer-t2 <Sip::CommonCfgTimerT2>

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:

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.

ii

Configure the SIP server(s) with the following command:


configure voice sip server (name) (no) admin-status <Sip::ServerAdminStatus> address <Sip::ServerAddr> (no) port <Sip::ServerPort> (no) server-role <Sip::ServerRole> (no) priority <Sip::ServerPriority> (no) weight <Sip::ServerWeight> (no) site <Sip::ServerSite> (no) transproto <Sip::ServerTransproto> (no) dnsname-type <Sip::DnsDomNameType> admin-domain-name <Sip::AdminDomName>

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:

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.

iii

Configure the DNS server(s) with the following command:


configure voice sip dnsserver (name) (no) admin-status <Sip::sipDNSServerAdminStatus> address <Sip::sipDNSServerAddr> (no) priority <Sip::sipDNSServerPriority> (no) site <Sip::sipDNSServerSite> admin-domain-name <Sip::AdminDomName> (no) port <Sip::sipDNSServerPort>

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:

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.

iv

Configure the SIP user agent with the following command:


configure voice sip user-agent (name) (no) ip-addr-policy <Sip::IpAddrPolicy> (no) ip-config-mode <Sip::IpConfigMode> (no) signal-gateway-ip <Sip::UserAgentIpAddr> signal-vlan-id <Sip::UserAgentVlanId> (no) signal-dscp <Sip::UserAgentSignalDscp> (no) signal-pbits <Sip::UserAgentSignalPbits> (no) signal-link-mtu <Sip::UserAgentLinkMTU> (no) rtp-gateway-ip <Sip::UserAgentIpAddr> rtp-vlan-id <Sip::UserAgentVlanId>

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 <Sip::UserAgentRtpDscp> rtp-pbits <Sip::UserAgentRtpPbits> rtp-link-mtu <Sip::UserAgentLinkMTU> dhcp-optreq-list <Sip::UserAgentDHCPOptionReqList> admin-status <Sip::UserAgentAdminStatus>

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:

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 <SIP::SlotIndex> signal-ip <SIP::IpAddressAndMask> rtp-ip <SIP::IpAddressAndMask> (no) dhcp-fqdn <Sip::UaApDHCPFQDN> (no) admin-status <Sip::UaApAdminStatus>

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 <Sip::SessionTimerMinSE> (no) se-time <Sip::SessionTimerSessionExpire> (no) admin-status <Sip::SysObjectsAdminStatus>

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 <Sip::RegisterUri> (no) register-intv <Sip::RegisterIntv> (no) reg-retry-intv <Sip::RegisterRetryIntv> (no) reg-prev-ava-intv <Sip::RegisterPrevAvaIntv> (no) reg-head-start <Sip::RegisterHeadStart> (no) reg-start-min <Sip::RegisterStartMin>

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 <Sip::TransportProviderName> (no) admin-status <Sip::TransportAdminStatus> (no) port-rcv <Sip::TransportPortRcv> (no) tcp-idle-time <Sip::TransportTCPIdleTime> (no) max-out-udp-size <Sip::TransportMaxOutgUdpReqSize>

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 <Sip::NetwRedunSupported> (no) dns-purge-timer <Sip::NetwRedunDnsPurgeTimer> (no) dns-ini-retr-int <Sip::NetwRedunDnsInitRetranTimer> (no) dns-max-retr-nbr <Sip::NetwRedunDnsMaxRetrNbr> (no) fg-monitor-method <Sip::NetwRedunFgMonitorMethod> (no) fg-monitor-int <Sip::NetwRedunFgMonitorInt> (no) bg-monitor-method <Sip::NetwRedunBgMonitorMethod> (no) bg-monitor-int <Sip::NetwRedunBgMonitorInt> (no) stable-obs-period <Sip::NetwRedunStableObsPeriod> (no) fo-hystersis <Sip::NetwRedunFailoverHystersis> (no) del-upd-threshold <Sip::NetwRedunDeliUpdThreshold>

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 <Sip::NetwRedunAutoFailOver> auto-server-fb <Sip::NetwRedunAutoFailBack> auto-sos-fo <Sip::NetwRedunAutoFailOver> auto-sos-fb <Sip::NetwRedunAutoSosFailback> rtry-after-thrsh <Sip::NetwRedunRetryAfterThreshold>

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

Configure the SIP Line Identifier Syntax with the following command:
configure voice sip lineid-syn-prof (name) (no) syntax-pattern <SIP::LineIdSyntaxPattern> (no) pots-syntax <SIP::PotsSyntax>

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 <Sip::DialPlanPreActivated> (no) static-prefix <Sip::DialPlanStaticPrefix> (no) static-suffix <Sip::DialPlanStaticSuffix>

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 <Sip::DialPlanDigitmapType> rule <Sip::DialPlanDigitmapValue> (no) access-type <Sip::DialPlanDigitmapAccessType>

Note 1 When the string in <Sip::DialPlanDigitmapValue> 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 <Sip::DHCPAuthentParaSecretId> (no) key <Sip::DHCPAuthentParaKey> (no) action-type <Sip::DHCPAuthentParaActionType>

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

Do one of the following:

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 <Sip::asamLluRelayStatus>

ii iii

Go to step 9. Configure the SIP terminations with the following command:


configure voice sip (no) termination (if-index) ) (no) directory-number <Sip::TermDnumber> (no) user-name <Sip::TermUserName> (no) display-name <Sip::TermUserName> (no) uri <Sip::TermUri> (no) direct-uri <Sip::TermUri> (no) line-feed <Sip::TermLineCharacter> (no) md5-realm <Sip::MD5Realm> (no) md5-password <Sip::MD5Realm> (no) admin-status <Sip::TermAdminStatus> (no) clip-mode <Sip::TermETSIClipDataMode> (no) anti-tapping <Sip::TermAntiTapping> (no) impedance <Sip::TermImpedance> (no) rx-gain <Sip::TermRxGain> (no) tx-gain <Sip::TermTxGain>

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 <Sip::JBFL> (no) low-jbfl <Sip::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 <Sip::FailXStartTime> (no) end-time <Sip::FailXEndTime> fail-x-type <Sip::FailXType>

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)]

View the SIP User Agent Access Point operational state with the following command:
show voice sip user-agent-ap [(name) [slot-id <SIP::SlotIndex>]]

View the SIP Termination Profile with the following command:


show voice sip termination [(if-index)]

View the Network Redundancy State with the following command:


show voice sip redundancy-node redundancy-state [(admin-name) [slot-id <SIP::SlotIndex>]]

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)]

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 +862155558236@fs5k8.shanghai.com 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 +862155558236@fs5k8.shanghai.com 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 <Igmp::PkgMemBitMap> (no) max-num-group <Igmp::ChannelMaxNumGroup> (no) igmp-version <Igmp::UserItfVersion> (no) forking <Igmp::ForkingStatus> (no) lt-ont-signaling <Igmp::ChannelLtOntSignaling> (no) mc-pbit-value <Igmp::McPbitValue> (no) mcast-vlan-id <Igmp::ProtocolMcastVlan> (no) mcast-svc-context <Igmp::McastSvcCtxtProfilePointer>

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)

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.

STOP. This procedure is complete.

DLP 2198-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 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:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | <Shub::MstpNetworkPort> (no) queue0-weight <Qos::ShubQueueWeight1> (no) queue1-weight <Qos::ShubQueueWeight1> (no) rx-pause (no) egress-rate <Qos::ShubPortRate> (no) dscp2p-enable

Configure the traffic classes on the SHub with the following command:
configure qos shub tc-map-dot1p (tc-priority) traffic-class <Qos::ShubTrafficClass>

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

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 <Qos::ShubDSCPPriority>

Configure the ingress policing parameters on SHub port with the following command:
configure qos shub meter (index) (no) name <Qos::DisplayString> max-ingress-rate <Qos::MeterIngressRate> burst-size <Qos::MeterBurstSize>

Configure the various flows to be policed with the following command:


configure qos shub flow (index) (no) name <Qos::DisplayString> (no) (type)

Configure the policing association with the following command:


configure qos shub policer nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> | <Shub::MstpNetworkPort> flow <Qos::PolicerFlowIndex> meter <Qos::PolicerMeterIndex>

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 <Sys::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 <Shub::StpPriority> (no) max-age <Shub::StpMaxAge> (no) hello-time <Shub::StpHelloTime> (no) forward-delay <Shub::StpFwDelay> (no) version stp-compatible | rstp | mstp (no) tx-hold-count <Shub::StpTxHoldCount> (no) path-cost-type 16-bit | 32-bit (no) max-hop-count <Shub::StpMaxHopCount> region-name <Shub::StpRegionName> (no) region-version <Shub::StpRegionVersion> (no) config-id-sel <Shub::StpConfigIdSelector>

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 <Shub::StpPriority>

Map/unmap the VLAN on the MSTP instance with the following command:
configure mstp instance (instance) (no) associate-vlan (vlan) <Shub::MstpVlanId>

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

Configure the port parameters for the Common Instance with the following command:
configure mstp port (port) (no) priority <Shub::MstpPortPriority> (no) disable-stp path-cost <Shub::MstpPathCost> (no) edge-port (no) admin-p2p <Shub::MstpAdminP2PPort> (no) hello-time <Shub::StpHelloTime>

Note By default MSTP is enabled on the network and outband ports.

Configure the MSTP parameters for a specific port-instance configuration with the following command:
configure mstp port-instance (network-port) instance <Shub::MstpInstance> (no) priority <Shub::MstpPortPriority> (no) disable-stp path-cost <Shub::MstpPathCost>

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

View the MSTP operational information: a View all the common spanning tree instances for the whole bridge with the following command:
show mstp bridge

View the parameters of a multiple spanning tree instance with the following command:
show mstp instance (instance)

View the MSTP network port information with the following command:
show mstp network-port (port)

View all the MSTP port instances with the following command:
show mstp port-instance (network-port) instance (instance)

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

Configure a VLAN on the SHub with the following command:


configure interface shub vlan-id (vlan-id)

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

Configure a VLAN on the SHub with as egress port the SHub port configured in:
configure interface shub ip (vlan-id) ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) local-arp-proxy

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

Configure a management VLAN on the SHub with the following command:


configure interface shub vlan-id 4093

Configure an unnumbered interface on the management VLAN with the following command:
configure interface shub ip 4093

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.

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 <Vlan::vmacUniqueHostID>

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 <Equipm::SystemRestart>

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

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

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 <Vlan::StackedVlan>] [mac <Vlan::MacAddr>]

STOP. This procedure is complete.

DLP 2209-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

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

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)

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)

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 Faceplate numbers for Configurable ports ERAM-A Remote Aggregator NCNC-B NCNC-C (1 of 2) 1 to 8 (1) 2 to 7 2 to 7
(1) (1)

Dedicated uplink ports

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 14 and 15 1 and 2(2)

NCNC-D NCNC-E NRNT-A (2 of 2)

2 to 7 (1) 2 to 7 3 to 6
(1) (1)

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 <Equipm::ExternalLinkConfigType>

You can verify the link direction of the configurable ports with the following command:
info configure equipment external-link-host (faceplate number)

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 <Equipm::SystemRestart>

Perform an NT reset in a non-redundant system with the following command:


admin equipment slot nt-a reboot <Equipm::BoardRestart>

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

You can troubleshoot a problem with a network link with the following command:
show equipment diagnostics sfp [position] detail

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}]

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

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)

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 <Cfm::FormatedName> level <Cfm::MdLevelType>

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

Create or modify an MA with the following command:


configure cfm domain (domain-index) association (association-index) vlan <Vlan::StackedVlan> (no) mhf-creation <Cfm::CfmMhfCreationType>

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 <Cfm::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 <Vlan::StackedVlan> level <Cfm::MdLevelType> direction <Cfm::CfmDirectionType>

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<tidXXXXX>' 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

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.)

DLP 2216-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 2216 Configure Voice MEGACO

POTS: a flat value in the rage [032767] ISDN BRI: a flat value in the range [08175]

Improved Flat Termination ID

Consists of a prefix and a termination ID. The format is 'prefix<tidXXXXX>'. 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 [032767] ISDN BRI: a flat value in the range [08175]

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

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.

DLP 2216-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 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:

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.

DLP 2216-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 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

Configure the Voice Server Addressing properties with the following command:
configure voice cluster (cluster-id) ip ivps-ip <Ip::V4Address> netmask <Ip::V4Address> router-ip <Ip::V4Address> vlan-id <MEGACO::ivpsXLESVLAN> (no) private-ip <Ip::V4Address> (no) private-netmask <Ip::V4Address> (no) private-vlan-id <MEGACO::ivpsPrivateVLAN>

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 <MEGACO::accessEquipmentAsamId> ip-address <Ip::V4Address> (no) nexthop <Ip::V4Address>

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

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 <Equipm::BoardFuncType> lanx-port <MEGACO::accessBoardLanxPort>

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 <MEGACO::mediaGatewayName> ip-address <Ip::V4Address> netmask <Ip::V4Address> (no) udp-port <MEGACO::mediaGatewayUDPPort> (no) router-ip <Ip::V4Address> vlan-id <MEGACO::mediaGatewayVLAN> (no) mgc-type <MEGACO::mediaGatewayMgcType> prim-mgc-ip <Ip::V4Address> (no) mgc-id <MEGACO::medGwyCtrlrCallServerId> (no) prim-mgc-udp <MEGACO::medGwyCtrlrPrimaryUDPPort> (no) sec-mgc-ip <Ip::V4Address> (no sec-mgc-udp <MEGACO::medGwyCtrlrSecondaryUDPPort> (no) tert-mgc-ip <Ip::V4Address> (no) tert-mgc-udp <MEGACO::medGwyCtrlrTertiaryUDPPort> (no) mg-mid-type <MEGACO::mediaGatewayMidType> (no) mg-domain-name <MEGACO::mediaGatewayDomainName> (no) svcreason-format <MEGACO::mediaGatewaySVCReasonFormat> (no) mg-profile-name <MEGACO::mediaGatewayProfileName> (no) admin-status <MEGACO::mediaGatewayadminStatus> termid-type <MEGACO::mediaGwyTermFormat> pstn-term-format <MEGACO::mediaGwyPstnTermFormat> isdn-term-format <MEGACO::mediaGwyIsdnTermFormat> isdn-suffix1 <MEGACO::mediaGwyIsdnSuffix> isdn-suffix2 <MEGACO::mediaGwyIsdnSuffix> (no) max-transhandling <MEGACO::mediaGwyTMax> (no) max-network-delay <MEGACO::mediaGwyMaxNetworkDelay> (no) max-retrans <MEGACO::mediaGwyMaxRetrans>

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 <MEGACO::mediaGwyRedBatteryDelay> release-delay <MEGACO::mediaGwyReleaseDelay> release-type <MEGACO::mediaGwyReleaseType> wt-rls-delay <MEGACO::mediaGwyWaitingReleaseDelay> active-heartbeat <MEGACO::mediaGwyHeartBeat> passive-heartbeat <MEGACO::mediaGwyHeartBeat> retrans <MEGACO::mediaGwyRetrans> max-waiting-delay <MEGACO::mediaGwyMaxWaitingDelay> prov-rpl-time <MEGACO::mediaGwyProvResp> no signal-dscp <MEGACO::mediaGatewaySignDscp> signal-pbits <MEGACO::mediaGatewaySignDot1P> rtp-dscp <MEGACO::mediaGatewayVoiceDscp> rtp-pbits <MEGACO::mediaGatewayVoiceDot1P> event-req-id <MEGACO::medGwyEventRequestId> stml-stdsg-evt al-of-evt al-on-evt al-of-strict-evt al-on-strict-evt mg-overload-evt rfc2833-pl-type <MEGACO::mediaGatewayRfc2833PayloadType> rfc2833-process <MEGACO::mediaGatewaytRfc2833Process> dial-start-timer <MEGACO::mediaGatewayDialStartTimer> dial-long-timer <MEGACO::mediaGatewayDialLongTimer> dial-short-timer <MEGACO::mediaGatewayDialShortTimer> min-data-jitter <MEGACO::mediaGatewayDataJitter> init-data-jitter <MEGACO::mediaGatewayDataJitter> max-data-jitter <MEGACO::mediaGatewayDataJitter> ephe-term-prefix <MEGACO::mediaGatewayEpheTermPrefix> ephe-term-min <MEGACO::mediaGatewayEpheTerm> ephe-term-max <MEGACO::mediaGatewayEpheTerm>

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

Configure the Signaling Gateway with the following command:


configure voice cluster (cluster-id) (no) signal-gateway (signal-gateway-id) prim-asp-ip <Ip::V4Address> prim-sctp-port <MEGACO::signallingGatewayInterfacePrimarySCTPPort> sec-asp-ip <Ip::V4Address> (no) sec-sctp-port <MEGACO::signallingGatewayInterfaceSecondarySCTPPort> tert-asp-ip <Ip::V4Address> (no) tert-sctp-port <MEGACO::signallingGatewayInterfaceTertiarySCTPPort> ip-address <Ip::V4Address> sgi-user-label <MEGACO::signallingGatewayInterfaceUserLabel> sgi-mgi <MEGACO::MediaGatewayId> (no) admin-status <MEGACO::signallingGatewayInterfaceAdminStatus>

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:

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 <MEGACO::accTerminationUserPortType> (no) switch-type <MEGACO::accTerminationPacketSwitchType> (no) activate-type <MEGACO::accTerminationL1ActivateType> termination-id <MEGACO::accessTerminationId> media-gateway-id <MEGACO::MediaGatewayId> (no) admin-status <MEGACO::accTerminationAdminStatus> (no) line-feed <MEGACO::accTerminationLineCharact> (no) rx-gain <MEGACO::accTerminationRxGain> (no) tx-gain <MEGACO::accTerminationTxGain> (no) impedance <MEGACO::accTerminationImpedance>

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 <MEGACO::accTerminationVoiceDscp> rtp-pbits <MEGACO::accTerminationVoiceDot1P> clip-mode <MEGACO::accTerminationETSIClipDataMode> metering-type <MEGACO::accTerminationMeteringPulseType> directory-number <MEGACO::accTerminationDirectoryNumber>

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:

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 <Itf::MegacoPotsLine> lktype <MEGACO::accTerminationLockType>

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 <MEGACO::mediaGatewayLockType>

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 <Shub::ModulStatus>

Configure the PCCP group with the following command:


configure pccp group (groupid) (no) admin-state <Shub::AdminState> ping-interval <Shub::PingInterval> ping-dest-ipaddr <Ip::V4Address> (no) switchover <Shub::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

Configure the network PCCP ports with the following command:


configure pccp group (groupid) (ports-list (port))

Retrieve the PCCP group information with the following command:


show pccp group (groupid)

Retrieve the PCCP group port information with the following command:
show pccp port-entry (ctrl-index)

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 <Sys::NetworkPort>

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

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:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId> | network:<Shub::NetworkPort> | nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> external (no) ingress (no) egress

Note 1 The port syntax nt:sfp:<Eqpt::PortIndex> or nt:xfp:<Eqpt::PortIndex> 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:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId> | network:<Shub::NetworkPort> | nt:sfp:<Eqpt::PortIndex> | nt:xfp:<Eqpt::PortIndex> internal (no) ingress (no) egress

Note The port syntax nt:sfp:<Eqpt::PortIndex> or nt:xfp:<Eqpt::PortIndex> is used for ERAM-A network ports only.

The mirroring configuration only becomes effective when it has been enabled with the following command:
configure interface shub mirror enable

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

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

Change the mode from NTIO_UNSUPPORTED to NTIO_SUPPORTED with the following command:
configure equipment shelf (index) mode no-extended-lt-slots

3 4

The system automatically goes into reset after the shelf mode has been changed. 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 Phy Phy LAG VLAN LT

NT_SHUB LT ISAM_SHUB

Procedure
Proceed as follows: 1 Configure a VLAN on the SHub with the following command:
configure vlan id <Vlan::UVlanIndex> name <Vlan::AdminString> mode cross-connect | residential-bridge

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 Phy LT Phy Phy LT Ports

NT_SHUB ISAM_SHUB

LT

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 <Sys::PortCtrlMode> 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

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

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: NT (active)

SyncE-1 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 2 Name QL-PRC Description This synchronization trail transports a timing quality generated by a Primary Reference Clock that is defined in Recommendation G.811. This synchronization trail transports a timing quality generated by Types I or V slave clock that is defined in Recommendation G.812. This synchronization trail transports a timing quality generated by a Type VI slave clock that is defined in Recommendation G.812. This synchronization trail transports a timing quality generated by a SDH Equipment Clock (SEC) that is defined in Recommendation G.813, Option I. This signal should not be used for synchronization. Value Name clk-ql-prc

QL-SSU-A

clk-ql-ssu-a

QL-SSU-B

clk-ql-ssu-b

11

QL-SEC

clk-ql-sec

15

QL-DNU

clk-ql-dnu

Remarks
1 2 SyncE (network) ports cannot be removed form the SyncE SSMout port list. They are always present, and will have SSMout enabled or disabled. 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

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 b For NANT-A and AGNT-A, go to step 2 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

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 4 Go to step 16. Configure the system timing clock priority with the following command:
configure system sync-if-timing ref-order prio1 <sysClkSrc> configure system sync-if-timing ref-order prio2 <sysClkSrc>

Note 1 The parameter <sysClkSrc> 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 <network-port> configure system sync-if-timing synce-2 <network-port>

Note The parameter <network-port> specifies the faceplate port to be used as syncE reference. This faceplate port can be one of the following ports:

nt:sfp:1 nt:sfp:2 none

DLP 2236-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 2236 Configure the enhanced system clock synchronization

Configure the reception of Synchronous Status Messages (SSM) for the synchronous Ethernet reference with the following command:
configure system sync-if-timing ssm <sysClkSrc> (no) ssmenable]

Note The parameter <sysClkSrc> 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

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 <sysClkSrc> (no) default-ql <sysClkSrcQL>]

Note 1 The parameter <sysClkSrc> specifies the clock source which can be one of the following values:

synce-1 synce-2

Note 2 The parameter <sysClkSrcQL> 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 <sysClkSrcQL> 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 <sysClkSrc> (no) target-ql <sysClkSrcQL>

Note 1 The parameter <sysClkSrc> specifies the clock source which can be one of the following values:

synce-1 synce-2

Note 2 The parameter <Sys::SysClkSrcQL> specifies manual setting of the clock source, chosen in compliance with the standards ITU-T G.781, G.8264. The default value for <sysClkSrcQL> 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

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 <Sys::SysClkWaitTime>

Note The parameter <Sys::SysClkWaitTime> specifies the amount of time in the range of [0...720] seconds. The default value for <Sys::SysClkWaitTime> 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 <vlan-id>

13

Optionally, configure the SSMout on SyncE (network) ports with the following command:
configure system sync-if-timing ssmout-synce <network-port> (no) ssmout-enable

Note The parameter <network-port> specifies the faceplate port to be used as syncE reference. This faceplate port can be one of the following ports:

nt:sfp:[1..6] none

DLP 2236-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 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 <dsl-port> [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 <Sys::SysClkSrcQL>

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/[48] 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 2 3 4 5 6 7 8 9 The External Packet Forwarding facility is supported on the 24Gbps NT (including the NRNT-A) only. The External Packet Forwarding facility is supported on the 7302 ISAM, 7330 ISAM FTTN and 7356 ISAM FTTB equipment practices. The External Packet Forwarding facility is supported for the MEGACO and the SIP Centralised based ISAM Voice Service. The External Packet Forwarding facility is supported on the HUB, Subtending and Remote (MEGACO only) ISAM Voice access nodes. The External Packet Forwarding facility is supported on VLANS of type Voice-VLAN and Residential Bridge. The External Packet Forwarding facility supports L2 aggregated network links through static L2 aggregation group configuration. The External Packet Forwarding facility supports L2 aggregated network links through LACP. The External Packet Forwarding facility supports xSTP. 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 <Ip::V4Address>]

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 manufacturer inventory-pba inventory-fpba inventory-ics inventory-clei serial-no Description An identification of the board manufacturer The Alcatel-Lucent Printed Board Assembly code of the code The Alcatel-Lucent Printed Board Assembly code of the board, which also identifies the boot software The Item Change Status iteration code of the board The (USA) Common Language Equipment Identification code of the board 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 <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot> detail show equipment applique <Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::AppliqueSlotId> detail

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 actual temperature tca-threshold-low tca-threshold-high shut-threshold-low shut-threshold-high Description Actual temperature of thermal sensor (in degrees Celsius) Low threshold for the alarm Temperature Exceeded (in degrees Celsius) High threshold for the alarm Temperature Exceeded (in degrees Celsius) Low threshold for the alarm Temperature Shutdown (in degrees Celsius) 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 <Eqpt::SensorId> detail]

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:

Prerequisite

dm_complete.tar dm.tar: This is the dm_complete.tar without the management data

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

Back up the NT database (and SHub database) with the following command:
admin software-mngt database upload actual-active:<Ip::V4Address>:<SwMngt::path>
where <IP::V4Address> is the IP address of the AMS server.

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

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 <Ip::V4Address>:<SwMngt::path>
where <IP::V4Address> is the IP address of the AMS server.

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

Activate the downloaded database with the following command:


admin software-mngt oswp (index current oswp) activate with-linked-db

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

View the result of the test with the following command:


info admin atm port (port)

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 2 3 Lock equipment (mostly plug-in units); see DLP 1112. Shut down individual equipment; see DLP 1153. 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 5 6 7 8 Replan equipment (for example, plug-in units); see DLP 2111. Plug in equipment; see the hardware installation manual for your equipment. Power up individual equipment; see DLP 1153. Unlock equipment (mostly plug-in units); see DLP 1112. Start up or shut down the system. Do one of the following: a b 9 Shut down or restart the SHub; see DLP 1151. 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 <rack>/<shelf>/<slot>/<port> 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 <rack>/<shelf>/<slot>/<port>

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 <rack>/<shelf>/<slot>/ <port> detail

iv

Stop the data collection with the following command:


configure xdsl line <rack>/<shelf>/<slot>/<port> carrier data off

To run DELT in carrier data mode with re-initialization: i Start the data collection with the following command:
configure xdsl line <rack>/<shelf>/<slot>/<port> 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 <rack>/<shelf>/<slot>/<port>

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 <rack>/<shelf>/<slot>/<port>

iv

Collect the results for the xDSL line with the following command:
show xdsl carrier-data [near|far]-end <rack>/<shelf>/<slot>/ <port> detail

Stop the data collection with the following command:


configure xdsl line <rack>/<shelf>/<slot>/<port> carrier data off

To run DELT in loop diagnostics mode: i Start loop diagnostics with the following command:
admin xdsl-line <rack>/<shelf>/<slot>/<port> 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 <rack>/<shelf>/<slot>/<port>

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 <rack>/<shelf>/<slot>/<port>

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 <rack>/<shelf>/<slot>/ <port> detail

Stop the loop diagnostics with the following command:


admin xdsl-line <rack>/<shelf>/<slot>/<port> loop-diagnostic stop

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 <rack>/<shelf>/<slot>/<port> carrier data off

ii

Collect the results for the xDSL line with the following command:
show xdsl carrier-data [near|far]-end <rack>/<shelf>/<slot>/ <port> detail

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 <rack>/<shelf>/<slot>/<port> loop-diagnostic stop

ii

Collect the results for the xDSL line with the following command:
show xdsl carrier-data [near|far]-end <rack>/<shelf>/<slot>/ <port> detail

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


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.

TAP 1107-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

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 Foreign AC voltage Foreign DC voltage Insulating resistance # Parameters 0 0 1 Parameter usage none none The parameter is optional. 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 (1 of 2) 0 none no Threshold configuration no no yes

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 Cable Pair Identification

# Parameters 2

Parameter usage

Threshold configuration no

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)

ETSI Signature (2 of 2)

none

no

Result Values
Following result values may be reported:
Table TAP 1107-2: Result values
LineTestType Foreign_AC_voltage_tr ltExtRptVal 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 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) N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. ltExtRp Val2 N.A. ltExtRp Val3 N.A. ltExtRp Val4 N.A. ltExtRp Val5 N.A.

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 Insulating_resistance_rt

ltExtRptVal Insulating resistance of user line (ring-tip) unit: Ohm Insulating resistance of user line (tip-ground) unit: Ohm Insulating resistance of user line (ring-ground) unit: Ohm Capacitance of user line (tip-ring) unit: nF Capacitance of user line (ring-tip) unit: nF Capacitance of user line (tip-ground) unit: nF Capacitance of user line (ring-ground) unit: nF playTraceToneOKTestTerminated(1), playTraceToneOKTimeout(2), playTraceToneFailed(3), stopTraceToneFailed(4)

ltExtRp Val2 N.A.

ltExtRp Val3 N.A.

ltExtRp Val4 N.A.

ltExtRp Val5 N.A.

Insulating_resistance_tg

N.A.

N.A.

N.A.

N.A.

Insulating_resistance_rg

N.A.

N.A.

N.A.

N.A.

Capacitance_tr Capacitance_rt Capacitance_tg Capacitance_rg Cable Pair Identification

N.A. N.A. N.A. N.A. N.A.

N.A. N.A. N.A. N.A. N.A.

N.A. N.A. N.A. N.A. N.A.

N.A. N.A. N.A. N.A. N.A.

Capacitance_sig Insulating_resistance_ring

Capacitance of etsi signature unit: pF Resistance of etsi signature unit: Ohm

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

(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 (1120 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 Low None Cable-pair-ident ETSI Signature IR A A A NA A None Group Foreign -ac-vol A NA A Foreign -dc-vol A NA A Resistance Capacitance

A NA A

A NA 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 Foreign AC Voltage Foreign DC Voltage Resistance Capacitance Type = Low Cable Pair Identification ETSI Signature CPI E None None None None MELT Session time-out None E E E E E Ref. Individual MELT tests None None None None Ref. Individual MELT tests None None None None Ref. Individual MELT tests None None None None

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 <LineTest::SessCmdForConfig> ownerid <Gauge> timeout-period <LineTest::TimeOutPer> line-num <LineTest::LineNum>

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 <LineTest::ltTypeHigh> type-low <LineTest::ltTypeLow> test-parm-num <LineTest::TestParmNum> test-mode <LineTest::TestModeForConfig> inactive-timer <LineTest::InactTimer>

Note For a description of the different session parameters, see CLI MELT parameter Description

Configure the line parameter with the following command:


configure linetest single ltline (sessionid) lineid <Itf::LineTestMegacoLineId> line-status <LineTest::LineStatusForConfig>

Configure the parameters with the following command:


configure linetest single ltparm (sessionid) test-name(unit) <LineTest::TestType> value1 <LineTest::ExtRpVal> value2 <LineTest::ExtRpVal> value3 <LineTest::ExtRpVal> value4 <LineTest::ExtRpVal> value5 <LineTest::ExtRpVal> min-threshold <LineTest::TestThreshold> max-threshold <LineTest::TestThreshold>

Note For a description of the different single line test parameters and paramter resuirements, see CLI MELT parameter Description

Run the MELT test with the following command:


configure linetest single ltsession (sessionid) session-cmd starttest

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 noerr paramnuminconsis Description No error 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. The number of input parameters configured in the parameter configuration command exceeds the maximum allowed range (0-4). The test parameter(s) been configured is(are) meaningless, because the MELT test type to be executed doesn't require any test parameter input. The test parameter(s) been configured is(are) for MELT test types which have not been defined in the actual configured session. Missing test parameter configuration input for the MELT test types been configured in the session configuration command. TimeOut-Period parameter input missing in session configuration command. 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. The line number configured in the session configuration command is different from the line number configured in line parameter configuration command. The configured number of lines in the session configuration command exceeds the maximum allowed range (1-72). The configured line identity in the line parameter configuration command is invalid. The same line Identity has been configured twice with the line parameter configuration command. The parameters Type-High and/or Type-Low are missing in the session configuration command. The configured value(s) for Type-High and/or Type-Low is(are) incorrect. The value configured for the threshold parameter in the parameter configuration command exceeds the maximum allowed range (0-39). The configured threshold value(s) is (are) meaningless, because the MELT test type to be executed doesn't require any threshold input. The configured threshold value(s) is(are) for MELT test types which have not been defined in the actually configured session. The configured MELT test type does not match the configured test mode. The number of lines been configured in the session configuration command does not match with the configured MELT test type and test mode. The actual line status for subtest is not as required to execute the subtest. The line Identity configured in the line configuration command is not in testing status. The configuration command is not allowed within the current session state.

paramnumoutrange typeneednoparam nontestingtype missingparamconf missingtimeout timeoutnotenough

linenuminconsis

linenumoutrange invalidlineid duplicatedline missingtesttype invalidtesttype thresholdnumerr neednothreshold threshfornon typemismatchmode linenummismatch

wrongstatusforsub lineidinnontest sessionstateerr (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 internalerror inactivetimeroutrange

Description Internal system error 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)

Show all parameters on a specific line id of a session with the following command:
show linetest single ltline (sessionid) lineid <Itf::LineTestMegacoLineId>

Show MELT test report with the following command:


show linetest single lineid-ext-rept (sessionid) lineid <Itf::LineTestMegacoLineId> test-name(unit) <LineTest::TestType> result-index <LineTest::RpRsIndex>

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 25C). 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


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:

TAP 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

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.
Table TAP 1108-1: Overview
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 Y Y Y Y Y Y Y Y Y Y Y Y(2) Y(2) Y(2) Y Y Y Y Y Y Y Termination Provisioned Admin: Unlocked Operational Enabled Line state Busy Test item/Status*

Foreign DC voltage (tr, tg, rg) Foreign AC voltage (tr, tg, rg) Capacitance (tr, tg, rg) Resistance (tr, rt, tg, rg) AC current (tr, tg, rg) DC current (tr, tg, rg) Cable pair identification Feeding voltage DC Feeding voltage AC Feeding current DC Low capacitance phone detect M-Socket (PPA) detection (1) Dial tone delay Noise level Status check Howler tone Talking tests ISDN Loop-Back

Termination Not provisioned Y Y Y Y Y Y Y

Y Y Y Y Y Y Y

Y Y Y Y Y Y Y

Y Y Y Y Y Y Y Y Y Y

Y Y

Y Y

Y Y

Y Y Y

Y Y

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.

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 Feeding Voltage AC: Following conditions are only supported at the 72 lines voice LT board: Termination provisioned & admin unlocked & operational Enabled & Line State Busy Feeding Current DC: Following conditions are only supported at the 72 lines voice LT board: Termination provisioned & admin unlocked & operational Enabled & Line State Busy

(3)

(4)

To allow the NBLT test types mentioned above to run for a non-provisioned port, the following minimum configuration requirements are required: 1 2 3 4 5 6 Configure the internal integrated VoIP service L2/L3 topology at the SHub/IHub. Configure the NT OAM IP address and IP gateway Plan the Voice server Configure the Voice cluster Plan the Voice LT boards in the voice cluster. 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 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 72 lines POTS LT Board Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y 24 lines POTS LT Board

H-Bit 31: Feeded_AC_RMS_Voltage_of_User_Circuit (tr) H-Bit 30: Feeded_AC_RMS_Voltage_of_User_Circuit (tg) H-Bit 29: Feeded_AC_RMS_Voltage_of_User_Circuit (rg) H-Bit 28: Foreign_AC_RMS_Voltage_of_User_Circuit (tr) H-Bit 27: Foreign_AC_RMS_Voltage_of_User_Circuit (tg) H-Bit 26: Foreign_AC_RMS_Voltage_of_User_Circuit (rg) H-Bit 25: Feeded_DC_Voltage_of_User_Circuit (tr) H-Bit 24: Feeded_DC_Voltage_of_User_Circuit (tg) H-Bit 23: Feeded_DC_Voltage_of_User_Circuit (rg) H-Bit 22: Foreign_DC_Voltage_of_User_Circuit (tr) H-Bit 21: Foreign_DC_Voltage_of_User_Circuit (tg) H-Bit 20: Foreign_DC_Voltage_of_User_Circuit (rg) H-Bit 19: Feeding_Current H-Bit 18: Feeded_DC_Voltage_of_User_Circuit (rt) H-Bit 17: Insulating_resistance_of_User_Circuit (tr) (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 Y Y Y Y Y Y Y Y Y Y Y Y Y Y

72 lines POTS LT Board Y Y Y Y Y Y Y Y Y Y Y Y Y Y

24 lines POTS LT Board

H-Bit 16: Insulating_resistance_of_User_Circuit (rt) H-Bit 15: Insulating_resistance_of_User_Circuit (tg) H-Bit 14: Insulating_resistance_of_User_Circuit (rg) H-Bit 13: Insulating_resistance_BAT_of_User_Circuit (gt) H-Bit 12: Insulating_resistance_BAT_of_User_Circuit (gt) H-Bit 11: Capacitance_of_User_Circuit (tr) H-Bit 10: Capacitance_of_User_Circuit (rt) H-Bit 09: Capacitance_of_User_Circuit (tg) H-Bit 08: Capacitance_of_User_Circuit (rg) H-Bit 07: Impedance_of_User_Circuit (tr) H-Bit 06: Impedance_of_User_Circuit (rt) H-Bit 05: Impedance_of_User_Circuit (tg) H-Bit 04: Impedance_of_User_Circuit (rg) H-Bit 03: Low_Capacitance_Phone_Detect H-Bit 02: Reserved H-Bit 01: Dial tone_delay_of_User_Circuit H-Bit 00: Termination_testing (M socket) L-Bit 31: AC_Current_of_user_Circuit (tr) L-Bit 30: AC_Current_of_user_Circuit (tg) L-Bit 29: AC_Current_of_user_Circuit (rg) L-Bit 28: DC_Current_of_User_Circuit (tr) L-Bit 27: DC_Current_of_User_Circuit (tg) L-Bit 26: DC_Current_of_User_Circuit (rg) L-Bit 25: Reserved L-Bit 24: Noise_level L-Bit 23: Reserved L-Bit 22: Howler Tone L-Bit 21: Reserved L-Bit 20: Status_Monitored L-Bit 19: Cable_Pair_Identification L-Bit 18: Talking_Father L-Bit 17: Line_Reverse-Sub_Test L-Bit 16: Private_Meter_Pulse_Sub_Test L-Bit 15: Ring_Subscriber-Sub_Test with Auto Ring Test L-Bit 14: DP/DTMF_Signal_Sub_test (2 of 3)

Y Y Y Y Y Y Y Y

Y Y Y Y Y Y Y Y

Y Y Y Y Y Y Y

Y Y Y Y Y Y Y

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 Y

72 lines POTS LT Board Y

24 lines POTS LT Board

L-Bit 13: Resistance_of_user_Circuit L-Bit 12: N.A. L-Bit 11: N.A. L-Bit 10: ISDN-Loop-Back 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 2 3 4 5 6 Bit 31: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) Bit 30: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) Bit 29: Feeded_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) Bit 28: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) Bit 27: Foreign_AC_RMS_Voltage_of_User_Circuit (Cat_00: Electric) 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 8 9

Bit 25: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric) Bit 24: Feeded_DC_Voltage_of_User_Circuit (Cat_00: Electric) 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 2 3 4 5 6 7 8 9 Bit 31: AC_Current_of_user_Circuit (Cat_00: Electric) Bit 30: AC_Current_of_user_Circuit (Cat_00: Electric) Bit 29: AC_Current_of_user_Circuit (Cat_00: Electric) Bit 28: DC_Current_of_User_Circuit (Cat_00: Electric) Bit 27: DC_Current_of_User_Circuit (Cat_00: Electric) Bit 26: DC_Current_of_User_Circuit (Cat_00: Electric Bit 25: Reserved (N.A.) Bit 24: Noise_level (Cat_00: Electric) 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 Maximum voltage AC - a/b Maximum voltage AC - a/E Maximum voltage AC - b/E Maximum voltage DC - a/b Minimum voltage DC - a/b Maximum voltage DC - a/E Minimum voltage DC - a/E Maximum voltage DC - b/E Minimum voltage DC - B/E Capacitance Maximum capacitance - a/b Maximum capacitance - a/E Maximum capacitance - b/E Loop resistance Insulation resistance Maximum loop resistance - a/b Minimum resistance - a/b and b/a Minimum resistance - a/E and E/a Minimum resistance - b/E and E/b Minimum resistance - a/BAT Minimum resistance - b/BAT AC and DC current Minimum current Maximum current Inward test Minimum feeding DC voltage - a/b Maximum feeding DC voltage - a/b Minimum feeding DC voltage - b/a Maximum feeding DC voltage - b/a Minimum feeding current - a/b Maximum feeding current - a/b Maximum Idle Noise Level Maximum Dial Tone delay Value 6000000 6000000 6000000 6000000 -6000000 6000000 -6000000 6000000 -6000000 5000000 1000000 1000000 1800 20000 20000 20000 20000 20000 -100000 100000 40000000 57000000 -57000000 -40000000 7000 29000 -50000 1000

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 Foreign AC voltage Foreign DC voltage Feeding DC Voltage Feeding Current Insulating resistance Capacitance Impedance. # Parameters 0 0 0 0 0 0 1 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 Low capacity Phone detection Battery Impedance (1 of 2) 0 Parameter usage none none none none none none ltValue1: Meaning: frequency. Range: 5 up to 3000 Hz. Default: 20 Hz. ltValue2: Meaning: RMS voltage. Range: -150V ~ +150V. Default: 15 V Threshold configuration no no no no no no no

none

no

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 Dial Tone delay M-Socket detection AC Current DC Current Noise Level Howler Line Status Monitoring

# Parameters 0 0 0 0 0 0 1

Parameter usage none none none none none none ltValue1: Meaning: Check real parking or short current state Range: 1, 2 1: No check 2: Check Default: -

Threshold configuration no no no no no no no

Cable Pair Identification Talking with Subscriber Line Reverse Subscriber Private Meter Pulses

0 0 0 1

none none none ltValue1: Meaning: Metering Mode Range: 1, 2 1: TAPI_METER_MODE_TTX 2: TAPI_METER_MODE_REVPOL Default: -

no no no no

Ring Subscriber DP/DTMF Signal

0 1

none ltValue1: Meaning: Amount of signals to collect. Range: 1 up to 20 Default: -

no no

Resistance of User Loop ISDN Loop Back

0 1

none LtValue1: 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: -

no no

(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 Feed_AC_voltage_tr ltExtRptVal Feeded AC RMS voltage of user line (tip-ring) 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 Feed_DC_voltage_rt Feeding current (tip-ring) unit: A Feeded DC voltage of user line (ring-tip) unit: mV (1 of 4) N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. ltExtRp Val2 N.A. ltExtRp Val3 N.A. ltExtRp Val4 N.A. ltExtRp Val5 N.A.

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 Insulating_resistance_tr

ltExtRptVal Insulating resistance of user line (tip-ring) unit: Ohm Insulating resistance of user line (ring-tip) unit: Ohm Insulating resistance of user line (tip-ground) unit: Ohm Insulating resistance of user line (ring-ground) unit: Ohm Insulating resistance of user line (tip-bat) unit: Ohm Insulating resistance of user line (ring-bat) unit: Ohm Capacitance of user line (tip-ring) unit: nF Capacitance of user line (ring-tip) unit: nF Capacitance of user line (tip-ground) unit: nF Capacitance of user line (ring-ground) unit: nF Impedance of user line (tip-ring) unit: nF Impedance of user line (ring-tip) unit: nF Impedance of user line (tip-ground) unit: nF Impedance of user line (ring-ground) unit: nF TRUE(1) or FLASE(0)

ltExtRp Val2 N.A.

ltExtRp Val3 N.A.

ltExtRp Val4 N.A.

ltExtRp Val5 N.A.

Insulating_resistance_rt

N.A.

N.A.

N.A.

N.A.

Insulating_resistance_tg

N.A.

N.A.

N.A.

N.A.

Insulating_resistance_rg

N.A.

N.A.

N.A.

N.A.

Insulating_resistance_tbat

N.A.

N.A.

N.A.

N.A.

Insulating_resistance_rbat

N.A.

N.A.

N.A.

N.A.

Capacitance_tr Capacitance_rt Capacitance_tg Capacitance_rg Impedance_tr Impedance_rt Impedance_tg Impedance_rg LowCapDetect (2 of 4)

N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.

N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.

N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.

N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A.

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 Dial_tone_delay

ltExtRptVal Result of the time interval between the off hook and dial tone is played

ltExtRp Val2 Only applicable to SIP 72 lines voice LT board Result of whether the dial tone is stopped by dialing of an arbitrary digit which is simulated by the LT. N.A.

ltExtRp Val3 N.A.

ltExtRp Val4 N.A.

ltExtRp Val5 N.A.

Termination_Testing (M Socket) AC_current_tr AC_current_tg

TRUE(1) or FLASE(0) AC current test normal test (tip-ring) unit: A AC current test normal test (tip-ground) unit: A AC current test normal test (ring-ground) unit: A DC current test normal test (tip-ring) unit: A DC current test normal test (tip-ground) unit: A DC current test normal test (ring-ground) unit: A unit: 0.001dbm playSuccessfulAndOnHookNormal(1) playSuccessfulAndTestTerminated(2) playSuccessfulButOnHookTimeout(3) playFailed(4)

N.A. N.A. N.A.

N.A. N.A. N.A.

N.A. N.A. N.A.

N.A. N.A. N.A.

AC_current_rg

N.A.

N.A.

N.A.

N.A.

DC_current_tr DC_current_tg

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

DC_current_rg

N.A.

N.A.

N.A.

N.A.

Noise_level Normal_Condition_Howler

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

Status_Monitored

eStatusMonitoredBlock(2), eStatusMonitoredIdle(3), eStatusMonitoredBusy(4), eStatusMonitoredParking(5), eStatusMonitoredShort(6)

N.A.

N.A.

N.A.

N.A.

(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 Cable Pair Identification

ltExtRptVal playTraceToneOKTestTerminated(1), playTraceToneOKTimeout(2), playTraceToneFailed(3), stopTraceToneFailed(4)

ltExtRp Val2 N.A.

ltExtRp Val3 N.A.

ltExtRp Val4 N.A.

ltExtRp Val5 N.A.

Talking test (father test item) Line Reverse lineReverseOKTestTerminated(1), lineReverseOKTimeout(2), lineReverseFailed(3) Private Meter Pulses Ring Subscriber with Auto Ring meterSuccess(1), meterFailed (2) 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) Resistance of user loop (rip-ring) 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)

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A.

N.A.

N.A.

N.A.

Resistance_loop_tr

N.A. N.A.

N.A. N.A.

N.A. N.A.

N.A. N.A.

(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 Feeding AC/ DC Voltage Feeding DC Current Not allowed Not allowed Port status = Idle (Onhook) Supported Supported. System simulates a 1.8k Ohm loop resistance between a/b lines. Returns feeding current: ~18mA. Port status = Busy

Not allowed Not allowed

From R4.3 onwards:


Table TAP 1108-7: Feeding DC Voltage / DC Current Test ( R4.3)
Port status = Lock/Disable/Not provisioned Feeding AC/ DC Voltage Not allowed Port status = Idle (Onhook) Supported Port status = Busy

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

Port status = Lock/Disable/Not provisioned Feeding DC Current Not allowed

Port status = Idle (Onhook) Supported. System measures the real feeding current on the line. Returns real feeding current: ~0mA.

Port status = Busy

Supported. Returns real feeding current: ~18mA.

(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 Feeding AC/ DC Voltage Feeding DC Current Not allowed Not allowed Port status = Idle (Onhook) Supported Supported. System simulates a 1.8k Ohm loop resistance between a/b lines. Returns feeding current: ~18mA. Port status = Busy

Not allowed Not allowed

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 Table TAP 1108-9: Allowed Type-High / Type Low parameter combinations
Low-capacitance-phone High Low Feeding-current Foreign-dc-vol Feeded-dc-vol Foreign-ac-vol Feeded-ac-vol Capacitance

None Ac-current Dc-current Noise-level Howler Status-monitored Cable-pair-ident Talking-father Line-reverse-sub p-meter-pulse-sub Ring-subscriber-sub Dpdtmf-signal-sub Userloop-sub Isdn-Loopback

IR A A A A A A A A A A A A A

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA NA NA NA NA NA NA NA NA NA NA NA NA

A NA 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

Msocket-detection A NA NA NA NA NA NA NA NA NA NA NA NA NA

Dialton-delay

Impedance

Resistance

Group

None

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 Feeded AC Voltage Foreign AC Voltage Feeded DC Voltage Foreign DC Voltage Feeding Current Resistance Capacitance Impedance Low Capacitance Phone Dialtone Delay Msocket detection Type = Low AC Current DC Current Noise Level Howler Tone Status Monitoring Cable Pair Identification Talking Father - Line Reverse Sub Talking Father - Private Meter Pulse Sub (1 of 2) E E E HT SM CPI TSTO TSTO 1, 2, 3, 4, 5 1, 2, 3, 4, 5 1, 2, 3, 4, 5 5 1, 2, 3, 4, 5, 6 1, 2, 3, 4, 5 6 6 None None None None None None None None None None None None None NBLT Session time-out NBLT Session time-out None E E E E E E E E E E DT E Ref. Individual NBLT tests 4, 5 ,6* 1, 2, 3, 4, 5 4, 5 ,6* 1, 2, 3, 4, 5 4, 5, 6* 1, 2, 3, 4, 5 1, 2, 3, 4, 5 1, 2, 3, 4, 5 1, 2, 3, 4, 5 4 1, 2, 3, 4 Ref. Individual NBLT tests None None None None None None None None None None None Ref. Individual NBLT tests None None None None None None None None None None None

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 6

MID-NBLT condition to be fulfilled Terminate Call prior to the start of the Ring Subscriber Sub Press digits after having started the DP DTMF Signal Sub None None

Post-NBLT condition to be fulfilled None

Talking Father - Ring Subscriber Sub

TSTO

Talking Father - DT DTMF signal Sub

TSTD

None

Talking Father - Userloop Sub ISDN Loop-Back (2 of 2)

TSTO IL

6 4, 5

None None

(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

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 <LineTest::SessCmdForConfig> ownerid <Gauge> timeout-period <LineTest::TimeOutPer> line-num <LineTest::LineNum> type-high <LineTest::ltTypeHigh> type-low <LineTest::ltTypeLow> test-parm-num <LineTest::TestParmNum> test-mode <LineTest::TestModeForConfig>

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:

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 <Itf::LineTestMegacoLineId> line-status <LineTest::LineStatusForConfig>

Configure the parameters with the following command:


configure linetest cluster (cluster-id) ltparm (sessionid) test-name(unit) <LineTest::TestType> value1 <LineTest::ExtRpVal> value2 <LineTest::ExtRpVal> value3 <LineTest::ExtRpVal> value4 <LineTest::ExtRpVal> value5 <LineTest::ExtRpVal>

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

Show session parameters with the following command:


show linetest cluster (cluster-id) ltsession [(sessionid)]

Show all parameters on a specific line id of a session with the following command:
show linetest cluster (cluster-id) ltline [(sessionid) [lineid <Itf::LineTestMegacoLineId>]]

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

Show Integrated Line Test Report with the following command:


show linetest cluster (cluster-id) lineid-ext-rept [(sessionid)] lineid <Itf::LineTestMegacoLineId> test-name(unit) <LineTest::TestType> result-index <LineTest::RpRsIndex>

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 25C). 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


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.

TAP 1109-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 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:

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)

TAP 1109-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 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 resu