You are on page 1of 766

Alcatel-Lucent 7302

INTELLIGENT SERVICES ACCESS MANAGER | RELEASE 3.4 | FEATURE GROUP 3.5

Alcatel-Lucent 7330
INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE NODE | RELEASE 3.4 | FEATURE GROUP 3.5
OPERATIONS AND MAINTENANCE USING CLI

3HH-05218-AAAA-TQZZA Edition 02 Released

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 2007 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) and the 7330 Intelligent Services Access Manager Fiber to the Node (7330 ISAM FTTN).

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.

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

Prerequisite knowledge
The reader must be familiar with general telecommunications principles.

Safety information
For ETSI safety information, see the 7302 ISAM Safety Manual. For ANSI safety information, see the Mandatory Regulations chapter in the 7330 ISAM FTTN ANSI documentation.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

iii

Preface

ETSI and ANSI release naming


Table 1 shows the ETSI and ANSI release naming.
Table 1 ETSI and ANSI release naming
Market ETSI ANSI Release name Release 3.4 Feature Group 3.5

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 the 7302 ISAM or 7330 ISAM FTTN before you install or use the 7302 ISAM or 7330 ISAM FTTN. The release notes provide important information about the software load.

Documents
Table 2 lists the documents that make up the 7302 ISAM Release 3.4 documentation set.
Table 2 7302 ISAM Release 3.4 documentation set
Title Documentation CD 7302 ISAM CD General documentation Product Information System Description Safety Manual Operations and Maintenance Using CLI Migration User Guide Hardware documentation XD Modular Hardware Installation Guide (1 of 2) Describes the hardware installation for the 7302 ISAM XD Modular equipment 3FE-21578-AAAA-RJZZA Provides general system information for the 7302 ISAM Provides conceptual information for the 7302 ISAM and the 7330 ISAM FTTN Provides general safety guidelines when handling, installing, or operating the 7302 ISAM equipment Provides task-oriented procedures for operating and maintaining the 7302 ISAM and 7330 ISAM FTTN using the CLI Provides information for installing or upgrading the 7302 ISAM 3HH-05221-AAAA-TCZZA 3HH-05217-AAAA-TQZZA 3HH-05223-AAAA-TCZZA 3HH-05218-AAAA-TQZZA CD containing all the documents in the 7302 ISAM documentation set 3HH-05883-AAAA Description Part number

3HH-05228-AAAA-TQZZA

iv

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Preface

Title FD Hardware Installation Guide UD Hardware Installation Guide CLI and TL1 documentation CLI Commands TL1 Commands and Messages Software documentation Software Installation Guide Software Upgrade and Migration Application Procedures (2 of 2) Note
(1)

Description Describes the hardware installation for the 7302 ISAM FD equipment Describes the hardware installation for the 7302 ISAM UD equipment

Part number 3HH-03591-AAAA-RJZZA 3FE-21575-AAAA-RJZZA

Describes the CLI commands for the 7302 ISAM and the 7330 ISAM FTTN Describes the TL1 commands and messages for the 7302 ISAM and the 7330 ISAM FTTN(1)

3HH-04416-CEAA-TCZZA 3HH-05220-AAAA-TCZZA

Describes the software management of the 7302 ISAM equipment Provides instructions for using the automated tools for upgrading and migrating the software for the 7302 ISAM and the 7330 ISAM FTTN

3HH-03390-AAAA-RJZZA 3HH-05609-AAAA-TCZZA

Software documentation is not included on the 7302 ISAM documentation CD

Table 3 lists the documents that make up the 7330 ISAM FTTN Feature Group 3.5 documentation set.
Table 3 7330 ISAM FTTN Feature Group 3.5 documentation set
Title Documentation CD 7330 ISAM FTTN CD General documentation Product Information Provides general system information, features and functionality, and hardware unit data sheets for the 7330 ISAM FTTN Provides conceptual information for the 7302 ISAM and the 7330 ISAM FTTN Provides information for planning and ordering the 7330 ISAM FTTN Provides task-oriented procedures for installing and maintaining the 7330 ISAM FTTN hardware Provides task-oriented procedures for operating and maintaining the 7302 ISAM and 7330 ISAM FTTN using the CLI 3HH-05123-AAAA-TCZZA CD containing all the documents in the 7330 ISAM FTTN documentation set (2) 3HH-05679-AAAA Description Part number

System Description Planning and Ordering Hardware Installation and Maintenance Practices Operations and Maintenance Using CLI CLI and TL1 documentation CLI Commands

3HH-05217-AAAA-TQZZA 3HH-05124-AAAA-TCZZA 3HH-05125-AAAA-TCZZA 3HH-05218-AAAA-TQZZA

Describes the CLI commands for the 7302 ISAM and the 7330 ISAM FTTN

3HH-04416-CEAA-TCZZA

(1 of 2)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

Preface

Title TL1 Commands and Messages Software documentation (2) Software Upgrade and Migration Application Procedures (2 of 2) Note
(2)

Description Describes the TL1 commands and messages for the 7302 ISAM and the 7330 ISAM FTTN

Part number 3HH-05220-AAAA-TCZZA

Provides instructions for using the automated tools for upgrading and migrating the software for the 7302 ISAM and the 7330 ISAM FTTN

3HH-05609-AAAA-TCZZA

Software documentation is not included on the 7330 ISAM FTTN documentation CD

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.

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 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 This is one option. This is another option.

vi

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Preface

You must perform this step.

Procedure 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.

Measurement conventions
Measurements in this document are expressed in imperial units. If metric measurements are included, they appear in brackets following the imperial measurement. The metric measurements follow the Systme international dunits (SI) standard for abbreviation of metric units.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

vii

Preface

viii

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Contents

Preface

iii

Scope .............................................................................................................................. iii Audience .............................................................................................................................. iii Prerequisite knowledge ......................................................................................................... iii Safety information.................................................................................................................. iii ETSI and ANSI release naming............................................................................................. iv Release notes........................................................................................................................ iv Documents ............................................................................................................................ iv Special information ................................................................................................................ vi

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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

ix

Contents

Non-Trouble Procedures (NTP)


NTP 100 Set up a CLI session and configure users NTP 101 Execute script files NTP 102 Configure the system NTP 103 Configure equipment NTP 104 Configure a cross-connect VLAN NTP 105 Configure an iBridge VLAN NTP 106 Configure an IP-aware bridge NTP 107 Configure an IP router NTP 108 Configure services NTP 109 Configure PPPoE termination NTP 110 Add an iBridge user NTP 111 Add an IPoA user NTP 112 Add an IPoE user NTP 113 Add a PPPoE user NTP 114 Perform equipment repairs NTP 115 Monitor alarms NTP 100-1 NTP 101-1 NTP 102-1 NTP 103-1 NTP 104-1 NTP 105-1 NTP 106-1 NTP 107-1 NTP 108-1 NTP 109-1 NTP 110-1 NTP 111-1 NTP 112-1 NTP 113-1 NTP 114-1 NTP 115-1

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Contents

NTP 116 Perform software management NTP 117 Modify system parameters

NTP 116-1 NTP 117-1

NTP 118 Monitor performance and view configuration NTP 118-1 NTP 119 Modify configured services NTP 120 Troubleshooting NTP 121 Manage an SNMP proxy CPE NTP 122 Cluster management NTP 123 Secure shell NTP 124 Maintain the system NTP 125 Add an IPoA cross-connect user NTP 126 Manage system logging NTP 127 Configure SHDSL NTP 128 Manage an IPProxy CPE NTP 119-1 NTP 120-1 NTP 121-1 NTP 122-1 NTP 123-1 NTP 124-1 NTP 125-1 NTP 126-1 NTP 127-1 NTP 128-1

NTP 129 Configure a loopback interface on the SHub NTP 129-1 NTP 130 Link Related Ethernet OAM NTP 130-1

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

xi

Contents

Detailed Level Procedures (DLP)


DLP 100 Set up a CLI session DLP 101 Create operator profiles and instances DLP 102 Configure dual IP address DLP 103 Configure system parameters DLP 104 Configure network interfaces DLP 105 Configure link aggregation usage DLP 106 Configure RSTP DLP 107 Configure OSPF DLP 108 Configure RIP DLP 109 Configure SNMP and trap management DLP 110 Manage alarms DLP 111 Plan, replan, and unplan equipment DLP 112 Lock and unlock equipment DLP 113 Configure the equipment DLP 114 Configure NT redundancy DLP 100-1 DLP 101-1 DLP 102-1 DLP 103-1 DLP 104-1 DLP 105-1 DLP 106-1 DLP 107-1 DLP 108-1 DLP 109-1 DLP 110-1 DLP 111-1 DLP 112-1 DLP 113-1 DLP 114-1

DLP 115 Create a layer2-terminated forwarder VLAN DLP 115-1

xii

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Contents

DLP 116 Create a layer2-terminated router VLAN DLP 117 Create a C-VLAN DLP 118 Create an S-VLAN DLP 119 Create an SC-VLAN DLP 120 Create an iBridge VLAN DLP 121 Add network interfaces to a VLAN DLP 122 Create a forwarding VRF DLP 123 Create a router VRF DLP 124 Create an xDSL user DLP 125 Create an IPoA user DLP 126 Create an IPoE user DLP 127 Create a PPPoE user DLP 128 Add an LT port to a VLAN DLP 129 Create xDSL profiles DLP 130 Configure xDSL bonding DLP 131 Create an xDSL bonding group DLP 132 Configure filtering on SHub DLP 133 Configure QoS on layer 2
Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 116-1 DLP 117-1 DLP 118-1 DLP 119-1 DLP 120-1 DLP 121-1 DLP 122-1 DLP 123-1 DLP 124-1 DLP 125-1 DLP 126-1 DLP 127-1 DLP 128-1 DLP 129-1 DLP 130-1 DLP 131-1 DLP 132-1 DLP 133-1
xiii

Contents

DLP 134 Configure QoS DLP 135 Configure a QoS-aware VLAN DLP 136 Configure multicast on the LT DLP 137 Configure IGMP proxy DLP 138 Configure IGMP snooping

DLP 134-1 DLP 135-1 DLP 136-1 DLP 137-1 DLP 138-1

DLP 139 Configure DHCP relay agent in iBridge mode DLP 139-1 DLP 140 Configure DHCP relay agent in router mode DLP 140-1 DLP 141 Configure DHCP relay agent in forwarder mode DLP 141-1 DLP 142 Configure the security domain DLP 142-1

DLP 143 Configure a PPP connection for local RADIUS authentication DLP 143-1 DLP 144 Configure RADIUS DLP 145 Configure 802.1x DLP 146 Configure PPPoE relay DLP 147 Configure PPPoX relay DLP 148 Enable the PPPoE server DLP 149 Configure PPPoE profiles DLP 144-1 DLP 145-1 DLP 146-1 DLP 147-1 DLP 148-1 DLP 149-1

xiv

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Contents

DLP 150 Configure ARP table entry DLP 151 Shut down and restart the NT DLP 152 Reboot the system

DLP 150-1 DLP 151-1 DLP 152-1

DLP 153 Shut down and restart individual equipment DLP 153-1 DLP 154 Create a snapshot alarm table DLP 155 Monitor alarms DLP 156 Management of the SHub database DLP 157 Manage the SHub database DLP 158 Manage the system database DLP 159 Manage OSWP DLP 160 View version of the SHub software DLP 161 View software licenses counters DLP 162 Modify the external management VLAN DLP 163 Modifying xDSL profiles DLP 164 Ping another host DLP 165 Perform a traceroute action DLP 166 Configure SNMP proxy CPE management DLP 167 Script files
Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 154-1 DLP 155-1 DLP 156-1 DLP 157-1 DLP 158-1 DLP 159-1 DLP 160-1 DLP 161-1 DLP 162-1 DLP 163-1 DLP 164-1 DLP 165-1 DLP 166-1 DLP 167-1
xv

Contents

DLP 168 Modify the system management IP parameters DLP 168-1 DLP 169 Configure cluster management DLP 170 Configure SSH DLP 171 Enable EMS management DLP 172 Create a default operator profile DLP 173 Switching a user from ADSL to VDSL DLP 174 Create an IPoA cross-connect user DLP 175 Configure single IP address DLP 176 Performance monitoring commands DLP 177 Configure SFP downlink ports DLP 178 Configure the default security domain DLP 179 Configure system logging DLP 180 Configure static MAC addresses DLP 169-1 DLP 170-1 DLP 171-1 DLP 172-1 DLP 173-1 DLP 174-1 DLP 175-1 DLP 176-1 DLP 177-1 DLP 178-1 DLP 179-1 DLP 180-1

DLP 181 Configure operator authentication via RADIUS DLP 181-1 DLP 182 Configure SHDSL links DLP 183 Configure IMA on SHDSL links DLP 184 Convert the NE IP address
xvi

DLP 182-1 DLP 183-1 DLP 184-1

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Contents

DLP 185 Configure ANCP session

DLP 185-1

DLP 186 Configure DHCP MAC concentration in forwarder mode DLP 186-1 DLP 187 Configure global VLAN parameters DLP 188 Configure custom PSD points DLP 189 Configure VDSL2 virtual noise values DLP 190 Configure threshold crossing alerts DLP 191 Enable dual tagging in the SHub DLP 192 Configure IPProxy CPE management DLP 193 Enable IPProxy CPE management DLP 187-1 DLP 188-1 DLP 189-1 DLP 190-1 DLP 191-1 DLP 192-1 DLP 193-1

DLP 194 Configure IPProxy CPE management session DLP 194-1 DLP 195 Configure general bridge parameters DLP 196 Configure Voice SIP DLP 195-1 DLP 196-1

DLP 197 View port configuration and operational data DLP 197-1 DLP 198 Configure multicast on the SHub DLP 199 Configure QoS on the SHub DLP 200 Configure MSTP DLP 198-1 DLP 199-1 DLP 200-1

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

xvii

Contents

DLP 201 Configure protocol tracing DLP 202 Configure QoS threshold crossing alerts DLP 203 Configure general security settings

DLP 201-1 DLP 202-1 DLP 203-1

DLP 204 Configure an unnumbered IP interface on the SHub DLP 204-1 DLP 205 Configure Link Related Ethernet OAM DLP 206 Configure a DPBO profile DLP 207 Modify a DPBO profile DLP 208 Configure power back off DLP 209 Configure vMAC DLP 205-1 DLP 206-1 DLP 207-1 DLP 208-1 DLP 209-1

DLP 210 View the status of various system parameters DLP 210-1 DLP 211 Configure SFP uplink ports DLP 211-1

Routine Task Procedure (RTP)


RTP 100 Backup the configuration RTP 101 Restore the configuration RTP 102 Retrieve remote inventory RTP 100-1 RTP 101-1 RTP 102-1

xviii

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Contents

Trouble Analysis Procedure (TAP)


TAP 100 Metallic test access TAP 101 F5 loopback test TAP 102 Equipment repair TAP 103 Single ended line testing TAP 104 Fault isolation and troubleshooting TAP 100-1 TAP 101-1 TAP 102-1 TAP 103-1 TAP 104-1

Training (TNG)
TNG 100 Service installation TNG 101 QoS configuration TNG 102 IGMP and multicast configuration TNG 103 VBAS TNG 104 DHCP relay agent configuration TNG 105 Overall software packages TNG 100-1 TNG 101-1 TNG 102-1 TNG 103-1 TNG 104-1 TNG 105-1

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI TNG 106-1 TNG 107 VDSLx parameters TNG 108 SHDSL parameters TNG 107-1 TNG 108-1

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

xix

Contents

TNG 109 Performance management counters TNG 110 Configuration examples TNG 111 7330 ISAM FTTN ES configuration

TNG 109-1 TNG 110-1 TNG 111-1

TNG 112 7330 ISAM FTTN configuration for subtending TNG 112-1 TNG 113 Multi-ADSL parameters TNG 114 DLP configuration examples TNG 115 TNG 116 Slot numbering schemes Link Related Ethernet OAM (EFM OAM) TNG 113-1 TNG 114-1 TNG 115-1 TNG 116-1

Glossary

Index

xx

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

1 Introduction

1.1 Introduction

1-2 1-2 1-5

1.2 How to Use this Document 1.3 Configuration examples

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

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 and the 7330 ISAM FTTN. These tasks and procedures are identical for the 7302 ISAM and the 7330 ISAM FTTN, unless specified otherwise. Throughout the document, the 7302 ISAM and the 7330 ISAM FTTN will be referred to as the Network Element (NE). See the CLI Commands document for more detailed information about the CLI command syntax.

1.2

How to Use this Document


This document uses the task-oriented practice (TOP) method. The TOP method is a documentation system that supports the installation, operation, and maintenance of telecommunications equipment and software through different layers of documentation. Most layers in the TOP system are programmed documents that provide step-by-step instructions for the successful completion of a specific task or procedure. A task document is structured to provide information in such a way that both experienced and inexperienced users can effectively use the material to perform work assignments. Less-experienced users can refer to detailed step-by-step procedure documents referred to by the task document to easily comprehend and complete the task. Experienced users can bypass the procedure documents and use only the level of information they need to do the task.

TOP layers
The TOP documentation method uses the following layers:

IXL Index List NTP Non-Trouble Procedure DLP Detailed Level Procedure RTL Routine Task List RTP Routine Task Procedure TAP Trouble Analysis Procedure TAD Trouble Analysis Data TNG Training

Figure 1-1 shows the layers and logical path of the TOP documentation method.

1-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

1 Introduction

Figure 1-1 TOP Layers and Documentation Path


Task index List (IXL) or Overview Flowchart User Training Package (TNG)

Non-Trouble Clearing Procedure (NTP) Trouble Analysis Procedure (TAP)

Routine Task List (RTL)

Routine Task Procedure (RTP) Detailed Level Procedure (DLP) or Chart Trouble Analysis Data (TAD)

All layers do not apply to all documents. This document contains only contains the layers needed to complete operation and maintenance tasks and procedures specific to the NE through the EMS.
Index List (IXL)

The IXL lists each task and procedure (for example, Log on to the 5526 AMS), along with related supporting information and the identification number of the corresponding document (for example, DLP 500). This lets users know where to find the appropriate documentation.
Non-Trouble Procedure (NTP)

NTPs are procedures that describe how to perform a task (what to do), such as how to accept 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 refer to detailed procedures (DLPs) or to supporting information (provided in TNGs). This allows inexperienced users (or experienced users who want more information) to go to the DLP or TNG for the additional information they need to complete the task. If user go to the referenced DLP or TNG, they must return to the NTP to continue the task. NTPs are typically referenced from the IXL.
Detailed Level Procedure (DLP)

A DLP describes how to perform a procedure. In addition to step-by-step information, DLPs contain any tables or illustrations that are required to perform the procedure. DLPs can be referenced from the IXL, an NTP, a lower-level TAP, another DLP, or from a TNG. When a DLP is completed, the user returns to the point from which the DLP was referenced.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

1-3

1 Introduction

Routine Task List (RTL)

An RTL provides a listing of routine maintenance procedures (what to do). The detailed steps for each procedure listed in the RTL are provided in RTPs. RTLs are typically referenced from the IXL.
Routine Task Procedure (RTP)

An RTP describes how to perform a routine maintenance procedure. RTPs are typically referenced from an RTL, but references can be made from the IXL if there is no RTL.
Trouble Analysis Procedure (TAP)

TAPs are intended to help identify and clear trouble in the system. TAPs may be organized in levels (what and how to do). A high-level TAP is designed to categorize the trouble through a series of decisions and instructions. Once categorized, a lower-level TAP is referenced. This lower-level TAP addresses only the isolated topic and is structured to isolate and clear the trouble through a series of decisions and instructions without returning to the higher-level TAP. For inexperienced users (or experienced users who want more information), a TAP may provide a references to a TAD, DLP, or TNG. If users go to the referenced TAD, DLP, or TNG, they need to return to the TAP to continue the procedure. TAPs are typically referenced from the IXL or other TAPs.
Trouble Analysis Data (TAD)

A TAD contains supporting information (other than procedural steps) to be used as a trouble-clearing aid. It may be a functional schematic, text, or trouble-clearing chart. TADs are typically referenced from a TAP.
Training (TNG)

A TNG contains supplementary information about a task or procedure. TNGs are typically referenced from an IXL, but references are also made from other TOP layers such as NTPs and DLPs.

Step Procedure 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 notes, tables, figures, examples, and other procedures. All mandatory information required to complete a step is shown at the beginning of the step.

1-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

1 Introduction

Optional information, which can be accessed according to experience level, is enclosed in parentheses as shown in the example below: Log on to the system (for details, see DLP-500). The completion of a specific task or procedure is indicated as follows: STOP. This procedure is complete.

1.3

Configuration examples
Configuration examples are provided in the DLPs. TNG 114 gives a summary of the configuration used in these examples.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

1-5

1 Introduction

1-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Index List (IXL)

IXL 100 Master Task Index List

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

IXL 100 Master Task Index List


Table IXL 100-1: Non-Trouble Procedures (NTPs)
Title Add a PPPoE user Add an iBridge user Add an IPoA cross-connect user Add an IPoA user Add an IPoE user Cluster management Configure a cross-connect VLAN Configure a loopback interface on the SHub Configure an iBridge VLAN Configure an IP router Configure an IP-aware bridge Configure equipment Link Related Ethernet OAM Configure PPPoE termination Configure services Configure SHDSL Configure the system Execute script files Maintain the system Manage an IPProxy CPE Manage an SNMP proxy CPE (1 of 2) NTP number NTP 113 NTP 110 NTP 125 NTP 111 NTP 112 NTP 122 NTP 104 NTP 129 NTP 105 NTP 107 NTP 106 NTP 103 NTP 130 NTP 109 NTP 108 NTP 127 NTP 102 NTP 101 NTP 124 NTP 128 NTP 121

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

IXL 100-1

IXL 100 Master Task Index List

Title Manage system logging Modify configured services Modify system parameters Monitor alarms Monitor performance and view configuration Perform equipment repairs Perform software management Secure shell Set up a CLI session and configure users Troubleshooting (2 of 2)

NTP number NTP 126 NTP 119 NTP 117 NTP 115 NTP 118 NTP 114 NTP 116 NTP 123 NTP 100 NTP 120

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


Title Add an LT port to a VLAN Add network interfaces to a VLAN Configure 802.1x Configure a DPBO profile Configure a QoS-aware VLAN Configure an unnumbered IP interface on the SHub Configure ANCP session Configure ARP table entry Configure cluster management Configure custom PSD points Configure DHCP MAC concentration in forwarder mode Configure DHCP relay agent in forwarder mode Configure DHCP relay agent in iBridge mode Configure DHCP relay agent in router mode Configure dual IP address Configure filtering on SHub Configure general bridge parameters Configure general security settings Configure global VLAN parameters Configure IGMP proxy Configure IGMP snooping Configure IMA on SHDSL links (1 of 4) DLP number DLP 128 DLP 121 DLP 145 DLP 206 DLP 135 DLP 204 DLP 185 DLP 150 DLP 169 DLP 188 DLP 186 DLP 141 DLP 139 DLP 140 DLP 102 DLP 132 DLP 195 DLP 203 DLP 187 DLP 137 DLP 138 DLP 183

IXL 100-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

IXL 100 Master Task Index List

Title Configure IPProxy CPE management Configure IPProxy CPE management session Configure link aggregation usage Configure Link Related Ethernet OAM Configure a PPP connection for local RADIUS authentication Configure MSTP Configure multicast on the LT Configure multicast on the SHub Configure NT redundancy Configure operator authentication via RADIUS Configure OSPF Configure power back off Configure PPPoE profiles Configure PPPoE relay Configure PPPoX relay Configure protocol tracing Configure QoS Configure QoS on layer 2 Configure QoS on the SHub Configure QoS threshold crossing alerts Configure RADIUS Configure RIP Configure SFP downlink ports Configure SFP uplink ports Configure SHDSL links Configure single IP address Configure SNMP and trap management Configure SNMP proxy CPE management Configure SSH Configure static MAC addresses Configure system logging Configure system parameters Configure the default security domain Configure the equipment Configure the security domain Configure threshold crossing alerts Configure VDSL2 virtual noise values (2 of 4)

DLP number DLP 192 DLP 194 DLP 105 DLP 205 DLP 143 DLP 200 DLP 136 DLP 198 DLP 114 DLP 181 DLP 107 DLP 208 DLP 149 DLP 146 DLP 147 DLP 201 DLP 134 DLP 133 DLP 199 DLP 202 DLP 144 DLP 108 DLP 177 DLP 211 DLP 182 DLP 175 DLP 109 DLP 166 DLP 170 DLP 180 DLP 179 DLP 103 DLP 178 DLP 113 DLP 142 DLP 190 DLP 189

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

IXL 100-3

IXL 100 Master Task Index List

Title Configure vMAC Configure Voice SIP Configure xDSL bonding Convert the NE IP address Create a C-VLAN Create a default operator profile Create a forwarding VRF Create a layer2-terminated forwarder VLAN Create a layer2-terminated router VLAN Create a PPPoE user Create a router VRF Create a snapshot alarm table Create an iBridge VLAN Create an IPoA cross-connect user Create an IPoA user Create an IPoE user Create an SC-VLAN Create an S-VLAN Create an xDSL user Create operator profiles and instances Create xDSL profiles Enable dual tagging in the SHub Enable EMS management Enable IPProxy CPE management Enable the PPPoE server Lock and unlock equipment Manage alarms Manage OSWP Manage the SHub database Modify a DPBO profile Modify the external management VLAN Modify the system management IP parameters Modifying xDSL profiles Monitor alarms Perform a traceroute action Performance monitoring commands Ping another host (3 of 4)

DLP number DLP 209 DLP 196 DLP 130 DLP 184 DLP 117 DLP 172 DLP 122 DLP 115 DLP 116 DLP 127 DLP 123 DLP 154 DLP 120 DLP 174 DLP 125 DLP 126 DLP 119 DLP 118 DLP 124 DLP 101 DLP 129 DLP 191 DLP 171 DLP 193 DLP 148 DLP 112 DLP 110 DLP 159 DLP 157 DLP 207 DLP 162 DLP 168 DLP 163 DLP 155 DLP 165 DLP 176 DLP 164

IXL 100-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

IXL 100 Master Task Index List

Title Plan, replan, and unplan equipment Reboot the system Script files Set up a CLI session Shut down and restart individual equipment Shut down and restart the NT Switching a user from ADSL to VDSL View port configuration and operational data View software licenses counters View the status of various system parameters View version of the SHub software (4 of 4)

DLP number DLP 111 DLP 152 DLP 167 DLP 100 DLP 153 DLP 151 DLP 173 DLP 197 DLP 161 DLP 210 DLP 160

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


Title Backup the configuration Restore the configuration Retrieve remote inventory RTP number RTP 100 RTP 101 RTP 102

Table IXL 100-4: Trouble Analysis Procedure (TAP)


Title Equipment repair F5 loopback test Fault isolation and troubleshooting Metallic test access Single ended line testing TAP number TAP 102 TAP 101 TAP 104 TAP 100 TAP 103

Table IXL 100-5: Training (TNG)


Title 7330 ISAM FTTN configuration for subtending 7330 ISAM FTTN ES configuration Configuration examples DHCP relay agent configuration (1 of 2) TNG number TNG 112 TNG 111 TNG 110 TNG 104

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

IXL 100-5

IXL 100 Master Task Index List

Title DLP configuration examples IGMP and multicast configuration Link Related Ethernet OAM (EFM OAM) Multi-ADSL parameters Overall software packages Performance management counters QoS configuration Service installation SHDSL parameters Slot numbering schemes Specifying 7330 ISAM FTTN remote expansion units using the CLI VBAS VDSLx parameters (2 of 2)

TNG number TNG 114 TNG 102 TNG 116 TNG 113 TNG 105 TNG 109 TNG 101 TNG 100 TNG 108 TNG 115 TNG 106 TNG 103 TNG 107

IXL 100-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Non-Trouble Procedures (NTP)

NTP 100 Set up a CLI session and configure users NTP 101 Execute script files NTP 102 Configure the system NTP 103 Configure equipment NTP 104 Configure a cross-connect VLAN NTP 105 Configure an iBridge VLAN NTP 106 Configure an IP-aware bridge NTP 107 Configure an IP router NTP 108 Configure services NTP 109 Configure PPPoE termination NTP 110 Add an iBridge user NTP 111 Add an IPoA user NTP 112 Add an IPoE user NTP 113 Add a PPPoE user NTP 114 Perform equipment repairs NTP 115 Monitor alarms

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 116 Perform software management NTP 117 Modify system parameters NTP 118 Monitor performance and view configuration NTP 119 Modify configured services NTP 120 Troubleshooting NTP 121 Manage an SNMP proxy CPE NTP 122 Cluster management NTP 123 Secure shell NTP 124 Maintain the system NTP 125 Add an IPoA cross-connect user NTP 126 Manage system logging NTP 127 Configure SHDSL NTP 128 Manage an IPProxy CPE NTP 129 Configure a loopback interface on the SHub NTP 130 Link Related Ethernet OAM

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 100 Set up a CLI session and configure users


Purpose
This procedure provides the steps to set up a CLI session with the NE and create a user using the Alcatel-Lucent-developed CLI.

General
Figure NTP 100-1 shows the management topology of the NE system.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 100-1

NTP 100 Set up a CLI session and configure users

Figure NTP 100-1: Management Topology


EMS (e.g. AWS 5523) TL1 Terminal CLI Terminal

SNMP UDP161/ 162

Telnet TCP1023

SSH TCP1022

Telnet TCP23

SSH TCP22

TL1 TL1 Gateway

TL1 Craft Terminal

CLI Craft Terminal

TL1 UDP13001

RS232

RS232

ISAM
TL1 agent CLI agent

IACM subsystem
SNMP agent

SNMP agent

SHub subsystem
Active DB

MIB NT Controller / LIMs

MIB SHub

Note The figure above is valid when the system operates in single IP address mode.
When the system operates in dual IP address mode, then there is also a direct access from the EMS to the SHub SNMP agent. Table NTP 100-1 lists the three types of system managers.
Table NTP 100-1: System Managers
Manager type EMS TL1 CT CLI CT Description Element Management System based on SNMP Craft Terminal using TL1 commands Craft Terminal using Command Line Interface (CLI) commands

See the CLI Commands and Messages document for detailed information about the CLI command syntax. The use of TL1 commands is still supported.

Procedure
Proceed as follows to set up the CLI session and configure the CLI users: 1
NTP 100-2

Set up a CLI session; see DLP 100.

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 100 Set up a CLI session and configure users

2 3 4

Create and configure an Operator Profile; see DLP 101. Create a default Operator Profile; see DLP 172. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 100-3

NTP 100 Set up a CLI session and configure users

NTP 100-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 101 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.

Procedure
In order to use script files, you need to perform the following tasks: 1 2 Create and execute script files; see DLP 167. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 101-1

NTP 101 Execute script files

NTP 101-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 102 Configure the system


Purpose
This document describes the procedure to be used to configure the system.

Prerequisite
A CLI session must have been set up; see DLP 100.

Security Considerations

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

It is NOT advised to use insecure management channels: CLI/Telnet, TL1/UDP, SNMPv1/2, dual IP address mode (only SNMPv1/2 on SHub), TFTP. If SNMPv1/2 is used anyway, it is advised not to use community string = public. It is advised to use secure management channels (CLI/SSH, TL1/SSH, SNMPv3, single IP address mode, SFTP). This implies closing the insecure management channels! SHub ACLs must be configured to allow only the traffic coming from the Element Management System (EMS) (such 5526 AMS or 5523 AWS) to be routed to the NT OBC. Encryption via keys must be promoted compared to passwords.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 102-1

NTP 102 Configure the system

Procedure
Proceed as follows to configure the system: 1 Configure the management IP parameters and network interfaces:

see DLP 175 for configuring the system in single IP address mode see DLP 102 for configuring the system in dual IP address mode

Note To convert the system IP address mode, that is from dual mode to single mode or from single mode to dual mode; see DLP 184.

2 3 4 5 6 7

Configure the system parameters; see DLP 103. Configure Simple Network Management Protocol (SNMP) and trap management; see DLP 109. Enable the management of EMS; see DLP 171. Configure the alarm management; see DLP 110. Save the SHub database; see DLP 157. STOP. This procedure is complete.

NTP 102-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 103 Configure equipment


Purpose
This procedure provides the steps to plan, unplan, or replan the equipment and to lock or unlock the equipment. 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 103-1 to configure the equipment.
Table NTP 103-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.

(1 of 2)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 103-1

NTP 103 Configure equipment

Action Replanning equipment Locking and unlocking equipment

Description Replanning is done when changing the current equipment. When necessary, you can lock any equipment, most often a unit, to put it out of service. Locking a unit renders it inactive. No traffic is generated or received by the units. 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)

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 111. Lock or unlock the equipment; see DLP 112. Modify the configuration of the system equipment; see DLP 113. Configure NT redundancy; see DLP 114. Configure SFP downlink ports; see DLP 177. Configure SFP uplink ports; see DLP 211. STOP. This procedure is complete.

NTP 103-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 104 Configure a cross-connect VLAN


Purpose
The NE supports several VLAN cross-connect models:

Customer VLAN (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. Service provider VLAN (S-VLAN) cross-connect: VLAN stacking for business users. In this cross-connect model, the 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. Two levels of VLAN tags are used, which allow support of hierarchical addressing: The customer VLAN: C-VLAN The service provider VLAN: S-VLAN S-VLAN/C-VLAN cross-connect: VLAN stacking for residential users: 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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 104-1

NTP 104 Configure a cross-connect VLAN

Figure NTP 104-1: CC-CLAN


NE

VLAN X

VLAN Y

VLAN A

VLAN B

Figure NTP 104-2: CC-VLAN: traffic flow


Source MAC address = PC Destination MAC address = Network

NE

PC

Network

Source MAC address = Network Destination MAC address = PC

Procedure
The procedures for creating a cross-connect VLAN are described in the following DLPs: 1 2 3 4 5 6
NTP 104-2

For the configuration of global VLAN parameters: see DLP 187. For the creation of a C-VLAN; see DLP 117. For the creation of an S-VLAN; see DLP 118. For the creation of an SC-VLAN; see DLP 119. For the creation of an Qos aware VLAN; see DLP 135. STOP. This procedure is complete.

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 105 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 NSP.

Note The NE supports up to 128 iBridges

Figure NTP 105-1: iBridge VLAN

VLAN X

NE

Video VLAN

Internet Video

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 105-1

NTP 105 Configure an iBridge VLAN

Figure NTP 105-2: iBridge VLAN: traffic flow


Source MAC address = PC Destination MAC address = Network

NE

PC

Network

Source MAC address = Network Destination MAC address = PC

Procedure
Proceed as follows to configure an iBridge VLAN: 1 2 3 4 For the configuration of global VLAN parameters: see DLP 187. For the creation of an iBridge VLAN; see DLP 120. Add the network interface to the iBridge VLAN; see DLP 121. STOP. This procedure is complete.

NTP 105-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 106 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 perform packet forwarding at L3. This procedure provides the steps to configure an IP-aware bridge on the NE.
Figure NTP 106-1: IP-aware Bridge
VLAN X

NE

Video VLAN

Internet Video

Video VLAN is always in iBridge

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 106-1

NTP 106 Configure an IP-aware bridge

Figure NTP 106-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 122. Create a L2 terminated forwarder VLAN for each of the Network Service Providers (NSP); see DLP 115. Add the network interfaces to the L2 terminated forwarder VLANs; see DLP 121. STOP. This procedure is complete.

NTP 106-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 107 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 106). 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 towards the end-user devices are either dynamically created in the NE in case of dynamic DHCP or PPPoE sessions, or statically provisioned in case of static IP address assignment. Towards the network, IP interfaces are numbered (meaning that the NE IP addresses and subnets are configured).

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 107-1

NTP 107 Configure an IP router

Figure NTP 107-1: IP Router


VLAN X

NE

Video VLAN

Internet Video

VLAN Y Video VLAN is always in iBridge Virtual VLAN

Figure NTP 107-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 123. Create a L2-terminated router VLAN; see DLP 116. Add users; see DLP 125 for adding IPoA user or DLP 126 for adding IPoE user. STOP. This procedure is complete.

NTP 107-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 108 Configure services


Purpose
This procedure provides the steps to configure the following services on the NE:

xDSL profiles Quality of Service (QoS) Internet Group Management Protocol (IGMP) and multicast Dynamic Host Configuration Protocol (DHCP) relay agent and Option 82 Authentication Point-to-Point Protocol (PPP) configuration NT redundancy Link aggregation Rapid Spanning Tree Protocol (RSTP) Routing protocols (optional) Voice Session Initiation Protocol (SIP) Network Access Control Protocol (NACP) session

Procedure
To configure a service, you need to perform the following tasks: 1 Configure xDSL profiles: i ii iii 2 3 For the configuration of the service profiles and the spectrum profiles; see DLP 129. For the configuration of custom PSD points; see DLP 188. For the configuration of virtual noise values for VDSL2; see DLP 189

Configure xDSL bonding; see DLP 130. Configure general bridge parameters for LT and SHub; see DLP 195.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 108-1

NTP 108 Configure services

Configure QoS: i ii iii iv v For the configuration of a QoS-aware VLAN; see DLP 135. For the configuration of QoS on L2; see DLP 133. For the configuration of QoS on L3; see DLP 134. For the configuration of QoS on the SHub; see DLP 199. For the configuration of QoS Threshold Crossing Alerts (TCA); see DLP 202.

Configure IGMP and multicast: i ii iii iv For the configuration of multicast on the LT; see DLP 136. For the configuration of multicast on the SHub; see DLP 198. For the configuration of IGMP proxy on the LT; see DLP 137. For the configuration of IGMP snooping on the SHub; see DLP 138.

Configure DHCP Relay: i ii iii iv For the configuration of the DHCP relay agent in iBridge mode; see DLP 139. For the configuration of the DHCP relay agent in router mode; see DLP 140. For the configuration of the DHCP relay agent in forwarder mode; see DLP 141. For the configuration of DHCP MAC concentration in forwarder mode; see DLP 186.

Configure the authentication settings: i ii iii iv v vi For the configuration of the security domain: see DLP 142. For the configuration of local authentication; see DLP 143. For the configuration of RADIUS; see DLP 144. For the configuration of 802.1x authentication; see DLP 145. For the configuration of operator authentication via RADIUS; see DLP 181. For the configuration of the default security domain; see DLP 178.

Configure the PPP relay settings: i ii For the configuration of PPPoE relay; see DLP 146. For the configuration of PPPoA-PPPoE relay; see DLP 147.

Configure NT redundancy; see DLP 114.

NTP 108-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 108 Configure services

Note If NT redundancy is not required, then this has to be specifically disabled to avoid a missing redundancy alarm; see DLP 114.

10

If necessary, configure link aggregation. Link aggregation is used to aggregate two or more physical links from one switch to another. For the configuration of link aggregation; see DLP 105. If necessary, configure Multiple Spanning Tree Protocol (MSTP); see DLP 200. 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 107. For the configuration of Routing Information Protocol (RIP) management; see DLP 108.

11 12

13 14 15

Configure Voice SIP; see DLP 196. Configure an ANCP session; see DLP 185. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 108-3

NTP 108 Configure services

NTP 108-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 109 Configure PPPoE termination


Purpose
This procedure provides the steps to configure Point-to-Point Protocol (PPP) on the NE.

Procedure
To configure PPPoE termination, you need to perform the following tasks: 1 2 3 For the configuration of the PPPoE server; see DLP 148. For the configuration of PPPoE profiles; see DLP 149. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 109-1

NTP 109 Configure PPPoE termination

NTP 109-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 110 Add an iBridge user


Purpose
This procedure provides the steps to add an iBridge user on the NE.

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

The LT must be planned; see DLP 111. The xDSL profiles must have been created; see DLP 129. An iBridge VLAN should be created; see DLP 120.

Procedure
Proceed as follows to add an iBridge user: 1 2 3 Add the LT to the VLAN, for the first user to be created on the LT for that VLAN; see DLP 128. Create an iBridge user; see DLP 124. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 110-1

NTP 110 Add an iBridge user

NTP 110-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 111 Add an IPoA user


Purpose
An IPoA user interface is a L2 interface created on a PVC which is configured in RFC2684 LLCSNAP routed or RFC2684 VC-MUX routed encapsulation modes. An IPoA interface is attached to a Virtual Router (VR) by configuring an unnumbered IP interface on top of it. The VR is always determined via configuration. Multiple user sessions (or users) may exist on the same IPoA interface. A session corresponds to all the traffic originating from or destined to a host whose IP address is seen by the NE in the customer environment. This procedure provides the steps to add an IPoA user on the NE.

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

The LT must be planned; see DLP 111. xDSL profiles must have been created; see DLP 129. An IP-aware bridge (see NTP 106) or an IP router (see NTP 107) must have been created.

Procedure
Proceed as follows to add an IPoA user: 1 2 If the first IPoA user to be created on a VLAN needs DHCP, configure the VRF for DHCP; see DLP 140. Create an IPoA user; see DLP 125.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 111-1

NTP 111 Add an IPoA user

Add the LT to the VLAN, for the first user to be created on the LT for that VLAN; see DLP 128.

Note This VLAN is a residential bridge VLAN if an IP-aware bridge (see NTP 106) was created before or a virtual VLAN if an IP router (see NTP 107) was created before.
4 STOP. This procedure is complete.

NTP 111-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 112 Add an IPoE user


Purpose
An IPoE(oA) user interface is a L2 interface created on a PVC which is configured in RFC2684 LLCSNAP bridged or RFC2684 VC-MUX bridged encapsulation modes. An IPoE(oA) interface is attached to a VR by configuring an unnumbered IP interface on top of it. The VR is always determined via configuration (802.1x authentication is not supported in combination with IP forwarding). Multiple user sessions (or users) may exist on the same IPoE(oA) interface. A session corresponds to all traffic originated from or destined to a host whose IP address is seen by the NE in the customer environment. This procedure provides the steps to add an IPoE user on the NE.

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

The LT must be planned; see DLP 111. xDSL profiles must have been created; see DLP 129. An IP-aware bridge (see NTP 106) or an IP router (see NTP 107) must have been created.

Procedure
Proceed as follows to add an IPoE user: 1 2 3 If the first IPoE user to be created on a VLAN needs DHCP, configure the VRF for DHCP; see DLP 140. Create an IPoE user; see DLP 126. Add the LT to the correct VLAN (service), for the first user to be created on the LT for that VLAN; see DLP 128.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 112-1

NTP 112 Add an IPoE user

STOP. This procedure is complete.

NTP 112-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 113 Add a PPPoE user


Purpose
A PPPoE(oA) user interface is a L2 interface created on a PVC which is configured in RFC2684 LLCSNAP bridged or RFC2684 VC-MUX bridged encapsulation modes. A PPPoE session is an unnumbered IP interface established by a user on a PPPoE(oA) interface. IP interface is a notion to group traffic and treat as a single entity for different purposes being authentication, accounting, service provisioning, and security. Multiple PPPoE sessions can be established on the same PPPoE(oA) interface. The system can also limit the max number of PPPoE session per PPPoE(oA) via configuration. This procedure provides the steps to add a PPPoE user on the NE.

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

The LT must be planned; see DLP 111. xDSL profiles must have been created; see DLP 129. An IP-aware bridge (see NTP 106) or an IP router (see NTP 107) must have been created. PPPoE termination (that is, enabling PPPoE server and configuration of PPPoE profiles) must have been configured; see NTP 109.

Procedure
Proceed as follows to add a PPPoE user: 1 2 Create a PPPoE user; see DLP 127. Add the LT to the correct VLAN (service), for the first user to be created on the LT for that VLAN; see DLP 128.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 113-1

NTP 113 Add a PPPoE user

STOP. This procedure is complete.

NTP 113-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 114 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 Plan, unplan, and replan equipment (for example, plug-in units); see DLP 111. Pull out and plug in equipment. For the procedures, refer to the XD Modular Hardware Installation Manual for the 7302 ISAM or the Hardware Installation and Maintenance Practices for the 7330 ISAM FTTN. Lock and unlock equipment (mostly plug-in units); see DLP 112. Start up or shut down the system, select one of: a b c 5 Shut down or restart the SHub; see DLP 151. Reboot the entire system; see DLP 152. Shut down individual equipment; see DLP 153.

3 4

STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 114-1

NTP 114 Perform equipment repairs

NTP 114-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 115 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 154. Monitor the alarms; see DLP 155. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 115-1

NTP 115 Monitor alarms

NTP 115-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 116 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 100. Management of the Overall Software Packages; see DLP 159. View the version of the SHub software; see DLP 160. Management of the software licenses; see DLP 161. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 116-1

NTP 116 Perform software management

NTP 116-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 117 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 management IP parameters; see DLP 168. Change the external management VLAN; see DLP 162. Configure an ARP table entry; see DLP 150. Configure filtering on the SHub; see DLP 132. Configure static MAC addresses; see DLP 180. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 117-1

NTP 117 Modify system parameters

NTP 117-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 118 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 Configure the Treshold Crossing Alert (TCA); see DLP 190 Viewing the PM counters; see DLP 176 Viewing the configuration and operational data of a port (xDSL or Ethernet); see DLP 197 STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 118-1

NTP 118 Monitor performance and view configuration

NTP 118-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 119 Modify configured 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 Modify an xDSL profile; see DLP 163. Switching a user from ADSL to VDSL; see DLP 173. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 119-1

NTP 119 Modify configured services

NTP 119-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 120 Troubleshooting


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 3 Ping command; see DLP 164. Traceroute command; see DLP 165. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 120-1

NTP 120 Troubleshooting

NTP 120-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 121 Manage an SNMP proxy CPE


Purpose
The Customer Premises Equipment (CPE) management functionality allows to troubleshoot a 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 CPEs 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 121-1.
Figure NTP 121-1: Network Reference Model
Network Management Entity

CPE-MM

RMI

User Management Entity

LMI NE xDSL CPE

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 121-1

NTP 121 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. For IPProxy CPE management; see NTP 128.

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

NTP 121-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 122 Cluster management


Support
Cluster management is supported on the 7302 ISAM only.

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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 122-1

NTP 122 Cluster management

Figure NTP 122-1 shows an example of the cluster management topology.


Figure NTP 122-1: Cluster Management Topology
Management Command to Cluster 2

Cluster No. 2 (A logical DSLAM)

EMS (AWS)

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

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

NTP 122-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 123 Secure shell


Purpose
Secure Shell (SSH) is a protocol that provides authentication, encryption, and data integrity to secure network communications. On top of this protocol, Secure Shell implementations offer secure replacements for rsh, rlogin, rcp, ftp, and telnet, all of which transmit data over the network as clear text. The Secure Shell protocol consists of several subprotocols:

SSH Transport Protocol This subprotocol is responsible for setting up the secure channel that can be used by the other SSH subprotocols. The SSH transport protocol handles secure key exchange, server authentication, encryption, replay, and integrity protection. It runs on top of any reliable transport protocol (for example, TCP). SSH User Authentication Protocol This subprotocol provides client-side user authentication. It runs on top of the SSH Transport protocol. SSH Connection Protocol This subprotocol provides interactive login sessions and forwarded TCP connections.

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 123-1

NTP 123 Secure shell

NTP 123-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 124 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 100. Restore the system configuration; see RTP 101. Retrieve the remote inventory; see RTP 102. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 124-1

NTP 124 Maintain the system

NTP 124-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 125 Add an IPoA cross-connect user


Purpose
An Inter-Working Layer (IWL) is created on a PVC that is configured in RFC2684 LLC-SNAP routed or RFC 2684 VC-MUX routed encapsulation modes. Only one C-VLAN or SC-VLAN is configured in cross-connect mode. This VLAN must then be associated with a bridge port, which is created on the same PVC as the IWL. This procedure provides the steps to add an IPoA Cross-Connect User on the NE.

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

The LT must be planned; see DLP 111. xDSL profiles must have been created; see DLP 129.

Procedure
Proceed as follows to add an IPoA cross-connect user: 1 2 3 Create a C-VLAN or SC-VLAN; see DLP 117 or DLP 119. Create an IPoA cross- connect user; see DLP 174. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 125-1

NTP 125 Add an IPoA cross-connect user

NTP 125-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 126 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 to all active CLI 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. The severity of the various application messages is predefined. It is reported as follows: Service Affecting alarm messages: EMERGENCY Authentication messages: ALERT Configuration change messages: NOTICE Other CLI/TL1 messages (admin, Show, retrieve): INFO protocol tracing: DEBUG videoCDR reporting: NOTICE

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 126-1

NTP 126 Manage system logging

See the 7302 ISAM | 7330 ISAM FTTN CLI Command Guide document for more information about CLI commands used to configure system logging. See the 7302 ISAM | 7330 ISAM FTTN System Description 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 179. Create, configure, and monitor system logs; see DLP 179. STOP. This procedure is complete.

NTP 126-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 127 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 deployed currently 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 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 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 108.

Procedure
Proceed as follows to configure SHDSL: 1 2 3 To configure SHDSL links; see DLP 182. To configure IMA on SHDSL links; see DLP 183. STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 127-1

NTP 127 Configure SHDSL

NTP 127-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 128 Manage an IPProxy CPE


Purpose
IPProxy CPE Management allows configuration, monitoring, maintenance and upgrade of ADSL Remote Terminals. These functions can be executed from a CPE Management Module (CPE-MM). The network reference model is illustrated in Figure NTP 128-1.
Figure NTP 128-1: Network Reference Model
Network Management Entity EMS CPE-MM

IP@/UDP IP@/TCP
RMI

IP@/UDP IP@/TCP
RMI

Telnet/ TCP/ IP/VLAN TFTP/UDP/ IP/ VLAN

User Management Entity NE Relay LMI xDSL CPE

Telnet/ IP/AAL5/ATM/DSL TFTP/ IP/AAL5/ATM/DSL

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 128-1

NTP 128 Manage an IPProxy CPE

For IPProxy CPE Management, the CPE must support both Telnet & TFTP server functions. The CPE-MM must support Telnet & TFTP client functions. The NE relays the Telnet and TFTP messages between the CPE-MM and the CPE.

The TFTP function is for the CPE firmware upgrade The Telnet function is for the configuration and operation of the 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

Two channels are present on the LMI interface:

Management channel Data channel

The management channel is used to carry CPE remote management information, to upload performance statistics, and to download CPE firmware. The protocol stack of the management channel is TELNET and TFTP over TCP/UDP/IP. The IP packets are RFC1483R encapsulated on AAL5/ATM over PVC (VPI = 1, VCI = 39). The protocol stack on the RMI is the same as for the NE management interface, that is, Telnet and TFTP over TCP/UDP/IP is supported.

Prerequisites
The following prerequisites must be fulfilled:

The CPE must have a Telnet and TFTP service on IPoA over ATM PVC 1,39 The CPE IP must be configured to be 192.168.1.1 for IPoA on ATM PVC 1,39

Procedure
To configure IPProxy CPE management, you need to perform the following tasks: 1 2 3 4 5 If not already done, enable the dual tagging mode in the SHub; see DLP 191 Configure the S-VLAN to be used for IPProxy CPE Management; see DLP 192 Enable the IPProxy CPE Management function; see DLP 193 Configure one or more IPProxy CPE Management sessions; see DLP 194 On the session configured, use Telnet or TFTP to the modem(s) to communicate using the connection (<CpeProxy::cpeIpProxySessionProtocolPort>) port allocated for the session. STOP. This procedure is complete.

NTP 128-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 129 Configure a loopback interface on the SHub


Purpose
Configure a loopback interface on the SHub.

Prerequisites
The following prerequisites 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 204. 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 129-1

NTP 129 Configure a loopback interface on the SHub

NTP 129-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

NTP 130 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
116.

Procedure
Proceed as follows to configure EFM OAM: 1 2 Configuration of EFM OAM; see DLP 205. After configuration, the following actions can be performed: a b c d 3 Viewing of Local and Remote (CPE) information; see DLP 205. Viewing of EFM OAM statistics; see DLP 205. Retrieve MAC counters; see DLP 205. Retrieve PME counters; see DLP 205.

STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

NTP 130-1

NTP 130 Link Related Ethernet OAM

NTP 130-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Detailed Level Procedures (DLP)

DLP 100 Set up a CLI session DLP 101 Create operator profiles and instances DLP 102 Configure dual IP address DLP 103 Configure system parameters DLP 104 Configure network interfaces DLP 105 Configure link aggregation usage DLP 106 Configure RSTP DLP 107 Configure OSPF DLP 108 Configure RIP DLP 109 Configure SNMP and trap management DLP 110 Manage alarms DLP 111 Plan, replan, and unplan equipment DLP 112 Lock and unlock equipment DLP 113 Configure the equipment DLP 114 Configure NT redundancy DLP 115 Create a layer2-terminated forwarder VLAN

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 116 Create a layer2-terminated router VLAN DLP 117 Create a C-VLAN DLP 118 Create an S-VLAN DLP 119 Create an SC-VLAN DLP 120 Create an iBridge VLAN DLP 121 Add network interfaces to a VLAN DLP 122 Create a forwarding VRF DLP 123 Create a router VRF DLP 124 Create an xDSL user DLP 125 Create an IPoA user DLP 126 Create an IPoE user DLP 127 Create a PPPoE user DLP 128 Add an LT port to a VLAN DLP 129 Create xDSL profiles DLP 130 Configure xDSL bonding DLP 131 Create an xDSL bonding group DLP 132 Configure filtering on SHub DLP 133 Configure QoS on layer 2 DLP 134 Configure QoS DLP 135 Configure a QoS-aware VLAN DLP 136 Configure multicast on the LT DLP 137 Configure IGMP proxy DLP 138 Configure IGMP snooping DLP 139 Configure DHCP relay agent in iBridge mode DLP 140 Configure DHCP relay agent in router mode DLP 141 Configure DHCP relay agent in forwarder mode DLP 142 Configure the security domain

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 143 Configure a PPP connection for local RADIUS authentication DLP 144 Configure RADIUS DLP 145 Configure 802.1x DLP 146 Configure PPPoE relay DLP 147 Configure PPPoX relay DLP 148 Enable the PPPoE server DLP 149 Configure PPPoE profiles DLP 150 Configure ARP table entry DLP 151 Shut down and restart the NT DLP 152 Reboot the system DLP 153 Shut down and restart individual equipment DLP 154 Create a snapshot alarm table DLP 155 Monitor alarms DLP 156 Management of the SHub database DLP 157 Manage the SHub database DLP 158 Manage the system database DLP 159 Manage OSWP DLP 160 View version of the SHub software DLP 161 View software licenses counters DLP 162 Modify the external management VLAN DLP 163 Modifying xDSL profiles DLP 164 Ping another host DLP 165 Perform a traceroute action DLP 166 Configure SNMP proxy CPE management DLP 167 Script files DLP 168 Modify the system management IP parameters DLP 169 Configure cluster management

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 170 Configure SSH DLP 171 Enable EMS management DLP 172 Create a default operator profile DLP 173 Switching a user from ADSL to VDSL DLP 174 Create an IPoA cross-connect user DLP 175 Configure single IP address DLP 176 Performance monitoring commands DLP 177 Configure SFP downlink ports DLP 178 Configure the default security domain DLP 179 Configure system logging DLP 180 Configure static MAC addresses DLP 181 Configure operator authentication via RADIUS DLP 182 Configure SHDSL links DLP 183 Configure IMA on SHDSL links DLP 184 Convert the NE IP address DLP 185 Configure ANCP session DLP 186 Configure DHCP MAC concentration in forwarder mode DLP 187 Configure global VLAN parameters DLP 188 Configure custom PSD points DLP 189 Configure VDSL2 virtual noise values DLP 190 Configure threshold crossing alerts DLP 191 Enable dual tagging in the SHub DLP 192 Configure IPProxy CPE management DLP 193 Enable IPProxy CPE management DLP 194 Configure IPProxy CPE management session DLP 195 Configure general bridge parameters DLP 196 Configure Voice SIP

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 197 View port configuration and operational data DLP 198 Configure multicast on the SHub DLP 199 Configure QoS on the SHub DLP 200 Configure MSTP DLP 201 Configure protocol tracing DLP 202 Configure QoS threshold crossing alerts DLP 203 Configure general security settings DLP 204 Configure an unnumbered IP interface on the SHub DLP 205 Configure Link Related Ethernet OAM DLP 206 Configure a DPBO profile DLP 207 Modify a DPBO profile DLP 208 Configure power back off DLP 209 Configure vMAC DLP 210 View the status of various system parameters

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 100 Set up a CLI session


Purpose
This procedure provides the steps to set up a CLI session with the NE.

Procedure
Proceed as follows to set up a CLI session: 1 Enter LOGIN to start up the command line interface. The logon prompt appears. 2 3 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. 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 1 For security purposes, change the default user name and password. The system will prompt you to do this when you log in for the first time. Note 2 For remote CLI, after you set up the management channel, you can set up a remote CLI session using Telnet.
4 STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 100-1

DLP 100 Set up a CLI session

DLP 100-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 101 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 101-1

DLP 101 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 after a password change.

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 No capitals may be used in the profile name.

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.

DLP 101-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 101 Create operator profiles and instances

STOP. This procedure is complete.

Configuration example:
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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 101-3

DLP 101 Create operator profiles and instances

DLP 101-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 102 Configure dual IP address


Purpose
This document describes the procedure to configure the system management IP parameters.

Security Considerations

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

It is NOT advised to use insecure management channels, such as dual IP address mode. It is advised to use secure management channels, such as single IP address mode. This implies closing the insecure management channels!

Procedure
Proceed as follows to configure the system management IP parameters: 1 By default, the system will start up in single IP address mode. You can set the mode to dual IP address (refer also to DLP 103, step 1) with the following command:
configure system id <Sys::systemId> no single-public-ip

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 102-1

DLP 102 Configure dual IP address

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 network port management (inband or outband) with the following command:
configure interface shub port (network-port) port-type <Sys::Type>
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 ===============================================================

DLP 102-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 102 Configure dual IP address

show interface shub port ================================================================ port table ================================================================ port admin-status oper-status speed type duplex ---------------------------------------------------------------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

----------------------------------------------------------------

Configure the SHub system IP group configuration with the following command:
configure system shub entry ip ip-cfg-mode <Sys::DefIpAddr>

Note Set the parameter <Sys::DefIpAddr> to:

dynamic in case of dynamic configuration (BOOTP) manual in case of manual configuration (default value)

Do one of the following:

In case of manual configuration, continue with step 6 In case of dynamic configuration, continue with step 9

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

Configure the SHub IP address as follows: i Set the adminstrative status of the OAM VLAN to down with the following command:
configure interface shub ip 4093 admin-status down

ii

Configure the SHub IP address with the following command:


configure interface shub ip 4093 ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 102-3

DLP 102 Configure dual IP address

iii

Set the adminstrative status of the OAM VLAN to up with the following command:
configure interface shub ip 4093 admin-status up

Configure the default route in the SHub with the following command:
configure ip shub vrf 0 route-dest 0.0.0.0/0 next-hop <gateway-ip-address> vlan-id 4093

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)

10

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

11

Configure the bridge port with the following command:


configure bridge shub port (network-port) pvid 4093

12

STOP. This procedure is complete.

Configuration example for dynamic configuration via BOOTP (for tagged network):
configure system id SystemID02 no single-public-ip configure system management host-ip-address bootp show transport ip-address configure interface shub port 7 port-type network configure system shub entry ip ip-cfg-mode dynamic configure vlan shub id 4093 egress-port network:7 configure bridge shub port 7 pvid 4093

DLP 102-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 102 Configure dual IP address

Configuration example for static configuration via manual configuration (for tagged network):
configure system id SystemID02 no single-public-ip configure system management host-ip-address manual:10.177.0.112/17 show transport ip-address configure interface shub port 7 port-type network show vlan global show interface shub port configure system shub entry ip ip-cfg-mode manual configure system management default-route 10.177.127.254 configure interface shub vlan-id 4093 admin-status down configure interface shub ip 4093 ip-addr 10.177.0.113/17 configure interface shub vlan-id 4093 admin-status up configure ip shub vrf 0 route-dest 0.0.0.0/0 next-hop 10.177.127.254 vlan-id 4093 configure vlan shub id 4093 egress-port network:7 configure bridge shub port 7 pvid 4093

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 102-5

DLP 102 Configure dual IP address

DLP 102-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 103 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 captions ().

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 <PrintableString-0-255> location <PrintableString-0-255> contact-person <PrintableString-0-255> (no) en-snmp-auth-trap <Transport::SnmpAuthTraps> (no) ether-shape-rate <Sys::etherShapeRate> mgnt-vlan-id <Vlan::VlanId> system-mac <Sys::MacAddr>/<Sys::MacAddr>/<Sys::Range> (no) single-public-ip (no) port-num-in-proto <Sys::PortNumberInprotocol>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 103-1

DLP 103 Configure system parameters

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 115. 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 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. 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>

Configure SNTP on the LT shelf 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 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.

DLP 103-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 103 Configure system parameters

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

STOP. This procedure is complete.

Configuration example:
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 clock-mgmt priority-scheme local configure error log-full-action wrap show sntp

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 103-3

DLP 103 Configure system parameters

DLP 103-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 104 Configure network interfaces


Note
This procedure is redundant and has been incorporated in DLP 175 and DLP 102 from Release 3.1 on.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 104-1

DLP 104 Configure network interfaces

DLP 104-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 105 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 ECNT-A: an aggregation can exist of maximum 7 component links. For ECNT-C, NANT-A: an aggregation can exist of maximum 8 component links. Subtending links: For an FE type link or a GE type link, an aggregation can exist of maximum 7 component links

Note Link aggregation cannot be used for user links.

This document describes the procedure to configure the link aggregation usage.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 105-1

DLP 105 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 port number within the group, provided the operational state of the link is UP. 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. 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 prerequisites 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> (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

DLP 105-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 105 Configure link aggregation usage

Note This command is only necessary if the Link Aggregation system was shut down manually. By default, Link Aggregation is enabled.

If necessary, use the following command to disable Link Aggregation:


configure la disable-lacp

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:
configure interface shub port [1...2] port-type subtending configure la aggregator-port [1...2] aggregatable name testsub lacp-mode enable-lacp active-lacp actor-key 1234 link-up-down-trap configure la no disable-lacp show la aggregator-info [1...2] show la network-port-info [1...2]

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 105-3

DLP 105 Configure link aggregation usage

DLP 105-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 106 Configure RSTP


Note
This procedure is no longer valid and is replaced by DLP 200 from R3.3/FGN 3.4 on.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 106-1

DLP 106 Configure RSTP

DLP 106-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 107 Configure OSPF


Purpose
This procedure provides the steps to configure Open Shortest Path First (OSPF) management 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 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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 107-1

DLP 107 Configure OSPF

Procedure
Proceed as follows to configure OSPF management: 1 Configure the OSPF parameters and attributes 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) passive-interface

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

DLP 107-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 107 Configure OSPF

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>

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) aggregate-addr (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) extern-aggr-addr (dest-ip) (no) advertise <Ospf::ExtAggregateEffect>

Configure the OSPF stub area parameters: i Configure the OSPF stub area with the following command:
configure ospf stub-area (area-id) (no) metric-type <Ospf::MetricType> (no) metric <Ospf::StubMetric> (no) summary]

ii

Configure the OSPF stub area interface with the following command:
configure ospf stub-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 stub area interface timers with the following command:
configure ospf stub-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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 107-3

DLP 107 Configure OSPF

(no) poll-interval <Ospf::PollIntvl>

iv

When MD5 is selected as authentication mode for an OSPF stub area interface, use the following command to configure the MD5 key:
configure ospf stub-area (area-id) interface (ip-addr) md5-key (index) key <Ospf::AuthTypeMd5> (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 stub area interface with the following command:
configure ospf stub-area (area-id) interface (ip-addr) (no) metric value <Ospf::Metric>

vii

Configure an OSPF stub aggregate with the following command:


configure ospf stub-area (area-id) aggregate-addr (dest-ip) (no) omit-advertise

Configure the OSPF NSSA area parameters with the following command: i Configure the OSPF NSSA area with the following command:
configure ospf nssa-area (area-id) (no) summary (no) translation <Ospf::Trnsltn> (no) trans-itvl <Ospf::TrnltnIntvl> (no) asbr-rtr-trans (no) metric-type <Ospf::NSSAMetricType>]

ii

Configure the OSPF NSSA area interface with the following command:
configure ospf nssa-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 NSSA area interface timers with the following command:
configure ospf nssa-area (area-id) interface (ip-addr) timers (no) transit-delay <Ospf::TransDelay> (no) retransmit-itvl <Ospf::RetransIntvl>

DLP 107-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 107 Configure OSPF

(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 NSSA area interface, use the following command to configure the MD5 key:
configure ospf nssa-area (area-id) interface (ip-addr) md5-key (index) key <Ospf::AuthTypeMd5> (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 NSSA area interface with the following command:
configure ospf nssa-area (area-id) interface (ip-addr) (no) metric value <Ospf::Metric>

vii

Configure an OSPF NSSA aggregate with the following command:


configure ospf nssa-area (area-id) aggregate-addr (dest-ip) lsa-type <Ospf::LSAType> (no) omit-advertise

viii Configure an OSPF NSSA aggregate from external autonomous systems with the following command:
configure ospf nssa-area (area-id) extern-aggr-addr (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

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 107-5

DLP 107 Configure OSPF

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.

Configuration example:
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

DLP 107-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 107 Configure OSPF

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 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 107-7

DLP 107 Configure OSPF

DLP 107-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 108 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.

Procedure
Proceed as follows to configure RIP management: 1 Configure the maximum number of peers that can be simultaneously in conversation with the RIP2 with the following command:
configure rip max-peer <Rip::Rip2Peer>

Configure RIP distribution with the following command:


configure rip redistribution (no) enable (no) default-metric <Rip::RouteMetric> (no) local (no) static (no) ospf

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 108-1

DLP 108 Configure RIP

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


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

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>

If the MD5 authentication method is selected for a RIP interface (see step 5), then the MD5 key can be configured with the following command: i Configure the MD5 key wit 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 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.

DLP 108-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 108 Configure RIP

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>

Add or delete a route aggregation with the following command:


configure rip (no) aggregation (ip-addr)

Define a route map with the following command:


configure rip route-map (vlan-id) sub-index <Rip::SubIndex> ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) direction <Rip::RouteMapDirection> (no) deny

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.

Configuration example:
configure rip max-peer 20 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 route-age-out 180 junk-collection 120 configure rip interface 192.168.80.39 md5-key 4 key plain:AlcatelTest expires 2147483647 starts 0 configure rip interface 192.168.80.39 authentication md5 configure rip redistribution enable static ospf configure rip route-map 70 sub-index 1 ip-addr 192.168.145.1/32

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 108-3

DLP 108 Configure RIP

no deny show rip statistics show rip peer show rip routing-table show rip global

DLP 108-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 109 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.

Note SNMPv3 is supported by default. SNMPv2 messages can be processed.

Trap management
An SNMP manager will receive traps when an event occurs in the system.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 109-1

DLP 109 Configure SNMP and trap management

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). 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 insecure 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 109-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 109 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 | 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

10

Configure community names on the SHub with the following command:


configure system security snmp shub community (index) name <PrintableString-0-255> (no) privilege <Snmp::SHubCommunityPrivilege> (no) ip-addr <Ip::V4Address>

11

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 109-3

DLP 109 Configure SNMP and trap management

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

link-up-trap auth-fail-trap change-trap init-started-trap lic-key-chg-occr topology-chg alarm-chg-trap phys-line-trap eqpt-change-trap success-set-trap other-alarm-trap warning-trap minor-trap major-trap critical-trap redundancy-trap eqpt-prot-trap craft-login-trap restart-trap max-per-window <Trap::WindowCount> window-size <Trap::WindowSize> max-queue-size <Trap::QueueSize> min-interval <Trap::Interval> min-severity <Alarm::alarmSeverity>

12

Configure an SNMP manager of the SHub with the following command:


configure trap shub manager <Ip::V4Address> : <Trap::Port> (no) cold-start-trap (no) auth-fail-trap (no) change-trap (no) community-string <PrintableString-0-255> (no) snmp-version <Snmp::SHubVersion> (no) min-severity <Snmp::SHubAlarmSeverity>

Note This command can only be used if the system mode is dual IP address. See DLP 184 for the procedure to convert the system mode.

13

Configure the trap definition table with the following command:


configure trap definition (name) priority <Trap::Priority>

14

If necessary, reset the trap table with the following command:


admin trap manager <Ip::V4Address> : <Trap::Port> reset-trap-buffer

15

STOP. This procedure is complete.

DLP 109-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 109 Configure SNMP and trap management

Configuration example: Example for SNMPv1 or SNMPv2:


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 shub community 3 name NETMAN privilege read-write ip-addr 10.176.8.8 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

Example for SNMPv3:


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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 109-5

DLP 109 Configure SNMP and trap management

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 shub community 3 name NETMAN privilege read-write ip-addr 10.176.8.8 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 109-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 110 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 155.

Prerequisite
The following prerequisite must be fullfilled:

The board must have been planned; see DLP 111.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 110-1

DLP 110 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

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-up (no) link-updown-trap (no) user <Itf::asamIfExtCustomerId> (no) severity <Itf::asamIfExtAlmReportingSeverity>

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

DLP 110-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 110 Manage alarms

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.

Configuration example:
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 no-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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 110-3

DLP 110 Manage alarms

DLP 110-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 111 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. For example, no extention subrack for XD equipment. 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 106 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 115 for more information on slot numbering schemes.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 111-1

DLP 111 Plan, replan, and unplan equipment

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> unlock (no) lock (no) extended-lt-slots (no) description <Description-127>

Note The parameter extended-lt-slots is only applicable for Flexible Density (FD) subracks. For more information on FD subracks, see the Product Information.
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) unlock (no) alarm-profile <Equipm::AlarmProf> capab-profile <Equipm::CapabilityProfile>

Note 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

DLP 111-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 111 Plan, replan, and unplan equipment

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 iont:<Eqpt::RackId>/<Eqpt::ShelfId> planned-type <Equipm::BoardType>

ii

Plan the remote subrack with the following command:


configure equipment shelf <Eqpt::RackId>/<Eqpt::ShelfId> planned-type <Equipm::ShelfType>

iii

Configure the SFP downlink port to the remote LT (and SHub VLAN) with the following command:
configure equipment external-link-assign (sfp-index) remote <Eqpt::ExpRack>/<Eqpt::ExpShelf>/<Eqpt::ExpSlot>

Note The range for the parameter sfp-index depends on the NT board type, see TNG 106 subsection SFP port mapping for more information.
iv Plan the remote LT with the following command:
configure equipment slot <Eqpt::ExpRack>/<Eqpt::ExpShelf>/<Eqpt::ExpSlot> 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 (sfp-index) no remote

ii

Unplan the remote LT with the following command:


configure equipment slot acu:<Eqpt::RackId>/<Eqpt::ShelfId> planned-type not-planned

iii

Unplan the remote subrack with the following command:


configure equipment shelf <Eqpt::RackId>/<Eqpt::ShelfId> planned-type not-planned

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 111-3

DLP 111 Plan, replan, and unplan equipment

View the slot status with the following command:


show equipment slot

STOP. This procedure is complete.

Configuration example for planning a subrack:


configure equipment shelf 1/1 description "***Mainshelf***" configure equipment slot 1/1/1 planned-type aacu-c configure equipment slot nt-b planned-type ecnt-c configure equipment applique iont:1/1 planned-type ecnc-a configure equipment slot lt:1/1/4 planned-type evlt-c configure equipment slot lt:1/1/5 planned-type eblt-c configure equipment slot lt:1/1/6 planned-type polt-b configure equipment slot lt:1/1/7 planned-type eblt-k configure equipment slot lt:1/1/8 planned-type eblt-k configure equipment slot 1/1/9 planned-type smlt-k info configure equipment slot flat show equipment slot

Configuration example for planning a remote subrack:


configure equipment slot acu:1/1 planned-type genc-e configure equipment shelf 3/1 planned-type rems-a configure equipment external-link-assign 10 remote 3/1/4 configure equipment slot 3/1/4 planned-type rvlt-a

Configuration example for unplanning a remote subrack:


configure equipment slot 3/1/4 planned-type not-planned configure equipment external-link-assign 10 no remote configure equipment shelf 3/1 planned-type not-planned configure equipment slot acu:1/1 planned-type not-planned

DLP 111-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 111 Plan, replan, and unplan equipment

Configuration example for planning multiple remote subracks:


configure equipment applique iont:1/1 planned-type ncnc-c configure equipment shelf 3/2 planned-type rems-a configure equipment shelf 3/3 planned-type rems-a configure equipment shelf 3/4 planned-type rems-a configure equipment external-link-assign 3 remote 3/2/1 configure equipment external-link-assign 4 remote 3/3/1 configure equipment external-link-assign 5 remote 3/4/1 configure equipment slot 3/2/1 planned-type rvlt-a configure equipment slot 3/3/1 planned-type rvlt-a configure equipment slot 3/4/1 planned-type rvlt-a

Configuration example for unplanning multiple remote subracks:


configure equipment external-link-assign 3 no remote configure equipment external-link-assign 4 no remote configure equipment external-link-assign 5 no remote configure equipment slot 3/2/1 planned-type not-planned configure equipment slot 3/3/1 planned-type not-planned configure equipment slot 3/4/1 planned-type not-planned configure equipment shelf 3/2 planned-type not-planned configure equipment shelf 3/3 planned-type not-planned configure equipment shelf 3/4 planned-type not-planned

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 111-5

DLP 111 Plan, replan, and unplan equipment

DLP 111-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 112 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:
configure equipment slot 1/1/5 no unlock configure equipment slot 1/1/5 unlock

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 112-1

DLP 112 Lock and unlock equipment

DLP 112-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 113 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 Commands and Messages document 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 <Eqpt::Rack> (no) description <Description>

Configure the subrack or shelf with the following command:


configure equipment shelf (index) class <Equipm::ShelfClass> (no) planned-type (no) unlock (no) extended-lt-slots (no) description <Description-127>

Enable or disable environment monitoring with the following command:


configure equipment envbox (no) enable-supervise

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 113-1

DLP 113 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:
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 1/1/5 detail show equipment applique 1/1/2 detail

DLP 113-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 114 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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 114-1

DLP 114 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 unlocked (that is, NT redundancy is enabled).
If NT redundancy is not required, then NT redundancy must be specifically disabled to avoid missing redundancy alarms. Use the following command:
configure equipment protection-group 1 admin-status lock

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 seconds (= 1000)

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>

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 (network-port) (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 (network-port) admin-status up

DLP 114-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 114 Configure NT redundancy

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

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 114-3

DLP 114 Configure NT redundancy

Configuration example:
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] 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 114-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 115 Create a layer2-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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 115-1

DLP 115 Create a layer2-terminated forwarder VLAN

Figure DLP 115-1: Layer2-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 Layer2-terminated forwarder VLAN.

Prerequisites
The following prerequisites must be fulfilled before a Layer2-terminated forwarder VLAN can be configured:

A forwarder VRF; see DLP 122.

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 Layer2-terminated forwarder VLAN: 1 Create a Layer2-terminated VLAN on the NT with the following command:
configure vlan id <Vlan::UVlanIndex> (no) name <Vlan::AdminString> mode layer2-terminated (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) no circuit-id <Vlan::CircuitId> (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding

DLP 115-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 115 Create a layer2-terminated forwarder VLAN

(no) aging-time <Vlan::MacAgingTime>

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

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> /<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 network:<Shub::NetworkPort>

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 115-3

DLP 115 Create a layer2-terminated forwarder VLAN

Configure the broadcast VLAN with the following command:


configure dhcp-relay agent (vrfid) bcast-vlan <Dhcp::VlanId>

STOP. This procedure is complete.

Configuration example:
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:7 configure vlan shub id 101 egress-port lt:1/1/[4...19] configure dhcp-relay agent 16 bcast-vlan l2-vlan:101

DLP 115-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 116 Create a layer2-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 LANX 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 116-1

DLP 116 Create a layer2-terminated router VLAN

Figure DLP 116-1: Layer2-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 Layer2-terminated router VLAN.

Prerequisites
The following prerequisites must be fulfilled before a Layer2-terminated router VLAN can be configured:

A router VRF; see DLP 123.

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.

DLP 116-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 116 Create a layer2-terminated router VLAN

Procedure
Proceed as follows to configure a Layer2-terminated router VLAN: 1 Create a virtual Layer2-terminated VLAN on the LT with the following command:
configure vlan id <Vlan::UVlanIndex> (no) name <Vlan::AdminString> mode layer2-terminated (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) no circuit-id <Vlan::CircuitId> (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

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

Add the virtual VLAN to the LT port where the Layer2-terminated router is active with the following command:
configure vlan shub id (vlanid) egress-port lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId>

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

Create a L2 network terminated VLAN on the Shub with the following command:
configure vlan shub id (vlanid)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 116-3

DLP 116 Create a layer2-terminated router VLAN

(no) name <Vlan::AdminString> mode layer2-term-nwport (no) mac-move-allow

Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half port-type network-port (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 network:<Shub::NetworkPort>

12

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

13

Configure the port VLAN ID for the untagged packets with the following command:
configure bridge shub port <Shub::NetworkPort> 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

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

DLP 116-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 116 Create a layer2-terminated router VLAN

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.

Configuration example (for tagged network): Note: In the configuration example, it is assumed that the index of the router VRF of the LT is 5 and the index of the router VRF on the SHub is 15.
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...9] 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 7 mode automatic port-type network configure interface shub port 7 admin-status up configure vlan shub id 1450 egress-port network:7 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 116-5

DLP 116 Create a layer2-terminated router VLAN

DLP 116-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 117 Create a C-VLAN


Purpose
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 support the configuration of DHCP Option 82 and PPPoE relay. This procedure provides the steps to configure a Customer VLAN (C-VLAN).

Prerequisite
The following prerequisite must be fulfilled before a C-VLAN can be configured:

The board must have been planned; see DLP 111. xDSL profiles must have been created; see DLP 129.

Procedure
Proceed as follows to configure a C-VLAN: 1 Create a C-VLAN: i 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 117-1

DLP 117 Create a C-VLAN

(no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>

ii

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


configure vlan id <Vlan::UVlanIndex> (no) name <Vlan::AdminString> mode <Vlan::SystemMode> (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) no circuit-id <Vlan::CircuitId> (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

iii

Create a C-VLAN on the SHub with the following command:


configure vlan shub id <Vlan::UVlanIndex> name <Vlan::AdminString> mode cross-connect

Create and configure an SHub network port: i Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half port-type network (no) mc-flooding admin-status up

ii

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

iii

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>

STOP. This procedure is complete.

DLP 117-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 117 Create a C-VLAN

Configuration example:
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 shub id 300 name "ISP_C_VLAN_300" mode cross-connect configure interface shub port 7 port-type network admin-status up configure vlan shub id 300 egress-port network:7 configure vlan shub id 300 egress-port lt:1/1/5

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 117-3

DLP 117 Create a C-VLAN

DLP 117-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 118 Create an S-VLAN


Purpose
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. This procedure provides the steps to configure an S-VLAN.

Prerequisite
The following prerequisite must be fulfilled before an S-VLAN can be configured:

The board must have been planned; see DLP 111. xDSL profiles must have been created; see DLP 129.

Procedure
Proceed as follows to configure an S-VLAN: 1 Create an S-VLAN: i 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 118-1

DLP 118 Create an S-VLAN

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

priority <Vlan::Priority> broadcast-frames protocol-filter <Vlan::ProtGroup> pppoe-relay pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>

ii

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


configure vlan id <Vlan::UVlanIndex> (no) name <Vlan::AdminString> mode <Vlan::SystemMode> (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) no circuit-id <Vlan::CircuitId> (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

iii

Create and configure an SHub network port with the following command:
configure vlan shub id <Vlan::UVlanIndex> name <Vlan::AdminString> mode cross-connect

Create and configure an SHub network port: i Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half port-type network (no) mc-flooding admin-status up

ii

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

iii

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>

DLP 118-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 118 Create an S-VLAN

STOP. This procedure is complete.

Configuration example:
configure vlan id stacked:400:0 name IPS_S_VLAN-400 mode cross-connect configure vlan shub id 400 name ISP_S_VLAN-400 mode cross-connect configure interface shub port 7 port-type network admin-status up configure vlan shub id 400 egress-port network:7 configure vlan shub id 400 egress-port lt:1/1/5

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 118-3

DLP 118 Create an S-VLAN

DLP 118-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 119 Create an SC-VLAN


Purpose
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. This procedure provides the steps to configure or delete a stacked VLAN.

Prerequisite
The following prerequisite must be fulfilled before an SC-VLAN can be configured:

The board must have been planned; see DLP 111. xDSL profiles must have been created; see DLP 129.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 119-1

DLP 119 Create an SC-VLAN

Procedure
Proceed as follows to configure an SC-VLAN: 1 Create an SC-VLAN: i 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 (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>

ii

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


configure vlan id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex> (no) priority <Vlan::Priority> (no) vmac-translation (no) vmac-dnstr-filter (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) no circuit-id <Vlan::CircuitId> (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

iii

Create a stacked SC-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>

iv

Create an cross-connect VLAN on the SHub with the following command:


configure vlan shub id <Vlan::UVlanIndex> name <Vlan::AdminString> mode cross-connect

DLP 119-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 119 Create an SC-VLAN

Create and configure an SHub network port: i Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half port-type network-port (no) mc-flooding admin-status up

ii

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

iii

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>

STOP. This procedure is complete.

Configuration example:
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 configure vlan shub id 500 name ISP_SC_VLAN-500 mode cross-connect configure interface shub port 7 port-type network admin-status up configure vlan shub id 500 egress-port network:7 configure vlan shub id 500 egress-port lt:1/1/5

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 119-3

DLP 119 Create an SC-VLAN

DLP 119-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 120 Create 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 NSP.

Note The NE supports up to 128 iBridges.

This procedure provides the steps to create or delete an iBridge VLAN.

Procedure
Proceed as follows to configure an iBridge VLAN: 1 Create an iBridge VLAN 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 (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 120-1

DLP 120 Create an iBridge VLAN

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


configure vlan id <Vlan::UVlanIndex> (no) priority <Vlan::Priority> (no) broadcast-frames (no) protocol-filter <Vlan::ProtGroup> (no) pppoe-relay (no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1> (no) dhcp-opt-82 (no) no circuit-id <Vlan::CircuitId> (no) circuit-id-dhcp <Vlan::CircuitIdDhcp> (no) remote-id <Vlan::RemoteId> (no) remote-id-dhcp <Vlan::RemoteIdDhcp> (no) dhcp-linerate <Vlan::Dhcp-linerate> (no) pppoe-linerate <Vlan::Pppoe-linerate> (no) circuit-id-pppoe <Vlan::CircuitIdPppoe> (no) remote-id-pppoe <Vlan::RemoteIdPppoe> (no) secure-forwarding (no) aging-time <Vlan::MacAgingTime>

Create an iBridge VLAN on the SHub with the following command:


configure vlan shub id <Vlan::UVlanIndex> name <Vlan::AdminString> mode residential-bridge

STOP. This procedure is complete.

Configuration examples:
configure vlan id 56 name vlan56 mode residential-bridge configure vlan id 100 name iBridge-vlan mode residential-bridge configure vlan id 100 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan shub id 100 name iBridge-vlan mode residential-bridge configure vlan id 200 name MC-vlan mode residential-bridge configure vlan id 200 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan shub id 200 name MC-vlan mode residential-bridge

DLP 120-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 121 Add network interfaces to a VLAN


Purpose
This procedure provides the steps to add network interface(s) (that is, network port(s)) to a VLAN.

Prerequisite
The following prerequisite must be fulfilled before network interfaces can be added to a VLAN:

A VLAN must have been created; see DLP 117, DLP 118, DLP 119 or DLP 120.

Procedure
Proceed as follows to add a network interface to a VLAN: 1 Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half (no) port-type <Sys::Type> (no) mc-flooding

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

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 121-1

DLP 121 Add network interfaces to a VLAN

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

Configure the port VLAN ID for the untagged packets with the following command:
configure bridge shub port <Shub::NetworkPort> pvid <Vlan::VlanOamIndex>

STOP. This procedure is complete.

Configuration example:
configure interface shub port 3 mode automatic port-type network configure interface shub port 3 admin-status auto-up configure vlan shub id 100 egress-port network:3 configure vlan shub id 100 egress-port lt:1/1/[4...7] configure vlan shub id 100 untag-port network:3 configure vlan shub id 200 egress-port network:7 configure vlan shub id 200 egress-port lt:1/1/[4...9] configure bridge shub port 3 pvid 100

DLP 121-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 122 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. This procedure provides the steps to configure a Virtual Routing Forwarding (VRF) context in forwarding mode on the NT.

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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 122-1

DLP 122 Create a forwarding VRF

STOP. This procedure is complete.

Configuration example:
configure ip vrf 16 name forwardingvrf16 mode forwarder

DLP 122-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 123 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.

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

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 123-1

DLP 123 Create a router VRF

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:
configure ip vrf 5 name routervrf5 mode router configure ip shub vrf 15 name routervrf15 fast-path-mode:ena-user-user-com

DLP 123-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 124 Create an xDSL user


Purpose
This procedure provides the steps to create an xDSL user.

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 betwene 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 explicitely.

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

The LT must be planned; see DLP 111. The xDSL profiles must have been created; see DLP 129. An VLAN must have been created: for creation of a cross-connect VLAN; see NTP 104 for creation of an iBridge VLAN; see NTP 105.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 124-1

DLP 124 Create an xDSL user

Procedure
Proceed as follows to create an xDSL 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-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-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-up bonding-mode <Xdsl::BondingMode> (no) 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 or VDSL 2 service is required.
2 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-updown-trap (no) user <Itf::asamIfExtCustomerId> (no) severity <Itf::asamIfExtAlmReportingSeverity>

DLP 124-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 124 Create an xDSL user

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 5.

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

For each of the created PVCs, 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) accept-frame-type <Vlan::VlanFrameTypes> (no) qos-profile <Vlan::QosProfileName> (no) prio-regen-prof <Vlan::PrioRegenProfile>

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

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 124-3

DLP 124 Create an xDSL user

STOP. This procedure is complete.

Configuration examples: 1. For an ADSL user:


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 configure bridge port 1/1/5/12:8:35 vlan-id 200 configure bridge port 1/1/5/12:8:35 pvid 200

2. For a VDSL or VDSL2 user:


configure xdsl line 1/1/4/12 service-profile 7 spectrum-profile 4 admin-up configure bridge port 1/1/4/12 configure bridge port 1/1/4/12 vlan-id 200 configure bridge port 1/1/4/12 pvid 200

DLP 124-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 125 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 111. xDSL profiles must have been created; see DLP 129. An IP-aware bridge (see NTP 106) or an IP router (see NTP 107) 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-am

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 125-1

DLP 125 Create an IPoA user

(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-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-up bonding-mode <Xdsl::BondingMode> (no) 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>

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

DLP 125-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 125 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 This command must be repeated for each IP address assigned to that particular user.

STOP. This procedure is complete.

Configuration example:
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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 125-3

DLP 125 Create an IPoA user

DLP 125-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 126 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 111. xDSL profiles must have been created; see DLP 129. An IP-aware bridge (see NTP 106) or an IP router (see NTP 107) must have been created.

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 126-1

DLP 126 Create an IPoE user

(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-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-up bonding-mode <Xdsl::BondingMode> (no) 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 or VDSL 2 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 | 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 126-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 126 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>

STOP. This procedure is complete.

Configuration examples: 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 configure bridge port 1/1/5/14:8:35 configure ip vrf 16 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 7 spectrum-profile 4 admin-up configure bridge port 1/1/4/14 configure ip vrf 16 user-itf bridgeport 1/1/4/14

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 126-3

DLP 126 Create an IPoE user

DLP 126-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 127 Create a PPPoE user


Purpose
This procedure provides the steps to create a PPPoE user.

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

The LT must be planned; see DLP 111. xDSL profiles must have been created; see DLP 129. An IP-aware bridge (see NTP 106) or an IP router (see NTP 107) must have been created. A PPP profile must have been created; see DLP 149. The PPP server must be enabled; see DLP 148.

Procedure
Proceed as follows to create a PPPoE 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 127-1

DLP 127 Create a PPPoE user

(no) g992-3-l1 (no) g992-3-l2 (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-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-up bonding-mode <Xdsl::BondingMode> (no) 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 or VDSL 2 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 5.

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

Create a bridge port with the following command:


configure bridge port (port) max-unicast-mac <Vlan::MaxMac>

Create a user PPPoX interface with the following command:


configure pppoe pppox-interface (port) (no) max-num-session <PPPoE::MaxNumSessions> (no) ppp-profile-name <AsamProfileName>

STOP. This procedure is complete.

DLP 127-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 127 Create a PPPoE user

Configuration examples: 1. For an ADSL user:


configure xdsl line 1/1/5/15 service-profile 7 spectrum-profile 5 transfer-mode atm admin-up configure interface port xdsl-line:1/1/5/15 user TestUser1 configure atm pvc 1/1/5/15:8:35 aal5-encap-type llc-snap configure bridge port 1/1/5/15:8:35 max-unicast-mac 4 configure pppoe pppox-interface 1/1/5/15:8:35 max-num-session 16 ppp-profile-name PPPProf1

2. For a VDSL or VDSL 2 user:


configure xdsl line 1/1/4/15 service-profile 7 spectrum-profile 4 admin-up configure interface port xdsl-line:1/1/4/15 user TestUser2 configure bridge port 1/1/4/15 max-unicast-mac 4 configure pppoe pppox-interface 1/1/4/15 max-num-session 16 ppp-profile-name PPPProf1

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 127-3

DLP 127 Create a PPPoE user

DLP 127-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 128 Add an LT port to a VLAN


Purpose
This procedure provides the steps to add an LT port to a VLAN.

Procedure
Proceed as follows to add an LT to the correct VLAN service: 1 Configure an LT port on the SHub with the following command:
configure vlan shub id (vlanid) egress-port lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot>

STOP. This procedure is complete.

Configuration example:
configure vlan shub id 200 egress-port lt:1/1/4

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 128-1

DLP 128 Add an LT port to a VLAN

DLP 128-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 129 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 129-1 describes the two types of profiles.
Table DLP 129-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 more information on power management mode, SRA,... See TNG 113 for a full description of the multi-ADSL related parameters and TNG 107 for a full description of the VDSL related parameters.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 129-1

DLP 129 Create xDSL profiles

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> (scope) 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 136.

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 163).

DLP 129-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 129 Create xDSL profiles

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 129-3

DLP 129 Create xDSL profiles

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>

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

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

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

DLP 129-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 129 Create xDSL profiles

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) 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) rx-psd-shape-up <Xdsl::RxVdslPsdShapeUp> (no) ghstones-pwr-mode <Xdsl::GhsTonesTxPwr> (no) max-band <Xdsl::VdslMaxBandNum> (no) max-freq <Xdsl::VdslMaxFrequency> (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) cust-psd-sc-down <Xdsl::PsdScaleBit> (no) cust-psd-ty-down <Xdsl::PsdTypeBit> (no) cust-rx-psd-sc-up <Xdsl::PsdScaleBit> (no) cust-rx-psd-ty-up <Xdsl::PsdTypeBit>

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 129-5

DLP 129 Create xDSL profiles

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

cust-psd-sc-down <Xdsl::PsdScaleBit> cust-psd-ty-down <Xdsl::PsdTypeBit> cust-psd-sc-up <Xdsl::PsdScaleBit> cust-psd-ty-up <Xdsl::PsdTypeBit> cust-rx-psd-sc-up <Xdsl::PsdScaleBit> cust-rx-psd-ty-up <Xdsl::PsdTypeBit>

11

Activate an xDSL spectrum profile with the following command:


configure xdsl spectrum-profile (index) active

12

STOP. This procedure is complete.

Configuration example:
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 129-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 130 Configure xDSL bonding


Purpose
xDSL bonding allows to carry the traffic 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 Provision 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 PTM/VDSL lines) Multi-LT line bonding (for ATM/ADSL lines)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 130-1

DLP 130 Configure xDSL bonding

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

The LT must be planned; see DLP 111. The xDSL profiles must have been created; see DLP 129. A cross-connect VLAN (see NTP 104), an iBridge VLAN (see NTP 105), an IP-aware bridge (see NTP 106) or an IP router (see NTP 107) must have been configured.

Procedure
Proceed as follows to create an xDSL bonding group profile: 1 Configure the xDSL lines to be bonded: a For ADSL lines, use the following command:
configure xdsl line (if-index) bonding-mode atm-bonding

For VDSL lines, use the following command:


configure xdsl line (if-index) bonding-mode native

Note 1 The following applies for 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

Note 2 The following applies for 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 124, DLP 125, DLP 126 or DLP 127 for the configuration procedure.

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> (no) max-delay-up <Xdsl::InterleavingDelay> (no) imp-noise-prot-dn <Xdsl::SignedIntegerSYMBOL> (no) imp-noise-prot-up <Xdsl::SignedIntegerSYMBOL> (no) active

DLP 130-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 130 Configure xDSL bonding

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.
3 Configure an xDSL bonding group with the following command:
configure xdsl-bonding group (bonding-group-idx) group-profile none | <Xdsl::GroupProfileIndexWithRemove> | name:<PrintableString> (no) admin-up

Do one of the following: a b In case of odd-even adjacent line bonding; go to step 7. In case of multi-LT line bonding; go to step 5.

Provison the bonding group (which consists of adding/removing links to/from the bonding group) with the following command:
configure xdsl-bonding group (bonding-group-idx) link (bonding-link-id)

Activate the xDSL bonding group with the following command:


configure xdsl-bonding group (if-index) admin-up

Configure the bonding group assembly timeout with the following command:
configure xdsl-bonding group-assembly-time <SignedInteger>

Note The default value is 0, and is interpreted as disabling the timer.

STOP. This procedure is complete.

Configuration example:
configure xdsl-bonding group-assembly-time 0 configure xdsl-bonding group-profile 1 name XBOND_0_0 local-profile version 1 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 min-bitrate-down 0 plan-bitrate-down 0 max-bitrate-down 0 max-delay-down 16

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 130-3

DLP 130 Configure xDSL bonding

imp-noise-prot-dn 0 configure xdsl-bonding group-profile 1 active configure xdsl-bonding group-profile 2 name GroupProfile1 local-profile version 1 configure xdsl-bonding group-profile 2 min-bitrate-up 800 plan-bitrate-up 1500 max-bitrate-up 2200 max-delay-up 16 imp-noise-prot-up 0 configure xdsl-bonding group-profile 2 min-bitrate-down 10000 plan-bitrate-down 20000 max-bitrate-down 40000 max-delay-down 16 imp-noise-prot-dn 0 configure xdsl-bonding group-profile 2 active configure xdsl line 1/1/8/47 service-profile name:XSRVC_0_0 spectrum-profile 5 bonding-mode atm-bonding admin-up configure xdsl line 1/1/8/48 service-profile name:XSRVC_0_0 spectrum-profile 5 bonding-mode atm-bonding admin-up configure xdsl-bonding group 1/1/8/47 group-profile name:GroupProfile1 up configure xdsl line 1/1/7/21 service-profile name:XSRVC_0_0 spectrum-profile 5 bonding-mode atm-bonding admin-up configure xdsl line 1/1/8/25 service-profile name:XSRVC_0_0 spectrum-profile 5 bonding-mode atm-bonding admin-up configure xdsl-bonding group 1/1/7/21 group-profile 2 no up configure xdsl-bonding group 1/1/7/21 link 1/1/8/25 configure xdsl-bonding group 1/1/7/21 up

DLP 130-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 131 Create an xDSL bonding group


Note
This procedure is no longer valid. The correct procedure for configuring xDSL bonding is described in DLP 130.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 131-1

DLP 131 Create an xDSL bonding group

DLP 131-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 132 Configure filtering on SHub


Purpose
This procedure provides the steps to configure filtering on the SHub. 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.

Creating a filter for a specific set of streams


Proceed as follows to create a filter that lets a specific set of streams through, but blocks all other traffic: 1 2 Create filters on the SHub that let certain streams with specific MAC addresses pass through Create one filter that blocks all the traffic (see Note after step 1).

Note The behaviour of the filters depends on the type of NT board:

For ECNT-C and NANT-A; the filters are ORed. For ECNT-A: the filters are overruled in order of creation. The filter that was created as first gets the highest priority.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 132-1

DLP 132 Configure filtering on SHub

Procedure
Proceed as follows to configure filtering on the SHub: 1 Configure the SHub MAC filter with the following command:
configure transport shub mac-filter (index-num) (no) in-port (port)

Note This command allows traffic from an LT to be filtered, but not from an individual DSL port.

To limit the filter to only the traffic coming from one specific port, use 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

Note 1 The MAC filter by default applies to any incoming SHub port, either network or LT. To apply the filter only to specific ports, use the command in step 2 to configure the incoming ports. Note 2 To configure a filter which will filter and drop all upstream straffic irrespective of the MAC source address, use the following command
configure transport shub mac-filter (index-num) filter 00:00:00:00:00:00-any vlan-id <Sys::FilterVlanId> action-drop

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

DLP 132-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 132 Configure filtering on SHub

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)

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

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)

DLP 132-3

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 132 Configure filtering on SHub

12

Configure an IP filter, for protocols other than ICMP, TCP or UDP, on the SHub with the following command:
configure system shub filter ip-filter port-filter (filter-rule) (no) protocol <Sys::RestrictedProtocol> (no) action-drop (no) dst-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) src-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull> (no) direction <Sys::Direction> (no) vlan-id <Vlan::VlanFilterIndex>

13

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.
14 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::OutPort> (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.
15 STOP. This procedure is complete.

DLP 132-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 132 Configure filtering on SHub

Configuration example:
configure transport shub mac-filter [450...451] in-port lt:1/1/4 configure transport shub mac-infilter 450 protocol-type 2222 filter any-56:0d:9d:47:dd:aa vlan-id 100 action-drop configure transport shub mac-infilter 451 protocol-type 2222 filter any-56:0d:9d:47:dd:bb vlan-id 100 action-drop configure system shub filter ip-filter icmp 12 action-drop 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 action-drop 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 action-drop 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 action-drop src-ip-addr 192.168.0.1/16

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 132-5

DLP 132 Configure filtering on SHub

DLP 132-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 133 Configure QoS on layer 2


Note
This procedure is no longer valid. Refer to DLP 134 for the configuration procedure.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 133-1

DLP 133 Configure QoS on layer 2

DLP 133-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 134 Configure QoS


Purpose
This procedure provides the steps to configure QoS.

Note For more information about QoS and the configuration of QoS, refer to TNG 101.

Procedure
Proceed as follows to configure QoS: 1 Configure general QoS parameters (if necessary): i Configure the ATM overhead factor 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>

iii

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 134-1

DLP 134 Configure QoS

Configure the QoS policer profiles with the following command:


configure qos profiles policer (name) committed-info-rate <Qos::InfoRate> committed-burst-size <Qos::CommittedBurstSize>

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 101.
3 Create one of the following marker profiles: 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

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

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

DLP 134-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 134 Configure QoS

Configure a scheduler profile with the following command:


configure qos profiles scheduler (name) wfq-q1-weight <Qos::WfqQ1Weight>

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>

Use one of the following commands to configure a filter which can be used to build policy actions based on filtering criteria, use one of the following commands: 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>

Configure QoS policy actions, 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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 134-3

DLP 134 Configure QoS

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

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>

12

Attach the created scheduler profile (see step 4) and CAC profile (see step 5) to: a a DSL port with the following command:
configure qos dsl-port (index) scheduler-profile <Qos::ProfileName> cac-profile <Qos::ProfileName>

an SHDSL interface with the following command:


configure qos shdsl-port (index) scheduler-profile <Qos::ProfileName> cac-profile <Qos::ProfileName>

an Ethernet link with the following command:


configure qos interface eth-itf (index) scheduler-profile <Qos::ProfileName> cac-profile <Qos::ProfileName>

DLP 134-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 134 Configure QoS

13

Attach the created queue profile (see step 6) to: a a DSL port with the following command:
configure qos dsl-port (index) queue (queue) queue-profile <Qos::QosProfileName>

an SHDSL interface with the following command:


configure qos shdsl-port (index) queue (queue) queue-profile <Qos::QosProfileName>

an Ethernet link with the following command:


configure qos interface eth-itf (index) queue (queue) queue-profile <Qos::QosProfileName>

14

STOP. This procedure is complete.

Configuration example:
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 configure qos profiles policy pcyDnVoice policy-action name:apVoice no precedence filter l3-name:f3pDsVoiceIp configure qos profiles policy pcyUpVod policy-action name:apVod

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 134-5

DLP 134 Configure QoS

filter l3-name:l3pUsVodIp configure qos profiles policy pcyDnVod policy-action name:apVod filter l3-name:l3pDsVodIp

DLP 134-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 135 Configure a QoS-aware VLAN


Purpose
The QoS-aware VLAN cross-connect is not a new cross-connect mode on its own, but it adds the possibility to support PVC-bundles as subscriber interfaces.

Note The QoS-aware VLAN cross-connect mode can be applied to all other VLAN cross-connect modes defined above, i.e. C-VLAN, S-VLAN and S-VLAN/C-VLAN cross-connects. In the last case, the cross-connect will consider the p-bits of the S-VLAN, the C-VLAN p-bits remaining transparent.
In the downstream direction, the egress bridge port is found by means of the combination of VLAN tag and p-bit. The p-bits are hence only used for a routing decision. There are no additional QoS requirements besides the generic QoS-handling available from the 'regular' cross-connect or residential bridging. This procedure provides the steps to configure a QoS-aware VLAN.

Prerequisites
The following prerequisites must be fulfilled before a QoS-aware VLAN can be configured:

The board must have been planned; see DLP 111. xDSL profiles must have been created; see DLP 129. A QoS policer profile must have been created A QoS session profile must have been created A QoS profile must have been created

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 135-1

DLP 135 Configure a QoS-aware VLAN

Procedure
Proceed as follows to configure a QoS-aware VLAN: 1 Create a QoS-aware VLAN: i Create a QoS-aware VLAN on the LT with the following command:
configure vlan id <Vlan::UVlanIndex> name <Vlan::AdminString> mode qos-aware (no) priority <Vlan::Priority>

ii

Create a C-VLAN on the SHub with the following command:


configure vlan shub id <Vlan::UVlanIndex> name <Vlan::AdminString> mode cross-connect

Create and configure an SHub network port: i Create and configure an SHub network port with the following command:
configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half port-type network (no) mc-flooding

ii

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

iii

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

iv

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>

3 4

Create an xDSL user; see DLP 124. STOP. This procedure is complete.

DLP 135-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 135 Configure a QoS-aware VLAN

Configuration example:
configure vlan id 350 name ISP_C_VLAN-350 mode qos-aware configure vlan shub id 350 name ISP_C_VLAN-350 mode cross-connect configure interface shub port 7 port-type network admin-status up configure vlan shub id 350 egress-port network:7 configure vlan shub id 350 egress-port lt:1/1/5 configure xdsl line 1/1/5/4 service-profile 7 spectrum-profile 5 admin-up configure atm pvc 1/1/5/4:8:35 aal5-encap-type llc-snap configure atm pvc 1/1/5/4:8:36 aal5-encap-type llc-snap configure bridge port 1/1/5/4:8:35 configure bridge port 1/1/5/4:8:35 vlan-id 350 prior-ctrl-load prior-less-100ms prior-less-10ms prior-nw-ctrl configure bridge port 1/1/5/4:8:36 configure bridge port 1/1/5/4:8:36 vlan-id 350 prior-best-effort prior-background prior-spare prior-exc-effort configure bridge port 1/1/5/4:8:35 pvid 350 default-priority 5 configure bridge port 1/1/5/4:8:36 pvid 350 prio-regen-prof cl-all-prio-3

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 135-3

DLP 135 Configure a QoS-aware VLAN

DLP 135-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 136 Configure multicast on the LT


Purpose
This procedure provides the steps to configure multicast on the LT (general parameters, capacity and source table) on the NE.

Procedure
Proceed as follows to configure multicast on the LT: 1 Configure the general multicast parameters with the following command:
configure mcast general (no) package-member <Igmp::Pkg> (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 129. Note 2 The parameter pkg-memb-bitmap is kept for backward compatibility with previous releases.
2 Configure the multicast capacity parameters 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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 136-1

DLP 136 Configure multicast on the LT

Configure the multicast source with the following command:


configure mcast src (class-d-addr) (no) dis-fast-change (no) pkg-mem-bitmap <Igmp::PkgMemBitMap> (no) name <Igmp::multicastSrcName> (no) guaranteed-serv (no) atm-peak-bit-rate <Igmp::McastSrcAtmPeakBitRate> (no) eth-peak-bit-rate <Igmp::McastSrcEtherPeakBitRate> (no) atm-sus-bit-rate <Igmp::McastSrcAtmSustainBitRate> (no) eth-sus-bit-rate <Igmp::McastSrcEtherSustainBitRate> vlan-id <Igmp::McastSrcVLANID> (no) service-name <Igmp::multicastSrcServiceName> (no) preview-duration <Igmp::multicastSrcMaxPreDuration> (no) preview-number <Igmp::multicastSrcMaxPreNumber> (no) preview-blackout <Igmp::multicastSrcPreBlackout>

Note 1 The parameter pkg-memb-bitmap is kept for backward compatibility with previous releases. Note 2 The parameters atm-peak-bit-rate and atm-sus-bit-rate are obsolete and are replaced by eth-peak-bit-rate and eth-sus-bit-rate respectively.
4 Configure the multicast source package members with the following command:
configure mcast src (class-d-addr) (no) packagemember (package)

STOP. This procedure is complete.

Configuration example:
configure mcast general package-member 50 configure mcast general max-bitrate 5000 mean-bit-rate 1000 configure mcast capacity max-num-group 128 max-num-uncfg 20 configure mcast src 224.1.1.10 eth-peak-bit-rate 5000 eth-sus-bit-rate 3000 vlan-id 100 configure mcast src 224.1.1.10 packagemember 50

DLP 136-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 137 Configure IGMP proxy


Purpose
This procedure provides the steps to configure IGMP proxy on the LT.

Procedure
Proceed as follows to configure proxy on the LT: 1 Configure the IGMP source channel parameters with the following command:
configure igmp channel (port) (no) perm-pkg-bitmap <Igmp::PkgMemBitMap> (no) max-num-group <Igmp::ChannelMaxNumGroup> cac-disable | cac ip-anti-spoof-dis | ip-anti-spoof (no) igmp-version <Igmp::UserItfVersion>

Note The parameter perm-pkg-bitmap is kept for backward compatibility with previous releases.

Configure the IGMP channel permission package members with the following command:
configure igmp channel (port) (no) fullview-packages (package)

Configure the IGMP channel preview package members with the following command:
configure igmp channel (port) (no) preview-packages (package)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 137-1

DLP 137 Configure IGMP proxy

Configure the package bitmaps. The package is intended primarily for use by a network element manager, such as AWS, 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. Use the following command:
configure igmp package (index) (no) name <PrintableString-0-32> (no) template-name <PrintableString-0-32> template-version <Igmp::igmpPackageTemplateVersion>

Configure the IGMP parameters on a per-VLAN basis with the following command:
configure igmp vlan (vlan-id) netw-igmp-version <Igmp::VlanV3ProcessStatus> (no) v3-max-num-rec <Igmp::V3MaxNumRecordReport>

Note The IGMP system may not be started when the IGMP version is configured. If the system has been started, then it must first be stopped before the IGMP version can be configured. Use the following command:
configure igmp system no start

After configuration, the IGMP system must be started again with the command
configure igmp system start

Configure the IGMP system parameters with the following command:


configure igmp system 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>

DLP 137-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 137 Configure IGMP proxy

Note 1 The networkside 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.
7 Configure the IGMP system system Call Detail Record (CDR) 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

STOP. This procedure is complete.

Configuration example:
configure igmp channel 1/1/5/14:8:35 max-num-group 2 configure igmp channel 1/1/5/14:8:35 fullview-packages 20 configure igmp channel 1/1/5/14:8:35 preview-packages 49 configure igmp package 20 name IGMPpack20 template-version 1 configure igmp system no start configure igmp vlan 200 netw-igmp-version 2 configure igmp system start configure igmp system src-ip-address 192.168.100.100 start cdr-generation

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 137-3

DLP 137 Configure IGMP proxy

DLP 137-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 138 Configure IGMP snooping


Purpose
This procedure provides the steps to configure IGMP snooping on the SHub.

Procedure
Proceed as follows to configure IGMP snooping on the SHub: 1 Configure the IGS system parameters 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> (no) max-mcast-learn <Igmp::MaxMulticastLearn> (no) glb-leave <Igmp::GlobalLeaveMessageStatus> (no) reduced-resp-int <Igmp::ReducedResponseInterval> (no) remove-root-int <Igmp::RemoveRootTimer>

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 router port with the following command:


configure igmp shub vlan-router-port (vlan-id) network-port <Shub::NetworkPort>

View the status of the IGMP VLAN router ports with the following command:
show igmp shub vlan-router-port (vlan-id) network-port <Shub::NetworkPort>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 138-1

DLP 138 Configure IGMP snooping

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> (no) v3-max-num-rec <Igmp::VlanMaxV3AllowedGrps> (no) drop-rpt-network <Igmp::ReportAcptOnAllPorts> (no) robustness <Igmp::VlanRobustnessVar> (no) unsolicit-rpt-int <Igmp::VlanUnsolicitedReportInterval> (no) retry-count <Igmp::VlanRetryCount>

Note 1 The IGMP version configured at the SHub must be the same as the networkside IGMP version. Note 2 If the IGMP version needs to be changed, then the snoop filter must first be enabled with the command
configure igmp shub vlan-filter (filter-id) snoop-filter

After configuration, the snoop filter must be disabled again wit hthe command
configure igmp shub vlan-filter (filter-id) no snoop-filter

Configure the IGMP Connection Admission Control (CAC) bundle with the following command:
configure igmp shub bundle (bundle) (no) bandwidth <Igmp::BundleBandWidth> (no) max-num-channel <Igmp::BundleMaxChannel>

STOP. This procedure is complete.

DLP 138-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 138 Configure IGMP snooping

Configuration example:
configure igmp shub igs-system start-snooping enable-snooping self-ip-addr-mode configure self-ip-addr 192.168.100.100 configure igmp shub response-timer 500 leave-rsp-timer 3 configure igmp shub vlan-router-port 500 network-port 3 show igmp shub vlan-router-port 500 network-port 3 configure igmp shub vlan-filter 500 snoop-filter configure igmp shub vlan-filter 500 igmp-version 2 configure igmp shub vlan-filter 500 no snoop-filter configure igmp shub bundle MyBundle bandwidth 5000 max-num-channel 10

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 138-3

DLP 138 Configure IGMP snooping

DLP 138-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 139 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 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.

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 120.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 139-1

DLP 139 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>

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 server (index) ip-addr <Ip::V4Address> server-name <PrintableString-0-32>

DLP 139-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 139 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 agent (vrfid) (no) enable-relaying (no) secs-threshold <Dhcp::SecsThreshold> (no) hops-threshold <Dhcp::HopThreshold> (no) context-lifetime <Dhcp::ContextLife> (no) agent-ip-addr <Ip::V4Address>

STOP. This procedure is complete.

Configuration example:
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 server 10 ip-addr 192.168.100.13 server-name DHCPRell0 configure dhcp-relay shub agent 10 enable-relaying agent-ip-addr 192.168.100.2

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 139-3

DLP 139 Configure DHCP relay agent in iBridge mode

DLP 139-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 140 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 116.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 140-1

DLP 140 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 Server to a particular VRF with the following command:
configure dhcp-relay shub server (index) ip-addr <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 agent (index) (no) enable-relaying (no) secs-threshold <Dhcp::SecsThreshold> (no) hops-threshold <Dhcp::HopThreshold> (no) context-lifetime <Dhcp::ContextLife> agent-ip-addr <Ip::V4Address>

STOP. This procedure is complete.

Configuration example:
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 server 15 ip-addr 10.178.14.66 server-name Antwerp15 configure dhcp-relay shub agent 15 enable-relaying agent-ip-addr 10.178.14.97

DLP 140-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 141 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 141-1

DLP 141 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>

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 server (vrfid) ip-addr<Ip::V4Address> server-name <PrintableString-0-32>

Configure the DHCP relay agent parameters to the VRF with the following command:
configure dhcp-relay shub agent (vrfid) (no) enable-relaying (no) secs-threshold <Dhcp::SecsThreshold> (no) hops-threshold <Dhcp::HopThreshold> (no) context-lifetime <Dhcp::ContextLife> agent-ip-addr <Ip::V4Address>

STOP. This procedure is complete.

DLP 141-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 141 Configure DHCP relay agent in forwarder mode

Configuration example:
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 server 17 ip-addr 192.168.116.13 server-name Antwerp17 configure dhcp-relay shub agent 17 enable-relaying agent-ip-addr 192.168.116.2

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 141-3

DLP 141 Configure DHCP relay agent in forwarder mode

DLP 141-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 142 Configure the security domain


Purpose
This procedure provides the steps to configure the security domain.

Procedure
Proceed as follows to configure the security domain: 1 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 local | radius:<Aaa::RadPolicyName> (no) admin-down

Define the security domain IP pool with the following command:


configure system security ip-addr-pool (name) vrf-index <Aaa::IpVrfIndex> start-addr <Ip::V4Address>/<Ip::PrefixLength> (no) size <Aaa::IpAddressPoolSize> (no) admin-down

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 142-1

DLP 142 Configure the security domain

Assign the security domain IP pool with the following command:


configure system security domain (name) ip-pool (name) vrf-index <Aaa::VrfIndex> priority <SignedInteger>

STOP. This procedure is complete.

Configuration example:
configure system security domain Domain1 vrf-index 16 vlan-id 56 authenticator local configure system security ip-addr-pool PoolDomain1 vrf-index 16 start-addr 10.179.16.100/24 size 100 no admin-down configure system security domain Domain1 ip-pool PoolDomain1 vrf-index 16 priority 3

DLP 142-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 143 Configure a PPP connection for local RADIUS authentication


Purpose
This procedure provides the steps to configure a PPP connection for local RADIUS authentication. The procedure entails:

Defining a security domain IP pool Assigning users to that security domain. A conceptual table lists the configurable parameters for a user of a particular domain. This table is used for authenticating users locally.

Note If a security domain is deleted, all the users of that security domain are deleted from the table.

Prerequisite
The following prerequisite must be fulfilled before a PPP connection for local RADIUS authentication can be configured:

A VRF must have been created.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 143-1

DLP 143 Configure a PPP connection for local RADIUS authentication

Procedure
Proceed as follows to configure a PPP connection for local RADIUS authentication: 1 Configure the security domain with the following command:
configure system security domain (name) vrf-index <Aaa::DomainVrfIndex> authenticator local

Define the domain users with the following command:


configure system security domain (name) user (name) password <Password>

If required, the password for a specific user can be changed with the following command:
configure system security domain (name) user (name) password <new Password>

If required, a user can be deleted from the authentication table with the following command:
configure system security domain (name) no user (name)

STOP. This procedure is complete.

Configuration example:
configure system security domain Domain1 vrf-index 16 authenticator local configure system security domain Domain1 user JohnDoe password zxspr12 configure system security domain Domain1 user JohnDoe password acdd35d configure system security domain Domain1 no user JohnDoe

DLP 143-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 144 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 144-1

DLP 144 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 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>

Enable the RADIUS relay on the SHub with the following command:
configure system security radius (no) relay (no) auth-super-user <Aaa::SuperUserAuth> oper-policy-name <Aaa::OperatorRadPolicyName>

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 144-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 144 Configure RADIUS

Configuration example:
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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 144-3

DLP 144 Configure RADIUS

DLP 144-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 145 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>

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>

Enable initialization control for a port with the following command:


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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 145-1

DLP 145 Configure 802.1x

STOP. This procedure is complete.

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

DLP 145-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 146 Configure PPPoE relay


Purpose
PPPoE relay needs no configuration. It should only be enabled or disabled on a specific VLAN.

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 146-1

DLP 146 Configure PPPoE relay

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 103, step 1. the port numbering method: configurable via the parameter port-num-inpro; see DLP 103, 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 117, DLP 118, DLP 119 or DLP 120.

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>

Disable PPPoE relay with the following command:


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

STOP. This procedure is complete.

Configuration example:
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

DLP 146-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 147 Configure PPPoX relay


Purpose
This procedure provides the steps to configure PPPoX relay.

Prerequisites
The following prerequisites must be fulfilled before PPPoX relay can be configured:

An iBridge VLAN must have been created; see NTP 105.

Procedure
Proceed as follows to configure PPPoX relay: 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) max-payload-tag <PPPoX::MaxPayLoadTag> (no) name <PPPoX::EngineName> (no) lock (no) service-name <PPPoX::EngineName>

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


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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 147-1

DLP 147 Configure PPPoX relay

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>

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.

Configuration example:
configure pppox-relay cross-connect global-session trans-max-age 250 cc-max-age 600 configure pppox-relay cross-connect engine 560 name PPPoXRelay560 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

DLP 147-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 148 Enable the PPPoE server


Purpose
This procedure provides the steps to create the PPPoE server and the state of the PPPoE server. By default, the PPPoE server is disabled.

Procedure
Proceed as follows to configure the PPPoE server: 1 Configure the PPPoE server with the following command:
configure pppoe server-name <PPPoE::ServerName> enable-server

STOP. This procedure is complete.

Configuration example:
configure pppoe server-name PPPoEServer1 enable-server

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 148-1

DLP 148 Enable the PPPoE server

DLP 148-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 149 Configure PPPoE profiles


Purpose
This procedure provides the steps to create and configure the PPPoE profiles.

Procedure
Proceed as follows to configure the PPPoE profiles: 1 Create and configure a PPPoE profile with the following command:
configure pppoe ppp-profile (index) (no) auth-type <PPPoE::pppProfileAuthenType> (no) keep-alive-intvl <PPPoE::ProfileKeepAliveInterval>

STOP. This procedure is complete.

Configuration example:
configure pppoe ppp-profile PPPProf1 auth-type chap-pap

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 149-1

DLP 149 Configure PPPoE profiles

DLP 149-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 150 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 117, DLP 118, DLP 119 or DLP 120.

Procedure
Use the following procedure to configure an ARP table entry: 1 Configure the IP Shub ARP parameters with the following command:
configure ip shub arp (no) cache-timeout <Ip::ArpCacheTimeOut> (no) cache-pending <Ip::ArpCachePendingTime> (no) cache-refresh <Ip::ArpCacheRefreshTime> (no) cache-retry-time <Ip::ArpCacheRetryTime> (no) max-retry-itvl <Ip::ArpCacheMaxRetryTime> (no) max-retries <Ip::ArpMaxRetries>

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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 150-1

DLP 150 Configure ARP table entry

Configuration example:
configure ip shub arp cache-timeout 10000 cache-pending 35 max-retries 5 configure ip shub arp vlan 4093 gratuitous-arp

DLP 150-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 151 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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 151-1

DLP 151 Shut down and restart the NT

Location of the flash disk on the NT board


The flash disk is located at the top of the board next to the top rear connector; see Figure DLP 151-1.
Figure DLP 151-1: Location of the flash disk on the NT board

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

DLP 151-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 151 Shut down and restart the NT

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

Pull out the NT board. Swap the flash disk from the old NT board with the new NT board (see Figure DLP 151-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. Send the old NT board back to Alcatel-Lucent. STOP. This procedure is complete.

Configuration example:
admin equipment prepare-sys-shutdown

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 151-3

DLP 151 Shut down and restart the NT

DLP 151-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 152 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

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

STOP. This procedure is complete.

Configuration example:
admin equipment reboot-isam with-self-test

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 152-1

DLP 152 Reboot the system

DLP 152-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 153 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.

Note This procedure is not valid for the Remote Expansion Module
(REM).

General
The only individual pieces of equipment that may be necessary to restart are plug-in units such as LTs. These can be shut down and restarted by powering down the slot in which the plug-in unit is inserted.

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 <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot> power-down

Restore power to a plug-in unit with the following command:


configure equipment slot <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot> no power-down

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 153-1

DLP 153 Shut down and restart individual equipment

STOP. This procedure is complete.

Configuration example:
configure equipment slot 1/1/5 power-down configure equipment slot 1/1/5 no power-down

DLP 153-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 154 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 or higher than the specified level, will be present in the table. This table is only temporary and exist only for 4 minutes. After the 4 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 154-1

DLP 154 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.

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

Note 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.

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>

The SHub alarm snapshot table can be viewed with the following command:
show alarm shub snap-shot table (index)

DLP 154-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 154 Create a snapshot alarm table

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: 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 SHub.
show alarm shub snap-shot table

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 154-3

DLP 154 Create a snapshot alarm 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 154-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 155 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 Commands and Messages 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 equipment | eqpt-holder | plug-in-unit | atm | ether-itf | sw-mgmt | xdsl misc | xdsl near-end | xdsl far-end | xdsl-tca | eo-conversion | authentication | bonding-group | ipox | redundancy | custom | sfp | llu-relay | custom-ext-alarm | plug-in-unit-ext | psc | sip-user-agent | sip-plugin-unit | sip-termination | shdsl | shdsl-isam | ima-group | ima-link | ether-tca | ether-sfp | qos-slot | qos-queue | filetransfer | l2forward | external-device (index)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 155-1

DLP 155 Monitor alarms

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 the general alarm log table with the following command:
show alarm current table

ii

View a specific alarm log table with the following command:


show alarm current equipment | eqpt-holder | plug-in-unit | atm | ether-itf | sw-mgmt | xdsl misc | xdsl near-end | xdsl far-end | xdsl-tca | eo-conversion | authentication | bonding-group | ipox | redundancy | custom | sfp | llu-relay | custom-ext-alarm | plug-in-unit-ext | psc | sip-user-agent | sip-plugin-unit | sip-termination | shdsl | shdsl-isam | ima-group | ima-link | ether-tca | ether-sfp | qos-slot | qos-queue | filetransfer | l2forward | external-device (index)

Note The detail mode can be used to obtain more detailed information on the alarm.

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)

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

DLP 155-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 155 Monitor alarms

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:
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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 155-3

DLP 155 Monitor alarms

DLP 155-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 156 Management of the SHub database


Note
This procedure is no longer valid. The correct procedure is described in RTP 100.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 156-1

DLP 156 Management of the SHub database

DLP 156-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 157 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:
show software-mngt shub config-file show system shub entry status

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 157-1

DLP 157 Manage the SHub database

DLP 157-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 158 Manage the system database


Note
This procedure is no longer valid. The correct procedure is described in RTP 100.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 158-1

DLP 158 Manage the system database

DLP 158-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 159 Manage OSWP


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

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> download-set <SwMngt::downloadSet> autofetch <SwMngt::autoFetch> activate manually | after-download

Note The parameters download-set and autofetch are obsolete parameters whose settings will be ignored by the system.

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 159-1

DLP 159 Manage OSWP

Start the actual OSWP download with the following command:


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

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

STOP. This procedure is complete.

Configuration example:
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

DLP 159-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 160 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:
show system shub entry version

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 160-1

DLP 160 View version of the SHub software

DLP 160-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 161 View software licenses counters


Description
The NE supports licensing counters. By these counters, the NE management station is able to license a set of features provided by the NE in its network. The licensing counters are defined at the level of the DSL interfaces.

Features
The feature counters can be retrieved by a manager for monitoring. The following features are monitored in the NE:

ADSL2+ READSL2 ADSL2/ADSL2+ Annex M IGMP IP-Forwarding PPPoX Relay PPPoX Termination 802.1x IPoA-CC Upstream Power Back-Off (UPBO policing)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 161-1

DLP 161 View software licenses counters

Procedure
Proceed as follows to retrieve the feature counters: 1 View the number of software licenses for the feature with the following command:
show system license adsl2-plus | readsl2 | igmp | ip-forward | pppox-relay | pppox-termination | 802dot1x | annex-m | ipoa-cc | upbo-policing

STOP. This procedure is complete.

Configuration example:
show system license

DLP 161-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 162 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

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) single-public-ip (no) port-num-inpro <Sys::PortNumberInprotocol>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 162-1

DLP 162 Modify the external management VLAN

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 network:<Shub::NetworkPort>

If the management traffic is untagged, do the following: i Configure the untag port and the PVID with the following commands:
configure vlan shub id (vlanid) untag-port network:<Shub::NetworkPort>

ii

Change the PVID on the management port with the following command:
configure bridge shub port (network-port) pvid <Vlan::VlanOamIndex>

Save the SHub database with the following command:


admin software-mngt shub database save

STOP. This procedure is complete.

Configuration example:
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

DLP 162-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 163 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 129.

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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 163-1

DLP 163 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)

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-am g992-5-a g992-5-b ansi-t1.424 dis-etsi-ts itu-g993-1 ieee-802.3ah 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>

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

DLP 163-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 163 Modifying xDSL profiles

STOP. This procedure is complete.

Configuration example:
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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 163-3

DLP 163 Modifying xDSL profiles

DLP 163-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 164 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>

STOP. This procedure is complete.

Configuration example:
ping 10.176.5.5 tries 3 ping 192.168.116.1 vrf 15 tries 3

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 164-1

DLP 164 Ping another host

DLP 164-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 165 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 1 The traceroute command can only be executed on systems operating in dual IP address mode, because this command runs on the SHub. On systems operating in single IP address mode, the command will not be accepted. Note 2 The following applies for traceroute actions:

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

Procedure
Proceed as follows to perform a traceroute action: 1 For a traceroute action: i Initiate the traceroute action with the following command:
traceroute (ip-addr) first-hop <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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 165-1

DLP 165 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

STOP. This procedure is complete.

Configuration example:
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 165-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 166 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

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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 166-1

DLP 166 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 managerwith the following command:
show cpe-management snmpproxy-statistics

STOP. This procedure is complete.

Configuration example:
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 configure cpe-management no proxy-mode

DLP 166-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 167 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 167-1

DLP 167 Script files

interface error system software-mngt transport qos vlan bridge la rstp ip igmp mcast pppox-relay pppoe dhcp-relay ospf rip cluster xdsl-bonding cpeproxy

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 7330 (via TFTP) using the following commands:
$ tftp <isam-ip-address> tftp> bin tftp> get /var/cmd/<file.txt>

DLP 167-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 167 Script files

Place a configuration file with a list of CLI commands on the 7330 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:
info configure | tee config info configure alarm flat | tee alaflat.cli exec /var/cmd/alaflat.cli

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 167-3

DLP 167 Script files

DLP 167-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 168 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 (see DLP 102 or DLP 175), 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>

Do one of the following: a b If the system is a single IP address system; go to step 12 If the system is a dual IP address system; go to step 5.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 168-1

DLP 168 Modify the system management IP parameters

Change the administrative status of the management vlan on the SHub to down with the following command:
configure interface shub vlan-id <Vlan::UVlanIndex> admin-status down

Optionally, remove the IP address connected to the management vlan on the SHub via the following command:
configure interface shub ip <Vlan::UVlanIndex> no ip-addr <Ip::V4Address>/<Ip::PrefixLengthHost>

Configure the new IP address to the management vlan on the SHub via the following command:
configure interface shub ip <Vlan::UVlanIndex> ip-addr <Ip::V4Address>/<Ip::PrefixLengthHost>

Change the administrative status of the management vlan on the SHub to up with the following command:
configure interface shub vlan-id <Vlan::UVlanIndex> admin-status up

Configure the default route in the SHub with the following command:
configure ip shub vrf 0 route-dest 0.0.0.0/0 next-hop <gateway-ip-address> vlan-id 4093

10

Save the changes on the NT disk with the following command:


admin software-mngt shub database save

11

To make the changes effective, the SHub must be restarted with the following command:
admin equipment reboot-shub systemreset

12

STOP. This procedure is complete.

Configuration example: 1. Configuration example for a single IP address system (IP address is assigned manually):
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 168-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 168 Modify the system management IP parameters

2. Configuration example for a dual IP address system (IP address is assigned manually:
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 configure interface shub vlan-id 4093 admin-status down configure interface shub ip 4093 ip-addr 192.168.204.148/24 configure interface shub vlan-id 4093 admin-status up configure ip shub vrf 0 route-dest 0.0.0.0/0 next-hop 192.168.204.1 vlan-id 4093 admin software-mngt shub database save admin equipment reboot-shub systemreset

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 168-3

DLP 168 Modify the system management IP parameters

DLP 168-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 169 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 environment. Each neighbor

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 169-1

DLP 169 Configure cluster management

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 169-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 169 Configure cluster management

Configure the neighbour discovery and topology collection on port level with the following command:
configure cluster port (port) (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:
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 7 discov-port-off show cluster counter show cluster neighbour show cluster device show cluster connect

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 169-3

DLP 169 Configure cluster management

DLP 169-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 170 Configure SSH


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

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

SSH can only be configured by the CLI security administrator. 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 101). 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 to 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. For SFTP: When the NE acts as an SFTP server, both password 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 170-1

DLP 170 Configure SSH

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:
configure system security ssh key-regen <SSH::RegenerateKey>

Configure the access channels (for example, disable the non-secure channels) with the following command:
configure system security ssh access (no) ftp <SSH::ChannelFTP> (no) protocol <SwMngt::Protocol> (no) cli <SSH::ChannelCLISSH> (no) tl1 <SSH::ChannelTL1SSH>

DLP 170-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 170 Configure SSH

Note The parameter ftp is obsolete and is replaced by the parameter


protocol.

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.
6 STOP. This procedure is complete.

Configuration example:
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 access cli telnet-ssh configure system security ssh sftp-user JohnDoe password plain:sshpsw01

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 170-3

DLP 170 Configure SSH

DLP 170-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 171 Enable EMS management


Purpose
This procedure provides the steps to enable the management of EMS:

Single IP address mode: via SNMPv3 via SNMPv1 Dual IP address mode: via SNMPv1

Procedure
Proceed as follows to enable the management of EMS: 1 Determine the task to perform and go to the appropriate step a b 2 To enable the management of EMS in single IP address mode, go to step 2. To enable the management of EMS in dual IP address mode, go to step 7.

Do one of the following: a b To enable EMS management via SNMPv3, go to step 3 To enable EMS management via SNMPv1, go to step 5

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 |

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 171-1

DLP 171 Enable EMS management

des:plain:<Sec::PlainPassword> | des : encrypted : <Snmp::PrivacyEncryptedKey> (no) public <Snmp::Identifier>

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>

4 5

Go to step 10. 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

6 7

Go to step 10. Configure the SNMP community name public with the following command:
configure system security snmp community public host-address <Ip::V4Address>/<Ip::PrefixLengthFull>

Configure the SHub management VLAN filter IP address with the following command:
configure system shub filter shub-manager (index) src-ip-addr <Ip::V4Address>
where <Ip::V4Address> is the IP address of the EMS

Configure the SHub security SNMP community with the following command:
configure system security snmp shub community (index) name <name> privilege read-write no ip-addr

10

STOP. This procedure is complete.

DLP 171-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 171 Enable EMS management

Configuration example: Configuration example for management via SNMPv3 for single IP address mode:
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:
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

Configuration example for dual IP address mode


configure system security snmp community public host-address 192.168.203.189/24 configure system shub filter shub-manager 1 src-ip-addr 10.176.8.8 configure system security snmp shub community 2 name PUBLIC privilege read-only configure system security snmp shub community 3 name NETMAN privilege read-write ip-addr 10.176.8.8

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 171-3

DLP 171 Enable EMS management

DLP 171-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 172 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> (no) transport <Sec::Transport> (no) vlan <Sec::Vlan> (no) xdsl <Sec::Xdsl> (no) security <Sec::Security> Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI DLP 172-1

DLP 172 Create a default operator profile

STOP. This procedure is complete.

Configuration example:
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 172-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 173 Switching 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 129. 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.

Create the new forwarding model. Refer to DLP 115 to DLP 127 for the correct procedure for the different modes.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 173-1

DLP 173 Switching a user from ADSL to VDSL

STOP. This procedure is complete.

Configuration example:
configure xdsl line 1/1/4/1 service-profile 7 spectrum-profile 5 transfer-mode ptm admin-up

DLP 173-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 174 Create an IPoA cross-connect user


Purpose
This procedure provides the steps to create an IPoA cross-connect user.

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

The LT must be planned; see DLP 111. xDSL profiles must have been created; see DLP 129.

Procedure
Proceed as follows to create an IPoA cross-connect user: 1 Create a cross-connect VLAN on the NT with the following command:
configure vlan id (vlanid) name <Vlan::AdminString> mode cross-connect

Create a cross-connect VLAN on the SHub with the following command:


configure vlan shub id (vlanid) name <Vlan::AdminString> mode cross-connect

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 174-1

DLP 174 Create an IPoA cross-connect user

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-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-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-up bonding-mode <Xdsl::BondingMode> (no) 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) admin-up aal5-encap-type llc-snap-routed

Create an IWL with the following command:


configure atm ip-cross-connect (interworking-port) cpe <Ip::V4Address> next-hop <Ip::V4Address>

DLP 174-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 174 Create an IPoA cross-connect user

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)

10

STOP. This procedure is complete.

Configuration example:
configure vlan id 2200 name ISP_C_VLAN mode cross-connect configure vlan shub id 2200 name ISP_C_VLAN mode cross-connect 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 atm ip-cross-connect 1/1/5/7:8:35 next-hop 192.168.150.1 cpe 192.168.150.2 configure bridge port 1/1/5/7:8:35 mac-learn-off configure bridge port 1/1/5/7:8:35 vlan-id 2200 configure bridge port 1/1/5/7:8:35 pvid 2200

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 174-3

DLP 174 Create an IPoA cross-connect user

DLP 174-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 175 Configure single IP address


Purpose
This document describes the procedure to configure the system management IP parameters.

Prerequisites
Communities must be configured on the SHub. The following commands give an example:

configure system security snmp shub community 1 name NETMAN privilege read-write ip-addr 127.0.0.2 configure system security snmp shub community 2 name PUBLIC

Procedure
Proceed as follows to configure the system management IP parameters: 1 Configure the system to use a single IP address with the following command:
configure system id <Sys::systemId> single-public-ip

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 175-1

DLP 175 Configure single IP address

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 automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half (no) port-type <Sys::Type> (no) admin-status <Shub::AdminStatus> (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 ===============================================================

DLP 175-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 175 Configure single IP address

show interface shub port ================================================================ port table ================================================================ port admin-status oper-status speed type duplex ---------------------------------------------------------------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 (network-port)

Configure the bridge port with the following command:


configure bridge shub port (network-port) pvid 4093

STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 175-3

DLP 175 Configure single IP address

Configuration example: Configuration example for dynamic configuration via BOOTP (for tagged network):
configure system id SystemID01 single-public-ip 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

Configuration example for static configuration via manual configuration (for tagged network):
configure system id SystemID02 single-public-ip 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 175-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 176 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 Commands and Messages. 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 show xdsl counters far-end line previous-1day (if-index) detail

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 176-1

DLP 176 Performance monitoring commands

Note The previous-1day counters are not available until 96 15-min intervals (that is, 24 hours) have passed.

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 command to show the bridge port counters:


show interface port bridge-port (port) detail

Use the following commands to show the link aggregation counters:


show la aggregator-info (port) show la aggregate-list (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 commands to show the PPPoE statistics:


show pppoe statistics-pppoe-itf tx-pkt (port) show pppoe statistics-pppoe-itf rx-pkt (port) show pppoe statistics-pppoe-itf stats (port) show pppoe ppp-statistics (port)

DLP 176-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 176 Performance monitoring commands

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)

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

10

Use the following command to show the IP forwarding statistics:


show ip vrf-statistics (vrf-id)

11

Use the following command to show the VRF net-to-media statistics:


show ip vrf-media (slot:vrf) [ip-address <Ip::V4Address>]

12

Use the following command to show the IP SHub ARP Statistics per VRF forwarding statistics:
show ip shub arp-stats (vrf-id)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 176-3

DLP 176 Performance monitoring commands

13

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 109.
14 Use the following command to show SHub DHCP relay agent statistics per VRF forwarding instance:
show dhcp-relay shub vrf-agent-stats (vrf)

15

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 109.
16 Use the following commands to show the PPoX 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)

17

Use the following commands to show the RADIUS statistics:


show security radius auth-server auth-stats (name) vrf-index

DLP 176-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 176 Performance monitoring commands

<Aaa::VrfIndex> show security radius acc-server acc-stats (name) vrf-index <Aaa::VrfIndex>

18

Use the following command to show the EAPOL statistics:


show security pae eapol-stats (port)

19

Use the following command to show the statistics related to the SNMP protocol:
show transport snmp protocol-stats

20

Use the following command to show the MAU statistics:


show transport ether-ifmau (if-index) index <Transport::Index>

21

Use the following command to show the SHub L2 information:


show transport shub mac (index-num)

22

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>

23

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-interval (if-index) unit-id <Shdsl::UnitId>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 176-5

DLP 176 Performance monitoring commands

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-interval (if-index) unit-id <Shdsl::UnitId> side <Shdsl::SegmentSide> wire-pair <Shdsl::SegmentTerminationWirePair> int-no <Shdsl::IntervalNumber> 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>

24

Use the following command to show the statistics related to CPE management:
show cpe-management snmpproxy-statistics (address) show cpe-management ipproxy-statistics (dslport)

25

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)

26

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)

DLP 176-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 176 Performance monitoring commands

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>

27

STOP. This procedure is complete.

Configuration example:
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 pppoe statistics-pppoe-itf tx-pkt show pppoe statistics-pppoe-itf rx-pkt show pppoe statistics-pppoe-itf stats

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 176-7

DLP 176 Performance monitoring commands

show pppoe ppp-statistics show qos statistics buffer-overflow total 1/1/4 show igmp channel counter show ip vrf-statistics show ip shub arp show dhcp-relay port 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 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

DLP 176-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 176 Performance monitoring commands

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 cpe-management snmpproxy-statistics show cpe-management ipproxy-statistics show vlan port-curr-15min-stats 1/1/5/4:8:35 show vlan port-curr-day-stats 1/1/5/4:8:35 show vlan port-15min-stats 1/1/5/4:8:35 interval-number 2 show vlan port-prev-day-stats 1/1/5/4:8:35 interval-number 2 show vlan current-15min-stats 200 port 1/1/5/4:8:35] show vlan current-day-stats 200 port 1/1/5/4:8:35 show vlan previous-15min-stats 200 port 1/1/5/4:8:35 interval-number 2 show vlan vlan-day-stats (vlanid) 200 port 1/1/5/4:8:35 interval-number 2

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 176-9

DLP 176 Performance monitoring commands

DLP 176-10

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 177 Configure SFP downlink ports


Purpose
This DLP provides the steps to configure rack, shelf, and slot IDs for SFP downlink ports on:

a GENC-E or GENC-F board installed in a 7330 ISAM FTTN ARAM-D host shelf. a NCNC-B, NCNC-C, NCNC-D or NCNC-E board installed in a 7330 FD ISAM shelf

General
Downlink SFP ports on the boards mentioned above are configurable using CLI. You can set the rack, shelf, and slot ID for each downlink port. 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 the REM derive their rack and shelf IDs from the SFP port. For an overview of the downlink port assignments on the faceplate of the GENC-x and NCNC-x boards, see TNG 106 - SFP port mapping. 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 SE, a REM or a SEM is 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 of the SFP port on a SEM or a REM to which a host shelf SFP is connected the slot number is slot 4 for SEM and slot 1 for REM (using legacy based numbering) or slot 1 for SEM (using position-based or type-based numbering) up to four shelves are supported in a rack

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 177-1

DLP 177 Configure SFP downlink ports

The following conditions apply specifically to the ES:

you are required to configure the rack, shelf, and slot ID of the SFP port on an ES to which a host shelf SFP is connected for an ES LT to come into service, the rack/shelf/slot configured against the GENC-x SFP port must match the installed rack/shelf/slot of the connected ES LT (where the far-end SFPs are on the EDSE-A faceplate). The ES ARAM-D shelf jumpers are used to set the ES installed rack and shelf information. the slot number is the LT slot on the ES 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 GENC-E or GENC-F board, or between expansion ports on the EDSE-A board, after the remote expansion unit is configured. Service disruptions will result and an alarm is raised.
If the rack and shelf assignment for a downlink port is already configured using CLI and you connect a remote LT unit from an ES that has a different rack and shelf jumper setting, an alarm is raised and the remote LT unit does not come in to service. If you connect a remote LT unit from an ES to a downlink port after a SEM or a REM unit was previously connected and commissioned, an alarm is raised and the remote LT unit does not come in to service. Do not change shelf and rack ID assignments using CLI 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. See 7302 ISAM Product Information or 7330 ISAM FTTN Product Information for more information about expansion configurations and configurable SFP ports. See TNG 106 for more information about rack and shelf assignments for remote expansion units.

Prerequisite
The subrack associated with the remote LT needs to be planned first, either the operator can explicitly plan the subrack (see DLP 111, step 3) or, for ARAM-D, it can be auto-planned by the system upon detection.

DLP 177-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 177 Configure SFP downlink ports

Procedure
Proceed as follows to configure the rack, shelf, and rack IDs of the SFP port on a SE or a REM or a SEM for a SFP port on GENC-x or NCNC-x board 1 Do one of the following:

For configuring an SFP downlink port on a GENC-x board, go to step 2 For configuring an SFP downlink port on a NCNC-x board, go to step 8

Configure the link direction (i.e. downlink) of the two configurable external-links on the host expansion board with the following command:
configure equipment external-link-host (SFP index 6 or 7) (no) direction <Equipm::ExternalLinkConfigType>

Configure the association between a host shelf SFP and a remote LT with the following command:
configure equipment external-link-assign (SFP index 6-17) (no) remote <Equipm::ExpansionSlotIndex>

View the traffic direction of the configurable ports with the following command:
info configure equipment external-link-host (SFP index 6 or 7)

View actual rack, shelf, and slot settings of the connected remote LT unit with the following command:
show equipment external-link-host (SFP index 6-17) detail

Troubleshoot a problem with an GigE optical link between a SEM, REM, or FD-REM, and its host shelf with the following command:
show equipment diagnostics sfp [position] detail

Note The rules for troubleshooting a problem with an GigE optical link
are:

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.

7 8

Go to step 14. Configure the traffic direction of the two configurable external-links on the host expansion board with the following command:
configure equipment external-link-host (SFP index 2-7) (no) direction <Equipm::ExternalLinkConfigType>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 177-3

DLP 177 Configure SFP downlink ports

Note For NCNC-x, SFP ports 2..7 are configurable as uplinks or downlinks. But the uplinks and downlinks shall be respectively consecutive with the uplink starting from SFP port 2 and the downlink starting from SFP port 7. For example, SFP port 5 cannot be configured as downlink unless ports 6 and 7 are configured as downlinks
9 Configure the association between a host shelf SFP and a remote LT with the following command:
configure equipment external-link-assign (SFP index 2-13) (no) remote <Equipm::ExpansionSlotIndex>

10

View the traffic direction of the configurable ports with the following command:
info configure equipment external-link-host [(SFP index 2-7)]

11

View actual rack, shelf, and slot settings of the connected remote LT unit with the following command:
show equipment external-link-host [(SFP index 2-13)] detail

12

Perform a system reset (with or without self-test) in an redundant or non-redundant system to allow the configuration of the SFP link direction (downlink) to take effect. In a non-redundant system, instead of system reset, a NT reset (with or without self-test) may be performed and the NT reset would take less time than the system reset. Use the following commands: a in a redundant or in a non-redundant system:
admin equipment reboot-isam <Equipm::SystemRestart>

in a non-redundant system:
admin equipment slot nt-a reboot <Equipm::BoardRestart>

13

Troubleshoot a problem with an GigE optical link between a SEM, REM, or FD-REM, and its host shelf with the following command:
show equipment diagnostics sfp [(SFP index 2-15)] detail

Note The rules for troubleshooting a problem with an GigE optical link
are:

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.

14

STOP. This procedure is complete.

DLP 177-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 177 Configure SFP downlink ports

Configuration example for a GENC-x board:


configure equipment external-link-host 6 direction remote-lt configure equipment external-link-assign 6 remote 1/1/5 info configure equipment external-link-host 6 show equipment external-link-host detail show equipment diagnostics sfp acu:1/1/6 detail

Configuration example for a NCNC-x board:


configure equipment external-link-host 6 direction remote-lt configure equipment external-link-assign 6 remote 1/1/5 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 177-5

DLP 177 Configure SFP downlink ports

DLP 177-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 178 Configure the default security domain


Purpose
This procedure provides the steps to configure a default security domain to be used in case PPP clients do not provide a domain name.

Prerequisites
The following prerequisites must be fulfilled before a default security domain can be created:

A RADIUS server must have been configured; see DLP 144.

Procedure
Proceed as follows to configure the default security domain: 1 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 <Aaa::InetAddress> (no) second-dns <Aaa::InetAddress> (no) primary-nbns <Aaa::InetAddress> (no) second-nbns <Aaa::InetAddress> (no) sess-timeout <Aaa::DomainSessionTimeout> (no) qos-policy <Aaa::QosProfileName> authenticator <Aaa::Authenticator>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 178-1

DLP 178 Configure the default security domain

Configure the connection profile parameters with the following command:


configure system security conn-profile (name) version <SignedInteger> (no) reject-no-domain (no) reject-inv-domain domain-name <Aaa::DomainName>

Configure the security connection policy with the following command:


configure system security conn-policy conn-profile-name <AsamProfileName>

STOP. This procedure is complete.

Configuration example: In the following example, a default security domain with name unspecified is created. The connection profile is named no-domain.
configure system security domain unspecified authenticator radius:RADPol23 vrf-index 1 configure system security conn-profile no-domain version 1 no reject-no-domain domain-name unspecified configure system security conn-policy conn-profile-name no-domain

DLP 178-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 179 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 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 in one of two ways: wrap new entries to overwrite the oldest entries, or discard all new entries.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 179-1

DLP 179 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 179-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 179-1: Message type and log severity parameters
Item Message type Description Authentication actions CLI configuration changes TL1 configuration changes CLI messages TL1 messages Protocol tracing messages Parameter authentication cli-config-chgs tl1-config-chgs cli-msgs tl1-msgs tracing1 tracing2 tracing3 Video CDR messages All message types (1 of 2) video-cdr all

DLP 179-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 179 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 7302 ISAM | 7330 ISAM FTTN TL1 Commands and Messages 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 179-3

DLP 179 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

Configure the system transaction parameters with the following command:


configure system transaction (no) time-out-value <Trans::TimeoutValue> (no) log-full-action <Trans::logFullaction>

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:
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 configure system transaction log-full-action halt info configure system syslog destination server1 detail admin system syslog destination server1 rotate

DLP 179-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 180 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 prerequisite must be fulfilled before static MAC addresses can be configured:

A VLAN must exist; see DLP 117, DLP 118, DLP 119 or DLP 120. The board must have been planned; see DLP 111. xDSL profiles must have been created; see DLP 129.

Procedure
Proceed as follows to configure static MAC addresses: 1 Configure a static MAC address on the LT with the following command:
configure vlan unicast-mac (unicast-mac) vlan-id <Vlan::UVlanIndex> | <Vlan::SVlanIndex>:<Vlan::CVlanIndex> forward-port <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> /<Eqpt::Port>:<Atm::DefaultVpi>:<Atm::DefaultVci>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 180-1

DLP 180 Configure static MAC addresses

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 lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId> | network:<Shub::NetworkPort> | nt

STOP. This procedure is complete.

Configuration example:
configure vlan unicast-mac 00:00:00:00:00:05 vlan-id 200 forward-port 1/1/5/12:8:35 configure vlan shub unicast-mac 00:00:00:00:00:01 vlan-id 200 forward-port network:7

DLP 180-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 181 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 181-1

DLP 181 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:
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 181-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 182 Configure SHDSL links


Purpose
This procedure provides the steps for configuring SHDSL links.

Note 1 Refer to the System Description 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 108.

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> (no) margin-up-worst <Shdsl::NoiseMarginWC> (no) margin-up-curr <Shdsl::NoiseMarginCC> (no) probe <Shdsl::SpanLineProbeEnable> (no) tc-pam-sele <Shdsl::SpanTCPAMSelection>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 182-1

DLP 182 Configure SHDSL links

Note The parameters min-line-rate and max-line-rate must be set to the same value.

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

STOP. This procedure is complete.

DLP 182-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 182 Configure SHDSL links

Configuration examples: Configuration example for 4-wire Multi-pair bonding


configure shdsl span 1/1/9/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/9/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/9/1 unit-id stu-r loopback-timeout 10 configure shdsl segment 1/1/9/1 unit-id stu-c side customer loopback normal configure atm pvc 1/1/9/1:8:35 no admin-down aal5-encap-type llc-snap configure atm pvc 1/1/9/3:8:35 no admin-down aal5-encap-type llc-snap configure bridge port 1/1/9/1:8:35 configure bridge port 1/1/9/1:8:35 vlan-id 100 configure bridge port 1/1/9/1:8:35 pvid 100 configure bridge port 1/1/9/3:8:35 configure bridge port 1/1/9/3:8:35 vlan-id 100 configure bridge port 1/1/9/3:8:35 pvid 100 configure shdsl span 1/1/9/16 min-line-rate 2304 max-line-rate 2304 margin-down-worst 5 margin-up-worst 5 op-mode ima active admin-up

Configuration example is for IMA


configure shdsl span 1/1/9/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/9/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/9/24 min-line-rate 2304 max-line-rate 2304 margin-down-worst 5 margin-up-worst 5 op-mode ima active admin-up

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 182-3

DLP 182 Configure SHDSL links

Configuration example is for PTM (4-wire PTM, no bonding).


configure shdsl span 1/1/9/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 admin-up configure bridge port 1/1/9/5 configure bridge port 1/1/9/5 vlan-id 100 configure bridge port 1/1/9/5 pvid 100

DLP 182-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 183 Configure IMA on SHDSL links


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

Note Refer to the System Description for a more detailed description of the IMA functionality.

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

the SHDSL links must have been created (and have operational mode ima); see DLP 182.

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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 183-1

DLP 183 Configure IMA on SHDSL links

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:
configure ima group 1/1/9/16 active admin-up min-tx-links 2 min-rx-links 2 configure ima link 1/1/9/16 grp-index 1/1/9/16 configure ima link 1/1/9/18 grp-index 1/1/9/16 configure ima link 1/1/9/21 grp-index 1/1/9/16 configure ima link 1/1/9/24 grp-index 1/1/9/16 configure atm pvc 1/1/9/16:0:35 aal5-encap-type vc-mux-bridged-8023 no admin-down configure bridge port 1/1/9/16:0:35 configure bridge port 1/1/9/16:0:35 vlan-id 100 configure bridge port 1/1/9/16:0:35 pvid 100

DLP 183-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 184 Convert the NE IP address


Purpose
This DLP provides the steps to convert the NE from single to dual IP address mode, or from dual to single IP address mode.

General
The EMS (5526 AMS or 5523 AWS) supports the creation of an NE using a single IP address for the NE only or dual IP addresses for the NE and SHub. After you have created the NE and configured it to use a single or dual IP address, you can convert the node from single to dual IP address mode, or from dual to single IP address mode, using the CLI commands in this DLP. SNMPv3 is only supported in single IP address mode. You cannot convert a system configured with SNMPv3 to dual IP mode. Before you perform the steps in this DLP, you must have already set up the NE for EMS (5526 AMS or 5523 AWS) management and have configured the system for single or dual IP address mode.

Note You can lose communication with the NE when you change the IP address. To ensure that the connection is maintained, perform these procedures from the craft port.

Note For a redundant EMS (5526 AMS or 5523 AWS) server configuration, you must perform the IP address configuration commands (for example, when you configure the SNMP community string or SHub filter) for the IP address of each of the active and redundant server.

Prerequisites
The NE must be administered by the EMS (5526 AMS or 5523 AWS).

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 184-1

DLP 184 Convert the NE IP address

Procedure
Proceed as follows to convert the IP address mode on the NE: 1 2 Establish a CLI session; see DLP 100. Determine the task to perform and go to the appropriate step. a b 3 To convert the NE from dual to single IP address mode, go to step 3. To convert the NE from single to dual IP address mode, go to step 5.

Configure a single IP address on the system with the following command:


configure system single-public-ip

Note The IP interface previously configured on the management VLAN will automatically be removed.

4 5

Go to step 10. Remove the single IP address mode configuration with the following command:
configure system no single-public-ip

Configure the SHub IP address as follows: i Set the adminstrative status of the OAM VLAN to down with the following command:
configure interface shub ip 4093 admin-status down

ii

Configure the SHub IP address with the following command:


configure interface shub ip 4093 ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull>

iii

Set the adminstrative status of the OAM VLAN to up with the following command:
configure interface shub ip 4093 admin-status up

Configure the default route in the SHub with the following command:
configure ip shub vrf 0 route-dest 0.0.0.0/0 next-hop <gateway-ip-address> vlan-id 4093

Configure the SHub filter (access list) with the following command:
configure system shub filter shub-manager <index> src-ip-addr <Ip::V4Address>
where <Ip::V4Address> is the IP address of the EMS

DLP 184-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 184 Convert the NE IP address

Configure the SNMP SHub community string with the following command:
configure system security snmp shub community <index> name <name> privilege read-write no ip-addr

Note The name of the SNMP community can be 1 to 32 characters.

10

STOP. This procedure is complete.

Configuration example: The following example shows the procedure to convert from dual to single IP address:
configure system single-public-ip

The following example shows the procedure to convert from single to dual IP address:
configure system no single-public-ip configure interface shub vlan-id 4093 admin-status down configure interface shub ip 4093 ip-addr 10.177.0.113/17 configure interface shub vlan-id 4093 admin-status up configure ip shub vrf 0 route-dest 0.0.0.0/0 next-hop 10.177.127.254 vlan-id 4093 configure system shub filter shub-manager 1 src-ip-addr 10.176.8.8 configure system security snmp shub community 4 name NETMAN privilege read-write no ip-addr

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 184-3

DLP 184 Convert the NE IP address

DLP 184-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 185 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 185-1

DLP 185 Configure ANCP session

Procedure
Proceed as follows to configure an ANCP session: 1 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) window-size <L2cp::WindowSize> (no) tcp-port <L2cp::InetPortNumber> (no) vrf-id <L2cp::VrfIndex>

Stop the ANCP session with the following command:


configure l2cp no session (index)

STOP. This procedure is complete.

Configuration example:
configure l2cp session 1 bras-ip-address 192.168.200.100 configure l2cp no session 1

DLP 185-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 186 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 186-1

DLP 186 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:
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 186-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 187 Configure global VLAN parameters


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

broadcast-frames: This parameter determines whether 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, cross-connect VLANs and QoS-aware 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 (no) pvid-usage c-vlan-translation | standard

STOP. This procedure is complete.

Configuration example:
configure vlan broadcast-frames priority-policy port-default pvid-usage standard Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI DLP 187-1

DLP 187 Configure global VLAN parameters

DLP 187-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 188 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) to protect 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 129) or by modifying an existing spectrum profile (see DLP 163). 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. See the CLI Commands and Messages document and also TNG 107 for a full description of all related parameters.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 188-1

DLP 188 Configure custom PSD points

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

custom PSD points for ADSL2+, go to step 2 custom downstream PSD points for VDSL, go to step 3 custom upstream PSD points for VDSL, go to step 4 custom downstream PSD points for VDSL2, go to step 5 custom upstream Rx PSD points for VDSL2, go to step 6 custom 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

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

DLP 188-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 188 Configure custom PSD points

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

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 188-3

DLP 188 Configure custom PSD points

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

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

DLP 188-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 188 Configure custom PSD points

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: Configuration example for ADSL2+:


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


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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 188-5

DLP 188 Configure custom PSD points

Configuration example for VDSL (upstream):


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

Configuration example for VDSL2 (downstream):


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


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

DLP 188-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 188 Configure custom PSD points

Configuration example for VDSL2 (upstream):


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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 188-7

DLP 188 Configure custom PSD points

DLP 188-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 189 Configure VDSL2 virtual noise values


Purpose
This procedure provides the steps to configure virtual noise values for VDSL2, both in downstream and upstream direction. 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 107.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 189-1

DLP 189 Configure VDSL2 virtual noise values

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>

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:
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 189-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 190 Configure threshold crossing alerts


Purpose
This document 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 110.

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

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 190-1

DLP 190 Configure threshold crossing alerts

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> (no) ses-farend <Xdsl::IntervalTcaThreshold> (no) uas-farend <Xdsl::IntervalTcaThreshold> (no) es-day-farend <Xdsl::DayTcaThreshold> (no) ses-day-farend <Xdsl::DayTcaThreshold> (no) 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: 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/5/14 tca-line-threshold enable los 40

DLP 190-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 191 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:
configure vlan shub dual-tag-mode

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 191-1

DLP 191 Enable dual tagging in the SHub

DLP 191-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 192 Configure IPProxy CPE management


Purpose
This procedure provides the steps required to configure the S-VLAN to be used for IPProxy CPE Management

Prerequisites
The following prerequisites must be fulfilled before IPProxy CPE management can be configured:

Dual tagging must be enabled in the SHub; see DLP 191 The S-VLAN must not be configured for any other (that is, non-IPProxy) traffic in the system IPProxy CPE Management must be disabled

Procedure
Proceed as follows to configure IPProxy CPE management: 1 Create the S-VLAN to be used for IPProxy CPE management in the system with the following command:
configure vlan id stacked:<Vlan::SVlanIndex>:0 name <Vlan::AdminString> mode layer2-terminated

Associate the S-VLAN created with the IPProxy CPE management function with the following command:
configure cpe-management vlan-id <CpeProxy::VlanIndex>

Create the S-VLAN in the SHub with the following command:


configure vlan shub id <Sys::VlanId> mode layer2-terminated

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 192-1

DLP 192 Configure IPProxy CPE management

Associate the S-VLAN created in the SHub with the IPProxy CPE management function with the following command:
configure cpe-management shub vlan-id <CpeProxy::ShubVlanIndex>

STOP. This procedure is complete.

Configuration example:
configure vlan id stacked:512:0 name IPProxyVLAN mode layer2-terminated configure cpe-management vlan-id 512 configure vlan shub id 512 mode layer2-terminated configure cpe-management shub vlan-id 512

DLP 192-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 193 Enable IPProxy CPE management


Purpose
This procedure provides the steps required to enable IPProxy CPE Management

Prerequisites
The following prerequisites must be fulfilled before IPProxy CPE management can be enabled:

CPE management mode must be disabled The IPProxy CPA management S-VLAN must have been configured; see DLP 192

Procedure
Proceed as follows to enable IPProxy CPE management: 1 Configure the CPE Management mode as IP with the following command:
configure cpe-management proxy-mode ip

STOP. This procedure is complete.

Configuration example:
configure cpe-management proxy-mode ip

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 193-1

DLP 193 Enable IPProxy CPE management

DLP 193-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 194 Configure IPProxy CPE management session


Purpose
In order to be able to use Telnet or TFTP to manage a CPE connected to an LT port, a IPProxy CPE management session has to be configured first. This procedure provides the steps to configure an IPProxy CPE Management session.

Prerequisites
The following prerequisites must be fulfilled before IPProxy CPE management session can be configured:

The IPProxy CPE Management S-VLAN must have be configured; see DLP 192 The IPProxy CPE Management S-VLAN function must have be enabled; see DLP 193 The LT to which the CPE is connected must be planned and unlocked; see DLP 111 and DLP 112 respectively. xDSL profiles must have been created; see DLP 129.

Procedure
Proceed as follows to configure a IPProxy CPE management session: 1 Configure the xDSL line to which the CPE is connected with the following command:
configure xdsl line <Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId>/<Eqpt::PortId> service-profile <Xdsl::LineServiceProfile> spectrum-profile <Xdsl::LineSpectrumProfile> (no) dpbo-profile <Xdsl::LineDpboProfile> admin-up

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 194-1

DLP 194 Configure IPProxy CPE management session

Configure xDSL line interface port with the following command:


configure interface port xdsl-line:<Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId>/ <Eqpt::PortId> (no) link-updown-trap (no) user <Itf::asamIfExtCustomerId> (no) severity <Itf::asamIfExtAlmReportingSeverity>

Add the SHub LT port to which the CPE is connected to the IPProxy CPE Management S-VLAN (if not already added) with the following command:
configure vlan shub id <Sys::VlanId> egress-port lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId>

If the NT type is not of type ECNT-C, add the SHub NT port to the S-VLAN (if not already added) with the following command:
configure vlan shub id <Sys::VlanId> egress-port nt

Configure the SC-VLAN to be used for this session. In this step, the CVlanIndex given must be calculated as follows based on the LT port on which the IPProxy session must be configured: CVlanIndex = 48 x (LT slot# - 1) + LT port# + 1
where: LT slot# has the range [1..16] (1 for left most LT slot on rack 1, shelf 1 and 16 for the last LT slot on rack 1, shelf 1) LT port# has the range [1..48] (1 for the first LT port and 48 for the last LT port).

configure vlan id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex> name <Vlan::AdminString> mode cross-connect

Configure the PVC for this session with the following command:
configure atm pvc <Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:Eqpt::VciId> aal5-encap-type llc-snap-routed

Configure an IPoA cross-connect for this session with the following command:
configure atm ip-cross-connect <Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId>::<Eqpt::VpiId>:<Eqpt::VciId> cpe <Ip::V4AddressHex> next-hop <Ip::V4AddressHex>

Configure a bridge port for this session with the following command:
configure bridge port <Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:<Eqpt::VciId> mac-learn-off

Configure the SC-VLAN on the bridge port with the following command:
configure bridge port <Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:<Eqpt::VciId> vlan-id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>

DLP 194-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 194 Configure IPProxy CPE management session

10

Configure a PVID on the bridge port as the SC-VLAN with the following command:
configure bridge port <Eqpt::RackId>/<Eqpt::ShelfId>/ <Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:<Eqpt::VciId> pvid stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>

11

Create the session with the following command:


configure cpe-management session <Eqpt::RackId>/<Eqpt::ShelfId> /<Eqpt::SlotId>/<Eqpt::PortId> [connection <CpeProxy::cpeIpProxySessionProtocolPort>]
where the connection parameter can be optionally specified as an unused (that is, unused by any other session) port in the range [13410..13457] or omitted. If omitted, the system will automatically assign a free connection port.

12

STOP. This procedure is complete.

Configuration example:
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 IPProxy CPE M configure vlan shub id 512 egress-port lt:1/1/5 configure vlan id stacked:512:57 name IPProxyCPE54 mode cross-connect configure atm pvc 1/1/5/8:1:39 aal5-encap-type llc-snap-routed configure atm ip-cross-connect 1/1/5/8:1:39 cpe 192.168.1.1 next-hop 192.168.1.2 configure bridge port 1/1/5/8:1:39 mac-learn-off configure bridge port 1/1/5/8:1:39 vlan-id stacked:512:57 configure bridge port 1/1/5/8:1:39 pvid stacked:512:57 configure cpe-management session 1/1/5/8

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 194-3

DLP 194 Configure IPProxy CPE management session

DLP 194-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 195 Configure general bridge parameters


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 ageing-time <Vlan::AgingTime>

Note The setting is applicable to the entire bridge.

Configure specify the aging time for dynamically learned MAC addresses in the filtering database of the SHub with the following command:
configure bridge shub ageing-time <Shub::AgingTime>

Note The setting is applicable to the entire SHub bridge.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 195-1

DLP 195 Configure general bridge parameters

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:
configure bridge ageing-time 360 configure bridge shub ageing-time 360 configure bridge shub mac-learning no disable-nw-port

DLP 195-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 196 Configure Voice SIP


Purpose
This document provides the steps to configure the Voice Session Initiation Protocol (SIP).

Prerequisite
The following prerequisite must be fullfilled before Voice SIP can be configured:

The board (POLT-B) and the applique (PTCP-A) must be planned; see DLP 111. A VLAN in mode voice-vlan must have been created configure vlan shub id <Sys::VlanId> mode voice-vlan Network interfaces must have been added to the VLAN; see DLP 121.

Procedure
Proceed as follows to configure Voice SIP: 1 To manage the Voice SIP server profile, do one of the following: a Manage the Voice SIP server profile by IPv4 with the following command
configure voice sip server (name) admin-status up address ipv4:<Ip::V4Address> (no) port <Sip::ServerPort> (no) server_type <Sip::ServerType>

Manage the Voice SIP server profile by DNS with the following command:
configure voice sip server (name) admin-status up address dns:<Sip::ServerAddr> (no) port <Sip::ServerPort> (no) server_type <Sip::ServerType>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 196-1

DLP 196 Configure Voice SIP

Manage the Voice SIP dial plan profile with the following command:
configure voice sip dialplan (name) (no) pre-activated <Sip::DialPlanPreActivated> (no) static-prefix <Sip::DialPlanStaticPrefix> (no) static-suffix <Sip::DialPlanStaticSuffix>

Manage the Voice SIP dial plan digitmap profile with the following command:
configure voice sip digitmap (name) type <Sip::DialPlanDigitmapType> rule <Sip::DialPlanDigitmapValue> (no) access-type <Sip::DialPlanDigitmapAccessType>

Note 1 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 2). Note 2 The parameter access_type is not visible when a new Voice SIP dial plan digitmap is created, but only when an existing digitmap is modified.
4 To configure the Voice SIP user agent profile, do one of the following: a Configure the Voice SIP user agent profile management by DHCP with the following command:
configure voice sip user-agent-dhcp (name) associated-slot <Equipm::LtSlotIndex> associated-proxyserver none | name:<Sip::ServerName> associated-regserver none | name:<Sip::ServerName> associated-dialplan none | name:<Sip::DialPlanName> (no) user-agent-domain <Sip::UserAgentUaDomain> admin-status up | down (no) port <Sip::UserAgentPort> vlan-id <Sip::UserAgentVlanId> (no) signal-dscp <Sip::UserAgentSignalDscp> (no) signal-pbits <Sip::UserAgentSignalPbits> (no) rtp-dscp <Sip::UserAgentRtpDscp> (no) rtp-pbits <Sip::UserAgentRtpPbits>

Configure the Voice SIP user agent profile mangement manually with the following command:
configure voice sip user-agent-manual (name) associated-slot <Equipm::LtSlotIndex> associated-proxyserver none | name:<Sip::ServerName> associated-regserver none | name:<Sip::ServerName> associated-dialplan none | name:<Sip::DialPlanName> (no) user-agent-domain <Sip::UserAgentUaDomain> admin-status up | down ip-address <Sip::UserAgentIpAddr> prefix-length <Sip::PrefixLength> gateway-ip <Sip::UserAgentIpAddr> domain-server <Sip::UserAgentIpAddr> (no) port <Sip::UserAgentPort> vlan-id <Sip::UserAgentVlanId> (no) signal-dscp <Sip::UserAgentSignalDscp>

DLP 196-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 196 Configure Voice SIP

(no) signal-pbits <Sip::UserAgentSignalPbits> (no) rtp-dscp <Sip::UserAgentRtpDscp> (no) rtp-pbits <Sip::UserAgentRtpPbits>

Manage the Voice SIP termination profile with the following command:
configure voice sip termination (termination) user-agent <Sip::UserAgentName> (no) directory-number <Sip::TermDnumber> (no) user-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>

Manage the Voice SIP port Local Loop Unbundling with the following command:
configure voice sip local-loop (line) (no) unbundle

Note This command can only be used when ALTS-U subracks are being used.

STOP. This procedure is complete.

Configuration example:
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-dhcp SIPAgent1 associated-slot 1/1/6 associated-proxyserver name:SIPServer1 associated-regserver name:SIPServer1 associated-dialplan name:SIPDialplan1 admin-status up vlan-id 650 configure voice sip termination 1/1/6/1 user-agent SIPAgent1 directory-number 123456 admin-status up

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 196-3

DLP 196 Configure Voice SIP

DLP 196-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 197 View port configuration and operational data


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 Commands and Messages.

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 197-1

DLP 197 View port configuration and operational data

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:
show xdsl config-data-port 1/1/5/12 show xdsl oper-data-port 1/1/5/12 show config-data-port 1/1/5/14 show oper-data-port 1/1/5/14

DLP 197-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 198 Configure multicast on the SHub


Purpose
This procedure provides the steps to configure multicast on the SHub (general parameters, capacity and source table) on the NE.

Prerequisites
The following prerequisites must be fulfilled before multicast on the SHub can be configured:

IGMP snooping must be activated; see DLP 138. The egress port must have been added to the VLAN; see DLP 128.

Procedure
Proceed as follows to configure multicast on the SHub: 1 Configure the multicast related parameters applicable to 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>

Configure entries 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 198-1

DLP 198 Configure multicast on the SHub

Configure the ports to which the traffic related to the specified multicast IP address will be forwarded with the following command:
configure mcast shub mcast-addr (mcast-addr) vlan-id <Vlan::VlanId> (no) egress-port (port)

Configure the CAC Multicast Source 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 <Igmp::MulticastGuaranteedServ> (no) bundle name <Igmp::IgnoredBundleName>

STOP. This procedure is complete.

Configuration example:
configure mcast shub active-streams 200 configure mcast shub mcast-addr 224.1.1.10 vlan-id 200 configure mcast shub mcast-addr 224.1.1.10 vlan-id 200 egress-port lt:1/1/5 configure mcast shub src 224.1.1.1 vlan-id 200 ip-addr 0.0.0.0 eth-sus-bit-rate 4250 guaranteed-serv bundle name:MyBundle

DLP 198-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 199 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 101.

Prerequisites
The following prerequisites must be fulfilled before QoS on the SHub can be configured:

The egress port must have been added to the VLAN; see DLP 128.

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 (port) (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 (port) traffic-class <Qos::ShubTrafficClass>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 199-1

DLP 199 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 (port-id) flow <Qos::PolicerFlowIndex> meter <Qos::PolicerMeterIndex>

STOP. This procedure is complete.

Configuration example:
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 199-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 200 Configure MSTP


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 prerequisite must be fulfilled before MSTP can be configured:

A VLAN in iBridge mode must have been created on the SHub; see DLP 120 step 3. The port-type of the network port must be different from unused. This can be verified with the command show interface shub port and, if necessary, 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 200-1

DLP 200 Configure MSTP

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.
4 Configure the port parameters for the Common Instance with the following command:
configure mstp port <Shub::MstpNetworkPort> (no) priority <Shub::MstpPortPriority> (no) disable-stp path-cost <Shub::MstpPathCost> (no) edge-port (no) admin-p2p <Shub::MstpAdminP2PPort> (no) hello-time <Shub::StpHelloTime>

DLP 200-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 200 Configure MSTP

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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 200-3

DLP 200 Configure MSTP

Configuration example: 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 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 200-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 201 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 protocol-trace (trace-subject) protocol igmp | dhcp | arp syslog <Debug::SyslogMsgType> (no) events (no) packet-summary

STOP. This procedure is complete.

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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 201-1

DLP 201 Configure protocol tracing

DLP 201-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 202 Configure QoS threshold crossing alerts


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

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

The board must have been planned; see DLP 111.

Procedure
Proceed as follows to configure QoS TCAs: 1 Configure the QoS global variables (buffer size, setting of thresholds for data aggregation buffer (both in up- and downstream direction, ...) 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 202-1

DLP 202 Configure QoS threshold crossing alerts

Configure the QoS 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:
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 202-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 203 Configure general security settings


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

password policy file transfer attributes

Procedure
Proceed as follows to configure general security settings: 1 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 file transfer states and attributes with the following command:
configure system security filetransfer (no) protocol <SwMngt::Protocol>

Configure the file transfer server attributes with the following command:
configure system security filetransfer server (serverid) user-name <SwMngt::UserName> password <SwMngt::Password>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 203-1

DLP 203 Configure general security settings

STOP. This procedure is complete.

Configuration example:
configure system security password min-length 8 min-num-special-char 2 mixed-case mandatory configure system security filetransfer protocol sftp configure system security filetransfer server 192.168.210.1 user-name JohnDoe password My#Pass&

DLP 203-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 204 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 prerequisites 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 204-1

DLP 204 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>

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)
where vlan-id is the VLAN created in step 2.

STOP. This procedure is complete.

Configuration example:
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 204-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 205 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.

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

The LT must be planned, see DLP 111. xDSL profiles must have been created, see DLP 129. VDSL 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

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.

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-up (no) passive-mode

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 205-1

DLP 205 Configure Link Related Ethernet OAM

keep-alive-intvl <Ether::KeepAliveTimeTicks> response-intvl <Ether::ResponseTimeTicks>

Note 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)]

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

DLP 205-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 205 Configure Link Related Ethernet OAM

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:
configure efm-oam interface 1/1/3/1 admin-up no passive-mode keep-alive-intvl 300 response-intvl 5 show efm-oam local-oam-info 1/1/3/1 show efm-oam peer-oam-info 1/1/3/1 show efm-oam oam-stats 1/1/3/1 show efm-oam mac-stats 1/1/3/1 show efm-oam pme-stats 1/1/3/1 show efm-oam pme-stats link:1/1/3/2

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 205-3

DLP 205 Configure Link Related Ethernet OAM

DLP 205-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 206 Configure a 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 prerequisites must be fulfilled before enhanced PSD shaping provisioning can be configured:

The LT board must be planned; see DLP 111.

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>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 206-1

DLP 206 Configure a DPBO profile

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

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>

DLP 206-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 206 Configure a DPBO profile

dpbo-profile (index)

STOP. This procedure is complete.

Configuration example:
configure xdsl dpbo-profile 1 configure xdsl dpbo-profile 1 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 configure xdsl dpbo-profile 1 active configure xdsl line 1/1/4/1 dpbo-profile 1

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 206-3

DLP 206 Configure a DPBO profile

DLP 206-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 207 Modify a DPBO profile


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

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

The DPBO profile must have been created; see DLP 206.

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

Modify the parameters of an e 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

Use one of the following commands to complete the modification of the DPBO profile:

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 207-1

DLP 207 Modify a DPBO profile

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:
configure xdsl dpbo-profile 1 modification start configure xdsl dpbo-profile 1 name test_profile configure xdsl dpbo-profile 1 modification complete

DLP 207-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 208 Configure 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.

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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 208-1

DLP 208 Configure power back off

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:
configure xdsl spectrum-profile 4 vdsl pbo 1 param-a 6000

DLP 208-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 209 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 SC-VLAN an iBridge VLAN

This procedure provides the steps to configure vMAC.

Prerequisite
A VLAN must have been created, see DLP 117, DLP 119 or DLP 120.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 209-1

DLP 209 Configure vMAC

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 vmac-unique-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 with the following command:
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

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.

Configuration example:
configure vlan vmac-address-format host-id 1 admin equipment reboot-isam with-self-test configure vlan id 100 vmac-translation vmac-dnstr-filter show vlan vmac-bridge-port-fdb vlan-id 100

DLP 209-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 210 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 command to view differnet 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)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 210-1

DLP 210 View the status of various system parameters

STOP. This procedure is complete.

Configuration example:
show system clock-mgmt show system memory-usage nt-a show system cpu-load nt-b

DLP 210-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

DLP 211 Configure SFP uplink ports


Purpose
This DLP provides the steps to configure the link direction for the SFP uplink ports on:

a GENC-E or GENC-F board installed in a 7330 ISAM FTTN ARAM-D host shelf. a NCNC-B, NCNC-C, NCNC-D or NCNC-E board installed in a 7330 FD ISAM shelf

Procedure
Proceed as follows to configure the link direction to uplink for an SFP port on a GENC-x or NCNC-x board: 1 Do one of the following:

For configuring an SFP uplink port on a GENC-x board, go to step 2 For configuring an SFP uplink port on a NCNC-x board, go to step 5

Configure the link direction (i.e. uplink) of the two configurable external-links on the host expansion board with the following command:
configure equipment external-link-host (SFP index 6 or 7) (no) direction <Equipm::ExternalLinkConfigType>

View the traffic direction of the configurable ports with the following command:
info configure equipment external-link-host (SFP index 6 or 7)

4 5

Go to step 8. Configure the traffic direction of the two configurable external-links on the host expansion board with the following command:
configure equipment external-link-host (SFP index 2-7) (no) direction <Equipm::ExternalLinkConfigType>

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

DLP 211-1

DLP 211 Configure SFP uplink ports

Note For NCNC-x, SFP ports 2..7 are configurable as uplinks or downlinks. But the uplinks and downlinks shall be respectively consecutive with the uplink starting from SFP port 2 and the downlink starting from SFP port 7. For example, SFP port 4 cannot be configured as uplink unless ports 2 and 3 are configured as uplinks.
6 View the traffic direction of the configurable ports with the following command:
info configure equipment external-link-host [(SFP index 2-7)]

Perform a system reset (with or without self-test) in an redundant or non-redundant system to allow the configuration of the SFP link direction (downlink) to take effect. In a non-redundant system, instead of system reset, a NT reset (with or without self-test) may be performed and the NT reset would take less time than the system reset. Use the following commands: a in a redundant or in a non-redundant system:
admin equipment reboot-isam <Equipm::SystemRestart>

in a non-redundant system:
admin equipment slot nt-a reboot <Equipm::BoardRestart>

STOP. This procedure is complete.

Configuration example for a GENC-x board:


configure equipment external-link-host 6 direction network info configure equipment external-link-host 6

Configuration example for a NCNC-x board:


configure equipment external-link-host 6 direction network info configure equipment external-link-host 6 admin equipment reboot-isam without-self-test

DLP 211-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Routine Task Procedure (RTP)

RTP 100 Backup the configuration RTP 101 Restore the configuration RTP 102 Retrieve remote inventory

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

RTP 100 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.

General
The TFTP daemon on the AWS assumes a default home directory /var/opt/aws/equipment. The TFTP daemon on the AMS assumes a default home directory /opt/ALAams/systemdata. This means that all the TFTPs initiated from the NE result in a file written relative to this point.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

RTP 100-1

RTP 100 Backup the configuration

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 AWS/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 # cd /var/opt/aws/equipment/temp (*) # 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

RTP 100-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

RTP 100 Backup the configuration

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 or AWS 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

RTP 100-3

RTP 100 Backup the configuration

RTP 100-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

RTP 101 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 or AWS server.

View the status of the database download process and, in case of an download failure, the reason, 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.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

RTP 101-1

RTP 101 Restore the configuration

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

RTP 101-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

RTP 102 Retrieve remote inventory


Purpose
This procedure provides the steps to retrieve and show the remote inventory information. Table RTP 102-1 describes the RI information that is shown.
Table RTP 102-1: RI information
RI information manufacturer inventory-pba inventory-fpba inventory-ics inventory-clie 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

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

RTP 102-1

RTP 102 Retrieve remote inventory

STOP. This procedure is complete.

Configuration example: show equipment slot detail show equipment applique detail

RTP 102-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Trouble Analysis Procedure (TAP)

TAP 100 Metallic test access TAP 101 F5 loopback test TAP 102 Equipment repair TAP 103 Single ended line testing TAP 104 Fault isolation and troubleshooting

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 100 Metallic test access


Purpose
This procedure provides the steps for Metallic Test Access (MTA) using TL1 commands.

Note Depending on the capabilities of the applique/splitter card, either full test access (that is, MTA) or limited test access (that is, outward test access) is supported.
The setup for MTA sessions is shown in Figure TAP 100-1.
Figure TAP 100-1: Metallic test access setup
To filter, modem and phone A special cable modified from serial cable, the outward and inward bos Test Shelf To PSTN

TAU

SPLITTER

NTIO TL1 gateway installed Computer/WS (Median Device software installed) Computer (test head Software installed) Power -48v Test Head NT Lab Network SHub LT

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 100-1

TAP 100 Metallic test access

Useful TL1 Commands


The following TL1 commands are useful for MTA:

ACT-USER command CONN-LPACC-MET command CONN-TACC-MET command CHG-SPLIT command CONN-MON command DISC-TACC command REPT-STAT command REPT-INITZN command REPT-OPSTAT-TACC command CANC-USER command

ACT-USER Command
Command Syntax ACT-USER:[tid]:uid:[ctag]::pid; Command Description This command activates the user session. Configuration Example ACT-USER::SUPERUSER:::PASWD;

CONN-LPACC-MET Command
Command Syntax CONN-LPACC-MET:[tid]:aid_circuit:[ctag]::[tap]:[configrn]; Command Description This command controls TAP selection, access point designation, and TAP loop around for the remote test unit to calibrate for the next test. Configuration Example CONN-LPACC-MET: LAB: XDSL-1-1-1-1:::1:2WA;

TAP 100-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 100 Metallic test access

CONN-TACC-MET Command
Command Syntax CONN-TACC-MET:[tid]:[tap]:[ctag]; Command Description This command enables the NE to provide a zero-loss, high-impedance monitor connection to the transmission pair of the circuit and complete circuit access. It also removes the TAP loop around and connects the appropriate TAP lead pair to the access point. Configuration Example CONN-TACC-MET:LAB:1:;

CHG-SPLIT Command
Command Syntax CHG-SPLIT:[tid]:[tap]:[ctag]; Command Description This command instructs the NE to provide the necessary connection to the TAP and split, at the access point, the pair or pairs specified by the access command of the circuit under test. Use this command to provide access to the lead pair in order to induce TDR testing. Configuration Example CHG-SPLIT:LAB:1:;

CONN-MON Command
Command Syntax CONN-MON: [tid]:[tap]:[ctag]; Command Description This command is used to establish a monitor state without having to re-access the circuit under test. Use this command to get from the SPLIT mode to MONITOR mode. Configuration Example CONN-MON:LAB:1:;

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 100-3

TAP 100 Metallic test access

DISC-TACC Command
Command Syntax DISC-TACC:[tid]:[tap]:[ctag]; Command Description This command causes the NE to restore the circuit under test to its through state and release all TAP connections to that access point. Configuration Example DISC-TACC:LAB:1:;

REPT-STAT Command
Command Syntax REPT-STAT:[tid]::[ctag]; Command Description This command is sent from the OS to the RTU or the NE to check that the link between them is in operation. Additionally, if the NE does not receive this command from the OS or the RTU for a period of 75 seconds, it shall release any access at the TAP. Configuration Example REPT-STAT:LAB::;

REPT-INITZN Command
Command Syntax REPT-INITZN:[tid]::[ctag]; Command Description This input command message is used to indicate an initialization by an OS to a RTU or by a RTU to NE or by NE to RTU. As input command, it is sent from the OS to the RTU or NE to indicate the OS has initialized. The RTU and NE will disconnect any accesses that are up at the request of the OS sending this command. If the RTU initializes, this command is sent to all NE's providing test access causing the accesses to release. If the NE initializes, this input command will be send to the RTU providing test access causing the RTU to release all resources. Configuration Example REPT-INITZN:LAB::;

TAP 100-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 100 Metallic test access

REPT-OPSTAT-TACC Command
Command Syntax REPT-OPSTAT-TACC:[tid]:[tap]:[ctag]; Command Description This command reports the status of the test access port (TAP). Following options are supported for STATE:

IDLE = No test access active. LPACC = The TAP has been assigned to a circuit, but it is in loopback mode. MON = The TAP is passively monitoring a circuit. SPLIT = The TAP is intrusively accessing the equipment and the circuit in full split mode.

Configuration Example REPT-OPSTAT-TACC:LAB:1:;

CANC-USER Command
Command Syntax CANC-USER:[tid]:[uid]:[ctag]; Command Description This command terminates the user session and releases all TAP resources on the NE. Configuration Example CANC-USER: LAB::;

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 100-5

TAP 100 Metallic test access

TAP 100-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 101 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 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 101-1

TAP 101 F5 loopback test

TAP 101-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 102 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 112. Shut down individual equipment; see DLP 153. Pull out equipment; see the XD Modular Hardware Installation Manual for the 7302 ISAM or the Hardware Installation and Maintenance Practices for the 7330 FTTN.

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 time synchronization with the management station. See DLP 103.
4 5 6 7 8 Replan equipment (for example, plug-in units); see DLP 111. Plug in equipment; see the XD Modular Hardware Installation Manual for the 7302 ISAM or the Hardware Installation and Maintenance Practices for the 7330 FTTN. Power up individual equipment; see DLP 153. Unlock equipment (mostly plug-in units); see DLP 112. Start up or shut down the system. Do one of the following: a b 9 Shut down or restart the SHub; see DLP 151. Reboot the entire system; see DLP 152.

STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 102-1

TAP 102 Equipment repair

TAP 102-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 103 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 centralized Network Analyser (NA) for loop pre-qualification and maintenance of the network. Refer to the System Description for more detailed information.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 103-1

TAP 103 Single ended line testing

TAP 103-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting


Purpose
This TAP provides steps to use the EMS (5526 AMS or 5523 AWS) or CLI to isolate a problem indicated by an alarm.

General
Resolve the alarms that affect service before the alarms that do not affect service. Use local procedures to correct problems associated with customized alarms. Contact Alcatel-Lucent customer technical assistance at 1-888-252-2832 (1-888-ALCATEC) when a problem cannot be corrected. Use the alarm information obtained from the EMS Event Viewer during analysis. Use the TL1 or CLI autonomous messages generated during trouble locating and additional data, such as visual or audible alarms, when available. Service states should also be considered.

Caution When an alarm has been disabled by the user, it is not generated or displayed in the Event Viewer.

See the 7302 ISAM | 7330 ISAM FTTN CLI Commands document for information about CLI syntax. See the 7302 ISAM | 7330 ISAM FTTN TL1 Commands and Messages document for information about TL1 syntax. Several of the protocols in this TAP may require the assistance of someone familiar with UNIX systems and commands. Many of the UNIX troubleshooting protocols and most of the UNIX commands require root access. In these cases, Alcatel-Lucent recommends that a UNIX system administrator perform the troubleshooting.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-1

TAP 104 Fault isolation and troubleshooting

Alarms are grouped by alarm type in Table TAP 104-1 and Table TAP 104-2. Each alarm has the following parameters listed in the order they appear in the table:

Alarm ID (No.): unique identification of the alarm Alarm name: descriptive alarm name followed by the alarm name as it appears in the CLI configure command (the CLI alarm name is in parenthesis) Class of the alarm: communication (Com) processing errors (Proc) quality of service (QoS) environmental (Envir) equipment (Equip) Severity level assigned to the alarm: Indeterminate (Ind) warning (War) minor (Min) major (Maj) critical (Crit) Service affecting: indicates whether the alarm is service affecting (SA) or non-service affecting (NSA) NE type: indicates whether the alarm applies to the 7302 ISAM (7302), the 7330 ISAM FTTN (7330), or both Description of the alarm Troubleshooting recommendations

Note Except where otherwise specified, the report and logging modes for all alarms are enabled.

Procedure
Use this procedure to isolate a fault indicated by an alarm. 1 Choose one of the following methods to access the alarms: a To access the alarms using the 5526 AMS, see the NTP for managing alarms and events in the 7330 ISAM FTTN Operations and Maintenance Using the 5526 AMS guide. To access the alarms using the 5523 AWS, see the AWS administration overview chapter in the 5523 AWS ADMIN User Guide. To access the alarms using CLI, see the NTP for monitoring alarms in the 7330 ISAM FTTN Operations and Maintenance Using CLI guide.

b c 2

Select the alarm you want to view. An associated message appears at the bottom of the window.

TAP 104-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Note If multiple alarms are present, resolve the alarms in the following order:

Critical (red) Major (orange) Minor (yellow)

Use Table TAP 104-1 and Table TAP 104-2 to help you determine the cause of the alarm and the appropriate action for resolving the alarm. Alarms are grouped by type. You can use the class column of the table to help locate an alarm in the table. Some alarms are not currently supported and are indicated as such.

Note 1 In Table TAP 104-1 and Table TAP 104-2, the CLI alarm names shown in parentheses are listed exactly as they appear in the CLI configure alarm command. Alarm names as they appear in the CLI show alarm commands are slightly different. Note 2 Note that the term board as it appears in the CLI alarms is referred to as either unit or card throughout the 7330 ISAM FTTN documentation. For example, the ECNT-A card is a type of NT unit and the EVLT-A card is a type of LT unit.
Table TAP 104-1: System alarm definitions for the 7302 ISAM and the 7330 ISAM FTTN
Alarm (grouped by alarm type) No. Alarm name (CLI) Class Sev. SA NE type Description Troubleshooting recommendations

Alarm type = Equip (1); Index1 = eqptHolderld (index in equipment holder Table), Index2 = not used 0 1 Persistent data loss (persist-data-loss) Equip Crit SA 7302 7330 No defects The system has lost all persistent data after a restart. The system is not configured. The SNTP server does not respond to the requested messages. The NT disk is 90% full. Reconfigure the system.

SNTP server not responding (sntp-comm-lost)

Equip

Maj

NSA

7302 7330

Check the SNTP server.

NT disk 90% full (nt-disk-90%full)

Equip

Maj

NSA

7302 7330

Clean up the disk space on the NT. Check that the external source signals at the BITS inputs to the system are within specification.

System clock not using preferred timing mode (preferred-mode)

Com

Maj

SA

7302 7330

The system is configured to synchronize to an external source and a source other than the configured highest priority source is being used to derive synchronization.

(1 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-3

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 6 Alarm name (CLI) System clock in holdover mode or in free-run mode (timing-reference) Class Com Sev. Crit SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Check that the external source signals at the BITS inputs to the system are within specification.

The system is configured to synchronize to an external source, and the system is deriving synchronization using the internal source due to a failure on the external source signal. The NT cannot communicate with the SHub. The NEP back panel type read from SMAS case is an unknown type.

Communication lost with SHub (shub-loc)

Equip

Crit

SA

7302 7330

Wait until the SHub has finished rebooting.

25

Back panel type invalid (back-pnl-inv)

Equip

Maj

NSA

7302

The system will start up with the default back panel. Check the back panel type configuration when the system is running. Compare the SHub configuration with the database (last database changes may be lost).

28

SHub configuration loss (shub-conf-loss)

Equip

Crit

SA

7302

The SHub configuration saved on the NT unit differs from the current SHub configuration. The last changes on the SHub database (in between two configuration save actions) were lost due to a subsystem reset.

Alarm type = EquipHolder (2); Index1 = eqptHolderId (index in equipment holder table), Index2 = not used 0 1 No defects Rack power alarm (rack-power) 2 Rack fan unit 1 alarm (rack-fan-unit1) 3 Rack fan unit 2 alarm (rack-fan-unit2) 7 Shelf-type mismatch alarm (shelf-mismatch) 8 Extension chain installation alarm (ext-chain-instl) Equip Crit SA 7302 7330 Equip Min NSA 7302 7330 Equip Maj NSA 7302 Equip Maj NSA 7302 Fan unit 1 in the rack is failing. Fan unit 2 in the rack is failing. A shelf detected, but the actual shelf type is unknown or it differs from the planned shelf type. A consistency problem has been detected with the installation of the extension chain or multiple chains. Check the fan. Equip Min NSA 7302 No defects The power fuse is broken. Check the power supplies.

Check the fan.

Check the equipment. Check the configuration.

Check the cabling of the extension cable.

(2 of 34)

TAP 104-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 9 Alarm name (CLI) Shelf missing alarm (shelf-missing) Class Equip Sev. Maj SA SA

NE type 7330

Description

Troubleshooting recommendations Check for a GENC-E or GENC-F card on the host shelf. Check the cabling to the ES. Verify there is an EDSE-A card on the ES. Verify there is at least one LT unit on the ES. Verify there is a PWIO-B on the ES. Check the fan on the ES. Check the power cable on the ES.

A shelf is planned, but no shelf is detected. A shelf has been detected at least once since the shelf was planned.

10

Shelf installation missing alarm (shelf-install-missing)

Equip

Min

NSA

7330

Shelf is planned, but no shelf detected. No shelf has been detected since it is was planned.

Check the presence of GENC-E or GENC-F on the host shelf. Check the cabling to the ES. Verify there is an EDSE-A card on the ES. Verify there is at least one LT unit on the ES. Verify there is a PWIO-B on the ES. Check the fan on the ES. Check the power cable on the ES.

Alarm type = EquipHolder (2); Index1 = eqptHolderId (index in equipment holder table to identify a shelf), Index2 = not used 0 15 No defects Door alarm (door) 17 Fuse alarm (fuse) Equip Crit NSA 7302 7330 An indication has been detected that exactly one power feed is inoperative within a shelf. This can be due to no input power or a blown fuse. One or more of the shelfs fans has failed. Two or more fans in the ARAM-D shelf have failed, or the fan tray was removed. The shelf on which the failure occurred automatically powers down after approximately 2 min. (1) The shelf can be a standalone, a host, or an expansion shelf. (3 of 34) Check the fuse. Check the power feed. Envir Min NSA 7302 No defects Open NEP cabinet door Close the door.

18

Single fan failure (single-fan-fail)

Equip

Maj

NSA

7330

Check the fan tray (the tray LED of the faulty fan is lit red). Check the fan tray of the shelf that raised the alarm. The shelf will power off within 3 minutes of the alarm.

19

Double fan failure (double-fan-fail)

Equip

Crit

SA

7330

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-5

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 20 Alarm name (CLI) System ac power failure (ac-power-fail) 21 Test chain not configured (test-chain-config) 22 TAU not present or failed (tau-problem) Equip Min NSA Equip Min NSA Class Envir Sev. Crit SA SA

NE type 7330

Description

Troubleshooting recommendations Check the power installation.

The shelf will shut down in 15 min. This alarm is externally provided.

7330

The test chain configuration does not support the test requested. The test cannot be completed because the GENC-F does not have a TAU (required for ITSC) or has failed.

Configure the test chain to support the test requested.

7330

If the GENC-F card does not support MTA, replace it with a GENC-F card that supports MTA. If the GENC-F card supports MTA, the card may be faulty. Force a cold reset of the card. If the card fails again, send the card for repair. If the GENC-F card does not support ITSC, replace it with a GENC-F card that supports ITSC. If the GENC-F card supports ITSC, the card may be faulty. Force a cold reset of the card. If the card fails again, send the card for repair. Verify the test equipment.

23

ITSC not present or failed (itsc-problem)

Equip

Min

NSA

7330

The test cannot be completed because the GENC-F card does not support ITSC or has failed.

24

No test resources (test-resources)

Equip

Min

NSA

7330

The test cannot be completed because one or more other test resources are not present (for example, the shelf is not available). The test equipment has failed during a test. Other equipment reported a hardware failure.

25

Hardware failed (hw-fail)

Equip

Min

NSA

7330

Force a cold reset of the card. If the card fails again, send the card for repair.

26

Test blocked during software download (test-blk-swdownload)

Equip

Min

NSA

7330

Test requests are blocked during software downloads to a GENC-F card.

Wait until the download is complete before starting a test (test requests are temporarily blocked while a software download is in progress). Reset the GENC-F card (test requests are blocked when a software download has failed).

27

Test blocked because software download failed (test-blk-faildownload)

Equip

Maj

NSA

7330

Test requests are blocked when the software download to a GENC-F card has failed.

Alarm type = PlugInUnit (3); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 0 (4 of 34) No defects No defects

TAP 104-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 3 Alarm name (CLI) Card-type mismatch alarm (board-mismatch) Class Equip Sev. Min SA NSA

NE type 7392 7330

Description

Troubleshooting recommendations Check the configuration.

An LT unit is detected, but the actual unit type is unknown or differs from the planned unit type. This alarm applies to all unit types: NT, LT, and ACU units.

Waiting for software (waiting-for-sw)

Equip

Maj

NSA

7302 7330

This system cannot download all the applicable software files (supported by the active OSWP) to a card because of any of the following reasons.

Check the configuration. Download the software and wait until the software download is complete.

The card detected belongs to a card type that the active OSWP does not support. The card detected belongs to a card type that the active OSWP supports but one or more of the applicable software files are no longer available on the file disk of the NT unit.

This alarm applies only to LT units and GENC-F cards. 8 Temperature exceeded (temp-exceeded) Equip Maj NSA 7302 7330 The temperature threshold on the unit is exceeded. This alarm applies to NT and LT units. In remote units, the cause may be a dirty fan filter. The unit has powered off as a result of temperatures that are too high. This alarm applies only to LT units. The plug-in unit is disconnected from the system as a means of defense. The reason for disconnecting depends on the plug-in unit type and the cause of the failure. Unit is planned, no unit is detected, but a unit has been detected at least once since it was planned. This alarm applies to all unit types: NT, EDSE-A, SATU-A, LT, and ACU units. (5 of 34) Check the fans and restart the unit. For remote units, check for a dirty fan dust filter.

12

Temperature shutdown alarm (temp-shutdown)

Equip

Maj

SA

7302 7330

Check the ambient temperature. Check the operation of the fans. Check the unit. Replace the unit.

13

Defense alarm (defense)

Equip

Crit

SA

7302 7330

14

Card missing alarm (board-missing)

Equip

Maj

SA

7302 7330

Verify that the unit is present.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-7

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 15 Alarm name (CLI) Card installation missing alarm (board-instl-missing) Class Equip Sev. Min SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Insert the unit.

Unit is planned, no unit is detected, and no unit has ever been detected since it was planned. This alarm applies to all unit types: NT, LT, and ACU units.

16

Card initialization alarm (board-init)

Equip

Maj

SA

7302 7330

A unit initialization failure has been detected. This alarm applies only to LT units and GENC-F cards. The number of unit resets within a certain timeframe exceeded the threshold. This alarm applies only to LT units. Power to the external power supply failed. SEM is running on battery power. External SEM power supply or the batteries failed. The external ac power supply can still provide power, but needs to be checked to ensure uninterruptible power service. The LT unit has reset (alarm ON followed by alarm OFF), or there is a communication failure (alarm ON).

Force a cold reset of the unit. If this fails, repair the unit. Force a cold reset of the unit. If this fails, repair the unit.

17

Card reset protection (board-reset-prot)

Equip

Maj

SA

7302 7330

28

SEM external power failure (sem-power-fail)

Equip

Crit

SA

7330

Check the power to the external power supply.

29

SEM external power supply failure (sem-ups-fail)

Equip

Crit

SA

7330

Check the external power supply.

30

Card reset or communication failure (board-reset-cf)

Equip

Maj

SA

7302 7330

Check cabling if alarm is persistent. If alarm toggles frequently, the card will go in Card Reset Protection mode (alarm 3, 17) and power down. Check the SHub uplink cable for loose contacts or missing connections.

31

SHub uplink breakdown (shub-uplink)

Equip

Crit

SA

7302 7330

The SHub uplink is broken. The alarm is forwarded to the NT, then to the ACU.

Alarm type = ATM (8); Index1 = ifIndex of ATM physical port, Index2 = see specific alarm number 0 1 No defects Connection alarm Equip Maj SA No defects A planned VPI/VCI could not be marked because of hardware problems. Index2 = VPC This alarm is not currently supported on the system. 2 Cell discarded in the upstream direction (cell-discard-up) QoS Min SA 7302 7330 ATM cell discarded in the upstream direction. Index2 = VPI/VCI Report mode = disabled Logging mode = disabled (6 of 34) No local repair action. Sender must lower shaping rate.

TAP 104-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 3 Alarm name (CLI) Cell discarded in the downstream direction (cell-discard-down) Class QoS Sev. Min SA SA

NE type 7302 7330

Description

Troubleshooting recommendations No local repair action. Sender must lower shaping rate.

ATM cell discarded in the downstream direction. Index2 = VPI/VCI Report mode = disabled Logging mode = disabled

Duplicate MAC address from this pvc (mac-conflict)

Com

Min

SA

Duplicate MAC address from this PVC (the port with the latter coming MAC address caused the conflict). Detailed information, such as the conflicting MAC address and the port on which the MAC address was first learned, can be retrieved with the diagnostics tool. Index2 = VPI/VCI Report mode = disabled This alarm is not currently supported by the system.

Alarm type = CustomizableAlarm (10); Index1 = rack ID (position of the rack), Index2 = not used 0 1 No defects Customizable alarm 1 (custom1) 2 Customizable alarm 2 (custom2) 3 Customizable alarm 3 (custom3) 4 Customizable alarm 4 (custom4) 5 Customizable alarm 5 (custom5) Envir Ind NSA 7302 Envir Ind NSA 7302 Envir Ind NSA 7302 Envir Ind NSA 7302 Envir Ind NSA 7302 No defects Customizable alarm 1 alarm Customizable alarm 2 alarm Customizable alarm 3 alarm Customizable alarm 4 alarm Customizable alarm 5 alarm

Alarm type = CustomizableAlarm (10); Index1 = eqptHolderID (shelf index in equipment holder table), Index2 = not used 0 11 No defects HE customizable alarm 1 (he-custom1) 12 HE customizable alarm 2 (he-custom2) 13 HE customizable alarm 3 (he-custom3) (7 of 34) Envir Ind NSA 7330 Envir Ind NSA 7330 Envir Ind NSA 7330 No defects Host/expansion customizable alarm 1 alarm Host/expansion customizable alarm 2 alarm Host/expansion customizable alarm 3 alarm

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-9

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 14 Alarm name (CLI) HE customizable alarm 4 (he-custom4) 15 HE customizable alarm 5 (he-custom5) 16 HE customizable alarm 6 (he-custom6) Envir Ind NSA Envir Ind NSA Class Envir Sev. Ind SA NSA

NE type 7330

Description

Troubleshooting recommendations

Host/expansion customizable alarm 4 alarm Host/expansion customizable alarm 5 alarm Host/expansion customizable alarm 6 alarm

7330

7330

Alarm type = IMA-group (13); Index1 = IfIndex of IMA-group, Index2 = not used 0 1 No defects Far-end starting up (ima-grp-fe-su) 2 Far-end failed configuration (ima-grp-fe-cfg) 3 Near-end failed configuration (ima-grp-ne-cfg) 4 Insufficient number of links at far-end (ima-grp-fe-nl) 5 Insufficient number of links at near-end (ima-grp-ne-nl) 6 Far-end is blocked (ima-grp-fe-blk) Com Min SA 7302 7330 Com Min SA 7302 7330 Com Min SA 7302 7330 There is an insufficient number of links at the far-end. There is an insufficient number of links at the near-end. The far-end is blocked. Com Min SA 7302 7330 The near-end is not configured properly. Com Min SA Com Min SA 7302 7330 7302 7330 The far-end is not configured properly. No defects The far-end is starting up. Check the IMA group configuration at the far-end. Check which configurations are supported at the near-end and the far-end. Check which configurations are supported at the near-end and the far-end. Check the status of the links at the far-end.

Check the status of the links at the near-end.

Check the status of the IMA group at the far-end.

Alarm type = IMA-link (14); Index1 = IfIndex of IMA-link, Index2 = not used 0 1 No defects Failure in link facility Com Min SA No defects There is a failure in the link facility. This alarm is not currently supported on the system. 2 Loss of IMA frame (ima-lnk-lif) 3 Link out of delay synchronization (ima-lnk-lods) 4 Link misconnect (ima-lnk-misc) (8 of 34) Com Min SA 7302 7330 There is a connection problem in the link. Com Min SA Com Min SA 7302 7330 7302 7330 One or more IMA frames are lost. The link is out of delay synchronization. Check the clock associated with this link. Check the clock configuration for the associated group. Check the link configuration at the far-end.

TAP 104-10

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 5 Alarm name (CLI) Link remote failure indication (ima-lnk-rfi) 6 Fault in link facility (ima-lnk-fault) 7 Transmission blocked at far-end (ima-lnk-txblk) 8 Reception blocked at far-end (ima-lnk-rxblk) Com Min SA Com Min SA Com Min SA Class Com Sev. Min SA SA

NE type 7302 7330 7302 7330 7302 7330 7302 7330

Description

Troubleshooting recommendations Check the state of the associated facility.

There is a remote link failure.

There is a fault in the link facility. The transmission is blocked because of a problem at the far-end. The reception is blocked because of a problem at the far-end.

Check for problems with the associated facility. Check the link configuration at the far-end. Check the link configuration at the far-end.

Alarm type = Redundancy (20); Index1 = not used, Index2 = not used 0 1 No defects Switchover capability lost (loss-over-cap) Equip Maj 7302 7330 No defects The switchover capability in a redundant system has been lost. Check link on standby NT. Check standby cards. Wait for Quench timeout.

Alarm type = SHDSL (23); Index1 = ifIndex of SHDSL physical port, Index2 = device ID 0 1 No defects Loss of signal on network side on first pair (shdsl-n-los-1) 2 Loss of signal on customer side on first pair (shdsl-c-los-1) 3 Loss of synchronization on network side on first pair (shdsl-n-losw-1) 4 Loss of synchronization on customer side on first pair (shdsl-c-losw-1) 5 Loop attenuation alarm on network side on first pair (shdsl-n-aten-1) Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA No defects Loss of signal on the network side on the first pair. This alarm is not currently supported on the system. Loss of signal on the customer side on the first pair. This alarm is not currently supported on the system. Loss of the synchronization word on the network side on the first pair. This alarm is not currently supported on the system. Loss of the synchronization word on the customer side on the first pair. This alarm is not currently supported on the system. Loop attenuation alarm on the network side on the first pair. This alarm is not currently supported on the system.

(9 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-11

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 6 Alarm name (CLI) Loop attenuation alarm on customer side on first pair (shdsl-c-aten-1) 7 SNR margin alarm on network side on first pair (shdsl-n-snr-1) 8 SNR margin alarm on customer side on first pair (shdsl-c-snr-1) 9 DC continuity fault on network side on first pair (shdsl-n-dccont-1) 10 DC continuity fault on customer side on first pair (shdsl-c-dccont-1) 11 Loopback active on network side (shdsl-n-loopback) 12 Loopback active on customer side (shdsl-c-loopback) Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Class Com Sev. Min SA SA

NE type

Description

Troubleshooting recommendations

Loop attenuation alarm on the customer side on the first pair. This alarm is not currently supported on the system.

Signal-to-noise margin alarm on the network side on the first pair. This alarm is not currently supported on the system.

Signal-to-noise margin alarm on the customer side on the first pair. This alarm is not currently supported on the system.

There is a DC continuity fault on the network side on the first pair. This alarm is not currently supported on the system.

There is a DC continuity fault on the customer side on the first pair. This alarm is not currently supported on the system.

7302

Loopback is active on the network side.

Testing is in progress.

7302

Loopback is active on the customer side. Report mode = disabled Logging mode = disabled

Testing is in progress.

13

Configuration error (shdsl-conferr)

Com

Min

SA

7302

There is a configuration error. Loss of ATM cell delineation

Check the configuration parameters supported by the device. Check the clock subsystem or the ATM configuration. Check the power supply at the STU-R.

14

Loss of ATM cell delineation (shdsl-atm-lcd)

Com

Min

SA

7302

15

Loss of power at STU-R (shdsl-lpr)

Com

Min

SA

7302

Loss of power at STU-R

16

Unable to disable STU-R access (shdsl-secu-err)

Com

Min

SA

7302

Unable to disable STU-R access

Check for devices that do not support disabling the STU-R access. Check the equipment.

17

Device fault (shdsl-dev-fault)

Equip

Min

SA

7302

Device fault

18

No ATM cell delineation (shdsl-atm-ncd)

Com

Min

SA

7302

No ATM cell delineation

Check the clock subsystem or the ATM configuration.

(10 of 34)

TAP 104-12

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 19 Alarm name (CLI) Loss of signal on network side on second pair (shdsl-n-los-2) 20 Loss of signal on customer side on second pair (shdsl-c-los-2) 21 Loss of synchronization on network side on second pair (shdsl-n-losw-2) 22 Loss of synchronization on customer side on second pair (shdsl-c-losw-2) 23 Loop attenuation alarm on network side on second pair (shdsl-n-aten-2) 24 Loop attenuation alarm on customer side on second pair (shdsl-c-aten-2) 25 SNR margin alarm on network side on second pair (shdsl-n-snr-2) 26 SNR margin alarm on customer side on second pair (shdsl-c-snr-2) 27 DC continuity fault on network side on second pair (shdsl-n-dccont-2) 28 DC continuity fault on customer side on second pair (shdsl-c-dccont-2) Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Class Com Sev. Min SA SA

NE type

Description

Troubleshooting recommendations

Loss of signal on the network side on the second pair. This alarm is not currently supported on the system.

Loss of signal on the customer side on the second pair. This alarm is not currently supported on the system.

Loss of the synchronization word on the network side on the second pair. This alarm is not currently supported on the system.

Loss of the synchronization word on the customer side on the second pair. This alarm is not currently supported on the system.

Loop attenuation alarm on the network side on the second pair. This alarm is not currently supported on the system.

Loop attenuation alarm on the customer side on the second pair. This alarm is not currently supported on the system.

Signal-to-noise margin alarm on the network side on the second pair. This alarm is not currently supported on the system.

Signal-to-noise margin alarm on the customer side on the second pair. This alarm is not currently supported on the system.

There is a DC continuity fault on the network side on the second pair. This alarm is not currently supported on the system.

There is a DC continuity fault on the customer side on the second pair. This alarm is not currently supported on the system.

(11 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-13

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. Alarm name (CLI) Class Sev. SA

NE type

Description

Troubleshooting recommendations

Alarm type = EthItf (24); Index1 = ifIndex of Ethernet port, Index2 = see specific alarm number 0 1 No defects IP address conflict on Ethernet port (eth-itf-ip-addr-cnflct) Com Crit NSA No defects IP address conflict on Ethernet port. This alarm is not currently supported on the system.

Alarm type = SwMgnt (29); Index1 = eqptSlotId (index in equipment card table for the NT), Index2 = not used 0 1 No defects Implicit software rollback (sw-rollback) Proc Maj SA 7302 7330 No defects The system cannot make the NotActive OSWP and linked database operational (although no error in the database is detected). The system performs an implicit rollback to the previous active OSWP (and linked database). The system cannot make the selected OSWP and linked database operational (an error is detected in the linked database). The system comes up with the selected OSWP and the previous linked database (if possible). The system cannot fetch a specific file from the corresponding file server. The name of the file that caused the failure is sent with the alarm. This alarm is not currently supported by the system. Alarm type = TmpFilter (34); Index1 = 0, Index2 = 0 Note: These values are inherited from the related basic alarm 0 1 No defects Derived alarm for temporal filter (der-temp1) Com Ind NSA 7302 7330 No defects Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled 2 Derived alarm for temporal filter (der-temp2) Com Ind NSA 7302 7330 Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled 3 Derived alarm for temporal filter (der-temp3) Com Ind NSA 7302 7330 Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled (12 of 34) Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Remove the corrupted OSWP (abort operation). Download the desired OSWP again. Activate the downloaded OSWP.

Implicit database rollback (db-rollback)

Proc

Maj

SA

7302 7330

Download the desired database again.

Autofetch failure

Proc

Min

NSA

TAP 104-14

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 4 Alarm name (CLI) Derived alarm for temporal filter (der-temp4) Class Com Sev. Ind SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter.

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

Derived alarm for temporal filter (der-temp5)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

Derived alarm for temporal filter (der-temp6)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

Derived alarm for temporal filter (der-temp7)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

Derived alarm for temporal filter (der-temp8)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

Derived alarm for temporal filter (der-temp9)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

10

Derived alarm for temporal filter (der-temp10)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

11

Derived alarm for temporal filter (der-temp11)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

12

Derived alarm for temporal filter (der-temp12)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

13

Derived alarm for temporal filter (der-temp13)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

14

Derived alarm for temporal filter (der-temp14)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

(13 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-15

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 15 Alarm name (CLI) Derived alarm for temporal filter (der-temp15) Class Com Sev. Ind SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter.

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

16

Derived alarm for temporal filter (der-temp16)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

17

Derived alarm for temporal filter (der-temp17)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

18

Derived alarm for temporal filter (der-temp18)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

19

Derived alarm for temporal filter (der-temp19)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

20

Derived alarm for temporal filter (der-temp20)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

21

Derived alarm for temporal filter (der-temp21)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

22

Derived alarm for temporal filter (der-temp22)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

23

Derived alarm for temporal filter (der-temp23)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

24

Derived alarm for temporal filter (der-temp24)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

25

Derived alarm for temporal filter (der-temp25)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

(14 of 34)

TAP 104-16

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 26 Alarm name (CLI) Derived alarm for temporal filter (der-temp26) Class Com Sev. Ind SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter. Check the cause of the related basic alarm. Check the setting of the related temporal filter.

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

27

Derived alarm for temporal filter (der-temp27)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

28

Derived alarm for temporal filter (der-temp28)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

29

Derived alarm for temporal filter (der-temp29)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

30

Derived alarm for temporal filter (der-temp30)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

31

Derived alarm for temporal filter (der-temp31)

Com

Ind

NSA

7302 7330

Derived alarm for temporal filter. Report mode = disabled Logging mode = disabled

Alarm type = SpaFilter (35); Index1 = 1, Index2 = not used 0 1 No defects Derived alarm for spatial filter (der-spa1) Com Ind NSA 7302 7330 No defects Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled 2 Derived alarm for spatial filter (der-spa2) Com Ind NSA 7302 7330 Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled 3 Derived alarm for spatial filter (der-spa3) Com Ind NSA 7302 7330 Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled 4 Derived alarm for spatial filter (der-spa4) Com Ind NSA 7302 7330 Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled 5 Derived alarm for spatial filter (der-spa5) Com Ind NSA 7302 7330 Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled (15 of 34) Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-17

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 6 Alarm name (CLI) Derived alarm for spatial filter (der-spa6) Class Com Sev. Ind SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter.

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

Derived alarm for spatial filter (der-spa7)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

Derived alarm for spatial filter (der-spa8)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

Derived alarm for spatial filter (der-spa9)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

10

Derived alarm for spatial filter (der-spa10)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

11

Derived alarm for spatial filter (der-spa11)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

12

Derived alarm for spatial filter (der-spa12)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

13

Derived alarm for spatial filter (der-spa13)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

14

Derived alarm for spatial filter (der-spa14)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

15

Derived alarm for spatial filter (der-spa15)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

16

Derived alarm for spatial filter (der-spa16)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

(16 of 34)

TAP 104-18

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 17 Alarm name (CLI) Derived alarm for spatial filter (der-spa17) Class Com Sev. Ind SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter.

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

18

Derived alarm for spatial filter (der-spa18)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

19

Derived alarm for spatial filter (der-spa19)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

20

Derived alarm for spatial filter (der-spa20)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

21

Derived alarm for spatial filter (der-spa21)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

22

Derived alarm for spatial filter (der-spa22)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

23

Derived alarm for spatial filter (der-spa23)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

24

Derived alarm for spatial filter (der-spa24)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

25

Derived alarm for spatial filter (der-spa25)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

26

Derived alarm for spatial filter (der-spa26)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

27

Derived alarm for spatial filter (der-spa27)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

(17 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-19

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 28 Alarm name (CLI) Derived alarm for spatial filter (der-spa28) Class Com Sev. Ind SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter. Check the cause of the related basic alarm. Check the setting of the related spatial filter.

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

29

Derived alarm for spatial filter (der-spa29)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

30

Derived alarm for spatial filter (der-spa30)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

31

Derived alarm for spatial filter (der-spa31)

Com

Ind

NSA

7302 7330

Derived alarm for spatial filter. Report mode = disabled Logging mode = disabled

Alarm type = xDSL (38); Index1 = ifIndex of xDSL physical port, Index2 = not used 0 1 No defects Near-end loss of signal (xdsl-ne-los) 2 Near-end loss of frame (xdsl-ne-lof) 3 Near-end loss of margin (xdsl-ne-lom) 4 Near-end excessive server errors (xdsl-ne-ese) 5 Activation failure configuration error (xdsl-act-cfg-error) Com Crit SA 7302 7330 Com Min SA 7302 7330 Near-end excessive server errors have occurred. The line configuration data cannot be used. Check the physical communication medium. Com Min SA 7302 7330 A near-end loss of margin has occurred. Check the physical line (new distributors). Com Min SA 7302 7330 A near-end loss of frame has occurred. Check modem equipment. Com Min SA 7302 7330 No defects A near-end loss of signal has occurred. Check the physical line.

Update the profile parameters. Ensure that the pilot tones are not marked. If Glite is used, ensure that the bit rates fit within the standard.

Activation failure configuration not feasible (xdsl-act-not-feas)

Com

Maj

SA

7302 7330

The line capacity is not high enough to set up the requested profile.

Check the configuration data. Check the physical line (length and noise). Lower planned upstream bit rate.

Near-end bit rate threshold alarm (xdsl-up-br-reach)

Com

Min

SA

7302 7330

The upstream planned bit rate was not reached after initialization. A near-end cell delineation has occurred.

Near-end no cell delineation (xdsl-ne-ncd)

Com

Min

SA

7302 7330

Check the quality of the line.

(18 of 34)

TAP 104-20

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 9 Alarm name (CLI) Near-end loss of cell delineation (xdsl-ne-lcd) 10 Far-end loss of signal (xdsl-fe-los) 11 Far-end loss of frame (xdsl-fe-lof) 12 Far-end loss of power (xdsl-fe-lpr) 13 Far-end loss of link (xdsl-fe-lol) 14 Far-end loss of margin (xdsl-fe-lom) 15 Far-end - excessive severe errors (xdsl-fe-ese) 16 Activation failure communication problem (xdsl-act-comm) 17 Activation failure No peer modem detected (xdsl-act-modem) 18 Far-end bit rate threshold (xdsl-do-br-reach) 19 Far-end no cell delineation (xdsl-fe-ncd) 20 Far-end loss of cell delineation (xdsl-fe-lcd) 23 Far-end UPBO violation (xdsl-fe-upbo-vio) 24 Activation failure CPE policing (xdsl-fe-cpe-pol) Com Maj SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Maj SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Com Min SA Class Com Sev. Min SA SA

NE type 7302 7330 7302 7330 7302 7330 7302 7330 7302 7330 7302 7330 7302 7330 7302 7330

Description

Troubleshooting recommendations Check the quality of the line.

A loss of near-end cell delineation has occurred.

A far-end loss of signal has occurred. A far-end loss of frame has occurred. A far-end loss of power was detected. A far-end loss of link was detected. A far-end loss of margin has occurred.

Check the physical line.

Check modem equipment.

There is no repair required because this is the normal power-down of CPE. Check the physical line.

Check the physical line (new distributors).

Far-end excessive server errors have occurred.

Check the physical line.

Unsuccessful initialization as a result of communication problems

Check the peer modem type. Check the physical line. Wait until the modem is connected. Check the physical line.

7302 7330

Peer modem not detected

7302 7330 7302 7330 7302 7330 7302 7330 7302 7330

The downstream planned bit rate was not reached after initialization. A far-end cell delineation has occurred.

Lower the planned downstream bit rate.

Check the quality of the line.

A far-end loss of cell delineation has occurred.

Check the quality of the line.

A far-end UPBO violation has occurred.

Check the peer modem type.

There was an activation failure due to CPE policing.

Check the peer modem type.

Alarm type = xDSLTca (39); Index1 = ifIndex of xDSL physical port, Index2 = not used 0 No defects No defects

(19 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-21

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 1 Alarm name (CLI) Near-end TCA alarm errored seconds in 15 min (xtca-ne-es) Class QoS Sev. Min SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the physical line. Check the modem equipment.

The number of errored seconds encountered by the ADSL line in the current 15-minute interval has reached its threshold value. The number of severely errored seconds encountered by the ADSL line in the current 15-minute interval has reached its threshold value. The number of unavailable seconds encountered by the ADSL line in the current 15-minute interval has reached its threshold value. The number of errored seconds encountered by the ADSL line in the current one-day interval has reached its threshold value. The number of severely errored seconds encountered by the ADSL line in the current one-day interval has reached its threshold value. The number of unavailable seconds encountered by the ADSL line in the current one-day interval has reached its threshold value. The number of errored seconds encountered by the ADSL far-end line in the current 15-minute interval has reached its threshold value. The number of severely errored seconds encountered by the ADSL far-end line in the current 15-minute interval has reached its threshold value.

Near-end TCA alarm severely errored seconds in 15 min (xtca-ne-ses)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Near-end TCA alarm unavailable seconds (xtca-ne-uas)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Near-end TCA alarm errored seconds in 1 day (xtca-ne-day-es)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Near-end TCA alarm severely errored seconds in 1 day (xtca-ne-day-ses)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Near-end TCA alarm unavailable seconds in 1 day (xtca-ne-day-uas)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Far-end TCA alarm errored seconds in 15 min (xtca-fe-es)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Far-end TCA alarm severely errored seconds in 15 min (xtca-fe-ses)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

(20 of 34)

TAP 104-22

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 9 Alarm name (CLI) Far-end TCA alarm unavailable seconds (xtca-fe-uas) Class QoS Sev. Min SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check the physical line. Check the modem equipment.

The number of unavailable seconds encountered by the ADSL far-end line in the current 15-minute interval has reached its threshold value. The number of errored seconds encountered by the ADSL far-end line in the current one-day interval has reached its threshold value. The number of severely errored seconds encountered by the ADSL far-end line in the current one-day interval has reached its threshold value. The number of unavailable seconds encountered by the ADSL far-end line in the current one-day interval has reached its threshold value.

10

Far-end TCA alarm errored seconds in 1 day (xtca-fe-day-es)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

11

Far-end TCA alarm severely errored seconds in 1 day (xtca-fe-day-ses)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

12

Far-end TCA alarm unavailable seconds in 1 day (xtca-fe-day-uas)

QoS

Min

NSA

7302 7330

Check the physical line. Check the modem equipment.

Alarm type = bonding (54); Index1 = IfIndex of bonding group, Index2 = not used 0 1 No defects Bonding group upstream planned bit rate threshold (up-plan-bitrate) 2 Bonding group upstream minimum bit rate threshold (up-min-bitrate) 3 Bonding group upstream configuration not feasible (up-config-not-feas) 4 Bonding group downstream planned bit rate threshold (down-plan-bitrate) Com Min SA 7302 7330 Com Maj SA 7302 7330 Com Min SA 7302 7330 Com Min SA 7302 7330 No defects Group upstream actual bit rate is above group upstream minimum bit rate but below group upstream planned bit rate. Group upstream actual bit rate dropped below group upstream minimum bit rate. Group upstream actual bit rate is not high enough to set up the configured group upstream minimum bit rate. Group downstream actual bit rate is above group downstream minimum bit rate but below group downstream planned bit rate. Group downstream actual bit rate dropped below group downstream minimum bit rate. Lower group upstream planned bit rate.

Check physical line. Check line state.

Check configuration data. Check physical line.

Lower group downstream planned bit rate.

Bonding group downstream minimum bit rate threshold (down-min-bitrate)

Com

Min

SA

7302 7330

Check physical line. Check line state.

(21 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-23

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 6 Alarm name (CLI) Bonding group downstream configuration not feasible (down-config-notfeas) 7 Bonding group no peer modem detected (no-peer-cpe) Com Min SA Class Com Sev. Maj SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Check configuration data. Check physical line.

Group downstream actual bit rate is not high enough to set up the configured group downstream minimum bit rate.

7302 7330

CPE modem is not connected to the group lines. This alarm is not currently supported on the system.

Check the modem. Check the physical lines.

Bonding group non-bonding CPE connected (non-bonding-cpe)

Com

Min

SA

7302 7330

The CPE connected does not support bonding.

Check the modem. Check the physical lines.

Bonding group connected to multiple CPEs (multiple-cpes)

Com

Maj

SA

7302 7330

The lines of the bonding group are connected to more than one CPE.

Check the xDSL wiring configuration. Check the CPE. Check the CPE.

10

Bonding group CPE register failure (register)

Com

Maj

SA

7302 7330

A discovery or aggregation register failure is detected. Not all configured lines of the bonding group are actually part of the bonding group.

11

Bonding group Incomplete (group-incomplete)

Com

Min

NSA

7302 7330

Check the xDSL wiring configuration. Check the CPE.

Alarm type = authentication (55); Index1 = ifIndex of interface on which authentication occurs (for example, the bridge port interface for 802.1x, the PPPoE interface for PPPoE), Index2 = not used 0 1 No defects VRF assignment failure (vrf-assign-fail) Proc Maj SA 7302 7330 No defects Failure to assign a VRF for a user session: Check the system configuration. Check the RADIUS server configuration.

unknown VRF: VRF returned by RADIUS server is not locally configured in the system; or no VRF: RADIUS server did not return a VRF while no default VRF is locally configured for the domain.

(22 of 34)

TAP 104-24

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 2 Alarm name (CLI) VLAN assignment failure (vlan-assign-fail) Class Proc Sev. Maj SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Check the system configuration. Check the RADIUS server configuration.

Failure to assign a VLAN for a user session:

unknown VLAN: VLAN returned by RADIUS server is not locally configured in the system; or no VLAN: RADIUS server did not return a VLAN while no default VRF is locally configured for the domain.

IP address pool assignment failure (ip-pool-assign-fail)

Proc

Maj

SA

7302 7330

Failure to assign an IP address pool:

Check the system configuration. Check the RADIUS server configuration.

unknown pool-id: pool-id returned by the RADIUS server is not locally configured in the system; or no pool-id: no pool id is returned by the RADIUS server while no pool is assigned to the domain; or pool administratively locked: pool-id returned by the RADIUS server is administratively locked; or VRF of the pool is not consistent: this can occur in the following cases: RADIUS server returns a pool-id: VRF of the returned pool-id is different from the VRF of the configured domain RADIUS server returns pool-id and VRF: VRF of the returned pool-id is different from the returned VRF

(23 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-25

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 4 Alarm name (CLI) QoS parameters assignment failure (qos-assign-fail) Class Proc Sev. Maj SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Check the system configuration. Check the RADIUS server configuration.

Failure to assign QoS parameters for a user session:

unknown QoS profile: QoS profile returned by the RADIUS server is not locally configured in the system; or QoS parameters syntax error: QoS parameters returned by the RADIUS server contain a syntax error.

IP address assignment failure (ip-addr-assign-fail)

Proc

Maj

SA

7302 7330

Failure to assign IP address for a user session:

Check the system configuration. Check the RADIUS server configuration.

IP address already in use: IP address returned by the RADIUS server is already allocated for another user; or no IP address available: no IP address available in the IP address pool of the domain or in the IP address pool returned by the RADIUS server.

Missing attributes (missing-attributes)

Proc

Maj

SA

7302 7330

RADIUS server should always specify a pool-id when it returns a VRF.

Check the system configuration. Check the RADIUS server configuration.

Alarm type = IpoX (68); Index1 = ifIndex of IpoX interface on which the session takes place, Index2 = not used 0 1 No defects IP address preempt (ip-addr-preempt) Com Maj SA 7302 7330 No defects A new IP session is established with a user IP address previously assigned to another IP session and the previous session has lower or equal precedence with the new one. The previous session is terminated and its IP address preempted. Check IP address pool on DHCP server. Check local IP address pool.

Alarm type = SFP (76); Index1 = ifIndex of IPoX interface on which the session takes place, Index2 = not used 0 1 No defects Host SFP LOS (host-sfp-los) Com Crit SA 7330 No defects Host shelf downlink SFP loss of signal. This alarm applies only to a host ARAM-D shelf. (24 of 34) Check the physical line.

TAP 104-26

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 2 Alarm name (CLI) Host SFP transmit fail (host-sfp-tx-fail) Class Com Sev. Crit SA SA

NE type 7330

Description

Troubleshooting recommendations Check the host shelf SFP module.

Host shelf downlink SFP transmission failure. This alarm applies only to a host ARAM-D shelf.

Host SFP not present (host-sfp-not-prst)

Com

Crit

SA

7330

Host SFP missing. Host shelf downlink SFP detected but later removed. This alarm applies only to a host ARAM-D shelf.

Check the host shelf SFP presence.

Host SFP invalid Alcatel-Lucent ID (host-sfp-inv-id)

Com

Crit

SA

7330

Host shelf downlink SFP does not have a valid Alcatel-Lucent ID. This alarm applies only to a host ARAM-D shelf.

Check the host shelf SFP module ID.

Host SFP control fail (host-sfp-ctrl-fail)

Com

Crit

SA

7330

Host shelf downlink SFP control failure. This alarm applies only to a host ARAM-D shelf.

Check the host shelf SFP module or I2C bus. If control of all host shelf SFPs fails, check the GENC-E or GENC-F. Check for missing host SFP assignment configuration. Check if the remote LT unit is cabled to the wrong host SFP. Check for cabling error. Check for host SFP assignment configuration error.

Host SFP unexpected remote LT (host-sfp-rmtlt)

Equip

Min

NSA

7330

The host SFP is not assigned to any remote LT units but a connection to a remote LT unit is detected.

Host SFP assignment mismatch (host-sfp-mismatch)

Equip

Maj

SA

7330

The detected slot ID of the remote LT unit cabled to the host SFP does not match the assigned remote LT slot ID configured for that host SFP. The actual shelf type of the remote LT unit cabled to the host SFP does not match the planned shelf type of the assigned remote LT unit configured for that host SFP.

Host SFP incompatible shelf (host-sfp-incompt)

Equip

Min

NSA

7330

Check for cabling error. Check for shelf type planning error. Check for assignment configuration error.

Alarm type = SFP (76); Index1 = eqptSlotId of corresponding LT unit in ES, Index2 = not used 0 11 No defects ES SFP loss of signal (exp-sfp-los) 12 ES SFP transmit fail (exp-sfp-tx-fail) Com Crit SA 7330 Com Crit SA 7330 No defects ES SFP loss of signal. This alarm applies only to the ES. ES SFP transmission failure. This alarm applies only to the ES. (25 of 34) Check the ES SFP module. Check the physical line.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-27

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 13 Alarm name (CLI) ES SFP not present (exp-sfp-not-prst) Class Com Sev. Crit SA SA

NE type 7330

Description

Troubleshooting recommendations Check the ES SFP presence.

ES SFP missing. ES SFP detected but later removed. This alarm applies only to the ES.

14

ES SFP invalid Alcatel-Lucent ID (exp-sfp-inv-id)

Com

Crit

SA

7330

ES SFP does not have a valid Alcatel-Lucent ID. This alarm applies only to the ES.

Check the ES SFP module ID.

15

ES SFP control fail (exp-sfp-ctrl-fail)

Com

Crit

SA

7330

The SFP alarm for the ES downlink SFP control failure. This alarm applies only to the ES.

Check the ES SFP module or I2C bus.

Alarm type = LLURelay (78); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 0 1 No defects Wrong applique for LLU (llu-relay-status) Com Maj SA 7302 No defects LLU relay set for some ports, but applique inserted in slot is not compatible with LLU relay. Replace the applique by an applique compatible with the LLU relay.

Alarm type = SHDSL_ISAM (82); Index1 = IfIndex of SHDSL physical port, Index2 = linkID (higher 16 bits) + device ID (lower 16 bits) 0 1 No defects Loss of signal on network side on each pair (shdsl-n-los) 2 Loss of signal on customer side on each pair (shdsl-c-los) 3 Loss of synchronization on network side on each pair (shdsl-n-losw) 4 Loss of synchronization on customer side on each pair (shdsl-c-losw) 5 Loop attenuation alarm on network side on each pair (shdsl-n-aten) 6 Loop attenuation alarm on customer side on each pair (shdsl-c-aten) (26 of 34) Com Min SA 7302 Loop attenuation alarm on the customer side on each pair Check the signal on the customer side. Com Min SA 7302 Loop attenuation alarm on the network side on each pair Check the signal on the network side. Com Min SA 7302 Loss of synchronization word on the customer side on each pair Check the signal on the customer side. Com Min SA 7302 Com Min SA Com Min SA No defects Loss of signal on the network side on each pair. This alarm is not currently supported on the system. Loss of signal on the customer side on each pair. This alarm is not currently supported on the system. Loss of synchronization word on the network side on each pair Check the signal on the network side.

TAP 104-28

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 7 Alarm name (CLI) SNR margin alarm on network side on each pair (shdsl-n-snr) 8 SNR margin alarm on customer side on each pair (shdsl-c-snr) 9 DC continuity fault on network side on each pair (shdsl-n-dccont) 10 DC continuity fault on customer side on each pair (shdsl-c-dccont) Com Min SA Com Min SA Com Min SA Class Com Sev. Min SA SA

NE type 7302

Description

Troubleshooting recommendations Check the signal on the network side.

Signal-to-noise ratio alarm on the network side on each pair

7302

Signal-to-noise ratio alarm on the customer side on each pair

Check the signal on the customer side.

7302

DC continuity fault on the network side on each pair

Check the equipment and wiring on the network side.

7302

DC continuity fault on the customer side on each pair

Check the equipment and wiring on the customer side.

Alarm type = CustomExternalAlarms (83); Index1 = eqptSlodId (index in equipment card table), Index2 = not used 0 1 No defects Customizable external alarm 1 (custextalarm1) 2 Customizable external alarm 2 (custextalarm2) 3 Customizable external alarm 3 (custextalarm3) 4 Customizable external alarm 4 (custextalarm4) 5 Customizable external alarm 5 (custextalarm5) Alarm type = PlugInUnit2 (84); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 0 1 No defects Fan (pluginfan) 2 DC A (plugin-dc-a) 3 DC B (plugin-dc-b) (27 of 34) Equip Maj NSA 7330 Equip Maj NSA 7330 REM DC A voltage low. DC B takes over. REM DC B voltage low. DC A takes over. Check the fuse. Check the cabling. Check the fuse. Check the cabling. Equip Maj NSA 7330 No defects REM fan power alarm Check the REM fan. Equip Maj NSA 7330 REM customizable external alarm 5 Equip Maj NSA 7330 REM customizable external alarm 4 Equip Maj NSA 7330 REM customizable external alarm 3 Equip Maj NSA 7330 REM customizable external alarm 2 Equip Maj NSA 7330 No defects REM customizable external alarm 1

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-29

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 4 Alarm name (CLI) Dying gasp (plugin-dg) Class Equip Sev. Crit SA SA

NE type 7330

Description

Troubleshooting recommendations Check the following at the REM and the cabinet: cabling, fuse, temperature, on and off switch.

REM dying gasp alarm. REM going out of service due to power shutdown. Possible causes: power failure, mains switch off, excessive over temperature, an so on. Applique power supply malfunction. The relays are no longer configurable and are switched to the hardware default position. The LT unit reports an NTR loss event when the NTR signal is not available. An NTR-A loss is reported even when there is no NT unit in the NT-A slot. The LT unit reports an NTR loss event when the NTR signal is not available. An NTR-B loss is reported even when there is no NT unit in the NT-B slot. The test cannot be completed because of missing test equipment. The LT unit is not present or has failed. The test cannot be completed because of missing test equipment. The applique is not present, not compatible or failed, or the LT unit is not compatible with the applique.

Applique power supply failure (apsf-alarm)

Equip

Crit

SA

7302

Check applique power supply.

NTR-A loss (ntr-a-loss)

Equip

Maj

SA

7302 7330

Check the status of the NT-A NTR.

NTR-B loss (ntr-b-loss)

Equip

Maj

SA

7302 7330

Check the status of the NT-B NTR.

ITSC LT unit not present or failed (lt-problem)

Equip

Min

NSA

7330

Verify compatibility with ITSC tests. Force a cold reset of the card. If the card fails again, send the card for repair. Check the applique. Verify compatibility with LT unit for test. Force a cold reset of the card. If the card fails again, send the card for repair.

ITSC applique not present, not compatible, or failed (applique-problem)

Equip

Min

NSA

7330

Alarm type = IntTestSealCur (85); Index1 = ifIndex of xDSL line being sealed, Index2 = not used 0 1 No defects Test exceeded maximum time (test-exceeded-maxtime) 2 No DC termination on line (dc-termination) Equip Min NSA 7330 Proc Min NSA 7330 No defects The test duration exceeded the maximum allowed duration. Try the test again.

The line being sealed with the sealing current is not terminated by a CPE. The sealing current process cannot proceed without DC termination on the CPE equipment.

Verify that the line on the customer side has a proper DC termination. Verify the connections of the test chain.

(28 of 34)

TAP 104-30

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 3 Alarm name (CLI) Sealing current cycle missed (sc-cycle-missed) Class Proc Sev. Min SA NSA

NE type 7330

Description

Troubleshooting recommendations Check the configuration. Check the equipment. Reduce or stop the number of manual ITSC tests to increase the time available for line sealing.

The line assigned to a sealing current interval could not be completed for two consecutive intervals. Possible reasons are:


4 Hazardous voltage detected on the line (hazardous-potential) Equip Maj NSA 7330

ON duration too long too many lines per interval too many lines being tested by operator

A hazardous voltage is detected on the line under test.

Verify the line at the customer side. WARNING: Ensure all proper precautions are taken to prevent injury. Verify the line on the customer side.

FEMF detected on the line (femf)

Equip

Min

NSA

7330

A foreign electromotive force is detected on the line under test. The ITSC card protection is activated for the line under test.

ITSC card protection detected on the line (device-protection)

Equip

Min

NSA

7330

Verify the line on the customer side.

Alarm type = SIP User Agent (98); Index1 = sipUaId (index in SIP user agent table), Index2 = not used 0 1 No defects DHCP server unreachable (dhcp-unreach) 2 SIP proxy server unreachable (proxy-srv-unreach) 3 SIP registrar server unreachable (reg-srv-unreach) Com Crit SA 7302 7330 Com Crit SA 7302 7330 Com Crit SA 7302 7330 No defects The DHCP server is unreachable for the SIP user agent. The SIP proxy server is unreachable for the SIP user agent. The SIP registrar server is unreachable for the SIP user agent. Check the link between the system and the DHCP server. Check the link between the system and the SIP proxy server. Check the link between the system and the SIP registrar server.

Alarm type = SIP PlugInUnit (99); Index1 = eqpSlotId (index in equipment card table), Index2 = not used 0 1 No defects Invalid CDE file (inval-cdefile) Proc Crit SA 7302 7330 No defects The CDE file in the card is invalid. This alarm is raised in the following situations: Contact Alcatel-Lucent technical support at 1-888-252-2832 (1-888-ALCATEC) to get a new load.


(29 of 34)

The CDE file does not exist. The CDE file is of invalid format.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-31

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 2 Alarm name (CLI) Short of resource (short-res) Class Proc Sev. Crit SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Wait until one of the busy calls is terminated.

The card is short of resources for more calls. For example, if there are 24 user ports already in conversation using G.729, the card does not have any resources left to accept more calls on any other user ports.

Alarm type = SIP Termination (100); Index1 = ifIndex of PSTN physical port, Index2 = not used 0 1 No defects Unknown SIP subscriber (unknown-sub) Com Maj SA 7302 7330 No defects The SIP subscriber information configured in the SIP termination does not exist on the SIP application server. The current threshold of the physical line of the port is exceeded. The usual root causes are: Verify if the directory number, the user name, or the URI of the SIP termination is valid. Check the cabling of the port.

Ground key (ground-key)

Equip

Maj

SA

7302 7330


3 Port high temperature (port-hightemp) Equip Maj SA 7302 7330

The tip and ring are shorted together. The tip is connected to the ground or to an ac source. The ring is connected to a source of high voltage or to ac. Check the ambient temperature. Check the operation of the fans. Check the port.

The temperature threshold on the physical PSTN port is exceeded. The port is automatically shut down.

Alarm type = NonAlcateldev (104); Index1 = not used, Index2 = not used 0 1 No defects No environment box (loss-env-mon) Equip Crit NSA 7302 7330 No defects The environment box does not exist or is not alive. Verify if there is an environment box.

Alarm type = FileTransfer (105); Index1 = file server ID (IP address), Index2 = not used 0 1 No defects File server unavailable (fileserv-unavailable) Com Maj NSA 7302 7330 No defects The system is not able to connect to the file server for a file transfer. Check if the file transfer server is correctly configured. Check the network-to-file transfer server. Alarm type = TrafficOverflow (106); Index1 = eqptSlotId (index in NT equipment card table), Index2 = not used 0 1 No defects LT load overflow (fanout) (30 of 34) QoS Min SA 7302 7330 No defects LT load overflow Check the LT load.

TAP 104-32

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 2 Alarm name (CLI) Upstream load overflow (up-overflow) 3 Upstream load to OBC overflow (upobc-overflow) 4 Downstream load to OBC overflow (dwobc-overflow) 5 Downstream load overflow (dw-overflow) 6 BE and CF packets dropped exceeds threshold (lwpri-overflow) QoS Min SA QoS Min SA QoS Min SA QoS Min SA Class QoS Sev. Min SA SA

NE type 7302 7330 7302 7330 7302 7330 7302 7330 7302 7330

Description

Troubleshooting recommendations Check the LT load in upstream.

Upstream load overflow

Upstream load to OBC overflow

Check the LT load to OBC in upstream.

Downstream load to OBC overflow

Check the LT load to OBC in downstream.

Downstream load overflow

Check the LT load in downstream.

The number of BE and CF packets dropped exceeds the threshold.

Check the voice and video loads.

Alarm type = EthTca (107); Index1 = ifIndex of Ethernet interface, Index2 = not used 0 1 No defects LOS errors encountered in current 15-min interval has reached threshold value (etca-los) 2 FCS errors encountered in current 15-min interval has reached threshold value (etca-fcs) 3 LOS errors encountered in current 1-day interval has reached threshold value (etca-day-los) 4 FCS errors encountered in current 1-day interval has reached threshold value (etca-day-fcs) QoS Min NSA 7302 7330 QoS Min NSA 7302 7330 QoS Min NSA 7302 7330 QoS Min NSA 7302 7330 No defects The number of LOS errors encountered by the Ethernet interface in the current 15-minute interval has reached its threshold value. The number of FCS errors encountered by the Ethernet interface in the current 15-minute interval has reached its threshold value. The number of LOS errors encountered by the Ethernet interface in the current one-day interval has reached its threshold value. The number of FCS errors encountered by the Ethernet interface in the current one-day interval has reached its threshold value. Check the physical line. Check the modem equipment.

Check the physical line. Check the modem equipment.

Check the physical line. Check the modem equipment.

Check the physical line. Check the modem equipment.

Alarm type = EthSFP (108); Index1 = ifIndex of Ethernet interface, Index2 = not used 0 1 No defects Ethernet SFP LOS (user-sfp-los) 2 Ethernet SFP transmit fail (user-sfp-tx-fail) Com Min SA Com Min SA 7302 7330 7302 7330 User SFP transmission failure Check the SFP module. No defects User SFP loss of signal Check the physical line.

(31 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-33

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 3 Alarm name (CLI) Ethernet SFP not present (user-sfp-not-prst) Ethernet SFP invalid Alcatel-Lucent ID (user-sfp-inv-id) Class Com Sev. Min SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Check if the SFP is present. Check the module ID of the SFP.

User SFP is not detected.

Com

Min

SA

7302 7330

User SFP does not have a valid Alcatel-Lucent ID.

Alarm type = L2Forward (109); Index1 = ifIndex of bridge port, Index2 = see specific alarm number 0 1 No defects Duplicate MAC address (dupadr) Com Min SA 7302 7330 No defects Duplicate MAC address on the bridge port indicated by Index1. The bridge port with the next MAC address is causing the conflict. Index2 = Layer 2 forwarder ID (VLAN ID) Alarm type = QueueCounter (112); Index1 = ifIndex of physical line, Index2 = queue index 0 1 No defects Packets dropped by queue exceed threshold (queue-drop) 2 Queue load exceeds threshold (queue-load) Alarm type = MEGACOMediaGateway (113); Index1 = slot ID of voice package server unit, Index2 = mediaGatewayId (identifier of the affected media gateway) 0 1 No defects Media gateway controller unreachable (2) Com Crit SA 7302 7330 No defects Contact is lost with the media gateway controller. Check the network connections. QoS Min SA 7302 7330 The queue load exceeds the threshold. Check the corresponding queue load. QoS Min SA 7302 7330 No defects The number of packets dropped by the queue exceeds the threshold. Check the corresponding queue load. No special repair action required. Open or close the conflicted port manually if needed.

Alarm type = MEGACOSignalingGateway (114); Index1 = slot ID of voice package server unit, Index2 = signallingGatewayId (identifier of the affected signalling gateway) 0 1 No defects Signalling gateway controller unreachable (2) Com Crit SA 7302 7330 No defects Contact is lost with the signalling gateway controller. Check the network connections.

Alarm type = MEGACOPlugInUnit (115); Index1 = slot or equipment ID of voice package server unit(3), Index2 = accessBoardId (identifier of the slot holding the voice package server unit) 0 1 No defects LT unit unreachable from server card (2) Com Crit SA 7302 7330 No defects The LT unit cannot be reached. Check the interface between the voice package server unit and the VoIP units. No action required.

LT unit already associated (2)

Com

War

SA

7302 7330

The LT unit is associated with another voice package server unit.

(32 of 34)

TAP 104-34

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 3 Alarm name (CLI) Invalid LT unit CDE file (2) Class Proc Sev. Maj SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Download the correct card CDE again.

The CDE file in the card is invalid. This alarm is raised in the following situations:


4 CDE download to LT unit failure (2) Proc Maj SA 7302 7330

The CDE file does not exist. The CDE file is of invalid format. Lock or unlock the VoIP unit. Reset the VoIP unit. The card software is automatically downloaded to the LT unit. Check the configuration of the provisioned card against the configuration of the equipped card.

The download of the card software to an LT unit did not succeed.

LT unit type mismatch


(2)

Equip

Maj

SA

7302 7330

An LT unit is detected, but the actual unit type is unknown or differs from the planned unit type.

Alarm type = MEGACOTermination (116); Index1 = slot or equipment ID of voice package server unit (3), Index2 = accTerminationUserPortId (identifier of the user port) 0 1 No defects Unknown media gateway controller subscriber (2) Com Crit SA 7302 7330 No defects A subscriber profile is defined in the voice package server unit but not in the media gateway controller. The current threshold for the physical line of the port was exceeded. The usual causes are: Check the user port identification.

Voice port ground key


(2)

Equip

Crit

SA

7302 7330

Perform a line test.


3 Voice port high temperature (2) Equip Crit SA 7302 7330

Tip and ring are shorted together. Tip is connected to the ground or the ac source. Ring is connected to a source of high voltage or to the ac source. Perform a line test.

The temperature threshold on the physical PSTN port was exceeded. The port is automatically shut down. The first link layer for an ISDN subscriber failed to activate. The current on the physical PSTN port exceeds the maximum allowable current.

L1 activation failure (2)

Equip

Crit

SA

7302 7330

Perform a line test.

Overcurrent (2)

Equip

Crit

SA

7302 7330

Perform a line test.

(33 of 34)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-35

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) No. 6 Alarm name (CLI) Line showering (2) Class Com Sev. Crit SA SA

NE type 7302 7330

Description

Troubleshooting recommendations Check the subscriber line connections.

One of the lines assigned to a subscriber is connected to another subscriber.

Alarm type = MEGACOSignalingLt (117); Index1 = slot ID of voice package server unit, Index2 = not used 0 1 No defects Invalid gateway CDE file (2) Voice signaling card persistent data loss
(2)

Proc

Crit

SA

7302 7330

No defects The card software file does not exist or is in an invalid format. The voice package server unit has lost all persistent data after restart. The card is not configured. The voice package server unit has reached a 90% full level. The voice package server unit is not able to activate the last downloaded database.

Download the correct CDE file for the voice package server unit again. Reconfigure the system.

Equip

Crit

SA

7302 7330

Voice signaling card disk 90% full (2) Voice signaling card implicit database rollback (2)

Equip

Maj

SA

7302 7330

Delete the unused data on the voice package server unit. Download the database again. Download the correct database.

Proc

Maj

SA

7302 7330

(34 of 34) Notes (1) No rack shutdown occurs on an ARAM-D shelf that has the following PWIO-B cards installed: 3FE 24323 AC or 3FE 24323 AD.
(2) (3)

This alarm cannot be viewed using CLI. The format is rack number/shelf number/slot number/equipment number. The equipment number is an identifier of the NE of the voice package server unit.

Table TAP 104-2: SHub alarm definitions for the 7302 ISAM and the 7330 ISAM FTTN
Alarm (grouped by alarm type) (1) No. Name (CLI) Class Sev. SA NE type Description Troubleshooting recommendations

Alarm type = LANX (51); Index1 = not used, Index2 = not used 0 1 SHub fan failure (fan) 2 SHub power fan failure (power-fan) 3 SHub database restore (db-restore) Eqp Maj SA 7302 7330 Eqp Maj NSA Eqp Maj NSA No defects SHub fan failure. This alarm is not currently supported on the system. SHub power fan failure. This alarm is not currently supported on the system. The SHub database restore has failed. Check local flash. Check remote file system. Check availability of MIB database.

(1 of 4)

TAP 104-36

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) (1) No. 4 Name (CLI) Emergency reboot (reboot) Class Eqp Sev. Maj SA NSA

NE type 7302 7330

Description

Troubleshooting recommendations Check local flash. Check remote file system. Check availability of software package. Check SNTP server.

The SHub has rebooted from the emergency boot package.

SHub SNTP Communication Lost (sntp-comm)

Eqp

Maj

NSA

7302 7330

SHub SNTP communication lost. The SNTP server does not respond to the requested messages from the SHub. An ARP request has been sent for a statistically configured next hop, but no ARP reply has been received in the specified time interval. Index1 = VRF ID Index2 = IP address of next hop Report mode = disabled

No ARP reply received for next IP hop (no-arp-reply)

Com

Maj

SA

7302 7330

Check existence of configured Nexthop. Check connection with configured Nexthop.

Alarm type = ethLanx (52); Index1 = port identification of SHub Ethernet port, Index2 = see specific alarm number 0 1 Ethernet link down (ether-link-down) 2 Ethernet frame discarded QoS Min SA Com Crit SA 7302 7330 No defects The Ethernet link is down. Index2 = not used. The Ethernet frame has been discarded due to buffer overflow. Index2 = not used This alarm is not currently supported by the system. 3 SHub MAC conflict (mac-conflict) COM Min SA 7302 7330 Duplicate MAC address from Ethernet port of LAN switch. Index1 = port with the later coming MAC address that causes conflict. Index2 = VLAN ID of domain on which the conflict happened. 4 SHub MAC learning Com Min SA The MAC address cannot be learned, because it is learned on a high-priority Ethernet port of the LAN switch. Index1 = the port with the lower priority Index2 = VLAN ID (the VLAN domain on which the conflict occurred) This alarm is not currently supported on the system. (2 of 4) No special repair action required. The conflict MAC address can be manually prohibited or permitted if needed. Check the Ethernet link.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-37

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) (1) No. Name (CLI) Class Sev. SA

NE type

Description

Troubleshooting recommendations

Alarm type = OSPF (69); Index1 = VRF-ID (VRF unique ID), Index2 = see specific alarm number 0 1 OSPF interface configuration error (ospf-itf-err) Com Min NSA 7302 7330 No defects Received a packet with: Check the configuration of the OSPF and OSPF interface. Check the configuration on the IP interface. Check the OSPF hello packets received on the OSPF interface.

OSPF version mismatch area mismatch (area ID or subnet ID not matching) netmask mismatch hello interval mismatch dead interval mismatch options mismatch

Index2 = interface index 2 OSPF interface authentication error (ospf-auth-err) Com Min NSA 7302 7330 Received a packet with:

authentication type mismatch authentication failure

Check the authentication type and password configured on the OSPF area and the OSPF interface. Check the authentication time range. Check the connection between the RIP interface and the cable. Do not input external routes anymore, except for major external network routes. Configure the OSPF area as a stub area if possible. Remove some external routes in the OSPF domain. Configure the OSPF area as a stub area if possible. Only input major external network routes.

Index2 = interface index 3 OSPF interface received bad packet (ospf-rx-bad-err) 4 OSPF LSDB approaching overflow (ospf-lsdb-oflow-90) Com Maj NSA 7302 7330 Com Crit SA 7302 7330 Received a packet that cannot be parsed. Index2 = interface index The external LSA database has reached 90% of the external LSA limit. Index2 = LSDB limit (percentage utilized) 5 OSPF LSDB overflow (ospf-lsdb-oflow) Com Maj NSA 7302 7330 The external LSA count has reached the external LSA overflow limit. Index2 = LSDB limit (percentage used)

OSPF neighbor state change (ospf-nhbr-statchg)

Com

Min

SA

7302 7330

An OSPF neighbor connection is newly established or dismantled. Index2 = interface index (interface on which the neighbor was learned)

Check the OSPF neighbor table.

If the neighbor is established correctly, the situation is normal. If the neighbor is down unexpectedly, check the OSPF process status or the interface-related parameters.

(3 of 4)

TAP 104-38

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TAP 104 Fault isolation and troubleshooting

Alarm (grouped by alarm type) (1) No. 7 Name (CLI) OSPF interface state change (ospf-itf-statchg) Class Com Sev. Min SA SA

NE type 7302 7330

Description

Troubleshooting recommendations No special repair action required. Check and modify the OSPF interface parameters if desired to change the OSPF interface status.

The OSPF interface status has changed (the DR or BDR may have been changed according to this OSPF interface). Index2 = interface index (interface on which the neighbor was learned)

Alarm type = RIP (70); Index1 = VRF ID (VRF unique ID), Index2 = interface index 0 1 RIP interface configuration error (rip-config-err) Com Min SA 7302 7330 No defects Received a packet with: Check the configuration of the RIP send and receive version. Check the configuration of the IP interface. Check the RIP request and update packets received on the interface. 2 RIP interface authentication error (rip-auth-fail) Com Min SA 7302 7330 Received a packet with:

RIP version mismatch netmask mismatch

authentication type mismatch authentication failure

Check the authentication type and password configuration of the RIP interface. Check the authentication time range. Check the connection between the RIP interface and the cable.

RIP interface received bad packet (rip-rcv-bad-pkt)

Com

Min

SA

7302 7330

Received a packet that cannot be parsed

Alarm type = LANXuplinkgroup (75); Index1 = uplink group number, Index2 = not used 0 1 SHub uplink group down (uplink-down) (4 of 4) Notes (1) The report mode is not supported on the SHub alarms. Equip Maj NSA 7302 7330 No defects The SHub uplink group is down. Check the SHub uplink group.

STOP. This procedure is complete.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TAP 104-39

TAP 104 Fault isolation and troubleshooting

TAP 104-40

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

Training (TNG)

TNG 100 Service installation TNG 101 QoS configuration TNG 102 IGMP and multicast configuration TNG 103 VBAS TNG 104 DHCP relay agent configuration TNG 105 Overall software packages TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI TNG 107 VDSLx parameters TNG 108 SHDSL parameters TNG 109 Performance management counters TNG 110 Configuration examples TNG 111 7330 ISAM FTTN ES configuration TNG 112 7330 ISAM FTTN configuration for subtending TNG 113 Multi-ADSL parameters TNG 114 DLP configuration examples TNG 115 Slot numbering schemes

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 116 Link Related Ethernet OAM (EFM OAM)

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 100 Service installation


General Information
This TNG provides information on:

Forwarding Modes Dynamic MAC Learning and Static Unicast MAC Addresses MAC Learning Rules MAC Learning on SHub and LT board (LIMs) MAC Learning and Unicast Configuration SHub MAC Filters

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 100-1

TNG 100 Service installation

Forwarding Modes
The system has the following forwarding modes:

Intelligent bridging VLAN (iBridge VLAN): In this mode, several User Logical Ports (ULPs) can be associated with a single VLAN. The following applies (see Figure TNG 100-1): 1 VLAN per ISAM 1 IP subnet per ISAM Complex IP address space management, complexity reinforced by static IP subnet provisioning Cross-connect VLAN: In this mode, only one ULP can be associated with a VLAN. In this VLAN, MAC learning is disabled. There are several VLAN cross-connect models supported: Basic VLAN cross-connect: C-VLAN cross-connect VLAN stacking for business users: S-VLAN cross-connect VLAN stacking for residential users: S-VLAN/C-VLAN cross-connect QoS aware VLAN cross-connect: VLAN + p-bits cross-connect Layer 2 termination: In this mode, you can configure the system to use Point-to-Point Protocol over Ethernet (PPPoE). PPPoAoE Relay IPoA/IPoE Forwarding: In this mode, the NE can be seen as an IP-aware bridge without being as an IP next-hop. Users connected to the NE are seen as being directly attached to the edge router IP interfaces. The following applies (see Figure TNG 100-2): 1 VLAN for all ISAMs 1 IP subnet for all ISAMs One single IP pool: IP addresses distributed at random over the whole access network IPoA/IPoE Routing: In this mode, the NE is seen as an IP next-hop on the IP path towards the users. A single Virtual Router (VR) 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. The following applies (see Figure TNG 100-3): 1 VLAN for all ISAMs 1 IP subnet per ISAMs Complex IP address space management but some automation possible through routing protocols

TNG 100-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 100 Service installation

Figure TNG 100-1: Intelligent Bridging

Edge

EMAN

ISAM

CPE

I-Bridge

VRF

Bridge I-Bridge

IP subnet

IP address
Figure TNG 100-2: IP Routing

Edge

EMAN

ISAM

CPE

IP Router VRF Bridge IP Router

IP subnet

IP address

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 100-3

TNG 100 Service installation

Figure TNG 100-3: IP Forwarding

Edge

EMAN

ISAM

CPE

IP Fwder VRF Bridge IP Fwder

IP subnet

IP address

Deleting a VLAN on the LT board is impossible unless all egress ports have been removed from the VLAN. There is no such restriction for the SHub.

Dynamic MAC Learning and Static Unicast MAC Addresses


The system provides standard Layer 2 MAC learning functionality. MAC address learning and configuring is done independently on the SHub and LT board (LIM), as is MAC aging. The system also supports static unicast MAC addresses on user logical ports, network (trunk) ports, cascade (trunk) ports, and user Ethernet ports. MAC learning and configuring are governed by secure MAC learning rules.

MAC Learning Rules


Different port types have different priorities for learning. The order of priority for learning (lowest to highest) is: ASAM/USER/SUBTENDING - NETWORK - CONTROL This means that learning an address on a control port takes higher priority than any other port. Similarly, NETWORK ports have a higher precedence than ASAM, USER, and SUBTENDING ports. ASAM, USER, and SUBTENDING ports have the same priority. Example: 1 MAC 'X' is learned on ASAM port. If packets with the same MAC address appear later on the control port, then MAC 'X' is learned on the control port and the same entry is removed from the ASAM port. MAC 'X' is learned on ASAM port 1. If packets with same MAC address appear on the USER port, then if MAC movement is enabled for the VLAN, the MAC address is learned on the USER port. Otherwise, a duplicate alarm is raised and that particular stream is discarded on the USER port.

TNG 100-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 100 Service installation

A duplicate MAC alarm is raised whenever there is a MAC conflict between same-priority ports, except when the two ports in question are network ports. This is because MAC movement is by default enabled on network ports. Also, a duplicate MAC alarm is raised when a lower-priority port tries to learn a MAC address in case a MAC address has already been learned on any higher priority port. When the duplicate alarm is raised, traffic with the same MAC address is blocked on the second port. The alarm is cleared when the MAC address ages out on the first port. Duplicate MAC alarms will not be raised when MAC movement is enabled. The MAC address will always be learned on the port where the packet arrives. If a dynamic MAC entry already exists on an other port, it is removed before learning the new MAC address on that port.

MAC Learning on SHub and LT board (LIMs)


There are some differences as well as some similarities between MAC learning on the SHub and MAC learning on a LIM in the LT board. Table TNG 100-1 compares the SHub with the LT board.
Table TNG 100-1: MAC learning: SHub versus LT board
SHub MAC learning cannot be disabled LT board (LIM) MAC address learning can be disabled or enabled on an ASAM LIM. MAC address learning is disabled on a LIM in CC-VLAN mode. Maximum number of MAC addresses that can be learned on a LIM is 1024.

Maximum number of MAC addresses that can be learned on SHub is 16384. Once the maximum limit is reached new addresses are not learned and the packets are discarded. Secure MAC learning rules are applicable to different port types Static MAC address can be configured. There is a limit of 25 static MAC entries. Default aging time: 300 s Aging time range: 10 to 1000000 s

NA Static MAC address can be configured Default aging time: 300 s Aging time range: 10 to 1000000 s

MAC Learning and Unicast Configuration


Static MAC addresses can be configured per VLAN on both the Shub and LIMs. The egress port for a particular MAC address is specified by these static MAC entries. Unlike dynamically learned MAC entries, static addresses can be configured to be permanent. When configuring a static unicast MAC address for a port, the system removes the old entry if the MAC address has been learned as a dynamic one in any port within the same VLAN. The system then either accepts or rejects this configuration. It rejects the configuration if the MAC address has been configured as a static one on another port within the same VLAN or the port is not in a valid VLAN. If the number of MAC addresses learned or configured has reached the limit, then one dynamic entry is removed from the database when configuring a new static entry.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 100-5

TNG 100 Service installation

A duplicate MAC alarm is raised when a packet with the same MAC address as a statically configured one on another port is encountered. The static entry is retained while the dynamic entry is discarded.

SHub MAC Filters


The system supports global MAC filters. These filters are supported in the SHub. There are no filters supported per user logical port. The system provides facilities to configure MAC address filtering based on destination MAC address, source MAC address, or both source MAC address and destination MAC address. The filter action is either Drop or Allow on packet match.

TNG 100-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration


Introduction
The Alcatel-Lucent ISAM (7302 ISAM, 7330 ISAM FTTN) as an access concentrator provides sophisticated means for enforcing subscriber SLAs, protect network resources, prevent service theft and impose security policies. This application note helps to understand the Alcatel-Lucent ISAM QoS policies and to choose the appropriate set of functionalities to support your deployment scenario. This application note presents the concepts and functions behind the Alcatel-Lucent 7302 ISAM and 7330 ISAM FTTN QoS Session and related profiles. First the main concepts are explained, followed by relatively simple step-by-step examples. This document explains the following concepts:

Service Access Point and logical flow type QoS Session profile QoS Policer profile QoS Marker profile QoS Policy framework L2 and L3 filters Policy Action profiles

Service Access Points


In a traditional ATM-based DSLAM the logical subscriber interface used to be typically an ATM VC. On the DSLAM the combination of subscriber DSL interface and the VPI/VCI numbers uniquely identified the service. On the BRAS the VPI/VCI numbers were the sole identifiers of the subscriber and the service. This model is still true in some network deployment cases, but the possibilities are proliferating. In general, the entity that identifies a subscriber interface (a logical flow) is called a Service Access Point (SAP).

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-1

TNG 101 QoS configuration

On the ISAM a subscriber interface can be:

a DSL interface an ATM PVC on a DSL interface a PPPoE session a VLAN an IP interface

The basic paradigm of subscriber SLA enforcement revolves around applying the correct policies to the subscriber SAP. Therefore, the solution is to attach QoS rules to such SAPs.

QoS Session Profile


The typical way of approaching residential customers is to offer a small set of service plans from which subscribers can choose, rather than negotiating a deal per subscriber. Therefore a convenient way to configure subscriber policies is via reusable profiles. The main building block of subscriber QoS policies is the QoS Session profile. In principle one such Session profile is required per service. When configuring a new subscriber, it is sufficient to name the appropriate QoS Session profile that applies to the SAP of the customer, and all settings are automatically populated in hardware. This not only provides for fast configuration, but also reduces the chances of erroneous configuration.

Contents of the Session Profile


The QoS Session profile contains settings related to rate enforcement, marking, filtering and basic ACL. More concretely, a QoS Session profile is made of (see Figure TNG 101-1): 1 2 3 4 a logical flow type two policer profiles (upstream, downstream) one marker profile (for upstream) two lists of sub-flow based policies.
Figure TNG 101-1: QoS Session Profile Structure
QoS Session Profile

Logical Flow Type

QoS Policer Profile Up

QoS Policer Profile Down

QoS Marker Profile Up

Qos Policy List Up

Qos Policy List Down

In general a profile that is a component of a session profile cannot be modified while it is associated to a Session profile. However, a Policer and Marker profile referenced in a Session profile can be changed while the Session profile is in use, and settings will be automatically replicated to the live SAPs.

TNG 101-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

Other profiles that are not session-related (buffer acceptance, scheduler, connection admission control) can be modified while in use, but not deleted.

The Logical Flow Type


The Logical Flow Type parameter determines the user interface encapsulation type and forwarding mode. This parameter is important for consistency reasons to parse the supported parameters that can be added, as well as to make sure that the policy can only be applied to the SAP type for which it was intended. The Logical Flow Type parameter is mandatory at profile creation time and cannot be changed later. Therefore it is important to know in advance the logical flow type of the forwarding mode for which the session profile is prepared. Table TNG 101-1 lists the supported logical flow types.
Table TNG 101-1: Logical Flow Types
Logical Flow Type Generic Supported Markers all Supported Filters L2, L3 Remarks May be used for all logical flow types, mainly for test purposes. The system will silently ignore unsupported contents from this profile. Designates all frames on a PVC. In case sub-flow policies need to be used, it is recommended to use one of the specific logical flow types for the forwarding mode rather than PVC, since unsupported filters will be ignored silently. This logical flow type passes also for the default bridge port of an EFM line. Designates all frames on a bridge port that was opened via 802.1x authentication This flow type is used to apply policies on a certain VLAN for tagged frames from the subscriber side. Often the PVC on ATM-based DSL flavors represents a bridge port. However this logical flow type can also be used on EFM DSL ports, where the PVC represents the sole bridge port supported on top of EFM lines. ISAM terminated PPP sessions can use this flow type Designates frames on an IP interface. This can be used for both IPoE and IPoA IP-aware bridges.

PVC

all

(L2, L3)

802.1x session

all

PVC.VLAN

all

L2, L3 (for cross-connect mode only)

PPP IP

all all

L3 L3

(1 of 2)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-3

TNG 101 QoS configuration

Logical Flow Type IPoE VLAN CC

Supported Markers all

Supported Filters L2, L3

Remarks All frames on a bridge port that is configured in VLAN CC mode and carries IPoE frames. It is important to distinguish among encapsulation types of the same forwarding mode for being able to determine the supported filters. This flow type supports both L2 and L3 filters. A cross-connect mode that transports PPP encapsulated frames. All frames on a PVC where PPPoATM encapsulation is used and is cross-connected to a VLAN. All frames on a subscriber-side IBridge port, where encapsulation mode is IPoE. All frames on a subscriber-side IBridge port, where encapsulation mode is PPPoE. Designates all frames on a PVC that uses PPPoA encapsulation but the PPP session is terminated in a central BRAS, therefore PPP packets are relayed with 802.1q encapsulation. All frames on an IP-aware bridge subscriber interface, using IPoE encapsulation All frames on an IP-aware bridge subscriber interface, using IP encapsulation directly over ATM.

PPPoE VLAN CC PPPoA CC

single dot1p single dot1p

L2 -

IPoE IBridge

all

L2, L3

PPPoE IBridge

single dot1p

L2

PPPoA relay

single dot1p

IPoE IP-aware Bridge IPoA IP-aware Bridge

all

L3

all

L3

(2 of 2)

To create a QoS Session profile via CLI, use the following command:
> configure qos profile session <qosSessionProfileName> log-flow-type <flowType>

QoS Policer Profile


The Policer profile contains information regarding the parameters of a policer resource. To date the Single Token Bucket policer is supported with two parameters:

Committed Information Rate (CIR): designates the token accumulation rate in Kbit/s Committed Burst Size (CBS): designates the maximum token count in the bucket

A Policer profile can be referenced by a Session profile in both upstream and downstream direction, and can be reused by many Session profiles. For instance, a Policer profile created for a Voice over IP connection is likely to be reusable both upstream and downstream in many Session profiles that allow the user a VoIP connection.

TNG 101-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

A Policer profile cannot be changed while in use (i.e., while it is associated to at least one Session Profile). However, in a Session profile the referenced Policer profile can be replaced by another one, even while the Session profile is in use (i.e., is instantiated in hardware on SAPs). This allows seamless service upgrades in the field. If there is at least one policer profile on the SAP level, it is not possible to remove it while the Session profile is in use. This is due to policer inheritance. Similarly, if previously there was no policer profile at all, then while the Session profile is in use it cannot be added to the Session profile. It is possible however, to add a second policer or to remove one when previously there were two.

Note 1 The big tolerance for small rate is caused by unit conversion. The CIR unit in NP is KBytes, so integers are accepted. Values are rounded up. As such, any roundup value will have a tolerance of 0.00000...01 to 0.9999...9 KBytes, which is obvious for small rate.
Example: take a CIR of 10 Kbit. This corresponds to 1.25 KB (=10/8). The roundup value becomes to 2 KB in NP. The actual result is 8 x 2KB = 16Kbits. This matches the actual CIR value in NP. For other CIR values: see Table TNG 101-2.

Note 2 Due to the same reasons, the policer works with an error of about 15% for 64B Ethernet frames, both in upstream as in downstream direction; see Table TNG 101-3.
Table TNG 101-2: Upstream Policer Characterization
CIR 10K 100K 300K 500K 800K 1000K 1500K CBS 1600 1600 1600 1600 1600 1600 1600 Result 16K 104K 305K 506K 690K 690K 690K CIR in HW 16K 102K 297K 492K 781K 977K 1469K Rate limited by modem in upstream Rate limited by modem in upstream Rate limited by modem in upstream Description Big tolerance due to SW conversion

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-5

TNG 101 QoS configuration

Table TNG 101-3: Illustration Policer Error


Packet length DS no policer 64 128 256 512 1024 1280 1518 435 409 409 409 819 1023 1214 policer 345 314 309 306 305 304 304 US no policer 544 512 614 819 491 614 729 policer 323 314 309 306 305 303 304

Values in the table above are for a policer with committed-info-rate 300 and committed-burst-size 1600

To create a QoS policer profile, use the following command:


> configure qos profile policer <policerProfileName> committed-info-rate <CIR_Kbps> committedburst-size <CBS_bytes>

TNG 101-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

QoS Marker Profile


The Marker profile contains upstream marking configuration settings for the SAP. Since various encapsulation modes exist, the Marker profile itself is rather complex. Please note that under normal circumstances only a very small subset of the offered functionality is required in a certain deployment scenario.

Basic concepts

Port default code point: all frames of a certain SAP get the same upstream code point (P-bits or DSCP) regardless of the incoming value. Alignment: process of setting a code point based on another code point (typically setting P-bits according to the DSCP). Contract table: a table that marks a code point based on the incoming value of the same code point. This is a 8x2 table for P-bits and 64x2 table for DSCP. Note that P-bit re-marking table is outside from the Marker profile, and can be configured on bridge ports that accept tagged frames. Trusted port: a subscriber SAP where ingress code points (P-bits or DSCP) are accepted as they are received.

In principle there is always a dominant entity that determines the code points to be applied on a frame. Such entities are for example: a parent bridge port, port default VLAN, ingress DSCP, ingress P-bits, or other header information (see marking based on sub-flow policies 4.7). One notable exception is when the port is trusted. For trusted ports received frames will keep their DSCP and P-bits, and un-tagged frames will get code point P=0 in the 802.1q header. Note that a port default P-bit marking can be configured on bridge ports even in the absence of a QoS Session profile. The convention is that the QoS Session profile provided it contains a marker for P-bits has precedence over a bridge port-based default. Also note, that there is a system-wide switch that determines whether code points are derived from bridge-port default settings or are VLAN-based.
> configure vlan priority-policy <vlan-specific | port-default>

Last, setting the DSCP is not supported for non-IP packets (including when IP packets are bridged with PPP-encapsulation). For such packets, the set-DSCP rule is automatically skipped.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-7

TNG 101 QoS configuration

Marker Profile Structure


The Marker profile contains a marker type, port default P-bits, DSCP, DSCP contract table and DSCP-to-P-bits alignment flag. Figure TNG 101-2 shows the marker profile structure.
Figure TNG 101-2: Marker Profile Structure

QoS Marker Profile

Marker Type

Default P-bits

DSCP

DSCP Contract Table DSCP-to-P-bits Alignment Table

The Marker type determines which of the following parameters apply. The port default P-bits enforces a given P-bit setting to all frames that emerge from the subscriber, and overwrites bridge-port-based defaults. The DSCP works similarly. Note that setting the DSCP is only supported for PPP termination, IPoA and IPoE frames. If the forwarding mode is bridging and the packet is PPPoE encapsulated, then setting the DSCP is not supported. It is however supported for bridged IPoE packets. The DSCP contract table maps incoming DSCP values to outgoing DSCP values. It is possible to map multiple incoming DSCP values to a singe outgoing DSCP value. The DSCP-to-P-bits alignment table on the subscriber side is unique system-wide and resides outside the QoS Marker profile. Not to be confused by a similar function on the SHub that can be applied on ISAM network interfaces and is configurable independently. The Marker profile contains only a flag that enables this alignment for upstream subscriber-originated frames or not.

TNG 101-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

Table TNG 101-4 shows the supported marker types.


Table TNG 101-4: Supported Marker Types
Marker Type P-bits DSCP DSCP Contract Table Alignment Flag Comments

singleDot1P

Sets a single P-bit for upstream frames on the SAP. Recommended marker type for bridged mono-QoS SAPs. Sets a single DSCP value for upstream frames. Alignment is optional. Allows a set of DSCP values based on incoming DSCP values. The contract table can enforce that only the agreed sub-set of code points passes by. Use DSCP-to-P-bits alignment to set in a subsequent step the P-bits based on the altered DSCP value. Sets a single DSCP and P-bit for all upstream frames of a SAP. Recommended marker for mono-QoS routed SAPs or IPoE CC. This marker type allows enforcing a permitted set of DSCP values to be used in a later part of the network. In the access part a single P-bit code point is set and used. Accepts incoming DSCP values and set P-bits accordingly, to be used in the L2-part of the access network.

singleDscp

dscpContract

dot1PandDscp

dot1PandDscp Contract

dscpToDot1P Alignment

In general, a code point can suffer multiple alterations, but this is not the purpose. P-bits can be set port-based, then altered in the policy processor block. Also, P-bits specified by the policy processor could be altered by the alignment. This is not the intention. The intention is to set either both code points in one shot according to the determining entity (like parent port) or mark the incoming DSCP with a contract table and align P-bits to it. The complex things are there not to be used for simple cases, but to suit the needs of special deployment scenarios.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-9

TNG 101 QoS configuration

QoS Policy Framework


The QoS Sub-flow Policy is used to provide special treatment to selected flows from within a SAP. In general rate limitation and marking can and should be done on the SAP level. However, in some cases multiple applications that demand differentiated treatment are deployed over the same SAP. Therefore, the solution is to isolate these flows via a filter and apply special treatment on the flow, like permit/deny, marking or rate limitation. A policy is made of a filter and an associated set of actions. Policies also have a precedence value, which allows ordering them in the service access point, in case some of the filters define overlapping sets of the flows. 255 priority levels are supported. A defined policy can be reused in many QoS Session profiles. The policy will always use the same precedence within all Session profiles, since the precedence is an attribute of the policy. Policies with unspecified precedence get precedence 10 (0 lowest, 255 highest). Policies with the same precedence will get instantiated in hardware with random ordering, therefore it is good practice to use correct precedence levels for policies that can be potentially conflicting. The rule is that within a session, the first filtering match will carry out the associated actions on the packet, and no other sub-flow policies are checked.

L2 and L3 Filters
L2 and L3 filters are stored as profiles, and are reusable in both upstream and downstream direction. Filters are multi-field classifiers. In other words, they contain a set of protocol headers, where each can be enabled or ignored or partially masked. However, the total evaluation of the fields is an AND function. Therefore a full match is required. When an OR function is desired, several sub-flow policies can be used to achieve the desired behavior (see Policy Sharing).
Figure TNG 101-3: L2 and L3 Filter Structure

L2 Filter
MAC Destination Address MAC DA Prefix MAC Source Address MAC SA Prefix
Ethertype

L3 Filter
Address Type IP Destination Address IP DA Prefix
IP Source Address

IP SA Prefix DSCP Protocol Type Destination Port Range Source Port Range

P-bits CFI bit VLAN ID

MAC address prefixes in L2 filters can be used for ACL functionality, for instance to specify a certain category of access boxes (like a residential gateway or STB of a certain type from a specific vendor). To specify a L2 policy that applies for all ingress frames, mask out the complete source or destination MAC address.

TNG 101-10

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

L3 filters presently do not support IPv6 addresses. Ranges of TCP and UDP ports are supported, which is a more convenient way for specifying L3+ policies than port masks. Note that protocol extraction, IP and MAC anti-spoofing and blocking special Ether-types happens before the policy processor block. Therefore, QoS filters cannot be used to disable the reception of certain protocols. They can be used to block certain protocols from being transmitted further to the network that are not extracted and treated by the ISAM control-plane processors. Filters look to potentially modified fields (such as VLAN ID, P-bits, DSCP) since the policy processor is located after the L2, L3 engines and the port-based marker block. The supported filter type (L2 or L3) depends on the SAP forwarding and encapsulation mode (see Table 1). The ISAM policy processor will forbid non-supported configurations already at the moment when a policy is attached to a session profile. For instance an IPoA virtual router SAP will not support a L2 filter since there is no incoming Ethernet header. Even if there was like the case of IPoE VR we still dont support L2 filters due to the fact that the L2 header is replaced by the L3 forwarding engine. Presently L2 filters are supported for the VLAN cross-connect mode. L2 and L3 filters can be used in the same Session profile if the flow type allows it.

Policy Action Profiles


Policy actions also stored as reusable profiles are grouping a set of nonconflicting actions that can be attached to a policy. These actions are: pass/discard packet, set P-bits, set DSCP, police sub-flow with a certain policer and policy sharing.
Figure TNG 101-4: Policy Action Profile

Policy Action
Default Disposition Set DSCP Set P-bits Police Sharing

The default disposition is a simple permit/deny statement. The deny statement is provided for building ACLs. By default the disposition is pass. Setting P-bits on the policy-level is supported for all forwarding modes, since upstream all packets will be tagged. However, setting P-bits in the downstream direction is still not useless in case frames are forwarded to subscribers downstream. An altered P-bit for internal purposes can be used to modify the scheduling priority of a downstream packet. This feature is useful to pull out a selected sub-flow (like VoD control traffic) from a best-effort aggregate into the controlled-load queue.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-11

TNG 101 QoS configuration

Setting the DSCP is only supported for IP frames (which includes terminated PPP sessions, since the system does have an IP interface at hand). Setting DSCP is not supported for bridged PPP traffic, as well as for SAPs at layer 2 that are not yet supported by the policy framework. Policing a certain sub-flow means that the selected traffic is not subject to the port-level policer. Therefore is a SAP has a port policer of 1Mbps and two sub-flow policies of 100Kbps, then the total traffic that can pass is 1.2Mbps. However, if the sub-flow policy does not contain policing, then the frame is subject to the port policer. This concept is some times referred as policer inheritance, which applies also across service access points that are on top of each other (like PPP sessions over a bridge port). Marking and sub-flow policies are not inherited across SAPs.

Policy Sharing
There are cases when a certain policy should apply to a set of micro-flows within a SAP that is difficult or impossible to capture with one filter. If this is the case when the policy is to apply an upper bound on the bandwidth to be used in common by such micro-flows, then policy sharing comes to help. Basically, policy sharing if enabled will cause the policies within a QoS Session profile that use the same Policy Action profile in the same direction more than once to share the instantiated policer. This way a common upper bound is placed on the rate of a set of ingress flows. It makes no sense to use policy sharing if no policer is named inside the policy action profile.

TNG 101-12

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

The Complete Marking Pipeline


Now that we introduced the policy framework, we can give the complete chain of policy decision points that may come into the picture for marking. We also give an overview which policy decision point gets its settings from where.
Figure TNG 101-5: Sequence of Policy decision Points for Upstream Marking
May come from: 1. Bridge port default 2. VLAN default 3. QoS Session Profile Marker Port default P-bits No Yes, (1) trusted Tagged? Yes, untrusted

Global Table

QoS Marker profile

QoS Marker profile

DSCP to P-bits alignment

Set P and DSCP for Yes subflow if specified Alignment enabled? (4)

Port default DSCP Yes Filter match? (3)

No, (2) trusted DSCP set? DSCP contract table

Yes, port default

Yes, contract

P-bit contract table Choose from factory defaults No QoS Marker involvement

QoS Marker profile

QoS Session profile Policy List

QoS Marker profile

As mentioned earlier, in a typical deployment scenario only a small fraction of all this is needed. For instance, it is rather common to set only a port default P-bit value. Downstream marking is typically not done in the DSLAM. The ISAM can do downstream P-bit and DSCP modification via the policy processors, but there are no explicit means to do session-based downstream marking. If for some reason this is required, a downstream generic filter has to be defined with action to modify the desired code point to the desired value.

Policy Decision Point (1)


Policy decision point (1) deals with the SAP-based P-bit marking. We distinguish 3 cases: 1 2 3 untagged frames from user, where a port default P-bit is always applied tagged or priority tagged frames, where subscriber marking is trusted tagged or priority tagged frames where correct P-bit marking is enforced via a P-bit contract table.

Port default P-bits can be configured also without a QoS profile, simply by configuring a P-bit on the bridge port level or using VLAN-based defaults. In case a QoS Session profile is attached that contains P-bit settings, this latter will overwrite port or VLA-based defaults. P-bit contract table is not yet possible to specify within a QoS marker profile, and only possible to configure on top of bridge ports (so no IP interfaces).

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-13

TNG 101 QoS configuration

Policy Decision Point (2)


Policy decision point (2) is very similar to (1). Settings for this policy decision point can only come from a Marker profile, therefore the use of a QoS Session profile is mandatory. In principle the first two policy decision points are nonconflicting, therefore their order is irrelevant.

Policy Decision Point (3)


Policy decision point (3) is the sub-flow policy processing block. Filters on P-bits and DSCP already look to altered code points in the previous tow policy decision points. This is key, as it is much simpler to enforce first the usage of a few allowed code points and apply the desired policies rather than defining a policy for all undesired code points. In this policy decision point both P and DSCP bits can be altered and the settings come exclusively from within the QoS Session profile.

Policy Decision Point (4)


Policy decision point (4) uses a global DSCP to P-bits alignment table. This table (defined for upstream use) is typically used when end applications set the DSCP value. In policy decision point 2 an allowed set of DSCP values can be enforced, which in turn is aligned to appropriate P-bits, using it for traffic segregation in the access network. The QoS Marker profile contains a flag whether the global DSCP-to-P-bits alignment table is applicable for a given SAP or not. Please note that the service hub has an independent DSCP to P-bits alignment table, that can be enabled or disabled on a per network interface basis. In principle the service hub alignment table can have a different set of mapping values than the subscriber-side mapping table.

TNG 101-14

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

Configuration Example
This section explains the steps required to create and configure a QoS Session profile and its components through an example.
Figure TNG 101-6: The QoS Session profile and component objects
QoS Session Profile

Logical Flow Type

QoS Policer Profile Up

QoS Policer Profile Down

QoS Marker Profile Up

Qos Policy List Up

Qos Policy List Down

1..16
QoS Policer Profiles QoS Marker Profiles Qos Policy Table

1..4

or
L2 Filter Table L3 Filter Table Policy Action Table

Example: Create a multi-QoS Session profile for an IP-aware bridge interface, with voice traffic limited in both direction to 100Kbps, VoD control traffic with enhanced priority and to limit the rest of traffic to 3Mbps downstream and 256Kbps upstream. Before we create the session profile, it is required that the components are created first. Step 1: Create the Policer profiles Create a Policer profile for upstream rate limitation for the service access point to 256Kbps, with burst tolerance of 32 Kbytes:
> configure qos profiles policer ppUsSap256k committed-info-rate 256 committed-burst-size 32000

Create a Policer profile for downstream rate limitation for the service access point to 3Mbps, with burst tolerance of 96 Kbytes:
> configure qos profiles policer ppDsSap3M committed-info-rate 3000 committed-burst-size 96000

Create a Policer profile for voice rate limitation to 100Kbps, with burst tolerance of 3 Kbytes:
> configure qos profiles policer ppVoice100k committed-info-rate 100 committed-burst-size 3000

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-15

TNG 101 QoS configuration

Step 2: Create the Marker profile The default P-bits for upstream packets are to be set to zero, for voice to 6 and for VoD to 3. In this example we identify voice packets as having a source IP address subnet of 192.170.xx.xx and VoD packets are using source IP addresses in the range of 192.172.xx.xx. Since by default packets get code point 0 if nothing is specified, and the ingress code points are not used for determining the outgoing code point, we can simply leave out the marker profile. However, just for the sake of the example, lets make a marker that sets P-bits equal to 0.
> configure qos profiles marker d1p mpUsSap default-dot1p 0

Step 3: Create the Filters To identify upstream voice traffic we need a filter on the source IP address:
> configure qos profiles l3-filter f3pUsVoiceIp src-ip-addr 192.170.0.0/16

Downstream we could use the same address for the IP destination addresses, or the used DiffServ code point. We choose to use the IP subnet.
> configure qos profiles l3-filter f3pDsVoiceIp dst-ip-addr 192.170.0.0/16

To identify VoD control packets upstream we can use the IP destination address of the VoD portal (e.g.: 192.180.2.2):
> configure qos profiles l3-filter l3pUsVodIp dst-ip-addr 192.180.2.2/0

The same IP address (this time as source) we can use for identifying VoD control traffic in the downstream direction:
> configure qos profiles l3-filter l3pDsVodIp src-ip-addr 192.180.2.2/0

Step 4: Create the Policy actions For voice, the action is setting the outgoing P-bits to 6 and policing the traffic to 100Kbps. The same policy can be used upstream and downstream, since it does not harm in our scenario to alter the downstream P-bits.
> configure qos profiles policy-action apVoice dot1p-value 6 policer-profile name:ppVoice100k

For VoD, the policy action is simply to raise it out of the BE traffic class, which can be again used both upstream and downstream.
> configure qos profiles policy-action apVod dot1p-value 3

TNG 101-16

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 101 QoS configuration

Step 5: Create the Policies The voice policy upstream uses the upstream voice filter (f3pUsVoiceIp) to identify upstream voice packets and do the voice actions (apVoice) both upstream and downstream.
> configure qos profiles policy pcyUpVoice policy-action name:apVoice no precedence filter l3-name:f3pUsVoiceIp > configure qos profiles policy pcyDnVoice policy-action name:apVoice no precedence filter l3-name:f3pDsVoiceIp

The VoD policy used the VoD filters to simply set the code point to 3. Upstream this will cause packets being marked with P-bit = 3, downstream it will cause the packet being redirected to the controlled load queue.
> 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

Step 6: Create the Session Profile Create the session profile for an IP-aware bridge, and add basic building blocks (policies come in a second command):
> configure qos profiles session spSapIpoeVr logical-flow-type ipoe-ip-aware-bridge up-policer name:ppUsSap256k down-policer name:ppDsSap3M up-marker name:mpUsSap > configure qos profiles session spSapIpoeVr down-policy pcyDnVoice > configure qos profiles session spSapIpoeVr down-policy pcyDnVod > configure qos profiles session spSapIpoeVr up-policy pcyUpVoice2 > configure qos profiles session spSapIpoeVr up-policy pcyUpVod

Remarks: 1 VoD control traffic - although treated via a sub-flow policy for marking - is still policed with the entire session. This may cause that from time to time subscriber data traffic consumes the allowed bandwidth for the session and VoD control traffic will be impacted as well. This will not happen to voice traffic, since the voice policy contains a dedicated policer. Therefore, it may be useful to add a policer to the VoD subflow policy such that the session-based policer does not apply to VoD control frames. Although some of the profiles can be reused for many building blocks, it may be wise to reuse them only when they refer to the same entity. Example, the reuse of the voice policy in many session profiles is probably wise to do. If it has to change (e.g., the rate or the filter IP address) it is likely that most of them will change. However, reusing the upstream policer on the session profile for the downstream policing of the VoD control traffic may cause some complications if later one or the other has to change.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 101-17

TNG 101 QoS configuration

TNG 101-18

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 102 IGMP and multicast configuration


General Description
IP multicasting is the transmission of an IP datagram to a host group. A host group is a set of one or more hosts identified by a single destination IP address. IP hosts report their multicast group memberships to any neighboring multicast routers using the Internet Group Management Protocol (IGMP). IGMP is an integral part of IP and must be implemented for all hosts wanting to receive IP multicasts. IGMP messages are encapsulated in IP datagrams, with an IP protocol of 2. Figure TNG 102-1 shows a typical IGMP configuration of a subscriber connected to the system watching a movie sent from the remote server connected on the network.
Figure TNG 102-1: Typical IGMP Configuration

7302 ISAM or 7330 FTTN

Internet Video server

User watching movie Joint Message Mcast Downstream Query Message

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 102-1

TNG 102 IGMP and multicast configuration

IGMPv3
IGMPv3 works basically the same as IGMPv2, except for some protocol improvements, which allow to enhance the scalability of the overall IGMP solution. For example, IGMPv3 allows to aggregate information about multiple multicast streams in a single IGMP report. In addition, IGMPv3 has the ability to support multicast source filters, which enables a system to report interest in receiving a given multicast stream only from specific source addresses or from all but specific source addresses. This is commonly referred to as Source Specific Multicast (SSM). IGMPv3 is the default. Support for IGMPv2 is now seen as a backward compatibility aspect. The IGMPv3 standard specifies that an IGMPv3 system must also be backward compatible towards peer systems with older versions. In practice, for the ISAM, this is realized as follows: The operator can control/configure which IGMP version to use at 2 points:

The version to be used towards the network side is configurable per VLAN. If the value of this parameter is set to v3, the NE will discard v2 messages received from this VLAN, and vice versa. The version towards the user side is primarily needed to tell the NEwhich IGMP version it has to use when sending GMQ messages. This version is configurable system-wide, and per DSL line (that is, the system-wide parameter is the default and the parameter per DSL line allows to overrule the default): When the value is set to IGMPv2, the NE will generate IGMPv2 GMQ messages to the user (which tells the client to switch to IGMPv2 if it was operating in IGMPv3), and will not accept IGMPv3 reports from the user. When the value is set to IGMPv3, the NE will generate IGMPv3 GMQ messages to the user. In this mode, both IGMPv2 and IGMPv3 reports are accepted from the user. The default value is IGMPv3

IGMP Message Types


There are three types of IGMP messages related to the host-router interaction:

membership query (MQ): general query, used to learn group members group-specific query, used to learn if a particular group has any members version membership report leave group message

IGMP Parameter Tables


IGMP is managed using a set of parameters arranged in various tables:


TNG 102-2

IGMP channel table multicast source table IGMP module table IGMP package to multicast source table IGMP system parameters

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 102 IGMP and multicast configuration

IGMP Channel Table


The IGMP channel table consists of multicast capacity parameters as well as statistics and counters related to IGMP that are multicast per bridge.
Table TNG 102-1: Multicast Capacity Parameters
Parameter max-num-group max-num-uncfg cfg-res-time uncfg-res-time Description Maximum number of groups supported by the system in enough bandwidth Maximum number of unconfigured groups supported by the system in enough bandwidth Time to reserve the unused configured groups Time to reserve the unused unconfigured groups Range 0..4096 0..128 0..2147483647 0..2147483647 Default 4096 64 125 0

You can configure the characteristics of an IGMP channel by specifying a unique index, a VCI, and a VPI for each channel, as well as the following parameters:

port index: Ranges from 1/1/3/0 to 1/1/18/47 VCI: Ranges from 0 to 255 VPI: Ranges from 32 to 65535

Refer to the CLI Command and Messages document for a description of all parameters.

Multicast source table


This table determines the characteristics of the multicast groups, which should be multicast in cross-VLAN mode. The table contains a maximum of 1024 multicast source entries.

IGMP module table


This table determines the distribution of statistic information maintained by the IGMP proxy.

IGMP Package to Multicast Source Table


The IGMP package to multicast source table is intended primarily for use by a Element Management System (EMS) (for example, the 5526 AMS). It allows the EMS to support multiple sets of packages in different regions. A package is a group of one or more multicast sources that share a common access permission. By grouping the source channels in one or more packages, a service provider is able to support and deliver services at various levels to the end users.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 102-3

TNG 102 IGMP and multicast configuration

The IGMP package to multicast source table shows the following parameters for a package:

The multicast group address The multicast group source address

IGMP System Parameters


These parameters are used to maintain active memberships of connected multicast channels and to process IGMP join, leave, and query messages. It is highly recommended that all default values be left as is. However, should there be a need to change the IGMP parameters, make sure to set all dependencies first. Failing to do this may lead to rejection of a set, since some of the valid ranges are dependent on other objects.

IGMP Snooping Configuration on the SHub


You can configure IGMP Snooping, Virtual LAN router port related parameters and the Virtual LAN filter for the IGMP Snooping for a particular VLAN.

TNG 102-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 102 IGMP and multicast configuration

Viewing the IGMP Related Parameters


Table TNG 102-2 describes the commands available that allow you to view the IGMP related parameters.
Table TNG 102-2: Parameter display commands
Command show igmp system show igmp channel counter (port) show igmp channel miscellaneous (port) show igmp channel protocol (port) show igmp package-to-src (package-id) show igmp grp-to-package (mcast-addr) show igmp module-mcast-src (slot) mcast-addr <MulticastAddress> show igmp module counter (slot-index) show igmp module time (slot-index) show igmp module miscellaneous (slot-index) show igmp shub vlan-router-port (vlan-id) network-port <Shub::NetworkPort> show igmp shub igs-stats (vlan-id) show igmp shub system-stats show igmp shub mcast-stats (src) vlan-id <Igmp::McastSrcVLANID> ip-addr <Ip::V4Address> show igmp shub bundle-stats (bundle-name) show igmp shub bundle-to-src (bundle-name) class-d-addr <Igmp::MulticastAddress> vlan-id <Igmp::McastSrcVLANID> Description Show all the IGMP system-related parameters Show the IGMP channel counter details Show the IGMP channel source details Show the IGMP protocol statistics for an IGMP channel Show the IGMP package to multicast source parameters Show the IGMP group to package parameters Show the distribution of statistic information maintained by IGMP channels Show the IGMP Module counters Show the time-related parameters of the IGMP module Show miscellaneous parameters of the IGMP module Show the status of the IGMP VLAN router ports Show the IGMP protocol statistics for the SHub Show the CAC system-related parameters and statistics Show the CAC multicast-related channel statistics

Show the CAC multicast-related bundle statistics Show the CAC bundle to multicast source parameters

Multicast Configuration Guidelines


When configuring multicast, the sequence of configuration actions is very important. When you are adding a multicast stream to the multicast source table, you need to configure the VLAN ID on which this stream can be received. You need to create and configure this VLAN ID prior to creating the multicast source table entry. Failing to do this may cause difficulty in joining the multicast group.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 102-5

TNG 102 IGMP and multicast configuration

TNG 102-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 103 VBAS


General Description
The Virtual Broadband Access Server (VBAS) protocol is used between the Broadband Access Server (BAS) and the system to get detailed information on the subscribers physical address. The VBAS protocol has two phases. After completing these phases, the BAS can get the physical address of any new subscriber. The two phases are:

VBAS Query VBAS sends a VBAS Query Packet to the system to gather physical-port information corresponding to the MAC address of the new subscriber. VBAS Response Upon receiving the request packet, the system sends a VBAS Response Packet to the BAS. This packet includes the physical-port information of the new subscriber.

All VBAS packets carry a destination. If the packet is not destined for a specific system, it will forward the packet to all subtending systems until it has reached its intended destination. In normal operation, the network port towards the BAS is tagged. This means that the network port is able to process and respond to tagged VBAS frames. If untagged packets are to be handled, then the network port is explicitly set as untagged. Also a PVID is configured for the port. When the system receives a VBAS query, user information is retrieved from the VLAN configured as PVID.

VBAS Configuration
No specific VBAS configuration as such is necessary on this system. However, as an Operator, you need to make sure that the network port is configured in order to properly communicate with the BAS. There are two modes in which the network port can operate: tagged or untagged.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 103-1

TNG 103 VBAS

VBAS Configuration in Tagged Mode


If the network port is set up as a tagged port, it should be a part of all related VLANs. The port will handle all tagged VBAS packets.

VBAS Configuration in Untagged Mode


If untagged VBAS frames are to be handled by the system, the network port must be untagged and a PVID must be configured.

Example
A user with MAC address 00-B0-D0-BC-D5-D3 is connected to slot 7, port 23 on LIM1. LIM1 is connected to ASAM port 1. The VLAN configured for the user is VLAN 100 on both LIM and SHub. When the VBAS request arrives from the server on the SHub, the MAC address of the user is retrieved in VLAN 100. Since the user MAC address is learned in VLAN 100, the request is forwarded to LIM1. LIM1 replies with VBAS response containing user information such as the slot and port number. The SHub forwards the VBAS response to the server. The process is shown in Figure TNG 103-1.
Figure TNG 103-1: VBAS Example

ISAM/L Shub: 06.00.00.00.00.80

ETHERNET
VBAS Req VBAS Resp User: MAC: 00.b0.d0.bc. d5.d3 Slot: 2 Port: 23 VLAN: 100 VBAS Resp: DA: 02.00.40.00.00.80 VL AN: 100 User: 00.b0.d0.bc. d5.d3

TNG 103-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 104 DHCP relay agent configuration


General Description
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable network addresses and additional configuration options. DHCP consists of two components: a protocol for delivering host-specific configuration parameters from a DHCP server to a host and a mechanism for allocation of network addresses to hosts. DHCP is built on a client-server model, where designated DHCP server hosts allocate network addresses and deliver configuration parameters to dynamically configured hosts. Figure TNG 104-1 shows a typical DHCP configuration.
Figure TNG 104-1: Typical DHCP Configuration

iSAM 7302 or 7330 FTTN

Internet DHCP server

Upstream packet Downstream


17704

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 104-1

TNG 104 DHCP relay agent configuration

IP Address Allocation Mechanisms


DHCP supports three mechanisms for IP address allocation:

automatic allocation DHCP assigns a permanent IP address to a client. dynamic allocation DHCP assigns an IP address to a client for a limited period of time (or until the client explicitly relinquishes the address). manual allocation A client's IP address is assigned by the network administrator, and DHCP is used simply to convey the assigned address to the client.

A particular network will use one or more of these mechanisms, depending on the policies of the network administrator.

DHCP Option 82
An option called Option 82 is inserted by the DHCP relay agent running on the system when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing Option 82 may use the information to implement an IP address or other parameter assignment policies. The DHCP server echoes the option back to the relay agent in server-to-client replies. The system strips the option before forwarding the reply to the client. Option 82 is organized as a single DHCP option that contains one or more suboptions that convey information known by the relay agent.

DHCP Relay Parameters


Table TNG 104-1 describes the parameters used to configure DCHP.
Table TNG 104-1: DHCP parameter descriptions
Parameter Relaying Server Server IP secs-threshold/hops-threshold Description When enabled, the relay agent is active When enabled, the relay agent forwards the packets to a specific DHCP server Address of the DHCP server to which the packets are to be forwarded Thresholds for DHCP realy agent

TNG 104-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 104 DHCP relay agent configuration

Conditions and Restrictions


Note the following conditions and restrictions.

Before you can enable the DHCP relay agent, you need to configure the DHCP servers on a VRF IP interface. The DHCP relay agent can only be configured on one VRF IP interface. A maximum of four DHCP servers can be configured on a VRF. The DHCP servers configured on a VRF IP interface must be part of the set of DHCP servers configured on the VRF.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 104-3

TNG 104 DHCP relay agent configuration

TNG 104-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 105 Overall software packages


Introduction
This TNG provides more information about:

Downloading a new OSWP. Aborting an OSWP. Activating a non-active OSWP. Committing an OSWP.

Download a New OSWP


The following prerequisites must be fulfilled before a new OSWP can be downloaded:

The system must have only one Enabled/Active/Committed OSWP. The management channel between the system and the manager has been established. The system is not involved in another OSWP download process.

The manager requests the system to download a new OSWP. He specifies:

The path name of the overall descriptor files The TFTP-servers where the overall descriptor files can be found. The set of overall descriptor files he wants to have available on the system before activating the new OSWP.

The system downloads the overall descriptor files and stores it persistently. The system downloads the software files that are specified in the downloaded overall descriptor files on condition that sufficient resources are available for their persistent storage. The manager has the possibility to monitor the progress of the download process with granularity.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 105-1

TNG 105 Overall software packages

The download of the process can be implicitly or explicitly interrupted:

The implicit interruption can occur due to the following: the unavailability of sufficient resources to store SWP files. the system is not able to download or interpret the overall descriptor file. the system is not able to download a selected SWP descriptor file. The explicit interruption can occur when the manager requests the system to abort the ongoing download process.

In case there are no exceptions, finally the system will have two OSWPs:

the Enabled/Active/Committed OSWP. the new downloaded OSWP. The status of the new OSWP is Enabled/NotActive/UnCommitted.

Abort an OSWP
The manager can abort an OSWP when the system has 2 OSWPs. The status of the first OSWP is Enabled/Active/Committed while the second one will be in one of the following three states:

Enabled/NotActive/UnCommitted Downloading/NotActive/UnCommitted Disabled/NotActive/UnCommitted.

The management channel between the system and the manager is established and the system is not involved in any other SW download process. The manager requests the system to remove the NotActive/UnCommitted OSWP. The system removes all the persistent stored files and databases not related to the Enabled/Active/Committed OSWP. The status of the OSWP to be removed will be Aborting/NotActive/UnCommitted during the complete remove operation. After the abort is successful the system will have only one OSWP. The status of this OSWP will be Enabled/Active/Committed. Only files and databases related to this OSWP are stored persistently in the system.

Activate a Non-active OSWP


To activate a not-active OSWP, the system must have two OSWPs: The first OSWP has the status Enabled/Active, while the second OSWP has the status Enabled/NotActive. The management channel between the system and the manager is established and the system is not involved in another SW download process. The manager requests the system to activate the Enabled/NotActive OSWP: 1 The system selects the database that is compatible with and linked to the Enabled/NotActive OSWP among the available databases.

TNG 105-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 105 Overall software packages

2 3

The system starts the activation procedure of the NotActive OSWP. When the activation of the NotActive OSWP is successful, the system has two OSWPs.

The previously NotActive OSWP is now active together with the selected compatible database. The previously Active OSWP is still available but its status is now Enabled/NotActive.

Commit an OSWP
To commit an OSWP, the system has two OSWPs. The first OSWP has the status Enabled/Active/Uncommitted, while the status of the second OSWP is Enabled/NotActive/Committed. The manager requests the system to commit the active OSWP: 1 The system removes all the persistent stored files and databases that do not belong to the Enabled/Active OSWP.

Note The status of the OSWP to be committed will be Enabled/Active/Committing during the entire commit operation.

After commit is successful, the system will have only one OSWP. The status of this OSWP is Enabled/Active/Committed. Only files related to this OSWP are stored persistently in the system.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 105-3

TNG 105 Overall software packages

TNG 105-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI
Purpose
This TNG provides information about how the system software of a host shelf identifies connected remote expansion units and how you can access remote components to configure them using a CLI management session from the host shelf.

Rack and shelf IDs


The expansion configuration for the 7330 ISAM FTTN consists of an ARAM-D host shelf connected to a combination of 7330 ISAM FTTN ES and 7330 ISAM FTTN REM or SEM remote expansion units. You can connect up to five ES and 12 REM or SEM as long as the total number of remote LT units does not exceed 12.

Rack and shelf assignments


The 7330 ISAM FTTN system and management software identify each 7330 ISAM FTTN according to a rack and shelf ID. A standalone 7330 ISAM FTTN always uses rack 1, shelf 1. In expansion configurations, the host shelf and each remote expansion unit require a unique rack and shelf ID. The rack and shelf ID, along with the MAC address, is used for routing traffic to subscribers connected to the shelf. The assigned rack and shelf IDs can reflect the actual installation of shelves within co-located racks, or be logical assignments for remote installations. It is possible to configure up to 7 racks in an expansion configuration, each rack with up to 4 shelves, for 28 possible rack/shelf combinations. However, because the host shelf supports a maximum of 12 downlinks, you can only connect 12 remote shelves to a host shelf.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 106-1

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI

Rack 1 must always contain the host ARAM-D shelf in the topmost position and the host shelf must be assigned rack 1, shelf 1. A combination of ES (maximum 5) and SEM or REM (maximum 12) can be installed in racks 1 through 7 to a maximum of 12 shelves. The SEM and the REM are nearly always installed in remote locations, away from the host shelf installed in the CO. Expansion shelves may be co-located with the host shelf or installed in remote locations. For this reason, racks 2 through 7 are virtual racks: they do not necessarily need to be physical racks installed in the same CO location as rack 1 containing the host shelf. Shelves 2 to 4 in rack 1 may also be assigned to remotely located ES, SEM or REM. For the ES, rack and shelf assignments are derived from the shelf jumper settings. For the SEM or REM, the rack and shelf assignment is derived from the downlink port on the board to which the SEM is connected (see section below for a list of possible boards), i.e. their positioning is provisioned by the operator by provisioning the mapping of the SFP port ID on the shelf expander unit (GENC/NTIO) to a remote LT slot position (rack/shelf/slot). Rack and shelf assignments for downlink ports are configurable using CLI.

Boards with downlink ports


The following boards are equipped with downlink ports:

GENC-E and GENC-F NCNC-B, NCNC-C, NCNC-D and NCNC-E

Configurable rack and shelf ID assignments


The downlink ports on the GENC-x or NCNC-x board to which you connect a remote expansion unit have configurable rack and shelf ID assignments. Each ES and SEM or REM must have a unique rack and shelf ID. For the ES, you do not have to configure the rack and shelf assignments for the downlink ports; shelf jumper settings are used by default to assign rack and shelf IDs.

Note The assignment is not required for the ES shelf itself (due to ES shelf autoplanning), but the assignment is required for VLAN configuration. Without the assignment it is not possible to configure VLAN on the LTs in ES. Therefore, it is highly recommended to configure the aasignements.

The SEM or REM does not use jumpers to set the rack and shelf ID. For the SEM or REM, the rack and shelf ID are derived from the downlink port settings of the GENC-x or NCNC-x board. The CLI is used to configure rack and shelf ID assignments for downlink ports.

Note A management session must be initiated on the host shelf. No direct management connection can be made to remote expansion units for configuration using CLI.

TNG 106-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI

After an ES is connected to a downlink port and is operational, swapping expansion link cables disrupts communications over the affected expansion links and an alarm is raised in the system software. If the rack and shelf assignment for a downlink port is already configured using CLI and you connect a remote LT unit from an ES that has a different rack and shelf jumper setting, an alarm is raised and the remote LT unit does not come in to service. If you connect a remote LT unit from an ES to a downlink port after a SEM unit was previously connected and commissioned, an alarm is raised and the remote LT unit does not come in to service. Using the CLI, you can change the shelf and rack ID assignments for all downlink ports on the GENC-x or NCNC-x board. Do not change shelf and rack ID assignments using CLI 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 that were affected will require reconfiguration.

Warning Do not swap optical expansion link cables between downlink expansion ports on the GENC-E, GENC-F, NCNC-B or NCNC-C board, or between expansion ports on the EDSE-A board, after the remote expansion unit is configured. Service disruptions will result and an alarm is raised. SFP port mapping
For VLAN configuration commands, the user enters a rack, shelf and slot as identifiers to apply the VLAN configuration. For LTs in the expansion shelf, the rack, shelf, and slot must be mapped to an SFP unit on the faceplate of the GENC (or NCNC-B/NCNC-C for FD).
Table TNG 106-1: Available SFP ports
Board GENC Available links 14 links: SFP number on faceplate 4...17 SFP to be cabled to rack/shelf/slot


NCNC-B

SPFs 4 and 5 are uplinks SPFs 6 and 7 are configurable (up/down) SFPs 8 to 17 are downlinks 2...7

6 links:

NCNC-C

SPFs 2 to 7 are configurable (up/down) 2...13

12 links:


NCNC-D

SPFs 2 to 7 are configurable (up/down) SFPs 8 to 13 are downlinks 2...7

6 links:

NCNC-E

SPFs 2 to 7 are configurable (up/down) 2...13

12 links:

SPFs 2 to 7 are configurable (up/down) SFPs 8 to 13 are downlinks

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 106-3

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI

The SFP to be cabled to field that contains the rack-shelf-slot of the desired LT to be cabled to that SFP requires that the shelf of the LT being referenced must be planned; only the shelf must be planned. This is required to check on the valid rack-shelf-slot ranges. Un-planning of a shelf will be blocked if the shelf is part of any of the rack-shelf-slot entries in the host SFP configuration extension table. For the configurable SFPs: If the SFP is configured as uplink then the association to an LT will be blocked. Similarly if the SFP is configured as downlink and there is an LT associated with that SFP, the configuration of the SFP to uplink will be blocked.

Specifying remote expansion units using CLI


You can configure the 7330 ISAM FTTN host shelf and connected remote expansion units using CLI. A management session must be initiated on the host shelf. No direct management connection can be made to remote expansion units for configuration using CLI.

Slot and port identification


After you initiate a management session with the host shelf and are ready to enter configuration commands, you need to know what parameters to enter that will apply the configuration command to the appropriate piece of equipment. For expansion configurations, you can configure operating parameters and services for the host shelf, the ES, or the SEM or REM. You must enter the unique rack and shelf ID for the host shelf or remote expansion unit. Depending on what you are configuring, you may also need to enter the slot number of a particular card and a specific port number. The following standard conditions apply:

a standalone 7330 ISAM FTTN always uses rack 1 and shelf 1 the host shelf in an expansion configuration always uses rack 1, shelf 1 the slot ID for the SEM or REM is slot 4 (using legacy based numbering) or 1 (using position-based or type-based numbering).

For shelves, you must enter the LT slot number that contains the card you want to configure. For a horizontally mounted ARAM-D shelf, the bottommost LT slot is LT1. The LT slot number increments for each successive LT slot in the shelf. The topmost LT slot in a horizontally mounted shelf is LT4. Table TNG 106-2 lists the ES shelf contents and indicates what you must enter using the CLI to reference a specific slot. The orientation of the table rows is the same as the slots of a horizontally mounted ARAM-D shelf, where the GFC slot has the topmost position in the shelf and slot LP1 has the bottommost position.

TNG 106-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI

Table TNG 106-2: ES slot designations for CLI


Slot type GFC ATI NT slot B (NTB) NT slot A (NTA) LT slot 4 (LT4) LT slot 3 (LT3) LT slot 2 (LT2) LT slot 1 (LT1) LP slot 4 (LP4) LP slot 3 (LP3) LP slot 2 (LP2) LP slot 1 (LP1) ES slot content PWIO-B card SATU-A card Filler plate EDSE-A card Any supported LT unit Any supported LT unit Any supported LT unit Any supported LT unit Matching applique for LT unit installed in LT4 Matching applique for LT unit installed in LT3 Matching applique for LT unit installed in LT2 Matching applique for LT unit installed in LT1 Slot identifier to enter using CLI 1 2 7 6 5 4

Note The default legacy-based slot numbering is used here. See TNG 115 for slot numbering using other slot numbering schemes.

Subscriber ports are uniquely identified by the rack, shelf, slot, and port number. The port number is determined by the cable pinout when subscriber lines are connected to the applique installed in the shelf, or to the SEM xDSL drop line break-out cable.

Example CLI configuration commands


An example command to configure an EVLT-A board installed in slot LT1 for shelf 2 in rack 1 is as follows: 1 Plan the shelf: configure equipment shelf 1/2 2 Plan the EVLT-A board: configure equipment slot 1/2/4 planned type evlt-a An example command to configure a SEM as an LT unit in slot 4 of rack 3, shelf 1 is as follows: 1 Plan the NT I/O board: configure equipment applique iont:1/1 planned-type genc-e 2 Plan the REM: configure equipment shelf 3/1 type sems-a

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 106-5

TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI

Configure the association between a host shelf SFP and a remote LT: configure equipment external-link-assign 10 remote 3/1/4

Plan the board: configure equipment slot 3/1/4 planned type vsem-a

An example command to configure 3 REMs as an LT unit in slot 4 of rack 3, shelves 2, 3 and 4 is as follows: 1 Plan the NT I/O board: configure equipment applique iont:1/1 planned-type ncnc-c 2 Plan the REMs: configure equipment shelf 3/2 planned-type rems-a configure equipment shelf 3/3 planned-type rems-a configure equipment shelf 3/4 planned-type rems-a 3 Configure the association between the host shelf SFPs and the REMs: configure equipment external-link-assign 3 remote 3/2/4 configure equipment external-link-assign 4 remote 3/3/4 configure equipment external-link-assign 5 remote 3/4/4 4 Plan the boards: configure equipment slot 3/2/4 planned-type rvlt-a configure equipment slot 3/3/4 planned-type rvlt-a configure equipment slot 3/4/4 planned-type rvlt-a

TNG 106-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters


Introduction
This TNG provides more information about the parameters used by the VDSLx modem:

Re-initialization triggers VDSLx configuration management Line operation configuration VDSLx common configuration parameters Flavor-dependent configuration parameters Flavor-specific configuration parameters Supported operational data parameters

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-1

TNG 107 VDSLx parameters

Re-initialization triggers
During showtime (L0 line state), the VDSLx Modem Subsystem performs persistency/severity checking and correlation on the defects/anomalies, in order to detect re-initialization triggers. Table TNG 107-1 lists them for the VTU-O and includes the required persistency time for each showtime error.
Table TNG 107-1: Re-initialization triggers
Related Defect/Anomaly Needed persistency to trigger re-start Near-End (f)los sef/rdi (f)lom (f)se (f)ncd (f)lcd (f)npd/(f)lpd 5 1 sec 5 1 sec 60 1 sec 10 1 sec 15 1 sec 15 1 sec 15 1 sec Far-End 6 1 sec 6 1 sec 60 1 sec 10 1 sec 17 1 sec 17 1 sec 15 1 sec

The VDSLx modem subsystem triggers/initiates re-activation of the modem when any of those triggers is fired. No other re-initialization triggers (annex timer values) are used by the modem subsystem than the ones mentioned in Table TNG 107-1. All the far-end countdown timers are frozen when any near-end defect occurs. When all the near-end defects have disappeared, the ar-end count-down timers resume from the frozen values (ignoring the in-between time). All the near-end defects are correlated independent from each other. The same holds for all the far-end defects in absence of near-end defects.

TNG 107-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

VDSLx configuration management

Line operation configuration


The VDSLx modem subsystem accepts the configuration parameters listed hereunder. Based on the required levels, the required modem reaction on each parameter is:

In case a parameter is indicated as optional, the input value is do not care, and any value is accepted without having impact on the modem subsystem behavior. In case a parameter is indicated to be required to a certain level (for example, only a limited set of defined number of input values), only input values corresponding to the required level are accepted. If the input parameter is not accepted, the modem subsystem raises a failure indication to the xDSL manager indicating Configuration Error In case extra consistency checks need to be performed on a parameter or between parameters and the configuration should be rejected, rejection always means that the modem subsystem raises a failure indication to the xDSL Manager indicating Configuration Error, rather that a returned error of the considered xDSL API call. An xDSL API configuration request is replied with an error only when the call is done in a wrong administrative state.

The VDSLx modem subsystem allows the configuration to be independently set on individual line basis.

VDSLx common configuration parameters


All the following parameters are common for all supported DSL flavours (includes VDSL and VDSL2). There is only one instance per parameters, whatever the number of operating modes selected.

Operating modes Rate adaptation mode Target noise margin Minimum noise margin Maximum noise margin Carrier mask RF band data Minimum bitrate Maximum bitrate Rate adaptation ratio Maximum interleaving delay Minimum impulse noise protection Bonding mode

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-3

TNG 107 VDSLx parameters

Downstream Power Back-Off (DPBO) shaping: The DPBO shaping defines additional constraints on the Limit Tx DS PSD Mask for VDSL2 respectively. Those constraints are based on ITU-T G.997.1 Downstream Power Back-Off Shaped (DPBOSHAPED). All DPBO configuration parameters defined hereunder related to PSD levels will be interpreted asPSD mask values by the modem subsystem. DPBO shaping mode DPBO electrical length DPBO assumed exchange PSD mask DPBO cable model parameters ABC DPBO minimum and maximum frequency DPBO minimum usable signal level Mode independent custom PSD mask downstream Extra DPBO maximum usable frequency control Extra DPBO remote side electrical length Extra DPBO offset Maximum deviation from maximum interleaving delay Band plan: Custom band plan Predefined band plan Maximum number of bands Maximum usable frequency ADSL band mode ADSL band mode end frequency Optional band mode Optional band mode end frequency US power backoff mode DS G.HS tones power: DS G.hs tones power mode DS G.hs tones power manual level

TNG 107-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-2: Operating modes


Name Description Operating Modes Specifies which xDSL standard shall be applicable: ANSI T1.424 (old trial use standard), ETSI TS 101 270, ITU-T G993.1, IEEE 802.3ah, or ITU-T G.993.2 (VDSL2) different Profiles. Line Bitmap: OpModesITU_G993_2_8A_Bit OpModesITU_G993_2_8B_Bit OpModesITU_G993_2_8C_Bit OpModesITU_G993_2_8D_Bit OpModesITU_G993_2_12A_Bit OpModesITU_G993_2_12B_Bit OpModesITU_G993_2_17A_Bit OpModesITU_G993_2_30A_Bit OpModesANSI_T1_424Bit OpModesETSI_TS_101_270Bit OpModesITU_G993_1Bit OpModesIEEE802.3ah_Bit Granularity & Unit -

Instances Values

Table TNG 107-3: Rate adaptation mode


Name Description Rate Adaptation Mode Specifies the Rate Adaptive mode of operation: RA mode 1 (manual): The VTU initializes at the specified Minimum Bitrate (while taking into account the bit rate rounding rules). During showtime, the VTU tries to maintain that bitrate with at least the specified Minimum Noise Margin. RA mode 2 (atInit): The VTU initializes at the bitrate corresponding with a noise margin of at least the specified Target Noise Margin and a BER better than 10-7 at 0 dB noise margin, provided that the bitrate is not less than the specified Minimum Bitrate and not greater than the specified Maximum Bitrate. During showtime, the VTU does not perform dynamic rate adaptation but instead, tries to maintain the initial bitrate with at least the specified Minimum Noise Margin. The modem optimizes according to a list of priorities. Instances Values Line DS, US raModeManual raModeAtInit Granularity & Unit -

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-5

TNG 107 VDSLx parameters

Table TNG 107-4: Target noise margin


Name Description Target Noise Margin Specifies the required noise margin, relative to a BER of 10-7 at 0 dB noise margin, the modem achieves in order to successfully complete the initialization. This parameter is not used in showtime. DS, US 0..31 0.1 dB

Instances Values Granularity & Unit

Table TNG 107-5: Minimum noise margin


Name Description Minimum Noise Margin Specifies the minimum noise margin, relative to a BER of 10-7 at 0 dB noise margin, the modem tolerates in order to maintain showtime. This parameter is only used in showtime. The VDSLx modem subsystem raises failure indication Configuration Error for configurations where Minimum Noise Margin > Target Noise Margin for one of the directions. Instances Values Granularity & Unit DS, US 0..31 0.1 dB

TNG 107-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-6: Maximum noise margin


Name Description Maximum Noise Margin Specifies the maximum noise margin sustained by the modem. This parameter is both used during initialization and in showtime.

during initialization: When the noise margin for transport configuration is higher than the Maximum Noise Margin, then the modem takes action to reduce the power to get the actual noise margin below this value. When the noise margin is lower than the Maximum Noise Margin, then the modem tries to optimize the Receive Power below the configured masks to get the noise margin as high as possible (still below the Maximum Noise Margin). in showtime: When the current noise margin gets above the Maximum Noise Margin, the modem attempts to reduce the far-end output power to get the noise margin below this limit (by means of bit-swap actions). When the current noise margin gets below the Maximum Noise Margin, then the ATU attempts to increase the far-end output power (still below the maximum allowed templates or masks) to get the noise margin as high as possible (by means of bits-swap actions).

If the Maximum Noise Margin is configured lower than the Target Noise Margin, the configuration is rejected, and the configuration error failure is raised. The special value NoMaximumNoiseMargin is interpreted as meaning that no Maximum Noise Margin limit must be applied. Note: values strictly bigger than 31.0 are converted to the special value NoMaximumNoiseMargin. Instances Values Granularity & Unit DS, US 0..51 and NoMaximumNoiseMargin 0.1 dB

For clarification, Figure TNG 107-1 gives an overview of the noise margin parameters, and the required actions from the modem.
Figure TNG 107-1: Noise margin parameters

Reduce Output Power at peer modem Maximum Noise Margin Maximum Additional Noise Margin Target Noise Margin Minimum Noise Margin 0 dB Margin Modem restarts if persistent in this region Increase Output Power at peer modem

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-7

TNG 107 VDSLx parameters

Table TNG 107-7: Carrier mask


In VDSL the carrier masking is not defined using bitmap. Instead carrier masking is defined via RF bands (see RF band data).

Table TNG 107-8: RF band data


Name Description RF Band Data Specifies the list of RF bands (HAM band or AM band) for egress control and ingress cancelling. Band RF type, ingress level and egress control parameters can be set independently from each other. Up to 16 bands shall be supported: RFBandi (i = 0..15). Egress control can be requested and applied in up to 16 bands simultaneously.Ingress level can be specified for each RF band such that it can be taken into account by the modem at initialization (usage for RFI cancelling purposes is vendor discretionary). However, when different ingress settings are configured for RF bands being in the downstream bandplan (gDS RF bandsh), the stronger ingress setting shall be assumed for all those DS RF bands. Instances Values Line Maximum 16 RF bands can be specified and are supported: RF band = [Start frequency, Stop frequency, RF type, Egress control, Ingress level]

Frequency: 0 30000 kHz RF type: HAM band (rfHam) or AM band (rfAm) Egress control: egressNotched: PSD level in the band is below -80 dBm/Hz egressMasked: tones in the bands are turned off egressNotchedMasked: PSD level in the band is below -80 dBm/Hz, and tones in the bands are turned off egressNoControl: PSD notching is not required Ingress level: (ingressLow): ingress level can be neglected (ingressWeak): expected ingress level is weak at -30dBm@LT/-20dBm@NT level (ingressStrong): expected ingress level is strong at -10dBm@LT/0dBm@NT level

Granularity & Unit

Table TNG 107-9: Minimum bitrate


Name Description Minimum Bitrate Defines the minimum requested transport bitrate which is set up and which is maintained during showtime by the VTU. Note: The value can be rounded by the modem subsytem according ti the bit rate rounding rules. Instances Values Granularity & Unit Bearer DS, US 0..262143 1 kbit/s

TNG 107-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-10: Maximum bitrate


Name Description Maximum Bitrate Defines the maximum allowed transport bitrate which is set up and which is maintained during showtime by the VTU. This parameter is relevant only in 'atInit' RA Mode. When RA Mode is manual, the Maximum Bitrate parameter is ignored. The VDSLx modem subsystem raises failure indication Configuration Error for configurations where Maximum Bitrate < Minimum Bitrate for one of the directions in case of the atInit RA Mode. Note: The value can be rounded by the modem subsytem according ti the bit rate rounding rules. Instances Values Granularity & Unit Bearer DS, US 0..262143 1 kbit/s

Table TNG 107-11: Rate adaptation ratio


Name Description Rate Adaptation Ratio The Rate Adaptation Ratio specifies the ratio that should be taken into account for allocating available data rate (in excess of the minimum data rate summed over all bearer channels) among the different bearer channels in a given direction. The ratio is defined as a percentage from 0 to 100. The sum of the raRatios for all bearers must be 100. The excessive bitrate (that is, the available bitrate minus the sum of the minimum bitrates) must be distributed among the different bearers according to their respective raRatio. When the maximum bitrate is achieved for one of the bearers, the raRatio of that bearer must be distributed to the other bearers according to their respective raRatio share. This parameter is only meaningful in case multiple bearers are used (for example, 2 for dual latency) and is ignored in case of single latency. Instances Values Granularity & Unit Bearer DS, US 0..100 1%

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-9

TNG 107 VDSLx parameters

Table TNG 107-12: Maximum interleaving delay


Name Description Maximum Interleaving Delay Specifies the maximum allowed delay introduced by the interleaving and deinterleaving function in the corresponding direction. The VTU-O and VTU-R choose their interleaving and coding parameters within the maxDelay and minInp constraints. Instances Values Bearer DS, US 0..63, and special value onems.


Granularity & Unit

0 is a special value used as don't care indication, that is, the interleaving delay is not restricted. 1 is a special value used to disable the interleaving (fast mode). onems is a special value used to select 1 ms maximum interleaving delay. Other values directly give the maximum impulse noise protection, in milliseconds.

1 ms

Table TNG 107-13: Minimum impulse noise protection


Name Description Instances Values Granularity & Unit Minimum Impulse Noise Protection Specifies the minimum required impulse noise protection as a number of protected DMT symbols at PMD output (de-interleaver input). Bearer DS, US 0..16 DMT Symbols 0.1 DMT symbol

Table TNG 107-14: Bonding mode


Name Description Instances Values Bonding mode This parameter indicates if the line is part of a bonding group or not. Line Enumeration

native: default, line is not included in a bonding group. ethernetBondingSystem: the line is part of an Ethernet bonding group. The packets fragmentation and re-assembly is performed outside the modem sub-system. However, the modem subsystem handles aggregation primitives, and sets G.hs bonding bits properly.

Granularity & Unit

TNG 107-10

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-15: DPBO shaping mode


Name Description DPBO shaping mode Specifies the DPBO shaping mode:

DPBO Off: the DPBO functions are disabled and the modem subsystem ignores subsequent (extra) DPBO configuration parameters. DPBO On: the modem subsystem enables the DPBO Shaping by taking into account the subsequent (extra) DPBO configuration parameter. Two working modes are possible: The MICOnly simplified mode, where the DPBO Shaping is solely determined by MICPSDMASKds (see TNG 107-22). This mode is applicable when: The DPBO Electrical Length (see TNG 107-16) is set to 0dB or The DPBO Minimum and Maximum Frequency are equal. The Full mode, applicable when not in MICOnly modes. In this case, all DPBO parameters defined here below will be used in DPBO algorithms.

Instances Values

Line DS psdDpboOff psdDpboOn

Default Granularity & Unit

Off -

Table TNG 107-16: DPBO electrical length


Name Description DPBO electrical length Specifies the electrical length of the loop segment from the exchange to the remote flexibility point, matching the DPBOESEL parameter described in of ITU-T G.997.1 7.3.1.2.13a2). Line DS 0..255.9 dB 0 dB 0.1 dB

Instances Values Default Granularity & Unit

Table TNG 107-17: DPBO assumed exchange PSD mask


Name Description DPBO assumed exchange PSD mask Specifies the Assumed Exchange PSD mask to be protected by the DPBO shaping mechanism at the remote flexibility point . This parameter matches the DPBOEPSD parameter described in ITU-T G.997.1 [7.3.1.2.13a1). The parameter consists of a set of PSD breakpoints, with a maximum of 16 breakpoints. The PSD mask is formed by connecting the points with straight lines on a linear scale on the frequency axis. Instances (1 of 2) Line DS

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-11

TNG 107 VDSLx parameters

Values Default Granularity & Unit

The VTU-O pre-configures the PSD breakpoints corresponding to the ITU-T G.992.5 Annex A.1.3 ATU-C DS Tx PSD mask; see Table TNG 107-18 below. 0 dB Frequency: 1 kHz PSD: 0.1 dBm/Hz

(2 of 2)

Table TNG 107-18: Default PSD breakpoints


Frequency (kHz) 0 4 4 80 138 138 1104 1622 2208 2500 3002 3132 30000 PSD level (dBm/Hz) -95 -95 -92.5 -72.5 -44.2 -36.5 -36.5 -46.5 -47.8 -59.4 -80 -95 -95

Table TNG 107-19: DPBO cable model parameters ABC


Name Description DPBO cable model parameters ABC Specifies the DPBO Cable Model: by means of three scalar parameters DPBO_CableModel_A, DPBO_CableModel_B and DPBO_CableModel_C. These three parameters match the parameters DPBOESCMA, DPBOESCMB and DPOBESCMC described in ITU-T G.997.1 7.3.1.2.13a3. Line DS -1..1.5 for all three DPBO Cable Model Parameters. [DPBO_CableModel_A]= 0 [DPBO_CableModel_B]= 0 Hz-0.5 [DPBO_CableModel_C]= 0 Hz-1 Granularity & Unit [DPBO_CableModel_A]= 2-8 [DPBO_CableModel_B]= 2-8 Hz-0.5 [DPBO_CableModel_C]= 2-8 Hz-1

Instances Values Default

TNG 107-12

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-20: DPBO minimum and maximum frequency


Name Description DPBO minimum frequency, DPBO maximum frequency Specifies the frequency range over which DPBO shaping is applied. The DPBO Minimum and Maximum Frequencies match the DPBOFMIN and DPBOFMAX parameters described in ITU-T G.997.1 7.3.1.2.13a5&6). In case the DPBO Minimum Frequency is larger than the DPBO Maximum Frequency, the modem subsystem raises the configuration error failure. Instances Values Default Line DS 0..30000 kHz DPBO Minimum Frequency = 0 kHz DPBO Maximum Frequency = 30000 kHz Granularity & Unit 1 kHz

Table TNG 107-21: DPBO minimum usable signal level


Name Description DPBO minimum usable signal level Specifies the DPBO minimum usable signal level, matching the DPBOMUS parameter described in ITU-T G.997.1 7.3.1.2.13a4. Note: this parameter refers to a mask level. Instances Values Default Granularity & Unit Line DS -140..0 dBm/Hz -127.5 dBm/Hz 0.1 dBm/Hz

Table TNG 107-22: Mode independent custom PSD mask downstream


Name Description Mode independent custom PSD mask downstream Specifies the DPBO Mode Independent Custom PSD Mask. It substitutes the PSDMASKds parameter and derived subsets described in ITU-T G.997.1 7.3.1.2.13b. Note: as DPBO shaping is enabled, this parameter overrides the Custom MIB PSD Mask parameter defined in Custom MIB PSD Mask. Nonetheless it possible to use the DPBO parameter MICPSDMASKds to define a custom PSD mask. The DPBO Mode Independent Custom PSD Mask consists of a set of breakpoints, with a maximum of 32 breakpoints, and may contain two subsets of breakpoints:


Instances (1 of 2)

The first subset defines the DPBO Custom PSD Mask. This subset matches the DPBOPSDMASKds parameter described in ITU-T G.997.1 7.3.1.2.13b1. The second subset, if any, defines the DPBO Minimum Override Mask. The DPBO Minimum Override Mask subset matches the DPBOLFO parameter described in ITU-T G.997.1 7.3.1.2.13b1.

Line DS

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-13

TNG 107 VDSLx parameters

Values

Frequency value range: 0..30000 kHz PSD value range: -95..0 dBm/Hz

Default

For frequency 0 kHz: PSD level 0 dBm/Hz For frequency 30000 kHz: PSD level 0 dBm/Hz

Granularity & Unit

Frequency: 1 kHz PSD: 0.1 dBm/Hz

(2 of 2)

Table TNG 107-23: Extra DPBO maximum usable frequency control


Name Description Extra DPBO maximum usable frequency control (xDPBOMUFCTRL) This parameter specifies the electrical length to be used for the computation of the DPBO MUF. It enables a more flexible control of the computation of the DPBO MUF compared to the requirements of ITU-T G.997.1 [7.3.1.2.13c. Important notice: this DPBO MUF does not relate to the MUF described in Maximum usable frequency. When the special value fromDPBOESEL is used, the modem subsystem shall assume that the actual value of this configuration parameter is equal to the value set in DPBO electrical length. Instances Values Line DS 0..255.9 dB Special value: fromDPBOESEL Default Granularity & Unit fromDPBOESEL 0.1 dB

Table TNG 107-24: Extra DPBO remote side electrical length


Name Description Extra DPBO remote side electrical length (xDPBORSEL) If this xDPBORSEL configuration parameter is set different from 0dB it modifies the standard DPBO algorithm by adding an extra term, function of xDPBORSEL. Line DS 0..255.99 dB 0 dB 0.01 dB

Instances Values Default Granularity & Unit

Table TNG 107-25: Extra DPBO offset


Name Description Instances (1 of 2) Extra DPBO offset (xDPBOOffset) This xDPBOOffset configuration parameter modifies the standard DPBO algorithm by adding an offset of magnitude xDPBOOffset. Line DS

TNG 107-14

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Values Default Granularity & Unit (2 of 2)

-256..255.9 dB 0 dB 0.01 dB

Table TNG 107-26: Maximum deviation from maximum interleaving delay


Name Description Maximum deviation from maximum interleaving delay Specifies the maximum deviation from the Maximum Interleaving Delay (see TNG 107-12) allowed in the final actual delay introduced by the interleaving and deinterleaving function (US bearers only). This parameter implicitly fixes a minimum interleaving delay (I.Del.) to achieve: Minimum I. Del. = maximum I. Del. - maximum deviation mrom maximum I. Del. Note: this parameter is given in number of bytes (although the maximum interleaving delay is given in ms). An interleaving delay of x bytes corresponds to a delay of 8 x/R ms, where R is the bitrate crossing the interleaver/de-interleaver of the involved bearer, in kbps. Note: This parameter is especially intended to be used by a bonding manager subsystem, implemented outside the modem. Instances Values Bearer US 0..16000 [bytes] Special value: unconstrained: no minimum Interleaver Delay applies. Default Granularity & Unit unconstrained 1 byte

Table TNG 107-27: Custom band plan


Name Description Custom Band Plan Specifies custom band plan in case Predefined Band Plan selection (see Predefined band plan) is set to bandPlanCustom, ignored otherwise. It always excludes the Upstream or Downstream optional Band control (see Optional band mode). Line Maximum 8 bands can be specified: band = [Start frequency, Stop frequency, Direction] where: Frequency: 0..30000 kHz Direction: Upstream (dirUp) or Downstream (dirDown) Granularity & Unit 1kHz (for frequency)

Instances Values

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-15

TNG 107 VDSLx parameters

Table TNG 107-28: Predefined band plan


Name Description Instances Values Predefined Band Plan Specifies the type of Band Plan. Line bandPlanCustom: custom defined band plan (see also VDSLx Custom Band Plan parameter) bandPlanA: 998 band plan bandPlanB: 997 band plan bandPlanC: Fx band plan (see also Fx Band Plan Parameter) bandPlanAext: ITU-T G.993.2 VDSL2 Annex C band plan bandPlanChina1: China band plan 1 bandPlanChina2: China band plan 2 bandPlanAnnexA: ITU-T G.993.2 VDSL2 Annex A (extended) band plan bandPlanAnnexB998E: ITU-T G.993.2 VDSL2 Annex B band plan type 998E bandPlanAnnexB997E: ITU-T G.993.2 VDSL2 Annex B band plan type 997E bandPlanAnnexB998ADE: ITU-T G.993.2 VDSL2 Annex B band plan type 998ADE bandPlanAnnexBHPE: ITU-T G.993.2 VDSL2 Annex B band plan type HPE When bandPlanAnnexBHPE is selected, the following operational modes (see Operating modes) bits are cleared: ITU_G993_2_8A_Bit, ITU_G993_2_8B_Bit, ITU_G993_2_8C_Bit, ITU_G993_2_8D_Bit, ANSI_T1_424Bit, ETSI_TS_101_270Bit, ITU_G993_1Bit, and IEEE802.3ah_Bit. Granularity & Unit -

Table TNG 107-29: Maximum number of bands


Name Description Maximum Number of Bands Specifies the maximum number of bands to be supported for the given band plan. In case the selected band plan (see DPBO assumed exchange PSD mask and Predefined band plan) contains more bands, the modem disables bands located at higher frequencies first. Otherwise, this parameter has no effect. The optional band is NOT counted as a band, and does not take part to the number of bands (example: if the maximum number of bands is set to 3, the modem is allowed to use the optional band + DS1 + US1 + DS2). The special value unlimited disables the maximum number of band constraint. Instances Values Unit Line unlimited, 2..8 Bands

TNG 107-16

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-30: Maximum usable frequency


Name Description Maximum Usable Frequency Specifies the maximum frequency usable both VTU-O and VTU-R VDSL modems, in showtime. The special value unlimited disables the maximum usable frequency constraint. In case the configuration of this parameter would conflict with other parameters, the configuration is rejected. Note: This parameter is not equivalent to the MUF parameter commonly used when dealing with CO-RT mixed deployment and PSD shaping. This last MUF parameter is equivalent to the ADSL band mode end frequency parameter. Instances Values Unit Line unlimited, 1104..30000 kHz kHz

Table TNG 107-31: ADSL band mode


Name Description ADSL Band Mode Specifies whether the VDSLx modem is allowed to use the ADSL spectrum or not in DS. The end frequency of the ADSL band is specified by the ADSL band mode end frequency. It controls the use of the ADSL spectrum within the defined VDSLx band plan, with the exception of the optional band, which is not impacted by this parameter. Note: whatever the value of this parameter, the modem is never allowed to exceed the configured PSD mask (see PSD ceiling). Instances Values Line 0: usage of ADSL spectrum is allowed. 1: usage of the ADSL spectrum is not allowed. Granularity & Unit -

Table TNG 107-32: ADSL band mode end frequency


Name Description ADSL Band Mode End Frequency This parameter specifies the ADSL band end frequency. The start frequency is always 25 kHz. It is used together with parameter 0 (see ADSL band mode). It controls the use of the ADSL spectrum within the defined VDSLx band plan, with the exclusion of the optional band, which is only controlled through the Optional band mode. This parameter is ignored when the ADSL spectrum usage is allowed.This parameter is assumed 1104 kHz if no value, or if the special 0 kHz value is configured. Instances Values Granularity & Unit Line 0 kHz, 276..2208kHz 1 kHz

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-17

TNG 107 VDSLx parameters

Table TNG 107-33: Optional band mode


Name Description Optional Band Mode Indicates if the VDSLx modem is allowed to use the optional band (25 kHz..x kHz) or not and defines its direction in case the use is allowed. The x value is a parameter specified by the ADSL band mode end frequency. This parameter is ignored and the optional band usage prohibited if not supported by the HW. The optional band usage is independent of the ADSL band mode parameter (0): in case the ADSL band mode is set to not allowed, and the optional band mode is enabled, the modem is still allowed to use the optional band. Note: on ISDN boards, the optional band start frequency is shifted from 25 kHz to 138 kHz. Note: This parameter must be enabled for VDSL2 profiles that require an upstream optional band, so they can be properly configured. Instances Values Granularity & Unit Line Off, Up or Down -

Table TNG 107-34: Optional band mode end frequency


Name Description Optional Band Mode End Frequency When the optional band usage is enabled (see Optional band mode), this parameter specifies the optional band end frequency. The start frequency is always 25 kHz on POTS cards, and 138 kHz on ISDN cards. The beginning of the first DS band is shifted accordingly (no spectrum overlap). When the optional band usage is disabled, this parameter still fixes the beginning of the normal DS band. It is assumed 138 kHz if no value, or if the special 0 kHz value is configured. Instances Values Granularity & Unit Line 0 kHz, 138..276 kHz 1 kHz

TNG 107-18

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-35: US power backoff mode


Name Description US Power Backoff Mode Specifies the upstream power backoff mode:

PBO Off (PBO with Transmit PSD Mask): The VTU directly uses the US PSD Mask parameter (see above) as the transmit PSD mask. PBO On (PBO with Receive PSD Mask): The VTU derives the transmit PSD mask from the US Power BackOff PSD Mask parameter.

and following settings are applicable for VDSL2 only in the sense that in VDSL1 they shall be interpreted as PBO On:

PBO On, Policing Passive: In addition to PBO On Mode, the VTU-C modem subsystem flags any violation of UPBO US PSD constraint by the VTU-R. PBO On, Policing Shutdown: In addition to PBO On Mode, the VTU-C modem subsystem flags any violation of UPBO US PSD constraint by the VTU-R. When such a violation occurs, the VTU-O also raises the CPE Policing activation failure, and goes back to IDLE state to avoid a spectrum management issue in the network. PBO On, Policing US0 only: In addition to PBO On Mode, the VTU-C modem subsystem flags any violation of UPBO US PSD constraint by the VTU-R. When such a violation occurs, as a workaround, the VTU-O forces the line to use US0 band only in all following line operations, until the VTU-O is restarted by the XDSL manager (with or without new configuration).

Note: If US Power Backoff Mode is set to PBO On, Policing US0 only and the optional band usage is disabled (see Optional band mode), the configuration is rejected and the configuration error failure is raised. Instances Values Line US psdPboOff psdPboOn psdPboOnPolicingPassive psdPboOnPolicingShutdown psdPboOnPolicingUS0Only Granularity & Unit -

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-19

TNG 107 VDSLx parameters

Table TNG 107-36: DS G.hs tones power mode


Name Description DS G.hs tones power mode This parameter determines the mode of DS tones used during G.hs (handshake) sequence. It is defined as an array of 4 mode values: one per possibly used DS tone set in VDSLx mode: A43, B43, A43c, and V43: GhsPSDMode = [GhsPSDMode_A43; GhsPSDMode_B43; GhsPSDMode_A43c; GhsPSDMode_V43] The following possible modes are defined:

The special value default is translated as the maximum power allowed in the ITU-T G.994.1 standard for that tone set. The special value manual is fetched from the DS G.hs tones power manual level requirements. The special value automatic is translated as the maximum power derived from the configured Tx DS PSD (see VDSL1 Limit Tx PSD mask for VDSL1 or VDSL 2 Limit Tx PSD mask for VDSL2), according to the following formula and table: If fi is the frequency of the middle tone of the tone set #i, if xi is the maximum DS template PSD allowed by the MIB at frequency fi, then the power of each tone of the tone set #i is: Pi = 36.35 + min(max(xi + 3, mi), Si), where: Si is the maximum standard value for tone set #I, and mi is the minimum PSD floor, defined in Table TNG 107-37.

An NSIF field is introduced for V43 back off communication from VTU-O to VTU-R. If the final derived value falls below the minimum value handled by the G.994.1 standard for the considered set, that minimum allowed value is used. Instances Values Granularity & Unit Line {default; automatic; manual} -

Table TNG 107-37: Minimum PSD Floor


Tone set i A43 B43 A43c V43 Si TBD dBm/Hz TBD dBm/Hz TBD dBm/Hz TBD dBm/Hz Si in conservative mode(1) -65 dBm/Hz -70 dBm/Hz -70 dBm/Hz -70 dBm/Hz

Note
(1)

Alcatel-Lucent will determine if the conservative mode will be used or not. This has to be hardcoded in the chipset implementation.

TNG 107-20

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-38: DS G.hs tones power manual level


Name Description DS G.hs tones power manual level This parameter determines the maximum power of DS tones used during G.hs (handshake) sequence, in case the manual mode is selected. It is defined as an array of 4 PSD values: one per possibly used DS tone set in VDSLx mode: A43, B43, A43c, and V43: GhsPSD = [manual_A43; manual_B43; manual_A43c; manual_V43] Each value is given in dBm/Hz. The power of each tone of a considered set is equivalent to the given PSD value integrated in a total bandwidth of 4.3125 kHz. One special value is defined: the value -99 dBm/Hz indicates that the full set is not used (that is, no power allowed). Instances Values Granularity & Unit Line -99..-40 dBm/Hz 0.5 dBm/Hz

Flavor-dependent configuration parameters


All parameters grouped under this requirement have a common for all DSL flavours supported in Alcatel-Lucent DSLAM products (including VDSL and VDSL2). However, the configured value, assigned by the operator, can be flavor dependent. Consequently, all parameters will have several instances: one per flavor.

Modem features Maximum aggregate transmit power PSD ceiling Support of Maximum PSD under -80dBm/Hz Custom MIB PSD Mask US Power BackOff PSD: US power backOff PSD mask selection US power backOff PSD AB parameters US power backoff PSD full custom parameters
Table TNG 107-39: Modem features
Name Description Modem Features Specifies modem features which can be allowed or not by the operator. Currently, only bit 0 (LSB) of this bitmap is interpreted by the VDSLx modem subsystem. BIT0 Standard Compliancy: if active (1), the modem subsystem must turn off all features not strictly compliant to the standard. If not active (0), the modem subsystem is allowed to use non-standard features, via the NSIF G.hs bits. Instances Values Granularity & Unit Line Bitmap -

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-21

TNG 107 VDSLx parameters

Table TNG 107-40: Maximum aggregate transmit power


Name Description Maximum Aggregate Transmit Power Specifies the maximum total power level that is allowed to be transmitted in the corresponding direction. This parameter is used to reduce the maximum allowed PSD derived from Custom MIB PSD Mask, VDSL1 Limit Tx PSD mask or VDSL 2 Limit Tx PSD mask. Note that this parameter overrules maximum aggregate Tx power standard restrictions, except if the special value standard is configured. The special value standard is used as special value:

Instances Values Granularity & Unit

For VDSL1: If the selected PSD is referring to a predefined PSD, then the maximum aggregate transmit power defined in the corresponding DSL standard must be used, in accordance with the deployment type PSD: FTTEx or FTTCab. Otherwise (customized PSD): no power limitation has to be applied. For VDSL2: The applicable maximum power constraint is the one corresponding to the selected VDSL2 profile.

Line DS, US -31..25.5 dBm 0.1 dBm

Table TNG 107-41: PSD ceiling


Name Description Maximum PSD (1) The PSD ceiling parameter specifies the maximum power spectral density level allowed on the line at the transmitter output (upstream and downstream) for initialization and showtime signals. This parameter shall be used to further restrict the maximum Tx PSD mask derived from Custom MIB PSD Mask, VDSL1 Limit Tx PSD mask or VDSL 2 Limit Tx PSD mask. The value no_constraint is used as special value, which avoids restrictions to the maximum Tx PSD mask. Note that this parameter is defined on the PSD template, not on the PSD mask. Instances Values Granularity & Unit Line DS, US 0..-95.5 dBm/Hz or no_constraint 0.1 dBm/Hz

Note
(1)

The Maximum PSD parameter cannot be used to boost the PSD beyond the configured LimitTxPSD and MIB Mask (See Custom MIB PSD Mask, VDSL1 Limit Tx PSD mask or VDSL 2 Limit Tx PSD mask), it can only be used to put additional constraints, i.e. to further lower the PSD. The modem supports extended maximum PSD range under to -80 dBm/Hz.

TNG 107-22

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-42: Support of Maximum PSD under -80dBm/Hz


The modem supports extended maximum PSD range under to -80 dBm/Hz.

Table TNG 107-43: Custom MIB PSD Mask


Name Description Custom MIB PSD Mask Specifies custom PSD Mask. Specifies the maximum transmit PSD allowed for the corresponding direction on a VDSLx line In VDSL1 mode, this parameter will be missing, in case a predefined limit Tx PSD mask other than psdMaskCustom is defined (see VDSL1 Limit Tx PSD mask). In VDSL2 mode, this parameter can be missing, in case a predefined limit Tx PSD mask other than psdMaskCustom is defined (see VDSL 2 Limit Tx PSD mask). If neither this parameter nor a Tx limit pre-defined PSD mask is configured, the configuration is rejected. If both this parameter and a Tx limit PSD mask is configured, the modem takes the minimum of the two masks, tone per tone (VDSL2 only). The PSD mask is made by connecting the points with straight lines, considering a linear PSD axis in [dBm/Hz], and either a linear, either a logarithmic frequency axis in [Hz], depending on the psdFreqScale parameter. The PSD has to be considered as a Mask or a Template, depending on the PsdType parameter. Note: This parameter is ignored when DPBO is enabled and the modem takes into account the DPBO shaping procedure instead. Instances Values Line DS, US Up to 20 PSD points can be specified and are supported for US Up to 32 PSD points can be specified and are supported for DS PSD point = [Frequency, PSD value]

Frequency: 0..12000 kHz PSD value: -25 to -127.5 dBm/Hz

No sub-array is allowed in the array. In VDSL2 mode, the rules of ITU-T G.993.2, section 7.2.1.1.2 are to be considered. The custom MIB PSD mask being the PSD specification of a signal, un-specified regions of the spectrum, if needed, are assumed by default at the maximum allowed PSD value (0 dBm/Hz). PsdFreqScale is lin or log. PsdType is Mask or Template Granularity & Unit 0.1 dBm/Hz for PSD value 1 kHz for Frequency PsdFreqScale and PsdType are boolean

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-23

TNG 107 VDSLx parameters

Table TNG 107-44: US power backOff PSD mask selection


Name Description US Power BackOff PSD Specifies the maximum receive PSD allowed for the US direction on a VDSLx line in case of psdPboOn (see US power backoff mode), ignored otherwise. The VDSLx modem subsystem checks consistency between the PSD Mask settings and other configuration parameters. If not consistent, the configuration is rejected by raising the Configuration Error failure (for example, the modem subsystem rejects configurations with inconsistent DS and US PSD mask settings). Instances Values US Power BackOff Following special configurations are supported:


Granularity & Unit -

PsdMaskABParameters (see also US power backOff PSD AB parameters) psdMaskFullCustom (See also US power backoff PSD full custom parameters)

Following masks are supported: psdMaskANSI_A psdMaskANSI_F psdMaskANSI_CustomEx (1) psdMaskANSI_CustomCab (1) psdMaskETSI_A psdMaskETSI_B psdMaskETSI_C psdMaskETSI_D psdMaskETSI_E psdMaskETSI_F psdMaskETSI_CustomEx (1) psdMaskETSI_CustomCab (1)

Remarks: The ANSI noise profiles are not defined yet for types B, C, D and E. The modem subsystem rejects the configuration of those ones. The ETSI UPBO masks for noise types A and B are the same. The modem subsystem rejects the configuration if an ANSI UPBO mask is used together with the ETSI operating mode, and vice versa (VDSL1 only). The _CustomEx/Cab masks allow the modem subsystem to use customized and pre-defined UPBO masks for specific deployment scenarios.

Note
(1)

This psdMask is outphasing

TNG 107-24

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-45: US power backOff PSD AB parameters


Name Description US Power BackOff PSD AB Parameters Specifies the a and b values in order to compute the PSDREF to be used for USPBO. If US Power Back Off is psdMaskABParameters, it is applied as follows:

PSDREF(f) = -(a + b f)
They are structured as an array [a b], f is the frequency in MHz. This parameter is only used when the mask selection is set to PsdMaskABParameters (see US power backOff PSD mask selection). Instances Values Default Granularity & Unit US Power BackOff (per upstream Bands) [40..80.95 dBm/Hz; 0..40.95 dBm/Hz] [For US0: 40 dBm/Hz; 0 dBm/Hz] 0.01 dBm/Hz; 0.01 dBm/Hz

Table TNG 107-46: US power backoff PSD full custom parameters


Name Description US Power BackOff PSD Full Custom Parameters This parameter is only used when the mask selection is set to psdMaskFullCustom (see US power backOff PSD mask selection). US Power BackOff PSD Full Custom Mask is only supported for VDSL1.

Flavor-specific configuration parameters


The following parameters are VDSL1 specific:

VDSL1 Limit Tx PSD mask Fx band plan frequency


Table TNG 107-47: VDSL1 Limit Tx PSD mask
Name Description Limit Tx PSD Mask For DS and US: specifies the maximum transmit PSD allowed for the corresponding direction on a VDSL1 line. A pre-defined set of standard PSD masks is defined. It is the responsibility of the VDSL1 modem subsystem to translate the PSD Mask number into the standard definition. The VDSL1 modem subsystem checks consistency between the PSD Mask settings and other configuration parameters. If not consistent, the configuration is rejected by raising the Configuration Error failure (for example, the modem subsystem rejects configurations with inconsistent DS and US PSD mask settings). Instances Line DS, US

(1 of 2)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-25

TNG 107 VDSLx parameters

Values

psdMaskCustom: custom defined PSD Mask (see Custom MIB PSD Mask) Line DS/US: psdMaskANSI_FTTEx_M1 psdMaskANSI_FTTEx_M2 psdMaskANSI_FTTCab_M1 psdMaskANSI_FTTCab_M2 psdMaskANSI_FTTCab_M1_ADSL: FTTCab.M1 used for US psdMaskANSI_FTTCab_M2_ADSL: FTTCab.M2 used for US psdMaskANSI_FTTCab_M1_ADSL2+: FTTCab.M1 used for US psdMaskANSI_FTTCab_M2_ADSL2+: FTTCab.M2 used for US Remarks:

The modem subsystem rejects the configuration if another band plan than 998 has been selected in combination with ANSI PSD masks. The modem subsystem rejects the configuration if the ETSI Operating Mode has been selected in combination with those ANSI PSD masks.

psdMaskETSI_PexP1.M1: P.M1 used for US psdMaskETSI_PexP1.M2: P.M2 used for US psdMaskETSI_PexP2.M1: P.M1 used for US psdMaskETSI_PexP2.M2: P.M2 used for US psdMaskETSI_Pcab.M1: P.M1 used for US psdMaskETSI_Pcab.M2: P.M2 used for US psdMaskETSI_PcabX.M1_ADSL: P.M1 used for US psdMaskETSI_PcabX.M2_ADSL: P.M2 used for US psdMaskETSI_Pcab.M1_ADSL2+: P.M1 used for US psdMaskETSI_Pcab.M2_ADSL2+: P.M2 used for US psdMaskETSI_PexP2.M2_ADSL_Sample1: P.M2 used for US psdMaskETSI_PexP2.M2_ADSL_Sample2: P.M2 used for US psdMaskETSI_PexP2.M2_ADSL_Sample3: P.M2 used for US psdMaskETSI_PexP2.M2_ADSL_Sample4: P.M2 used for US Remarks:


Granularity & Unit (2 of 2) -

The modem subsystem uses the value of the Optional Band Mode parameter whether to use one of both variants for the P.M1 and P.M2 US masks. The modem subsystem uses the value of the ADSL Band Mode parameter whether to use variant A or B for the Pcab masks. The modem subsystem uses the value of the VDSLx Band Plan parameter whether to use the 998 or 997 variants of the ETSI PSD masks. The modem subsystem rejects the configuration if another band plan than 998 or 997 has been selected in combination with ETSI PSD masks. The modem subsystem rejects the configuration if the ANSI Operating Mode has been selected in combination with those ETSI PSD masks.

Table TNG 107-48: Fx band plan frequency


Name Description Instances Values Granularity & Unit Fx Band Plan Frequency Specifies Fx frequency in case of bandPlanC band plan, ignored otherwise. Line 3750..12000 kHz 1 kHz

TNG 107-26

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

The following parameters are VDSL2 specific:

VDSL 2 Limit Tx PSD mask US Power Back-off electrical length override Virtual Noise PSD Virtual Noise SNRM_MODE Erasure detection in INP
Table TNG 107-49: VDSL 2 Limit Tx PSD mask
Name Description Limit Tx PSD Mask For DS and US: specifies the maximum transmit PSD allowed for the corresponding direction on a VDSL2 line. A pre-defined set of standard PSD masks is defined. It is the responsibility of the VDSL2 modem subsystem to translate the PSD Mask number into the standard definition. The VDSL2 modem subsystem checks consistency between the PSD Mask settings and other configuration parameters. If not consistent, the configuration is rejected by raising the Configuration Error failure (for example, the modem subsystem rejects configurations with inconsistent DS and US PSD mask settings). Instances Values Line DS, US

psdMaskCustom: custom defined PSD Mask (see Custom MIB PSD Mask). In this case, there is no limit mask (unlimited), and the maximum Tx PSD mask envelope is determined by the Custom MIB PSD mask. PsdMaskRegionA: refers to North American standard Annex A Remarks: Detailed PSD Mask for region A can be derived from the Optional band mode end frequency parameter, which fixes US0/DS1 transition frequency. PsdMaskRegionB_M1 PsdMaskRegionB_M2: refers to European standard Annex B Remarks: Detailed PSD Mask for region B has to be used in combination with the Predefined band plan parameter to check validity. Detailed PSD Mask for region B can be derived from other parameters. The modem subsystem shall reject the configuration if another band plan than 998 or 997 has been selected in combination with ETSI PSD masks. PsdMaskRegionC: refers to Japanese standard Annex C PsdMaskRegionC corresponds to the G993.2 [5] AnnexC (Japan region) and shouldnt be misinterpreted as the G993.1 [4] AnnexC. It is also associated to the BandPlanAext band plan (see Band plan).

Granularity & Unit

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-27

TNG 107 VDSLx parameters

Table TNG 107-50: US Power Back-off electrical length override


Name Description US Power Back-off electrical length override This parameter tells the VTU-O to override the kl0 (electrical length) estimated by the VTU-R. One special value is defined: the value electricalLengthEstimated indicates that the US Power Back-off electrical length estimated by the VTU-T is not overwritten by the VTU-O. Instances Values Line 0..127.5; Electrical Length Estimated Default Value is Electrical Length Estimated Note: We consider here that electrical length is positive when the loop gain is negative in dB (smaller than one in linear). Granularity & Unit 0.1 dB @ 1 MHz

Table TNG 107-51: Virtual Noise PSD


Name Description Virtual Noise PSD TXREFVNL defines the Transmitter Referred Virtual Noise Level to be used in determining the SNR margin. It is defined as an array of 32 breakpoints for downstream bands and 16 breakpoints for upstream ones. Breakpoints definition is identical to the VDSL2 MIB PSD defined in Custom MIB PSD Mask. Points are given in frequency [kHz] and PSD [dBm/Hz] components, and are translated to sets of arrays per US band: TXREFVNL[..] [] = [(t1, PSD1), (t2, PSD2), , (tN, PSDN)], where t1 and tN are, respectively, the lower and higher band edge frequencies of the band. Arrays are then concatenated to make one unique array. When the VTU operates with 8.625 kHz sub-carrier spacing, all odd sub carriers are converted by the VTU, to the closest even value, and values t1 and tN are rounded (up and down, respectively) to even values. Instances Values Line PSD component of breakpoint: -40 dBm/Hz..-140 dBm/Hz Special Value (default):NoVirtualNoise (- dBm/Hz) Frequency component of breakpoint: 0..30000 kHz Granularity & Unit 1 kHz; 0,5 dBm/Hz

Table TNG 107-52: Virtual Noise SNRM_MODE


Name Description Instances (1 of 2) Virtual Noise SNRM_MODE Selects the reference noise PSD that shall be considered when evaluating the noise margin. US, DS

TNG 107-28

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Values

SNRM_MODE_1: the reference noise PSD is the external noise PSD present at U interface. SNRM_MODE_2: the reference noise PSD is the maximum (tone per tone) between the external noise PSD present at U interface and the received virtual noise derived from parameter Virtual Noise PSD.

Note:


Granularity & Unit (2 of 2) -

If SNRM_MODE_2 for US is selected, and the virtual noise is not supported by the VTU-O, the VTU-O raises a configuration error failure. If SNRM_MODE_2 for DS is selected, and the virtual noise is not supported by the VTU-R, the VTU-O falls back to DS SNRM_MODE_1, and proceeds normally.

Table TNG 107-53: Erasure detection in INP


Name Description Erasure detection in INP When VTUs select internal FEC and interleaving parameters according to configured minimum INP and maximum interleaver delay, fixes whether the Erasure detection mechanism has to be ignored or not. Bearer US, DS When set to 1, it indicates that the VTU receiver shall select framing parameters so that INP_no_erasurep INP_minConfigured. This means that the minimum configured INP (together with maximum interleaver delay) will already be achieved with the erasure detection mechanism disabled. When set to 0, it indicates that VTUs receivers are not required to select framing parameters that ensures INP_no_erasurep INP_minp. In all cases, the VTU-R receiver meets the requirement, INPp INP_minConfigured. This applies to all latency paths. Unit Binary (0/1)

Instances Values

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-29

TNG 107 VDSLx parameters

Supported operational data parameters


The Initialization value is the parameter value when entering the showtime (L0) state. Consequently, the value has to be derived during initialization. The Showtime value is the (current if updated) parameter value during the showtime state. The Update frequency is the update frequency of the parameter during showtime (L0) state. The VDSLx Modem Subsystem assures that the Showtime values (if applicable for the considered parameter) are available for retrieval over the xDSL API within 10 seconds after entering the L0 state. During the first 10 seconds of the L0 state, the VDSL Modem Subsystem returns the Initialization values (if applicable for the considered parameter) if the Showtime value for the considered parameter is not available yet. The following operational data parameters are supported:

Current operational mode Operational mode capabilities SNR margin Loop attenuation Signal attenuation Aggregate output power Actual average PSD Last state transmitted Attainable line bitrate Actual line bitrate Line relative capacity occupation Attainable transport bitrate (per bearer channel) Actual transport bitrate (per bearer channel) Actual interleaving delay (per bearer channel) Actual impulse noise protection (per bearer channel) Actual TPS-TC mode TPS-TC mode capabilities Actual tone spacing Actual US PBO electrical length Actual VTU-R timing advance Actual highest frequency used Actual sub-carrier group size Actual maximum PSD VDSL2 annex modes capabilities VDSL2 actual standard limit PSD VDSL2 limit PSD mapping Actual DS virtual noise SNRM_MODE Actual use of Trellis Coding Actual used cyclic extension Actual framing parameters

TNG 107-30

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-54: Current operational mode


Name Description Instances Values Granularity & Unit Initialization value Update frequency Current Operational Mode The operational mode used for the current operation of the VDSLx modem subsystem (see Operating modes). Line See Operating modes. Only 1 bit can be set to 1 at a time. Defined during configuration and G.hs. NA

Table TNG 107-55: Operational mode capabilities


Name Description Instances Values Granularity & Unit Update frequency Operational mode Capabilities The total set of operational modes supported by the VTU-O and the VTU-R respectively. Near-end/Far-end See Operating modes. NA

Table TNG 107-56: SNR margin


Name Description SNR Margin Indicates the current showtime noise margin: the maximum increase (in dB) of the reference noise PSD (at all relevant frequencies), such that the BER of each TPSTC stream does not exceed the maximum BER specified, without any change of PMD parameters (that is, bits and gains) and PMS-TC parameters (for example, FEC parameters). The BER is referenced to the output of the PMS-TC function (that is, the / interface). * the maximum increase (in dB) of the reference noise power that can be tolerated such that the VTU can still meet the target BER requirement. The reference noise PSD, in VDSL2 mode, does not correspond with the total (internal + external) noise. The SNR Margin in a given band shall assume a PSD noise increase in the relevant band only. Instances Values Granularity & Unit Update frequency Global DS/US for VDSLx, and per band for VDSL2 on top (including US0 band). -64..+63 dB 0.1 dB DS: each = 10 seconds via EOC @ VTU-O US: each < 10 seconds @ VTU-O

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-31

TNG 107 VDSLx parameters

Table TNG 107-57: Loop attenuation


Name Description Loop Attenuation The difference in dB between the power received at one end and that transmitted at the opposite end over all subcarriers during initialization. It is not updated during showtime. It corresponds to the Line Attenuation as defined in G.997.1 Global US for VDSLx Global DS, and on top per band for VDSL2 (including US0/DS0 band). Values 0..102.3 dB Note: when the actual loop attenuation is exceeding an extremum value that can be represented, clamping to this extremum representable value is done. Granularity & Unit Accuracy Update frequency 0.1 dB 0.5 dB NA

Instances

Table TNG 107-58: Signal attenuation


Name Description Signal Attenuation The difference in dB between the power received at one end and that transmitted at the opposite end over all subcarriers during showtime. Note: difference with Loop Attenuation is that the transmit power has changed for the subcarriers and that the total number of subcarriers during showtime typically will be less than during initialization. Instances Global US for VDSLx Global DS, and on top per band for VDSL2 (including US0/DS0 band). Values 0..102.3 dB Note: when the actual loop attenuation is exceeding an extremum value that can be represented, clamping to this extremum representable value is done. Granularity & Unit Update frequency 0.1 dB DS: each = 10 seconds via EOC @ VTU-O US: each < 10 seconds @ VTU-O

Table TNG 107-59: Aggregate output power


Name Description Instances Values Aggregate Output Power Actual aggregate output power (that is, the total output power for the carriers of the corresponding direction) when the modem is in showtime. DS/US -31..+31 dBm Note: when the actual aggregate transmit power is exceeding an extremum value that can be represented, clamping to this extremum representable value is done. Granularity & Unit (1 of 2) 0.1 dBm

TNG 107-32

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Accuracy Update frequency

1 dB (maximum admissible deviation with actual measured value) DS: each bit swap US: each bit swap

(2 of 2)

Table TNG 107-60: Actual average PSD


Name Description Instances Values Aggregate average PSD Actual Average (in dB) Transmit power spectrum density over the loaded subcarriers. DS/US -95..0 dBm/Hz. A special value Out of Range indicates the parameter is out of range to be represented. Granularity & Unit Accuracy Update frequency 0.1 dBm/Hz 0.1 dBm/Hz DS/US: each bit swap

Table TNG 107-61: Last state transmitted


Name Description Last state transmitted This parameter represents the last successful transmitted (VTU-O instance) and received (VTU-R instance) SOC message ID during initialization sequence in the relevant direction, in the last full initialization performed on the line. Thus, initialization states are defined as the SOC message code IDs. Instances Values Granularity & Unit Update frequency DS (VTU-O)/US (VTU-R) 0x0 -> 0xFF 1 Not Applicable

Table TNG 107-62: Attainable line bitrate


Name Description Attainable Line Bitrate Indicates the maximum bitrate the modem can sustain on the line (that is, the transported payload plus all overhead from the PMD (If a Trellis encoder would be used, the overhead will be included in the Attainable Line Bitrate), PMS-TC and TPS-TC layers) taking the current configuration into account (for example, the Attainable Line Bitrate assumes that the current interleaver and coding settings are not changed). If multiple bearer channels are active, the calculation assumes that all capacity would be allocated to the bearer channel with the highest coding gain. The value only depends on the actual noise margin on the line. Instances (1 of 2) DS/US

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-33

TNG 107 VDSLx parameters

Values

0..65535 Remark: in case of no EOC, the initialization value for Attainable DS Line Bitrate is returned.

Granularity & Unit Update frequency

1 kbps DS: each = 10 seconds via EOC @ VTU-O US: each < 10 seconds @ VTU-O

(2 of 2)

Table TNG 107-63: Actual line bitrate


Name Description Actual Line Bitrate The line rate corresponding to the Actual transport Bitrate (that is, the actual transported payload plus all overhead information from the PMD (If a Trellis encoder would be used, the overhead shall be included in the Attainable Line Bitrate), PMS-TC and TPS-TC layers). The line rate is given by the number of bits per DMT symbol (VDSL2 PMD sync symbol excluded), multiplied by fs: the number of DMT symbols per second, and divided by 1000 to provide the result in [kbps] unit. Instances Values Granularity & Unit Update frequency DS/US 0..262143 1 kbps NA

Table TNG 107-64: Line relative capacity occupation


Name Description Line Relative Capacity Occupation The ratio of the Actual Line Bitrate and the Attainable Line Bitrate when both are available. In case of an activation error Configuration not feasible, it is set to 100 % for each direction where the minimum bitrate cannot be sustained. Instances Values Granularity & Unit Update frequency DS/US 0..100% 1% DS: derived from Actual and Attainable Line Bitrate US: derived from Actual and Attainable Line Bitrate

TNG 107-34

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-65: Attainable transport bitrate (per bearer channel)


Name Description Attainable transport Bitrate Indicates the maximum net data bitrate (that is, transported payload plus TPS-TC layer overhead) the VTU can sustain on the line taking the current configuration into account, with margin not lower than Target Noise Margin. This parameter is provided for each activated bearer channel. The calculation estimates the attainable transport Bitrate assuming that all available capacity is allocated to that bearer channel and that current interleaver and Reed-Solomon settings are not changed. The value depends on the actual noise margin on the line. Instances Values Granularity & Unit Update frequency Per bearer channel 0..262143 1 kbps DS: each = 10 seconds via EOC @ VTU-O US: each < 10 seconds @ VTU-O

Table TNG 107-66: Actual transport bitrate (per bearer channel)


Name Description Actual transport Bitrate The actual transport rate (that is, the transported payload plus header bytes) expressed in kbps. Note: The value with respect to the configured Minimum and Maximum bitrate configuration complies with bitrate rounding rules. Instances Values Granularity & Unit Update frequency Per bearer channel 0..262143 1 kbps NA

Table TNG 107-67: Actual interleaving delay (per bearer channel)


Name Description Instances Values Granularity & Unit Update frequency Actual Interleaving Delay Actual delay caused by the interleaving and coding functionality. Per bearer channel 0..63 1 ms NA

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-35

TNG 107 VDSLx parameters

Table TNG 107-68: Actual impulse noise protection (per bearer channel)
Name Description Instances Values Actual Impulse Noise Protection Actual value of the impulse noise protection offered by the interleaving and coding functionality. Per bearer channel 0..16 DMT symbols Note: Care should be taken to the Carrier Spacing (see also Actual tone spacing) Granularity & Unit Update frequency 0.1 DMT symbols NA

Table TNG 107-69: Actual TPS-TC mode


Name Description Instances Values Granularity & Unit Update frequency Current TPS-TC Mode The TPS-TC layer mode used for the current operation of the VDSLx modem subsystem. Per line Same bitmap as TPS-TC mode capabilities. Only 1 bit can be set to 1 at a time. NA

Table TNG 107-70: TPS-TC mode capabilities


Name Description Instances Values TPS-TC Mode Capabilities The total set of TPS-TC modes supported by the VTU-O and the VTU-R respectively. Line Near-end/Far-end Bitmap: TPSTCModesATMBit TPSTCModesPTM_64_65Bit TPSTCModesPTM_HDLCBit Granularity & Unit Update frequency NA

TNG 107-36

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-71: Actual tone spacing


Name Description Instances Values Current Tone Spacing DMT tone spacing currently used by the PMD layer. DS/US Bitmap: SingleToneSpacingBit DoubleToneSpacingBit Granularity & Unit Update frequency NA

Table TNG 107-72: Actual US PBO electrical length


Name Description Actual US Power Back-off electrical length Estimated modem kl0 (electrical length). For VTU-R instance, gives the electrical length estimated by the VTU-R. For VTU-O instance, gives the final values set by the VTU-O (can be identical if VTU-O does not correct it). Instances VTU-R/VTU-O Note: We consider here that electrical length is positive when the loop gain is negative in dB (smaller than one in linear). This is data is only available in VDSL2 operational mode. Values Granularity & Unit 0..127.5 0.1 dB @ 1 MHz

Table TNG 107-73: Actual VTU-R timing advance


Name Description Actual VTU-R Timing Advance Defines the VTU-R timing advance. Positive values indicates that the transmitted symbol will be advanced more with respect to the received symbol. The VTU-R instance represents the initial TA as proposed by the VTU-R, and the VTU-O instance represents the final VTU-R TA value, after VTU-O correction (if any). Instances Line VTU-R and VTU-O This is data is only available in VDSL2 operational mode. Values Granularity & Unit Accuracy -250..+250 10 ns +/- 25 ns

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-37

TNG 107 VDSLx parameters

Table TNG 107-74: Actual highest frequency used


Name Description Actual Highest Frequency used Defines the highest carrier for which the SNR is sufficient, such that the bit loading allocates at least 1 bit. Rounding rule: Value is rounded to the lowest frequency bigger or equal to the highest used carrier. Instances Values Granularity & Unit US/DS 0..30000 1 kHz

Table TNG 107-75: Actual sub-carrier group size


Name Description Actual Sub-Carrier Group Size Defines the sub-carrier spacing used in some carrier related test parameters. In VDSL1 mode, the report value shall always be 1. Instances Values Unit US/DS 1, 2, 4, or 8. Number of carriers

Table TNG 107-76: Actual maximum PSD


Name Description Instances Values Actual Maximum PSD Actual Maximum Transmit power spectrum density over the loaded subcarriers. US/DS -95..0 dBm/Hz A special value Out of Range indicates the parameter is out of range to be represented. Granularity & Unit Accuracy Update frequency 0.1 dBm/Hz 0.1 dBm/Hz DS/US: each bit swap

TNG 107-38

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-77: VDSL2 annex modes capabilities


Name Description VDSL2 Annex modes capabilities VDSL2 Annex capability bitmap. Contain three 32 bits words, one per VDSL2 annex: W0 = a31 a30 a29 ... a2 a1 a0 for VDSL2 annex A W1 = b31 b30 b29 ... b2 b1 b0 for VDSL2 annex B W2 = c31 c30 c29 ... c2 c1 c0 for VDSL2 annex C The MSB (that is, the bit #31) of each word is set if the VTU supports the corresponding annex. Other mode bits are mapped to G.994.1 US0 octets of the corresponding annex, from LSB to MSB: G.994.1 octet #k shall be mapped to bits x(k-1)*6 -> xk*6-1. Instances Values Granularity & Unit VTU-O/VTU-R Three times 32 bits word: [W2, W1, W0], according to parameter description above. -

Table TNG 107-78: VDSL2 actual standard limit PSD


Name Description VDSL2 Actual Standard Limit PSD Returns the actual applicable ITU-T.993.2 ([5]) standard limit PSD mask, including the US0 mode/variant. The returned data are three 32 bits words, and a limit PSD indicator: [W2, W1, W0, M]. The first three words (Mx) identify the actual standard annex and US0 mode/variant, following the format defined in VDSL2 annex modes capabilities. Up to one word has raised bits: the word associated with the actual standard annex. In this word, the MSB (that is, the bit #31) is raised, together with up to one other bit identifying the actual US0 mode. The PSD indicator (M) identifies the actual limit PSD mask, taken from Table TNG 107-79 The unknown answer type is used when the transceiver does not find any match with standard PSDs, or when no direct match is found (that is, short name if PSD is NONE). The other answer type is used when a match is found with the current standard, but the corresponding PSD or Annex is missing from the PSD list. (see Table TNG 107-79). Instances Values Granularity & Unit Line Three times 32 bits word: [W2, W1, W0], according to parameter description above. -

Table TNG 107-79: VDSL2 limit PSD mapping


Annex (1 of 2) PSD Invalid Unknown

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-39

TNG 107 VDSLx parameters

Annex A A A A B B B B B B B B B B B B B B B B B B B B B B B B B B B B C C C C (2 of 2)

PSD Other Annex Unknown in Annex A Other in Annex A PSD mask for operation over POTS PSD mask for all-digital mode operation Unknown in Annex B Other in Annex B 997-M1c-A-7 997-M1x-M-8 997-M1x-M 997-M2x-M-8 997-M2x-A 997-M2x-M HPE17-M1-NUS0 HPE30-M1-NUS0 997E17-M2x-NUS0 997E30-M2x-NUS0 998-M1x-A 998-M1x-B 998-M1x-NUS0 998-M2x-A 998-M2x-M 998-M2x-B 998-M2x-NUS0 998E17-M2x-NUS0 998E17-M2x-NUS0-M 998ADE17-M2x-NUS0-M 998ADE17-M2x-A 998ADE17-M2x-B 998E30-M2x-NUS0 998E30-M2x-NUS0-M 998ADE30-M2x-NUS0-M 998ADE30-M2x-NUS0-A Unknown in Annex C Other in Annex C PSD mask for operation above POTS PSD mask for operation above TCMISDN

TNG 107-40

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Table TNG 107-80: Actual DS virtual noise SNRM_MODE


Name Description Actual DS Virtual Noise SNRM_MODE VDSL2 only This operational data is matched with DS configuration parameter Virtual Noise SNRM_MODE when the VTU-R support virtual noise. Otherwise, it shall be SNRM_MODE1. Instances Values Granularity & Unit DS SNRM_MODE1, SNRM_MODE2 -

Table TNG 107-81: Actual use of Trellis Coding


Name Description Instances Values Actual Use of Trellis Coding Indicates the actual use of Trellis coding. DS/US 0: Not used 1: Used Granularity & Unit Boolean.

Table TNG 107-82: Actual used cyclic extension


Name Description Instances Values Granularity & Unit Actual Used Cyclic Extension Indicates the actual cyclic extension used on the line (in showtime). Line 2, 3, 4, 5, , 16. Unit of N/32 samples, where 2*N is the IFFT size.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-41

TNG 107 VDSLx parameters

Table TNG 107-83: Actual framing parameters


Name Description Actual Framing Parameters Indicates the following actual used framing parameters, per bearer. and linked to the latency path that carries that bearer:


Instances Values

Nfec: actual size of Reed Solomon codeword Rfec: actual number of Reed Solomon redundancy bytes Lsymb: actual number of bits per symbol assigned to the latency path transporting the bearer (excluded Trellis overhead) Dintlv: actual interleaving depth Iintlv: actual interleaving block length

Per bearer channel Nfec: bytes, ranging from 0 to 255. The value 0 indicates no Reed Solomon coding. Rfec: bytes, ranging from 0 to 16. The value 0 indicates no Reed Solomon coding. Lsymb: bits (per symbol), ranging from 0 to 65536. Dintlv: ranges from 1 to 4096. The value 1 indicates no interleaving. Iintlv: ranges from 4 to 255, plus the 1 value that indicates no interleaving.

Granularity & Unit

See Values.

TNG 107-42

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 107 VDSLx parameters

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 107-43

TNG 107 VDSLx parameters

TNG 107-44

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters


Introduction
This training document gives more information about the parameters used by the SHDSL modem:

Re-initialization triggers Supported span operation configuration parameters Supported unit operation configuration parameters Supported segment termination operation configuration parameters Supported span operational data parameters Supported unit operational data parameters Supported segment termination operational data parameters

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-1

TNG 108 SHDSL parameters

Re-initialization triggers
During showtime (L0 line state), the SHDSL Modem Subsystem performs persistency/severity checking and correlation on the defects/anomalies, in order to detect re-initialization triggers. Table TNG 108-1 lists them for the SHDSL Transceiver Unit at the Central office side (STU-C) and includes the required persistency time for each showtime error.
Table TNG 108-1: Re-initialization triggers
Related Defect/Anomaly Needed persistency to trigger re-start Near-End (f)los sef/rdi (f)lom (f)se (f)ncd (f)lcd (f)npd/(f)lpd 5 1 sec 5 1 sec 60 1 sec 10 1 sec 15 1 sec 15 1 sec 15 1 sec Far-End 6 1 sec 6 1 sec 60 1 sec 10 1 sec 17 1 sec 17 1 sec 15 1 sec

The SHDSL Modem Subsystem triggers/initiates re-activation of the modem when any of those triggers is fired. No other re-initialization triggers (annex timer values) are used by the Modem Subsystem than the ones mentioned in Table TNG 108-1. All far-end count-down timers are frozen when any near-end defect occurs. When all near-end defects have disappeared, far-end count-down timers resume from frozen values (ignoring the in-between time). All near-end defects are correlated independent from each other. The same holds for all far-end defects in absence of near-end defects.

TNG 108-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Supported span operation configuration parameters


The SHDSL Modem Subsystem accepts the configuration parameters listed hereunder. Based on the required levels, the required modem reaction on each parameter is:

In case a parameter is indicated as optional, the input value is dont care, and any value is accepted without having impact on the modem subsystem behavior. In case a parameter is indicated to be required to a certain level (for example, only limited set of defined number of input values), only input values corresponding to the required level are accepted. If the input parameter is not accepted, the modem subsystem raises a failure indication to the xDSL Manager indicating Configuration Error In case extra consistency checks need to be performed on a parameter or between parameters and the configuration should be rejected, 'rejection' always means that the modem subsystem raises a failure indication to the SHDSL Manager indicating Configuration Error, rather that a returned error of the considered SHDSL API call. An SHDSL API configuration request is replied with an error only when the call is done in a wrong administrative state.

The SHDSLx Modem Subsystem allows that the configuration can be independently set on individual line basis. M-pair (1 < M < 4) stands for a multiple-pair operation over SHDSL span for some applications having higher data rate requirements for end users.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-3

TNG 108 SHDSL parameters

Four-wire mode is identical to M-pair mode with M = 2, except for the method of assigning ordinal numbers to the wire pairs.

Data Rates: M-pair operational mode is capable of supporting user (payload) data rates from M *192 kbit/s to M *2.312 Mbit/s in increments of M * 8 kbit/s, where 1 < M < 4. Note that optional extensions described in Annex F/G allow user data rates up to M *5696 kbit/s. Four-wire mode is identical to M-pair mode with M = 2, except for the method of assigning ordinal numbers to the wire pairs. Embedded Operations Channel (EOC): For optional M-pair operation, each EOC message is sent in parallel such that redundant and identical messages are sent over all M loops. In M-pair mode, eoc01 - eoc20 on Pair 1 carries the primary EOC data. The corresponding Pair 2 to Pair M eoc bits are duplicates of the Pair 1 eoc bits. SHDSL Transceiver Unit at the Remote side (STU-R) Power Status: In M-pair mode, ps on Pair 1 carries the primary power status indication. The ps bit on all other pairs are duplicates of the Pair 1 ps bit. Power Feeding/Wetting Current: In the optional M-pair mode, the requirements for remote power feeding or wetting current for each of the M pairs are identical to the requirements for a single pair. Activation Procedure: In devices supporting the optional M-pair mode, the core activation procedure is considered as an independent procedure for each pair. Such devices are capable of detecting the completion of activation for all pairs and upon completion will initiate the transmission of user data over all pairs. Line Probe: In the optional M-pair mode, STU-R remote probe signal Pri and STU-C central probe signal Pci are sent in parallel on all wire pairs. G.994.1: In the optional 4-wire mode, Pair 1 and Pair 2 are determined during the preactivation sequence procedures defined in Annex B/G.994.1 entitled, Operation over multiple wire pairs. Pair 1 is defined as the pair on which the final G.994.1 transaction is conducted. In the optional M-pair mode, the G.994.1 exchange follows the defined procedures for multi pair operation.

TNG 108-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Operating Modes
Table TNG 108-1 describes the operating modes parameter.
Table TNG 108-2: Operating Modes
Name Description Operating Modes Specifies which operational protocol/standard are applicable for a span:

(1) ATM-Native (2) ATM-IMA (ATM Forum) (3) PTM-64/65B (4) PTM-HDLC

The standards that need to be supported for the current projects are listed in SHDSL_R24. Operational modes not supported by the STU-C shall be ignored (that is, they are not considered selected). Multiple mode selection is not allowed. The operational mode is selected by the SHDSL Manager before startup the line, each lines operational mode are independent to the other lines, with exception of M-pair mode which requires all lines belong to a M-pair configuration in the same operational mode. Operational modes are not exchanged by G.hs. The modem rejects the configuration and raises the Configuration error activation failure in the following scenarios:

No mode is selected (or no STU-C supported mode is selected)

In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the same value, which would be the same for all links in the IMA group. For this reason, the IMA mode selection and Group assignment needs to be made at the same time as the initial provisioning. IMA is not supported over M-pair links. Instances Values Span shdsl_native_mode shdsl_ima_mode shdsl_efm_mode Granularity & Unit -

Number of Repeaters
Table TNG 108-2 describes the number of repeaters parameter.
Table TNG 108-3: Number of Repeaters
Name Description Instances (1 of 2) Number of Repeaters Configures the number of SRU (repeater) units to be configured for this SHDSL span. It controls the number of SRU (repeater) entries in the unit configuration. Span

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-5

TNG 108 SHDSL parameters

Values Granularity & Unit (2 of 2)

0-8 1

Spectral Profile
Table TNG 108-3 describes the spectral profile parameter.
Table TNG 108-4: Spectral Profile
Name Description SHDSL Spectral Profile Specifies the spectral mode in which this SHDSL span is to be configured with. Two options are supported:

AsymmetricProfile SymmetricProfile

In case of AsymmetricProfile the valid data rates are restricted as follows: Region 1/Annex A/M-pair: M * 768 kb/s & M * 1536 kb/s Region 2/Annex B/M-pair: M * 2048 kb/s & M * 2304 kb/s

Examples: Annex A/2-Wire: 768 kb/s & 1536 kb/s Annex A/4-Wire: 1536 kb/s & 3072 kb/s Annex B/2-Wire: 2048 kb/s & 2304 kb/s Annex B/4-Wire: 4096 kb/s & 4608 kb/s Instances Values Span symmetricProfile asymmetricProfile Granularity & Unit -

Wire Mode
Table TNG 108-4 describes the wire mode parameter.
Table TNG 108-5: Wire Mode
Name Description Wire Mode Specifies whether 2-Wire or 4-Wire or 6-Wire or 8-Wire operation is in place. The supported wire mode depend on the actual lines of modem ASIC. IMA is not supported over M-pair links. The modem rejects the configuration and raise the Configuration error activation failure in the following scenarios:


Instances (1 of 2)

No wire mode is selected (or no STU-C supported mode is selected) IMA operational mode is selected for multi-wire operation

Span

TNG 108-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Values

shdsl_two_wire shdsl_four_wire shdsl_six_wire shdsl_eight_wire

Granularity & Unit (2 of 2)

Support Management from STU-R


Table TNG 108-5 describes the support management from STU-R parameter.
Table TNG 108-6: Support Management from STU-R
Name Description Instances Values Managed from STU-R Specifies whether the STU-R initiated management flow is enabled/disabled by the STU-C. Span disabled enabled Granularity & Unit -

Regional Setting
Table TNG 108-6 describes the regional setting parameter.
Table TNG 108-7: Regional Setting
Name Description Regional Setting Specifies the regional setting for the SHDSL line per the ITU-T G.992.1 Annexes (Annex A/F and Annex B/G).

Region 1 - G.991.2 Annex A/F Region 2 - G.991.2 Annex B/G

Only a single setting (region 1 or region 2) can be provisioned. In Asymmetric Spectral Profile Mode, the regional setting cannot be modified. The modem rejects the configuration and raises the Configuration error activation failure in the following scenarios:


Instances Values

No region is selected (or no STU-C supported region is selected) Region 1 and region 2 are selected together

Span BitMap: Bit --0 1 Setting --------Region 1 Region 2

Granularity & Unit

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-7

TNG 108 SHDSL parameters

Minimum and Maximum Data Rate


Table TNG 108-8 and Table TNG 108-9 describe the minimum and maximum requested data rate parameters.
Table TNG 108-8: Minimum Requested Data Rate
Name Description Minimum Requested Data Rate Defines the minimum requested transport payload bitrate which shall be set up and which shall be maintained during showtime by the STU. When line probe is enabled, the SHDSL line is probed for levels between this rate and the maximum requested data rate. The Line will not be activated at a lower rate. Only ATM/EFM Mapping is supported, this limits the resulting data rates to multiples of 64k (192 to 5696) in TwoWire mode; and to multiples of 128k (384 to 11,392) in FourWire mode, to multiples of 192k (576 to 17,088) in SixWire mode, to multiples of 256k (768 to 22,784) in EightWire mode. In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the same value which would be the same for all links in the IMA group. This result in a constraint to use exact 64 kb/s multiples in provisioning. Instances Values Span 2-wire: 192 to 5696 in multiple of 64, and 2312 4-wire: 384 to 11,392 in multiple of 128 6-wire: 576 to 17,088 in multiple of 192 8-wire: 768 to 22,784 in multiple of 384 Granularity & Unit 64 kbit/s * M (pair number)

TNG 108-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Table TNG 108-9: Maximum Bitrate


Name Description Maximum Bitrate Specifies the maximum requested SHDSL data rate which can range from 192 to 5696 kb/s in Two Wire mode, plus the rate of 2312; and from 384 to 11.392 kb/s in FourWire mode; from 576 to 17,088 kb/s in SixWire mode; from 768 to 22.784 kb/s in EightWire mode The SHDSL line is probed for levels between this rate and the minimum requested data rate. The Line will not be activated at a higher rate. Only the ATM/EFM Mapping is supported, this limits the resulting data rates to multiples of 64k (192 to 5696) in TwoWire mode; and to multiples of 128k (384 to 11.392) in FourWire mode, to multiples of 192k (576 to 17.088) in SixWire mode, to multiples of 256k (768 to 22.784) in EightWire mode. In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the same value which would be the same for all links in the IMA group. This result in a constraint to use exact 64 kb/s multiples in provisioning. This parameter is relevant only in line probe enabled mode. When line probe is not enabled, the Maximum Bitrate parameter is ignored. As the data rate granularity is in multiple of 64 kbps, the following rounding scheme for Minimum and Maximum Bitrates is implemented:

The Minimum Bitrate is rounded up and the Maximum Bitrate is rounded down according to the data rate granularity when for the corresponding direction Maximum Bitrate Minimum Bitrate after rounding. Otherwise, both bitrates are rounded up and Minimum Bitrate = Maximum Bitrate after rounding up.

The SHDSL modem subsystem raises failure indication Configuration Error for configurations where Maximum Bitrate < Minimum Bitrate for one of the directions when line probe is enabled. Instances Values Span 2-wire: 192 to 5696 in multiple of 64, and 2312 4-wire: 384 to 11.392 in multiple of 128 6-wire: 576 to 17.088 in multiple of 192 8-wire: 768 to 22.784 in multiple of 384 Granularity & Unit 64 kbit/s * M (pair number)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-9

TNG 108 SHDSL parameters

Worst Case Downstream Target Noise Margin


Table TNG 108-10 describes the worst case downstream target noise margin parameter.
Table TNG 108-10: Worst Case Downstream Target Noise Margin
Name Description Worst Case Downstream Target Noise Margin Specifies the Target Margin in the Downstream direction, relative to the reference Worst Case, to be used during handshake and line-probe procedure in gauging a Bit Error Rate (BER) better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated Signal-to-Noise Ratio (SNR) associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction. Instances Values Granularity & Unit Span -11to 10 1 dB

TNG 108-10

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Current Case Downstream Target Noise Margin


Table TNG 108-11 describes the current case downstream target noise margin parameter.
Table TNG 108-11: Current Case Downstream Target Noise Margin
Name Description Current Case Downstream Target Noise Margin Specifies the Target Margin in the Downstream direction, relative to the Current noise conditions, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction. Instances Values Granularity & Unit Span -11to 10 1 dB

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-11

TNG 108 SHDSL parameters

Worst Case Upstream Target Noise Margin


Table TNG 108-12 describes the worst case upstream target noise margin parameter.
Table TNG 108-12: Worst Case Upstream Target Noise Margin
Name Description Worst Case Upstream Target Noise Margin Specifies the Target Margin in the Upstream direction, relative to the reference Worst Case, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction. Instances Values Granularity & Unit Span -11to 10 1 dB

TNG 108-12

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Current Case Upstream Target Noise Margin


Table TNG 108-13 describes the current case upstream target noise margin parameter.
Table TNG 108-13: Current Case Upstream Target Noise Margin
Name Description Current Case Upstream Target Noise Margin Specifies the Target Margin in the Upstream direction, relative to the Current noise conditions, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction. Instances Values Granularity & Unit Span -11to 10 1 dB

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-13

TNG 108 SHDSL parameters

Line Probe Enable


Table TNG 108-14 describes the line probe enable parameter.
Table TNG 108-14: Line Probe Enable
Name Description Line Probe Enable Specifies support for Line Probe (rate adaptation) of the units in a SHDSL line. When Line Probe is enabled, the system performs Line Probing to find the best possible rate. If Line probe is disabled, the rate adaptation phase is skipped to shorten set up time. Span disabled enabled Granularity & Unit

Instances Values

TNG 108-14

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Supported unit operation configuration parameters

Loop Attenuation Threshold


Table TNG 108-15 describes the loop attenuation threshold parameter.
Table TNG 108-15: Loop Attenuation Threshold
Name Description Loop Attenuation Threshold Specifies the Loop Attenuation Threshold Value in dBs, for generated associated alarms. A value of 0 disables alarm generation. Instances Values Granularity & Unit Unit 0-127 1 dB

SNR Margin Threshold


Table TNG 108-16 describes the SNR margin threshold parameter.
Table TNG 108-16: SNR Margin Threshold
Name Description SNR Margin Threshold Specifies the SNR Margin Threshold Value in dBs, for generated associated alarms. A value of 0 disables alarm generation. Instances Values Granularity & Unit Unit 0-15 1 dB

Loopback Timeout
Table TNG 108-17 describes the loopback timeout parameter.
Table TNG 108-17: Loopback Timeout
Name Description Loopback Timeout Specifies the Loopback Timeout duration in minutes. A value of 0 disables timeout. Instances (1 of 2) Unit

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-15

TNG 108 SHDSL parameters

Values Granularity & Unit (2 of 2)

0-4095 1minute

Supported segment termination operation configuration parameters

Loopback Configuration
Table TNG 108-18 describes the loopback configuration parameter.
Table TNG 108-18: Loopback Configuration
Name Description Loopback Config Specifies the loopbacks for the associated side of an SHDSL unit. Only Network Side loopbacks are supported for SRU and STU-R units Instances Values Segment Termination NoLoopback NormalLoopback Granularity & Unit -

Power Backoff Mode


Table TNG 108-19 describes the power backoff mode parameter.
Table TNG 108-19: Power Backoff Mode
Name Description Instances Values Power Backoff Mode Specifies the Power Backoff rule at the associated Segment Termination. Segment Termination Default Selected Granularity & Unit -

TNG 108-16

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Soft Restart
Table TNG 108-20 describes the soft restart parameter.
Table TNG 108-20: Soft Restart
Name Description Soft Restart Initiate a Soft Restart message towards the relevant segment termination. When the value of this object is set from 0 to 1, a Soft Restart EOC message is initiated. After 5 minutes the value of the object is automatically set back to 0. Instances Values Segment Termination 0 (Normal Operation) 1 (Soft Restart) Granularity & Unit -

Supported span operational data parameters


The Initialisation value is the parameter value when entering the active/data/showtime (Operational Up) state. Consequently, the value has to be derived during initialisation. The Showtime value is the (current if updated) parameter value during the active/data state. The Update frequency is the update frequency of the parameter during active/data/showtime (Operational Up) state. The SHDSL Modem Subsystem assures that the Showtime values (if applicable for the considered parameter) are available for retrieval over the SHDSL API within 10 seconds after entering the Operational Up state. During the first 10 seconds of the Operational Up state, the SHDSL Modem Subsystem returns the Initialisation values (if applicable for the considered parameter) if the Showtime value for the considered parameter is not available yet.

Span State
Table TNG 108-21 describes the span state parameter.
Table TNG 108-21: Span State
Name Description Instances Values Span State Indicates the overall state of this SHDSL span Span unknown unequipped faulty idle startup active Granularity & Unit (1 of 2) -

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-17

TNG 108 SHDSL parameters

Initialization value Showtime value: Update frequency (2 of 2)

Idle Active NA

TNG 108-18

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Detected Units
Table TNG 108-22 describes the detected units parameter.
Table TNG 108-22: Detected Units
Name Description Instances Values Detected Units Indicates the units that have been detected on this SHDSL span, bits are set(1) for detected units. Span Bitmap: Bit --0 1 2 3 4 5 6 7 8 9 Granularity & Unit Initialization value Showtime value: Update frequency NA Derived from EOC NA Unit -----STU-C STU-R SRU-1 SRU-2 SRU-3 SRU-4 SRU-5 SRU-6 SRU-7 SRU-8

Configured Units
Table TNG 108-23 describes the configured units parameter.
Table TNG 108-23: Configured Units
Name Description Instances Values Configured Units Indicates the units in the SHDSL span which have been successfully configured, bits are set (1) for units which have been successfully configured. Span Bitmap: Bit --0 1 Granularity & Unit Initialization value (1 of 2) NA Unit -----STU-C STU-R

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-19

TNG 108 SHDSL parameters

Showtime value: Update frequency (2 of 2)

Derived from EOC NA

Span Status
Table TNG 108-24 describes the span status parameter.
Table TNG 108-24: Span Status
Name Description Span Status Indicates the overall status of this SHDSL span. Status conditions are associated with individual SHDSL segments. This object represents collective span status by logically-OR-ing individual segment status bits. Instances Values Span Bitmap: Bit --0 1 2 3 4 5 6 7 8 9 10 11 Granularity & Unit Initialization value Showtime value: Update frequency NA Derived from EOC NA Condition --------No Error LOSW Loop Attenuation Alarm SNR Margin Alarm DC Continuity Fault Device Fault Configuration Error Loopback(s) Active Non-Conform to STU-C Enable/Disable of STU-R Initiated Management Flow ATM LCD/PTM LPD Loss of Power ATM NCD/PTM NPD

TNG 108-20

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Wire Pair Assignment


Table TNG 108-25 describes the wire pair assignment parameter.
Table TNG 108-25: Wire Pair Assignment
Name Description Wire Pair Assignment Provides the correlation between the actual ports and their dynamic designation as fistPair and secondPair and thirdPair and fourthPair (if M>2 is supported) as a result of the pre-activation sequence in a modem ASIC. (firstPair is defined as the pair on which the final G.994.1 transaction is conducted) For 4-wire mode:


Instances Values

00000100b: if the first port is the first pair, second port is the second pair 00000001b: if the second port is the first pair

6-wire mode examples: 00100100b: if the first port is the first pair, second port is the second pair, third port is the third pair 00010010b: if the second port is the first pair, third port is the second pair 00001001b: if the third port is the first pair, first port is the second pair

8-wire mode examples: 11100100b: if the first port is the first pair, second port is the second pair, third port is the third pair, fourth port is the fourth pair 10010011b: if the second port is the first pair 01001110b: if the third port is the first pair 00111001b: if the fourth port is the first pair

Span Bitmap: Bit --Condition ---------

1,0 wirePair of the 1st modem ASIC port for 6/8-wire, 1st/3rd numbered port for 4-wire 3,2 wirePair of the 2nd modem ASIC port for 6/8-wire, 2nd/4th numbered port for 4-wire 5,4 7,6 wirePair of the 3rd modem ASIC port for 6/8-wire, set to 0 for 4-wire wirePair of the 4th modem ASIC port for 8-wire, set to 0 for 4/6-wire value -------00 01 10 11

wirePair ---------1stPair 2ndPair 3rdPair 4thPair Granularity & Unit Initialization value Showtime value: Update frequency NA

Derived from EOC NA

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-21

TNG 108 SHDSL parameters

Supported unit operational data parameters


The Initialisation value is the parameter value when entering the active/data/showtime (Operational Up) state. Consequently, the value has to be derived during initialisation. The Showtime value is the (current if updated) parameter value during the active/data state. The Update frequency is the update frequency of the parameter during active/data/showtime (Operational Up) state. The SHDSL Modem Subsystem assures that the Showtime values (if applicable for the considered parameter) are available for retrieval over the SHDSL API within 10 seconds after entering the Operational Up state. During the first 10 seconds of the Operational Up state, the SHDSL Modem Subsystem returns the Initialisation values (if applicable for the considered parameter) if the Showtime value for the considered parameter is not available yet. Unit Operational Data only exist for those units that are configured as indicated by the shdslSpanConfiguredUnits, and which support SHDSL EOC Performance Status messages defined in ITU-T G.991.2[1].

Unit DC Powering
Table TNG 108-26 describes the unit DC powering parameter.
Table TNG 108-26: Unit DC Powering
Name Description Instances Values Unit DC Powering Indicates whether this unit is powered locally, or derives power from the SHDSL span. Unit LocalPowered spanPowered Granularity & Unit Initialization value Showtime value: Update frequency NA Derived from EOC NA

TNG 108-22

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Supported segment termination operational data parameters


The Initialisation value is the parameter value when entering the active/data/showtime (Operational Up) state. Consequently, the value has to be derived during initialisation. The Showtime value is the (current if updated) parameter value during the active/data state. The Update frequency is the update frequency of the parameter during active/data/showtime (Operational Up) state. The SHDSL Modem Subsystem assures that the Showtime values (if applicable for the considered parameter) are available for retrieval over the SHDSL API within 10 seconds after entering the Operational Up state. During the first 10 seconds of the Operational Up state, the SHDSL Modem Subsystem shall return the Initialisation values (if applicable for the considered parameter) if the Showtime value for the considered parameter is not available yet. Segment Termination Operational Data only exist for those units that are configured as indicated by the shdslSpanConfiguredUnits, and which support SHDSL EOC Performance Status messages defined in ITU-T G.991.2[1].

Segment Termination Status


Table TNG 108-27 describes the segment termination status parameter.
Table TNG 108-27: Segment Termination Status
Name Description Instances Values Segment Termination Status Indicates any exception conditions active at this SHDSL segment termination Segment Termination Bitmap: Bit --0 1 2 3 4 5 6 7 8 9 10 11 Granularity & Unit Initialization value Showtime value: Update frequency NA Derived from EOC NA Condition --------No Error LOSW Loop Attenuation Alarm SNR Margin Alarm DC Continuity Fault Device Fault Configuration Error Loopback(s) Active Non-Conform to STU-C Enable/Disable of STU-R Initiated Management Flow ATM LCD/PTM LPD Loss of Power ATM NCD/PTM NPD

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-23

TNG 108 SHDSL parameters

Loopback State
Table TNG 108-28 describes the loopback state parameter.
Table TNG 108-28: Loopback State
Name Description Loopback State Indicates any loopback active at this SHDSL segment termination. In M-pair mode, the loopbacks can only be set-up and torn-down simultaneously on all pairs. Instances Values Segment Termination noLoopback normalLoopback specialLoopback Granularity & Unit Initialization value Showtime value: Update frequency noloopback Derived from EOC NA

SNR Margin
Table TNG 108-29 describes the SNR margin parameter.
Table TNG 108-29: SNR Margin
Name Description SNR Margin Indicates the currently measured SNR Margin in dB at this SHDSL segment termination. A value of 127 indicates that this information is unavailable. Instances Values Granularity & Unit Accuracy Initialization value Segment Termination -128 to 127 dB 1 dB 1 dB DS: passed via initialization messages US: locally at the STU-C Showtime value: DS: passed via EOC Remark: In case no EOC, the initialization value for the DS SNR Margin shall be returned. US: local at the STU-C Update frequency DS: each = 10 seconds via EOC @ STU-C US: each < 10 seconds @ STU-C

TNG 108-24

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 108 SHDSL parameters

Loop Attenuation
Table TNG 108-30 describes the loop attenuation parameter.
Table TNG 108-30: Loop Attenuation
Name Description Loop Attenuation Indicates the currently measured Loop Attenuation in dB at this SHDSL segment termination. A value of -128 indicates that this information is unavailable. Instances Values Granularity & Unit Accuracy Initialization value Segment Termination -128 to 127 dB 1 dB 1 dB US: Measured during initialization. DS: Not Available Showtime value: Update frequency NA NA

Power Backoff Level


Table TNG 108-31 describes the power backoff level parameter.
Table TNG 108-31: Power Backoff Level
Name Description Instances Values Granularity & Unit Accuracy Initialization value Power Backoff Level Indicates the current Power Backoff value in dB at this SHDSL segment termination. Segment Termination 0 to 31 dB 1 dB 1 dB US: Measured during initialization. DS: Not Available Showtime value: Update frequency NA NA

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 108-25

TNG 108 SHDSL parameters

Tip Ring Reversal


Table TNG 108-32 describes the tip ring reversal parameter.
Table TNG 108-32: Tip Ring Reversal
Name Description Instances Values Tip Ring Reversal Indicates the current state of the Tip/Ring pair at this SHDSL segment termination. Segment Termination normal reversed Granularity & Unit Accuracy Initialization value US: Measured during initialization. DS: Not Available Showtime value: Update frequency NA NA

Power Backoff Status


Table TNG 108-33 describes the power backoff status parameter.
Table TNG 108-33: Power Backoff Status
Name Description Power Backoff Status Indicates the Power Backoff status at this SHDSL segment termination. This value indicates the mode that will be selected at the next reset. Instances Values Segment Termination default selected Granularity & Unit Accuracy Initialization value US: Measured during initialization. DS: Not Available Showtime value: Update frequency NA NA

TNG 108-26

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters


Introduction
This TNG document describes the performance management counters for:

xDSL ARP DHCP

xDSL Counters
The XDSL performance monitoring functions are defined in ITU.T Rec. G.997.1 7.2. The inhibiting rules for the accumulation of performance parameters comply with G.997.1, 7.2.7.13. For the derived counters (Errored Second (ES), Severely Errored Second (SES), Unavailable Second (UAS)), the following rules apply:

During periods of unavailable time (UAS), the accumulation of the ES and SES counter will be inhibited. SES will not inhibit the accumulation of the ES counter, i.e. during periods of SES both the ES and SES counter will be incremented. In case the modem is not in showtime, but is allowed to activate the line (port is in admin-state up), all seconds are classified as NE/FE SES (resulting in NE/FE UAS) and measured-time is still incremented. In case the modem is not allowed to activate the line (port is in admin-state down), all PM counters are frozen and measured-time is not updated anymore

Near-end Line Performance Monitoring parameters


Table TNG 109-1 lists the related CLI commands for near-end line performance monitoring.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 109-1

TNG 109 Performance management counters

Table TNG 109-1: Near-end line: related CLI commands


Command show xdsl counters near-end line current-interval [ (if-index) ] show xdsl counters near-end line current-1day [ (if-index) ] show xdsl counters near-end line previous-interval [ (if-index) [ interval-no <Xdsl::IntervalNumber15min> ] ] show xdsl counters near-end line previous-1day [ (if-index) [ interval-no <Xdsl::IntervalNumber1day> ] ] Description Displays xDSL counters of the near end line for the current 15 min interval Displays the xDSL counters of the near end line for the current day interval Displays the xDSL counters of the near end line for a previous 15 min interval Displays the xDSL counters of the near end line for a previous day interval

Table TNG 109-2 lists the performance management counters for near-end line
Table TNG 109-2: PM counters for near-end line
Parameter Name es ses uas los lof lom ese re-init Description Errored Second count (ES) for upstream as per G.997.1 7.2.1.1.2 Severely Errored Second count (SES) for upstream as per G.997.1 7.2.1.1.3 Unavailable Second count (UAS) for upstream as per G.997.1 7.2.1.1.5 Loss Of Signal failure count (LOS) for upstream, counts the number of los failures as per DSL standard Loss Of Frame failure count (LOF) for upstream, counts the number of lof failures as per DSL standard Loss Of Margin failure count (LOM) for upstream, counts the number of lom failures as per DSL standard Excessive Severe Error failure count (ESE) for upstream, counts the number of ese failures. An ese failure is raised after 10 contiguous SES. Re-init count: counts the number of spontaneous initialisations. The counter is incremented each time the modem leaves showtime due to the detection of a persistent defect. A timer is used to exclude shut down of the CPE by the subscriber. failed-init ra-upshift ra-downshift Failed-init count, as per G.997.1 7.2.1.3.2 Rate Adaptation Upshift (RAU) for upstream, counts the number of rau anomalies as per DSL standard Rate Adaptation Downshift (RAD) for upstream, counts the number of rad anomalies as per DSL standard

Far-end Line Performance Monitoring parameters


Table TNG 109-3 lists the related CLI commands for far-end line performance monitoring.

TNG 109-2

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters

Table TNG 109-3: Far-end line: related CLI commands


Command show xdsl counters far-end line current-interval [ (if-index) ] show xdsl counters far-end line current-1day [ (if-index) ] show xdsl counters far-end line previous-interval [ (if-index) [ interval-no <Xdsl::IntervalNumber15min> ] ] show xdsl counters far-end line previous-1day [ (if-index) [ interval-no <Xdsl::IntervalNumber1day> ] ] Description Displays xDSL counters of the far end line for the current 15 min interval Displays the xDSL counters of the far end line for the current day interval Displays the xDSL counters of the far end line for a previous 15 min interval Displays the xDSL counters of the far end line for a previous day interval

Table TNG 109-4 lists the performance management counters for far-end line
Table TNG 109-4: PM counters for far-end line
Parameter Name es ses uas los lof lpr lol Description Errored Second count (ES) for upstream as per G.997.1 7.2.1.1.2 Severely Errored Second count (SES) for upstream as per G.997.1 7.2.1.1.3 Unavailable Second count (UAS) for upstream as per G.997.1 7.2.1.1.5 Loss Of Signal failure count (LOS) for upstream, counts the number of los failures as per DSL standard Loss Of Frame failure count (LOF) for upstream, counts the number of lof failures as per DSL standard Loss Of Power failure count (LPR), counts the number of far-end lpr failures as per DSL standard Loss Of Link failure count (LOL), counts the number of far-end lol failures Note: this counter is not incremented (LOL alarm never raised) lom ese ra-upshift ra-downshift Loss Of Margin failure count (LOM) for upstream, counts the number of lom failures as per DSL standard Excessive Severe Error failure count (ESE) for upstream, counts the number of ese failures. An ese failure is raised after 10 contiguous SES. Rate Adaptation Upshift (RAU) for upstream, counts the number of rau anomalies as per DSL standard Rate Adaptation Downshift (RAD) for upstream, counts the number of rad anomalies as per DSL standard

Near-end Channel Performance Monitoring parameters


Table TNG 109-5 lists the related CLI commands for near-end channel performance monitoring.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 109-3

TNG 109 Performance management counters

Table TNG 109-5: Near-end channel: related CLI commands


Command show xdsl counters near-end channel current-interval [ (if-index) ] show xdsl counters near-end channel current-1day [ (if-index) ] show xdsl counters near-end channel previous-interval [ (if-index) [ interval-no <Xdsl::IntervalNumber15min> ] ] show xdsl counters near-end channel previous-1day [ (if-index) [ interval-no <Xdsl::IntervalNumber1day> ] ] Description Displays xDSL counters of the near end channel for the current 15 min interval Displays the xDSL counters of the near end channel for the current day interval Displays the xDSL counters of the near end channel for a previous 15 min interval Displays the xDSL counters of the near end channel for a previous day interval

Table TNG 109-6 lists the performance management counters for near-end channel
Table TNG 109-6: PM counters for near-end channel
Parameter Name cv fecc cec Description Count of upstream Code Violations, i.e. incorrect CRC (CRC-8 anomalies) as per G.997.1 7.2.2.1.1 Count of upstream Forward Error Corrections, i.e. the number of corrected RS codewords (fec anomalies) as per G.997.1 7.2.2.1.2 Count for Codeword Error Count (CEC) for upstream (VDSL2 only), counts the number of non-corrected errored RS codewords occurring in the bearer channel during the accumulation period

Far-end Channel Performance Monitoring parameters


Table TNG 109-7 lists the related CLI commands for far-end channel performance monitoring.
Table TNG 109-7: Far-end channel: related CLI commands
Command show xdsl counters far-end channel current-interval [ (if-index) ] show xdsl counters far-end channel current-1day [ (if-index) ] show xdsl counters far-end channel previous-interval [ (if-index) [ interval-no <Xdsl::IntervalNumber15min> ] ] show xdsl counters far-end channel previous-1day [ (if-index) [ interval-no <Xdsl::IntervalNumber1day> ] ] Description Displays xDSL counters of the far end channel for the current 15 min interval Displays the xDSL counters of the far end channel for the current day interval Displays the xDSL counters of the far end channel for a previous 15 min interval Displays the xDSL counters of the far end channel for a previous day interval

Table TNG 109-8 lists the performance management counters for far-end channel

TNG 109-4

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters

Table TNG 109-8: PM counters for far-end channel


Parameter Name cv fecc cec Description Count of downstream Code Violations, i.e. incorrect CRC (CRC-8 anomalies) as per G.997.1 7.2.2.1.1 Count of downstream Forward Error Corrections, i.e. the number of corrected RS codewords (fec anomalies) as per G.997.1 7.2.2.1.2 Count for Codeword Error Count (CEC) for downstream (VDSL2 only), counts the number of non-corrected errored RS codewords occurring in the bearer channel during the accumulation period Note: not available from far-end

IP SHub ARP Counters


The supported counters include both error counters and statistics counters. The statistics counters are defined both at node level and at each VRF level. The show commands display both the global counters and the VRF counters.
Table TNG 109-9: Related CLI commands
Command admin ip shub arp-stats (vrf-id) (clear-statistics) Description Allows the operator to clear the VRF counters at any point in time.

Table TNG 109-10 gives more information on the different individual counters.
Table TNG 109-10: Individual counters
Command Node level counters in-packets discard in-request in-resp out-request out-resp VRF level counters arp-discards rx-arp-packets Number of ARP packets that have been discarded because error checks have failed. Total number of ARP packets received on this vrf. Includes packets that may have been discarded. Total number of ARP packets received on all interfaces. Includes packets that may have been discarded. Number of ARP packets that have been discarded because error checks have failed. Number of incoming ARP requests that have been processed. Number of incoming ARP responses that have been processed. Number of ARP requests that have been transmitted out. Number of ARP responses that have been transmitted out. Description

(1 of 2)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 109-5

TNG 109 Performance management counters

Command rx-arp-req rx-arp-rsp tx-arp-req tx-arp-rsp invalid-op-code unsupported-hw-type unsupported-l3-proto unsupported-addr-len

Description Number of incoming ARP requests that have been processed. Number of incoming ARP responses that have been processed. Number of ARP requests that have been transmitted out. Number of ARP responses that have been transmitted out. Number of ARP packets discarded because the specified opcode is invalid. Number of ARP packets discarded because the received ARP packet header specifies a HW type other than Ethernet. Number of ARP packets discarded because the received ARP packet specifies a L3 protocol type other than IP. Number of ARP packets discarded because the address lengths specified in the packet are not supported. The addresses under consideration can be L2 or L3. Number of ARP packets discarded because the specified source MAC address in the received ARP packet is invalid. The source MAC address cannot be a multicast or broadcast or all zeros. Number of ARP packets discarded because the specified source MAC addresses in the ARP packet header and Ethernet header are not in sync. Number of ARP packets discarded because of internal software logic errors. Number of ARP packets discarded because of ARP cache overflow.

invalid-src-mac

invalid-user-mac internal-ctxt-error no-free-arp-entry (2 of 2)

IP User Port ARP Counters


The counters supported include both error counters and statistics counters. By default, only the summary error counter is maintained for each of the user ports. For monitoring or for trouble shooting purposes, the operator needs to explicitly enable the detailed counters.

Note 1 Because of resource constraints, there is a restriction on the number of user ports that can be enabled for ARP detailed counters. For a given Slot, only FIVE user ports can be configured for ARP detailed counters at any given point in time. Note 2 When the detailed counters are enabled, all the detailed error counters will be in their initial state of zero. These counters will account for any errors in packets processed only henceforth. The operator may choose to reset the counters to bring the error summary counter in sync with the detailed counters
Table TNG 109-11: Related CLI commands
Command configure ip vrf (index) user-itf port (port-interface) [no] arp-proxy-stats admin ip arp-proxy-stats (user-port) (clear-statistics) Description Allows the operator to enable or disable ARP detailed counters on a given user port. Allows the operator to clear the summary and detailed counters at any point in time.

TNG 109-6

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters

Table TNG 109-12 gives more information on the different individual counters.
Table TNG 109-12: Individual counters
Command Summary counters error-summary Detailed counters internal-ctxt-err unsupported-hw-type unsupported-l3-proto unsupported-addr-len Number of ARP packets discarded because of internal software logic errors. Number of ARP packets discarded because the received ARP packet header specifies a HW type other than Ethernet. Number of ARP packets discarded because the received ARP packet specifies a L3 protocol type other than IP. Number of ARP packets discarded because the address lengths specified in the packet are not supported. The addresses under consideration can be L2 or L3. Number of ARP packets discarded because the specified packet opcode is invalid. Number of ARP packets discarded because the specified source MAC address in the received ARP packet is invalid. The source MAC address cannot be a multicast or broadcast or all zeros. Number of ARP packets discarded because of ARP cache overflow. Maximum Number of ARP entries allowed in the cache is reached and hence packet is discarded. Currently this cache limit is set to 384, both per VRF and across all VRFs. Number of ARP packets discarded because the configured User interface is not supported. Only IPoE is supported. Number of ARP packets discarded because the Target IP specified in the received arp packet is invalid. The Target IP cannot be a class D, class E or a loopback IP address. It also cannot be a Directed Broadcast or a Limited Broadcast address. Number of ARP packets discarded because the Sender IP specified in the received arp packet is invalid. The Sender IP cannot be a class D, class E or a loopback IP address. It also cannot be a Directed Broadcast address. A Limited Broadcast address of all ones (255.255.255.255) is also not allowed. Number of ARP packets discarded because the Sender IP in the received arp packet has not been learnt on the incoming user interface (IP anti-spoofing). Number of ARP packets discarded because of both sender and target IP addresses having been learnt on the same user interface. Number of upstream ARP packets discarded because of unknown target IP. A target IP is classified as unknown if it does NOT satisfy any of the below criteria: Number of ARP packets that have been discarded because error checks have failed. Description

invalid-op-code invalid-src-mac

arp-cache-overflow

unsupported-user-itf invalid-target-ip

invalid-src-ip

unknown-user

identical-user-itf unknown-target-ip


(1 of 2)

Same as the gateway IP Is in the same subnet as the sender IP Is matching any other subnet of the gateway IP addresses configured on the user-gateway interface.

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 109-7

TNG 109 Performance management counters

Command unsupported-probe-pkt

Description Number of ARP Probe packets received and discarded. The received packet is classified as an ARP probe packet if the Sender IP in the packet has been specified as all zeros. This is a valid ARP packet but is currently not supported in LT and is treated as an error. Number of all ARP Requests received from User on this interface and responded. Note that ARP Gratuitous User requests will not be responded by LT. Number of all ARP Requests transmitted out on this user interface and responded by the User. Number of all ARP Requests transmitted out on this user interface and not responded by the User. This counter is also incremented, each time a re-try message is sent out. Number of all ARP Requests transmitted out on this user interface and for which the LT is currently in a pending state. Number of all ARP Gratuitous Requests that have been received by LT on this user interface and processed.

req-rx-and-reply

req-tx-and-reply req-tx-no-reply

req-tx-wait-reply grat-rx-and-accept

(2 of 2)

SHub DHCP Relay Agent Counters


The counters supported include both error counters and statistics counters. The error and statistics counters are defined at each VRF level. The counters are valid only if the DHCP relay agent has been enabled for the particular VRF.
Table TNG 109-13: Related CLI commands
Command admin dhcp-relay shub vrf-agent-stats (vrf-id) (clear-statistics) Description Allows the operator to clear the VRF counters at any point in time

Table TNG 109-14 gives more information on the different individual counters.
Table TNG 109-14: Individual counters
Command fwd-upstream Description Counter is incremented every time the DHCP relay agent transmits a DHCP message upstream towards a DHCP server. In case the same message is transmitted to more than one DHCP server, every transmitted copy of the message is counted. Counter is incremented every time the DHCP relay agent transmits a DHCP message downstream towards the DHCP client (User). Number of DHCP messages received by the relay agent from LT/User. Number of DHCP messages received by the relay agent from network. Number of DHCP packets that were not forwarded by the relay agent and discarded.

fwd-downstream rx-upstream rx-downstream errors

(1 of 2)

TNG 109-8

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters

Command internal-ctxt-err packet-expired malformed-packets

Description Number of DHCP packets discarded because of internal software logic errors. Number of DHCP request packets discarded because time stamp on the packet is less than the threshold time as configured on the relay agent. Number of DHCP request packets discarded because of packet corruption. Magic cookie verification has failed. Magic cookie is 4 byte field before the Options field in a dhcp packet. Number of DHCP request packets discarded because packet hops exceeded the configured maximum hops.This check is done only if giaddr of incoming Packet is not equal to Zero. Number of DHCP packets discarded because the packet matches an existing context in the relay agent, but on a different port. Number of DHCP packets discarded because of failure to add a new context for an incoming packet.Maximum number of Contexts for SHub globally across VRFs is 512. Number of DHCP request packets discarded because giaddr of incoming packet matches one of the interfaces' address in the VRF. Number of DHCP response packets discarded because DHCP reply does not contain SHub interface address as giaddr. Number of DHCP packets discarded because route to the DHCP server could not be determined. Number of DHCP response packets discarded because the received DHCP reply could not be associated with any existing context. Number of DHCP packets discarded because the received packet does not contain a valid message type . The message type should be either BootRequest / BootReply. Number of DHCP request packets discarded because the giaddr in the received packt is zero while the hops count is non zero. Number of DHCP packets discarded because the 'htype' and 'hlen' fields of the received packet do not correspond to Ethernet type and Ethernet mac length or the chaddr field in the packet has been specified as zero.

too-many-hops

dup-client-hw-addr no-free-context

upstr-invalid-giaddr downstr-invalid-giaddr no-route-to-server downstr-no-ctxt-found invalid-packet-type

invalid-hops invalid-client-hw-addr

(2 of 2)

User Port DHCP Relay Counters


The counters supported include both error counters and statistics counters. By default, only the summary error counter is maintained for each of the user ports. For monitoring or for trouble shooting purposes, the operator needs to explicitly enable the detailed counters.

Note 1 Because of resource constraints, there is a restriction on the number of user ports that can be enabled for DHCP detailed counters. For a given Slot, only TEN user ports can be configured for DHCP detailed counters at any given point in time. Note 2 When the detailed counters are enabled, all the detailed error counters will be in their initial state of zero. These counters will account for any errors in packets processed only henceforth. The operator may choose to reset the counters to bring the error summary counter in sync with the detailed counters

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 109-9

TNG 109 Performance management counters

Table TNG 109-15: Related CLI commands


Command configure dhcp-relay [no] port-stats (port-interface) admin dhcp-relay port-stats (user-port) (clear-statistics) Description Allows the operator to enable or disable DHCP detailed counters on a given user port. Allows the operator to clear the summary and detailed counters at any point of time.

Table TNG 109-16 gives more information on the different individual counters.
Table TNG 109-16: Individual counters
Command Summary counters error-summary Detailed counters internal-ctxt-err up-corrupt-pkt Number of DHCP packets discarded because of internal software logic errors. Number of upstream DHCP packets dropped because of one of the following: Number of DHCP packets that have been discarded because error checks have failed. Description

Error in retrieving L2 frame / L2 frame details from the received buffer IP checksum does not match the one specified in the IP header Mismatch between the packet lengths specified in the IP header and UDP header. The following equation needs to be true if a packet is valid: IP Total Length - IP Header Length = UDP Length. The IP Total Length and IP Header Length are specified in the IP header while the UDP Length is specified in the UDP header IP Total Length specified is more than the received L2 Frame payload size UDP checksum does not match the one specified in the UDP header. However if the received packet contains an all zero checksum, no validation is done. An all zero UDP checksum indicates that the transmitter has generated no checksum and hence no validation can be done

up-invalid-l2-proto

Number of upstream DHCP packets discarded because of invalid Layer 2 protocol configuration. The user interface has been configured in L2 forwarding mode and the received packet does not have an Ethernet header. DHCP in L2 forwarding mode is possible only for IPoE user interfaces. Number of upstream DHCP packets dropped because the specified protocol version in the IP header is not IPv4. Number of upstream DHCP packets discarded because the received IP packet size exceeds the MTU for the Ethernet side. For example, this packet could have been received over a IPoA user interface. Number of upstream DHCP packets discarded because the received DHCP packet is a fragmented IP packet. Fragmented packets are not handled.

up-unsupp-l3-proto up-large-pkt-discard

up-frag-pkt-discard

(1 of 4)

TNG 109-10

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters

Command up-malformed-option

Description Number of upstream DHCP packets dropped because the 'options' field in the received packet could not pass the error checks. The errors include:

The options field does not start with the magic cookie. Option 82 exists but is not followed by the 'End' option. Option 82, if present, has to be the last option in the DHCP options list. Mismatch between the 'Options' length as derived from the received DHCP packet and the sum of the lengths specified by each of the individual options. Semantic checks for all the options specified in the packet. Some of the options that could be specified are: DHCP Message Type, DHCP Lease Time, DHCP Requested Address, DHCP Server Identifier etc. The above option list is only indicative. It is not exhaustive.

up-invalid-hops

Number of upstream DHCP packets discarded because the 'giaddr' field is null but the 'hops' field is not zero. If the 'hops' field has been incremented by another relay agent closer to the user, the 'giaddr' value needs to be set to a valid Relay Agent IP address. Number of upstream DHCP packets discarded because the received DHCP packet header specifies an invalid opcode. It is neither a BOOT REQUEST nor a BOOT REPLY. Number of upstream DHCP packets discarded because the received packet type is not valid in upstream. The received DHCP packet is a server initiated DHCP message. Users cannot act as a DHCP Server and hence server initiated DHCP messages are discarded in the upstream. The packet is identified as a server initiated message by one of the following:

up-invalid-op-code

up-not-allowed-pkt


up-opt82-too-long

the packet header specifies the opcode as a BOOT REPLY message. the message type specified in the DHCP packet is one of the following: DHCP OFFER, DHCP ACK, DHCP NAK or DHCP FORCERENEW.

This counter is incremented whenever the received DHCP packet, after Option 82 insertion, exceeds the MTU for the Ethernet side. However in this case the packet will NOT be discarded. The error counter will be incremented and the packet processed without option 82 insertion. Number of upstream DHCP packets discarded because of the presence of Option 82 in the received packet when it should not have been present. ISAM treats all user ports as untrusted. So when a DHCP packet is received with giaddr set to zero but with an Option 82 already inserted, the packet is discarded. Number of upstream DHCP packets discarded because the client hardware address, 'chaddr', has been set to an invalid value. Counter incremented in each of the below scenarios:

up-not-trusted

up-invalid-chaddr

Received packet has the client hardware address, 'chaddr', set to zero. The 'chaddr' value specified is not in the MAC address format. The 'htype' and 'hlen' fields of the received DHCP packet do not correspond to Ethernet MAC addresses. There is no further downstream relay agent closer to the user and the 'chaddr' value specified in the received BROADCAST DHCP packet does not match the source MAC address of the ethernet frame. Hence discarded.

up-dup-chaddr

In case of DHCP session snooping, number of upstream DHCP packets discarded because of duplicate chaddr. There already exists a DHCP transaction with the same 'chaddr' value as the one specified in the discarded packet on another user interface. In case of DHCP session snooping, number of upstream DHCP packets discarded because of IP anti-spoofing failure for 'giaddr' field. In case of DHCP session snooping, number of upstream DHCP packets discarded because of IP anti-spoofing failure for 'ciaddr' field or the user specified DHCP option 'Requested IP Address'.

up-invalid-giaddr up-invalid-ciaddr

(2 of 4)

Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 November 2007 3HH-05218-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI

TNG 109-11

TNG 109 Performance management counters

Command up-no-free-context

Description In case of DHCP session snooping, number of upstream DHCP packets discarded because no free context is available. Applicable constraints are as below:


up-no-assoc-context

In the upstream, a maximum number of only four contexts can be created per port. In addition there is also a global limit across all ports for a given LT. Currently a maximum of 384 contexts are supported per LT at any given time.

In case of DHCP session snooping, this counter represents the number of upstream DHCP packets received for which no session context could be associated and hence discarded. Upstream DHCP messages of type DHCP RELEASE and DHCP DECLINE can only be processed if they are related to existing DHCP sessions. MAC concentration has been enabled for the Relay Agent. This counter represents the number of upstream DHCP packets discarded because they have already been relayed by another relay agent closer to the user. Relay packets are not handled if MAC concentration is enabled. Number of upstream DHCP packets discarded because no Upstream broadcast VLAN has been configured for this VRF. This needs to be configured as the LT broadcasts the DHCP messages on this VLAN. Number of downstream DHCP packets discarded because of the presence of Option 82 in the received packet when it should not have been present. The Option 82 insertion has been switched off for this VLAN and there is no further downstream relay agent closer to the User. So Option 82 should not be present in the received DHCP packet. In case of DHCP session snooping, number of downstream DHCP packets discarded because the client IP address, 'yiaddr', in the received packet has been set to an invalid value. Counter incremented for each of the below scenarios:

up-relay-agent-unsupp

up-no-broadcast-vlan

dn-not-trusted

dn-invalid-yiaddr

Received a unicast DHCP ACK from the server and there is no further downstream relay agent closer to the user. Packet is discarded because Yiaddr != Destination IP address. Received a DHCP ACK with a Yiaddr value different from what has been specified in the upstream DHCP REQUEST. The IP address offered to the User is same as the Server IP address. The server IP address is specified in the DHCP option 'server-identifier'. Yiaddr value cannot be set by the DHCP server to its own IP, hence discarded.

dn-invalid-server-resp

In case of DHCP session snooping, number of downstream DHCP packets discarded because of invalid response received from the DHCP Server. The server-identifier option specified in the DHCP ACK/NAK message does not match the server-identifier as specified in the corresponding upstream DHCP REQUEST message. In case of DHCP session snooping, number of downstream DHCP packets discarded because no free session context is available. A DHCP session is created on the receipt of a DHCP ACK in the downstream. For a given LT, there is a global limit across all ports on the number of session contexts that could be created. Currently a maximum of 384 sessions could be created at any given time for a given LT. Count of all DHCP packets received in the upstream and successfully inserted with option 82. For option 82 insertion to be successful, the Option 82 insertion flag must have been enabled for the associated VRF/VLan and the packet must have passed all the error checks.

dn-no-free-context

option82-inserted

(3 of 4)

TNG 109-12

November 2007 Alcatel-Lucent 7302 ISAM R3.4 FGN3.5 | 7330 ISAM FTTN R3.4 FGN3.5 Operations and Maintenance Using CLI Edition 02 Released 3HH-05218-AAAA-TQZZA

TNG 109 Performance management counters

Command option82-removed

Description Count of all DHCP packets received in the downstream and from which option 82 has been successfully removed. For option 82 removal to be successful, the Option 82 insertion flag must have been enabled for the associated VRF/VL